Sorry friends if you found yourself being blocked from accessing the #NoGooMe #SearXNG instance these days. I miswrote some variable affectation in the anti-bot script and it was blocking a bit to many people (including myself ) when some limits were reached… This should hopefully be solved now

Hey #noGooMe users!
We've applied changes so that you can now use w3m with this #SearXNG instance.
Quite a few things have been refactored but we expect to have tested everything properly. Should this not be the case, don't hesitate to ping me if something broke on your side.
Enjoy!

#RunBSD

We have received an email from #Hetzner. They can’t send us the monthly invoice because the $5 cost has not been reached.

You should #SearXNG for more things #noGooMe friends. And more often. Or they’ll end up starving

Hey fellow users,

Being myself a heavy user of the #noGooMe service, I sometimes see my Web browser of choice (namely Librewolf theses days) getting CSS "not loading" errors. It presents itself in the form of the web page rendering being scrambled and only displaying unscaled images and icons.

Once it happens, the web browser seems stucked in this state. Even if a Private Browsing window may not suffer from it.

This is the time I generally decide to update the software and switch the blue/green instance. Then, the problem looks solved for a bunch of more days.

That looks like a local cache error to me rather than an error on the #SearXNG side. So I consider it acceptable for my daily usage. BUT I would change my mind if it happens to be more global. So, question for you:
Do you also encounter this kind of issue regularly?
(If so, please notify me when it happens so that I can react quicker; and I know there is something wrong to investigate :)

Hey fellow #nogoome users,

Seems like our last #SearXNG update went with a rendering issue when using mobile device. We're keeping a eye on the PR and will update ASAP.

Sorry for the inconvenience.

https://github.com/searxng/searxng/issues/4187

Hey fellow #nogoome users, time for a quick look in the review mirror.

The overall uptime of the #SearXNG service on 2024 is about 98.04%*.
The overall usage is slightly less than 1 search per minute.
The overall quality of the instance has nothing to be ashamed of (compared to other referenced public instances*); although running on #OpenBSD and #ARM hardware.

We are still experimenting monitoring and automation to fight script kiddies and bots. As usual, don't hesitate to ping this account if you have any trouble with the service.

We have big plans for this new year. Stay tuned.
In the meantime, have a great new year!

https://about.nogoo.me/

* value provided by uptime.searxng.org

Dear #noGooMe users,
We're having a holiday week, not that close from a WiFi spot.
Feel free to contact me in case of trouble but expect at least 4H delay before even getting an ACK :)
That said, have a nice Winter holiday season.

Dear #noGooMe users,

In order to lower rate limiting from remote engines and be able to apply anti-bot policy without locking you, users, I have turned **off** the `image_proxy` feature. The reason is that this implies lots of connections from this instance to the remote engines - and triggers rate limiting from them.

This changes nothing regarding protection of your privacy when you do "textual" searches. This only means that, to get images & videos thumbnails, it's your browser that gets the resources from the remote engines and not this instance. Turned simply: for each rendered thumbnails, remote sites will see **your IP**. Once again, it's not the case for "textual" searches.

I hope this will participate in lowering the "suspended: to many requests" error messages that some of you have reported. This should not diminish your search experience but should it happen, just let me know.

#SearXNG

_Side note: turned out much of `image_proxy` usage was done to render (and hide) "questionable" pictures. I don't judge those, it's none of my business what teases people. But I decided to not endorse it in the expense of users doing "regular" text searches._

Dear users of #noGooMe,
I’m currently blocking a bunch of /24 that have TCP sessions up but no HTTP usage. Given the number there are and relayd is sweating, I’m blocking using my axe.
If I end up blocking you too, then
1. sorry :)
2. give me your IP in PM so that I unblock it.
Cheers!

#SelfHost #SearXNG

Hey fellow users,
#noGooMe has been updated to the latest version and we switched to the "green" instance. All seems ok here. As usual, let me know if something fails for you.

https://nogoo.me/

#SearXNG #OpenBSD #SelfHost #ThereIsNoCloud

In our eternal quest for a better service, we're switching to a Blue / Green deployment method; instead of Backup+Update+Hope :) The #SearXNG instance Blue has been activated. Let us know if there's something weird on your side.

#RunBSD #noGooMe

Sorry folks, I walked on my own fingers while testing a correction for a #SearXNG configuration bug preventing thumbails with peertube video. The modification was half pushed on Prod when it shouldn’t have been at all…

Anyway, #NoGooMe should be up and running again. Thank you #OpenBSD for being so stable even when dummy SysAdmin drives

@joel will upgrade the #NoGooMe server to #OpenBSD 7.6 today (Thu 10/10) at 12:00 Paris time. It will hopefully not be long