Finally I have tracked down my #Qutebrowser issue that only seemed to mess with #DuckDuckGo search results returning an 400 Bad Request It seems in my config.py I had the following user agent line.
@justine i don't know whether running javascript adds another step and maybe there was a malfunction in that step. i use tor browser (safest setting) and it disables any javascript, and it works. i must admit that i dont use ddg much these days tho so maybe it does redirection links from time to time, when it wants to learn more.
i HAVE found another set of concerning issues tho, that relate mostly to privacy.... they will be forthcoming
@stefano@justine TIL the alleged paragon of privacy, #duckduckgo, not only redirects visitors off their onion site when u visit it (at least it does with js disabled, which is the safest way to use #torbrowser), but ddg also have a separate domain (external-content.duckduckgo.com) for serving the little icons alongside each search result, and that is put through THE CLEARNET!! This means that if an entity happened to provide the guard and exit node then they can possibly track the user even if they are using tor browser!
oh and #ddg is served from #microsoft servers (m$ has military contracts so make of that what u will)
who wants succulent roasted duck? because im in my right mind to rake some burning hot coals over this duck, does it deserve to be lauded as highly as it has been. I say NO. Dear @torproject can u c this? do we need to do a call to action to help other search engines take pride of place in tor browser?