oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-05-16 15:07:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix typos

Browse source
This commit is contained in:
nihilist 2025-05-15 08:40:31 +02:00
parent 9f05f656f1
commit e142601b4d
6 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
whytheblog/index.md
View file

@ -39,7 +39,7 @@ You get the idea, we're here to reverse this trend, and bring back actual truth
This mountain of work that explaining operational security is, cannot be summarized in 1 afternoon, in a 4 hour effort post. This is a multiple thousand-hour effort, to effectively plan it out, list all the blogposts to explain all the concepts, all of the topics to be explored, to actually explore them, rewrite them whenever valid criticism gets thrown at it, on and on and on it goes. AND you have to apply a quality standard on ALL posts, to make sure that you effectively convey your knowledge to your audience properly.
Not to mention the organization of the whole blogpost will affect wether or not you can reach that goal of making that one place to contain every possible opsec advice one needs under 3000 hours of work or 9000 hours of work. It needs to be correctly organized from the start, otherwise it will remain a distant target that you'll never reach. (not to mention that one needs to have enough humility to realize the enormity of the task, and also effectively organize recieving external contributions).
Not to mention the organization of the whole blogpost will affect whether or not you can reach that goal of making that one place to contain every possible opsec advice one needs under 3000 hours of work or 9000 hours of work. It needs to be correctly organized from the start, otherwise it will remain a distant target that you'll never reach. (not to mention that one needs to have enough humility to realize the enormity of the task, and also effectively organize recieving external contributions).
**TLDR: if you're not serious about it, in the long run, you're bound to make a mess out of it.**
@ -80,7 +80,7 @@ Truth seeking is definitely required in Opsec, since it is about combining all v
## **Priority Number 2: Applicability to 90% of the people out there, to defeat 99% of the risks**
When you're giving operational security advice, people need to care about it first of all. Everyone cares about privacy sooner or later in their life. Wether it is to do something private in the bedroom, or to have some private discussion about something, it is a clear topic that people want to know about. Especially on the digital side of things.
When you're giving operational security advice, people need to care about it first of all. Everyone cares about privacy sooner or later in their life. Whether it is to do something private in the bedroom, or to have some private discussion about something, it is a clear topic that people want to know about. Especially on the digital side of things.
Thing is, **context matters immensely.** you can't give advice that applies to everyone in the world at once because you need to take into account threats that may exist in a country and not in another. For example, when to it comes to using VPNs in combination with Tor to protect your anonymity we need to contextualize it correctly: