I just did a quick comparison of how search results looks on Google, DuckDuckGo, and self-hosted SearXNG

#selfhosting #searxng

First Google: three screenshots and few actual search results

Dear readers, this TrustNoOne special day is the perfect one to advertise for this #SearXNG instance hosted on #OpenBSD and freely available. It will allow you to fact-check all the news you’ll get today

https://nogoo.me

Just successfully set up a personal searxng instance on a raspberry pi on my tailnet so I can access it with all my devices and I’m feeling like a hacker-ninja. Time for bed.
#searxng #docker #raspberrypi #selfhosting #tailscale #linux

Сегодня я узнал, что в #SearXNG всё-таки есть нормальные Bangs!! Да, нужно поставить не один восклицательный знак, а два.

!ddg — ищет в DuckDuckGo и показывает результаты внутри SearXNG.
!!ddg — открывает сайт DuckDuckGo с указанным запросом.

Вместо DuckDuckGo может быть любой другой поисковик или сайт — посмотреть можно в настройках. Но это не всегда работет. Например, !!mjk должен открывать Mojeek, но этого не происходит.

Вообще, мне нравится, что можно искать в желаемом поисковике, не открывая его, для большей приватности. Но иногда SearXNG ломается и ничего не показывает. В таком случае я хочу именно открыть сайт нужного мне поисковика.

Per chi è in Fuga da Firefox

Sempre più utenti migrano verso browser privacy-first come @librewolf, @Waterfox o @mullvadnet browser Perché? Meno tracciamento, più libertà!

Vuoi usare SearXNG (motore di ricerca open che non ti spia) senza complicazioni?

Basta installare l'estensione devol per Firefox e derivati: https://addons.mozilla.org/it/firefox/addon/devol-searxng

Cosa fa?

Configura automaticamente #SearXNG nei browser

Niente passaggi tecnici: ricerca anonima in 1 click

@sicurezza@diggita.com

Still not sure how to use #SearXNG as your default (meta)search engine? Here’s an example using #Firefox.

https://eggflix.foolbazar.eu/w/3uy4utZeURCZF4P1Ak1tdi

Trying @kagihq search for the first time. As they offer 100 free searches. I already host #searxng so never tried it.
Let's see if #kagi meets my needs.

A tip to all the #Searxng admins out there: replace all results to paywalled sources with links to archive.is / archive.ph.

This is my configuration for example:

hostnames:
  replace:
    '^(www\.)?nytimes\.com$': 'archive.is/https://nytimes.com'
    '^(www\.)?bloomberg\.com$': 'archive.is/https://bloomberg.com'
    '^(www\.)?washingtonpost\.com$': 'archive.is/https://washingtonpost.com'
    '^(www\.)?ft\.com$': 'archive.is/https://ft.com'
    '^(www\.)?newyorker\.com$': 'archive.ph/https://newyorker.com'
    '^(www\.)?theatlantic\.com$': 'archive.ph/https://theatlantic.com'
    '^([\w-]+).substack\.com$': 'archive.is/https://\1.substack.com'
    '^(www\.)?newscientist\.com$': 'archive.is/https://newscientist.com'

In a time where democracy is threatened by late-stage capitalism and paywalls (voters can’t take sound decisions if access to reliable information is protected by dozens of subscriptions, and all that is left for free is social media memes and 3rd-hand misinformation), and where we seriously run the risk of the next generations being unable to even access the news from our age, this is a civic duty.

If the page the user is looking for hasn’t been archived yet, then the user may be prompted to do so - and, by doing so, the user of your search engine has just become an archivist that ensures that one more piece of information will be available to tomorrow’s historians.

Be careful using #atuin server and #searxng
on the same machine.

Default ports are both set to :8888 causing incompatibility.

You'll have to find other creative port numbers .

Keeping an eye on #SearXNG logs makes me realize how many fuckers try to badly access web sites all day long... I'll have to see if I can implement all the live-bans that I have build based on nginx log using #relayd on some other web site.

Ola
Vous auriez des ressources pour comprendre comment ça marche #SearXNG et pourquoi selon les instances y'a le gros carré rouge « Désolé aucun résultat trouvé » qui se pointe ? C'est relouuu (de ne pas comprendre)

Desde hace muchos meses, mi buscador por defecto es #searxng que uso desde esta instancia patria

https://ala.mbre.es/searxng

Últimamente me estaba sucediendo que al clicar en un resultado de búsqueda y a continuación volver al buscador, firefox daba documento expirado y tenía que hacer dos clicks para reenviar la búsqueda anterior, expirando después de un cierto tiempo.

El problema se soluciona cambiando en las preferencias/privacidad del buscador en HTTP Method por get en lugar de post.

I don't understand people who say they'll pay for a #searchengine. Not only is all that public data and knowledge, but they pretend like #SearXNG don't exist - which basically includes indexing from many search engines.

In some cases, it's just another #LLM and selling of tokens. Fine - pay per process is fine. But let's not pretend that these LLMs have anything more special than the aforementioned public data at their disposal, and let's not pretend that this algorithm can't also be skewed.

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

Ho aggiornato il mio post "Migliorare la propria privacy online" aggiungendo una piccola sezione riguardante le Chat #AI

https://pietro.in/posts/privacy/

Tra i primi step da attuare c'è quello di cambiare motore di ricerca ed usare ad esempio SearXNG:
https://pietro.in/posts/searxng/

E' possibile usare la mia istanza gratuita all'indirizzo https://searxng.pietro.in/

Weiß jemand, wie ich bei der #Bilder #Suche in #SearXNG einstellen kann, dass die Ergebnisse im Original #Format angezeigt werden und nicht als diese merkwürdigen Balken, auf denen man nichts richtig erkennen kann? In den #Einstellungen finde ich dazu nichts.

Pour info le service zoTop.fr est reparti.

Bon à savoir : on pensait que ça venait des blocages prévus et connus que peut rencontrer une instance #SearXNG mais finalement un simple redémarrage du serveur a suffit.