4 ms·
It's a fine suggestion. If it breaks the site, then I'd call that a broken website and move on. Maybe next time someone points me there, they'll have fixed thei
by tasha0663 5y ago
It's a fine suggestion. If it breaks the site, then I'd call that a broken website and move on. Maybe next time someone points me there, they'll have fixed their critical issue for users who block tracking proxies.
I'm okay with not being in the target audience of sites that really want to do this. I've got enough other things to do at less hostile places that my FOMO isn't triggered in the least.
- gigel82 5y agoHow do you identify tracking proxies though? When everything is going through the same domain you don't even know if data is being sent to Google, it's all a server-side black box.
- aembleton 5y agoBy using Cname uncloaking that uBlockOrigin can do on Firefox. It should see that the real domain is Google Tag Manager.
- thejohnconway 5y agoI think the article mentions that Google recommends against using Cname for this, and using A records instead.
- tasha0663 5y ago> Google recommends against using Cname for this So use Cname? :D
- thejohnconway 5y agoSites want the ads to get through, right? So they’re going to do the thing that makes that happen: A records.
- pixeldetracking 5y agoublock origin has actually an experimental option for this: https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#header https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#... only issue with blocking the proxies is that you can now decide to host the container on your own infra through docker, and it's documented by Google: https://developers.google.com/tag-platform/tag-manager/server-side/manual-setup-guide https://developers.google.com/tag-platform/tag-manager/serve... I guess this is very interesting for many people, especially in Europe with the "Google Analytics ban"