this post was submitted on 04 Apr 2026
14 points (100.0% liked)

technology

24317 readers
402 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 5 years ago
MODERATORS
context@hexbear.net
SexUnderSocialism@hexbear.net
gaycomputeruser@hexbear.net
Wakmrow@hexbear.net
SwitchyandWitchy@hexbear.net
14
Age verification on Systemd and Flatpak (cybrkyd.com)
submitted 1 day ago by git@hexbear.net to c/technology@hexbear.net
20 comments fedilink hide all child comments
top 20 comments
sorted by: hot top controversial new old
[–] invalidusernamelol@hexbear.net 8 points 1 day ago (5 children)

I didn't really get the panic on the systemd PR. It's literally just adding a "birthDate" field to the user record that behaves like any other field? If you're running your own system you can change your birthdate to whatever you want since you have access to sudo.

Maybe kinda make sense for people who want to give their kids accounts and have their access locked down? It's not like it's any different than those "enter your age" screens on Steam or whatever.

Also:

We're about to see millions of 126 year old Linux users lmao

[–] hello_hello@hexbear.net 4 points 19 hours ago (2 children)

Apparently the person who made that PR was doxxed and sent death threats, which only makes me empathize with systemd even more.

[–] Inui@hexbear.net 4 points 19 hours ago

Theyve posted in a Discord I'm in that they've gotten death threats, stuff sent to their house, endless phone calls and spam emails, people threatening their family members on social media. Everything you can think of outside of literally lighting their house on fire (so far).

I think their decision to voluntarily add this feature was poor and unnecessary (nobody asked or paid them to) but the reaction is disgusting.

[–] invalidusernamelol@hexbear.net 2 points 18 hours ago

That's insane... It's not like they added any sort of tracking code or any code that can cause anyone harm. They literally just added a date field to user accounts called "birthDate". People need to fucking relax.

[–] Liketearsinrain@lemmy.ml 5 points 20 hours ago

I think it has to do with the slippery slope. When fields like work phone were added they served actual uses at the time.

They may be functionally identical but this is happening under an increasingly more invasive surveillance system and people have hated systemd eating every linux component since forever. Now that it's a soft dependency on major desktop environments it just feels like a rug pull that they get to make these changes

[–] balsoft@lemmy.ml 1 points 16 hours ago

If you’re running your own system you can change your birthdate to whatever you want since you have access to sudo.

Best part is that you can just not set it at all and then literally nothing changes for you.

Other PRs from this developer which make useradd ask you for your birth date with no way to opt out... Yeah that's bad.

[–] chgxvjh@hexbear.net 2 points 20 hours ago (1 children)

It's just annoying and Lennart has also been very normal about the whole thing.

I don't think my distro even runs userdbd so it's kinda whatever.

[–] Liketearsinrain@lemmy.ml 2 points 20 hours ago (1 children)

It upsets me more that he's letting AI bros contribute to systemd than anything he did before. I think he even used one of the slop machines to review the PR.

[–] invalidusernamelol@hexbear.net 1 points 16 hours ago

That's a way bigger story. Open Source projects need at least a "you have to tell us if you used AI" policy. Even then slop reviews and slop PRs are a recipe for disaster.

Beyond the ethical, environmental, and legal issues, it just means you're more likely to get complacent. Most projects have some sort of BDFL that guides the overall vision, and if that gets co-opted by a system designed to trick people into thinking it's smart you're fucked.

[–] BabyTurtles@hexbear.net 4 points 1 day ago (4 children)

It's reasonable to assume the next legal step is to outlaw lying about your age. IP logs associated with an age of 126 would be easy targets. You could lie about your age with something more realistic, but then it's another avenue of device fingerprinting.

A better thing to do would run a script that edits your age every boot, randomly between 25 and 65, along with an always-on vpn that keeps switching locations.

Or just switch to a distro without systemd, like KaOS. That's probably the direction I'll head next.

[–] milk@discuss.tchncs.de 2 points 15 hours ago (2 children)

If lying about your age is illegal then not verifying your age at all is probably also illegal. You probably wouldn't be able to access any commercial, online software or websites using an unverified distro

[–] BabyTurtles@hexbear.net 3 points 14 hours ago

You probably wouldn't be able to access any commercial, online software or websites using an unverified distro

This would be a significantly better problem to deal with than having the OS compromised in the first place.

[–] invalidusernamelol@hexbear.net 2 points 13 hours ago

Again, that's outside the control of systemd. If they need to provide an interface, they need to provide an interface. If you don't want to use that interface you don't have to, but I'd rather have that commercial stuff pinging a known open API than doing something sketchy internally.

[–] chgxvjh@hexbear.net 5 points 20 hours ago* (last edited 20 hours ago) (1 children)

The push is towards identity attestation with digital signatures issued by authorities. Of course that's still quite the technological leap from having an dob field in a user database, but that's just a part of what's required by the Californian legislation. The NY legislation already tried to include identity providers. And EU countries already have the IDs, the EU is just not in a strong position to require OSes to implement uniform support.

EU has been trying to push for government identities on social media for like 15 years.

[–] TheTaglineToldMeTo@hexbear.net 2 points 12 hours ago* (last edited 12 hours ago)

Of course that's still quite the technological leap

Yeah I highly doubt this specifically will be any meaningful change or particularly the coming avenue for change, but I don't necessarily think that's fully it, because it has always been just as technologically feasible DRM currently is ("Secure"/"Trusted^(treacherous)^" Computing, TrustZone, TEE(s), Secure Element(s), ME, TPM, SGX, TDX et al..) all designed trusting the manufacturer first then the user second if even at all, all widely used(or capable) almost without exception today. I just don't think the appetite or need has gotten truly there yet. but with with how suffocatingly American core internet infrastructure and historicaly entrenched design elements are, when truly threatened i can see the dropping of the "open" internet facade becoming much much much worse that won't be as solvable as just some configs or applying some patches. ignoring the liberal dogs with unimaginable cognitive dissonance and white hubris that somehow imagine building around the exact same panopticon but painted blue with stars, and "European"^(whatever\ this\ is)^ will somehow be spectacularly different. i can't tell if my thinking is just borderline conspiratorial, but there is wayyy to much undeserved trust in this stuff that just because it hasn't been weaponized more overtly yet doesn't mean in more desperate scenarios/stronger positions it wont or cant be.

  • (I agree with you I'm just talking into the aether getting carried away typing saying the same thing but worse and convoluted. I need some sleep :( )

  • (removed my doomer disjointed rambling about actually important and real security being wrapped into "trusted" computing. truly free computing died soon after it was born; it is possible, but only in a better world. the last time I smiled was on August 19th, 1991. etc...)-

[–] reader@hexbear.net 3 points 21 hours ago (1 children)

It's reasonable to assume the next legal step is to outlaw lying about your age. IP logs associated with an age of 126 would be easy targets.

Its really not reasonable to assume either of those things. If shit like this really takes off it'll be less like the linked discussions and more like DRM, with proprietary software (and hardware, if they want it to stick), linked to an online service that "verifies" your age externally.

[–] BabyTurtles@hexbear.net 3 points 17 hours ago

I think you're offering way too much good faith to a government that believes in prisonlabormaxxing and genocidemaxxing.

[–] invalidusernamelol@hexbear.net 1 points 1 day ago (1 children)

Avoiding systemd is getting harder and harder though. Some sort of script or plugin would probably be best.

[–] BabyTurtles@hexbear.net 2 points 17 hours ago (1 children)

Avoiding systemd is getting harder and harder though.

That's exactly why it should be avoided. The vision of the FOSS operating system was that parts were interchangeable, and you aren't locked into any one thing.

People raised the alarm bells on systemd years ago and unfortunately it seems they were correct all along.

[–] invalidusernamelol@hexbear.net 1 points 16 hours ago* (last edited 16 hours ago)

Eh. I'm not really on the systemd hate train that a lot of people are. I think having a unified interface is good actually. Plus it's modular enough that you can absolutely add/remove components in your distro.

I also really don't think that this is a sign that they were correct, the whole point of my comment was to point out how ridiculously small this change is and it has no visible path towards becoming anything more.

systemd's whole thing is being the glue, so it makes sense for them to expand their API when changes are being proposed. Doing that ahead of time saves them headache later since people will splinter into other workarounds.

If the "age verification" stuff ends up centralizing on a systemd module, that's good actually since it means you're less likely to see people implementing it themselves in ways that are harder to see or disable.

If all of that flows through systemd, you can just turn it off on the API layer and anyone who uses it (which at this point, will probably be a lot of people since they're ahead of the game) hands off that control to a thing you as a sysadmin have easy control over.