levino

Top 10 Security Incidents (letzte ~10 Jahre, nach Schaden)

Diese Tabelle zeigt die 10 teuersten Cybersecurity-Incidents seit ~2013, kategorisiert danach, ob die Ursache eine kompromittierte Dependency (echte Supply-Chain-Attack) oder ein eigener Bug (Patch vergessen, keine MFA, schwache Krypto) war. Ergebnis: 70% der größten Incidents hätten durch Security-Basics verhindert werden können.

Incident	Jahr	Schaden	Kategorie	Link
SolarWinds	2020	~$100 Mrd.	Dependency kompromittiert	senate.gov
NotPetya	2017	~$10 Mrd.	Dependency kompromittiert	beyondidentity.com
MOVEit	2023	~$10+ Mrd.	Dependency kompromittiert	huntress.com
WannaCry

levino

Git-Based Media Platform: Architecture Specification

Vision

A fully git-based, headless video and audio podcast platform. No web interfaces, no databases, no CMS. Content lives in a git repository, media assets in S3-compatible storage, and everything is controlled from the terminal and text editor. AI coding tools handle the heavy lifting of implementation.

Why Not PeerTube or Castopod?

PeerTube

levino

📘 One-File Markdown Demo (Mermaid Everything)

Dieses Dokument ist eine einzige Markdown-Datei mit allen Mermaid-Beispielen: Flowcharts, Graphen, Sequences, Timelines, States und Charts.

👉 Funktioniert direkt in GitHub Repos und GitHub Gists (ohne Setup).

---

1️⃣ Flowchart

levino

GitHub as a Backend for Collaborative Work

Architecture & Implementation Specification (Discussion + AI Contract)

---

1. Motivation & Background

Many organizations – NGOs, associations, initiatives, editorial teams, political organizations, as well as companies – produce large amounts of structured digital content: internal documentation, policies, protocols, resolutions, position papers, as well as external artifacts such as letters, invitations, or documents following a strict corporate design (for example via Typst or Markdown templates).

From a technical perspective, Git, Markdown, CI/CD, and AI are well suited to manage this content in a versioned, auditable, and highly automated way. In practice, however, these workflows often fail due to accessibility: GitHub is powerful, but for many contributors it is too complex, English-only, and cognitively overwhelming.

levino

{
  
}

levino

type standardFunction = (arg1: number, arg2: number) => number

// Should be okay
const add: standardFunction = (arg1, arg2) => arg1 + arg2 // Types can be inferred from 'standardFunction'
const addLater = (
  arg1: number,
  arg2: number
): (() => Promise<number>) => async () => arg1 + arg2 // Return type of promise can be inferred from type definition of 'addLater'

// Should not be okay

levino

import * as R from 'ramda'
import * as React from 'react'
import { ReactElement } from 'react'
import { connect } from 'react-redux'
import { State } from 'src/selectors'
import * as urlJoin from 'url-join'
import * as selectors from '../../../selectors'
const API_URL =
  process.env.REACT_APP_API_URL ||
  `https://api.example.com/.netlify/functions`

levino

diff --git a/node_modules/scrypt/index.js b/node_modules/scrypt/index.js
index 7b13a79..1e40d76 100644
--- a/node_modules/scrypt/index.js
+++ b/node_modules/scrypt/index.js
@@ -1,6 +1,6 @@
 "use strict";
 
-var scryptNative = require("./build/Release/scrypt")
+var scryptNative = require("./build/Release/scrypt.node")
   , Crypto = require("crypto")

levino

declare module 'bn.js' {
  type Endianness = 'le' | 'be';
  class BN {
    constructor(
      inputNumber: number | string | number[] | Buffer,
      base?: number,
      endian?: Endianness
    );
    clone(): BN;
    toString(base?: number, length?: number): string;