prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

ABP naming convention, grammar / rewording fixes, formatting fixes

q1800 2022-04-13 22:41:16 -05:00
parent 2c09d382e9
commit 19bcb530a6
1 changed files with 18 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
uBlock-and-others:-Blocking-ads,-trackers,-malwares.md

@ -1,21 +1,18 @@
Hard data, not hype.
Here is the factual data with no hype.
Latest benchmark: 16 February 2015 ([raw data spreadsheet](https://github.com/gorhill/uBlock/blob/master/doc/benchmarks/privex-201502-16.ods)). (Previous: [2014-09-30](https://github.com/gorhill/uBlock/blob/master/doc/benchmarks/privex-201409-30.ods), [2014-07-22](https://github.com/gorhill/uBlock/blob/master/doc/benchmarks/privex-201407-22.ods))
This benchmark is to measure privacy exposure, by counting the number of **distinct 3rd-party domains** which
have been hit by net requests during the benchmark. The lower the number of distinct 3rd-party domains hit, the better.
This benchmark measures privacy exposure by counting the number of **distinct 3rd-party domains** hit by net requests. The lower the number of these 3rd-party domains, 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 being hit (and leaving a trace in the servers' logs).
Some benchmarks measure the number of requests blocked, which I think is of no interest as a usable measurement of privacy exposure. The number of requests blocked is no guarantee of less distinct 3rd-party domains hit (and leaving a trace in the servers' logs).
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.
My opinion is that the direct measurement of the number of distinct 3rd-party domains that get hit is much better and more relevant for privacy protection efficiency.
uBlock Origin (uBO) and Disconnect required no extra configuration steps. Other blockers required configuration. The one requiring the most configuration for that benchmark was Adblock Plus.
uBlock Origin (uBO) and Disconnect required no extra configuration steps. Other blockers required configuration. The one requiring the most for that benchmark was Adblock Plus (ABP).
![Privacy benchmark graph](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/benchmarks/privex-201502-16.png)
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.
Caveat: the definition of a "3rd-party" is a domain not matching the web page. 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 using no blocker.
The URLs (84) from the [reference benchmark](./Reference-benchmark) were used.
@ -28,7 +25,7 @@ Results -- figures are "3rd party / all". Ordered from least 3rd-party hits to m
- Outbound cookies: 58 / 269
- Net requests: 3,987 / 7,956
#### Adblock Plus 1.8.10
#### ABP 1.8.10
- Distinct 1st-party/3rd-party pairs: **497**
- Scripts: 1009 / 1733
@ -58,21 +55,19 @@ Results -- figures are "3rd party / all". Ordered from least 3rd-party hits to m
### Notes
The figures show the number of requests **allowed**, thus lower numbers are better.
The point is to count the number of distinct 3rd-party/1st-party pairs after running
the reference benchmark (two repeats in the current instance).
The figures show the number of requests **allowed** and lower numbers are better. The point is to count the number of distinct 3rd-party/1st-party pairs after running the reference benchmark (two repeats in the current instance).
The less distinct 3rd-party/1st-party pairs, the better.
### Data diffs
This shows the differences in what was **not** blocked. If something appears on side A but not on side B, this mean side B blocked something not blocked by side A, and vice versa.
These show the differences in what was **not** blocked. If something appears on side A but not on side B, it means side B has blocked something not blocked by side A and vice versa.
- uBO/ABP: https://www.diffchecker.com/czy6h5lq
- uBO/Ghostery: https://www.diffchecker.com/zapbh5b9
- uBO/Disconnect: https://www.diffchecker.com/386c367m
These diffs may help you in deciding whether you should complement uBO with another blocker, though keep in mind you can always ask uBO to block more (dynamic filtering may come handy for this).
These diffs may help you decide whether you should complement uBO with another blocker, though remember you can always ask uBO to block more (dynamic filtering may come in handy for this).
### Observations
@ -84,7 +79,7 @@ Using the data diffs, one can observe that with uBO + default settings, there ar
- `twitter.com` (34)
- `taboola.com` (11)
So if this concerns you (it should), I would say the best way to foil these is to use [dynamic filtering](./Dynamic-filtering). Here are the rules, which will block all these 3rd-parties, except when used as 1st-party:
So if this concerns you (it should), I would say the best way to foil these is to use [dynamic filtering](./Dynamic-filtering). Here are the rules that will block all these 3rd-parties, except when used as 1st-party:
* facebook.com * block
* facebook.net * block
@ -95,25 +90,24 @@ So if this concerns you (it should), I would say the best way to foil these is t
facebook.com facebook.net * noop
twitter.com twitter.com * noop
With these few dynamic filtering rules, you would lower the _"distinct 1st-party/3rd-party pairs"_ figure for uBO to 318 (from 491). As a bonus, pages will load markedly faster.
With these few dynamic filtering rules, you would lower the _"distinct 1st-party/3rd-party pairs"_ figure for uBO to 318 (down from 491). As a bonus, pages will load markedly faster.
Any of the blocked domains above can easily be unblocked for a specific site. For example, if ever you want Twitter widgets to work when visiting AnandTech, just set `twitter.com` to a local _noop_ for that site, a mere point-and-click when using the dynamic filtering matrix.
You can unblock any blocked domains above for a specific site. For example, if ever you want Twitter widgets to work when visiting AnandTech, just set `twitter.com` to a local _noop_ for that site, a mere point-and-click when using the dynamic filtering matrix.
### Methodology
All blockers were configured in such a way as to compare apples-vs-apples:
All blockers got configured in such a way as to compare apples to apples:
- **Ghostery:** Select all trackers except "Widgets". _"GhostRank"_ not checked. _"Update now"_ clicked (and ensured whatever new filters were used).
- **Ghostery:** Select all trackers except "Widgets". _"GhostRank"_ unchecked. _"Update now"_ clicked (and ensured that it used any new filters).
- **uBO:** Out-of-the-box settings -- no change.
- **Adblock Plus:** _"EasyList"_ + _"EasyPrivacy"_, _"Peter Lowe's list"_, _"Malware Domains"_ checked. _"Acceptable ads"_ unchecked. _"Update now"_ clicked.
- **ABP:** _"EasyList"_ + _"EasyPrivacy"_, _"Peter Lowe's list"_, _"Malware Domains"_ checked. _"Acceptable ads"_ unchecked. _"Update now"_ clicked.
- **Disconnect:** Out-of-the-box settings -- no change.
Browser settings (if you mind your privacy, there is no way around these settings):
- _"Click to play"_ enabled.
I forgot to check _"Block third party cookies and site data"_, so 3rd-party cookies were allowed during the benchmark.
I forgot to check _"Block third-party cookies and site data"_, so 3rd-party cookies were allowed during the benchmark.
[Sessbench](https://github.com/gorhill/sessbench) was used to run the benchmarks,
and each extension was tested as the only extension active in the browser.
[Sessbench](https://github.com/gorhill/sessbench) performed the benchmarks. Each extension was tested alone, with no other extensions enabled in the browser.
The official [Public Suffix List](https://publicsuffix.org/list/) is used to determine the domain of a URL.