[FEATURE] Anti "Instance Has Been Ratelimited" tool

[patyarishimai]

Describe the feature you'd like to see added
After self-hosting Whoogle, it will eventually get ratelimited. This happens not only with a self-hosted instance but also with every public instance rendering Whoogle useless and unusable. I would truly appreciate a way or method to stop this annoying problem from happening.

Additional context
A temporary fix was implemented named Farside, the problem with this is that if you want to use Whoogle, it redirects to another ratelimited instance ad infinitum, it also redirects to SearXNG and other search engines but I (as many others) want to use Whoogle.

[boognish-rising]

I suspect @benbusby is familiar with Farside, as it's another project of his. So, without speaking for him, I also suspect he sympathizes. I know I do. However, I'm not sure that there's much that can be done about it. Google sets and enforces rate limits so it becomes a numbers game of the number of available (not rate limited) instances vs. the number of users/queries, with the rate limit value also factoring in there somewhere, i.e., the number of queries at which Google declares an instance to be rate limited for X period of time.

Farside is one of the only tools/solutions I'm aware of that attempts to combat the problem of rate limits on public instances of self-hosted front-ends, but it can only do so much. Sadly, at present, there is no silver bullet against the scourge that is rate limiting and I do believe that Farside is probably the closest thing we've got to one.