There is a lot of demand for digital privacy and security advice out there right now and lots of people are giving advice and writing guides. I beg them to do a few things:
1. Be explicit about the threat model your advice is meant for.
2. Do not give advice you haven't tried implementing yourself. Eat your own dog food.
3. Get feedback on your guide from your target audience before publication.
4. Incorporate that feedback. This is not an optional step.
@evacide In that case couldn't they be called JOI?
I'll see myself out.
@evacide If I'm going to give instructions to someone else, I first write them out and try to follow them exactly as written. It makes mostly sure they are reproducible. Mostly.
I like the callout on threat models and their applicability. I'm going to steal that.
@evacide Before writing yet another guide, see if there already is a good enough guide you can share, as is or with some commentary, and/or contribute to, rather than starting from scratch.
For a starting list of existing guides, see page 5 of the full version of
https://www.turnoffyourphone.org (that guide is good too).
ObXkcd: https://xkcd.com/927/
@evacide Number two is questionable.
Let's say I use Linux exclusively. Why can't I give good advice for, for example, using local users in Windows?
equivocal
evacide
Furbland's Very Cool Mastodon™
Cassandrich
xyhhx 
bearbob ☭
Hasufin
run_atalanta 😷💯
Adam Shostack 
Hey Gus
Flipper 🐬🏳️🌈
... and and and and ...
Scien
Rodrigo Dias
Derrial Book
Owl Eyes