News for hackers. Stuff that matters.
Re:Searx – A privacy-respecting, hackable metasearch engine by aantix on Monday July 25, 2016 @10:31AM (#12158925)
I don't see the API limits posted anywhere? Any limits on the number of requests?

And since they're aggregating from other search engines, won't they eventually reach a point where they're running out of API requests?

Re:Searx – A privacy-respecting, hackable metasearch engine by jasonkostempski on Monday July 25, 2016 @10:45AM (#12159024)
If API keys are required how is this truly private? Either you get your own keys and loose privacy or you use someone else's service which brings you right back to what you get with any other search engine.
Re:Searx – A privacy-respecting, hackable metasearch engine by aantix on Monday July 25, 2016 @10:49AM (#12159059)
Fair point. This occurred to me as well after doing my initial post (follow up below).
Re:Searx – A privacy-respecting, hackable metasearch engine by nattaylor on Monday July 25, 2016 @10:39AM (#12158986)
It appears the linked searx.me is just a deployment of the open source searx project, and probably will reach the limit.
Re:Searx – A privacy-respecting, hackable metasearch engine by aantix on Monday July 25, 2016 @10:44AM (#12159021)
It's interesting, if their claim of " while not storing information about its users" is totally true, I guess request limits would be impossible without at least tracking the originating IP?
Re:Searx – A privacy-respecting, hackable metasearch engine by JD557 on Monday July 25, 2016 @12:12PM (#12159629)
They could limit requests by IP without storing them explicitly.

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.

Re:Searx – A privacy-respecting, hackable metasearch engine by epchong on Monday July 25, 2016 @10:46AM (#12159033)
It does not seem to be limiting incoming requests by IPs. So IPs does not need to be stored anywhere.