California’s Digital Age Assurance Act (AB 1043), effective January 1, 2027, mandates operating system providers to collect and transmit user age information to app developers via a real-time API, categorizing users into four age brackets. This law broadly defines operating system providers to include various software developers, shifting the burden of age-appropriate content decisions to app developers who are deemed to have actual knowledge of a user’s age range upon receiving the signal. While the act avoids biometric verification, focusing on self-reported age, it carries significant penalties for non-compliance, though enforcement against decentralized Linux distributions is expected to be challenging. Governor Newsom has also encouraged legislative amendments to address complexities before the law’s effective date.
Read the original article here
California has recently enacted a new law that introduces age verification requirements for operating systems, extending its reach to include Linux and SteamOS, with the age verification process integrated directly into the operating system account setup. This development has sparked considerable discussion, largely revolving around the practical feasibility and underlying intent of such a mandate, especially for systems that operate differently from more mainstream alternatives like Windows or macOS.
A significant point of contention is the fundamental misunderstanding of how Linux and similar open-source operating systems function. Unlike proprietary systems that often rely on centralized accounts linked to online services from companies like Microsoft, Apple, or Google, Linux distributions typically allow users to create accounts with minimal or no online linkage. The flexibility of Linux means users can remove packages, even critical ones, and the concept of a single, online-dependent OS account isn’t inherent. Creating a user on Linux is often a straightforward command, decoupled from any specific online identity.
Assemblymember Buffy Wicks, the author of the bill, has stated that the legislation aims to “avoid constitutional concerns by focusing strictly on age assurance, not content moderation.” This suggests the intention is to create a mechanism for age signaling rather than directly controlling or censoring content. However, critics argue that the law’s reliance on self-reporting for age verification is inherently flawed. The argument is that if age verification is voluntary and based on self-reporting, it places little burden on providers and offers a superficial layer of protection. The notion of enforcing such a law on systems like Linux, where user control is paramount and technical barriers can be easily overcome, seems highly impractical to many.
The core of the issue, for many observers, lies in the belief that this law is less about genuine child protection and more about data aggregation and control. There’s a strong suspicion that the underlying motive is to make it easier to tie personal data, including age, to specific individuals. This concern is amplified by the fact that the bill, Assembly Bill No. 1043, mandates that operating system providers must offer an interface during account setup for users to indicate their birth date or age. This information is then to be transmitted as a signal about the user’s age bracket to applications available in a covered app store. Developers are required to request this signal when an application is downloaded and launched.
The self-reporting aspect of the law has been met with widespread skepticism. Many anticipate that users will simply input an age of 18 or older, rendering the verification process effectively meaningless. This leads to the question of whether this law is truly intended to safeguard children or if it’s a way to shift liability. The proposed framework suggests that if an operating system provider transmits a self-reported age signal in good faith, and an app maker receives that signal, then the responsibility for age-appropriate content decisions might shift to the individual user or their parents, rather than the platform or application developer.
While the bill states it does not require photo ID or facial recognition, relying instead on self-reporting, many question the efficacy of such a system. The idea of mandating age verification on operating systems, especially those as configurable as Linux, brings up further practical challenges. For instance, what happens when a user installs a custom version of Linux that bypasses or manipulates this age verification mechanism, perhaps reporting all users as over 18? This highlights the potential for workarounds and the difficulty in enforcing such a law on a system that prioritizes user freedom and customization.
The implementation for offline or air-gapped systems also presents a conundrum. If an operating system is installed without an internet connection, how will the age verification process be initiated or enforced? The law’s creators are seen by some as disconnected from the realities of technology, leading to what many consider poorly thought-out legislation. This mirrors past instances where state-level initiatives have been criticized for a lack of technical understanding.
The implication for gaming platforms like SteamOS is also a significant consideration. For users who have long-standing accounts, their Steam accounts might be “old enough to drink,” making the idea of re-verifying age seem redundant or even intrusive. Furthermore, some argue that the focus should shift towards parental responsibility for monitoring children’s internet usage, a task that is arguably made easier by built-in parental controls on some platforms.
Ultimately, the law raises broader questions about privacy, control, and the role of technology in society. While the stated aim is to protect children, the methods proposed, particularly on open-source and highly customizable platforms like Linux, seem to fall short of practical implementation and raise concerns about government overreach and data collection. The debate continues as to whether this legislation will truly achieve its objectives or simply become another example of well-intentioned but technically unfeasible regulation.
