I'm still trying to figure out how systemd has anything to do with this. Any configurable level user database could have implemented this. /etc/passwd has your "Real Name" in it as well. Finger protocol could have been selected to expose this. Literally there's dozens of different places the age thing could have been implemented. The maintainers of systemd decided to be the first. Hell, MidnightBSD just added a daemon to implement it.

Likewise if you're informed enough you also know there's a flag to explicitly block it and ways to patch it out. While I'm typically a Slackware and sysvinit type of person, there's nothing unique about systemd that enabled the shitty law California passed. And fi you really care about privacy, how about less gloat and more information about ways around it, like this fork.

You'll go a lot further educating folks how to get around the things you perceive as bad rather than whatever your original comment was. The entire point is to get people ... on your side.

i guarantee you the lawmakers who pass this kind of awful law have no idea what systemd even is or what it does

blaming it (or "systemd simps") for this is a colossal waste of time. the surveillance society has been progressively installed in the imperial core ever since 9/11, age verification and what’s it turning into is a consequence of this, and systemd adding an age field is a consequence of that.

blaming systemd for this shit, even in part, is so bafflingly silly, such a ridiculous example of swapping cause and effect that i can’t imagine you’re doing it sincerely but apparently people agree with this???

that’s like blaming the small creek in your garden for the existence of the raging river upstream. idk.

It was obvious from the start that enabling DRM and surveillance was the point of systemd all along.