As you can see when it comes to giving an overview which scripts are allowed or blocked, ScriptKeeper and NotScripts do a better job of keeping it simple. But let's agree to disagree.
I have 3rd party blocked by default and only allow 1st party. If page breaks I can see everything that was blocked and can easily find what breaks it. If I would had to switch through tabs to find out everything that was blocked it would become real PITA to manage rules.
I see you got the 2nd one. As for the first one, it works right away for me. The reason? Because over time when managing sites with a script blocker such as this one, you will get a good feel for certain common domains like, for example, ytimg.com, *.ytimg.com, apis.google.com and googlevideo that are required for many sites to fully render desired content. So for these domains, you can easily whitelist them globally in the matrix, so that they are automatically whitelisted when you visit sites for the first time that need them, such as the ones you linked to.
That's some unflexible mind. Whining this and that I have seen, if something is not exactly to his liking. Unwilling to learn what is needed instead. The matrix concept is nice also to me. And uMatrix can pretty much be made how most wants it to be, but it takes some learning. That global hint was a good one if someone wants this to be more "easy".
An observation I got from User Agent spoofing option in uMatrix. That I had enabled globally. I was watching Dr Who episode on a finnish public broadcasting website. And I noticed that every about 5 minutes the broadcast was cut down. I was really puzzled and changed to Firefox, no problems with it. Came back to Chrome and disabling ua spoofing for that domain stopped the connection from terminating. Just an observation to other users if you are experiencing the same and what to do then. I did not see any warning on the question mark hint that this can happen. And it was really alarming until I found out what was the cause.
Yes, this happens on a couple of sites. That's why gorhill introduced a per-scope switches in v. 0.8.1.0 where you can disable UA spoofing (among other things) on sites where this causes trouble.
It's not about learning, it's about my own user experience. I noticed that all that other stuff is distracting to me, when I try to quickly enable some scripts. And unlike you, I don't say that people are "whining" when they think differently. It's just an idea, you never know if the developer may like it, though I doubt it. I'm also not sure if it's possible to offer 2 different UI's, probably not. Isn't that the standard setting? I thought that it's script filtering that breaks most pages?
XHRs and frames also break some pages and instantly seeing everything that is blocked is just priceless for me.
I'm having a problem... I want to enable "scripts" by default, and then disable it for certain sites. I remember being able to do that by making "script" green and then making whatever site I don't dark red. I can't do this now. If I make "Script" green, whenever I go to a different site, it's red again.. Is this how it's supposed to work?
You have to change scope (on left side where it's yourvisitingdomain.com, you change it to *) and save allow scripts for scope *.
I can't understand your directions.. I make the "Scripts" green and then click on "Save all temporary changes for this scope"... After doing that, if I go with a different page, the scripts will be again red. i don't want that to happen. I want to allow scripts globally and then block locally.
It will help a lot to understand the rule system in uMatrix. This link is a kind of longwinded in some words, but looking same time your own rules will make you understand this page: https://github.com/gorhill/uMatrix/wiki/Rules-syntax The way uMatrix came when I first installed it was it allowed all in the 1st-party domain and only blocked the other domains (the 3rd party). Intended to be very easy start for newcomers I guess. Safer setup would be something like this: * * * block * * cookie block * * css allow * * doc allow * * frame block * * image allow These are all global rules, because they start with *. Basically I allow only css and image for any non whitelisted domain. This is of course too restricting to many, but you can achieve what you want by just making these global rules to your likings. And they can all be made from the GUI. Now if I allow 1st-party for some domain. I will still have cookies and frame blocked. Because that's the way I want it. And yes one can make global allow rules for whitelisted domains, to make this work in pretty much the same way as NoScript. With still having the flexibility of that matrix available, if needed.
Sure, the attached image shows what's needed. As for your second question, please see Simplicity's post #215.
And make sure you change the scope back to site-level/domain level from global, after you have whitelisted the resource
Thanks I will check it out. And personally I prefer making global rules, but still kinda cool that you can also do it per site.
Call me stupid, but I can't figure out how to let uMatrix ALWAYS make global rules. I do not want to make site specific rules.
just keep it at the Global scope selection, then any rules you create form that point on will be applied globally.
I think * * doc allow is hidden by default now.... Also i would like to know if this is the right approach http://malwaretips.com/threads/µmat...rix-to-filter-net-requests.36920/#post-309683 Please correct me if i am wrong
I do have that * * doc allow rule. If you mean it has now come hidden in the newer installs, I don't know. My uMatrix version is 0.8.1.1. That is I think good advise you are posting there, removing that 1st party global rule etc. I myself don't want to block script globally. If I allowed a domain 1st-party, in many cases the site still won't work without script. So it will become too much of a bother. See I have then already whitelisted the site. Cookies I block for privacy and frames for security because blocking them does not brake the sites so often. These are just my preferences.