Updated µBlock and others: Blocking ads, trackers, malwares (markdown)

gorhill 2014-09-30 19:13:13 -07:00
parent 6f3d6d9e4d
commit fd417b4b75
1 changed files with 1 additions and 1 deletions

@ -10,7 +10,7 @@ measurement of privacy exposure. The number of requests blocked is no guarantee
Measuring directly the number of distinct 3rd-party domains which were hit is a much better and relevant measurement for comparison of privacy protection efficiency in my opinion. Measuring directly the number of distinct 3rd-party domains which were hit is a much better and relevant measurement for comparison of privacy protection efficiency in my opinion.
![Privacy benchmark graph](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/privex-201409-30.png) ![Privacy benchmark graph](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/benchmarks/privex-201409-30.png)
Caveat: "3rd-party" is defined as a domain which doesn't match the domain of the web page. For sure many Caveat: "3rd-party" is defined as a domain which doesn't match the domain of the web page. For sure many
domains reported as "3rd-party" actually belong to the same entity which owns the page domain (for example, `yimg.com` is owned by `yahoo.com`). There is no way for the benchmark code to know this, unless using a comprehensive database of who owns which domain -- that is beyond my means. Still, the benchmark is useful if comparing blockers among themselves, or against when no blocker is used. domains reported as "3rd-party" actually belong to the same entity which owns the page domain (for example, `yimg.com` is owned by `yahoo.com`). There is no way for the benchmark code to know this, unless using a comprehensive database of who owns which domain -- that is beyond my means. Still, the benchmark is useful if comparing blockers among themselves, or against when no blocker is used.