08-19-2020, 12:19 PM
uBlock & uMatrix are written by the same developer, and both are needed for full functionality.
uBlock takes up what he calls the "static filtering" part, it's a replacement for AdBlock and an element hider, not NoScript. It will only block site elements that it has a pre-existing rule for in some filter list, and it provides a UI for creating your own filter rules, matching by URL, or by CSS selector for cosmetic filters.
uMatrix is the "dynamic" filtering half, performing the functions of NoScript, RequestPolicy and a cookie manager. You can set it to deny everything by default, and then choose what to enable from the categories of cookies, css, images, media, script, XHRs (requests by a script to load content on the fly), frames, and miscellaneous, and from what domains & subdomains the current site should be allowed to load each of these.
uMatrix is better than NoScript & RequestPolicy once you get used to it, and has an interface better suited to complex modern sites with a lot of cross-site requests. It does not include some of NoScript's niche extra features, like "ClearClick"; if you actually need those, then you'll need to install NoScript alongside it.
As soon as I install uBlock, I turn off & delete the subscriptions to massive third-party filter lists and just use it for creating my own filters to zap things with more resolution that uMatrix allows for. Typically this occurs when you want to block only some scripts or images from a particular origin, while allowing others.
uBlock takes up what he calls the "static filtering" part, it's a replacement for AdBlock and an element hider, not NoScript. It will only block site elements that it has a pre-existing rule for in some filter list, and it provides a UI for creating your own filter rules, matching by URL, or by CSS selector for cosmetic filters.
uMatrix is the "dynamic" filtering half, performing the functions of NoScript, RequestPolicy and a cookie manager. You can set it to deny everything by default, and then choose what to enable from the categories of cookies, css, images, media, script, XHRs (requests by a script to load content on the fly), frames, and miscellaneous, and from what domains & subdomains the current site should be allowed to load each of these.
uMatrix is better than NoScript & RequestPolicy once you get used to it, and has an interface better suited to complex modern sites with a lot of cross-site requests. It does not include some of NoScript's niche extra features, like "ClearClick"; if you actually need those, then you'll need to install NoScript alongside it.
As soon as I install uBlock, I turn off & delete the subscriptions to massive third-party filter lists and just use it for creating my own filters to zap things with more resolution that uMatrix allows for. Typically this occurs when you want to block only some scripts or images from a particular origin, while allowing others.