I actually do one better: I use the Feedback link at the bottom of the bogus search results to formally tell DDG about my bad experience. After having done that

I actually do one better: I use the Feedback link at the bottom of the bogus search results to formally tell DDG about my bad experience. After having done that for years with no improved outcome, it sure does feel like spitting into the wind, but it also has a higher probability of change than just swearing at my monitor I wish people would save and share with us these supposed failed DDG queries https://duckduckgo.com/?q=%22docker%22%20%22unable%20to%20find%20user%22%20%22invalid%20argument%22&ia=web https://duckduckgo.com/?q=%22docker%22%20%22unable%20to%20fi... Contrast that with the !g of the same query And after grinding on search permutations this was what I was looking for: https://github.com/portainer/portainer/issues/4319#issuecomment-690204016 https://github.com/portainer/portainer/issues/4319#issuecomm... Or this would have been fine, too: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1764964.html https://www.mail-archive.com/debian-bugs-dist@lists.debian.o... Maybe people who are unhappy with DDG results are just extraordinarily technical, but in the absence of a regex powered search engine, the least DDG could do is honor my quotes and index GitHub issues and major Linux mailing lists (I have some sympathy for not finding that mailing list entry since it is only hours old, but I know for certain that GitHub offers a firehose stream of events that will proactively tell DDG of changes, no crawling required)