Stores the user’s birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.
Stores the user’s birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.
They literally said it’s to address the laws in the PR.
systemd: “Yeah sure, here you go, some integers maybe. Could just be some zeroes, who cares, not me”
bunch of lazy reaction-baited dummies: “it’s age verification!”
It’s one step toward addressing the laws, but systemd isn’t going to implement the remaining steps to have actual age verification.
Just one little aoldier following orders. There are definitely not copious numbers of examples of that going poorly…
But they did what the laws (Californian, Colorado’s and basically every other, except for the New York’s and Texan) required them to do.
And then expand in the further discussion that the field has further use besides compliance, and that even if it complies that a field that you can control whenever is not real verification. Please don’t be a headline Andy. I’ve also been one, but if I’m to dive in comments and write about it I usually give it a read, specially if I reference the content of the post.
I’m not a headline Andy. They literally said, in the PR, that it was also to address these laws. It is not a slippery slope fallacy when they’re citing it as a reason. It’s part of the fucking motivation. It’s part of the reason it exists in the first place.
Just because you are too young/naive to understand how this kind of shit turns over in the real world, and/or too illiterate to read PR comments, doesn’t magically make all the people upset about it alarmists.
Yes, and the laws (so far) are exactly that: you input an age, and provide that age to applications that want it. No further identity verification or anything.
I don’t like the law for the precedent but as it stands it’s a harmless, potentially even useful feature.