Google pulls the plug on uBlock Origin

Original Article ↗ Hacker News Discussion ↗

Google’s deprecation of Manifest V2 in Chrome, which effectively breaks the full version of the uBlock Origin ad blocker for over 30 million users, is prompting intense concern over privacy, security, and control of the browsing experience. Commenters argue that Manifest V3 cripples powerful content blockers and many other extensions, pushing people toward alternative browsers like Firefox, Brave, Vivaldi, or Firefox-based forks with built‑in or bundled blocking. Others explore workarounds such as enterprise policies, DNS‑level blocking, or local proxies, while warning that tying extension capabilities to an ad-funded browser vendor creates a deep conflict of interest.

Reactions to Google Disabling uBlock Origin on Chrome

  • Many commenters say this confirms their decision to keep or switch to Firefox or other non-Chrome browsers.
  • Several state they will not use the web without a strong ad blocker and will abandon any browser that weakens ad blocking.
  • Some frame this as a core usability/security feature, comparable to removing the back button.

Manifest V3 and uBlock Origin Lite

  • uBlock Origin Lite is described as MV3-compliant but significantly less capable: no dynamic filters/scriptlets, limited heuristics, and filter lists only updatable via extension updates controlled by Google.
  • Concern that YouTube and “bait URL” anti–ad-block techniques can’t be countered effectively under MV3.
  • Some users with basic needs report seeing little practical difference; others emphasize that limitations will show up on more adversarial or complex sites.
  • Enterprise/managed-policy flag (ExtensionManifestV2Availability) can delay MV2 removal until June 2025 for some users.

Browser Choices and Built‑In Ad Blocking

  • Alternatives mentioned: Firefox, LibreWolf, Orion, Vivaldi, Opera, Brave, Edge, future projects like Ladybird.
  • Firefox praised for continuing MV2 support, containers, and extensibility, though some distrust its dependence on Google funding.
  • Several want ad blocking baked into the browser “guts” rather than via extensions; Vivaldi and Brave are cited as examples with built-in blockers.

Ad Blocking, Funding Models, and Adoption

  • Many find today’s ad-heavy web unusable, especially for less technical or elderly users at risk of scams.
  • Debate over how many people actually use ad blockers; some claim 30–50%, others argue actual usage is far lower based on Chrome/uBO numbers.
  • Discussion of non-ad funding models: paid services, government-funded services, non-profits, and hobbyist-supported sites.

Security, Extensions, and Workarounds

  • Some welcome MV3’s restrictions on remote code as protection against malicious extensions; others call this threat overstated and note Google’s review is imperfect.
  • Manifest V3 is criticized for breaking many long-tail extensions whose authors may never update them.
  • Suggested workarounds include DNS-level blocking (e.g., Pi-hole), local proxies (e.g., privoxy), and eventually forking or replacing Chromium.