<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Information Leaks via Safari's Intelligent Tracking Prevention · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2001.07421/</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/2001.07421/feed.xml" rel="self" type="application/rss+xml" /><item><title>Information Leaks via Safari's Intelligent Tracking Prevention — mentioned by codezero</title><link>https://news.ycombinator.com/item?id=22128754</link><guid isPermaLink="false">urn:hackerpapers:mention:2001.07421:22128754</guid><pubDate>Thu, 23 Jan 2020 16:20:43 GMT</pubDate><description>&lt;p&gt;The PDF of the findings is here: https://arxiv.org/pdf/2001.07421.pdf The way the anti-tracking is worked around is to... use the anti-tracking very intentionally. It&amp;#x27;s pretty clever. Apparently Apple has addressed a number of the techniques, but I&amp;#x27;m sure more will surface. The incentives for the adtech industry to find workarounds is huge, and always has been, I have a feeling it&amp;#x27;ll continue to be a game of whack-a-mole. Also, as a nerdy aside, looking at the resources on the PoC pages, this work looks to have been done in July of last year.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2001.07421/"&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>Information Leaks via Safari's Intelligent Tracking Prevention — mentioned by arkadiyt</title><link>https://news.ycombinator.com/item?id=22120472</link><guid isPermaLink="false">urn:hackerpapers:mention:2001.07421:22120472</guid><pubDate>Wed, 22 Jan 2020 18:32:07 GMT</pubDate><description>&lt;p&gt;Here&amp;#x27;s the arxiv paper this article is reporting on, it&amp;#x27;s a short 6 page read: https://arxiv.org/pdf/2001.07421.pdf Basically Safari keeps track of which domains are being requested in a 3rd party context (i.e. I load example.com in my browser and the page loads the facebook sdk - Safari increments a counter for facebook by 1). Once a given domain reaches 3 hits, Safari will strip cookies and some other data in 3rd party requests to that domain. The problem is that advertisers can use this to fingerprint users: register arbitrary domains, make 3rd party requests to them, and detect whether or…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2001.07421/"&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>Information Leaks via Safari's Intelligent Tracking Prevention — HN submission</title><link>https://news.ycombinator.com/item?id=22119832</link><guid isPermaLink="false">urn:hackerpapers:submission:2001.07421:22119832</guid><pubDate>Wed, 22 Jan 2020 17:35:12 GMT</pubDate><description>&lt;p&gt;Information Leaks via Safari’s Intelligent Tracking Prevention&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;151 points; 35 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2001.07421/"&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>
