{"id":12237,"date":"2025-06-13T10:34:29","date_gmt":"2025-06-13T17:34:29","guid":{"rendered":"https:\/\/jasonsblog.ddns.net\/?p=12237"},"modified":"2025-06-13T10:41:18","modified_gmt":"2025-06-13T17:41:18","slug":"planning-a-privacy-safe-search-strategy-options-in-2025","status":"publish","type":"post","link":"https:\/\/jasonsblog.ddns.net\/index.php\/2025\/06\/13\/planning-a-privacy-safe-search-strategy-options-in-2025\/","title":{"rendered":"Planning a Privacy Safe Search Strategy – Options in 2025"},"content":{"rendered":"\n

Interesting overview, and he arrives at the correct conclusion, SearXNG, though I don’t know what he’s talking about with it being hard to setup. I run my own SearXNG<\/a> instance on the same server with this blog using docker, though that setup is a bit more complicated with integration with Nginx Reverse Proxy Server to support Let’s Encrypt certificates for encryption, but you can easily just run it on the local network without encryption, as it only takes a simple command to add to a running docker installation (as I keep one on my local network as a backup to my public instance, though you lose IP isolation unless you set it up to use a VPN or proxy).<\/p>\n\n\n\n

docker run -d --name searxng --restart=always -p 8080:8080 searxng\/searxng<\/code><\/pre>\n\n\n\n
One other note, there is Whoogle<\/a>, which is a privacy front end for Google that is worth using if you really just want Google results, which is good for technical searches. I have my own public instance, but I’m mainly using SearXNG these days and hardly touch it. And you can customize SearXNG by going into the settings and enabling what search engines it queries. And as far as I’m concerned, AI is trash unless it cites sources, as it’s fed too much false information and propaganda with no actual intelligence to figure out truth from fiction, so use your own gray matter.<\/p>\n\n\n\n
\n