From 95a8df567493c9d976e4428e1d00b06f308edd74 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 14 Jul 2014 21:45:14 -0700 Subject: [PATCH] =?UTF-8?q?Updated=20=C2=B5Block=20vs.=20others:=20Blockin?= =?UTF-8?q?g=20ads,=20trackers,=20malwares=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- µBlock-vs.-others:-Blocking-ads,-trackers,-malwares.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/µBlock-vs.-others:-Blocking-ads,-trackers,-malwares.md b/µBlock-vs.-others:-Blocking-ads,-trackers,-malwares.md index e412c62..f8777f2 100644 --- a/µBlock-vs.-others:-Blocking-ads,-trackers,-malwares.md +++ b/µBlock-vs.-others:-Blocking-ads,-trackers,-malwares.md @@ -6,7 +6,7 @@ This benchmark is to measure privacy exposure, by counting the number of **disti have been hit by net requests during the benchmark. The lower the number of distinct 3rd-party domains hit, the better. Some benchmarks measure the amount of requests blocked, which I think is of no interest as a useful -measurement of privacy exposure. The number of requests blocked is no guarantee of less distinct 3rd-party domains. Measuring directly number of distinct 3rd-party domains is a much better and relevant measurement. +measurement of privacy exposure. The number of requests blocked is no guarantee of less distinct 3rd-party domains being hit (and leaving a trace in the server log). Measuring directly number of distinct 3rd-party domains is a much better and relevant measurement. Results -- figures are *3rd party* / *all*. Ordered from least 3rd-parties hits to most 3rd-parties hits: