HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gorhill
uBlock
JavaScript2014–2026
gorhill / uBlock

uBlock

uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.

554Distinct people
875Mentions
11Explicit recommenders
69.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.

GitHub

Where it is used

  • LibreWolf — LibreWolf includes uBlock Origin in the browser. Source
  • Mullvad Browser — Mullvad Browser uses uBlock Origin to block third-party trackers. It includes this extension as part of its tracker-blocking approach. Source

What people are saying

You should look into the homepage linked from there https://github.com/gorhill/uBlock because that's were it's really from, and not some recommendation via. Especially their…

LargoLasskhyfv used a recommendation phrase. 12 indexed comments match. 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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:02:44 AM 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 year875 dated mentions

Observed mentions: 2014-06-24 09:19:53 UTC to 2026-10-13 19:36:47 UTC.

0501002014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 24 mentions; 4 submissions, 20 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 127 mentions; 13 submissions, 114 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 70 mentions; 3 submissions, 67 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 53 mentions; 2 submissions, 51 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 67 mentions; 2 submissions, 65 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 59 mentions; 4 submissions, 55 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 76 mentions; 3 submissions, 73 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 85 mentions; 5 submissions, 80 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 92 mentions; 7 submissions, 85 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 99 mentions; 9 submissions, 90 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 52 mentions; 3 submissions, 49 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 45 mentions; 2 submissions, 43 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 26 mentions; 0 submissions, 26 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC24420
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC12713114
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC70367
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC53251
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC67265
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC59455
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC76373
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC85580
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC92785
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC99990
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC52349
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC45243
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC26026

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
uBlock Origin (uBO) Browser Install from ... Status Firefox Add-ons uBO works best on Firefox Edge Add-ons "Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3": "Beginning in August 2026, Microsoft Edge will start the consumer transition away from Manifest Version 2 (MV2) extensions and toward MV3. Our goal is to complete the consumer transition by the end of 2026, with enterprise deprecation following in early 2027." Opera Add-ons Removed "Manifest V2 support timeline": "Aug 31st 2026: All remaining Manifest V2 extensions removed from the Chrome Web Store" About Google Chrome's "This extension may soon no longer be supported" Thunderbird Add-ons No longer updated and stuck at 1.49.2. Later versions require "GitHub - Releases". GitHub - Releases Stable and development versions on Firefox, Chromium MV2, and Thunderbird. Must be placed manually into web browsers; the Chromium and Thunderbird versions usually won't auto-update. Related: uBlock Origin Lite uBlock Origin (uBO) is a CPU and memory-efficient wide-spectrum content blocker for Chromium and Firefox. It blocks ads, trackers, coin miners, popups, annoying anti-blockers, malware sites, etc., by default using EasyList, EasyPrivacy, Peter Lowe's Blocklist, Online Malicious URL Blocklist, and uBO filter lists. There are many other lists available to block even more. Hosts files are also supported. uBO uses the EasyList filter syntax and extends the syntax to work with custom rules and filters. You may easily unselect any preselected filter lists if you think uBO blocks too much. For reference, Adblock Plus installs with only EasyList, ABP filters, and Acceptable Ads enabled by default. It is important to note that using a blocker is NOT theft. Do not fall for this creepy idea. The ultimate logical consequence of blocking = theft is the criminalization of the inalienable right to privacy. Ads, "unintrusive" or not, are just the visible portion of the privacy-invading means entering your browser when you visit most sites. uBO's primary goal is to help users neutralize these privacy-invading methods in a way that welcomes those users who do not wish to use more technical means. Documentation Installation Firefox Chromium Thunderbird All Programs Enterprise Deployment Release History Translations About Documentation Basic Mode Advanced Mode The simple popup user interface for an install-it-and-forget-it type of installation that is configured optimally by default. The advanced popup user interface includes a point-and-click firewall that is configurable on a per-site basis. Visit the Wiki for documentation. For support, questions, or help, visit /r/uBlockOrigin. Installation Required Permissions Firefox Firefox Add-ons Development Builds uBO works best on Firefox and is available for desktop and Android versions. Chromium Chrome Web Store: Removed on 2026-08-31 Microsoft Edge Add-ons (Published by Nicole Rolls until version 1.62. Ownership transfer at version 1.64.) Opera Add-ons uBO should be compatible with any Chromium-based browser. Thunderbird Thunderbird Add-ons In Thunderbird, uBlock Origin does not affect emails, just feeds. All Programs Do NOT use uBO with any other content blocker. uBO performs as well as or better than most popular blockers. Other blockers can prevent uBO's privacy or anti-blocker-defusing features from working correctly. Manual Installation Enterprise Deployment Deploying uBO Release History Releases Page Translations Help translate uBO via Crowdin. About Manifesto Privacy Policy GPLv3 License Free. Open-source. For users by users. No donations sought. If you ever want to contribute something, think about the people working hard to maintain the filter lists you are using, which are available to use by all for free.
Read the full README on GitHub

What Hacker News says

127 sources
The fix works only for Firefox-based browsers, because it makes use of inline script tag filtering[1] which does not work on chromium, because it does not support `beforescriptexecute`[2]. The work around for Chromium-based browsers is to wholesale block inline script for the page, at the cost of probably breaking some functionality on the page. [1] https://github.com/gorhill/uBlock/wiki/Inline-script-tag-fil... [2] https://code.google.com/p/chromium/issues/detail?id=168175
In Show HN: FuckFuckAdblock
> I block their Scripts, only temporarily allow if I need them, I don't keep cookies for longer than my current session except for Fastmail, I use VPN, have no DNS-Leak and WebRTC Detection turned off (last I checked you could not turn WebRTC Detection off in Chrome and the Extensions promising to do that were not working). It's been possible to disable multiple webrtc routes since M42[1]. uBlock exposes this option as a checkbox in its main settings. > And that's also why I use Mozilla Firefox. Not because it's the technically better browser, but I have trust in Mozilla and their API just allows capabilities Chrome isn't capable of (that's why there is no NoScript in Chrome and no, there is no NoScript-Alternative in Chrome with the same features and capabilities, look it up). The only thing Chrome/Chromium cannot block are inline scrip
Read the rest
t tags[2]. Inline script tags should apparently be considered cosmetic filtering according to [2]. Other than the above exception you can pretty close to blocking everything you could in Firefox with uBlock[3]/uMatrix[4]. Unless you're referring to something else? With uMatrix you can get basically the same granularity that you can with NoScript just in a much nicer looking interface (which is available for Firefox now as well). > Back when I used both Chrome and Firefox side by side, Firefox for example would turn off some Add-Ons/Extensions in Private Browsing Mode, while Chrome would not. I guess we all can grasp what most likely was the reason for it (Add-Ons/Extensions should not be able to obtain information from the user if in private browsing). Chrome extensions will by default NOT be allowed in incognito mode. I don't know what you observed but you must have explicitly allowed this behavior. [1] https://code.google.com/p/chromium/issues/detail?id=457629 [2] https://github.com/gorhill/uBlock/wiki/Inline-script-tag-fil... [3] https://github.com/gorhill/uBlock [4] https://github.com/gorhill/uMatrix
In Popular Google Chrome extensions are constantly tracking you by default
> I immediately found a few potential tracking issues with its default lists I am curious: what are these "few potential tracking issues" specifically? Whatever default lists uBO is using, unlike with ABE (which is essentially ABP filtering engine), users have the last words in what is blocked: - The `important` filter option can be used to override exception filters.[1] - Dynamic filtering override all static filters.[2] For example, you do not need a special filter list to block Facebook everywhere, it's a matter of a few point-and-click to block it everywhere without any way for any static filter to counter it.[3] * * * [1] https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#... [2] https://github.com/gorhill/uBlock/wiki/Overview-of-uBlock's-... [3] https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-to...
In Firefox Now Offers a More Private Browsing Experience

Showing the 15 most recent of 127 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.