Live data from Hacker News

Chrome phasing out Manifest v2 support from Jan 2022

developer.chrome.com

11–20 of 34 posts

Re: Chrome phasing out Manifest v2 support from Jan 2022

#11
post #3

Is this gonna kill Adblock or not? Heard different things at different times about manifest 3

It removes the ability for extensions to intercept network requests. Instead, it provides a means for extensions to block content by providing a blacklist. This is similar to how content blockers work in Safari.

It won't kill adblockers, but severely limit their functionality in the face of increasingly elaborate advertising techniques

Re: Chrome phasing out Manifest v2 support from Jan 2022

#12
Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

Re: Chrome phasing out Manifest v2 support from Jan 2022

#14
post #12

Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

> Is there an easy way to run two profiles of firefox simultaneously?

Start one of them with

    firefox.exe -p profile_name -no-remote
I do this to run the beta and the stable version at the same time.

More details here: https://support.mozilla.org/en-US/kb/profile-manager-create-...

Re: Chrome phasing out Manifest v2 support from Jan 2022

#15
post #7

Some absolutely cavalier bombastic bullshit that Google is going to finally send a messenger to the WebExtensions working group like a week or two before they shut off capable MV2[1], having never ever replied to any of the massive massive outpourings of dismay, sadness, & hatred. Just dogshit apocalypically bad mishandling, complete & utter trashfire stewardship. This is the most trust-breaking saddening enraging th…

> I've never seen a company sell such bitterness & sadness so actively before, ever.

If I were to look anywhere, it might be at how Apple is trying to claim the ability to sideload apps on an iPhone would lead to the destruction of modern civilization as part of their war on general purpose computers.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#16
It's been puzzling to me just how slow developers have been to adopt v3. Even right now if you look at a brand new extension created yesterday, or read a chrome extension tutorial from last week...they completely ignore the new manifest requirements.

And Google has been clear for a very long time that v2 was being phased out, so what gives? Laziness? Inertia?

Re: Chrome phasing out Manifest v2 support from Jan 2022

#17

The only hope is that other Chromium derivatives like Edge and Brave continue supporting v2. Considering Microsoft's history, I doubt they are going to be the resistance against ads. Brave has a bright future ahead, I feel.

I appreciate what Brave are doing, but this will affect them whether they support MV2 or not. Extensions on most Chromium forks are installed through Google's Chrome Web Store, so when Google drops support browsers who do not agree will need an alternative distribution platform (like Opera's fork).

More generally, Brave's attitude towards Chromium changes has been "disable first, ask questions later", even when it hurts forward-looking developers and useful feature adoption [1]. In the case of the file system API, there's also a possible conflict of interest, given how they're pushing IPFS and the rest of the crypto web bullshit. My biggest gripe with them is that most of their development efforts go into developing the cryptocurrency features and they end up neglecting general browser usability and innovation.

[1] https://github.com/brave/brave-browser/issues/11407

Re: Chrome phasing out Manifest v2 support from Jan 2022

#18
post #16

It's been puzzling to me just how slow developers have been to adopt v3. Even right now if you look at a brand new extension created yesterday, or read a chrome extension tutorial from last week...they completely ignore the new manifest requirements. And Google has been clear for a very long time that v2 was being phased out, so what gives? Laziness? Inertia?

I worked on a v3 extension earlier this year, and the docs were still half baked and missing a lot of features, often hand waving links to v2 docs.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#19
post #12

Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

Create a shortcut to firefox using the command

firefox -P

whenever you launch it you'll be presented with a dialog to pick a profile or create a new one.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#20
Yeah this is a very awkward release, and not just because MV3 cripples the most important extensions (adblockers).

Firefox also hasn't released MV3 support yet so extensions that are cross-browser can't be MV3, which will be really annoying when Chrome no longer accepts MV2 extensions.

I ran into this just yesterday when I tried to release an extension that removes those stupid fixed banners that take up vertical screen space when you're trying to read an article (https://addons.mozilla.org/en-US/firefox/addon/remove-floati..., https://chrome.google.com/webstore/detail/remove-floating-ba...). I tried to convert it to MV3 only to test on Firefox and find out it doesn't support MV3 :(

I also run https://extensionpay.com which lets developers easily take payments in their extensions without writing their own backend or paying for server costs. A lot of the developers using ExtensionPay in their extensions default to using MV3 since that's what Google says they should do, despite its limitations. It's a really sad state of affairs.

Post reply on HN