The linked post is about an Illinois bill that would make operating systems and app stores carry an age-related setting that apps can query, with the stated goal of letting services apply child-safe defaults and restrictions. The article framed this as Illinois telling every operating system to report your kid’s age. A lot of the useful clarification was that the bill, as described in the comments, does not require hard identity checks or government ID collection. It mostly mandates a parental-controls style birth date or age bracket field and says the resulting signal must be encrypted when shared.
That distinction drove the entire reaction. The dominant view was still hostile because people saw the mandate as infrastructure for censorship, liability shifting, and future surveillance. The sharper version of that argument was not just "privacy bad." It was that Meta and similar platforms want the operating system to own the age signal so they can stop being the party blamed when minors see harmful content, ads, or features. Put differently, the law can shrink platform liability faster than it shrinks platform power.
The strongest pushback to the panic was that this is much less invasive than the age-verification regimes already spreading elsewhere, where users get forced into face scans, ID brokers, or third-party verification vendors. Several commenters argued that if some form of age gating is politically inevitable, a coarse
OS-level age bracket is the least dangerous version because it avoids pushing every app toward collecting passports and selfies. They treated it as standardized parental controls, not real verification, since parents or users could still lie unless some separate verification layer is added.
Where people seemed to land is that the bill is neither harmless nor the apocalypse. It is a standards move with real policy consequences. It creates a common age signal that could reduce repetitive app-level checks, but it also builds a clean handoff that lets platforms say "the OS told us this user was an adult" when things go wrong. For open source operating systems and smaller developers, that same standard could become a compliance burden even if the practical implementation is just an age bucket in account settings. The live issue is less the exact Illinois text than the precedent that age classification becomes a built-in feature of general-purpose computing platforms.
itsfoss.com