From 21e28bb56b0929952c0c982a06b0fb69c44e4bc6 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 24 Aug 2014 05:38:05 -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 34031f7..24b8246 100644 --- a/Counterarguments.md +++ b/Counterarguments.md @@ -17,7 +17,7 @@ Memory and CPU cycles are finite resources. A sure way for a developer to **not* µBlock supports the parsing/enforcing of hosts files, and ships with a couple of them. One of them, _"Peter Lowe’s Ad server list"_ is enabled out of the box. -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 not a single net request would ever reach such remote server. +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.