Loading...
Loading...
systemd maintainers merged a pull request adding a birthDate field to JSON user records to help applications support age-attestation needs brought on by new laws (California, Brazil and elsewhere). The change, proposed by Dylan M. Taylor, stores a user's birth date in YYYY-MM-DD and allows admins to set it; unprivileged users cannot modify it but can be queried via the XDG Accounts portal. The proposal sparked an intense and hostile backlash—including doxxing and threats—despite the change being
Linux developer Dylan M. Taylor proposed adding a birthDate field to systemd's JSON user records so applications can record users' birth dates for age-attestation and age-verification compliance. The change—intended to let admins set birth dates (YYYY-MM-DD) while preventing unprivileged modification but allowing queries via the XDG Accounts portal—sparked a disproportionately hostile reaction, including doxxing and death threats against Taylor. Some community members raised legitimate concerns about portability (System76) and legal exemptions, while others argued such requirements are likely to spread. Maintainer Luca Boccassi merged the change after discussion; the article stresses the difference between attestation (self-reported) and external verification and notes the feature alone doesn’t implement attestation systems.
systemd maintainer Dylan M. Taylor added a birthDate field to systemd's JSON user records to let applications store users' birth dates for potential age-attestation workflows; the change was merged by Luca Boccassi after discussion. The proposal sparked a disproportionate backlash, including doxxing and death threats against Taylor, driven by misinformation despite the change being a small, opt-in storage feature (unprivileged users cannot modify the date). The article distinguishes age attestation (user/administrator-provided data) from age verification and notes legal drivers—California and Brazil laws and talk elsewhere—pushing distributions to support compliance, plus concerns about portability to non-systemd systems raised by System76. The author argues the reaction was overblown given the narrow scope of the change.
A controversial proposal to add an optional age (date-of-birth) attestation field to systemd sparked a sharp backlash, with critics arguing the OS should not collect identity-related data and accusing maintainers of political overreach. The debate intensified on Hacker News and LWN, where proponents noted the field is optional and similar metadata (name, email, location) already exists; opponents countered that even optional DOB data is unnecessary and risky. The discussion escalated beyond technical critique: project lead Taylor faced targeted harassment, doxxing, and death threats. The episode matters because it highlights tensions around privacy, metadata in core system components, open-source governance, and how community disputes can threaten maintainers and project security.
systemd maintainers merged a pull request adding a birthDate field to JSON user records to help applications support age-attestation needs brought on by new laws (California, Brazil and elsewhere). The change, proposed by Dylan M. Taylor, stores a user's birth date in YYYY-MM-DD and allows admins to set it; unprivileged users cannot modify it but can be queried via the XDG Accounts portal. The proposal sparked an intense and hostile backlash—including doxxing and threats—despite the change being a minimal storage feature rather than a full attestation/verification system. Some technical objections focused on portability and whether distributions might instead avoid legal exposure; maintainers noted attestation vs verification are distinct issues.