Updated Reference benchmark: comparative results (markdown)

Raymond Hill 2015-07-27 09:01:25 -04:00
parent 8b7755924c
commit 6f2da3ef1d

@ -30,7 +30,9 @@
#### Raw data
The `3rd-party domains` section is _[3rd-party] [1st-party]_, and ordered by 3rd parties. This allows you to assess how much some specific 3rd-parties are able to create a profile of your browsing history. Notice that in medium mode, most 3rd-parties are actually auxiliary domains which are related to the 1st-party, which means that actual 3rd-party profiling has been essentially foiled.
The `3rd-party domains` section is _[3rd-party] [1st-party]_, and ordered by 3rd parties. This allows you to assess how much some specific 3rd-parties are able to create a profile of your browsing history.
Notice that in medium mode, most 3rd-parties are actually auxiliary domains which are related to the 1st-party, which means that actual profiling by 3rd parties has been foiled to a great extent. At this point, it's a matter of selectively blocking the remaining 3rd parties which might be deemed undesirable by a user (for example, blocking `gravatar.com`, `fonts.googleapis.com`). Hard mode will actually ensure that profiling by 3rd parties is completely foil, though at the expense of having to fix most web sites. For privacy-minded users, _medium mode_ seems to be the optimal approach.
- [No blocking](#no-blocking)
- [Very easy mode](#very-easy-mode)
@ -4181,4 +4183,4 @@ The `3rd-party domains` section is _[3rd-party] [1st-party]_, and ordered by 3rd
wp.com thechive.com
wsj.net marketwatch.com
wsj.net wsj.com
yimg.com yahoo.com
yimg.com yahoo.com