Quick Summary
MidnightBSD, an open-source operating system designed for desktop usability, has modified its license to exclude California residents from using the system starting January 1, 2027.
This decision is a direct response to California’s Digital Age Assurance Act (AB 1043), which requires OS providers to build mandatory age-verification interfaces and real-time data-sharing APIs.
The small team behind MidnightBSD chose to bar the state's users rather than risk the law's severe financial penalties, which can reach $7,500 per child for intentional violations.
From ostechnix.comUnderstanding the Digital Age Assurance Act (AB 1043)
California passed AB 1043 in 2025 to protect minors online. The law applies to "operating system providers" and "developers". It creates several strict requirements:
Age Verification: The OS must show an interface during account setup. This screen requires the user to provide their birth date or age.
The Digital Signal: The OS must share a real-time "signal" with apps. This signal tells app developers if a user is a child (under 18) and which age bracket they fall into.
Strict Compliance: Developers must request this signal every time someone launches an app for the first time.
This law becomes fully operative on January 1, 2027.
The Risks for Small Developers
You might wonder why a small software team would ban a whole state instead of just following the law. The answer lies in the technical burden and the financial risk.
1. Engineering Hurdles
The law requires a complex system to track and share user ages securely via an API. For a small team, building this infrastructure takes time and resources away from improving the core operating system.
2. Extreme Financial Penalties
The penalties for mistakes are very high.
If the California Attorney General finds a "negligent" violation, the fine is up to $2,500 per affected child. If they find an "intentional" violation, the fine jumps to $7,500 per child.
A small open-source project could face millions of dollars in fines very quickly.
The Decision to Exclude California
On February 27, 2026, the MidnightBSD team posted on X (formerly Twitter) about the license change. They stated the exclusion is a measure they are taking "until [they] have a better plan".
MidnightBSD Announcement to Exclude California Users from using MidnightBSD for desktop use effective January 1 2027MidnightBSD Announcement to Exclude California Users from using MidnightBSD for desktop use effective January 1 2027
By changing the license, the developers hope to protect the project from the legal reach of AB 1043. Because they cannot afford the risk of massive fines, they chose to bar users in that region instead.
Conclusion
The conflict between MidnightBSD and California highlights how broadly drafted consumer protection laws can unintentionally alienate small, community-driven projects.
While AB 1043 aims to protect minors, its technical requirements (like real-time age-signaling APIs) and heavy fines create a prohibitive compliance burden for "small communities of dedicated developers".
For a project like MidnightBSD, which operates on a volunteer basis, the legal risk of non-compliance outweighs the benefit of serving the California market, forcing them to abandon their mission of being "The BSD For Everyone" in that region.
The conflict also highlights a growing problem in the tech world. When states pass complex regulations with high fines, small creators often suffer the most.
MidnightBSD started with a mission to be a system for everyone. Now, because of the Digital Age Assurance Act, the project must limit who can use it to survive.
For now, if you live in California and want to use MidnightBSD, you will have to wait for the team to find a "better plan".
It's just going to get worse, this stuff is spreading. And the whole premise is stupid, it's the parents' job, not the software developers. Inevitably kids will use their parent's computers after they were declared to be used by adults, negating the whole effort. Their only way around that would be taking this to the next level, requiring selfies every time the OS is used, an application is launched etc.
