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

ell1e left a comment (whatwg/fetch#1891)

> I think that it's only fair to mention https://prefersafe.github.io/ here as well.

Interesting, I have to admit I didn't think of ads targeting kids. That seems like a potential issue for sure.

But I guess the main question is what's the least worst options of 1. gov id or strict age check linked measure like Online Safety Act, 2.  `Prefer: safe`, 3. `<meta name="rating" content="adult"/>`, 4. or I guess trying to not have any of these mechanisms ever, but e.g. the 3rd one already is out there.

Re-reading one of the criticisms posted in the other issue about the meta tag:

> In a year Texas will threaten to sue user agents who refuse to censor content about LGBTQ+ people in reaction to this meta tag, under the active today assertion that such content is fundamentally "adult" (the big user agents will comply). In three years browser owners and sites alike will find themselves operating under a regime based around this Comstock meta tag.

I feel like that's still possible to happen with the `Prefer: safe` one, so I wonder if adding a tag may actually have the least downsides, but I'm not sure. It's also the one mechanism that seems to have already quite wide usage from various adult sides in practice.

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

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