Searx VS whoogle-search

I think searx was largely built by a single person.

https://github.com/searx/searx

I use Recoll to index all of it. Recoll WebUI exposes an API, which I plugged into Searx.

The quality of Google search results has been awful for many years now, but if you still want to use it, the only usable way is via a frontend like Searx[1]. Using any of Google's frontends for any of their services is an exercise in frustration from dodging ads and fighting their hostile UI.

[1]: https://github.com/searx/searx

RSS-Bridge has a Google search adapter. You can also fake it with Searx (which offers RSS feeds of search results).

I've recently wondered how effective local models were at chaining together thoughts as proposed in https://ofir.io/self-ask.pdf. Turns out they are indeed capable of doing so while also creating reasonable chains of thoughts that are easily as good as OpenAI's models. To make it completely free to run I used SearX running inside a Docker container with a second model curating the search results for the main model to get answers from the web.

Google Search → Whoogle

Google Search → Whoogle

I deployed whoogle search at home. For laptops it is rather easy to define it as the default search for alfred and the respective browser, but for iOS devices I have not found a way (except some rather clunky and intrusive extensions) to change the default search engine beyond what Apple tells you. Is there a way to to this via pfSense or pihole? So whenever someone searches in the address bar in safari on iOS that pfSense redirects that search to the whoogle URL?

I host an instance of Whoogle Search that I use and never looked back. It's like someone brought Google back to the golden age. No (direct) tracking, no ads, complete control over the results.

Source Code: https://github.com/benbusby/whoogle-search