3 ms·
Right now it's very easy to see, the companies are not hiding it at all. They send the data to third-party trackers straight from their website or application.
by speedgoose 6y ago
Right now it's very easy to see, the companies are not hiding it at all. They send the data to third-party trackers straight from their website or application.
- EGreg 6y agoDisqus loads a million external resources That’s so stupid, why not just take your OWN cookie and use it in the backend to send to all these resources, proxying through your own server or having a CNAME for theirs under your domain?
- speedgoose 6y agoI guess it's often much simpler and cheaper to not try to hide it. The CNAME practice is becoming more and more common. See https://blog.apnic.net/2020/08/04/characterizing-cname-cloaking-based-tracking/ https://blog.apnic.net/2020/08/04/characterizing-cname-cloak... or https://medium.com/nextdns/cname-cloaking-the-dangerous-disguise-of-third-party-trackers-195205dc522a https://medium.com/nextdns/cname-cloaking-the-dangerous-disg... or https://www.laquadrature.net/2020/10/05/le-deguisement-des-trackers-par-cname/ https://www.laquadrature.net/2020/10/05/le-deguisement-des-t... I think proxying or doing it server side only will be implemented later when these people will be forced to hide to save their shitty business model.
- Sayrus 6y agoCNAME cloacking has gone even further, ad company now ask you to put a A/AAAA record pointing to one of their IPs as CNAME uncloaking was working pretty well.
- _-david-_ 6y agoI think the move will be for ANAME records. ANAME is not a real record (yet), but some providers are supporting them. It is similar to a CNAME record but instead of storing the domain name you want to map to it pulls the A record and puts that IP as your A record.