|
|
|
|
|
by jedwhite
1893 days ago
|
|
I'd recommend blocking FLoC on any websites you run. It is simple to do. Add this header to block FLoC: `permissions-policy: interest-cohort=()` See also this post on StackOverflow for information on how it adds a warning message in Chrome DevTools for browsers that aren't part of the current test [1] [1] https://stackoverflow.com/questions/66997942/error-with-perm... Edit for typo. |
|
Privacy is really important to me, so I am not affected because I don't use chrome in the first place. All the people who use chrome, especially on this site, know damn well what they agreed to. You all already opted into this and everything google comes up with tomorrow. Why should I put in work to give you the warm fuzzy feeling of having staved of the google spying for another day? If you want protection from this, use another browser.
At this point, blocking this from the website level just seems to support google even more, because it takes the pressure from chrome users to actually start thinking and stop being victims.