1st-party tracker blocking #476
Comments
|
Hey @gurgunday! We are following these developments very closely. We're still assessing what the best course of action should be and how big of a privacy issue this first-party DNS method is. But we will update you on the status ASAP. You can be assured that if something needs to be fixed we will push an update very soon. Thanks for opening an issue! Rémi |
|
Seems like a security concern as well as a privacy concern. Yet all the major tracker companies have started to support it. |
Yes indeed. Not sure if you noticed but @konark-cliqz who wrote the tweet is a co-worker of mine at Ghostery/Cliqz and we are currently running an in-depth investigation of all negative consequences that 1st party tracking can have. In parallel, we have already developed some tooling to automatically and continuously uncover usage of this pattern across the Internet to generate blocking rules that can be used by Ghostery and Cliqz to block this tracking; it is only a first-step. We are also exploring ways to leverage our search engine to help discover 1st party tracking at scale. We already crawl the Web and have access to content of millions of domains in our index; this puts us in a unique position to run analysis truly at scale and in real-time to inform our tracking protection. We will keep you posted about development soon but we expect protection against 1st-party tracking to ramp up in the coming days. Cheers, |
|
Wow, I sure hadn't noticed that! Seems like Cliqz really has a great team that knows what they are doing. Thanks for your answer and as always, keep up the great work. |
|
The latest release of uBlock Origin seems to have fixed this issue. |
Hey, sorry for not updating the ticket earlier. We have released this "fix" already in Cliqz browser last November and it is in the pipeline for next Ghostery release as well. In the meanwhile we also pushed custom rules to all Ghostery users. We analyze websites on the backend to detect cases of 1st party tracking and create custom rules to block these. The rules have been pushed last November as well so Ghostery users are protected, but the CNAME trick will be deployed too, soon. This CNAME trick only works on Firefox, though, whereas the custom rules that we already push also protect Ghostery users on Chrome. |
|
Thanks a lot for the update! We should obviously close the issue then. Good thing I use Cliqz Browser at home, I'd love to support Ghostery with a subscription on Firefox. However, unfortunately it’s not available in many countries. |
Since a week or so, cases of 1st-party tracking that seem to be unblockable started appearing. There have been discussions on places such as uBlock Origin's GitHub page. (More can be found here)
Is Ghostery equipped to handle these first party tracking scripts and if not, is there anything that can be done to prevent this kind of tracking at all?
The text was updated successfully, but these errors were encountered: