1
0
mirror of https://github.com/gorhill/uBlock.git synced 2024-07-05 11:37:01 +02:00

Short names

neonItem 2022-02-06 20:05:52 +02:00
parent 735bf08ea9
commit 58f29fe654

@ -2,7 +2,7 @@ TL;DR: Do **not** rely on the number shown over an extension badge to judge bloc
***
For both Adblock Plus and uBlock (and many other such extensions), the badge on the icon reports the number of net requests blocked by the extension.
For both Adblock Plus (ABP) and uBlock Origin (uBO) (and many other such extensions), the badge on the icon reports the number of net requests blocked by the extension.
Sometimes, for the same page, one extension can report more stuff blocked than the other, while the reality could be the opposite.
@ -14,11 +14,11 @@ If you don't want to run a benchmark, I have this [little online tool](http://ra
Clear the browser cache by right-clicking somewhere in the _Network_ tab console. Force a reload of the web page, then right-click in the _Network_ tab console, and select _"Copy all as HAR"_. Then paste the result in the text area of [this online tool](http://raymondhill.net/httpsb/har-parser.html), and click _Parse_. You will be shown the hostnames which were hit by the browser for the particular page you loaded.
For example, for the front page of <https://www.cnet.com/>, **uBlock shows 10 requests blocked**, while **ABP shows 16 requests blocked** (both with a lot of filter lists). However here is what really happened internally:
For example, for the front page of <https://www.cnet.com/>, **uBO shows 10 requests blocked**, while **ABP shows 16 requests blocked** (both with a lot of filter lists). However here is what really happened internally:
Remote servers reached:
Adblock Plus
ABP
- dw.cbsi.com
- cnet3.cbsistatic.com
- cnet4.cbsistatic.com
@ -33,7 +33,7 @@ Adblock Plus
- dw.cbsimg.net
- geo.query.yahoo.com
uBlock:
uBO:
- dw.cbsi.com
- cnet3.cbsistatic.com
- cnet4.cbsistatic.com
@ -41,7 +41,7 @@ uBlock:
- urs.cnet.com
- www.cnet.com
So uBlock caused the browser to hit many less remote servers, meaning it blocked more, and yet its badge displayed a lower number of requests blocked.
So uBO caused the browser to hit many less remote servers, meaning it blocked more, and yet its badge displayed a lower number of requests blocked.
So the point is, do not rely on the badge to judge blocking power, i.e. to assess how well your privacy is protected, you would fool yourself big time.