

I’m personally against this kind of thing, but I hate how much of a fantasy echo chamber this stuff is here. There’s so much misinformation and hyperbole in this thread alone.
In general I support the idea of device-level age verification. The narrative around it uses old school methods only (this one goes with just inputting your date of birth, which I’ve already done for years for stuff like Steam), rather than the ID or face scan by random third parties methods used in age verification discussions and requirements elsewhere. In my opinion software being able to use an API provided by the OS itself is much better, and with the right OS (linux) much more trustworthy than any web-based solution.
My only real problem is the lack of user choice. This comes in two forms:
- Giving your birth date should be optional. I’m fine with them requiring that no birth date given means you default to being underage, but actually giving the birthdate should be up to the user.
- The birthdate should not be given out to random software asking for it. Either the user should be asked for permission, or only a boolean of whether they are underage or not should be provided. This bill doesn’t require either of those, nor leaves it to later clarification.

This bill requires the OS to ask you for your birth date, explicitly the birth date. That’s all the age verification it requires. So I’m not sure how that’s “not going to qualify as age verification”. Why would the very method specified in the bill not count? There’s no requirement to use other methods to verify the age you’re given. The user just selects their birth date freely and the OS accepts it and that’s it if they’re not underage.