Live data from Hacker News

"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

developer.chrome.com

191–200 of 490 posts

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#192

I am tied to Microsoft Edge for sync between desktop and phone, and Microsoft Edge on iOS has AdBlock built in. But looking at this it seems inevitable that Edge will retain V2. As to switching to Firefox? I'd love to, but Firefox on iOS refuses to put in an AdBlocker. Yea, you can use Firefox Focus but that one doesn't sync. I don't understand Mozilla's stance on this.

Firefox doesn't exist on iOS, it's just reskinned safari. It's not Mozillas fault that Apple won't let you install a different web engine.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#193
post #185

Earlier quoted context omitted.

onBeforeRequest was removed because it is a massive spyware and malware vector. > I do get that this sounds like conspiracy theory. > … was not a coincidence. Could it be that it was coincidence? Do you have a solution for reducing extension malware without removing onBeforeRequest?

> onBeforeRequest was removed because it is a massive spyware and malware vector. Yet you can still inject js right into the page. You just can't stop a page that was going to load from loading. They could have taken away the onBeforeRequest redirect capability and left just the onBeforeRequest cancel capability. Not sure I've heard of any spyware/malware depending on just that cancel capability.

That uses a different manifest permission.

https://developer.chrome.com/blog/crx-scripting-api#breaking...

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#194

Earlier quoted context omitted.

To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible

Though it is less of an issue for those two, given that they have built-in adblocking. Still a laudable effort.

At least when I last tested, Vivaldi on Android's adblocking is pretty far behind uBlock Origin -- it doesn't get nearly as many anti-adblock interstitials as it should.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#195

Earlier quoted context omitted.

To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible

Though it is less of an issue for those two, given that they have built-in adblocking. Still a laudable effort.

While adblocking has gotten most of the focus, it isn't the only functionality that is being limited or made more complicated. One of my favorite extensions is still not available for MV3 because of complications: https://github.com/openstyles/stylus/issues/1430

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#196

Earlier quoted context omitted.

I don't know if this is what you meant, but as an alternative to profile switching, there are Multi Account Containers [1]. It allows assigning a container to each tab, and the containers are isolated from each other. If you have an MS or Google account for both work and personal, you can open them at the same time in different tabs. [1] https://addons.mozilla.org/en-US/firefox/addon/multi-account...

this is such a killer feature I don't understand why it even is an extension, every browser that isn't adversarial to the user should have that feature tbh

I've found it hard to teach people how to use but it is a killer feature.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#197

For people who want to stick with a Chrome-based browser while still using the full-featured uBlock Origin: Brave will keep supporting uBlock Origin even after Manifest V2's removal from Chromium. https://brave.com/blog/brave-shields-manifest-v3/

Note that Brave's creator opposes same sex marriage, is a Coronavirus "skeptic", and his silly cryptocurrency is made to work with brave browser.

I don't care.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#198

Notably, Firefox is not removing v2 support (at least for now as of March 2024) > Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed. [1] [1]: https://blog.mozilla.org/a…

To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible

Aren't these v2 extensions being removed from Chrome's store? If so, are the alternatives based on Chromium running their own store?

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#199
post #42

Earlier quoted context omitted.

The widespread adoption of Chrome was largely driven by word of mouth, people like you and I installing it on our friend's/relative's computers and telling them it was safer/faster/better. Nothing stops us from doing the same thing again. I've been recommending Firefox to all my family/friends/colleagues for years (ever since I've seen the writing on the wall for Chrome). While Firefox isn't perfect, it's in a much b…

>The widespread adoption of Chrome was largely driven by word of mouth No, it was driven by having a banner in the most privileged spot of the Internet, Google.com (the most visited site in the world with 0 ads on the homepage) saying that was faster and more secure than the alternatives. In fact Firefox benefited from some free ads on Google.com against Internet Explorer before Google developed Chromium.

The other aspect, somewhat memory-holed, was that Chrome was automatically installed as shovelware if you went to install Adobe Flash for IE or Firefox:

https://www.reddit.com/r/chrome/comments/23jnmy/why_is_chrom...

This kind of not-freely-given consent was key to Chrome's growth.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#200

Earlier quoted context omitted.

If I remember right then the difference is more about ad-tracking/privacy than blocking. V2 allowed UBO to find and intercept the calls to the ad servers before the calls were made. Where V3+UBL still makes the calls it just doesn't display the results. So while you might not see the ads, the ads see you.

On the contrary, MV2 used onBeforeRequest which let extensions see what requests you were making. They could then take that data and use it for malicious purposes. MV3 doesn’t allow extensions to know what requests are being made, so extensions can’t use your data maliciously. Requests to ads that are blocked are blocked. I think you’re thinking of Privacy-preserving ad measurement which is an option in Firefox and S…

Doesn't onBeforeRequest still exist in Manifest v3? The thing that's been removed is the ability to block on it, not the ability to register handlers for requests.
Post reply on HN