diff --git a/opsec/criticism/6.png b/opsec/criticism/6.png new file mode 100644 index 0000000..fb9b33f Binary files /dev/null and b/opsec/criticism/6.png differ diff --git a/opsec/criticism/index.html b/opsec/criticism/index.html index 30ca5e4..efdde1d 100644 --- a/opsec/criticism/index.html +++ b/opsec/criticism/index.html @@ -62,7 +62,8 @@
Message to everyone that ever wrote, and will ever write criticism regarding the blogposts we wrote so far: Go ahead, if you are closer to the truth than we are, tell us about it and why, but if you want to get your point across efficiently, Learn how to Criticize like an adult.
+In this tutorial, we're going to cover how you can contribute as a reader, by effectively criticizing the blogposts we wrote, in order to help us find what we overlooked so that we can fix it.
+Message to everyone that ever wrote, and will ever write criticism regarding the blogposts we wrote so far: Go ahead, if you are closer to the truth than we are, you're more than welcome to tell us about it and why, but if you want to get your point across efficiently, you have to learn how to criticize like an adult.
Sidenote: Help us improve this tutorial by letting us know if there's anything missing or incorrect on this git issue directly!
I'll have to heavily quote Graham's excellent blogpost on the matter, because there is a hierarchy to argue about something, and contratry to what most people think, you can also do so respectfully (which means that you can argue like an adult, instead of argue like a child).
+I'll have to heavily quote Graham's excellent blogpost on the matter, because there is a hierarchy to argue about something, and contrary to what most people think, you can also do so respectfully (which means that you can argue like an adult, instead of argue like a child).
First of all it's a matter of maturity. If you're an adult and your ego is still in the way, refer to Sum Nihil to fix it. Because otherwise you're most likely going to be incapable of stopping yourself to resort to ad hominem on the way. I saw that happen way too often, which is a clear shame.
Proper communication is very important if you wish to convey your perception to someone else. In our usecase where we have blogposts relating to operational security, if we are wrong anywhere along the way, there's potentially an entire reasoning, context, logic, purpose, and setup to dismantle and criticize.
@@ -121,11 +122,23 @@ Truly refuting something requires one to refute its central point, or at least o- Level 2: (Responding to the tone) you can also criticize how arrogantly i wrote what i wrote and how i pretend to know more than you, but still even here you're not even addressing the actual content that i wrote. Again, all you're doing is just noise still.
+If this is what you think criticizing is about, you need to realize that all you're trying to do is paint yourself in a good picture, and paint the other side in a bad picture, and in a lazy way too. If you act that way, all you're doing is just being obvious in showing off your lack of maturity. Feel free to do that, but don't expect me to listen to what you have to say afterward.
+ +
- Level 3: (Contradiction) For example, if you start to say that using closed-source software is suitable for private use without explaining why, like how the moderators at privacy guides are doing, you're not helping either. Just because you're a moderator of a privacy laxism forum doesn't mean that affirming the opposite of what an entire blogpost says without explaining why is going to disprove anything.
This is an example of a very low effort criticism, it simply highlights that one party has a ton of compelling arguments and while the other one doesn't, they don't even care about defending their point. In this particular contradiction, the other party is downplaying the requirements to achieve privacy, implying that being spied on by the government or corporations is acceptable, when in fact it is not. This is also known as a Minimisation Fallacy
+The other extreme of this type of fallacy would be spreading FUD (Fear Uncertainty Doubt) like in this article:
+it is a disinformation technique simply aimed at spewing bullshit without any proof to back up one's claims, because according to Brandolini's law, also known as the bullshit asymmetry principle:
+
+The amount of energy needed to refute bullshit is an order of magnitude bigger than that needed to produce it.
+
+
+Nowadays, where everyone (including journalists or sunday privacy laxists) can have their uneducated say on everything, it is because of idiots that can't shut up that we are swimming in an ocean of bullshit where actual quality is hidden 10,000 kms below the surface. It is an herculean task to untangle everyone's blatant lack of education, but lucky for you we're not lazy blogposters, this blog is here to preserve quality, when we're wrong we admit it, learn from it, adapt and rewrite accordingly to get closer to the truth. We won't give in to FUD, or any minimization fallacy whatsoever, Stay true to your logic and reasoning.
+Don't just contradict what we say, bring reasoning, arguments, logic, data and links to those to the table when you do so because otherwise you're just ignoring the argument completely. Legit Criticism takes more effort like in the examples below, where we will definitely listen:
-If this is what you think criticizing is about, you need to realize that all you're trying to do is paint yourself in a good picture, and paint the other side in a bad picture, and in a lazy way too. If you act that way, all you're doing is just being obvious in showing off your lack of maturity. Feel free to do that, but don't expect me to listen to what you have to say afterward. However if you put more effort into your criticism like in the examples below, i will definitely listen:
Articles Status:
💻 Clientside - Getting Started
Just warning you, this is the most annoying part of being a maintainer, so if the reviewing is extra-tedious becuase you are facing an incompetent or lazy contributor, don't worry i'll send you extra monero your way for your trouble.
+Just warning you, this is the most annoying part of being a maintainer, so if the reviewing is extra-tedious because you are facing an incompetent or lazy contributor, don't worry i'll send you extra monero your way for your trouble.
I don't want this blog to contain ANY half-assed content, the only acceptable content is VALID, FINISHED, QUALITY content. It takes time to have quality, that's why we give a 1 month default deadline (which is more than enough 99% of the time, even for complex contributions). if contributor A is not going to write a tutorial correctly before the deadline, REJECT THEIR CONTRIBUTION, contributor B will write it correctly later on (Sum Nihil, don't care who does what, only care about what they do).
diff --git a/sed.sh b/sed.sh old mode 100644 new mode 100755 index f55ee71..21934cc --- a/sed.sh +++ b/sed.sh @@ -15,5 +15,6 @@ # adding legal in footer # find opsec/ -name '*.html' -print0 | xargs -0 sed -i 's/Until there is Nothing left.<\/p><\/br><\/br>Creative Commons Zero/Until there is Nothing left.<\/p>