|
|
##### Where can I see how it impacts my network activity?
|
|
|
|
|
|
There's a [testing tool](http://formble.nl/test-decentraleyes), but you can also use Firefox's built-in network monitor to view all requests made in the course of loading a page. Lastly, by default, Decentraleyes marks locally fetched resources by prepending comments to them.
|
|
|
|
|
|
##### Why doesn't it deliver resources from CDNs I block using a different add-on?
|
|
|
|
|
|
Once a different add-on cancels a request, there's nothing left for Decentraleyes to intercept. You can solve this by white-listing the domain and making Decentraleyes block requests for missing resources.
|
|
|
|
|
|
##### Can CDNs track me even though they do not place tracking cookies?
|
|
|
|
|
|
Absolutely. Requests to content delivery networks contain a "Referer" HTTP header that reveals what page you're visiting. Techniques like IP address tracking and [browser fingerprinting](https://panopticlick.eff.org/browser-uniqueness.pdf) can be used to determine your identity.
|
|
|
|
|
|
##### My browser caches downloaded CDN libraries, doesn't that protect my privacy?
|
|
|
|
|
|
Sadly, no. Even if the file in question is stored inside your cache, your browser will still contact the delivery network to see if the resource has been modified. Decentraleyes solves this issue. |
|
|
\ No newline at end of file |