March 21, 2026
Age rage meets penguin pride
Revert "userdb: add birthDate field to JSON user records
Linux slams the brakes on age checks — comments erupt
TLDR: Developers scrapped birth date storage in Linux over privacy, shaky laws, and no consensus. Comments split: anti-systemd purists celebrated, parents pitched privacy-friendly age signals, and jokers mocked naming—signaling a bigger moment of open-source saying “no” to age-gate pressure.
Linux devs just yanked a plan to stash birth dates in the user database so apps could ask the OS (the core software running your computer) for age signals, and the comments turned into a bonfire. The strongest voices shouted privacy and freedom: no new sensitive data, no “permission checks” creeping into your desktop, and definitely no turning Linux into an age cop. One fiery reply declared systemd (the controversial service manager) has gone from tech trouble to political drama, while another rallied the old-school mantra: programs should do one thing well. Snark also landed: someone suggested updating ancient POSIX standards instead, another dunked on the proposed camelCase naming, and a skeptic quipped it would be a shock if “systemdb” ever did the right thing. Yet a minority tossed a curveball: OS-level age signals could make parental controls simpler and more private than websites demanding IDs, citing platforms like Discord. The devs pointed to messy laws, lack of consensus (Ubuntu, Fedora hit pause), and a broken enforcement story. They left a tiny window open for zero-knowledge age proofs—cryptography that proves your age without revealing your birth date. Until then, the penguin crowd cheered: keep the OS clean. Read more via Fedora’s thread and System76’s post.
Key Points
- •The project reverted a change to add a birthDate field to system user records and dropped OS-level age attestation plans.
- •Privacy and freedom concerns were central: storing birth dates in the OS creates new sensitive data and risks normalizing permission checks.
- •Enforcement is impractical without invasive verification, and non-signaling OSes could face site/app blocks, creating de facto requirements.
- •Legal uncertainties across jurisdictions (e.g., California, Colorado) and misalignment with open-source philosophy influenced the decision.
- •No upstream consensus existed (freedesktop.org MR closed; Ubuntu/Fedora not adopting; systemd PR draft); the team may revisit if privacy-preserving standards or legal clarity emerge.