- Oct 9, 2016
- 6,038
Let's start with what benefits it brings to the user
1) Protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.
2) Speed optimization and bandwidth saving as they are local resources now
The question is 'How does CDNs track a user as they're not websites?'
Frequently asked questions · Wiki · Thomas Rientjes / decentraleyes · GitLab
In short, if no referer is being sent (or hidden/obfuscated) then the CDNs will not be able to track you.
And other means to track you will be likely handled by your other extensions
Secondly, as to whether there's significant savings in bandwidth and speed optimization I really doubt so. If it does significantly speed up your surfing then by all means use it.
There's setting in Chrome/FF to prevent referer being sent. Otherwise choose extension with referer control to do the job.
Some interesting read up here
Does CDN know which website the client is visiting when fetching jquery.min.js or other resource from CDN?
Decentraleyes for Firefox loads CDN resources locally - gHacks Tech News
1) Protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.
2) Speed optimization and bandwidth saving as they are local resources now
The question is 'How does CDNs track a user as they're not websites?'
Frequently asked questions · Wiki · Thomas Rientjes / decentraleyes · GitLab
Can CDNs track me even though they do not place tracking cookies?
Absolutely. Requests to Content Delivery Networks contain the "Referer" HTTP header (originally a misspelling of referrer) that reveals what page you're visiting. Techniques like IP address tracking and browser fingerprinting can then be used to associate the aggregated data with your identity.
In short, if no referer is being sent (or hidden/obfuscated) then the CDNs will not be able to track you.
And other means to track you will be likely handled by your other extensions
Secondly, as to whether there's significant savings in bandwidth and speed optimization I really doubt so. If it does significantly speed up your surfing then by all means use it.
There's setting in Chrome/FF to prevent referer being sent. Otherwise choose extension with referer control to do the job.
Some interesting read up here
Does CDN know which website the client is visiting when fetching jquery.min.js or other resource from CDN?
Decentraleyes for Firefox loads CDN resources locally - gHacks Tech News
Last edited: