Updated Counterarguments (markdown)

Raymond Hill 2014-08-24 05:38:05 -07:00
parent 7efe573ada
commit 21e28bb56b
1 changed files with 1 additions and 1 deletions

@ -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 Lowes 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.