HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
uBlockOrigin
uBlock-issues
Security & Privacy2018–2026
uBlockOrigin / uBlock-issues

uBlock-issues

This is the community-maintained issue tracker for uBlock Origin

Security & Privacy
Explore on GitHubRead Hacker News discussions
93Distinct people
110Mentions
1Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is the community-maintained issue tracker for uBlock Origin

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I can't provide a source for Google axing a too-invasive extension, because they've never been straightforward about it. My favorite excuse was that the extension's description…

stonogo 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

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, 4:01:40 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 year110 dated mentions

Observed mentions: 2018-10-25 03:16:40 UTC to 2026-09-15 09:50:47 UTC.

01020302018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 32 mentions; 6 submissions, 26 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 18 mentions; 2 submissions, 16 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 25 mentions; 4 submissions, 21 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC110
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC32626
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC18216
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC14014
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC25421
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC505
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC716
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC606
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

From the project README

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

Read the project’s introduction
uBlock Origin (uBO) Issues This repository is the official community-maintained issue tracker for uBO. Support Forum For support, questions, or help, visit /r/uBlockOrigin. Filter List Issues Report issues with filter lists or broken website functionality in the uAssets issue tracker. uBO Lite (uBOL) Issues Report issues specific to the Manifest Version 3 (MV3) variant in the uBOL issue tracker. Localization issues Language translations are handled at Crowdin: https://crowdin.com/project/ublock Performance Issues Speculated performance issues are marked as invalid and closed if they do not come with actual profiling data from the Firefox Profiler (or Firefox Profiler for Chromium) and a fully substantiated analysis supporting the claim. WebRTC Issues Do not open issues about WebRTC leaking local IP addresses. Supported modern browsers do not cause undue local IP address leaks through WebRTC. uBO is not a VPN/proxy tool. If you are experiencing such an issue, report it to the browser or VPN/proxy tools software provider or, if needed, both. Filter List Requests New filter list requests are not permitted and will be declined and closed. uBO Development Builds Use the development builds to help report issues and regressions before the next stable release. Once you install a development build, it will automatically update when a new version is published. Chromium: Click the most recent uBlock0_[version].chromium.crx file from the uBO Releases page. Firefox: Click the most recent uBlock0_[version].firefox.signed.xpi file from the uBO Releases page. Thunderbird: Download the most recent uBlock0_[version].thunderbird.xpi file from the uBO Releases page, then drag-n-drop it into Thunderbird's Add-ons Manager pane (Thunderbird 91+ required).
Read the full README on GitHub

What Hacker News says

18 sources
bad_user·Sep 6, 2020
Serving ads or doing tracking from random URLs doesn't work with extensions like uBlock Origin. In Firefox, uBO can block first party domains: https://github.com/uBlockOrigin/uBlock-issues/issues/780 Also domain or URL blocking isn't the only thing you can do. You can also ban scripts from the page, or monkey patch JavaScript to change behavior that ad networks rely on. And you can also do cosmetic ads blocking, to hide elements from the page, via user stylesheets. It's no wonder that Google is deprecating the APIs uBlock Origin relies on, in Manifest v3 ;-) Fact of the matter is Google is now engaged in war against ad-blocking.
In Google proposed Web Bundles could threaten the Web as we know it
Fej·Aug 21, 2020
uBlock Origin is already a bit nerfed on Chrome, and will likely be completely gone in the near future. That's Firefox's killer app for "regular" users, and power users too. It's a matter of getting the word out. Mozilla likely won't outright bundle its features as to not completely alienate Google, since they are their main source of revenue, but seem to be okay with promoting it otherwise, as it is on the front page of addons.mozilla.org and was the first extension (and the only one, for a time, and still only one of nine) supported in the new Firefox for Android. There are also "normal" users who do not care about blocking ads and tracking, or do not know about the performance issues, malware risk, and other reasons for using a blocker and have not made such a decision, trusting the browser to act in the best interest of the user. (We
Read the rest
know that last bit doesn't work anymore.) (Regarding uBlock Origin, gorhill has expressed that he will not neuter the extension to work with Chrome's API change, reference: https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss... )
In Why Did Mozilla Remove XUL Add-Ons?
AaronFriel·May 13, 2020
Chrome's Extension v3 API will remove the ability for uBlock Origin to filter web requests in code, instead the application will have to submit a list of URLs to filter to an internal API and this list has a maximum size and limits the flexibility of the URL filtering. See the uBlock Origin author's post: https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss... This is ironic, because uBlock implements an extremely efficient filter and is even looking into using WASM to speed it up even more. Google's public position is that implementing functionality in JS or WASM is unacceptably slow. They say "[Preventing or weakening ad blockers] is absolutely not the goal. In fact, this change is meant to give developers a way to create safer and more performant ad blockers."[1] Google's public position is also that WASM is "consistently fast"
Read the rest
[2], fast enough to rewrite Google Earth to target it[3], and "It's entirely feasible to build a complex code-base to run performantly in the browser using WebAssembly"[4]. So which is it? Is the Web Request API being deprecated because it's not possible to write performant code in extensions using Chrome's powerful JS and WASM engine, or is it possible but there might be some other, different reason that they're blocking it? [1] https://blog.chromium.org/2019/06/web-request-and-declarativ... [2] https://developers.google.com/web/updates/2019/02/hotpath-wi... [3] https://blog.chromium.org/2019/06/webassembly-brings-google-... [4] https://developers.google.com/web/updates/2018/08/wasm-av1#f...
In Let's guess what Google requires in 14 days or they kill our extension

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