4 ms·
The obvious solution is to block the server-side pages that the CSS elements link to. This kind of tracking can be mitigated the same way any other kind of trac
by nukeop 9y ago
The obvious solution is to block the server-side pages that the CSS elements link to. This kind of tracking can be mitigated the same way any other kind of tracking is already handled by uBlock or uMatrix.
- supermdguy 9y agoWouldn't that require a separate blacklist for each site?
- nukeop 9y agoProbably not everyone would be willing to create their own user tracking solutions, most websites use third party analytics, which can be handled by generalized rules. For those that do roll their own solutions, per-website block lists would be needed, but that's how site-specific adblocking already works. The lists are maintained by the community and updated very frequently.
- supermdguy 9y agoOh, that's true. I wasn't really thinking about third party solutions.
- ams6110 9y agouBlock and a hosts file are standard on every computer I own.
- kalcode 9y agouBlock can't block manual tracking...just third-party scripts that do it. Example: You visit example-site.com example-site.com is the php server that sends you the html. It also the site that does the tracking. So when you click something it sends that data to example-site.com and then it can forward the data to a third-party tracking service. If you blocked or used host files on the server-side pages then the site example-site.com would be completely blocked too. Ultimately if everyone uses ad-blocks to block tracking script they can be added to the back end. If you block the back-end you effectively block the website you are accessing in the first place.
- nukeop 9y agoIf it's all moved to the backend, then we win, because then we can easily control what data is being collected.