From cad559b32995c45c475cc6cd17f19d14bf3eb51c Mon Sep 17 00:00:00 2001
From: gorhill <rhill@raymondhill.net>
Date: Tue, 7 Oct 2014 10:09:47 -0700
Subject: [PATCH] Updated Dynamic filtering (markdown)

---
 Dynamic-filtering.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Dynamic-filtering.md b/Dynamic-filtering.md
index 2179575..f0dc644 100644
--- a/Dynamic-filtering.md
+++ b/Dynamic-filtering.md
@@ -1,5 +1,7 @@
 Dynamic filtering, introduced in version 0.7.0.0, allows a user to filter dynamically certain classes of requests. Currently, `script` and `iframe` objects can be dynamically filtered, i.e. filtered on or off without having to create a custom filter.
 
+This feature is not suited for users who like an install-and-forget blocker. Thus it is tucked away by default, and all dynamic filters are turned off by default. Dynamic filtering is targeted toward users who wish to have that extra control about where their browser is allowed to connect and what it is allowed to execute.
+
 Dynamic filtering is a useful feature security-wise. For example, blocking 3rd-party `<iframe>` by default would have protected users in the case of the [jQuery.com malware attack](http://www.riskiq.com/resources/blog/jquerycom-malware-attack-puts-privileged-enterprise-it-accounts-risk). Disabling inline javascript is also often useful to work around anti-blockers on some sites.
 
 Of course, blocking portion of a page may cause page breakage, sometimes benign, sometimes severe. It is up to the user to choose how to make use of this feature.