-
-
Couldn't load subscription status.
- Fork 410
Description
When we see a 3rd party tracking on a website, we block the etld+1 associated with the 3rd party.
This makes sense when we see cookie tracking, because cookies are scoped by domain.
However it does not make sense for localstorage or fingerprinting tracking. Localstorage tracking is scoped to a domain. Fingerprinting tracking is probably most easily associated with URLs (or something like them).
An example of how this might be a problem:
- we see fingreprinting tracking from a third party
https://cdn.jsdelivr.net/fingerprintjs2/1.5.,1/fingerprint2.min.js - we block
jsdelivr.net - this breaks stuff so we add
jsdelivr.netto the cookieblock list (it is actually on there) - fingerprinting tracking can now continue, just as before
So we didn't actually fix anything.
It is hard to tell how big of an issue this is, since we don't get information about why a thing was blocked (related to #1289 #963), but we should keep this in mind as we develop a new action_map.