From 274644de249fca2f3ee6333b883bedcc7532b782 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 26 Nov 2017 17:44:20 -0500 Subject: [PATCH] Updated How to work only with global rules and all scripts blocked by default (markdown) --- ...ly-with-global-rules-and-all-scripts-blocked-by-default.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md index dc94752..0e05134 100644 --- a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md +++ b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md @@ -1,7 +1,3 @@ -The motivation for this article is the following argument I've seen being made: - -> I like the way NoScrip works. If you think a domain should be untrusted, you untrust it everywhere. If you trust it, and require the domain, then you white list it. - The way you work your ruleset with uMatrix is not dictated by uMatrix. If you want to work strictly with global rules, i.e. rules that apply everywhere, uMatrix allows that. Using an example page, this is uMatrix with out-of-the-box ruleset -- by default uMatrix is set up to work with per-base domain rules: