Re: [whatwg/fetch] Add `Prefer: safe` HTTP header (Issue #1891)

linusmartensson left a comment (whatwg/fetch#1891)

I feel like this is interesting, but if it doesn't take into account different definitions of 'safe' for different regions (e.g. what is "PG13" may differ depending on user location) - it will be hard to enforce in practice, and it again pushes complexity to each website and relies on external legalese or website preferences to decide what should be shown.  

'Safe' becomes intractable when one jurisdiction wants it to be safe for 5 year olds browsing on their parents' phones, while another wants it to be 'safe' for teenagers, and a third wants to restrict communication functionality but not content. I'm still of mind that the previously discussed <meta name="rating"> tag provides a solution that can enable age restriction in a way that pulls the rug on the need for invasive legal frameworks altogether. 

The parent decides on an OS with age restriction support and a browser with age restriction support, then configures as desired for a given age bracket. Not the governments, not the server.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1891#issuecomment-4012578983
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1891/4012578983@github.com>