Heavy-handed web regulations are pushing us toward a dystopian future. Shifting filtering directly to the router level fixes the problem without forcing adults to hand over sensitive ID data.
My opinion: The other way around puts the onus for violating the law on the OSes.
Also the telemetry is the same either way:
“Are you over 18?” Yes/No is basically the same signal to the server as “This content is rated 18+” followed by downloading more content or not.
It’s also vulnerable to basically the same brute force age guessing which should be outlawed, e.g., “This pixel is for 5+, that one is 10+, …” Until you get the user’s age, but that also should be considered a violation by the website and not the OS, in my book.
Policing the OS is like policing credit card companies for kids buying cigarettes. It could work but it’s not really their responsibility to check.
Brute forcepixel valid concern, but that why tag might better (and tracking pixel should illegal anyway). Also parent then has control to allow different thing depend on what they think ok.
But think this not os thing, this browser thing. Since most based on big project (chromium, firefox, webkit) if base implement parental control most other will automatically get. And display blocked for set range or set of tag usually not difficult. If in HTTP header could even do in OPTION response before any data sent.
If they want for “app store” maybe become difficult. Then recommend policy maker to sponsor standard library for check implementation.
Honest though any force to have block implement just stupid, parent should get tool to enable where want and get proper education on it, and child too. This decision of parent not fucking government. And education is government fail, not parent.
Edit: but also this more force of implement parental control than force to check user. Enforce should really be on website to send correct information and then parent decide what to do with.
My opinion: The other way around puts the onus for violating the law on the OSes.
Also the telemetry is the same either way:
“Are you over 18?” Yes/No is basically the same signal to the server as “This content is rated 18+” followed by downloading more content or not.
It’s also vulnerable to basically the same brute force age guessing which should be outlawed, e.g., “This pixel is for 5+, that one is 10+, …” Until you get the user’s age, but that also should be considered a violation by the website and not the OS, in my book.
Policing the OS is like policing credit card companies for kids buying cigarettes. It could work but it’s not really their responsibility to check.
Brute forcepixel valid concern, but that why tag might better (and tracking pixel should illegal anyway). Also parent then has control to allow different thing depend on what they think ok.
But think this not os thing, this browser thing. Since most based on big project (chromium, firefox, webkit) if base implement parental control most other will automatically get. And display blocked for set range or set of tag usually not difficult. If in HTTP header could even do in OPTION response before any data sent.
If they want for “app store” maybe become difficult. Then recommend policy maker to sponsor standard library for check implementation.
Honest though any force to have block implement just stupid, parent should get tool to enable where want and get proper education on it, and child too. This decision of parent not fucking government. And education is government fail, not parent.
Edit: but also this more force of implement parental control than force to check user. Enforce should really be on website to send correct information and then parent decide what to do with.