<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>User Tracking in the Post-cookie Era: How Websites Bypass GDPR Consent to Track Users · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2102.08779/</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/2102.08779/feed.xml" rel="self" type="application/rss+xml" /><item><title>User Tracking in the Post-cookie Era: How Websites Bypass GDPR Consent to Track Users — mentioned by 1vuio0pswjnm7</title><link>https://news.ycombinator.com/item?id=33144218</link><guid isPermaLink="false">urn:hackerpapers:mention:2102.08779:33144218</guid><pubDate>Sun, 09 Oct 2022 19:05:51 GMT</pubDate><description>&lt;p&gt;&amp;quot;In some cases, however, these banners can serve as trackers themselves, as they engage in a privacy-breaching data exchange before the user even has a chance to opt out.&amp;quot; See, e.g., https://arxiv.org/abs/2102.08779v1 Blocking the banners, which generally require Javascript to function, is enough to stop consent, but keeping Javascript enabled still enables and/or strengthens the ability to track. No doubt JS is on by default in Brave. Can it be disabled globally for all websites or only on a site-by-site basis. The project was co-founded by the creator of Javascript. There will be people who…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2102.08779/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CY</category></item></channel></rss>
