DuckDuckGo browser seemingly sends domains a user visits to DDG servers
1–10 of 531 posts
Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#2Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#3Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#4Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#5They should probably change the behavior to how it’s suggested in the thread, but I’m still going to use DDG over alternatives for the bang feature.
Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#6Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#7Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#8Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#9Re: DuckDuckGo browser seemingly sends domains a user visits to DDG servers
#10This makes sense to me and is not alarming. Getting favicons actually is difficult to do robustly; many applications and websites use Google's service to do so, which then leaks the request to Google: https://www.google.com/s2/favicons?domain=ycombinator.com
Putting this logic in the client is not feasible. You want to send requests directly to every shady site that shows up in your search results, load their pages in the background, work through network delays and HTTP errors, and parse out the location/format of the favicon files?
DuckDuckGo hosting this functionality themselves is also a positive. They have previously been burned when the Web of Trust service they were originally using was found to be farming data, and turned it off immediately once discovered. Processing, hosting, and serving the icon themselves prevents that from happening again.
This is not to say that DDG is perfect: links you click do seem to be redirected through a /l/ page on their domain, which can cause problems: https://lapcatsoftware.com/articles/duckduckgo.html