From 2a111255b2eb354f1a0df8ae010308e8b03bd311 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Fri, 2 Oct 2015 10:09:27 -0400 Subject: [PATCH] Updated Inline script tag filtering (markdown) --- Inline-script-tag-filtering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Inline-script-tag-filtering.md b/Inline-script-tag-filtering.md index 1526581..e6244e1 100644 --- a/Inline-script-tag-filtering.md +++ b/Inline-script-tag-filtering.md @@ -50,7 +50,7 @@ In the cat and mouse game between web sites and blockers, the new script tag fil The big advantage of this new filter is that it can fix _at the source_ many of the anti-blocker workarounds used by some web sites. -For example, the web site at `http://focus.de/` will resort to deface itself with ridiculous ads when the site detects that the user is using a blocker, and using _EasyList_ + _EasyList Germany_ does not work, as the images pulled by the page are randomly named defeating pattern-based network filters and easily defeating cosmetic filters as well. +For example, the web site at `http://focus.de/` will resort to deface itself with ridiculous ads when the site detects that the user is using a blocker, and using _EasyList_ + _EasyList Germany_ does not work, as the images pulled by the page are randomly named, defeating pattern-based network filters and cosmetic filters as well. Wholesale blocking of inline script tags does prevent the auto-defacing, but possibly at the cost of using useful functionalities. However, a script tag filter to block the specific inline script tag which contains the self-defacement javascript code allows a more targeted approach: prevent the undesirable inline javascript code from executing while keeping the desirable inline javascript code intact. At time of writing, this script tag filter worked for the site: