It is great to have an alternative that doesn’t count on google or bing for results, but it’s NOT the best option right now. IMO, searx is the best option, but you have to choose an instance you can trust or host your own (but beware that all the engines your instance using will get your instance’s IP address).
As you’ve said, the major issue with SearX and other open source and self-hostable options is that they don’t have their own crawlers and self-hosting means giving your IP to the big tech search engines you’re pulling results from. Tor or other proxies are always an option to prevent this but they make it more likely that your search requests from Google, etc. will be blocked. For centralized search engines with better-than-average privacy policies and their own crawlers, Brave Search probably is the best option at the moment in terms of returning relevant results.
That said, I’m eagerly awaiting for an open-source, self-hostable search engine with its own crawler. We shouldn’t be satisfied with the current lackluster options.
Well yeah, it doesn’t make sense to open your own instace and use it alone, but if you make it public it won’t matter as much because they can’t know which queries are yours. It would force you to get another ip address for the server though.
The only complain I have about searx is that the owner can log stuff, which forces you to choose a public instance carefully. If instances couldn’t log it would be the perfect option IMO.
There’s no such thing as “couldn’t log” when you’re talking about an open source project. The source code can always be modified. Even if something is open-source, you’re always trusting the one hosting it with your data.
It’s cool that they have that info (hadn’t noticed it before), though it only looks at the front end code, there is no way to check for any malicious code on the back end. At the very least, logging the IP addresses that use the search engine is trivial without any changes to the front end. Actually correlating search queries to IPs would probably be harder since the query isn’t in the URLs, but maybe not that much harder, I’m not sure.
This is what I meant, SearX is only a patch to a problem that won’t be solved using SearX. Brave Search is more private than Google and at least is working on a new independent index
It is great to have an alternative that doesn’t count on google or bing for results, but it’s NOT the best option right now. IMO, searx is the best option, but you have to choose an instance you can trust or host your own (but beware that all the engines your instance using will get your instance’s IP address).
As you’ve said, the major issue with SearX and other open source and self-hostable options is that they don’t have their own crawlers and self-hosting means giving your IP to the big tech search engines you’re pulling results from. Tor or other proxies are always an option to prevent this but they make it more likely that your search requests from Google, etc. will be blocked. For centralized search engines with better-than-average privacy policies and their own crawlers, Brave Search probably is the best option at the moment in terms of returning relevant results.
That said, I’m eagerly awaiting for an open-source, self-hostable search engine with its own crawler. We shouldn’t be satisfied with the current lackluster options.
Well yeah, it doesn’t make sense to open your own instace and use it alone, but if you make it public it won’t matter as much because they can’t know which queries are yours. It would force you to get another ip address for the server though.
The only complain I have about searx is that the owner can log stuff, which forces you to choose a public instance carefully. If instances couldn’t log it would be the perfect option IMO.
There’s no such thing as “couldn’t log” when you’re talking about an open source project. The source code can always be modified. Even if something is open-source, you’re always trusting the one hosting it with your data.
You can see at searx.space if an instance changed the code he uses.
It’s cool that they have that info (hadn’t noticed it before), though it only looks at the front end code, there is no way to check for any malicious code on the back end. At the very least, logging the IP addresses that use the search engine is trivial without any changes to the front end. Actually correlating search queries to IPs would probably be harder since the query isn’t in the URLs, but maybe not that much harder, I’m not sure.
Oh right. Well yeah that’s a shame. I bet there’s a way to make the frontend select an instance randomaly from a list and send the query to it.
deleted by creator
This is what I meant, SearX is only a patch to a problem that won’t be solved using SearX. Brave Search is more private than Google and at least is working on a new independent index