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.
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
deleted by creator
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)
The same with the birthDate field.
I think back then it was generally assumed this simply assisted with office communication.
Imagine telling a UNIX engineer in the 70’s how almost everything you enter into a machine would eventually be used to manipulate or entrap you by the State and surveillance capitalism.
This isn’t a hypothetical. North Korea uses a version of Linux which does exactly that.
It still doesn’t make these fields inherently dangerous, and that same argument applies to birthDate. Even if systemd build a verification system that required photo identification and a DNA sample it wouldn’t be a problem.
The community would just fork the project before the totalitarianism update. The FOSS world already has a process to avoid massively unpopular changes. This change isn’t massively unpopular, this is a vocal minority who is stirred up by web articles leveraging clickbait and outrage to drive ad revenue.
The age verification laws are unpopular, I’m personally completely against them. However, they do exist and adding an optional field in order to allow project, who choose to do so, to store that data is not a red line or the start of a slippery slope.
In the future, if there was a red line that was crossed, we would fix it with a fork and not with a harassment campaign.
https://en.wikipedia.org/wiki/Boiling_frog
That’s you. You have no issues giving anyone an inch and then wondering why you’re being lined up on the street afterwards once they’ve taken the mile.
https://en.wikipedia.org/wiki/Slippery_slope
That’s you. You have no issue embarking on a creative writing exercise, painting the scariest possible scenario and pointing at that piece of fiction as if it were reality.
You think you can just make up lies about countries far away from you and no one will notice? Think again, whisu.
Stored “because law”, right?
Who cares why it is stored, these fields exist for every user in every Linux system and they have existed for decades.
Either birthDate the field is dangerous or it isn’t. If it is, how?
It is no different than data fields that ask for way more identifiable and personal information such as Real Name and Office number which have, again, existed for decades without issue.
I care. One thing is “you know, fields with this name have been around since before you were born”, another thing is “some idiots passed the law half the globe away, now we are preparing your system to comply. Someone has to ©”. The field is not the danger, the thinking, attitude and act is
Edit: some local law, for fuck’s sake
Half a world away where do you live since this is happening everywhere. To be half a world away from any place doing this would be hard.
That’s a fair argument.
Is it fair to say: The field is benign but there is contention about if it should be added or not and users of the software are concerned that their voices were not heard on the issue. That can be handled in the normal project framework, perhaps by suggesting a publicly stated policy about these issues around legal compliance so the community can determine if they want to support the project or not.
My argument is that I don’t think that the damage that was done justifies the hitpiece in the OP which is, almost literally, painting a target on the developer with the mugshot photograph and loaded language.
So, if you’re not one of the people then we’re having different conversations. In that conversation, I do agree with what you just said. I’d like to see the very large projects, which affect a lot of users, such as systemd, have a more formal way to accept public comment and respond on contentious changes and feature requests.
It is benign if it is optional, remains 100% local and under the user’s control and doesn’t prevent other software from functioning as expected.
You must be off by a decade. Your reference mentions no OS and Unic was developed around 1970.