Enabling developers and organizations to use differential privacy
Hi, I'm one of the authors of the scientific paper¹ linked in this blog post. Incidentally, I wrote a series of blog posts explaining differential privacy in layman's terms. The first post might be "not-technical-enough" for HackerNews, but maybe the next in the series make up for it. Feedback welcome =)<p>- <a href="https://desfontain.es/privacy/differential-privacy-awesomeness.html" rel="nofollow">https://desfontain.es/privacy/differential-privacy-awesomene...</a><p>- <a href="https://desfontain.es/privacy/differential-privacy-in-more-detail.html" rel="nofollow">https://desfontain.es/privacy/differential-privacy-in-more-d...</a><p>- <a href="https://desfontain.es/privacy/differential-privacy-in-practice.html" rel="nofollow">https://desfontain.es/privacy/differential-privacy-in-practi...</a><p>- <a href="https://desfontain.es/privacy/almost-differential-privacy.html" rel="nofollow">https://desfontain.es/privacy/almost-differential-privacy.ht...</a> (describes a core intuition behind the system described in our paper)<p>- <a href="https://desfontain.es/privacy/local-global-differential-privacy.html" rel="nofollow">https://desfontain.es/privacy/local-global-differential-priv...</a><p>I also think Section 2 of the paper should be readable by most folks with a basic understanding of SQL and differential privacy.<p>¹ <a href="https://arxiv.org/abs/1909.01917" rel="nofollow">https://arxiv.org/abs/1909.01917</a>