They’re likely referring to the sentences outlining the differences between searx and SearXNG in searX README (archived Github repo). I think it was about some feature to report bugs to the project. And NG having a faster pace of development.
A software developer and Linux nerd, living in Germany. I’m usually a chill dude but my online persona doesn’t always reflect my true personality. Take what I say with a grain of salt, I usually try to be nice and give good advice, though.
I’m into Free Software, selfhosting, microcontrollers and electronics, freedom, privacy and the usual stuff. And a few select other random things, too.
They’re likely referring to the sentences outlining the differences between searx and SearXNG in searX README (archived Github repo). I think it was about some feature to report bugs to the project. And NG having a faster pace of development.
I’d say if it’s as power hungry as people say, it’d maybe make a good on-demand backup solution. Install some NAS distribution and power it on once a month, make backups of your *arred collection and your laptop/workstation and shut it off again.
I think as written, I’d say these words are more FUD (fear, uncertainty and doubt)
And I’ve been running servers for quite some time as well. SearXNG seems rock solid. And it’s tested. And when I had security issues in general, it was because we didn’t do timely updates. I haven’t really ever been affected by zero days in my hobby linux endeavours. Okay, we had a few nasty things in some more fundamental building blocks and sometimes people using slower distributions had been fine… But I don’t think it applies here. With these kinds of things, the latest stable release is your best bet. Not a previous version with bugs in it, which have been fixed since. And especially not an unmaintained project.