Recent Canary version of Google Chrome starts to block Manifest V2 extensions and you cannot enable them back.
https://www.androidpolice.com/chrome-canary-manifest-v2-extensions-ad-blockers-gone/

In the MS Store uBlock Origin still has the featured badge.
So I believe that uBO is available for Edge for a longer time than Chrome.

On Thursday I did some thinking with a former colleague of mine about some Chromium-based browsers that claimed to continue UBO MV2 support.
MSFN members will certainly be interested in Thorium/Supermium.

Here is what it reads here:

• Manifest V2 (once removed by Google)

https://github.com/win32ss/supermium

1. All browsers that will continue this hypothetical support to the bitter end do NOT have their own Web Extensions Store.
2. Gorhill has NEVER provided, in Github, a UBO MV2 installer for Chromium untethered from the Chrome Web Store.
3. Probably when UBO MV2 is removed from the Chrome Web Store (June 2025?) Gorhill will also stop developing this extension.

In my opinion, UBO MV2 will stay longer in the MS Store than UBO MV2 in the Chrome Web Store.

 

 

I don't know anything about Chrome. But there are many forks of it out. Is support for old plugins something they could easily add back in? Or has Google put hurdles in for that?

15 hours ago, j7n said:

I don't know anything about Chrome. But there are many forks of it out. Is support for old plugins something they could easily add back in? Or has Google put hurdles in for that?

It takes time to add those back. So far, only a couple of China forks (Cent, for example) still maintain V2, Supermium, also.

When asked on the forum, the Chinese developer wrote he will go on with V2 until he's exhausted to revert the changes, and then moves to V3.

So, time's not on our side.

If any forum members would like to check in with other Chromium-based forks and provide feedback:

 

https://www.ghacks.net/2024/11/28/google-claims-that-ublock-origin-is-no-longer-available-for-chrome-but-that-is-not-true/

So far, I have not been affected here at work.  I would witness MV2 disables here at work long before at home due to limitations on what I can do to prevent those MV2 disables here at work compared to home.

 

Who on MSFN uses the webstore? 

Just get 'em here.

https://github.com/gorhill/uBlock/releases

11 hours ago, NotHereToPlayGames said:

So far, I have not been affected here at work.

People write it will turn itself off, like we assumed with you before.

https://github.com/uBlockOrigin/uBlock-issues/discussions/2977

3 minutes ago, D.Draker said:

Who on MSFN uses the webstore? 

Not me!

But that is also irrelevant.  The issus at hand is whether Chrome or Chrome Forks will disable any MV2 extension that you have installed, regardles of from where or how you installed that extension.

But it only affects those on 127+, so I'm planning to stick with 125 for some time.

8 minutes ago, D.Draker said:

But it only affects those on 127+

Good to know!  I'm still on v122 and plan to remain as long as possible.

Here at work, I'm "forced" to use Official Chrome for the desk PC, I have a "little" more control over lab PCs.

So far, I've been able to prevent Official Chrome from auto-updating with this startup commandline switch:  --simulate-outdated-no-au="Tue, 31 Dec 2099 23:59:59 GMT"

Edited November 29, 20241 yr by NotHereToPlayGames

14 hours ago, NotHereToPlayGames said:

Good to know! 

Welcome,

 

14 hours ago, NotHereToPlayGames said:

I'm still on v122 and plan to remain as long as possible.

A year old browser might not hold out for long, sorry to be the downer. And we need new ideas on how to hold onto V2.

Seeing Supermium stuck at 126, more than 7 major versions behind , I kinda suspect that the manifest could be the reason.

Edited November 29, 20241 yr by D.Draker
a typo

Remember that Supermium 126 is supposedly an ESR version.

11 hours ago, Dave-H said:

Remember that Supermium 126 is supposedly an ESR version.

Dave, thanks for reminding. There's a Chinese fork which solved all of the problems, including the bloody V3/V2. Found by @Saxon.

I still hope @win32 will take it into consideration.