this post was submitted on 22 Mar 2026
198 points (72.9% liked)

linuxmemes

30723 readers
1282 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] peacefulpixel@lemmy.world 25 points 22 hours ago (1 children)

    source? i mean you went through the effort to post a meme about it at least include the relevant information

    [–] brucethemoose@lemmy.world 10 points 21 hours ago* (last edited 21 hours ago) (3 children)

    The source is the source: https://github.com/systemd/systemd/commit/acb6624fa19ddd68f9433fb0838db119fe18c3ed

    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.

    [–] Deceptichum@quokk.au 7 points 19 hours ago* (last edited 19 hours ago) (1 children)

    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

    [–] CosmoNova@lemmy.world 7 points 20 hours ago (1 children)

    earliest representable year is 1900

    (Time to set it to) literally 1984!

    [–] irish_link@lemmy.world 0 points 21 hours ago (1 children)

    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.

    [–] greencoil@lemmy.frozeninferno.xyz 18 points 20 hours ago (3 children)

    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.

    [–] caseyweederman@lemmy.ca 10 points 19 hours ago* (last edited 7 hours ago) (1 children)

    "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

    Edit: source, two weeks ago, the pull request conversation: https://github.com/systemd/systemd/pull/40954#issuecomment-4032221990

    [–] Telemachus93@slrpnk.net 1 points 13 hours ago (1 children)

    That's the question: would they fight it? From all I've seen so far, they wouldn't.

    [–] caseyweederman@lemmy.ca 1 points 7 hours ago* (last edited 7 hours ago) (1 children)

    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 compliance.
    https://github.com/systemd/systemd/pull/40954#issuecomment-4032221990

    [–] Telemachus93@slrpnk.net 2 points 5 hours ago

    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).

    [–] NotSteve_@piefed.ca -3 points 18 hours ago (1 children)

    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.

    [–] possiblylinux127@lemmy.zip -3 points 20 hours ago (2 children)

    It is just a optional field

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

    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.

    [–] NutinButNet@hilariouschaos.com 2 points 19 hours ago

    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.