571
Google's Manifest V3 changes will soon disable uBlock Origin on Chrome
(www.androidauthority.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Nov 2023
571 points (96.1% liked)
Technology
34908 readers
182 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 5 years ago
MODERATORS
That, my friends, is why we kept fighting for firefox. It doesn't matter if you like or dislike Mozilla foundation, they have to exist because of shit like this
yet we already have a working implementation of ublock origin for mv3 by it's main developer, gorhill
When I read about that like a year ago gorhill had clearly stated that the mv3 version's efficacy is severely kneecapped and while it works as well as it can it's extremely bad in comparison to the present version on Firefox and Edge
How is edge working better than chrome? It's basically just a reskinned chrome.
Edge has been picking and choosing what features to carry over and off the top of my head announced they wouldn't be merging in the most unpopular MV3 changes
Firefox has the same problem with V3, it has nothing to do with the browser, adblocker V2 will stop working, because are the advertising companies wich will use V3 scripts. For Chrome and Chromium the only thing is, that are no more V2 adblocker in the Chrome Store and installed adblock extensions won't work anymore. after June 24. But don't panic, the fact that adblocker V2 stops working does not exclude that there will be adblocker V3, the devs of these are not going to rest on their laurels either.
to my knowledge Firefox is keeping compatibility with most current extensions at least in terms of adblockers and privacy tools as they transition to manifest v3
Didn't they say they will implement V3, but change it slightly to allow extensions like ublock origin to block web requests? Also I'm pretty sure there's still no timeline for any deprecation of V2 in FF, unlike for Chrome, which will disable all V2 extensions.
Also not a problem in Vivaldi, it has a own inbuild ad/trackerblocker, no need of the Chrome Store for this. Anyway until June 24 also the adblocker devs have updated their products for sure.
If you understood the differences between manifest v2 and v3 you'd understand that it's pretty much impossible to make an ad blocker with the same effectiveness in V3 as in V2.
So they will exist, just be worse.
No https://blog.shahednasser.com/chrome-extension-tutorial-migrating-to-manifest-v3-from-v2/ How long do you think it will take the devs to change the adblockers to v3? 3..2..1..
That doesn't even mention the changes to webrequest. Here's an intro: https://developer.chrome.com/docs/extensions/migrating/blocking-web-requests/
Only hard and adrich times for Chrome users and some work of the devs from adblockers and other browsers.
What the hell are you talking about? This has nothing to do with what advertising companies do.
The main reason adblockers don't like manifest V3 is that the webRequest API is gone. The proposed replacement, declarativeNetRequest, does not have the same functionality.