Motivation for me to use Brave and Safari more. The best way to opt out is to not use Chrome.
How to fight back against Google FLoC
11–20 of 95 posts
Re: How to fight back against Google FLoC
#12I want to suggest another thing we can collaborate on. File bugs against Apache and nginx such that Apache and nginx emit Permission-Policy header by default. People who want FloC can opt-in, but since Pervasive Monitoring Is an Attack (RFC 7258), it is clearly severe security bugs in Apache and nginx that they don't emit this header by default.
This may need CVE.
Re: How to fight back against Google FLoC
#13Would I be terribly downvoted if I said that I prefer targeted ads? I'd rather see GPUs than feminine hygiene products. FLoC seems like a method of saving my preferences locally, which is fine. I'm not interested. I won't use Google's browsers and I'll continue to filter my traffic. Internet privacy will always be an uphill battle, there's worse things going on, starting with centralized and monopolized DNS, I feel w…
From what I can tell if you don't use Google chrome then you're not affected by this.
Re: How to fight back against Google FLoC
#14Would I be terribly downvoted if I said that I prefer targeted ads? I'd rather see GPUs than feminine hygiene products. FLoC seems like a method of saving my preferences locally, which is fine. I'm not interested. I won't use Google's browsers and I'll continue to filter my traffic. Internet privacy will always be an uphill battle, there's worse things going on, starting with centralized and monopolized DNS, I feel w…
It’s not local, because your cohort id will be sent to advertisers, and they’ll back-reference that against what they believe you’re interested in.
But either way, your initial statement assumes that ads will only be interesting to you if your browsing habits are tracked across the internet. There’s another option: if you visit sites that are focused on GPUs they can advertise GPUs to you. This is the way advertising worked from 1700-2000.
Re: How to fight back against Google FLoC
#15I'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.
Re: How to fight back against Google FLoC
#16I want to suggest another thing you can do as a web developer. If you can afford it, block all Chrome users, and instruct users to download Firefox instead. Explain why your website is not available for Chrome.
[deleted]
Re: How to fight back against Google FLoC
#17At what point enough is enough and Chrome and other data-collecting Google products can be called for what they are - spyware? It’s time to pick another browser.
Point is right now. Chrome is spyware, clear and simple.
It really is, but oh how times have changed since that term actually meant something to web users.
Re: How to fight back against Google FLoC
#18I want to suggest another thing you can do as a web developer. If you can afford it, block all Chrome users, and instruct users to download Firefox instead. Explain why your website is not available for Chrome.
Maybe notify instead of block?
“You are using Chrome which tracks you without consent. Download a spyware-free browser here.” In red at the top of the page with links to brave and Firefox.
Re: How to fight back against Google FLoC
#19While I do understand that some people may not like it, I don't see how FLoC is particularly harmful. I've read several articles about it, and most of them just say something like "you are being put in a advertising cohort -- see how creepy it is", which doesn't really prove anything. One more specific argument against FLoC is that it will make help tracking users via fingerprinting. I don't really buy it. First of a…
and if FLoC has only 8 bits of entropy
From the EFF article that you don't like:
> Google’s experiment used 8-bit cohort identifiers, meaning that there were only 256 possible cohorts. In practice that number could be much higher; the documentation suggests a 16-bit cohort ID comprising 4 hexadecimal characters.
Also, its since someone can belong to more than 1 cohort, the 8bits is a bare minimum and not a maximum. For instance, techie who likes hiphop, buys whisky and is looking for a washing machine is 32bits of entropy and covers the billion users with ease.
Re: How to fight back against Google FLoC
#20I want to suggest another thing you can do as a web developer. If you can afford it, block all Chrome users, and instruct users to download Firefox instead. Explain why your website is not available for Chrome.
Maybe notify instead of block? “You are using Chrome which tracks you without consent. Download a spyware-free browser here.” In red at the top of the page with links to brave and Firefox.
This is also a good idea.