this post was submitted on 24 Mar 2026
43 points (93.9% liked)

Linux

16765 readers
288 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
43
Birthdate field under discussion also in Arch Linux (github.com)
submitted 1 day ago* (last edited 1 day ago) by pglpm@lemmy.ca to c/linux@lemmy.world
7 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ca/post/62271746

Add a required birth date prompt (YYYY-MM-DD) to the user creation flow, stored as a systemd userdb JSON drop-in at /etc/userdb/.user on the target system.

Motivation

Recent age verification laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc. require platforms to verify user age. Collecting birth date at install time ensures Arch Linux is compliant with these regulations.

This is just a pull request, no changes yet.

The pull-request discussion thread has been locked, just like it happened for the similar thread in Systemd, owing to the amount of negative comments...

top 7 comments
sorted by: hot top controversial new old
[–] traxex@lemmy.dbzer0.com 3 points 1 hour ago

So excited for the new rectal scanners being added to all of the IoT bidets everywhere.

[–] Oinks@lemmy.blahaj.zone 3 points 6 hours ago

I appreciate the work ahead of time, and the law is the law. @svartkanin raised this PR internally within staff channels, and the feedback is that we'll wait until there's an overall stance from Arch Linux on this before merging this, and preferably involve legal representatives on this matter on what the best way forward is for us.

But from a personal reflection it's clear that there's a disconnect between law makers intent and how things like this will be implemented in reality, and once a law is in place - we might have to implement inconvenient things..

So I'll leave this open for now, but I'll also lock the conversation because experience from the mailing lists on this topic has told us this thread will get out of hand quickly.

@dylanmtaylor: this stance does not mean that we won't merge this. And despite locking this thread, I think you, me and other contributors and maintainers can still comment (which is fine, and good).

Sounds reasonable to me

[–] Skankhunt420@sh.itjust.works 18 points 20 hours ago (1 children)

Why the fuck is it the same bootlicker in both of them?

Seriously, absolutely fuck this guy.

[–] StealthLizardDrop@piefed.social 15 points 20 hours ago

Its very likely to not even be a real person, just another bot shilling for corpos

[–] xyro@morbier.foo 16 points 1 day ago

On the systemd discussion : "Don't worry bro, it's not a mandatory field" 😂

[–] corsicanguppy@lemmy.ca 2 points 19 hours ago

The only solution is a pivot: the component needs to be dead to us now; and forever, too, as they'll erode privacy and leak p-i-i at the drop of a hat.

[–] Luminous5481@anarchist.nexus 6 points 1 day ago

Oh shit, here we go again 😂