3 ms·
It’s a opportunity to put priv engineering techniques to the test in prod, at least. That’s 100% the main thing that stands out here. In the raw browser histor
by dogman144 6y ago
It’s a opportunity to put priv engineering techniques to the test in prod, at least. That’s 100% the main thing that stands out here.
In the raw browser history, prior to ~hashing it to a FLoC ID, can Google anon PII while still maintaining good data analytics from the rest* of the dataset’s fields?
Priv engineer, as an engineering discipline, would argue yes.
If this is what Google does and the privacy is put through its paces (can a FLoC ID de-anon into a user?), then yeah this isn’t a bad trade off.
Use case: Google has to make money, I love Chrome’s and GSuite’s UX, priv eng’ing lets them use my data to pay for that UX while moving all the tracking in-house and ending 3rd party cookies.
- livre 6y ago> can a FLoC ID de-anon into a user? Currently yes and seems like a though problem to solve (there are trade offs but it's likely that this will never be fully solved, like encryption, you can only make it so difficult that it isn't worth doing it but not impossible to do): https://github.com/WICG/floc/issues/100 https://github.com/WICG/floc/issues/100
- dogman144 6y agoVery cool I’ll check it out. I’ll push back on it being tough to solve — unless you’ve looked into privacy engineering and have some further data in that direction. Whole field exists to de-link PII to data that supports business analytics, and the tech is there at a non-tough level for Google to achieve.