HN Debrief

Google Chrome update will close the door on ad blockers

  • Browsers
  • Privacy
  • Open Source
  • Antitrust
  • Developer Tools

The article says Chrome 150 and 151 will finish the long-announced removal of Manifest V2, the old extension model that full-strength blockers like uBlock Origin depended on. In practice that means Chrome users lose the original uBlock Origin and get pushed toward Manifest V3 tools like uBlock Origin Lite, which use Google's newer extension rules and are broadly seen as less capable. A lot of people pointed out that this is not a sudden cutoff. Chrome has been marching toward this for years, many users already got moved, and some commenters said they barely noticed because uBO Lite still blocks most visible ads in normal browsing.

If ad blocking and browser independence matter to your team, stop treating Chrome as the default and test a migration path now, especially for managed devices and nontechnical users. Also separate the short-term question of 'will ads still be blocked for me this week' from the strategic one of whether Google should control the only browser engine most sites optimize for.

Discussion mood

Mostly hostile toward Google and pessimistic about Chromium monoculture. People were angry that an ad company is narrowing browser control in ways that weaken advanced blocking, while also conceding that MV3 blockers are good enough that many mainstream users will not notice and therefore will not switch.

Key insights

  1. 01

    What disappears is privacy control

    The missing capability is not just cosmetic ad removal. Full blockers used MV2 to inspect and alter requests in real time, strip tracking parameters, and apply site-specific logic before the browser loaded junk. Under MV3, commenters said that kind of programmatic URL manipulation and deeper privacy filtering becomes much harder or impossible, so a browser can still look clean while leaking more data and giving users less control.

    Do not evaluate blocker quality by whether pages 'look ad free.' If privacy or security matters, test whether your setup still strips trackers and blocks background requests, not just whether it hides banners.

      Attribution:
    • kgwxd #1
    • anal_reactor #1
    • krackers #1
  2. 02

    Brave buys time, not independence

    Built-in blocking and hosting a few preserved MV2 extensions may keep Brave usable for now, but commenters framed that as a maintenance strategy, not an escape hatch. A Chromium fork can patch around today's breakage, yet it still depends on an upstream controlled by the company creating the restrictions. That means every future Google change becomes technical debt for Brave and anyone betting on Chromium forks as the long-term answer.

    If you choose Brave or another Chromium fork, treat it as a temporary mitigation and watch upstream changes closely. For long-horizon browser strategy, engine diversity matters more than this quarter's ad-blocking workaround.

      Attribution:
    • throwatdem12311 #1
    • jrm4 #1
    • arecsu #1
  3. 03

    Firefox tradeoffs are now narrower

    When people named concrete reasons to stay on Chromium, they were mostly edge features and workflow details, not basic browsing quality. The recurring examples were Web USB, Web NFC, desktop Progressive Web App support, Chrome devtools, tab behavior, and some UI sluggishness or memory complaints. That narrows the decision. For many users, the blocker difference now outweighs the feature gap, but teams with hardware, embedded, or heavy web app workflows may still hit real friction.

    Audit the specific browser capabilities your org actually depends on before pushing a switch. If your stack needs Web USB, advanced devtools, or desktop Progressive Web Apps, plan exceptions instead of assuming every Chrome user can move painlessly.

      Attribution:
    • ldom66 #1
    • mschuster91 #1
    • barnabee #1
    • dunham #1
  4. 04

    Mozilla distrust is real but secondary

    A lot of commenters still dislike Mozilla's leadership, spending, product decisions, and dependence on Google money. Even so, that criticism did not translate into a strong pro-Chrome case. The practical conclusion was that you can dislike Mozilla and still prefer Firefox, or a Firefox-based fork, because the strategic problem is Google's leverage over the dominant engine, not whether Mozilla is an admirable institution.

    Do not let dissatisfaction with Mozilla collapse into acceptance of Chromium dominance. If governance is your concern, compare Firefox, LibreWolf, Waterfox, and similar forks instead of defaulting back to Chrome.

      Attribution:
    • maxloh #1
    • glenstein #1
    • joe_mamba #1
    • SwamyM #1
  5. 05

    Network-level blocking is only partial cover

    DNS and host-file blocking came up as a fallback, but commenters were blunt that it cannot replace application-layer filtering. Many sites now serve ads from the same domains as real content, and element-level cleanup or per-URL blocking is impossible at the DNS layer. That makes Pi-hole, AdGuard Home, and private DNS useful first lines of defense, not substitutes for a capable browser blocker.

    Layer your defenses. Use DNS blocking for broad coverage across devices, but keep a browser-level blocker anywhere you care about fine-grained filtering, page cleanup, or anti-tracking.

      Attribution:
    • MrDrMcCoy #1
    • drdexebtjl #1
    • dbpc #1
  6. 06

    Distribution power keeps deciding browser share

    Several commenters tied this story to antitrust and defaults rather than pure product quality. One argument was that browser choice screens or other distribution remedies could have mattered more than endless debate about Mozilla's product decisions, because Chrome's position is reinforced by preinstall and ecosystem defaults. The point was not that Firefox would suddenly win, but that competition in browsers has been shaped by distribution power for years.

    If you work on policy, enterprise IT, or platform deals, focus on defaults and distribution contracts as much as product features. Browser competition will not recover on technical merit alone while one stack owns the default path.

      Attribution:
    • glenstein #1
    • markstos #1
    • casefields #1

Against the grain

  1. 01

    MV3 is good enough for most people

    For many everyday users, uBlock Origin Lite and other MV3 blockers still remove almost all visible ads and keep browsing tolerable. These commenters were not defending Google's motives. They were pointing out that the practical pain is often overstated for normal browsing, which helps explain why Chrome can make this change without triggering a mass exodus.

    Do not assume users will switch browsers just because the technical ceiling got lower. If you want migration to happen, you need a clearer user-facing benefit than abstract claims about lost capability.

      Attribution:
    • flohofwoe #1
    • colechristensen #1
    • twostorytower #1
    • ApolloFortyNine #1
  2. 02

    Chrome's original goal was distribution cost

    One commenter pushed back on the idea that Chrome was born as an ad-control plot from day one. The claim was that Chrome initially helped Google reduce traffic acquisition costs by shifting users away from browsers owned by companies it had to pay for search defaults. The ad-control incentives came later, once browser dominance was already secured.

    When modeling competitor behavior, separate original strategy from what market power enables later. Products often begin as distribution plays and only become control points after they win.

      Attribution:
    • siren2026 #1
    • advisedwang #1
  3. 03

    The headline overstates the immediate breakage

    A few commenters insisted this is old news, not a sudden browser apocalypse. MV2 has been on the way out for years, many users were already migrated, and Chrome still permits ad blocking through MV3 or browser-native approaches like Brave Shields. That does not refute the long-term monopoly concern, but it does undercut the idea that Chrome updates instantly mean 'no more ad blockers.'

    Communicate this issue in two layers. The immediate operational change is limited, while the strategic change in who gets to define browser limits is much bigger.

      Attribution:
    • insanitybit #1
    • Havoc #1
    • charcircuit #1

In plain english

AdGuard Home ↩
A self-hosted network-level ad and tracker blocker that filters DNS requests.
Chromium ↩
The open source browser project that Google Chrome is built on.
DNS ↩
Domain Name System, the internet service that turns site names like example.com into network addresses.
LibreWolf ↩
A privacy-focused Firefox fork that removes or changes some Mozilla defaults.
Manifest V2 ↩
The older Chrome extension platform model that gave extensions broader access to inspect and modify browser requests in real time.
Manifest V3 ↩
The newer Chrome extension platform model that restricts how extensions work, especially by pushing more actions into predefined browser-managed rules.
MV2 ↩
Short for Manifest V2, the older Chrome extension system.
MV3 ↩
Short for Manifest V3, the newer Chrome extension system.
Orion ↩
A browser from Kagi that uses WebKit and emphasizes privacy and compatibility with some browser extensions.
Pi-hole ↩
A network-level blocker that filters ads and tracking domains for devices on a local network.
uBlock Origin ↩
A browser extension that blocks ads, trackers, and other unwanted web content.
uBlock Origin Lite ↩
A reduced-capability version of uBlock Origin designed to comply with Manifest V3 restrictions in Chrome and other Chromium browsers.
uBO ↩
A common shorthand for uBlock Origin.
Waterfox ↩
A Firefox-based browser fork aimed at users who want a different balance of features, privacy settings, and branding from mainstream Firefox.
Web NFC ↩
A browser feature that lets websites interact with Near Field Communication hardware for short-range data exchange.
Web USB ↩
A browser feature that lets websites communicate directly with USB devices.
Zen ↩
A Firefox-based browser fork focused on a different user interface, especially vertical tabs and workspace-style browsing.

Reference links

Browser alternatives and projects

MV3 and ad blocker references

Reporting and background articles

Platform and standards references

Mozilla and policy context