Crosspost from the The Donald. DDG is getting moe pozzed. Stop using DuckDuckGo
(media.communities.win)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (44)
sorted by:
Searx
Use a public node, or host your own if you don't care about privacy but want better results.
If you're able to deploy a public node others can use do that, the more nodes there are the harder it is for the fuzz to find your needle in the haystack.
I'm technically competent, having run webservers for 15+ years. I'm genuinely considering setting up a public node that I can also share amongst family/friends.
One bit I didn't quite get of your comment: "host your own if you don't care about privacy" – do you simply mean that server providers are going to require personal details and it's not too hard to track down who runs one? - or is there some other consideration I'm not understanding?
the privacy thing is a basic one in that all the search providers know which IP the requests are coming from.
Running a searx instance requires no personal data, from you as the hoster or from users.
It's just a simple docker image for most people (that's what I use for my personal instance)
If you're eager to hide your controversial knitting hot takes, hosting a node for yourself isn't going to protect you from unscrupulous three letter agencies.
Hosting a public node can help other people who are worried about privacy as their request will be lost in all the other requests.
Running a public node is a great thing to do as it helps others.
If you're hosting I would recommend going for the domain owner anonymizer protection if your registrar supports it.