From 288d87d64a4e9bdbd4bb03ebca4eca6e6acdf73e Mon Sep 17 00:00:00 2001 From: gorhill Date: Tue, 7 Oct 2014 08:45:03 -0700 Subject: [PATCH] Updated Dynamic filtering examples (markdown) --- Dynamic-filtering---examples.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dynamic-filtering---examples.md b/Dynamic-filtering---examples.md index d3931f5..886fdfe 100644 --- a/Dynamic-filtering---examples.md +++ b/Dynamic-filtering---examples.md @@ -1,6 +1,6 @@ Dynamic filtering can be used to block much more aggressively than what would normally happen when relying only on the default filter lists. With dynamic filtering, web pages are definitely more likely to break, but for many users this is acceptable, so long as the content of a web page can still be read. -Following are some examples of using dynamic filtering vs. not using dynamic filtering, with both scenarios using the default filter lists. The top row in each table shows the used bandwidth. +Following are some examples of using dynamic filtering vs. not using dynamic filtering (i.e. relying solely on the static filter lists), with both scenarios using the default filter lists. The top row in each table shows the used bandwidth. I didn't report below the comparative results without a blocker, that would be a lot of noise detracting from the main topic here, but I provide a summary of what would have happened without µBlock with default filter lists. (That is with click-to-play enabled for plugins -- it would be much worst without this.)