Don’t get me wrong, I’m all for privacy. But between setting up the birthdate when creating my children’s local account on their computers, and having to send a copy of their ID to every platform under the sun, I’d easily chose the former.
I’d even agree to a simple protocol (HTTP X-Over-18 / X-Over-21 headers?) to that.
There’s fairly clear evidence at a societal level that access to, for instance, hardcore pornigraphic material is harmful to children, but that is very different to having evidence that a particular child is currently being exposed to it.
exactly. so why do we need more laws that also happen to provide massive leak able tracking to corporations and govs without warrants, etc?
I’m not sure what you mean by “massive leak able tracking” in this case. It’s literally a flag that indicates the user’s age bracket, and means sites don’t use the really invassive options.
setting that flag involves the leakable process.
Again, I’m only going by the Californian bill, but that one is pretty clear that the person setting up the account should either supply the user’s birth date, or the age bracket they are in. There is nothing indicating this should be validated in any way. I’d agree that, if the machine was compromised, and the user’s birth date was used, it would be possible to leak that data, but given those preconditions, it would be one of the least interesting things leaked. I’d certainly prefer to just store the age bracket, and have a way for the computer admin update it as the user grows towards their 18th birthday.