oxeo0/blog-contributions
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git synced 2025-07-02 11:56:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fuck bad criticism

Browse source
This commit is contained in:
nihilist 2025-04-07 23:28:57 +02:00
parent c948b5776d
commit 2c6790c17a
3 changed files with 13 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
opsec/criticism/4.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 202 KiB

22
opsec/criticism/index.html
View file

@ -80,8 +80,8 @@
<h2><b>Nobody knows everything</b></h2> <h2><b>Nobody knows everything</b></h2>
<p>First of all, i'll clear up a misconception that people seem to think far too often: <b>No, <a href="../../productivity/scio-nihil/index.html">i don't know everything.</a></b> But neither do they, even if they pretend otherwise. There is a reason as of why we are welcoming criticism on all of our blogposts: <b>we are aware that we don't know everything, and we strive to know as much as we possibly can.</b> </p> <p>First of all, i'll clear up a misconception that people seem to think far too often: <b>No, <a href="../../productivity/scio-nihil/index.html">i don't know everything.</a></b> But neither do they, even if they pretend otherwise. There is a reason as of why we are welcoming criticism on all of our blogposts: <b>we are aware that we don't know everything, and we strive to know as much as we possibly can.</b> </p>
<img src="../../productivity/scio-nihil/4.png" class="imgRz"> <img src="../../productivity/scio-nihil/4.png" class="imgRz">
<p>Just because you managed to fill your head (this bucket) with water from the ocean (knowledge from a particular topic), <b>doesn't mean that you managed to empty the whole ocean into the bucket.</b> Nobody knows everything, myself included, and yourself included. Yeah i know, it's hard to admit.</p> <p>Just because you managed to fill your head (this bucket) with water from the ocean (knowledge from a particular topic), <b>doesn't mean that you managed to empty the whole ocean into your bucket.</b> Nobody knows everything, myself included, and yourself included. Yeah i know, it's hard to admit sometimes.</p>
<p>Our tutorials aren't perfect, and don't pretend that i believe that they are. There's always room for improvement, so you're more than welcome to send us criticism to let us know what we missed. And if your criticism is valid, we'll listen and update the tutorial accordingly. </p> <p>Our tutorials aren't perfect, and we're never going to pretend that they are. <b>There's always room for improvement, so you're more than welcome to send us criticism to let us know what we missed.</b> And if your criticism is valid, we'll listen and update the tutorial accordingly. </p>
<p>Thing is, you also need to know how to criticize correctly if you want us to actually improve what we're doing. (if you're not criticizing correctly, all you're making is just noise and contributing to the problem, rather than putting in a little more effort to contribute to the solution that we're trying to bring to the table.)</p> <p>Thing is, you also need to know how to criticize correctly if you want us to actually improve what we're doing. (if you're not criticizing correctly, all you're making is just noise and contributing to the problem, rather than putting in a little more effort to contribute to the solution that we're trying to bring to the table.)</p>
</div> </div>
</div><!-- /row --> </div><!-- /row -->
@ -109,16 +109,18 @@
<div class="row"> <div class="row">
<div class="col-lg-8 col-lg-offset-2"> <div class="col-lg-8 col-lg-offset-2">
<h2><b>Low-Quality Criticism</b></h2> </br> </br> <h2><b>Low-Quality Criticism</b></h2> </br> </br>
<p><b><u>- Level 0:</u></b> At the lowest level (Name-calling)</b> you can call me a dumbo jumbo and meanie, but in the end you're just whining aimlessly at how cruel the world is.</p> <p><b><u>- Level 0:</u></b> At the lowest level (Name-calling)</b> you can call me a dumbo jumbo and meanie, but in the end you're just throwing a tantrum because you don't like me. I think you can avoid polluting whatever public place you have found to do that and grow up a bit, you'll save everyone's time.</p>
<p><b><u>- Level 1:</u></b> (Ad Hominem)</b> you can also criticize my characteristics and pretend that i am too young to know more than you the mighty all knowing, same thing as the above but also puffing up your own ego at the same time. If the other party is dishonest about it, they'll even try to do some sophisticated ad hominem: </p> <p><b><u>- Level 1:</u></b> (Ad Hominem)</b> you can also criticize my characteristics and pretend that i am too young to know more than you, Oh, The mighty all knowing, you're doing the same thing as the above but you're also trying to puff up your own ego at the same time. Dishonesty in arguments is way too common, resulting in Sophisticated Ad Homiems like in the example below. (Which is a clear sign of immaturity, obviously). </p>
<img src="4.png" class="imgRz">
<pre><code class="nim"> <pre><code class="nim">
[...] We still sometimes see deliberate dishonesty, as when someone picks out minor points of an argument and refutes those. Sometimes the spirit in which this is done makes it more of a sophisticated form of ad hominem than actual refutation. For example, correcting someone's grammar, or harping on minor mistakes in names or numbers. Unless the opposing argument actually depends on such things, the only purpose of correcting them is to discredit one's opponent. [...] We still sometimes see deliberate dishonesty, as when someone picks out minor points of an argument and refutes those. Sometimes the spirit in which this is done makes it more of a sophisticated form of ad hominem than actual refutation. For example, correcting someone's grammar, or harping on minor mistakes in names or numbers. Unless the opposing argument actually depends on such things, the only purpose of correcting them is to discredit one's opponent.
Truly refuting something requires one to refute its central point, or at least one of them. And that means one has to commit explicitly to what the central point is. Truly refuting something requires one to refute its central point, or at least one of them. And that means one has to commit explicitly to what the central point is.
</pre></code> </pre></code>
<p><b>If all you can think about is how to win the next argument, then you're not a truth seeker, You're just desperatly trying to protect your ego.</b> I was once like that to be clear, but i grew out of it. Everyone can grow out of it. You just have to be willing to leave your insecurities behind to be able to move forward.</p>
<p><b><u>- Level 2:</u></b> (Responding to the tone)</b> 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. </p> <p><b><u>- Level 2:</u></b> (Responding to the tone)</b> 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.</p>
<p><b><u>- Level 3:</u></b> (Contradiction)</b> For example, <b>if you start to say that using closed-source software is suitable for private use without explaining why</b>, 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 <b>doesn't mean that affirming the opposite of what an entire blogpost says without explaining why is going to disprove anything.</b> </p> <p><b><u>- Level 3:</u></b> (Contradiction)</b> For example, <b>if you start to say that using closed-source software is suitable for private use without explaining why</b>, 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 <b>doesn't mean that affirming the opposite of what an entire blogpost says without explaining why is going to disprove anything.</b> </p>
<img src="1.png" class="imgRz"> <img src="1.png" class="imgRz">
@ -140,16 +142,16 @@ Truly refuting something requires one to refute its central point, or at least o
<div class="col-lg-8 col-lg-offset-2"> <div class="col-lg-8 col-lg-offset-2">
<h2><b>High-Quality Criticism</b></h2> </br> </br> <h2><b>High-Quality Criticism</b></h2> </br> </br>
<p><b><u>- Level 4:</b> (Counterargument)</u></b> For example, if you had read the <a href="../sensitivevm/old.html">previous Sensitive VM Setup</a> tutorial i wrote, you'd realize that the crucial Host OS live mode requirement wasn't even covered, instead i was recommending a particular script to wipe off the forensic traces regarding the presence of the VC hidden volume. Therefore, as someone correctly did so, they added me to send me the following (valid) criticism:</p> <p><b><u>- Level 4:</b> (Counterargument)</u></b> For example, if you had read the <a href="../sensitivevm/old.html">previous Sensitive VM Setup</a> tutorial i wrote, you'd realize that the crucial Host OS live mode requirement wasn't even covered, instead i was recommending a particular script to wipe off the forensic traces regarding the presence of the VC hidden volume. Therefore, as someone correctly did so, they added me on SimpleX to send me the following (valid) criticism:</p>
<img src="2.png" class="imgRz"> <img src="2.png" class="imgRz">
<p>In this case it's an absolutely valid criticism which definitely makes sense, since it simplifies the previous setup by removing the use of that wipe.sh script, and by not even requiring to install the veracrypt software. In that case i scheduled the changes for multiple tutorials, and came up with the following 4 updated tutorials to take this criticism into account: <a href="../linux/index.html">[0]</a><a href="../livemode/index.html">[1]</a> <a href="../veracrypt/index.html">[2]</a> <a href="../sensitivevm/index.html">[3]</a>. <b>One valid criticism can have an effect on the entire Opsec blog like this one, since there are alot of blogposts that are inter-dependant.</b></p> <p>In this case it's an absolutely valid criticism which definitely makes sense, since it simplifies the previous setup by removing the use of that wipe.sh script, and by not even requiring to install the veracrypt software. In that case i scheduled the changes for multiple tutorials, and came up with the following 4 updated tutorials to take this criticism into account: <a href="../linux/index.html">[0]</a><a href="../livemode/index.html">[1]</a> <a href="../veracrypt/index.html">[2]</a> <a href="../sensitivevm/index.html">[3]</a>. <b>One valid criticism can have an effect on the entire Opsec blog like this one, since there are alot of blogposts that are inter-dependant.</b> In this case, since the Host OS had to change, i rewrote the Host OS tutorial, the hypervisor tutorial, the veracrypt tutorial and ultimately the sensitive VMs tutorial accordingly to be able to match the criticism that was sent to me.</p>
<p>That's the minimum for me to consider your feedback and do something about it. However if you want to bring some extra quality to your criticism, you can do the following:</p> <p><b>This is the minimum for me to consider your feedback and do something about it.</b> However if you want to bring some extra quality to your criticism, you can do the following:</p>
<p><b><u>- Level 5:</u></b> (Refutation)</b> You can first quote what i wrote (but i know what i wrote so you can simply link to the tutorial directly and i'll immediately know the context of what you're talking about), and then explain exactly why it's not correct. <b>Ideally if you're basing your criticism on external sources, also post links to those resources that explain further what you're talking about,</b> so that i get the full picture: </p> <p><b><u>- Level 5:</u></b> (Refutation)</b> You can first quote what i wrote (but i know what i wrote so you can simply link to the tutorial directly and i'll immediately know the context of what you're talking about), and then explain exactly why it's not correct. <b>Ideally if you're basing your criticism on external sources, also post links to those resources that explain further what you're talking about,</b> so that i get the full picture: </p>
<img src="3.png" class="imgRz"> <img src="3.png" class="imgRz">
<p><b><u>- Level 6:</u></b> (Refuting the central point)</b> If you actually care about me improving my tutorials, you should stick to refuting what i wrote, explicitely. Whether it be the reasoning behind the tutorial, the explanations, the showcased setups, or the purpose of any of the tutorials, <b>but for every criticism that you make, ideally bring an improvement to the table.</b> Tell me how you'd improve the tutorial if you think the solution i presented is not good enough (or not simple enough) like in the example above.</p> <p><b><u>- Level 6:</u></b> (Refuting the central point)</b> If you actually care about me improving my tutorials, cut out all the bullshit you see from level 0 to level 3 and <b>just stick to refuting what i wrote, explicitely.</b> Whether it be the reasoning behind the tutorial, the explanations, the showcased setups, or the purpose of any of the tutorials. <b>However, for every criticism that you make, also let me know how you think the blogpost could be improved.</b> Tell me how you'd improve the tutorial if you think the solution i presented is not good enough (or not simple enough) like in the example above.</p>
<p>And that's it! You now know how to send valid criticism, <b>and you now know how to do it like an adult</b>. By doing so you can effectively contribute to continuously improving our blogposts accordingly.</p> <p>And that's it! You now know how to send valid criticism, <b>and you now know how to do it like an adult</b>. By doing so you can effectively contribute to the overall project by helping us continuously improving our blogposts.</p>
</div> </div>
</div><!-- /row --> </div><!-- /row -->
</div> <!-- /container --> </div> <!-- /container -->

2
opsec/index.html
View file

@ -402,7 +402,7 @@
<div class="col-lg-8 col-lg-offset-2"> <div class="col-lg-8 col-lg-offset-2">
<h2><b> Contributing to the Project</b></h2> <h2><b> Contributing to the Project</b></h2>
<ol> <ol>
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/250">❌ How to become a Moderator </a></li> <li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/260">✅</a><a href="criticism/index.html"> How to write good Criticism</a></li>
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/275">✅</a><a href="contribute/index.html"> How to become a Contributor</a></li> <li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/275">✅</a><a href="contribute/index.html"> How to become a Contributor</a></li>
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/200">✅</a><a href="qualitystandard/index.html"> The Quality Standard</a></li> <li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/200">✅</a><a href="qualitystandard/index.html"> The Quality Standard</a></li>
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/203">✅</a><a href="maintainers/index.html"> How to become a Maintainer</a></li> <li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/203">✅</a><a href="maintainers/index.html"> How to become a Maintainer</a></li>