It aggregates searches from other search engines. You can specify a specific search engine to search with a !-shortcut, e.g. "!go your search query" to just search Google.
More info: https://asciimoo.github.io/searx/
Onion link for searx.me: http://ulrn6sryqaifefld.onion/
In any case, thanks for the link; I'll give StartPage a go for a week and see if it sticks.
This has been a keen interest of mine the last few months, and I will be releasing my own open source search engine which basically a collection of linked docker containers (solr, scrapy, Django, workers).
Certainly the hard road ahead will be relevancy and broad crawling.
 - http://yacy.net
And duckduckgo is not owned by yahoo. It has partnerships with yahoo, bing and yandex to use their search databases.
I am not sure that partnership or ownership really changes anything. But I hope I am wrong about it. :)
It changes everything. DDG is a Yahoo customer and, as adrusi wrote, sources search data from them among other providers. Yahoo doesn't control DDG, its privacy measures, data collection, or product direction as they would as a parent company. The relationship is completely different.
I do agree with you about Searx having the optional self-hosting advantage. DDG claim they won't track you, but there's really no way to be certain.
 - https://duck.co/help/company/yahoo-partnership
And since they're aggregating from other search engines, won't they eventually reach a point where they're running out of API requests?
They could use something like a count-min sketch to store how many requests a certain IP has executed, and clean the sketch every minute, for example.
The limit would not be exact, though.
Somewhat relatedly, I wonder when the right to digitally remember what the browser has seen (and create one's own database and automation and share synthesized results) will become a thing for individuals.
I've wondered about this (specifically in the context of DDG and Bing, but more generally). You say "another wack-a-mole game" (emphasis mine), so I guess that it's happened before, but I don't know of any occurrences. Has it happened that search engines have blocked this sort of large-scale aggregator/re-director type access?
We need to go deeper.
Turns out Wikipedia has a nice list of search engines. Didn't realize there's so many but not surprised given lower barrier-to-entry.
There's also a list of possible engines to support on their wiki:
The Internet Archive is on there - I'm sure they'd appreciate a pull request adding it!
The client and server don't support a common SSL protocol version or cipher suite.
from Chrome's dev console:
www.searx.me/:1 This site requires a DHE-based SSL cipher suite. These are deprecated and will be removed in M52, around July 2016. See https://www.chromestatus.com/feature/5752033759985664 for more details.
Disclaimer: I used to work there.