Code: Select all
* * script allow
aol.com * script block
If this doesn't work then the site in question might not be aol.com, and the logger would be needed.
Code: Select all
* * script allow
aol.com * script block
I assume that you understand that I don't want to block all AOL scripts, just the ones I believe are responsible for the JS redirects. Will this allow me to block only selected scripts, as in what I had been trying to do before, but which failed? Anyway, will give this a try and see how it turns out.barbaz wrote:Hmm. You could try adding this -This should have µMatrix blocking scripts by default on aol.com, but leave it allowing scripts elsewhere.Code: Select all
* * script allow aol.com * script block
If this doesn't work then the site in question might not be aol.com, and the logger would be needed.
Yep, but finding the ideal solution would take a bit more time and digging.kukla wrote:I assume that you understand that I don't want to block all AOL scripts, just the ones I believe are responsible for the JS redirects.
Sort of. If you explicitly allow all the scripts individually, and narrow it down from there, the end result will be the same.kukla wrote:Will this allow me to block only selected scripts, as in what I had been trying to do before, but which failed?
Great!kukla wrote:* * script allow + aol.com * script block did the job. No more AOL JS redirects!
That's exactly it. Generally it's not worth the extra frustration. It's only useful in specific cases.kukla wrote:Now that NS is set to be the sole script blocker, with this exception, can you explain why you prefer that arrangement as one opposed to letting both be involved with the scripts? This came up when I said that NS alone was often frustrating enough to deal with, and that's when we got started down this road.
Not that I know of, since you can always turn µMatrix script blocking on for specific sites as needed.kukla wrote:Are there any drawbacks to this arrangement?
Looking at the code, I think it ignores duplicate entries.kukla wrote:And another thing I've been meaning to ask is why aren't all the domain names in the each of the Hosts Files not being blocked. Each list is never fully loaded. Is this something set by uMatrix, for some reason?
Don't know what I'm doing with the Logger, plus it behaves quite squirrely. Sometimes where the hangup occurs it's showing hundreds of lines, next time I try it it's blank. Anyway, what do these two screenshots mean to you? (Hoping the anti-spammer allows TinyPic this time.)barbaz wrote:Deos the µMatrix logger show anything blocked?
Don't think they're getting anything from me. Refused to update to any version above the 5.4.11, released 2/16 (but still getting tracker and cookie updates), after which all their BS started. Don't have anything enabled in options that allows data mining. You still think this is a privacy risk?yes_noscript wrote:You should uninstall ghostery if you care about your privacy