Hacker News Reader

Parent Full thread

EMM_386

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.

View on HN

Or (hopefully) Microsoft Edge - Chromium engine, without this (and quite a lot of other Goog tracking code).

This assumes Microsoft hasn’t replaced all the Google tracking with their own.

What would stop a malicious client from implementing a noisy FLoC to 'poison the well'?

You 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.

Ok. But what if, say, Mozilla did this?

Reply on news.ycombinator.com