Opting Your Website Out of Google's FLoC Network

Re:Opting Your Website Out of Google's FLoC Network by pdenton on Friday April 16, 2021 @06:01AM (#26831859)

I don't think the meta version of Permissions-Policy ever got implemented. "http-equiv" isn't a magic "here's a HTTP header I forgot to mention" pixie dust.

Better stick to the actual recommendation of adding the header in the server configuration.

[ Parent | on HN ]

Re:Opting Your Website Out of Google's FLoC Network by shakna on Friday April 16, 2021 @09:21PM (#26840827)

Whilst http-equiv is said to be an enumerated value, so far as I know in Chrome, it actually is "magic HTTP Header pixie dust": [0]

And whilst in Firefox parsing of the element is more spread out, they accept a very wide number of headers that aren't documented, and you'll find examples on MDN for any number of headers using http-equiv which aren't specified in the standard or on their docs for http-equiv itself [2] (For example, X-DNS-Prefetch-Control [1]).

[0] https://source.chromium.org/chromium/chromium/src/+/master:o...

[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-...

[2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/me...

[ Parent | on HN ]

Re:Opting Your Website Out of Google's FLoC Network by imwillofficial on Friday April 16, 2021 @10:41AM (#26834470)

In my case I don’t have access to the server configuration. I’m running a blog with Ghost Pro, is the above a reasonable workaround?

[ Parent | on HN ]