Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[dead]


There is a way to do this, where nearly everyone is fine.[0]

However, the orgs don’t get to capture verified adult user identity to pad the value of their user data profiles…

[0] https://blog.google/company-news/inside-google/around-the-gl...


It seems unlikely that "is user adult" is not already easily modeled by any of these companies to within a very high degree of confidence. Even 15 or 20 years ago Google search could bracket your age pretty effectively. It doesn't seem like this adds metadata that wasn't already there.

Google prompts me to verify my age on my account I created in 2004. They’re not trying too hard.

If they admit this, they wouldn't be able to advertise to children anymore without breaking many rules.

Except that in the legal sense, "is user adult" flips from false to true overnight, and there isn't an easy way to account for that in any model that doesn't include verified ID. Same reason many liquor stores ID anyone who looks younger than 40.

I prefer if it's pretty easy to bypass, if it's going to be law at all. My favourite example of this so far is how bluesky handles it.

https://gist.github.com/mary-ext/6e27b24a83838202908808ad528...

The official app/client is 100% legally compliant in its unmodified state. But doing something like using another client, having your PDS say you're age verified, or using a ublock origin rule to change where the geolocation API thinks you are completely sidestep it.


It was never going to be perfect. I suspect the goal with things like these is to add additional friction to the process, to make it much harder for the general population to bypass them.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: