You guys fell for clickbait

https://lemmy.zip/post/61219686

I don’t even know where this rumour came from.
It’s not a rumor, systemd merged a PR that explicitly said it was to allow handling the new age verification laws. Just because they aren’t actually verifying anything doesn’t mean that they didn’t merge code in direct support of the laws. And why in the world would this even be handled at systemd level anyway?

Ideally, we wouldn’t need to do age verification at all. But if it’s absolutely required, the most privacy-preserving way would be:

  • System administrator verifies the birthdate of the user, stores it on the user account
  • Applications can then ask, “is the current user over 18?” And just gets true/false.
  • But if it’s absolutely required

    It’s not.

    Applications can then ask, “is the current user over 18?” And just gets true/false.

    the current implementation allows reading the precise age

    Exactly, and some of the laws require just asking if the age is over a some pre-defined threshold, not sending the full date, for example “is the user over 18? Is the user over 15? 13?”

    And just to be clear, I do think that “protecting the children” is just an excuse to push surveillance tech that was very convenient to use after the Epstein files. I am strongly against these laws and I am supporting ($$$) activist groups fighting against them. Do consider donating or getting involved too if you can.

    But this specific change isn’t adding surveillance to Linux. It’s just a date of birth field that a parent can set. I can see why a parent would want it instead of using shady and intrusive “child control” software that takes over the computer.

    You need to store the date of birth to update the user’s reported age automatically. It makes sense and puts the “protecting the children” responsibility back on parents instead of third parties that every website is now starting to use.

    The systemd solution is not even reusable for actual verification because it can’t provide any cryptographic proof of the verification! It’s literally just a date.

    All of this was discussed in the PR.

    Systemd is present on the vast majority of Linix systems so it made the most sense to put it in systemd. It is an optional field so it is up to applications and distros on weither to use it for something. Age verification laws are legally binding so compliance is not optional.

    If you have a problem with age verification call your local lawmaker. Don’t attack a bunch of devs who somehow got stuck in the middle.

    Well, how do I put it… compliance is optional
    Because most people apparently don’t know the difference between a system manager and an operating system.
    source? i mean you went through the effort to post a meme about it at least include the relevant information

    The source is the source: github.com/…/acb6624fa19ddd68f9433fb0838db119fe18…

    Takes a birth date for the user in ISO 8601 calendar date format. The earliest representable year is 1900. If an empty string is passed the birth date is reset to unset.

    That’s it. That’s all it does.

    Whatever was discussed in the PR, the code does precisely nothing to implement any kind of verification. It’s just an optional birth date field, like tons of electronics have had forever.

    userdb: add birthDate field to JSON user records (#40954) · systemd/systemd@acb6624

    Add an optional field that can be used to store a user's birth date. userdb already stores personal metadata (`emailAddress`, `realName`, `location`) so `birthDate` is a natural fit.

    GitHub
    I don’t think anyone who read even the first paragraph of the article (at least the one i read) would say they are doing verification. They are simply adding a field for data to be housed if anyone wants to opt in. Instead of putting it in 20 different spots/apps it’s in one place that any third party can reference.

    it’s in one place that any third party can reference.

    But why would I want that?

    Even if you ignore the whole “this doesn’t verify anything” discussion, why would I want to give third parties easy access to personal and potentially sensitive information? I personally am not interested in simplifying data collection for corporate entities who definitely do not give a shit about the safety of my personal data, let alone hypothetical children. I do not know why this data collection needs or would be desired to be implemented within systemd, besides being a direct response to age verification laws saying its an OS providers responsibility to collect it. Arbitrary data collection by private entities is not “useful”. My personal data has no business being referenced by random asshats that ask for it. There are so few things in the world that “justify” needing my age that I would suggest it would be easier to make my birth date a permanent data point on my PC. Same goes for the other personal details that systemd already supports. Crazy to imagine anyone actually using those on a personal machine.

    It is just a optional field

    Be mad at lawmakers not developers who are trying to make the best of a shitty situation

    I speak only for myself, but I’m not mad at any developers for following with this. I wish they wouldn’t, but I can’t blame them for following the law to protect themselves.

    I still think this is bullshit and just going down the slippery slope. The next thing is “this value doesn’t do anything. Now we need a law that actually checks an ID!” And it just keeps getting worse and worse.

    Don’t give them an inch on any of this bullshit. And by them, I do mean the governments trying these stupid laws that, at best, waste taxpayer money and valuable time spent on other worthwhile things.

    It was also an option to not make a useless field. Not like this self reported dob is going to cut it for the existing age verification laws as is exists now. But I can be mad at people in a position of community production for not having a spine, too.

    How is this supposed to be making the best of the situation anyway? It accomplished nothing but piss off the community and signify to authoritarians that open source developers are ready to bend over for them. Simply threaten unenforceable fines across the world and suddenly everything is hopeless. Better get ready to comply, its inevitable! Its pathetic. Ageless Linux might be performative bs, but at least its critical of this over reach instead of intentionally signalling compliance in advance.

    “While our lawyers are fighting it in court, we decided to whip up the barest minimum viable proof of concept so that if it does come to pass, at least it’ll be on our terms, and not a rushed piece of easily-exploitable garbage pushed out at the last second” the systemd team, probably
    That’s the question: would they fight it? From all I’ve seen so far, they wouldn’t.

    I’m Jeremy from System76. We are in talks with legislators and there are likely to be amendments to the age verification bills, as well as conflicting requirements in different jurisdictions. It may even be the case that open source operating systems are exempted entirely. I detailed this on the xdg mailing list here:

    https://lists.freedesktop.org/archives/xdg/2026-March/014797.html

    I have other concerns about this specific implementation. By relying on systemd, which is decidedly unportable to non-Linux operating systems, and not used across all Linux operating systems either, it will force at least one alternative implementation to exist. If these implementations end up having to collect jurisdiction specific requirements, that makes it much harder for complihttps://github.com/systemd/systemd/pull/40954#issuecomment-4032221990

    On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states

    Yeah, I’ve read that discussion a few days ago. That specific post seemed reasonable, but that was a comment from outside the core systemd team, wasn’t it? As far as I understood all of this, different people took the decision to merge, without coordinating their efforts with those of the corporate linux distros (Pop!, Ubuntu, Red Hat/Fedora, (Open)SUSE).
    Its a nullable field, chill. It’s exactly the same as a Linux distro installer asking for your first name for account setup and the moral outrage is genuinely embarrassing

    Good system design doesn’t do things without me asking it to. I’ll gladly manually re enter my birth date for an external service if its required, which to be clear, should be as close to 0 times as possible. What, should I keep all my job application info in the initialization system too? Because a website I’m on might ask for it at some point? Don’t want to be too redundant.

    Literally this field serves no purpose other than to build compliance with the surveillance state. No end user asked for this. Like I said, can’t imagine any end user making use of the existing systemd fields either. But those also didn’t get any attention because they weren’t made as a reaction to threats by a malicious regime.

    earliest representable year is 1900

    (Time to set it to) literally 1984!

    You can if you want

    You also could just ignoro it entirely as it is optional

    So they’re introducing a system where a users age can be verified?

    Hmm, if only there was a name for that.

    Stores the user’s birth date for age verification, as required by recent laws\

    in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.

    https://github.com/systemd/systemd/pull/40954

    Guess

    userdb: add birthDate field to JSON user records by dylanmtaylor · Pull Request #40954 · systemd/systemd

    Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc. The xdg-desktop-portal project is addi...

    GitHub

    So they’re introducing a system where a users age can be verified?

    No. They are not.

    It is an optional field that does no semblance of checking its veracity. Again, like basically every bit of electronics has had forever.

    It is literally for the act of verifying a users age.

    Being the verifier instead of the requester doesn’t make it not age verification. It’s part and parcel.

    I just don’t see how it’s any different than my Sony PSP having an optional birthday field. Or oldschool forums having one. It can’t possibly affect me, or anyone who’s concerned about it.

    If systemd starts talking about bundling face scanners or whatever they actually need to verify someone’s age, and then tons of linux systems start requiring it, then I will be gravely concerned.

    it’s optional now but can be mandatory later? It literally takes a baby monkey’s brain to understand that.

    Also this is literally in the PR:

    Stores the user’s birth date for AGE VERIFICATION, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.

    userdb: add birthDate field to JSON user records by dylanmtaylor · Pull Request #40954 · systemd/systemd

    Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc. The xdg-desktop-portal project is addi...

    GitHub
    ah yeah because all of our digital clocks, smartphones, microwaves, washing machines, TVs, and… what else stores user age in a standardized manner? oh, you say none of these and no other things either?

    Couldn’t reply to me pointing out that this was merged, and was stated to be explicitly to support age verification laws, so you had to lie about it as a meme instead.

    Because thats what youre doing right now, lying and spreading misinformation. You can admit it.

    The birth date field that was added can be used by age verification processes, but it’s not age verification itself.

    It was added specifically for the purpose of two state laws and Brazil.

    Trying to weasel it as “this doesnt implement it” is misinformation at best.

    Okay.
    How does it verify?

    sigh

    How do these laws do anything to “protect children”? And since they dont actually do that, which you may already be aware of, what do you think their purpose is?

    Then ask that question to yourself and think about whether the verification of an age is the issue with what’s going on here, and why people are angry with systemd maintainers merging something that houses PII, for no other stated reason or potential use case than a law that will have zero ability to “protect children”.

    Then ask that question to yourself and think about whether the verification of an age is the issue with what’s going on here

    Verification is the issue. Or, rather, it would be if there was any verification here at all.

    I could put 1970-01-01 in that field no problem. Systemd has asked for precisely 0 additional information from any of its users, because it neither asks you to fill it in nor verifies that what you filled it with is correct. Just like the real name and location fields that were already present, which, might I remind you, are also PII.

    Systemd isn’t the problem here. The laws are a problem and pissing in systemd’s direction won’t change that.

    Okay
    Look at the pull request
    Tell me how it verifies anything. It’s a field.
    I’m not arguing about the politics. The law is laughably inept at best and horrifyingly insidious at worst (and the truth is likely both at the same time).
    But again, read the change, read the comments, tell me what verification is happening.
    Age verification could be a usecase. The PR in question just adds a optional date field labeled birth date. If you are mad about age verification (as you should be) feel free to direct your rage elsewhere.

    Age verification could be a usecase.

    ITS THE EXPRESS PURPOSE AS WRITTEN IN THE PR.

    I will absolutely direct my anger and frustration where it belongs, which includes systemd along with the dumbasses pushing these laws.

    As well as you for spreading misinformation. Make no mistake, its deserved.

    It enables other dead brained dev to push it further

    Little by little

    It is just a arbitrary field. They could have a field for all sorts of questionable things and it wouldn’t bother me.

    It is up to the people outside of systemd on how it gets used. Systemd is non political and will implement whatever features have a use case. They don’t control the distro.

    Technology is inherently political.

    This is something that has been known and taught for decades.

    Learning towards bad faith pedant here.

    you don’t know what inherent means, apparenty.

    That’s actually an interesting question…is grass political ?

    By touching it, would we be signalling some sort of political stance ?

    Something to ponder.

    hi. slrpnk.net user here. yes. grass is political. when you mow your grass is determined by social contracts, the kind of grass you grow is reflective of the economic pressures you experience. when a city makes a green area, they must engage with politics on how to determine where and what the green area will be.

    since the dawn of civilization, aka growing grass for food purposes, grass growing has been both political in its decision making, as well as a driving force in politics.

    everything is political, and calling people who think that chronically online is goofy

    github.com/systemd/systemd/pull/40954

    They don’t control the distro.

    And google doesn’t officially control web standards, but their monopoly on browser usage means they have “effective” control, for the most part at least.

    See the manifest v3 changes for extensions.

    userdb: add birthDate field to JSON user records by dylanmtaylor · Pull Request #40954 · systemd/systemd

    Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc. The xdg-desktop-portal project is addi...

    GitHub
    Its step one of falling in line like a good little fascist puppet.
    Can’t tell if you’re a bad faith pedant or just indescribably naive.

    Storing a users birthday is useful metadata anyway. I’m surprised it wasn’t stored before.

    The age isn’t verified is any way. You can set it to the 1800s for all it cares

    This is not very 01 Jan 1970 00:00:00 of you.
    How does one enter an older DOB without causing an underflow?
    Implement it as a s64 instead of a u64. Ugh, honestly. Back when it was a 32 bit integer it made sense to make it unsigned because we’d have run out of numbers by now otherwise. But as of the advent of 64 bit unix time values there’s really no reason not to implement it as a signed value smh
    It is stored as a json date string
    That was a Unix Epoch joke
    Bug

    xkcd
    Wrong. The earliest date you can set it id 1900!!! 😠

    Yeah like the email address and the full name of the user.

    … What do you mean it’s blank for 99% of users?

    Email address and name are actually useful for network environments of a system admin needs to know who is the user behind a process or something. How old the user is is complete useless.
    Unless your system is for you and your kid, for example

    And how is it useful then? Parental controls have existed for decades and you never had to give your age to Facebook, who is the main proponent of these laws in the US and has poured millions of dollars into their creation.

    This isn’t about protecting kids. It’s about adding an additional fingerprint companies and governments can use to track and identify you and what you do with your system.

    Providing a place to store and read data for minimal, nominal, non-invasive compliance with legislation so that people can protect themselves without harming anyone else

    Things I have never said anything about:

    • Facebook
    • Giving your age to anyone
    • Laws in the US
    • Protecting kids
    • Fingerprinting