Google frequently stops working as an engine
Don’t threaten me with a good time.
Comment on YSK about SearXNG - an open metasearch engine
saylesss88@eviltoast.org 2 days ago
SearXNG is great but unfortunately Google frequently stops working as an engine in SearxNG because its anti-bot and rate‑limiting systems detect SearxNG traffic as automated scraping and either return CAPTCHAs, “access denied/suspended” messages, or HTTP 429 “too many requests” errors.
Their devs admit that there’s no simple solution because Google actively hunts and stops this traffic once a fix is implemented. The other search engines still work but I tend to get irrelevant nonsense as results. I have started using StartPage and am pretty happy with it so far as another option for a metasearchengine.
Google frequently stops working as an engine
Don’t threaten me with a good time.
The other search engines still work but I tend to get irrelevant nonsense as results
Yahoo and Duckduckgo return good results for me on the instance I use.
We are back to Yahoo?
Full internet circle.
I like it because there are some very obscure sites in its index, which can be returned from fairly simple queries.
DDG has gone completely shitty for me recently.
Such a weird thing to be seeing.
I've switched the default search engine in Firefox to DDG finally, and I honestly haven't noticed a difference in results. This may not be the best praise though, since Google has sucked for a number of years now.
At best, DDG results are only 33% less shitty than Google’s, but the UI is 2000% better.
I wonder if routing it through FlareSolverr isn’t a solution.
suzune@ani.social 2 days ago
I only get crap results when using the public SearXNG instances. It’s far better when I use my own container.
I didn’t notice google results are gone. But I also don’t care. If they rely on your metadata to give you results, it’s obvious they are violating privacy.