4 ms·
The problem is that DNT isn't verifiable DNT should be done in browser and in the original website by not loading the tracking scripts at all. ATM how it goes
by dogma1138 11y ago
The problem is that DNT isn't verifiable DNT should be done in browser and in the original website by not loading the tracking scripts at all.
ATM how it goes is that the DNT header is attached to outgoing requests and you "hope" that the 3rd party is discarding them.
- allendoerfer 11y agoYou do know, that you do not need a dedicated tracking script to track you serverside?
- dogma1138 11y agoEh? they know that some one accessed resource X from IP address Y that's not tracking.
- seba_dos1 11y agoThey know that someone accessed resource X from IP address Y from browser Z with language preferences A, encoding preferences B, SSL cipher suites C (when https is used), DNT preferences D, sometimes also protocol support E (when upgrading to SPDY or HTTP/2.0), having a TCP/IP fingerprint of OS F. I guess I still haven't covered it all.
- seba_dos1 11y agoExactly, that's the sole purpose and that's how DNT works. It's nothing more than a voice "I don't wish to be tracked" and an expectation to be listened to.