5 ms·
I am surprised that there is such a fundamental misunderstanding of differential privacy on the Hacker News crowd. Meeting the standard of true differential pr
by FlyingLawnmower 9y ago
I am surprised that there is such a fundamental misunderstanding of differential privacy on the Hacker News crowd.
Meeting the standard of true differential privacy is one of the strongest known unconditional privacy guarantees. It will prevent Mozilla from being able to answer any user specific questions. For example, they might have an accurate count of how many people visit Google.com (say 60% of their user base), but they will be mathematically unable to point to exactly which 60% visited the site.
Differential privacy in the RAPPOR implementation is peer reviewed and well understood. We can also review the actual code that ships in Firefox, which is a big plus over the Chrome implementation. There are some caveats -- what epsilon are they setting, are they adding an appropriate amount of noise, how do they protect against repeated queries, etc. but all of these can and will be reviewed by the differential privacy community.
I am not affiliated with Mozilla or Google, though I do work in the field of differential privacy. On mobile now, but I am happy to provide links or answer questions to people who might have any when I am back at a laptop.
- devotedtoneu 9y agoI'm surprised at how difficult it is for certain posters in this thread to recognize the following about our behavior and device usage: More Data Collection < Less Data Collection
- GrayShade 9y agoI only skimmed the RAPPOR paper, but can you discuss the worst-case scenario where an NSA-like adversary is able to each data point when it arrives? Assuming this happens from the start, how much information would she be be able to obtain? > We can also review the actual code that ships in Firefox, which is a big plus over the Chrome implementation. Sure, but note that it's been implemented already and will be pushed to the users as an add-on, without going through the full release process. Even this HN post seems to have been prematurely buried. It would have been possible for this to be deployed without anyone knowing. Post-hoc reviewing of functionality as sensitive as this is not the ideal solution.