Updated Dynamic filtering: default deny (markdown)

Raymond Hill 2015-02-08 16:04:39 -05:00
parent e50ba78112
commit a9a31224f3

@ -14,9 +14,13 @@ The benefits of using default-deny are plenty:
- Increase browser security
- Easier on your browser's memory and CPU footprint
[...]
The advantages do not come for free. Often, default-deny will require a bit of work the first time you visit a web site. Using [The Guardian](http://www.theguardian.com/) as our current example:
You can disengage default-deny for the current site with one click: set the "3rd-party" local setting to `noop`:
![Default-deny](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/df-dd-03.png)
As seen in the picture above, a few 3rd-party domains related to `theguardian.com` had to be un-blocked for the page to display and behave properly. Note that all rules are permanent as soon as they are set (or unset).
You can disengage default-deny for the current site with one click: set the "3rd-party" local setting to `noop` if you prefer to work this way:
![Default-deny](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/df-dd-02.png)<br>
<sup>Default-deny cancelled locally. Notice that the blocking of 3rd-party frames is still in effect: cells with higher precedence won't have their rules overriden by cell with lower precedence.</sup>
@ -29,4 +33,4 @@ This results in default-deny being disengaged for the current site (`theguardian
>
> ubiquitous servers blocked by default, i.e. no need to pre-emptively block facebook, google, twitter, linkdin, etc. to prevent tracking by these
>
> provide many real-life examples of how easy it is to un-break websites
> provide many real-life examples of how easy it is to un-break websites