<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1709.02753/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1709.02753/feed.xml" rel="self" type="application/rss+xml" /><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — mentioned by matthewdgreen</title><link>https://news.ycombinator.com/item?id=43695546</link><guid isPermaLink="false">urn:hackerpapers:mention:1709.02753:43695546</guid><pubDate>Tue, 15 Apr 2025 16:59:06 GMT</pubDate><description>&lt;p&gt;I went looking for exactly this information the other day. I was surprised to find that it&amp;#x27;s hard to come up with recent, detailed explanations of what Apple is doing for telemetry collection. When they announced their DP systems back in 2017, they were clearly doing something like Google&amp;#x27;s RAPPOR [1]. But it&amp;#x27;s been several years since then and their writeups haven&amp;#x27;t been updated very much at all [2]. This is pretty important, because these systems aren&amp;#x27;t so robust that you can just assume everything is working without review. (See, for example, this paper [3].) Apple should at least document…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — HN submission</title><link>https://news.ycombinator.com/item?id=19684594</link><guid isPermaLink="false">urn:hackerpapers:submission:1709.02753:19684594</guid><pubDate>Wed, 17 Apr 2019 17:32:31 GMT</pubDate><description>&lt;p&gt;Privacy Loss in Apple’s Implementation of Differential Privacy (2017)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;59 points; 8 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — mentioned by Cynddl</title><link>https://news.ycombinator.com/item?id=16672621</link><guid isPermaLink="false">urn:hackerpapers:mention:1709.02753:16672621</guid><pubDate>Sun, 25 Mar 2018 15:36:06 GMT</pubDate><description>&lt;p&gt;Differential privacy appears regularly on Hacker News, with either theoretical articles or projects that aim to implement it. Yet often there is a huge gap between both. For example, Apple has touted about its use of differential privacy, but researchers [1] have shown that the privacy budget is reset every day and the parameters, buried inside the code, lack a proper derivation. Similarly, Uber seems to use DP for internal analytics. However, the proposed model does not seem really robust and does not provide accurate results at all [2]. One should always carefully review claims associated…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — mentioned by frankmcsherry</title><link>https://news.ycombinator.com/item?id=15600666</link><guid isPermaLink="false">urn:hackerpapers:mention:1709.02753:15600666</guid><pubDate>Wed, 01 Nov 2017 12:51:50 GMT</pubDate><description>&lt;p&gt;&amp;gt; Wired recently deployed a team of experts to deconstruct Apple’s code and found its differential privacy practices to be lacking, a characterization that the company strongly disputes. If by &amp;quot;deployed&amp;quot; they mean &amp;quot;interviewed about their work&amp;quot;. I don&amp;#x27;t understand Time crediting Wired with the research[0], which does a disservice to their actual sources of funding. https://arxiv.org/abs/1709.02753&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — mentioned by pgeorgi</title><link>https://news.ycombinator.com/item?id=15355085</link><guid isPermaLink="false">urn:hackerpapers:mention:1709.02753:15355085</guid><pubDate>Thu, 28 Sep 2017 06:26:29 GMT</pubDate><description>&lt;p&gt;Apple still needs data to build these locally running models. They advertise differential privacy as a solution for that but researchers aren&amp;#x27;t impressed (https://arxiv.org/pdf/1709.02753.pdf). Meanwhile on Android you can opt for a different photo gallery app, giving Google _nothing_ to work with, while on iOS you&amp;#x27;re stuck with whatever Apple allows you to use.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Privacy Loss in Apple's Implementation of Differential Privacy on MacOS 10.12 — HN submission</title><link>https://news.ycombinator.com/item?id=15224312</link><guid isPermaLink="false">urn:hackerpapers:submission:1709.02753:15224312</guid><pubDate>Tue, 12 Sep 2017 02:34:06 GMT</pubDate><description>&lt;p&gt;Privacy Loss in Apple&amp;#x27;s Implementation of Differential Privacy on MacOS 10.12&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;180 points; 39 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1709.02753/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
