HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
r4vi
block-the-eu-cookie-shit-list
Clojure2012–2022
r4vi / block-the-eu-cookie-shit-list

block-the-eu-cookie-shit-list

Adblock / Adblock plus filter list for blocking cookie notifications

10Distinct people
16Mentions
1Explicit recommenders
295GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Adblock / Adblock plus filter list for blocking cookie notifications

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

This one works well for me: https://github.com/r4vi/block-the-eu-cookie-shit-list

ghba66 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2012-09-05 11:34:07 UTC to 2022-01-24 22:54:30 UTC.

02462012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC707
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

16 sources
There are several blocklists specifically curated to adress the EU cookie nag: http://prebake.eu/ https://www.i-dont-care-about-cookies.eu/ https://github.com/r4vi/block-the-eu-cookie-shit-list AFAIK some prominent cookie notices are also part of the Fanboy Annoyances list: https://easylist.to/ The only prominent nags that are not very well targeted with those lists are in webapps like reddit mobile. Primarily because of their dynamic, non-descriptive ids.
In Facebook Container for Firefox
One thing about this, is that I don't particularly want an ad-blocker per se: I want a malicious-or-annoying-stuff blocker. So I primarily use Privacy Badger, which dynamically blocks sites that try to track me (and gives me an excuse to rail against sites that tell me I'm running an ad-blocker, because I'm not running an ad-blocker!) and self-destructing cookies to stop first-party tracking on sites I don't trust. The down-side of self-destructing cookies being the EU cookie regulation, which relies on sites setting a cookie to tell me that I have to agree to set cookies, when I've actually configured my browser to do what I want with the cookies anyway. So then I need an ad-blocker set up specifically to block the cookie panels (with https://github.com/r4vi/block-the-eu-cookie-shit-list) which requires me to have an ad-blocker installe
Read the rest
d after all, even if it's not set to block ads...
In Show HN: Let's encourage ad blocking
I've been using a different filter list[1] for more than a year, and it's really useful as I already use self-destructing-cookies[2] to exercise control over which cookies my browser will remember, meaning that pretty much all sites think I've never visited before and therefore try to annoy me with their cookie banner. [1]: https://github.com/r4vi/block-the-eu-cookie-shit-list [2]: https://addons.mozilla.org/en-GB/firefox/addon/self-destruct...
In Prebake: Block EU Cookie Notices with Adblock
If there are already so many ways to fingerprint via cookies, JavaScript, Flash, etc. that it probably doesn't matter then why do cookies matter? That the EU parliament decided to pass some weird law is not much of an argument. They're not exactly known for their technological proficiency. And it did nothing for privacy. It only annoys people[1]. Sure, we could start with cookies. However, that would break a lot of the web with no immediate benefit. On SSL everywhere (not "anywhere"), how much resources does it cost to negotiate SSL/TLS with every single smartphone in their area? Supposedly, not much[2]. I run https websites on an Atom server. Frankly, that was rather unconvincing. Although it does seem likely than the entire process was driven by IETF trying to stay politically relevant in the face of SPDY. [1] https://github.com/r4vi/bl
Read the rest
In HTTP/2.0 — Bad protocol, bad politics

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.