@cheryanne @Qwant I uninstalled #Qwant from my allowable SEs some years ago. Atm struggling to recall specifics, but vaguely think there was some integrity controversy [tbc; i might be hallucinating]. One thing i do know for sure though [just tested it now], as a control-freak i find Q just too simple for my tastes wrt config options. So, i still use a nice #SearXNG instance, #NoGooMe, with #Ecosia for the occasional times that the former is feeling a bit tired & emotional.

Dunno if the content in this is legit or tinfoil stuff, but fwiw:
https://foliovision.com/2022/03/independent-european-search

That you use it infers you find it nice, so IMO ... yay for diverse choice! 🎉 🥳 👯‍♀️

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 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 ;-)

@xyhhx Don't know about the latter, but fwiw i use & like #NoGooMe

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 🤣

@chirp I am using Firefox and I never encounter this issue with #noGooMe
Maybe an issue with LibreWolf local cache?

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

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: #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.

My Hashtag Dump [as part of my latest Instance-hop🤦‍♀️]

LAST EDITED 23/4/25

#FollowedHashtags

#AUR
#AboutConfig
#AdvancedWebInterface
#AnnaMadrigal
#AnonsysNet
#Arch
#ArchInstall
#ArchLinux
#Archie
#Archies
#Atheism
#AusPol
#Beatles
#Biodiversity
#BirdMakeup
#CSLewis
#ChangeTheSystem
#DarwinAwards
#Debian
#Depression
#Distrobox
#DouglasAdams
#DrHelenMagnus
#EnidBlyton
#FOSS
#FOSSemojis
#FamousFive
#FediTips
#Fedia
#Fedora
#Firefox
#FirefoxBeta
#FirefoxNightly
#FirefoxSecondSidebar
#Firejail
#Floorp
#Friendica
#FriendicaHelp
#fsckALLreligion
#FsckChristoFascists
#FsckRWNJs
#FsckThePatriarchy
#FuckAroundAndFindOut
#Gaia
#GilmoreGirls
#GlitchSoc
#GlitchSocial
#GnuCash
#Grammar
#Greens
#HHGTTG
#HumanRights
#InfosecExchange
#InfosecSpace
#Insiders
#JRRTolkien
#KDE
#KDELinux
#KDEOS
#KDEPlasma
#KMyMoney
#Kalpa
#Kbin
#Kinoite
#KVM
#LauraTingle
#Lesbian
#LibreOffice
#LibVirt
#Linux
#LinuxWomen
#Logic
#MastoAdmin
#Matildas
#MichaelWestMedia
#MicroOS
#MicroOSDesktop
#Misanthropy
#Misdirection
#Misogyny
#MontyPython
#MontyPythonsFlyingCircus
#MostlyHarmless
#MrsMadrigal
#Narnia
#NationStates
#Nihilism
#NoGooMe
#Nonsense
#OhGreatProphetZarquon
#openSUSE
#Overshoot
#Penguinistas
#Phanpy
#Plasma
#ProgIndies
#PulseBrowser
#QEMU
#RWNJs
#RachelWithers
#RedFireAnts
#RenewableEnergy
#RightToProtest
#RippingYarns
#searX
#Semantics
#Sengi
#Sidebery
#SlowMode
#SocialPhobia
#StateCapture
#Statuzer
#SteamEngine
#SteamLocomotive
#SteamLocomotives
#Stylus
#TheGolgafrinchamArkFleetShipB
#TheGoons
#TheGreatProphetZarquon
#TheLordOfTheRings
#TheSpanishInquisition
#Tillies
#TreeStyleTab
#Tumbleweed
#UniversalBlueAurora
#UserJS
#VM
#VPN
#VerticalTabs
#VirtManager
#Wayland
#WeAreSelfishCruelBastards
#WeAreTotallyFscked
#Whimsy
#WindowRules
#Xfce
#YellowCrazyAnts
#ZenBrowser

@tag-aur
@tag-arch
@tag-archlinux
@tag-distrobox
@tag-firefoxnightly
@tag-friendicahelp
@tag-fsckallreligion
@tag-fsckchristofascists
@tag-fsckrwnjs
@tag-fsckthepatriarchy
@tag-gnucash
@tag-hhgttg
@tag-kmymoney
@tag-lesbian
@tag-linuxwomen
@tag-montypython
@tag-mostlyharmless
@tag-penguinistas
@tag-sengi
@tag-statuzer
@tag-weareselfishcruelbastards
@tag-wearetotallyfscked
@tag-whimsy

Dear :searxng: #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.

:runbsd: #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