By default - Google disabled the store extension pages for browsers it flags as "Not Google" (incl ungoogled-chromium) but the extensions are still compatible.
I'm using UnGoogled Chromium right now, and it seems not to be willing to install uBlock Origin. You can use uBlock Origin Lite. Ironically, The author of uBlock originally recommended switching to Firefox; I wonder if he'll want to change that recommendation now...
> I wonder if he'll want to change that recommendation now...
The recommendation is because Firefox is the only browser running full uBo (and even before uBo on FF had slightly more features than Chrome). Nothing changed there.
I do hope that any FF replacement can run uBo. Well, ideally the best situation is FF changes course by putting the users in control, but I don't see that happening.
>I'm using UnGoogled Chromium right now, and it seems not to be willing to install uBlock Origin.
Works fine on my machine. What version/distribution are you using? There's a specific patch to enable manifest v2 extensions, so it's supposed to be working.
Apparently, at some point, manifest V2 support was introduced. Maybe my build was too old, maybe there was some other issue, but - it seems that current Ungoogled Chromium for Windows builds _do_ support manifest V2.
By default - Google disabled the store extension pages for browsers it flags as "Not Google" (incl ungoogled-chromium) but the extensions are still compatible.
I use https://github.com/NeverDecaf/chromium-web-store
There's a longer walk-through here: https://ungoogled-software.github.io/ungoogled-chromium-wiki...
Long story short - my extensions work just fine. Ublock, bitwarden, etc.
---
Editing this to add - Ublock Origin (not lite) is still working for me on ungoogled-chromium v133.0.XXXXX.
The same version of Chrome on macOS (v133.0.XXXXX) has disabled it by default claiming it's no longer compatible.
So we'll see how long the fork continues manifest v2 support, but at least right now it's still a much better version of chromium than chrome.
I'm already planning on moving to dns based blocking here, because I still have to touch chrome for work...