I'm surprised I cant find any mention of this "age check" (not verification!) concept/technique that works the other way around and is pretty perfect regarding security, privacy, not-tracking, no-data-collection, etc.
AGE-[CountryCode].XML 1. Basically every domain/site/service or even single page/URL-path can have a corresponding age-[].xml file "attached" to it. 2. Any device can request that file and act accordingly (if for example parents configure their children's s-phone to only allow content for ages below 13 it will just not show porn sites (which will be "forced" by law to supply such age-[].xml files which costs them nothing)).
On eg. Wikipedia specific pages on eg. sexuality could have their own more strict age requirements than almost anything else.
- https://age-label.com/features/overview
- https://de.wikipedia.org/wiki/JusProg
- https://www.jugendschutzprogramm.de/age-xml/
AFAICT it was developed in 2012 by a/the German (government/non-profit?) organization for youth protection. To offer solution of what the Jugendmedienschutzstaatsvertrag mandated – nice to see ZensUrsula implementing shit outside of Germany again (because she failed inside) \sigh**
This is not a full concept nor have I thought about all potential use-cases, not to even mention edge cases but it would remove age verification completely (replaced with just a check) and would shift the control/power over what children can access/see/use to parents guardians (as it should be for such a wide field – a blanketed ban on drugs below certain ages is different…).
I assume age isn't the only qualifier – age + allow-/block-lists for more granular control (allow sexual topics on wikipedia but sill block porn).
Addressing some issues mentioned elsewhere: 1. eg. Facebook would need to know the money-calf's age, so transfer age form device to service? Nope – they could just create www.fb4kids.com or www.facebook.com/forkids and facebook.com would just AGE.XML block minors but allow them on the other domain/URL (non-children could create accounts there too ;-)).
- regarding tracking of which IPs/clients access the
age.xmlat all, which of those stop all further traffic, etc.: The age.xml information could be integrated into the DNS maybe (like MX-records?)? Or hosted by government / non-profit organizations – Requests would ask for the first few digits of the sha256 of the site/service/domain you're trying to access or something (ask for a bunch of destinations in one go to kinda hide which one you're specifically asking for).
Some keywords for "SEO" (If you want to complain because you think you know what SEO stands for, please think again – maybe a little deeper this time – thank you) AGE.XML AGE-DE.XML AGE-[CountryCode].XML JusProg Jugendschutz JMStV
Source: r/StopKillingGames · by /u/Nilm0