90
I Spoke To The Developer Of The Systemd Birth Date PR - YouTube
(www.youtube.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
So they added a date of birth field. Not technically doing anything wrong but a concerning direction morally. If it wasn't for the fash / authoritarian bullshit in the world that field wouldn't be a problem.
However, the question is how should the Linux community respond. Rather than grabbing pitch forks we should do what the Linux community does best. Support the alternatives, be it a fork or a replacement stack.
I'm watching for what lands and becomes popular. It seems inevitable that Devs in countries that aren't forcing ID checks will build what we need. I hope to see either a fork of systemd free from redhat influence (always suspicious of large corps), or a true set of alternatives that can realistically replace the systemd stack.
The community will drive the change. Put down your pitch forks, pick up your keyboard yourself, or just support the good Devs instead.
I expect someone will just make a systemd patcher package that removes the field and provides clean error handling for anything that tries to use it.
You're not going to get something complying with Californian law out of Brazil (for example), so you're talking about diverging. California can have it's own version. Sadly that pushes burden onto maintainers that may not be interested in dealing with the pain.
The engineering mindset is to have it support both use models, but that is explicitly what people don't want. Hidden features which enable authorities to enforce toxic concepts.
What toxic concepts can authorities enforce with your birthDate that they could not already enforce with your realName?
This is a question that nobody has an answer to.
The entire premise of this argument is that adding birthDate allows for some new kind of oppression not previously possible and so it should be fought or else someone will use it in a bad way.
Except, if that were true, these hypothetical evil forces could already have access to your REALNAME and LOCATION. Both of which are fields that have existed since the 60s.
That hasn't happened, those fields, like birthDate were added to allow support for some use cases and outside of those uses cases (which, you have to choose to implement because you are in complete control over your system in the FOSS world) the fields are completely optional and not used.
I don't care if that optional field exists in the config. Implement age verification if you want, just don't make it mandatory. My working laptop with Ubuntu has fingerprint verification, which I can disable. I didn't even know about this functionality before. If this stays in systemd like this, then whatever