Skip to content
This repository was archived by the owner on Oct 2, 2023. It is now read-only.

Update README.md #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,13 +93,11 @@ In the screenshot below, the most ubiquitous 3rd party is `google-analytics.com`

***

Notice that there are two 3rd-party exposure scores. The larger one is the actual 3rd-party exposure score, i.e. the score according to what **actually** occurred during page load.
Notice that there are two 3rd-party exposure scores. The larger one is the **unfiltered** 3rd-party exposure score, i.e. the score according to what would have been loaded without a content filter. It represents the 3rd-party exposure you would have **minimally** subjected yourself to if no network request had been blocked when the page loaded. The smaller one is the **filtered** 3rd-party exposure score.

The smaller one is the **averted 3rd-party exposure score**. It represents the 3rd-party exposure you would have **minimally** subjected yourself if no network request had been blocked when the page loaded.
Click on either of the 3rd-party exposure scores will cause the heatmap to switch between unfiltered and filtered view. The purpose of the **unfiltered** view is to provide some sense of what would have happened if no network request had been blocked.

Click on either of the 3rd-party exposure scores will cause the heatmap to switch between actual and averted view. The purpose of the averted view is to provide some sense of what would have happened if no network request had been blocked.

Notice that I used and emphasized the word **minimally** above. This is because typically, on pages which rely on a lot of 3rd parties, quite commonly many 3rd party resources loaded in your browser will cause **more** 3rd party resources to be loaded, which resources could not be seen by uBO-Scope when resources from the first wave of 3rd parties were blocked.
Notice that I used and emphasized the word **minimally** above. This is because typically, on pages which rely on a lot of 3rd parties, quite commonly many 3rd party resources loaded in your browser will cause **more** 3rd party resources to be loaded. These resources cannot be seen by uBO-Scope as the first wave of 3rd parties are blocked.

![](https://cloud.githubusercontent.com/assets/585534/23466176/5ca61714-fe68-11e6-9431-8df766719e79.png)

Expand Down