this post was submitted on 25 Mar 2026
78 points (68.1% liked)
Linux
64114 readers
567 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To be clear, I would also be outraged if some personal privacy nightmare got merged into foss projects I used.
However, adding an optional field to userdb for self reporting of age is definitely not a privacy concern. I honestly have not heard a valid argument against this addition of an optional field. Most are just appeals to emotion/outrage not grounded in the reality of what code was actually committed/merged.
What benefit is there to have it? The only purpose it serves is to create privacy concerns.
Benefits:
I maintain that optional self reporting of age is not a privacy violation. Would you clarify: what specific privacy concerns does the merged systemd PR create? Be specific about the material consequences it has on the privacy of users.
How is having a centralized store of all your demographic information where any app can query it on your OS a privacy concern? Are you serious? Maybe people don't want to send their personal information to every single god damn thing that asks for it?
Example:
The Datastealingassholes app wants your data
Without this: You are prompted to enter your DOB in a field, decide fuck no, and that's that.
With this: They query the data store on your OS and they have whatever they want without input from you. Maybe the app is run by a bad actor trying to spy on you. They already have your DOB. It just confirmed for them that YOU are the person operating this PC.
Your example relies on some assumptions:
None of these assumptions are garunteed by the merged code into systemd. The following are optional, and not required as a result of the code merged into systemd:
It’s possible to put your full first and last name into your user, so by your logic the first and last name fields of the user profile should not exist.
Did that help identify the absurdity of your argument?
It doesn't guarantee anything, but does open the door for it. Now that this functionality exists, apps are going to start using it and requiring it. It's now something we all have to worry about and compensate for going forward.
If you're not putting accurate information in there why have it at all? Why argue in favor of it? There is literally no benefit to having this shit other than to comply with a bullshit law that they could get around by simply blocking California users from downloading their OS (this wouldn't actually work because peer to peer exists, but it would eliminate the OS developers responsibility in the situation).
Agreed
Despite all of us collectively agreeing that the law is dumb/flawed, the 40 M residents of Cali should have the liberty to be able to use distros that depend on systemd, legally. And, the developers of these distros using systmed (whether you interpret the law to see them as OS providers or not) want to be able to provide these distros legally.
Yes, but not all apps. While the CA law mandates that app developers must use some API to get the age bracket, the merged code into systemd is not causually related to all apps actually implementing and using the API. Just because systemd merged this code does not inherently result in every single user application querying this, nor does it force you to install apps that do query the API. One may freely choose to not use apps that require it. If one needs an app that requires it, one may set a garbage DOB to their user. I don't see this as an issue. Do you?
It seems you disagree with the law (so do I) but are blaming the wrong person here (author of merged systemd code). I maintain that complying with the law is harmless, and thus it is beneficial to add this DOB field to the userdb json, because in all cases of some distro user using their computer, they are not compelled to compromise their personal privacy.
Disagree, they should deal with the consequences of electing mentally deficient legislators. But even so. They could make a fork that meets californias requirements and leaves the rest of us out of it. No reason the whole god damn world should be dragged down with one shitty state.
Not every app that does this will have a viable alternative that doesn't. And yes there is an issue, putting in a fake DOB isn't a sure bet because what if some of the apps that you must use that start utilizing this API are comparing their info against yours for some kind of verification purpose, while you also must use another app that uses it that you do not want to provide your DOB to? You can't have it both ways with this system.