4 ms·

I've just logged in to my DigitalOcean account and, while Privacy Badger does block a load of connections, I don't see any for Google Ads or Facebook. Most of t

by spzb 6y ago

I've just logged in to my DigitalOcean account and, while Privacy Badger does block a load of connections, I don't see any for Google Ads or Facebook. Most of the ones I do see are for CDNs.

kemonocode 6y ago
Just did the same, and likewise here. I wonder if it's just a product of A/B testing or, more alarmingly, that person has malware injecting ads into any websites they browse which then Privacy Badger proceeds to block.
- kimi 6y ago
  Don't think so. The list looks pretty legit (was posted separately).
- spzb 6y ago
  Are you in the EU by any chance? Just wondering if it’s a GDPR thing
MacsHeadroom 6y ago
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.

by spzb 6y ago

I've just logged in to my DigitalOcean account and, while Privacy Badger does block a load of connections, I don't see any for Google Ads or Facebook. Most of the ones I do see are for CDNs.

kemonocode 6y ago

Just did the same, and likewise here. I wonder if it's just a product of A/B testing or, more alarmingly, that person has malware injecting ads into any websites they browse which then Privacy Badger proceeds to block.

kimi 6y ago
Don't think so. The list looks pretty legit (was posted separately).
spzb 6y ago
Are you in the EU by any chance? Just wondering if it’s a GDPR thing

MacsHeadroom 6y ago

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.