Fork time? Maybe all the anti-systemd zealots were right all along…
Edit: To address whether it is likely that this change will affect users: Gnome is planning a stronger dependence on userdb, the part of systemd where this change is being implemented. https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/
how do you think this can be most effectively fought?
🤷
In a few years, we may be smuggling in contraband Chinese RISC-V computers.
Huh, we really do live in a cyberpunk novel…
Email your legislators telling them that parents already have access to network block tools, these laws won’t stop the problem anyway (run through a vpn), they’re a free speech nightmare, they’re collecting more data on American citizens when America has data breaches losing data every few days, and Congress literally studied this twenty years ago and decided it wasn’t a good idea then, what makes it a good idea now?
uh…$? same reason the majority of US politicians vote anyway on anything put in front of them.
the only thing sacred in the USA is $
I’ll never buy a computer that can’t be run without this shit. If that means I run what I have until it breaks and then never have a PC again then that’s what I’ll do
The last computer I bought (a couple of years back) was a decade old PC, the price was €10 or so. I needed to add RAM, SSD, and used it for a couple of years as a Fedora Workstation desktop. It was plenty powerful for most of my needs. I’m not too worried about it. I think I can survive on a machine like that.
What if users are redefined as context? Now the is does not have users anymore. That’s not a ‘root’ user, it’s a ‘root’ context. And that’s non root context with supercontext privileges
Unless first worlders get out of their comfort zone and fight back, nothing can be done.
so much for making our own tech!
By implementing it all in the most brain dead, user space writable fashion
DRM writers love this too.
In my opinion, storing a date is pretty much irrelevant unless there’s a process that validates the supplied date, otherwise every Linux user was born on 1/1/1, if not, an administrator can “fix” that
Furthermore, that
systemdthinks that it’s the place to store such information is in my opinion beyond absurd.Who appointed that project the source of age truth in the Linux ecosystem? What discussion was there, who was consulted and where was the vote?
Exactly. This is a massive overreach, and it is crazy that Poettering is even considering merging this.
I would say the majority of objections to systemd pertain to perceived overreaches of the project (perceptions I generally share). So in that sense, it is kind of on brand.
it is crazy that Poettering is even considering merging this
You’ve, uh, seen systemd, right? Cmon; this is just one more section for the cancer to eat.
and it is crazy that Poettering is even considering merging this.
Not familiar with him then?
He thinks that systemd is desktop linux.
1/1/1
every linux user is jesus confirmed
This change is mostly in the userdb code which is a sub-component of systemd that stores user records. It isn’t in the PID1 process. But I could see an argument for having it be part of the desktop environment in GNOME or something like that instead.
They haven’t fessed up yet that that’s part of their plan. I expect to hear from them after they’ve passed the first half.
You’re right that asking a user for a date is next to useless. However, that isn’t a reason to not fight this stuff. Asking the user for the date is step one to getting people accept it. After that they’ll point out that people were lying, and they’ll need our government ID to verify (and link us to activity). It’s all a step towards a surveillance network tracking every move you make on your computer.
Come on, you know it’s going to be 1/1/1970 most of the time.
I was ambivalent about systemd up until now. If this gets merged I’m moving to a non-systemd distro. I do not live in California or even the USA. I do not want age verification garbage in my OS.
Iv not given a shit one way or another as well. But as a Californian I refuse to have this shit on my PC damn be what the law says.
Consider PCLinuxOS: they’re an RPM-based mandriva (mandrake/conectiva) derivative with really great and wide compatibility in stacks without the ‘modules’ shitfest RH started after no one remembered what ‘alternatives’ was for.
They don’t use systemd, but their installation is a bit shite as it’s a “live CD” installer – they pruned out the proper templatey install that mandriva has. But so far that’s the biggest issue. If they can get off networkManager we’ll be even better off, though.
You mean they’re complying with Meta’s age verification at OS level lobbying?
https://github.com/upper-up/meta-lobbying-and-other-findings
Something feels fishy… The user who made this pull request has more than doubled his contributions to various repositories since January (from 20–400 to more than 1100), and this is his first pull request in the systemd repo.
echo "18+" > ~/.age_rcAm I compliant with California’s law now? Apps can use the POSIX API to access my age.
Yes, and you can do the same thing to your child’s non-root account. The point of the California law is to allow admins (parents) to do that.
Yes and that’s fine and everyone freaking out is being dumb.
There are fascist governments demanding genital inspection for playing highschool sports and they’re losing their shit over an accounts API returning an unverified age bracket!
There are fascist governments demanding genital inspection for playing highschool sports
- That is already going on in the very same country we’re discussing.
- “Things could be even worse, so until things are just as bad as that, don’t complain or try to stop it from getting worse.”
If you yell that the everything is on fire, over an API that doesn’t do verification, it’s less effective when you yell the same thing over real issues.
That’s a poor analogy, because nobody is lying, saying things are on fire that aren’t.
We weren’t born yesterday—or at least I wasn’t. We know where this is going, and it’s folly to wait until almost the end before pushing back.
@skyline2@lemmy.dbzer0.com @linux@lemmy.ml
Brazilian here. I’m neither a lawyer nor a specialist, just someone who has read the Portuguese text from the Brazilian flavor of the ongoing worldwide age check set of laws.
I must note that the Brazilian age check law (Lei 15.211/2025) specifies “vedada a autodeclaração” (English: “self-declaring is forbidden”). This means that this kind of implementation, where age or birthday is an user input, wouldn’t be compliant to Lei 15.211/2025, because it requires the age information to be assessed independently from the user whose age is being assessed. This means face biometrics, government-issued ID (in our case, CPF, CNH, Passaporte and similar) or “behaviorial analysis”… Anything but a “yes I’m 18” or “I was born in day month year”, for those are self-declared and the Law says it’s “not enough”.
Someone should warn the systemd maintainers of this “Brazilian jabuticaba”.
(Cross posting this reply of mine because the post was cross posted to two different Lemmy instances)
I believe this only stores that information. It’s not a system of declaring an age
They want to store the actual birthdays (not just a boolean stating it complies with an age bracket). And using claude to review PRs… fucking systemd
The answer to the PII issues is hence not restrictions in userdb, the answer is proper app sandboxing. And that even already exists in flatpak! It restricts access to $HOME already, and to userdb too! And that’s the way to do it!
I don’t use flatpak. I don’t like it. Linux is about choice and I choose not to use that.
Hence, just embrace app sandboxing! And if you come to me and say “hey, I run all my apps without sandboxing, but i want the birthday hidden anyway” then I can only say, your model is really really broken. Fix your security model first, then come back.
In the words of the great Linus Torvalds, go fuck yourself.
what a fucking bootlicker
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.
https://github.com/systemd/systemd/pull/40954#issuecomment-4032355482
Ofcourse the project run by a microslop employee wants to force this on almost every distro as soon as possible.
same thing with manifest v3, just some mega corp goon doing the work no one’s asked for
Poettering is not with Microsoft anymore, though
- get top recent commiters with https://github.com/systemd/systemd/pulse
- click on 1st link https://github.com/bluca and see https://github.com/microsoft in profile
Just 2 steps.
Yes Poettering isn’t at Microsoft but seems the person driving the project at the moment is.
Meta’s lobbies reach really everywhere these days.
This is the first time I’ve cared about the whole systemd debate, so that’s something I guess. Not interested in anything that kowtows to this age verification nonsense
Damn that’s crazy. It’d be a shame if someone not beholden to California law just forked the code
