this post was submitted on 09 Mar 2026
46 points (100.0% liked)
Privacy
9170 readers
289 users here now
A community for Lemmy users interested in privacy
Rules:
- Be civil
- No spam posting
- Keep posts on-topic
- No trolling
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In the OS is where it belongs. But not like this.
Parental controls is the answer. The OS should be required to support robust APIs that allow parents to set the age of their child and prevent children from accessing apps or sites (via browser APIs that hook into the OS APIs) that are out of the age range. The only actual "verification" should be parents choosing to type in the number.
There should be no mechanism broadcasting age information. Flip it, make websites contain content tags, browsers/OS would then block based on opted out content. Parents get controls, we get to keep our privacy.
Honestly, that is how I would prefer it be done. But it isn't what OP asked for.
It would have to be set at an operating system level, with the OS providing an API for the browser to use, while the os itself restricts installation of unapproved apps (and to work, installation of apps would have to use an allow-list or a similar age-tagging system, where any app that includes general web access has to be 18+ unless it also implements age-gating correctly).
But yes, this would be the best system. Parental controls have never been very successful in the past, but I think part of the reason for this is that they've never been properly supported up and down the stack. The government should mandate that it is supported the whole way, so that parents really have the tools they need to enforce parental controls.
For sure. If we wanted to protect kids with no intrusion we'd just make an HTTP header that was "user age" and then let the sites decide what to show and what to block. Porn sites don't want to show dicks to 6 year olds, it'd be 10 seconds to make an nginx rule that says "if user age < 18, show static error page".
And that's it, easy peasy. If we wanted to, at that point we could start suing individual sites that choose not to use that information in order to get compliance, but probably we don't need to, since it's pretty easy to support and like I said, there's no money in showing these things to kids anyway.
But that's not what it's about.
That's effectively all the Californian law requires, and it doesn't even expose the age details to apps that ask for it.
The California law requires everyone to show their age, not just kids.
Forcing companies to respect voluntary parental controls is not even close to demanding everyone to prove their age.
No it doesn't, at all. In fact it specifically says it only applies in the case where it's a parent setting up a device for a child.
You can read the actual law, it's short.
Number 4 wouldn't be a thing if it didn't apply to everyone.
If the API can't respond with "is an adult", how should it respond when an adult is using it?
The API should work like parental controls: Is a kid and age bracket/meets minimum age. Anything else is a NULL or no age value.
If you have to say you are 18 then it applies to everyone.
Then that is the 18+ age signal. "This user is not covered by age restrictions" implies they're older than 18.
And as the law says...
Parental controls don't apply to anyone not using parental controls.
This applies to everyone.
Do you get how those are two very different things?