Cname cloaking, a disguise of third-party trackers

Re:Cname cloaking, a disguise of third-party trackers by ignoramous on Saturday November 23, 2019 @04:30PM (#21616705)

Instead of websites deploying reverse-proxies to tunnel ads through, Google has entire websites tunnel through their edge via AMP. Wouldn't surprise me if BigTech gets together and introduces standards that open up more avenues for CDNs to take away even more control and monetize the traffic they serve, on their terms.

Google has pretty much checkmated content-blockers in that they control the servers, the OS, and the clients used by an overwhelming majority internet users and service providers, alike.

[ Parent | on HN ]

Re:Cname cloaking, a disguise of third-party trackers by earthboundkid on Saturday November 23, 2019 @09:56PM (#21618056)

TBF, Google is probably going to be broken up in the next five years and AMP will be exhibit A at the trial.

[ Parent | on HN ]

Re:Cname cloaking, a disguise of third-party trackers by peteretep on Sunday November 24, 2019 @12:55AM (#21618672)

I guess we get to the point where the content blockers load the scripts, and run heuristics on them before loading them, and perhaps running an adaptive real-time blacklist?

[ Parent | on HN ]

Re:Cname cloaking, a disguise of third-party trackers by takeda on Sunday November 24, 2019 @02:47PM (#21622831)

I hate AMP but maybe it is ad blockers, but I believe I can count on my fingers how many times I visited an AMP page.

[ Parent | on HN ]