uBlock Origin is no longer available on Chrome web store

Status of uBlock Origin on Chrome

  • Original Reddit post showed a screenshot saying “extension is no longer available,” but multiple commenters verify uBlock Origin is still installable from the Chrome Web Store.
  • Chrome shows a warning that it “may soon no longer be supported” because it doesn’t follow extension “best practices.”
  • Some speculate the screenshot came from Chrome Beta/Dev/Canary where Manifest V2 is disabled earlier.
  • Enterprise policy can keep V2 extensions working until June 2025, but only for managed environments.

Manifest V3, Google, and Ad Blocking

  • Manifest V3 deprecates key capabilities used by uBlock Origin; many say a full port without losing functionality is impossible.
  • Others point to uBlock Origin Lite (MV3) as “good enough” for most, but with limitations: fewer default blocks, opt‑in for stronger blocking, and filter updates controlled via extension updates.
  • Some see MV3 as a security improvement; others call that pretext for weakening user control in favor of Google’s ad business.

Browser Choices and Alternatives

  • Strong push toward Firefox: better uBO support, MV2 still allowed, mobile with extensions, and features like Multi‑Account Containers.
  • Critiques of Firefox: performance lag versus Chromium, discoverability and UX of profiles, built‑in ads/telemetry concerns, and Windows taskbar/profile issues.
  • Brave: built‑in ad blocker unaffected by MV3; claims it will keep supporting some privacy MV2 extensions, but skepticism that a Chromium fork can resist upstream long‑term.
  • Other options mentioned: PaleMoon (older uBO), Orion (WebKit with Chrome/Firefox extensions), Zen Browser, Edge, Safari with DNS‑level blockers.

Why People Care About Ad Blocking

  • Many treat ad blockers as essential security: history of ad-network malware and bank‑credential hijacking.
  • Ads and tracking seen as major attention drains, especially for people with ADHD, screen-reader users, and those with migraines; cookie banners and AI chat popups are singled out.
  • Some argue ads are merely a nuisance, not a “public danger”; others counter with privacy, profiling, malware risk, and resource usage.

Technical and Ecosystem Concerns

  • Router/DNS‑level blocking can’t fully replace uBO because many filters depend on page context and CSS/HTML.
  • Ideas floated: local TLS‑inspection proxies and “shadow browser” renderers, with pushback that TLS interception itself is a big security risk.
  • Frustration that Chromium’s control over standards and extension APIs leaves users dependent on a few engines; calls to move to Firefox or future alternative engines.