All’s well until other countries try to implement this and you will very quickly see how nearly none of them agree with each other on which age limit goes where. In my opinion, the best way to ensure that children don’t go to certain places on the internet is to either not give them access to the internet at all or to only let them use whitelisted websites that you review yourself before adding.
how nearly none of them agree with each other on which age limit goes where.
that’s the task of the website to figure out, the device does not have to be aware of the laws. but I think is still much easier to manage than id verification.
I habe an other idea. don’t make the websites send agelimit http headers, because as you said that can easily vary by country. instead send http headers that tell what kind of content is available there. only the categories that could be questionable. that way the device (actually the browser) would decide if with the kid account’s age that kind of content is accessible.
that way the browsers need to know the age limits, and maybe it’s easier to handle it this way.
In my opinion, the best way to ensure that children don’t go to certain places on the internet is to either not give them access to the internet at all or to only let them use whitelisted websites that you review yourself before adding.
ok, and I agree, but only very few parents will do that unfortunately. especially considering that their kids could be discriminated against by their limited clasates who don’t have their access so broadly limited.
and then, you still need such a whitelisting capability, which I think does not really exist today in firefox and such browsers. addons cant solve this because they can be removed.
This is kinda genius
All’s well until other countries try to implement this and you will very quickly see how nearly none of them agree with each other on which age limit goes where. In my opinion, the best way to ensure that children don’t go to certain places on the internet is to either not give them access to the internet at all or to only let them use whitelisted websites that you review yourself before adding.
that’s the task of the website to figure out, the device does not have to be aware of the laws. but I think is still much easier to manage than id verification.
I habe an other idea. don’t make the websites send agelimit http headers, because as you said that can easily vary by country. instead send http headers that tell what kind of content is available there. only the categories that could be questionable. that way the device (actually the browser) would decide if with the kid account’s age that kind of content is accessible.
that way the browsers need to know the age limits, and maybe it’s easier to handle it this way.
ok, and I agree, but only very few parents will do that unfortunately. especially considering that their kids could be discriminated against by their
limitedclasates who don’t have their access so broadly limited.and then, you still need such a whitelisting capability, which I think does not really exist today in firefox and such browsers. addons cant solve this because they can be removed.