4 ms·
This is self-hosted, so I'm assuming it's running under the assumption that each person hosts their own instance and uses that instance. The number of queries c
by VoidWhisperer 9y ago
This is self-hosted, so I'm assuming it's running under the assumption that each person hosts their own instance and uses that instance. The number of queries coming from the instance in that case wouldn't look too out of the ordinary.
- lawl 9y agoThen that defeats the purpose of trying to be privacy focused if your search queries aren't mixed with other people's queries.
- y4mi 9y agoI can't grasp how you got that idea. Do you not know what self-hosted means? the engine craws the web and saves its data locally. this locally saved data can be queried/searched. So yes, in your search engine, there will only be your own searches. But these searches are only visible to your own servers/services.
- jbg_ 9y agoThis is not how searx works.
- halflings 9y ago> I can't grasp how you got that idea. By reading the link? > the engine craws the web and saves its data locally ...Saves an index of the whole web, locally? This is not what SearX does. It queries other search engines.
- y4mi 9y agoyes, i mixed up the engines and commented without verifying which it was. i'm sorry for that. i just thought it wasn't necessary to edit as somebody sufficiently pointed out how mistaken i was 9 days ago.
- jbg_ 9y agoI also run searx self-hosted, configured to proxy all its queries through Tor. Occasionally one of the engines doesn't return results (probably due to blocking), which is barely noticeable since several others still work, but normally all the engines including Google return results. Since searx doesn't store cookies returned by the search engines, and I'm using it through Tor, I think this is a significant improvement over sending all my search queries to Google directly from my laptop.