Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers
-
What makes you think mozilla will not follow the same path.?.which comsidering their history they will do eventually,so moving to firefox is not really a solution.
Do you have a source for where it states ublock origin will not be supported by v3.?.
Don't bother with librewolf because that is just firefox with the arkenfox user.js touted as a private alternative.
-
This keeps coming up and we'll keep merging the topics.
There will be no official response before there is an official response and you will likely read about it in the Vivaldi Blog when it happens.
https://vivaldi.com/blog/ -
@Priest72
Firefox has come out and stated that they will use most of the Manifest V3 spec while still allowing webRequest
https://www.theverge.com/2022/6/10/23131029/mozilla-ad-blocking-firefox-google-chrome-privacy-manifest-v3-web-requestuBlock has said in the past that V3 will kill their ability to function meaningfully:
https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23 -
Thanks for merging my post. I did check/search before posting and didn't find this message.
At this point, we should have heard something from the V team. Most other browsers or projects being affected by this have made some sort of statement. My guess is that V will not do anything to alter, prevent, not include, etc. all of Mv3. At least w/FF, they will not be implementing the web request portion which is really the key here. I do fear as V is building momentum and users, since Mv3 is making headlines, they will drop quickly if they go with Mv3 as-is.
It's okay, I've jumped ship before, back and forth and back again. What's nice now is all of the extensions I use have export/import options, are on both stores and bookmarks are easy to migrate.
-
@vongalin said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
At this point, we should have heard something from the V team. Most other browsers or projects being affected by this have made some sort of statement.
There's a statement from @OlgaA here from 2019
"Needless to say, we'll be following closely and come up with a plan based on their final decision."
I think we can trust the Vivaldi team to continue working on solutions that will be presented when they are concrete.
In principle, Vivaldi will certainly not go down the same path as Google. -
@ingolftopf said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
In principle, Vivaldi will certainly not go down the same path as Google.
While I generally trust that to be the case, Vivaldi is unfortunately literally in the same vehicle as Google (Chromium), so to my understanding unless there is an entirely unique browser engine in the works, there may not be anything that can be done.
-
So with Google limiting or blocking ad-blocking extensions, will this also happen with Vivaldi? I know Vivaldi uses the opensource Chromium but I don't know if Google will be making the changes within that or not.
Anyone have any idea how this will go down? Ad-blocking is a core feature I won't do without, not because they are ads but because so many ads are a security risk and just straight up slow down web sites.
P.S. I also run Pi-hole on my home network but that can't get everything and works a bit different in many ways.
-
Hello (and thanks) to whoever responds here. What's the latest on Vivaldi's plan to address Google's Manifest V3 platform for Chrome? It's been in the news lately, and so I thought I'd check in and see if Vivaldi has any plans in the works to maintain the functionality we've gotten used to with adblocking, etc. And from what I understand, Manifest V3 will be fully in place by January 2023. That's not too far off from now. What's the game plan?
-
Vivaldi won't be affected by MV2->MV3 API switch, for it's own content blocker, for example.
Vivaldi won't support MV2 API anymore, as soon as this API will be removed from Chromium project. -
@ra-mon - thank you for replying.
-
Manifest V3 will be the end of Chrome browsers for me. The web is a toxic advertising dump these days.
The reduced ability to block is a total deal breaker. Manifest V3 will also limit many great modules.My hope is that some browsers such as Vivaldi will remove Manifest V3 or even just fork off. Since Firefox is also planning on adding Manifest V3 as they always copy Chrome, it seems like the perfect time for a new browser engine that moves the power of the browser back into the hands of the users.
-
@ra-mon said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
Vivaldi won't be affected by MV2->MV3 API switch, for it's own content blocker, for example.
Vivaldi won't support MV2 API anymore, as soon as this API will be removed from Chromium project.I don't like the change. Vivaldi's built-in AdBlocker is not as powerful enough as uBlock Origin. Vivaldi's AdBlocker doesn't support scriptlet, doesn't support CNAME cloaking, and doesn't even support blocking Google Analytics, not to mention being compatible with all AdBlock Rule syntax.
If Vivaldi decides not to be compatible with uBlock Origin / uMatrix anymore, well, I guess it is about time for me to leave Vivaldi and switch to a browser that allows me to use uBlock Origin (which is Firefox).
Goodbye, Vivaldi! Wish you still have as many user as you have today by the time you drops MV2's
webRequest
API. -
@sukka said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
@ra-mon said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
[...]Vivaldi won't support MV2 API anymore, as soon as this API will be removed from Chromium project.
Ugh, I wonder how well that's going to go down with people regarding extensions such as uBlock Origin (no, not uBlock minus) as a clear must have.
I don't like the change. Vivaldi's built-in AdBlocker is not as powerful enough as uBlock Origin. Vivaldi's AdBlocker doesn't support scriptlet, doesn't support CNAME cloaking, and doesn't even support blocking Google Analytics, not to mention being compatible with all AdBlock Rule syntax.
Wow. Really? Can't even block the most basic and most invasive things?
If Vivaldi decides not to be compatible with uBlock Origin / uMatrix anymore, well, I guess it is about time for me to leave Vivaldi and switch to a browser that allows me to use uBlock Origin (which is Firefox).
Yes, alternatives have become more and more scarce. I wish we were still in the Presto days, when Tetzchner's Opera was still under their full control.
Goodbye, Vivaldi! Wish you still have as many user as you have today by the time you drops MV2's
webRequest
API. -
... Vivaldi's AdBlocker doesn't support scriptlet, doesn't support CNAME cloaking, and doesn't even support blocking Google Analytics, not to mention being compatible with all AdBlock Rule syntax.
Wow. Really? Can't even block the most basic and most invasive things?Yes. No scriptlet, no style injection, and wildcards are only supported if it is in the domain (so wildcards in the path will simply be ignored).
...
Yes, alternatives have become more and more scarce. I wish we were still in the Presto days, when Tetzchner's Opera was still under their full control.Brave browser confirms that they will drop all MV2 API but leave the
webRequest
API intact, Mozilla Firefox has a very similar plan. If Vivaldi decides not to be compatible with uBlock Origin, well, guess Vivaldi is not "privacy first" as they claimed (Just take a look at how weak the built-in AdBlock support it is!)Goodbye, Vivaldi! Wish you still have as many users as you have today by the time you drops MV2's
webRequest
API. -
@sukka There hasn’t been any change yet. That Vivaldi will be following Google’s approach one to one is highly unlikely and pure speculation on your part. The inbuilt adblocker has no restrictions regarding amount of entries, but lacks cosmetic filters and the ability to zap elements. In my opinion these issues could be addressed.
-
@luetage said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
There hasn’t been any change yet. That Vivaldi will be following Google’s approach one to one is highly unlikely and pure speculation on your part. The inbuilt adblocker has no restrictions regarding amount of entries, but lacks cosmetic filters and the ability to zap elements. In my opinion these issues could be addressed.
Here is a thing. Chrome claims that MV2's
webRequest
API will always be available to Chrome Enterprise customers through policyExtensionForceList
. That's to say, any extension installed through Chrome's policyExtensionForceList
will still have access to thewebRequest
API.What does it mean? Well, it means Chromium will almost never remove the
webRequest
API code from its codebase. It is just behind a feature flag.So, since the code and the API are always there and will not fade away, it is dead simple for Vivaldi or any Chromium-based browser to provide MV2's
webRequest
API to every extension, just one or two simple patches of the feature flag and make it re-available.
It is not as hard as you might think. It is not copying the old Chromium code then adding it to the current code base. No. All they have to do is to patch the feature flag.The only reason I can think of Vivaldi not doing this is that Vivaldi is not privacy first as they claimed.
-
@sukka Yes, you have a point. Now that you explained it to me thoroughly, the only logical explanation is Vivaldi has bad intentions and together with Google plots to take away our privacy for profit. It’s a conspiracy and if you ask me, it’s very likely the government is behind it.
-
@luetage said in Request for Manifest V3 implementation in Chromium could result in breaking AdBlockers:
Vivaldi has bad intentions
Fully agree, Vivaldi is totally known for their bad intentions. For example, Google once had the slogan "don't be evil" and dropped it. Vivaldi never even had a slogan like that to drop, so obviously they are worse than Google.
@sukka thanks for joining the community yesterday to explain this to us and open our eyes!
-
Manifest v3 is a hot topic these days, so our developer Julien looked into this and has written a blog post about it. You can read it here: https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/.
-
Google devs delayed cut of V2 manifests ⇒ https://groups.google.com/a/chromium.org/g/chromium-extensions/c/zQ77HkGmK9E