Hacker News Reader

Can't privacy concious browser defeat FLoC simply by sending random cohort IDs on each request?

That would require admitting that moving the tracking process to client-side actually improves on status quo (by not collecting data on the server).

While the whole framing of EFF et. al. is put in a way that does not allow for even a small doubt that the proposal is just the worst thing ever with no redeeming qualities. That framing disallows working within this feature to modify browsers to send the required headers.

not at all if you're not taking part in the data collection at all and are just sending noise on the channel. I guess chrome could counter DRM-signing the cohort-id or something

I would believe that random noise is easy to filter when you are Google.

Depends upon the noise, But even if they filter it out it will get the desired result of not having a cohart id. In case of opting out you are in the default don't like privacy invasive cohart

Reply on news.ycombinator.com