AdGuard publishes the first ad blocker built on Manifest V3

Post by cycomanic » Tue, Aug 30, 2022, 1:38 PM UTC

chrismorgan wrote: post #92

gnomewascool wrote: post #51

Earlier quoted context omitted.

I also was and still am disappointed about both changes, but I don't think you're being at all fair to Mozilla. In both transitions, Mozilla made sure to support the needs of both uBlock origin and NoScript, extending the webextension API (such that uBlock origin on Firefox is more capable than on current Chromium) and working with uBlock to make its interface more mobile-friendly. They also extended the webextension…

I’d say fairness also requires mentioning how the browser has been able to improve because of killing off XUL extensions; technologically, they were holding things back. Firefox is considerably faster than would have been possible without breaking a great many XUL extensions anyway. And more secure, if you care about that kind of thing, which normal people probably do or should, but frankly it’s the performance I car…

Post by Abishek_Muthian » Tue, Aug 30, 2022, 1:39 PM UTC

e3bc54b2 wrote: post #87

gorhill wrote: post #71

One of the stated goal of MV3 by Google[1] was to avoid extensions with broad permissions: > our new declarativeNetRequest API is designed to be a privacy-preserving method for extensions to block network requests without needing access to sensitive data This MV3-based AdGuard extension still requires a broad permission to "read or modify host data" on all sites[2]: "host_permissions": [ " " ], So what you have now i…

For context, gorhill is the veteran author of original uBlock, and current uBlock Origin. He knows what he's talking about as author, maintainer and one of the community leader/voice of probably the single best and only conflict-of-interest-free ad-blocker currently in existence. His past post[0] was reposted and generated quite a discussion on HN [1]. For further details on why uBO is conflict free, this is the READ…

Post by ComodoHacker » Tue, Aug 30, 2022, 1:43 PM UTC

gorhill wrote: post #71

One of the stated goal of MV3 by Google[1] was to avoid extensions with broad permissions: > our new declarativeNetRequest API is designed to be a privacy-preserving method for extensions to block network requests without needing access to sensitive data This MV3-based AdGuard extension still requires a broad permission to "read or modify host data" on all sites[2]: "host_permissions": [ " " ], So what you have now i…

Post by moonchrome » Tue, Aug 30, 2022, 1:43 PM UTC

avhception wrote: post #109

ameshkov wrote: post #81

Earlier quoted context omitted.

All true, and we (content blockers devs) were saying this all for years, since MV3 was first announced. MV3 brings very little (if any) privacy and security enhancements, this is for the future MV4 when extensions will be dumbed down to sets of declarative rules. We'll now need to rely on Chrome team for implementing what we need. But they do it painfully slow or not do at all. Also, where will we get the new ideas i…

I just wanted to say that you (content blocker devs) have been heard, maybe not by the majority of browser users but at least people like me are championing Firefox over webkit-based browsers precisely because to do otherwise would be to loose control of the web to FAANG, especially Google. I've been telling everyone who would listen about how Google leverages Chrom(e/ium) against user interests and have deployed Fir…

Post by webmobdev » Tue, Aug 30, 2022, 1:46 PM UTC

lotsofpulp wrote: post #106

webmobdev wrote: post #34

I don't know if it is cartelisation (both Apple and Google have an ad division and it is in their interest to work together on some aspects of this business) or Google bribed Apple (through its ios search engine deal), but Safari webkit also has limitations in ad blocking through the content blocking API which Apple created for Safari. (See Explanation of the state of uBlock Origin (and other blockers) for Safari #15…

Is it possible that Apple’s implementation uses less power and hence conserve battery life? Also, is it possible Apple’s implementation requires less trust in extension and is more private because no browsing information can exit? It is also possible for the above, and collusion to all simultaneously happen, and or Apple advancing their own ad business.