LmCast :: Stay tuned in

Colorado and California Exempt Open Source from Age Attestation

Recorded: May 27, 2026, 12:03 a.m.

Original Summarized

Colorado and California Exempt Open Source from Age Attestation - System76 Blog

Computers Engineered to Unleash Your Potential

laptops

desktops

mini

servers

keyboards

components

pop!_os
All Blog Posts
Blog Posts

Founder

Pop!_OS

COSMIC DE

Tuesday, May 26, 2026

Colorado and California Exempt Open Source from Age Attestation
Open source need not applyOpen source values are just different. Our operating systems and apps don’t collect personal information, profile children, inject targeted ads, or create addictive design patterns. The kinds of behaviors these children’s safety laws regulate are antithetical to open source values. For software that does not engage in these behaviors, mandatory age attestation creates privacy costs without corresponding safety benefits.We’re naturally resistant to this kind of activity. If an open source project attempted these behaviors, it would be relegated to the heap of random software rotting on the internet. Or forked without those properties. systemd, a common init+more system recently added a birthdate field to users accounts. That’s okay. We simply ignore the field. We don’t want to know the user's birthday because a username and birthday could identify an individual. Personal privacy is central to our philosophy.The processThe nature of open source is not well understood by many of our representatives, or many people for that matter. Don’t be too surprised. For most of the world, modern technology means seeing an ad for something they were just talking about with their friends. It’s creepy and feels invasive. It’s up to us to articulate how open source differs from that experience. And that’s what we did.In Colorado, we had the opportunity to meet with our representatives along with other members of the local open source community. Our concerns were heard and shared by our reps. A collaborative process followed where every participant exchanged suggestions and language to protect privacy while exempting open source software, code repositories, and container registries. Constructive engagement got results.I had helpBrainstorming discussions internally at System76 and with folks in the community and Red Hat helped identify potential improvements to the legislation. We found holes in proposed language and explored issues that could arise. We drafted and exchanged numerous changes and played devil’s advocate, understanding that we will have to defend language we propose to our representatives and perhaps in committee hearings.We also coordinated with community members and lobbyists in California, exchanging notes and language that ultimately made it into the California legislation.Our strategy was to establish an example in Colorado that could influence amendments in California. While I’m a bit in shock, it worked. The goal was to set an open source exemption standard in Colorado and California that other legislatures could adopt. But for that to succeed, California had to be on board.On the meritsAge attestation, and in some locations full age verification, is the current legislative soup du jour. It’s spreading not only throughout the United States, but throughout the world, from Australia to Brazil to Europe. There’s more work to be done.I’m sharing this story because I see the cynicism. I understand it too. If we can move beyond cynicism and talk about the merit of open source, we can make a difference for the open source community.iOS and Android have distorted the view of computing into platforms for consuming apps. We must illustrate the contrast with the world we live in: a world of computing centered on creation, where people build and share free software, collaborate openly, and drive innovation that ultimately benefits everyone.Write your legislatures with constructive, educational feedback. Engage as deeply as you can. The altruism inherent in open source, its privacy-oriented values, and importance for education and innovation are not widely understood. Let’s change that.Carl RichellCEOSystem76—Pop!_OS and the COSMIC Desktop Environment will not include Age Verification or Age Attestation.
Like what you see?

Share on Social Media

Contact

Support

Shipping

Careers

About Us

Sustainability

Privacy & Legal

Blog

Copyright © 2026 System76, Inc.

Intel, the Intel Logo, Intel Core, Iris, and Xeon are trademarks of
Intel Corporation or its subsidiaries in the U.S. and/or other
countries.

Open source values are fundamentally different from the concerns addressed by mandatory age attestation laws, as open source operating systems and applications do not collect personal information, profile children, inject targeted advertisements, or create addictive design patterns. The author posits that mandatory age attestation introduces privacy costs without providing corresponding safety benefits, arguing that open source projects are naturally resistant to these types of behaviors. For instance, the author notes that even systems like systemd, which added a birthdate field to user accounts, can simply ignore such data because a username and a birthdate could uniquely identify an individual, emphasizing that personal privacy is central to the open source philosophy.

The author explains that the nature of open source is often misunderstood, contrasting it with modern technology experiences where users are frequently subjected to invasive advertising. To counter this, the author emphasizes articulating how open source differs from such experiences. The process for achieving legislative exemptions involved a collaborative strategy. In Colorado, representatives engaged with the author and other members of the local open source community to share concerns. This resulted in a process where participants exchanged suggestions and language to protect privacy while seeking exemptions for open source software, code repositories, and container registries.

System76 engaged in internal brainstorming with community members and Red Hat to identify potential improvements to the proposed legislation, uncovering gaps in the language and exploring potential complications. The strategy involved coordinating with community members and lobbyists in California, exchanging notes and language that ultimately shaped the legislation. The primary goal was to establish an exemption standard in Colorado that could influence amendments in California, requiring California's support for success. This effort aimed to set an open source exemption standard that other legislatures could adopt.

The author advocates for moving beyond cynicism and focusing on the merits of open source to foster change for the community. The argument is made that advancements in computing, exemplified by iOS and Android, have shifted the focus toward platforms for application consumption rather than creation, necessitating an illustration of the contrast with a computing environment centered on the creation, sharing, and open collaboration inherent in free software. The author calls for legislatures to be engaged with constructive, educational feedback to better understand the altruism, privacy-oriented values, and importance of open source in education and innovation.