this post was submitted on 22 Mar 2026
344 points (95.3% liked)

Linux

13019 readers
717 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 

The latest changes implemented in the Systemd repo, related to or prompted by age-verification laws, have made many people unhappy (I suppose links about this aren't necessary). This has led to a surge in Systemd forks during the last days ("surge" because there have always been plenty of forks). Here are some forks that explicitly mention those changes as their reason for forking (rough time ordering taken from the fork page):

Hopefully the energy of this reaction won't be scattered among too many alternatives, although some amount of scattering is always good.

top 50 comments
sorted by: hot top controversial new old
[–] mrbigmouth502@piefed.zip 17 points 6 days ago (1 children)

This is one of the beautiful things about open source. If the original devs do something stupid, the community can fork.

[–] pglpm@lemmy.ca 8 points 6 days ago
[–] drmoose@lemmy.world 8 points 6 days ago (3 children)

Out of the loop:

The systemd project merged a pull request adding a new birthDate field to the JSON user records managed by userdb, in response to age verification laws in California, Colorado, and Brazil.

Lennart Poettering clarified that this is an optional field in the userdb JSON object — not a policy engine, not an API for apps. It just defines the field so it's standardized if people want to store the date there, but it's entirely optional. Systemd itself does nothing with the data.

What a nothing burger

[–] rumba@lemmy.zip 23 points 6 days ago (17 children)

It's not nothing, freedom is often taken by inches.

load more comments (17 replies)
[–] Blue_Morpho@lemmy.world 9 points 6 days ago

In response to German purity laws, IBM has added an optional field to their citizen database. It just defines a field "Is Jewish" so it's standardized, but entirely optional. IBM does nothing with the data.

What a nothing burger.

load more comments (1 replies)
[–] AeonFelis@lemmy.world 7 points 6 days ago (3 children)
[–] Digit@lemmy.wtf 3 points 5 days ago

Yes. Because Rust solves all things, just like that.

load more comments (2 replies)
[–] Mikina@programming.dev 4 points 6 days ago (1 children)

I'm mostly interested in how will they handle giving the info to apps. If it'd let me to block or fake the request depending on what I currently need (just prompt me every time an app asks, and let me choose the bracket), I'm good.

Tbh, most sites that are slowly getting targeted by age verification laws are things I'm kind of addicted to and have been trying to drop for a long time. A "scan your face or id" dialog would be a good reminder to finally cold turkey it. It's one of the things I hate more than however much I need their platforms.

[–] Tinidril@midwest.social 3 points 6 days ago* (last edited 6 days ago)

If you have root access to the system, then you can enter any date you wish. That's not exactly a per-app or per-request prompt, but there is nothing preventing you from using whatever date you want. The only situation where this is going to matter is when an adult manages a computer for a minor and wants them to be age restricted.

I get the "boiling a frog" arguments against this. It does feel like a first step towards gating the Internet behind government ID. However, if this were to forever be the way things work, I don't see a problem.

I'm also not sure how resistance from the Linux community on this law will do anything to prevent future authoritarian overreach. It could do more to keep us marginalized, which will make us even less capable of standing up to the next phase.

[–] Digit@lemmy.wtf 2 points 6 days ago (1 children)

And it appeared to me at a glance that many pre-existing systemd forks came out of dormancy and updated after that merger too, to apply the regression. Far more than just 11.

load more comments (1 replies)
load more comments
view more: next ›