uBlock Origin is no longer available on Chrome web store

This link wants me to login.

My guess is that the user took the screenshot from a Chrome Beta/Dev/Canary build which is following an accelerated timeline for disabling Manifest V2 extensions [1].

Also, note that there is an enterprise policy that can enable Manifest V2 extensions through June 2025 [2].

[1]: https://developer.chrome.com/docs/extensions/develop/migrate...

[2]: https://chromeenterprise.google/policies/#ExtensionManifestV...

I absolutely agree with that from a technical perspective, but in typical usage, the users won't notice any difference.

To be honest, I think uBo almost become a cult (which is nothing wrong, to be clear). It has lots of very opinionated development progress happened/happening to it, and most of them are irrelevant for majority of users (even the "power" users). And if I dare to say, it's at the cost of its UX.

For example, a few years ago, uBo disabled the ability to "greenlight" a domain (i.e. adding a whitelist dynamic rule) by simply clicking in the (advanced) popup. The official reason is that it's the most misused features, which is true, but it makes legitimate use of it (to whitelist a 3rd-party domain for a specific site because otherwise the site is broken) very inconvenient.

And if you ask about it, they (people in related forums like reddit) tell you "well you should never use it. NOOP should be sufficient. If not, the rules are wrong and you should report to the rule author(s)." This is cool but it didn't solve my immediate problem that a site I want to visit is broken by uBo.

I learned later, again from uBo subreddit, that you can double press ctrl to temporarily enable this feature back -- which is more than enough for me -- but how the hell do you even discover this?

And I never remembered what the two columns for adding dynamic rules are supposed to be -- since there is no headers.

FF profiles do work.

The problem is discoverability and UX. I believe, in chrome profile management is another menu option. In FF you have to use about:profiles or start Firefox with a specific command line argument.

Unless you know about it or are actively looking for the feature, there's no way to know. If you are coming from Chrome, this unfortunately leaves the impression that Firefox doesn't support profiles (a must have feature for some).

It doesn't even hint or show up in settings search. It is as if they don't want anyone to use/know about profiles.

Still, time to swap brower rather than prolonging it.