Reviews for DuckDuckGo Search & Tracker Protection
DuckDuckGo Search & Tracker Protection by DuckDuckGo
Review by Firefox user 13707739
Rated 1 out of 5
by Firefox user 13707739, 7 years agoBad tracking protection!
It doesn't block lots of trackers.
* Nope, no extension conflicts.
* I didn't look numbers. I took into account just what your own extension detailed as blocked. And sadly, your extension didn't catch several trackers.
* I read your extension uses something from EasyList + something from Disconnect + something from you. Well, something went wrong, and nope, your extension doesn't catch trackers and webgarbage as other extensions catch. Your extension has a poor tracking protection.
It doesn't block lots of trackers.
* Nope, no extension conflicts.
* I didn't look numbers. I took into account just what your own extension detailed as blocked. And sadly, your extension didn't catch several trackers.
* I read your extension uses something from EasyList + something from Disconnect + something from you. Well, something went wrong, and nope, your extension doesn't catch trackers and webgarbage as other extensions catch. Your extension has a poor tracking protection.
Developer response
posted 7 years agoWould it be possible to reach out to us directly to better understand what is going on? You can email open at duckduckgo.
We are using the same filter lists as other extensions in addition to our own changes, and so we should be blocking similarly and are in all our tests. If you’re not seeing that it could be because you have multiple blocking extensions installed and we are not seeing those requests. In any case, would love to get to the bottom of it if you don’t mind reaching out.
We should also point out you shouldn’t look at numbers because one thing we did to be more informative is group requests into tracker networks. So, for example, if there were 50 trackers from the same network, it would only count as 1 tracker network blocked, but we block all 50 requests.
We are using the same filter lists as other extensions in addition to our own changes, and so we should be blocking similarly and are in all our tests. If you’re not seeing that it could be because you have multiple blocking extensions installed and we are not seeing those requests. In any case, would love to get to the bottom of it if you don’t mind reaching out.
We should also point out you shouldn’t look at numbers because one thing we did to be more informative is group requests into tracker networks. So, for example, if there were 50 trackers from the same network, it would only count as 1 tracker network blocked, but we block all 50 requests.