CDNs are server side trackers. Even when not serving up browser side tracking code that makes yet more requests (which they often do), they're collecting locati

CDNs are server side trackers. Even when not serving up browser side tracking code that makes yet more requests (which they often do), they're collecting location and other data based on response times and headers. Google's gv2 beacons, newrelic, cloudflare, etc. This is why tools like decrentral-eyes exists. Unfortunately, tools like actually introduce additional unique identifiers. Even with Javascript disabled, web fonts are tracking you. Even with javascript and web fonts disabled, images and CSS are tracking you. Even first-party images and CSS track you, even over VPNs and Tor. First class web experiences that can't track are only possible by routing all traffic through a trusted remote privacy-by-design pre-caching hash table, like via a trusted IPFS node. Then you also need to only transact with the non-web (e.g. server hosting) service over a routeless protocol. The latter requires the service to support non-custodial routeless protocols for payment and control. This is something dApps do well. It sounds complicated, but every Web3.0 (not to be confused with Web3.js) service already supports this by necessity, even in outdated browsers, simply by choosing a trusted node and updating your browser or device's DNS and proxy settings. No additional software required.