[_zekiel]

Thanks for helping point this out! I lead community at DuckDuckGo and there are a lot more, "Instant Answers" that the world should know about. The community of open source devs really deserve a standing ovation for things like this (https://duckduckgo.com/?q=who%27s+in+space&ia=answer).

Check out the whole list of answers in development and live here: https://duck.co/ia

[anexprogrammer]

Most of what DDG is doing is great, and for a lot of things it's just as good as and often better than Google. It's really good to see how far you've come.

A few times I've found the instant answers are just plain wrong, and even though I've hit feedback they never got corrected. Hopefully you're trying to improve how you react to feedback? It's partly because you do so damn well on things like single link for a song lyric search, or just the answer snippet you need like an IP address, and highlight it better than Google that it becomes so noticeable when you do get something wrong.

I'd be hard pushed to remember a specific broken search to point you to as last time was around Christmas.

[AdamSC1]

Hey Anex,

We're actively working towards improving feedback loops. But one of the best parts about our Instant Answers is they are open source. You, or others, can help submit new answers or correct them as part of our duckduckhack.com community. Some of our information comes from partner sites via an API and so if you find something wrong there it can take a bit longer to fix as we need to reach out to them and have it updated on their end.

As a team of 35 tackling a big problem like search we count on our community for help, but we do try and react to feedback as best we can.

If you ever seen anything grossly wrong, such as vandalized information or something malicious you can also report that to us more directly. Through our Instant Answer email at [e-mail]

Lastly, we really appreciate the feedback. Since we don't track users, we only get that type of feedback when you take the time to submit it or to post it here - so I want to let you know your voice is being heard and that we are indeed working through the feedback we get. Thanks for sharing it! :)

[rizzin]

DDG team can be really slow with feedback.

Last year I submitted fixes for several bang searches, and I received an answer from them about three months later.

[agumonkey]

I didn't even know it was a "team"

[agumonkey]

But no emacs lisp, lisp, clojure, ruby, c(89|99|ansi) cheatsheets... very fishy!

[r3bl]

You're more then welcome to submit one yourself.

[agumonkey]

In progress

[agumonkey]

elisp stub https://github.com/agumonkey/ddg_elisp_cheatsheet (waiting for #emacs input about curating elisp examples, so it's mostly empty)

[Ntrails]

A month or two ago I asked for a fix to FX queries (in the wrong part of github - in fact I probably did everything wrong as I know nothing of github) - within the day someone had added the new syntax parse.

Literally magic. <3