HN Debrief

Firefox is now the last major browser that still supports uBlock Origin

  • Browsers
  • Privacy
  • Security
  • Open Source
  • Developer Tools

The article argues that Firefox has become the last major browser where the original uBlock Origin still works as designed, because Google’s Manifest V3 changes cut off the older extension APIs that made full network-level filtering possible in Chrome and Chromium-based browsers. That lands as more than a niche extension story. People read it as a visible example of what happens when the browser market converges on an ad company’s engine and extension model.

If ad blocking, privacy tooling, or extension flexibility matter to your users or employees, test your stack on Firefox now instead of assuming Chromium is the whole web. Also stop treating uBlock Origin Lite as a drop-in equivalent to full uBlock Origin if your workflow depends on per-site controls or stronger filtering.

Discussion mood

Mostly pro-Firefox and anti-Chromium consolidation. People were pleased that Firefox still supports full uBlock Origin and saw it as rare user-aligned differentiation, while frustration centered on Google’s influence over browser APIs, worsening ads, and the shrinking room for powerful extensions.

Key insights

  1. 01

    Mozilla manually reviews top extensions

    Firefox’s advantage here is not just that uBlock Origin still runs. Mozilla also puts recommended extensions through recurring technical review, including checks on updates, which commenters framed as a meaningful defense against the common pattern where a trusted extension is sold and later turned malicious. That makes Firefox’s extension story stronger than “more power for add-ons” because it pairs power with at least some human scrutiny.

    If you standardize on browser extensions inside a company, look at the review and update process as closely as the feature list. Firefox’s recommended extension program gives security teams a cleaner shortlist than the open extension stores on most Chromium browsers.

      Attribution:
    • GeekyBear #1
    • big_toast #1
    • elashri #1
    • gurjeet #1
  2. 02

    uBO Lite misses workflow-critical controls

    The practical gap between full uBlock Origin and the Lite version is not just obscure filter syntax. Commenters called out concrete losses like no per-domain toggling and weaker cosmetic cleanup, which makes debugging your own sites more annoying and leaves obvious ad placeholders behind on some pages. For developers and power users, that changes the tool from precise instrument to blunt compromise.

    If your team uses ad blockers while building or QA testing web apps, verify that your browser setup still allows site-specific disable rules and predictable page rendering. Otherwise you will lose time chasing false positives or miss layout issues hidden by weaker blockers.

      Attribution:
    • jimrandomh #1
    • fsflover #1
    • sys_64738 #1
  3. 03

    Manifest V3 solves the wrong layer

    The strongest technical critique was that Manifest V3 narrows one attack surface without fixing the bigger one. Blocking direct network inspection sounds safer, but malicious extensions can still read page content, steal form data, and manipulate the DOM. So the result is less capability for trusted tools like uBlock Origin, while the underlying extension trust problem largely remains. What people actually want is a browser permission model that can grant high trust to a few tools without giving every add-on the keys to everything.

    Treat extension security claims around Manifest V3 with caution. If you care about both safety and powerful tooling, push for finer-grained permissions and internal extension allowlists rather than assuming reduced API surface alone meaningfully solves the risk.

      Attribution:
    • matheusmoreira #1
    • codedokode #1
    • michaelt #1
    • lxgr #1 #2
    • Gigachad #1
    • underlipton #1
  4. 04

    Chromium holdouts look temporary

    Brave, Vivaldi, and in some cases Edge complicate the headline, but commenters did not see them as stable long-term answers. Brave requires special paths and also ships its own ad blocker. Vivaldi explicitly says its Manifest V2 extension support is re-enabled only for the time being. The key point is cost. Any Chromium browser that keeps old extension behavior now has to carry and maintain that divergence itself.

    Do not base a long-lived browser policy on temporary Chromium exceptions. If full extension power is strategic for your users, assume the maintenance burden will eventually force smaller Chromium vendors to converge back toward upstream constraints.

      Attribution:
    • eahm #1
    • LeoPanthera #1
    • Aldo_MX #1
    • hackernud3s #1
    • ipsum2 #1
    • rasz #1
    • rwz #1

Against the grain

  1. 01

    Most users will find Lite sufficient

    For ordinary browsing, several people said uBlock Origin Lite blocks enough ads that the difference is barely noticeable day to day. The missing features become visible mainly to developers, tinkerers, or people who need fine-grained site controls. That weakens the idea that Firefox will win a mass migration purely on this issue.

    Do not assume ad-blocking differences alone will move mainstream users. If you want people off Chromium, you need a migration pitch that includes visible everyday benefits beyond extension internals.

      Attribution:
    • ivraatiems #1
    • jimrandomh #1
    • ImJamal #1
    • Andrex #1
  2. 02

    Mozilla’s privacy trust is not clean

    Some commenters rejected the idea that Firefox is the obvious privacy-safe choice. They pointed to telemetry, Mozilla’s terms-of-use controversy, and broader distrust of the company’s direction. That does not erase Firefox’s extension advantage, but it means many privacy-conscious users now separate “better for uBlock Origin” from “fully trusted vendor.”

    If you recommend Firefox on privacy grounds, be specific about what you mean. Its browser architecture and extension support may be preferable, but you should still review telemetry defaults and policy changes instead of treating the brand as automatically aligned with your threat model.

      Attribution:
    • Madmallard #1
    • einpoklum #1
    • shooly #1
  3. 03

    Chromium still has security advantages

    One dissenting line held that Chromium’s tighter extension constraints and broader security posture make it the safer base even if it is less friendly to blockers. From that view, Firefox is winning on user freedom while losing on hardening and vendor priorities. That reframes the trade as capability versus security engineering, not simply users versus ads.

    Security teams should resist framing this as a one-dimensional choice. Compare browser sandboxing, update cadence, extension controls, and enterprise policy support alongside ad-blocking capability before you standardize.

      Attribution:
    • odidiejdiwjd #1
    • armadyl #1

In plain english

Chromium
The open-source browser project that underlies Google Chrome and many other browsers such as Edge, Brave, and Vivaldi.
DOM
Document Object Model, the browser’s in-memory representation of an HTML page that JavaScript can read and modify.
Manifest V2
An older Chrome and Chromium browser extension format that allowed more powerful blocking behavior than the newer Manifest V3 system.
Manifest V3
A newer browser extension system from Google that restricts how blockers work and pushes them toward declarative rules.
telemetry
Data sent automatically from a remote device back to a receiver or server.
uBlock Origin
A browser extension that blocks ads, trackers, and unwanted page elements.
uBlock Origin Lite
A lighter version of uBlock Origin built around newer browser extension limits, especially the declarative model used by Manifest V3.

Reference links

Mozilla extension review and policy

uBlock capability differences

Alternative browser support status

Privacy and telemetry references

Related discussions and alternatives