Well, since SearXNG aggregates results from more than 70 search engines and not solely Google, it's a safe bet they'll be fine regardless of Googles moves. However, sourcing results from Google may be impacted, but they still have many other options built in aside from Google. Whoogle being a proxy only for Google makes it reliant on Google, so their upstream changes will be very noticeable. This being the case, I'd say switching to SearXNG is going to be the best move as it has redundancy built in making it not dependent on any one engine.
this post was submitted on 16 Jan 2025
18 points (95.0% liked)
homelab
6773 readers
2 users here now
founded 4 years ago
MODERATORS
Just installed SearXNG the other day and have been loving my little private instance.
Are you using the Docker image or the stand alone? Pretty straight forward setup?
Docker and very straightforward. I would argue it's easier to set up than using their installation script.
Gave it a shot, it's been working pretty well so far. Only issue is that Firefox seems to want to use https://localhost instead of the IP address when I make it a default search engine.
Yeah, to fix that I've had to employ the Redirector add-on. Slightly annoying but no big deal.
Is it lightweight?
Very.
Then I’ll try it too. I’ve been using distroot
Lemme know how you get on
I use SearcXNG. It can use Google on the backend, but in default configuration it uses several different backends. It can also use paid backends if you set it up. Basically if it has a search api, SearXNG can hook into it with the right configuration.
Is Yacy still a thing?
There was an update tonight to patch it using another user agent.