[jrochkind1]

I didn't realize FLOC was already in use.

Looks like to disbable it in Chrome... you have to find a deeply nested config and then tell chrome you want to "disable privacy-preserving features". !?!?

I can do this. But of course nobody else is, it's telling you are disabling privacy-preserving features! Its' making me kind of livid.

[sixothree]

I'd hate to be that guy. But Chrome is not your friend when it comes to privacy. Chrome is the adversary.

[Farow]

If you're using uBO, it's defused by default: https://github.com/gorhill/uBlock/releases/tag/1.35.0

[r00fus]

I thought that µBlock Origin didn't work on Chrome?

If you want privacy, stay on Firefox.

[hda2]

My understanding is that it's gimped on Chrome. It's still better than nothing.

Firefox unfortunately is becoming harder to use with every release.

[stjohnswarts]

by disabling it you're giving more uniquely identifying info to the fingerprinting backend apps lol

[lurkerasdfh8]

"the only wining move is not to play"

really, if you are in a point where you hunt for hidden settings to disable in your browser? why not just use firefox?

[jorvi]

You can either obfuscate with stuff Like Canvasblocker and Brave, both which expose slightly randomized prints, or 'poison the well' with Ad Nauseum.

[jrochkind1]

what uniquely identifying info does the feature disable, in exchange for FLoC?