Cloudflare and Fastly should step up and add this header for all domains by default. That would probably be enough to kill this idiotic mal-feature.
Client side there is also the DNT header which everyone, including Google is happily ignoring. So I'd imagine things will get ignored similarly here.
Re:Am I FLoCed?
by 1vuio0pswjnm7 on Saturday April 10, 2021 @07:44PM
(#26766355)
You are suggesting that Chrome will ignore this header sent from a site. You are suggesting that sites will not be able to opt-out.
Seems like the easierst way to opt-out of FLoC is to use a browser that does not support it. I already do that. It does not even support CSS or Javascript. I love it.
With client-side header "DNT", sites can ignore it. With server-side header "Permissions-Policy", browsers or other programs that make HTTP requests can ignore it.
Re:Am I FLoCed?
by 1vuio0pswjnm7 on Saturday April 10, 2021 @07:37PM
(#26766316)
Wrong syntax.
http-response add-header Permissions-Policy "interest-cohort=()"
Permissions-Policy: interest-cohort=()"
https://github.com/WICG/floc
Added to proxy config.
http-response add-header "Permissions-Policy: interest-cohort=()"