

I see, I don’t know how I missed that, thanks for pointing it out. I still think that the API itself is neat and I’d love to see that for the sake of comfort, but I also agree that the enforcement to use it even when it makes no sense to do so is just stupid. Let’s just hope that they fix this overshot at least if they refuse to drop it altogether.



So far, this bill (and every other one I’ve) seen basically wants to force OS developers to add a birthdate field to your account setup process and an APi to expose this field, which should then be used by other software to obtain your age and limit what they serve you (ads, tracking, nsfe content) based on the legal requirements of your current age bracket. So, no more age gates for every virtual “adult service” you consume, just once on OS setup.
And how to circumvent this? Simple: You lie, just like you did when you were a teen and wanted to access inapropriate content for your age.
Now, if they expand the bill to actually require verification instead of indication, that’s when things will get interesting. But even then, as long as you own a PC and not use a cloud PC, which means that the data is still stored somewhere locally, it can and will be manipulatable and therefore circumventable. How exactly is hard to say without seeing the actual implementation of the affected OS.
One thing to actually fear tho is how Microsoft and Apple will handle this: They tend to overshoot what the bare minimum law is asking for and actual, verified age data can be valuable when harvested in larger quantities, combined with other metrics and sold (think about how many surveys ask for your age or an age bracket). Most of the bills I read do mention “privacy and security when it comes to sensitive user information”, but as we all know: A fee is just another expense when it comes to calculating your net profit from your total revenue…