Working backwards, I think the device is exactly the wrong place for enforcement. Devices are not individuals and individuals are not their devices. Devices are tools for interacting with the open internet. Multiple people can share one and most persons own multiple. Additionally, we don't treat any aspect of our society with this attitude. Would it be preferable for 16 year olds to be provisioned cars that were unable to turn into the parking lot of a liquor store so that the work of verifying the customer's age would not be "outsourced to people who don't want to do it"? I like the real world, and I think we have done a pretty good job at organizing ourselves as a society, and it's my sincere belief that our interactions online would benefit by closer reflecting those that happen in the material world. I wrote about this at length in the essay in comments below.
Second, while it is admittedly a very difficult challenge, the privacy can be solved, and I'm very excited to be working on it. I don't accept that the status quo or a dystopian alternative are the only two outcomes, but I do sincerely respect those in bucket 2 and their prerogative to avoid any site utilizing age verification technology. That being said, I do plan to earn the trust of many in that bucket with a bit of integrity, transparency and cryptography :)
As for bucket 3, that's exactly who this was made for.
It’s true that devices aren’t people, but I think that’s a strength of taking a device-based approach. It’s easier to for parents to keep track of which devices their kids have, and there are fewer privacy issues.
It’s okay for people to share devices. Parents (or anyone else who is curious) can use a child-locked device to see what the Internet looks like for kids. Kids can use a parents’ device with supervision.
It’s also safer if websites cannot assume that whoever is using a locked device is necessarily a child. If it’s just an http header, search engines should be able to crawl the Internet in child-locked mode to see what’s there. It would be easier to enforce laws against advertising to children.
I do actually think there's still a role for device-based parental controls in certain contexts for many of the reasons you mentioned (the portal is a cool analogy for this), and I like both your ad and cookie blocking ideas. Thanks for taking the time to share your thoughts.
1) Those who are clamoring for age verification (generally on sites they never interact with themselves.)
2) People arguing fiercely against age verification and won't engage with any site who uses it
3) Most significantly, the large majority of people in the middle who can't be bothered to do AV and will just use another overseas website instead.
Even if the privacy can be solved (and I don't believe it can as someone fundamentally unwilling to upload my ID even once), that balance is basically the problem with trying to outsource the work to people who don't want to do it. We can already see that even privacy preserving solutions will not be used by adult site visitors in multiple adult site attempts to roll it out. The ONLY viable solution is parental filters on device. Anything that pushes the work to people who don't want it fails because the sites will just move overseas instead of losing the vast majority of their actual users. Or they roll it out and the traffic moves overseas, like data analysis has shown happened in UK.
You just can't solve the problem by pushing the work onto everyone instead of tackling it at its source. Rather than try to lock down the entire Internet, which will never happen, lock down child devices.