Linux

17573 readers

46 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:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 2 years ago

MODERATORS

MigratingtoLemmy@lemmy.world

421

How Linux developers defeated the new OS age-verification laws (blazetrends.com)

submitted 1 week ago by Lisk91@sh.itjust.works to c/linux@lemmy.world

60 comments fedilink hide all child comments

The coordinated effort worked. When lawmakers finalized Colorado SB26-051, they added Section 6-30-105(e) to the text. This specific clause waives compliance for operating systems and applications distributed under licenses that allow copying, modifying, and redistributing without platform-imposed technical restrictions. Why the Section 6-30-105(e) Exemption Protects Decentralized Tech

This exemption establishes a formal legislative precedent for the tech industry. It legally shields free and open-source operating systems from hardware-level age attestation laws that closed ecosystems like iOS and Windows will soon have to follow.

(page 2) 11 comments

sorted by: hot top controversial new old

[–] Onomatopoeia@lemmy.cafe 1 points 1 week ago* (last edited 1 week ago)

Seems to me the only reason they included this was because there's no way to enforce it on OSS that you can compile yourself.

Not because they saw it was wrong, for any OS.

I expect clearly documented ways to disable this in Windows in 3....2...1...

load more comments