oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-07-02 03:26:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix

Browse source
This commit is contained in:
anon 2025-06-22 15:34:20 +02:00
parent b1128e473f
commit d275a9ee09
4 changed files with 8 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

3
whytheblog/index.md
View file

@ -107,8 +107,6 @@ Anonymity for example also has a serverside context. [You may want to anonymousl
All of this to say, **we seek to give advice that is applicable to 90% of the people out there, to defeat 99% of the risks one may face**. We don't care about the advice that only 10% of the people can actually pull off, to protect against the 1% most unlikely risk that could happen. We want to make sure that as many people as possible actually get to have relevant opsec advice for their day to day lives, wheter it be privacy, anonymity or deniability related.
![](../contribute/65.png)
For instance, we won't recommend you to hook up wires to your motherboard, risk bricking your laptop permanently, all to just hopefully disable some closed-source software that came with the closed-source hardware you bought. that's a 1% unlikely risk whose protective action only 1% of the people can actually pull off. No, instead we're going to recommend you purchase a laptop that is open-hardware by default once it hits the market, and you won't have any closed-source hardware backdoor to remove in the first place.
**_TLDR:_ We put forward realistic advice only that can be applied to 90% of the people out there to defeat 99% of the risks**
@ -123,7 +121,6 @@ For example, recommending to use signal to message someone privately is more com
Every complication needs to be justified, and requiring a phone number to chat privately with someone is not justifiable. You need to realize that sometimes there exists a huge amount of possible solutions to solve a given problem (yes there exists a TON of chat apps out there). The only difference is that some solutions are overly complex, while others are simpler. **The simpler solution that actually delivers opsec-wise IS the best solution.**
![](../contribute/64.png)
The first goal is to make sure to show that privacy, anonymity and deniability is required AND achievable, but then we need to make sure that as many people as possible can achieve it, by simplifying it as much as possible, without making the individual vulnerable to any statist threat.