this post was submitted on 16 Apr 2026
231 points (99.6% liked)

Linux

17374 readers
25 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
231
Oh No! Now A Federal Bill Wants OS-Level Age Verification for Everyone in the USA (itsfoss.com)
submitted 2 weeks ago* (last edited 2 weeks ago) by pglpm@lemmy.ca to c/linux@lemmy.world
48 comments fedilink hide all child comments
 

From the press release [my emphasis]:

Require operating system developers like Apple and Google to verify users’ ages when setting up a new device, rather than relying on self-reported ages.

cross-posted from: https://beehaw.org/post/25834609

The U.S. has been quietly building up a set of state-level laws that push operating system providers into the age verification plague.

California's AB 1043, signed in October 2025, requires OS providers to collect age data at account setup and pipe it to apps through a real-time API. It kicks in on January 1, 2027.

Colorado is working on something nearly identical. SB26-051 (which we covered when it was still a proposal) passed the state Senate 28-7 on March 3, 2026, and is now waiting on a House vote to become law there too.

However, these are just state-level laws. A new federal bill, H.R.8250, introduced on April 13, 2026, by Rep. Josh Gottheimer, with Rep. Elise M. Stefanik signing on as cosponsor, has us intrigued.

you are viewing a single comment's thread
view the rest of the comments
[–] pinball_wizard@lemmy.zip 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

There's literally no way they van enforce laws on an open source project

I'm guessing you weren't running a modded Minecraft server when CraftBukkit was hit with a DMCA ban and disappeared from GitHub overnight. (The DMCA is a shit law, passed by shit-heads to be shitty.)

Open Source is huge, but not invincible. We still have to act to protect it.

[–] quick_snail@feddit.nl 0 points 2 weeks ago (1 children)

So they moved to gitlab of codeberg or self hosted gitea?

What's your point? Git is decentralized. Getting banned from GitHub takes about 1 day to fix, at most.

[–] pinball_wizard@lemmy.zip 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

That's not how it played out. Contributors were alarmed, distribution modes had to be rebuilt. Some of those options fight exist yet.

Contributors were afraid to continue to contribute.

The ecosystem is more resilient today because of crap like that.

But it's vain to believe that public copies won't go away. People have to feel safe to share.

[–] quick_snail@feddit.nl 1 points 2 weeks ago

So self censorship is the problem. But there is no real threat to contributors