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.
to all y’all with the “it’s just a text field”: what if the field is “race”? “sexual orientation”? “jerks_off_to”? what the fuck has a system managing daemon got to do with any of that? and why would you preemptively put it in there without even a pretense of a fight?
fuck you make us! make linux illegal, in Cali of all places. guess how long that will last?
Yeah, scary.
What about some other scary fields like:
I mean if those fields were stored, could you imagine the danger that Linux users would be in?
You don’t have to imagine, because those fields have been stored in UNIX/Linux since 1962. https://en.wikipedia.org/wiki/Gecos_field
Your argument is an informal fallacy called Whataboutism.
I invite you to educate yourself by reading about it on Wikipedia
Those are also entirely optional and not having them filled in doesn’t cause other software to stop doing what the user wants.
(same for the birthDate field)
Not true. Because the stated purpose of the laws at play is to enable that to be queried so that sites can decide what is appropriate for you to see.
That is the purpose, but the field is implemented as optional and modifiable with admin privileges.
That is not the point and you know it.
Your point is true, but I’m saying its impact is also optional.
The option is not supposed to be there at all. Don’t comply with ANY part of it, especially in advance.
The same with the birthDate field.
… unless someone merges a PR making it required, which is the discussion of this thread.
What if someone makes a PR making your real name and address being required? Damn…
So you’re arguing that systemd shouldn’t have reverted that pointless PR because it’s not actually enforced? Sorry, I’m probably not understanding your comment