3 ms·
It does not allow request blocking as that has been understood in the context of extensions until now It is not a question that V3 breaks the gold standard pri
by LamaOfRuin 5y ago
It does not allow request blocking as that has been understood in the context of extensions until now
It is not a question that V3 breaks the gold standard privacy protecting extension.
- nickelpro 5y agoI quibble with this. Request blocking "as that has been understood", is preventing the request from leaving the browser. That's still demonstrably doable with mv3. What's changed is the mechanism. You can argue about the value of changing the mechanism, about the burden placed on plugin developers, or the efficacy of various APIs, but the functionality is inarguably still there.
- creamytaco 5y agoYou're being disingenuous. With Manifest v3, it is not possible any more to block requests dynamically which has huge implications for the efficacy of ad blocking (example: forget blocking youtube ads). Additionally, you're limited in how many static rules you can have. Therefore, it's not just about changing the mechanism, the end result is clearly a lot worse. One can say, they crippled ad-blocking which this change. Hopefully, once the millions of people using ublock origin start noticing what's happening, they will move away from Chrome. I already did, ublock origin is worth more to me than any feature Google puts in Chrome.