lunduke-retarded: GitHub Becomes a Compliance Ledger

A community tracker turns distro statements into a source-linked map of who will comply with OS-level age verification laws, and who will not.

8 min read • View on GitHub • More from dmtrKovalenko

A black ink illustration shows a filing clerk sorting source cards into a huge ledger cabinet while threads connect each card back to pinned clippings on a wall. It explains that the repository works as a curated index of public positions, not as a conventional software project. — The project behaves like an index of stances, with each entry tied back to a public source.

Key Takeaways

This repository functions more like a public ledger than a software project.
Its value comes from turning scattered statements into a single source-linked index.
GitHub makes the debate legible because it adds canonical URLs, history, and contribution flow.
The repository's real competition is not other code, but the chaos of unindexed policy chatter.

GitHub usually hosts code. Here it hosts a position. The interesting move in dmtrKovalenko/lunduke-retarded is that it turns a policy dispute about age verification at the operating system layer into something you can scan, share, and update like a project board.

Omarchy has no plans to do anything in response to this retarded California law.

David Heinemeier Hansson (DHH), Creator of Ruby on Rails, co-founder of Basecamp & HEY, lead of Omarchy · Podscan episode

Why this repo exists

The repository appears to sit at the edge of journalism, protest, and open-source bookkeeping. Based on the metadata and the surrounding reporting, its job is to document how Linux distributions and adjacent projects respond to age-verification mandates in places like California and Brazil.

Lunduke started a list of distros without the age verification nightmare

Katja Lutz, Nostr User · Nostr note

That is why the format matters. A blog post can explain one stance. A repo can hold many stances side by side, keep them source-linked, and make contradictions obvious. In practice, the project is closer to a living dossier than a library.

What makes it different

The name signals that this is not trying to look neutral, and that is part of the point. The repository is not pretending to be a detached standards document. It is using GitHub's familiar mechanics, commits, issues, pull requests, to turn a messy public argument into a shared reference point.

The repo acts as a junction box. It gathers public statements, normalizes them, and exposes one searchable index.

Seen this way, the repository is not a destination. It is a routing layer. The value is not in the raw statement itself, but in the fact that the statement becomes comparable, portable, and easier to revisit when the debate moves.

How it works

Each entry points back to a public source.
Each stance gets reduced to something scannable.
Each update keeps the history visible instead of overwritten.
The format stays simple enough for strangers to contribute.

That simplicity is the whole trick. The repository does not need heavy automation to be useful. It needs discipline, clear sourcing, and a shared convention for recording whether a project will comply, refuse, or stay silent.

Compared with other ways to track the issue

Tracking method	What it does well	Where it falls short
Community GitHub tracker	Centralizes stances into one searchable index	Relies on human curation and source discipline
Official distro blog or README	Holds the most authoritative answer	Scattered, hard to compare across projects
Podcast or news coverage	Captures context and friction	Difficult to skim, diff, or maintain

The real competition here is not another app. It is entropy. When policy pressure reaches the OS layer, somebody has to turn scattered statements and commentary into something a developer can inspect in thirty seconds. This repo tries to do exactly that.