this post was submitted on 24 Mar 2026
552 points (91.2% liked)

Technology

83027 readers
3628 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Blemgo@lemmy.world -3 points 1 day ago* (last edited 1 day ago) (1 children)

I don't think that systemd is really bending the knee too hard on this one. Actually, I think this move is actually a great way to render any sort of age verification, when using systemd, inert. Because, let's think about it: it's an optional field, in a JSON file that NEEDS to be editable at all times. If a distro decides to implement any serious age verification, it will have to store the data, namely the date of birth, somewhere. The /home folder would be wrong, as the user could edit that at all times. The userdb on the other hand can be restricted, meaning that the user can only edit it with user privileges. So if a government questions the seriousness of this verification method, distros can just claim that it is the administrative duty of the parent to prevent their children accessing things they shouldn't, and that the Linux kernel itself provides the proper tool to do it without constant supervision. Yet systemd cannot enforce any stricter rules because service users, especially root, are not real people and thus cannot have any age verification. The only solution would be to tie these accounts to a person. This would cause an outrage at companies, considering that this role would most likely be the CEO or CIO, and if that device is stolen their identity could be linked to a crime, and I doubt any police station would bother trying to retrieve that laptop.

So this change will most likely be the maximum systemd can do without breaking distros for corporations, while at the same time allow classic Linux users, who most likely give themselves admin rights, a way to render any verification null and void by editing this optional field on their own.

EDIT: Also, being mad at an organisation trying to meet the laws in order to be usable will solve nothing. As you said yourself: a strong stance is needed. So complaining about systemd and trying to make them revert it will do nothing, because there will always be someone who bends the knee. If you want to do something, organize or join a protest and go to the streets, show that the law is for the people, not to be used as an oppression tool.

[โ€“] Skankhunt420@sh.itjust.works 6 points 20 hours ago* (last edited 20 hours ago)

No no no, NOT "meeting the law" this has not been made law in USA yet which is the law they referenced when mentioning this merge.

You should read the thread in github.

A system76 developer said he's in talk with state representatives, that this might even be overturned, and that it might not even affect open source software at all and one of the systemd maintainers said and I quote:

"It is possible that California law will be changed. But similar ideas are popping up in other contexts and it's unlikely that they'll all go away. This implementation is fairly generic and useful for other things besides age verification, so we shouldn't decide whether to merge it or not based on a single law in any jurisdiction." -keszybz

That seems like bending the knee pretty fucking hard man.

What they have done is proven that they can bully and harass open source software into submission. They should have waited until FORCED to do something like this but it seems like they're beyond eager to lick anyone's boots USA or otherwise.

Linux distros are not US entities bound to US law the last I checked (of course you have your Redhats and etc. And I guess maybe their Fedora distro might fall under us jurdistiction since its developed by red hat but I'm not sure because of being open sourced licensed.

They've bent the knee before with banning Russian and I think Chinese Linux kernal maintainers before which was also fucking bullshit.

The USA shouldn't be able to swing its dick around and force the whole world into submission but boy it sure seems to get to every single year more and more and more.

And a lot of people here support it its so sad.

Anyway I'm getting off track with this but seriously no, they should have taken a stand not only for all of us but for Linux as a whole because systemd is a part of Linux as a whole.

If forced, I understand. This was not forced. This was suggested, merged welcomed and the thread locked as soon as any pushback happened.

Doesn't seem very open anymore to be honest.