直接上adguard桌面端软件理论上是最优解，但看很多人反馈如果功能开太全会影响体验

这个Manifest V3确实烦，一直用的uBlock Origin，浏览器一直提示即将弃用，就试了下ubo lite，发现功能差太远了，反手删了下回ubo

新版crx + adguardhome就行

对吧，别升级

哪个版本开始影响去广告？我chrome 128下uBlock origin没发现啥不对的么

从 AdGuard 浏览器扩展 5.0.91 版本发布开始，MV3 版本成为 Chrome Web Store 中 Adguard 的主要扩展，换句话讲，原扩展用户将会自动迁移到 MV3 版本。在 MV2 完全不受支持之前，使用 MV2 版本仍然是可能的。

GitHub

Release 5.0.91 · AdguardTeam/AdguardBrowserExtension

The time has come for a big move: the release is out and our trusty ad-blocking extension is now fully compatible with MV3. Let’s take a look at what’s changed.

If you’re already using our extensi...

AdGuard Blog

AdGuard Browser Extension for Chrome MV3: release version

The journey of adapting to Google’s new API Manifest V3 is over and we present you with a new release: Our browser extension for Chrome is now fully functional. Dive in to get the details.

uBlock Origin 开发者拒绝实施类似的自动迁移，因此没有立刻看到 MV3 方面的差异是预期行为。在 MV2 完全不受支持之前，你可能不会受到影响。

---

另一个问题是，AdGuard 和 uBlock Origin 在其 MV3 版本上的哲学是不同的。简单来说，AdGuard 确实尽努力在 MV3 的允许范围内制作一个 MV3 兼容版本，但 uBlock Origin Lite 被实现为声明性内容拦截器，它并不完全是 MV3 兼容版本；顾名思义，这是一个 Lite 版本。

GitHub

Frequently asked questions (FAQ)

uBO Lite home (MV3). Contribute to uBlockOrigin/uBOL-home development by creating an account on GitHub.

news.ycombinator.com

<i>> The name of his new extension, "uBlock Origin Lite", will also not help with adoption.</i><p>Honestly until actually looking at it earlier this year I assumed the Lite version was just a somewhat pared down version but people should really look at the screenshots[1]. It's <i>painfully</i> mocking of the change with an intentionally kids-drawing-like UI and seemingly zero...

Springtime —
5:47 PM - 31 May 2024

如果你关心的只是有效的广告拦截，在支持 MV3 的浏览器扩展的前提下，前者可能是更好的选择。

大佬桌面版怎么配置，我桌面版和插件一样的规则，桌面版的体验就会卡

谷歌改插件就是为了消灭这些广告拦截器，因为影响它的利润了

Firefox 我记得是明确说要保留 MV2 的

Well what’s happening with MV2 you ask? Great question – in case you missed it, Google announced late last year their plans to resume their MV2 deprecation schedule. Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.