Comment by data-ottawa
8 days ago
Adding a browser header field would be sufficient, could be easily integrated into the OS and browser, and would let developers handle this issue in a few hours worth of effort.
ID verification is such an invasive measure and prone to the exact same failures as the simplest solutions.
While I'd agree, the issue with that solution is that validating against government issued identity solutions aren't always free. I don't know if this is the case with the UK digital ID, but the Danish version certainly isn't free to query. The Danish one has, to my knowledge, a solution that would allow you to do an age for a person, without getting any other information, so yes, the browser could do that, but there cryptographic bits ensure that now body messed with the header data is still missing. And again, who's suppose to pay for the API calls if the browser does it, Mozilla, Google, Microsoft... Ladybird?
I like this solution, integrated with whatever existing parental controls are in the OS.
That would empower parents to keep their kids from accidentally or casually accessing porn. Of course, an intelligent and determined teenager will probably find a way around it, which is also good; then they've learned a bit about computers.
I'm going to bet most kids will get around it by registering accounts with the IDs that they've taken pictures of, which belong to adults, then sharing the accounts widely.
Grandma isn't likely to have an account on one of these sites (unless one of your cousins beat you to it).