How will Vivaldi deal with Google's Manifest V3?
-
@Pathduck, well let's see until when, both are scripts that Google surely doesn't like. For sure it isn't tampermonkey which will delete it, but for sure Google if it noticed it, Google has access to the extensions in the store.
-
@Catweazle Google can't remove installed user scripts.
-
@Pathduck It can try to scare users away from using them. If I add a userscript I now get a warning box saying something like "can't verify where this script came from". I can ignore it and dismiss it. For now.
-
@LonM Yeah, that's new in C128.
I guess, if the browser is able to warn it's also able to block it from being installed. But the browser can't (far as I know) remove or block a userscript that's managed by a userscript manager extension - at least one that follows Mv3 rules.
And there are some really really shady userscripts out there, so the warning is warranted I think. People should definitely not just install untrusted userscripts, manager or not.
But if a user even is able to get to the point, of having opened the browser extensions page, enabled developer mode and then managed to drag the script in, surely that must be a willed action - I'm unable to imagine someone accidentally getting to that point
-
@Pathduck, when it not was the dev of the extension, nor Google, who delete than this scripts from the extension?
-
@Catweazle You still did not say which extension it is.
And I did not say it was not the dev of the extensions, in fact I implied that was the most likely. It was not Google, that's all I said.
-
@Pathduck, anyway the scripts are working now as they should installed from my HD, without Script Manager extension. I will use the other extensions until they work, no more visits to the Chrome Store.
In the German subforum they are also mencioning that Google will eliminate all adblockers from the store, only maintain some "light" versions. Also Mozilla will next year adopt Mv3, because of the "new
orderwebstandart".
We'll see -
Said:
In the German subforum they are also mencioning that Google will eliminate all adblockers from the store, only maintain some "light" versions.
You don't need to read it in the German subforum.
It is known that after June 2024 all extensions, not only ad blockers that are not MV3 compliant, will be phased out.
So it will not be "light" ad blockers, but those that are MV3 compliant.
In Chromium without policy:
βSoonβ means between June 2024 and June 2025.
-
How soon?
I would imagine that these criteria would be taken into account:
- Your country (Perhaps taking into account how many blockers were downloaded in that country. Those who have downloaded the most will be left for the end.)
- What extension blocker you use
- How much do you use YT
- etc.
I don't think it will be random.
-
Said:
If I add a userscript I now get a warning box saying something like "can't verify where this script came from".
Where?
Page of extensions or Tampermonkey?
Please post an image.
-
AFAIK there are only 4 userscript repositories, Greasyfork, OpenuserJS, Userscripts-Mirror and GitHub, there is also a list in the Wikipedia, most Wikipedia related.
Respect adblocking, most are not updated since several years and for sure useless because of this and the Mv3, eg. Anti-Adblock Killer.
-
With a sad hart I'm saying goodbye to Vivaldi after many years.
It has absolutely nothing to do with Vivaldi itself but with the whole Google Manifest V3 thing.
I did read the pro, con and neutral articles about it and it all leaves a very bad taste in my mouth.
I'm sure it will do some good for the Chromium based browsers and it will lighten the workload on computers.
And it has some privacy advantages because "wild" extensions can't be used anymore.Yet, my gut feeling keeps on telling me that control is the main purpose of Google here. They live for data collection and advertisements, so for Google it's good.
In Dutch we have a saying: "Het is als een slager die zijn eigen vlees keurt"
Roughly translated that comes down to: "It's like a butcher who certifies his own meat".
And this is something that drives me away from the Chromium based browser.
And sadly Vivaldi is one of those.So a huge THANK YOU!! to all the people who made it possible for the many years that I could use the great browser!
-
What a poetic funeral poem! Who died?
Please explain in detail to those of us who will be "left" to lose control, how this will be noticed in the daily use of Vivaldi.
Perhaps your wisdom is greater than ours and we do not see it.
What those of us who remain will see is that the balance between the pros and cons is that the pros win.
Show us the light.
-
Huh! Some think with Manifest v3 Chromium is a sinking ship now and leave Vivaldi in favor to Mozilla!?
I wait until June 2025 and then decide if Vivaldi is still usable for me. -
We know your particular case and it is understandable. Wait and see is rational and valid.
-
@DoctorG, FF also will change to Mv3, because it will be the new standard. So I think, that a lot of users will return to Vivaldi anyway.
I think more about in methodes to surround eventual inconveniences in June 2025 that will surely be. -
While google will replace MV2 with MV3, FF will support both MV2 and MV3. It's a huge difference.
Remember that FF did not implement other google "standards" also. FF, for example, accepts "Client Hints" requests but returns nothing, while Vivaldi cannot do the same.
-
@stilgarwolf, yes, but also Vivalldi can still accept MV2 and Mv3 like FF, but the problem is depending on the Chrome Store, where Mv2 extensions are not longer exist after June 2025. That the only difference.
Because of this it's good to have included in the browser al the features needed related to security and privacy. Maybe in the future with an inbuild userscript manager.
In other extensions not related to this it's irrelevant if they are v2 or v3.
Firefox, without an inbuild ad/trackerblocker depends of blocker extensions, hoping that it's devs also support v2 blockers in the future, which isn't so clear.
-
@Catweazle said in How will Vivaldi deal with Google's Manifest V3?:
FF also will change to Mv3
you keep repeating this fallacy. it's like you're deliberately trying to misdirect people, for goodness sake. mozilla have stated & restated that they are incorporating mv3 for ongoing compatibility BUT [& you keep ignoring this vital part] it is to complement their existing & ongoing mv2 capability, not replace it.
-
How can I call this command again? Unfortunately, I have forgotten how it works.