|
|
|
|
|
by SudoNick
4427 days ago
|
|
In order to be effective against the numerous tracking techniques that are in use, the extension MUST block requests. If you aren't breaking many popular websites as a result of blocking their third party requests then it is your own privacy that gets broken. So this concerns me: "In some cases a third-party domain provides some important aspect of a page's functionality, such as embedded maps, images, or fonts. In those cases, Privacy Badger will allow connections to the third party but will screen out its tracking cookies." |
|
This pull request will also apply the whitelisting to subdomains of the domains on the whitelist: https://github.com/EFForg/privacybadgerfirefox/pull/63.
Unfortunately blocking all those sites and making users whitelist them manually is a lot of work for most users. So we ship a whitelist.