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.
Well, the problem is less setting up the birthdate and more whether the birthdate needs to be verified.
Plenty of OSs already query for a birthdate, particularly on gaming devices. And yes, they will provide age-based protections already.
The question is, does the parent/account creator need to enter an accurate birthdate or not, and how does the system know?
If they don’t, then whatever, it’s the same self-declaration we already have all over the Internet. No biggie. Everybody was born in 1901 and we’re all chill about it. It still makes for an absurd situation where you HAVE to have a personal profile for every user on every computer, which a ton of computers aren’t expecting, so it’s still dumb on top of being useless, but it’s a solvable problem.
If they do, then you know have one of the biggest cryptographic and data management challenges in computing history. How do you have every single device across the entire planet interface with every single piece of software and server to authenticate a piece of personal data and safely store it so you don’t have to constantly re-check? It’s insane. Plus it removes a parent’s ability to enable their children to engage with content at whatever speed they see fit. And there are potentially different regulations in different areas, where both the server and user location may change the required behavior, so the whole thing is an absolute mess from the concept up.