Searx is unmaintaned, there is a fork called SearXNG.
Privacy
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
I skimmed it really quick. Looks like a really good writeup! You talk about stylometry, you might be as paranoid as I am.
I don't even try to hide my speech patterns, but I should.
Will try to give it a slow read when I have time. I like your work so far!
I think it’s good you tell people to check their threat model, but then on the other hand some of the advice comes across for those in an extreme category of the spectrum, which most people aren’t.
For example, most people aren’t whistleblowers or political dissidents sharing news online and needing to hide from state governments - they’re regular working folks who need to be more worried about falling prey to the everyday phishing and social engineering attacks aiming for their bank accounts and credit cards.
It’s cool to know the extreme parameters for top security, but it’s important to get the daily, small stuff right, too. Like using password managers, MFA, being vigilant looking out for all chances of scams, not using shady websites, services or pirated software, leaving software and devices unpatched, etc.
A table of contents with links to headers would be good to include, so people can easily jump to sections that interest them.
An additional subheading for each category that covers negative consequences of using whatever method might be good, especially since this is a guide for neophytes as well as more experienced people, and the (often) inverse relationship between security and useability isn't always understood.
Thanks for making this @whoszycker@lemmy.ml, I found this a useful writeup :)