Someone brought this up in my repo that searx.me no longer exists, so either we need another instance or another search engine.
I suggest using search.disroot.org, it's the best instance I've seen so far
Instances can change at any time and experiences will wary. For example, I tried the suggested engine and got no results two times in a row (third time worked).
Hence I suggested using a different engine altogether, such as Qwant.
Actually when I tried to add Qwant in latest build I noticed that it was already added in UC, just not got listed as search engine in any of the languages. I will make a PR here when I have time.
How can we decide which instance to have as default? There are a number of them on https://searx.space/ and after reviewing many discussions about it online, nobody really has a definitive answer.
Outside of doing some sort of filtering based on jurisdiction, cryptcheck TLS grade, and perhaps other fields, we are arbitrarily choosing one over another.
I've seldom used searx instances鈥攎ainly searx.me鈥攂ecause it was often unusable.
I'm currently using MetaGer and it seems to be quite functional. Not only have I not ever yet experienced it not showing any results, but its search results with queries in East Asian languages (tested Korean and Japanese) is superior over both default SearX search and with their inconvenient language specification settings set. I expect it to be equivalently better in European Asian language queries and have better chance to improve, considering it's developed in European Asia. It seems it's developed mainly by German devs, so there may be some German jargon here and there, but being an open source software under AGPLv3, I suggest it as a candidate.