4 ms·
Note this all occurs client-side, which means that it only affects browsers that implement FLoC. You can opt-out of this (for now) in Chrome by disabling third
by EMM_386 6y ago
Note this all occurs client-side, which means that it only affects browsers that implement FLoC.
You can opt-out of this (for now) in Chrome by disabling third-party cookies.
You can also simply use another browser such as Firefox.
- traskjd 6y agoOr (hopefully) Microsoft Edge - Chromium engine, without this (and quite a lot of other Goog tracking code).
- adamcstephens 6y agoThis assumes Microsoft hasn’t replaced all the Google tracking with their own.
- snovv_crash 6y agoWhat would stop a malicious client from implementing a noisy FLoC to 'poison the well'?
- dialtone 6y agoYou could do that, technically there are other APIs like Trust Token API to protect against malicious clients, but one client in a giant cohort is unlikely to cause much damage anyway so it doesn't matter... And this is anyway going to be machine learning driven so unless you poison all of the FLoCs a lot it may end up being discovered or the FLoC simply not considered performant by a specific ad campaign.
- snovv_crash 6y agoOk. But what if, say, Mozilla did this?