The post points to Chrome’s long-running Manifest V2 shutdown reaching its final stage. In plain terms, Chrome is removing the extension capabilities that let tools like uBlock Origin inspect and block requests dynamically. Manifest V3 does not kill all blockers, but it does force them into a narrower model, which is why uBlock Origin Lite exists and why many people still say it is not the same product. That distinction drove most of the reaction. People were not confused about the technical mechanism. They were angry at the incentives behind it. The dominant read was simple: Google sells ads, so of course it eventually constrained the best ad blocker on the dominant browser engine.
A lot of the conversation then turned practical. Many said this was the last push they needed to move daily browsing to Firefox, while keeping Chrome or another Chromium browser around only for the stubborn sites that still break elsewhere. Others pushed back that this migration story is too neat. They said Firefox still loses on some mix of performance, battery life,
WebGL or canvas-heavy apps, devtools, tab/session handling, and plain site compatibility, especially for banking, government, Google properties, and certain enterprise apps. The net effect was not “everyone should switch immediately.” It was that Chrome’s moat is less about love and more about lock-in, defaults, and a web built around Chromium behavior.
The useful technical clarification was that “
MV3” itself is not the whole story. Firefox supports Manifest V3 while keeping the blocking
WebRequest capability that serious blockers need. Chrome’s choice to steer extensions toward
declarativeNetRequest is what narrows ad blockers. That is why comments kept separating “Firefox with MV3” from “Chrome with MV3.” People also drew a line between browser-level blocking and weaker substitutes.
DNS tools like
Pi-hole or
AdGuard Home help, but they cannot do cosmetic filtering or robust
DOM-level cleanup. Local proxy approaches can recover some network filtering, but not the full in-page behavior that makes uBlock Origin so effective.
The sharpest non-consumer point came from security and enterprise users:
MV2 was not just an ad-blocking story. It enabled classes of browser security controls that regulated environments and enterprise products relied on. In that framing, Chrome is not merely simplifying extensions. It is moving power away from user-controlled tooling and toward Google-controlled browser and enterprise features. That made the change look less like cleanup and more like centralization.
Mood-wise, this was hostile toward Google, appreciative but wary toward Firefox, and skeptical of Chromium forks that promise to hold the line. Brave got the most credit because it has a built-in blocker and has publicly said it can preserve limited MV2 support for a small set of extensions. Vivaldi was treated as trying, but likely constrained by how much upstream Chromium work it can realistically carry. Orion and Helium got attention as alternatives, but the comments around Orion in particular were full of caveats about stability, missing platform support, and misleading claims about where uBlock Origin actually works. The bottom line people landed on was not that one perfect replacement has arrived. It was that browser choice now hinges on who controls the engine and whether they see content blocking as a feature or as damage to their business.