-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use searx.space to see if SearXNG instances are online #95
Comments
Understandable. I'll just remove the periodic polling for SearXNG and update the nightly build to factor in instance availability when generating the instance list. |
We can also increase the frequency of checking the health of each instance. @dalf proposed to do that, I'm not what's the current frequency (one per hour)? |
return42
added a commit
to return42/searxng
that referenced
this issue
Apr 13, 2023
Since [bb3a01f8] has been merged to the Farside project, Farside instances do no longer need to send requests to SearXNG instances [1]. There are some old unmaintained Farside instances on the web that continue to query SearXNG instances --> we can safely block their requests. [1] benbusby/farside#95 [bb3a01f8] benbusby/farside@bb3a01f8 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
return42
added a commit
to return42/searxng
that referenced
this issue
Apr 13, 2023
Since [bb3a01f8] has been merged to the Farside project, Farside instances do no longer need to send requests to SearXNG instances [1]. There are some old unmaintained Farside instances on the web that continue to query SearXNG instances --> we can safely block their requests. [1] benbusby/farside#95 [bb3a01f8] benbusby/farside@bb3a01f8 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The implementation of farside instances do a search request on each SearXNG instance to see if the instance is online and does it work.
From the view of a SearXNG instance, the sum of the farside instance behave like a bot net that has been gone wild / doing the same query:
farside/config/config.exs
Lines 16 to 18 in 6048d3c
.. again and again, 24/7 from different IPs. In SearXNG we tend to block wild bots since they will have a negative impact on the engines of the SearXNG instance when we pass trough these requests.
My suggestion:
To avoid this flood of requests on each SearXNG instance, the farside instances can use the list from the SearXNG team to see what instances are online --> https://searx.space/
May the farside team has more / other suggestions to improve the situation / Thank you for your understanding.
The text was updated successfully, but these errors were encountered: