Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
I have read the git thread related to the merge request.
I don’t see what’s the big deal. You have a user model that already contain fields like user’s full name, location, … among others and all this developer did was adding yet another optional field called date of birth.
This does nothing to verify user’s age and enforce nothing. They’ve stressed that repeatedly in the comments.
What that does is making it easy for a Linux distro to store user’s birthday - should they wish to do so - and making that bit of info accessible to running apps so that each app can do what it wants with it.
User’s fullname and location are already there which are also optional so what’s the big deal?
Fields like name and location do not have any expectation for the information being valid or accurate (see eg.:
adduser).DOB is different. It comes from a legal expectation that correctness of the information will be enforced somehow. If going by the Colorado and NY law proposals, IIRC, by using biometrics at the time of system install.
[citation needed]
…Have you eve been following the news and the law proposals? I’m not sure you are engaging in good faith here.
not even said laws have an expectation that the date of birth provided would be accurate. the colorado bill just says “require[] an account holder to indicate” and never defines “indicate”, the ny bill says “request an age category signal” and never defines “signal”, so i assume they’re like the california law which has been verified to be just “enter your date of birth in this text field/dropdown and we’ll trust you girl”. i don’t think any of that involves biometrics
there’s no alien intelligence or protocol specification in systemd that ensures or says the dob field must be accurate either
Wow, picking choice words only in sections of the laws and proposals. At least try and engage in honest discussion, mate,
Honestly, just go check Ageless Linux’s site. They have a complete rundown on how and where does each law’s expectation come from.
Just one (1) example:
Requires “commercially reasonable” method. In other words, the powerful agents of the market (the Googles, the Facebooks, the NSAs) get to choose what you have to do to validate. Could even require biometrics.
That’s because systemd, a well-known Microslop infection into the Linux ecosystem, is using the wayland playbook: specify nothing, leave to other projects the task and legal weight of implementation. All systemd has to do is to ship the field, then other projects are delegated the task of entering in a “legally compliant” way.