diff --git a/README.md b/README.md index ad54974..eec0117 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ ## If you want to edit one of my existing blogposts: - fork the repository - edit what you want to edit, from the forked repository - - create a PR, and wait for me to merge it. (feel free to ping me on matrix about it) + - create a PR, and wait for me to merge it. (feel free to ping me on SimpleX about it) ## If you want to create a new blogpost: yes, i pay in moneros, for well made, complete blogpost contributions @@ -66,12 +66,18 @@ Send me on chat your blogpost idea, and tell me where exactly it's supposed to f ``` -Each tutorial can be assigned to at most one contributor, and I allow only ONE tutorial assigned per contributor at a time, i want quality, not quantity. +Each tutorial can be assigned to at most one contributor, and I allow only ONE tutorial assigned per contributor at a time, **i want quality, not quantity.** If you see a tutorial already being assigned to someone, either wait for that tutorial to be un-assigned (past the deadline) and then ask me to assign it to you, or go pick another one. +The default deadline is 1 month from when you're being assigned the issue. Even for complex tasks this is more than enough time if you are actually capable of doing what you chose to do. + + **NOTE: If your assigned tutorial is past the deadline, the tutorial won't be assigned to you anymore, and you won't recieve any payment, it must be completed by that time. If you want to move the deadline, contact me directly explaining why.** +If you miss more than 2 deadlines, i'll stop assigning issues to you. Same thing if you can't deliver proper quality, i will refuse further contributions from you. In short, **if you're not competent enough to actually do what you're talking about and explain why, don't bother.** + +However If over time you're a frequent contributor (that has contributed multiple complex blogposts), contact me if you want to become a maintainer (in short, being one that validates contributions). ### Contributors Todolist ### @@ -79,11 +85,10 @@ Each upcoming blogpost has it's own gitea issue as listed [here](https://git.now To see their status in the overall opsec blog project, check out the project board [here](https://git.nowhere.moe/nihilist/blog-contributions/projects/1). - - ### LICENSE ### This entire blog is licensed under Creative Commons Zero: No Rights Reserved (Public Domain) + Feel free to run your own blog if you want a more restrictive license. diff --git a/index.html b/index.html index 21ce35c..9c26bd8 100644 --- a/index.html +++ b/index.html @@ -37,7 +37,7 @@ - nihilist`s Blog + The Nihilism Blog
--> -
+
@@ -165,7 +150,7 @@

Nihilism

- Until there is Nothing left. + Until there is Nothing left.



Creative Commons Zero: No Rights Reserved

@@ -174,14 +159,14 @@

My Links

- RSS Feed
Matrix Chat
+ RSS Feed
SimpleX Chat

About nihilist

-

Donate XMR: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8


Contact: nihilist@nihilism.network (PGP)

+

Donate XMR: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8


Contact: nihilist@contact.nowhere.moe (PGP)

diff --git a/productivity/index.html b/productivity/index.html index d50d7e2..3066d62 100644 --- a/productivity/index.html +++ b/productivity/index.html @@ -62,12 +62,18 @@
-

Preparing the Body

+

Preparing the Body and Mind

@@ -79,14 +85,14 @@
-

Preparing the Mind

+

Planning the Work

@@ -98,18 +104,17 @@
-

Planning the Work

+

Doing the Work

+
@@ -120,14 +125,13 @@
-

Doing the Work

- +

Reflecting on the Work

diff --git a/productivity/microworkflow/1.png b/productivity/microworkflow/1.png new file mode 100644 index 0000000..88e1f8b Binary files /dev/null and b/productivity/microworkflow/1.png differ diff --git a/productivity/microworkflow/index.html b/productivity/microworkflow/index.html index 0f31cef..6ccd0cc 100644 --- a/productivity/microworkflow/index.html +++ b/productivity/microworkflow/index.html @@ -63,6 +63,7 @@ Previous Page

Micro Workflow: Todo Listing, Contextualizing, and Ordering Tasks

+
@@ -73,14 +74,26 @@
-

a

-

- +

Todo Listing

+

As a continuation of our previous tutorial on macro workflow, to write your todo list effectively, you need to contextualize it in a particular project (or topic) list the tasks, label them, and note down on what other task do they depend on.


+-Project Opsec (243 -> 211)
+	-Privacy Category (2112)
+		-Linux Host OS Task (21121)
+	-Anonymity Category (2113)
+	-Deniability Category (2114)
+		-Veracrypt Task (21121 -> 21141)
+		-Deniable VMs Task (21141 -> 21142)
+
+-Project Infrastructure (24)
+	-setup VPS  (241)
+	-create the blog (241 -> 242)
+	-officially announce the blog is accepting contributions (242 -> 243)
-

+

As you can see here, we have our 2 Projects: Infrastructure and Opsec, with tasks under each that are labeled, this is for us to be able to contextualize them more easily.

+

And with the label at the end, we also write which other task must be completed before starting each task, if there are any.

@@ -90,15 +103,27 @@
-

b



-

- +

What happens when the todo list gets too big ?



+

Following this way of working is nice at first, but when the todo list gets too big to be done in one day or week, it's going to feel very overwhelming. For example if i were to detail what i have to do for the Deniable VMs tutorial


+-Project Opsec (243 -> 211)
+	-Deniability Category (2114)
+		-Deniable VMs todo list, not Task (21141 -> 21142)
+			-To be explained:
+				- What is the usecase ?
+				- What tools are going to be used ?
+				- Why do we need Veracrypt ? 
+				- Why do we need Whonix ?
+			-To be showcased:
+				- How to create the hidden volume
+				- How to put the Whonix VM inside the hidden volume
+				- How to use the emergency shutdown script as a non-root user
+				- How to start the emergency shutdown script with a cinnamon keyboard shortcut
+

In short, when each Task is starting to become a todo list of it's own, you need to treat it not as a task, but as a separate todo list.

-
@@ -110,13 +135,57 @@
-

c



-

+

How to handle multiple todo lists



+

So to have multiple todolists, we're going to have multiple files:


-	
+[ mainpc ] [ /dev/pts/4 ] [~/todo lists]
+→ tree .
+.
+├── 0.txt
+├── 21141.txt
+├── 21142.txt
+└── 243.txt
+
+1 directory, 4 files
+
-

+

as you can see, the smaller the number, the higher level we have for the todo list. The master todolist is the 0.txt text file, it references the projects and labels them, and also labels each todo list underneath.

+

+[ mainpc ] [ /dev/pts/4 ] [~/todo lists]
+→ cat 0.txt
+-Project Opsec (243 -> 211)
+        -Privacy Category (2112)
+                -Linux Host OS Task (21121)
+        -Anonymity Category (2113)
+        -Deniability Category (2114)
+                -Veracrypt Task (21121 -> 21141.txt)
+                -Deniable VMs Task (21141 -> 21142.txt)
+
+-Project Infrastructure (24)
+        -setup VPS  (241)
+        -create the blog (241 -> 242)
+        -officially announce the blog is accepting contributions (242 -> 243.txt)
+
+
+

Now we have the todolist "Deniable VMs" labeled 21142, so we have the 21142.txt textfile containing the todolist accordingly:

+

+[ mainpc ] [ /dev/pts/4 ] [~/todo lists]
+→ cat 21142.txt
+-Deniable VMs todo list, not Task (21141 -> 21142)
+        -To be explained:
+                - What is the usecase ?
+                - What tools are going to be used ?
+                - Why do we need Veracrypt ?
+                - Why do we need Whonix ?
+        -To be showcased:
+                - How to create the hidden volume
+                - How to put the Whonix VM inside the hidden volume
+                - How to use the emergency shutdown script as a non-root user
+                - How to start the emergency shutdown script with a cinnamon keyboard shortcut
+
+
+

And that's it! now you have a very rudimentary way of keeping track of what you need to do, in what context, and in what order.

diff --git a/pull.sh b/pull.sh old mode 100755 new mode 100644 diff --git a/pushtoprod.sh b/pushtoprod.sh old mode 100755 new mode 100644