From 6bbdad59632859fe5050e31cf81f6f87e01d212b Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 24 Aug 2014 05:38:40 -0700 Subject: [PATCH] Updated Counterarguments (markdown) --- Counterarguments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Counterarguments.md b/Counterarguments.md index 24b8246..644c717 100644 --- a/Counterarguments.md +++ b/Counterarguments.md @@ -19,7 +19,7 @@ Memory and CPU cycles are finite resources. A sure way for a developer to **not* Using a hosts file at OS level is definitely the best solution for lists of malware domain, since these malware-linked domains would be blocked system-wide at OS level, and all applications would benefit from it. -However, for lists of domain linked to ad servers, trackers, analytics, etc., this is not a good solution: You can't un-break web pages with a [hosts file](http://en.wikipedia.org/wiki/Hosts_(file)) at OS level. +However, for lists of domain linked to ad servers, trackers, analytics, etc., this is not a good solution: **You can't easily un-break web pages with a [hosts file](http://en.wikipedia.org/wiki/Hosts_(file)) at OS level.** With hosts file under control of µBlock, it is possible to un-break web sites: a user can just disable µBlock for the web site which breaks, or an exception filter can be created to counter the blocking of a specific hostname appearing in a hosts file.