I'm curious: how do you use it? Do you have to mass-enable stuff using the 'power' icon, for many sites? Or do you just enable the things you know you need, on a per-site basis? Or are your default just good enough?
The reason I ask is that I was curious about it, so tried it out for a couple of days. I found many sites were not usable with the default settings, e.g. Udemy's login box didn't show up until I turned off µMatrix.
I haven't used uMatrix, since I use Firefox, but I can speak for RequestPolicy, which is kind of the same thing basically AFAICS. It's very very very rare that I end up whitelisting everything that's requested on a site. The more you use the extension, the more you learn to recognize what domains you need to allow in order to have the site working as intended, and this way you end up building your own whitelist: allowing requests from a domain is a one-time only thing most of the times (additionally, there's an extension you can install that syncs your whitelist to your Firefox Sync account).
> the more you learn to recognize what domains you need to allow in order to have the site working as intended
Sites using cloudflare are a major issue here, specifically their cryptic subdomains. If someone were to hide an ad network behind those they would be hard to tell apart from the rest, at least for humans.
Yes this is true. If a site is not working and the only reasonable domain to allow is something from cloudflare, I resort to allowing it temporarily. Not many ways around that, I think.
I'm curious: how do you use it? Do you have to mass-enable stuff using the 'power' icon, for many sites? Or do you just enable the things you know you need, on a per-site basis? Or are your default just good enough?
The reason I ask is that I was curious about it, so tried it out for a couple of days. I found many sites were not usable with the default settings, e.g. Udemy's login box didn't show up until I turned off µMatrix.