That repo is archived. Is the project dead?

Isn't it pretty much redundant? You just have to enable advanced mode in ublock origin extension settings. The interface is arguably slightly harder to figure out though, but the functionality is there once you've enabled it.

the ublock origin repo actually has a video linked how it works: https://youtu.be/2lisQQmWQkY?t=294

I'm so sick of reading this.

uBO covers most of uMatrix (and more).

Some of that uMatrix coverage is a hell of a lot harder/more awkward in uBO.

Basically every uMatrix user always also ran uBO too, for the more DOM/'content blocking' aspects (primarly 'cosmetic filtering' as it calls it iirc).

uMatrix lets me block all third-party, allow only first-party scripts/XHR/iframes by default, and then in two clicks (including opening the extension's popover menu) allow some specific host's scripts or whatever, while still blocking its cookies/frames/XHR/media/et al.

uMatrix is more advanced than uBO 'advanced mode', and just as easy to use; i.e. easier to use than 'dynamic filtering' or whatever people suggest that's buried in the full-page settings and not something I'm going to be doing 'on the fly' while visiting a site.

I still use uMatrix (and uBO!) and remain thankful for it - I just hope it lasts, not obsoleted by browser API changes or whatever. (nuTensor was forked to take on that burden, but itself now archived. Apparently - I read in another HN topic on this recently - because uMatrix actually did receive some maintenance update.)

Also uMatrix makes it a lot easier to figure out what you need to allow through - uBO just gives you the hostname, but with uMatrix you know in the popover menu whether it's a XHR, script not loaded, etc.

Yes, it's not actively developed anymore because of the large overlap in functionality with uBlock Origin as well as the maintainance burden.

However it's not equivalent, because in uMatrix you have even more fine-grained control which content a certain domain in a certain context can load (i.e. scripts, images, css and xhr requests).

Its functionality is equivalent, its ease of use isn't (at least in my opinion)

with uBlock origins UI you can block by content type and then whitelist the domains which are still allowed and that feels less granular then the uMatrix configuration dialog.

But if you check the generated dynamic rules in the settings you'll see that it supports the same granular controls as uMatrix

GP is correct afaik: the request categories for dynamic rules in ublock are image, 3p, inline-script, 1p-script, 3p-script, 3p-frame. The 3p vs 1p vs inline is kinda weird in itself since it's contextual and not relating to the content-type of the request, and we are missing css and xhr. Thing is, i realized i most of my dynamic rules are by domain anyway. Maybe if i find a real use case i'll try to look into the code and make this a bit more versatile.

I tried uMatrix for a bit and it seems the dynamic filtering capabilities of uBlock do 80%+ of what uMatrix does.