

Good system design doesn’t do things without me asking it to. I’ll gladly manually re enter my birth date for an external service if its required, which to be clear, should be as close to 0 times as possible. What, should I keep all my job application info in the initialization system too? Because a website I’m on might ask for it at some point? Don’t want to be too redundant.
Literally this field serves no purpose other than to build compliance with the surveillance state. No end user asked for this. Like I said, can’t imagine any end user making use of the existing systemd fields either. But those also didn’t get any attention because they weren’t made as a reaction to threats by a malicious regime.





It was also an option to not make a useless field. Not like this self reported dob is going to cut it for the existing age verification laws as is exists now. But I can be mad at people in a position of community production for not having a spine, too.
How is this supposed to be making the best of the situation anyway? It accomplished nothing but piss off the community and signify to authoritarians that open source developers are ready to bend over for them. Simply threaten unenforceable fines across the world and suddenly everything is hopeless. Better get ready to comply, its inevitable! Its pathetic. Ageless Linux might be performative bs, but at least its critical of this over reach instead of intentionally signalling compliance in advance.