Actually I´m trying to understand a little bit more about tracking. During that activity I also found articles speaking about CDN (Coentent Delivery Networks) as a privacy threat due to metadata exchange.
- Is there any protection against CDN integrated in eblocker standard? (Some CDN protection is visible when Duck Duck Go Tracker Radar is activated!)
- If there is no CDN threat protection in eblocker standard is there any recommendation to install Decentraleyes or LocalCDN, which are CDN emulators?
Thanks for your feedback!
With the eBlocker standard filters our approach is a balance between tracking protection and convenience so most sites still work as expected.
Using the DuckDuckGo tracker filter in addition will cover you from (most) CDN tracking - but it will also break some sites as CDNs are quite common with major Internet services.
The choice is yours 😉
Thanks for your comment!
As far as I understand the approach of DuckDuckGo and LocalCDN/Decentraleyes is different.
- DuckDuckGo is blocking CDN.
- LocalCDN/Decentraleyes are replacing CDN with local ressources.
That‘s only partly correct. eBlocker replaces blocked „standard scripts“ with so called surrogates. This keeps the site working while the original script is replaced locally.
Maybe the surrogates developer @mainzelM (who is also the inventor of the duckduckgo filter compiler) can help with more details here? 🤔