3 ms·
I would expect that it's practical to reverse engineer the cohorts into a browsing history. This means that an interested party could derive browsing informatio
by lumost 6y ago
I would expect that it's practical to reverse engineer the cohorts into a browsing history. This means that an interested party could derive browsing information from a page visit rather than needing to instrument thousands of websites with cookies.
There isn't really any hard bound on how much information could be leaked via these algorithms.
- morelisp 6y agoCohorts could be reverse-engineered to give you a probability space of browsing history, which would be identical for any user in the cohort given a single sample. > There isn't really any hard bound on how much information could be leaked via these algorithms. With ~33k cohorts, there is literally a hard bound of just above 15 bits per visit. That's still theoretically a lot if you have some other stable identifier, but practically speaking most users on most sites will have an identical cohort and it will drop off rapidly as cohorts stabilize into groups appropriate for ad targeting. Barring the other considerations I've mentioned in the comments here, that's still immeasurably better for individual privacy than ~infinite bits per visit from stable third-party cookies.
- benatkin 6y agoExcept the privacy conscious just won, so there is no need to compare it to the former status quo. Why squander our victory?