From a1c560ed7c72a64089144fce1d1b2454fc55de60 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Wed, 28 Oct 2015 15:51:53 -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 a660010..ef0c394 100644 --- a/Inline-script-tag-filtering.md +++ b/Inline-script-tag-filtering.md @@ -130,7 +130,7 @@ Also, when script tag filters are present, it's entirely reasonable to imagine t Inline script tag filters are something to use as last resort when all else fail. Without inline script tag filters, when all else fail, the remedy is to disable the blocker -- which is the absolute worst option, which has a much worst effect on performance than the code used to enforce inline script tag filters. Currently this is what users of Adblock Plus have to do: disable the extension on _Bild_. -Keep in mind that currently a common way for Adblock Plus to deal with anti-blockers is to create exception filters, i.e. to no longer block specific 3rd-party network requests which would have otherwise been blocked ([example](https://adblockplus.org/forum/viewtopic.php?p=140159#p140159)), so essentially to allow more unwanted 3rd parties into your browser. This can often be avoided with inline script tag filters. +Keep in mind that currently a common way for Adblock Plus to deal with anti-blockers is to create exception filters, i.e. to no longer block specific 3rd-party network requests which would have otherwise been blocked ([example](https://adblockplus.org/forum/viewtopic.php?p=140159#p140159)), so essentially to allow more unwanted 3rd parties into your browser. This can often be avoided with inline script tag filters ([example](https://github.com/gorhill/uBlock/commit/52b1b2c2947698eaa86284bcf28d8848adb1d2d3). > They won't do that for a small extension like uBlock but they will definitely do it if we implement something like that.