@matt I maintain the #nogoome instance and the few people who use it seem to be satisfied with it.

I opted out of searx.space as this tends to bring bots and other script sh!t.

@justine@snac.smithies.me.uk i've used it for the past year or two [or longer; i really struggle with time], but unfortunately for several months it's not behaved well for me. the various safety checks it now does on each incoming query always breaks my query [landing me just at their default front page after the checks are done] so i have to keep repeating my query several times before it works. it is driving me away from it in frustration, alas. less common, but still occurring enough to be another disappointment, are badly formatted "results" pages saying "no results". #nogoome

Vous ne savez pas ce qu’est #nogoome ?

Vous voulez en savoir plus sur ce qu’on fait, pourquoi on le fait et comment on le fait ?

Les détails sont résumés ici :
https://about.nogoo.me/fr/

#SearXNG #WhatsMyIP #OpenBSD #SelfHost #DeGooglisonsInternet

Still not sure what #nogoome is about?

Want to learn what and why we do things we do?

Details are sumed up here:
https://about.nogoo.me

#SearXNG #WhatsMyIP #OpenBSD #SelfHost #DeGoogleIfyInternet

Your (almost) weekly informative message to notify that the #nogoome #SearXNG instance has been updated. It seems to work ok here. We just had a hiccup because of a configuration issue but everything should be fixed. As usual, ping to complain or send love ;-)

:runbsd: #RunBSD

@Stomata here’s mine.

#SearXNG #nogoome

Dear #noGooMe users,

Since the Layer7 Networks provider failed me twice during my holidays and communication was not-good, I decided to leave this cheap VPS provider. The #SearXNG instance has been reinstalled at @hetzner@mastodon.hetzner.social. It now runs on #OpenBSD #arm64 again.

I also added #Anubis in front of it, expecting to limit bots traffic. Not sure if it will really help. Time will tell.

It seems to work ok on my side.
As usual, don't hesitate to ping me if something fails on yours.

Right, the @chirp #GoToSocial account has been migrated here. Thanks to the #slurp software, most posts have also been migrated (except non-public ones and replies). Manual pinning was also required but that's ok.

You shall get future news about the #noGooMe #SearXNG instance running on #OpenBSD from here as of now. Spoiler alert: there will be some really soon ;)

Follow up: People in the DC have started working on the issue. The instance seem to be back online. It may still encounter a few hiccups until everything is fully corrected.

#noGooMe #SearXNG

Hey #noGooMe users,
The new VPS provider (Layer7 Networks) is having major storage issues on the PAR location. This #SearXNG instance will be unavailable until they solve the problem...
Sorry for the inconvenience.

#UpdateMonday notification for our #noGooMe fellow users.

#SearXNG has just been updated. Everything looks ok here. As usual, don't hesitate to ping me if you have issues.

Hey beloved #noGooMe users,

A quick reminder that you *must* have the proxy image option unchecked when using this #SearxNG instance. It can be disabled, if you previously had it enabled, browsing to /preferences, then selecting the "privacy" tab and uncheck the "image proxy" switch.

It is disabled by default so any first connection to this instance has the proper setting set up.

If you do have it enabled, you’ll quickly be blocked at the firewall level by our #awk AI agent 🤖

My reason for disabling this feature is that it generates loads of requests from the instance IP to the external engines. And this makes those block us really fast.

This means that the engines will have *your IP* logged when you search for images, only. Classical text search are still masqueraded with our instance IP.

Hey beloved #nogoome users,

A quick reminder that you *must* have the proxy image option unchecked when using this #searxng instance. It can be disabled, if you previously had it enabled, browsing to /preferences, then selecting the "privacy" tab and uncheck the "image proxy" switch.

It is disabled by default so any first connection to this instance has the proper setting set up.

If you do have it enabled, you’ll quickly be blocked at the firewall level by our #awk AI agent 🤖

My reason for disabling this feature is that it generates loads of requests from the instance IP to the external engines. And this makes those block us really fast.

This means that the engines will have *your IP* logged when you search for images, only. Classical text search are still masqueraded with our instance IP.

Hey fellow #noGooMe users,
We’ve just finished the procedure for being unreferenced from searx.space.

The reason being it seems services like searx.neocities.org (which sources the searxng instances list) is used by a lot of bots; which leads to the instance being blocked by remote engines quite often.

This #SearXNG instance continues to #RunBSD and be available as it used to be. We simply expect more real users and less blocks this way. So, from your POV, this shouldn’t change anything; hopefully.

As usual, ping me if I’m getting wrong ;-)

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 :openbsd: #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: #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 :)

*Breaking News* The bug has been corrected upstream and applied on the instance. Enjoy!

#nogoome #SearXNG #OpenBSD