feat: Replace static blog system with Notion-backed dynamic content

26 files changed, 0 insertions, 662 deletions

diff --git a/content/blogs/finger_archive/2024_06_27.gmi b/content/blogs/finger_archive/2024_06_27.gmi
deleted file mode 100644
index 7821f3b..0000000
--- a/content/blogs/finger_archive/2024_06_27.gmi
+++ /dev/null
@@ -1,149 +0,0 @@
-```
-the ios 18 developer beta 1 wiped my iphone ! kind of.
-
-the first few days of having the beta installed was fine—great, even;
-however, two days ago, my phone started slowing down on the simplest tasks,
-which coincided with system crashes.
-
-these crashes weren't just simple ones that required a quick reboot to
-fix. they were ones where the phone would halt to a small loading icon for
-a few seconds, then to a black screen for a few minutes, then to the apple
-icon for a few minutes, then back to the home screen.
-
-the crashes were accompanied by what i assume to be the entire icon cache
-to be wiped as well, since on boot, i would be met by a load of placeholder
-icons and no app titles on my home screen. some sort of other caches must have
-been affected as well, because many apps' settings were wiped, alongside the
-affected icons and titles. at the same time, many apps' settings stayed, too,
-oddly ! my educated guess is that these apps store their local configuration
-in a different manner.
-
-today, i had no crashes at all, so i was under the assumption that my problems
-have vanished, but i spoke too soon ! my first crash of the day was a big
-one. it was followed by the same hard-crash symptoms i mentioned before,
-but it also happened to wipe a lot more than just icon and local settings
-caches. this crash cleared my open tabs on safari, logged me out of multiple
-apps, brought on the same cache wipes as above, and i'm guessing much more
-that i haven't fully disconvered yet.
-
-the good news is that i don't keep local data on my phone—or rather,
-i don't keep important local data on my phone. all my files are commited
-to icloud, all of my device backups are present icloud, and i don't use my
-mobile device for important things. it's a tool, not a workstation.
-
-now starts part two of this adventure !
-
-before i bricked my iphone for good, i wanted to go ahead and either revert
-to ios 17, or update to a more stable release of the ios 18 developer
-beta. thankfully, beta 2 had been released two days ago. this is likely just
-a coincidence, but these nasty bugs actually begin on the day of beta 2's
-release. (queue tinfoil hat)
-
-anyway, from what i was able to find, beta 2 was somewhat more stable that
-beta 1. that's good news. the bad news is that i don't have enough storage
-on my device.
-
-i needed to sacrifice something for some space, and that something was
-wuthering waves. sitting at 17 gigabytes, i wiped wuthering waves, which
-should have given me plenty enough extra space to install the beta 2 update,
-given that it only needed an additional 15 gigabytes of total storage to
-install, but i was informed that i had been lacking the required available
-storage to install the update, regardless of my actions ....
-
-i thought that this was some sort of storage calibration bug, so i restarted
-my iphone, but i was still unable to update.
-
-it turns out that the "system data" portion of my device's storage was the
-culprit, and was reading something in the order of 30 gigabytes. this value
-should be closer to 1–2 gigabytes, and can maybe reach up to 5 gigabytes
-in rare cases. i'm not sure exactly where it was sitting before i uninstalled
-wuthering waves, but after i did uninstall wuthering waves, the "system data"
-promptly expanded itself to fill up the reset of that newly freed 17 gigabytes
-of storage.
-
-i'm not sure what "system data" actually means, but it must be a fluctuative
-set of data, as i was observing it dancing around the 25–30 gigabyte range,
-back and forth, sometimes by megabytes, sometimes gigabytes. one second it'd
-be 25.3, then 25.36, then 29.3.
-
-the best idea i could come up with was to see if i could beat it in time
-by restarting my device and requesting an update as soon as i could after
-reaching boot.
-
-attempt one: i could not beat it in time.
-
-attempt two: i did beat it in time ! after this success, i requested an
-update, which went through, but was stuck on "requesting update", or some
-thing along those lines, for many minutes. after backing in and out of the
-menu, i was once again prompted to free up more storage, and the "system data"
-had once again expanded to occupy the free space.
-
-attempt three: i actually, fully beat "system data" this time, but with a
-small bump. the update medium actually pre-downloaded, or whatever apple
-does with updates before actually intalling the update, but i was informed
-with a similar "more storage required" screen. this screen was requesting an
-additional 5 gigabytes of storage. i backed in and out of the menu to see if
-i could trick the update to go through, or get "system data" to budge, and
-i actually got the value down to 3.11 gigabytes ! since initially getting it
-to come down, i haven't had any success to get it to force itself any furthur.
-
-i imagine that the "system data" and the beta 2 update process are having a
-land war of sorts, where the "system data" is trying its best to eat every
-last byte, while the update process is trying to do the same. my guess is
-that the update process just needs a little help. surely, the "system data"
-doesn't actually have a consistent byte munching agenda, while the update
-process actually is forcefully pushing back.
-
-as of this time, i am still stuck at an additional 3.11 gigabytes required
-to install the beta 2 update, even after offloading ~400 megabytes of
-applications. i'll test out some more fixes and report back if i have any
-updates !
-
-update one: after a restart, i was able to get the update to go through
-first try ! as soon as i clicked the update now button, i was locked into
-a prompt which read "verifying update". given this reading, i'm not so sure
-if that 3.11 gigabyte additional resource request was fibbing, or that the
-update was so close to completely downloaded, that this "verifying update"
-prompt deployed some additional troops to fight off the "system data" regime.
-
-the update is slowly going through, and has reached approximately 1/4
-progress complete after 3–4 minutes of waiting. i'll report back on any
-furthur developments !
-
-update two: it's up ! i'm not going to sit on my phone here for hours and
-hours to test it all out and see if it's still having the same issues, but
-from my about 30 second test, it seems fine. i'll report back after about
-a good day's use, or if i hit any of the same bugs.
-
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣤⣤⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⣀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣾⣿⣿⣿⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⢀⣾⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⣾⣿⣿⣿⣿⣿⣿⣧⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⣧⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⣿⣿⣿⣇⠀⠀⠀⠀⠀⠀⠀⢀⣿⣿⣿⣿⣿⣿⣿⣿⡆⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡄⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⢀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣧⠀⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡇⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡄⠀⠀⠀⢀⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣇⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⢀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠈⣿⣿⣿⣿⣿⣿⠟⠉⠀⠀⠀⠙⢿⣿⣿⣿⣿⣿⣿⣿⡿⠋⠀⠀⠙⢻⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⠃⠀⠀⠀⠀⣠⣄⠀⢻⣿⣿⣿⣿⣿⡿⠀⣠⣄⠀⠀⠀⢻⣿⣿⣏⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⣾⣿⣿⣿⣿⠀⠀⠀⠀⠰⣿⣿⠀⢸⣿⣿⣿⣿⣿⡇⠀⣿⣿⡇⠀⠀⢸⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⣄⠀⠀⠀⠀⠙⠃⠀⣼⣿⣿⣿⣿⣿⣇⠀⠙⠛⠁⠀⠀⣼⣿⣿⣿⡇⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⣿⣷⣤⣄⣀⣠⣤⣾⣿⣿⣿⣿⣽⣿⣿⣦⣄⣀⣀⣤⣾⣿⣿⣿⣿⠃⠀⠀⢀⣀⠀⠀
-⠰⡶⠶⠶⠶⠿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡟⠛⠉⠉⠙⠛⠋⠀
-⠀⠀⢀⣀⣠⣤⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⠷⠶⠶⠶⢤⣤⣀⠀
-⠀⠛⠋⠉⠁⠀⣀⣴⡿⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣯⣤⣀⡀⠀⠀⠀⠀⠘⠃
-⠀⠀⢀⣤⡶⠟⠉⠁⠀⠀⠉⠛⠿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⠟⠉⠀⠀⠀⠉⠙⠳⠶⣄⡀⠀⠀
-⠀⠀⠙⠁⠀⠀⠀⠀⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠁⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⠀⣸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⠀⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⠀⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⠀⣰⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⢀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-⠀⠀⠀⠀⣸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
-```
\ No newline at end of file
diff --git a/content/blogs/finger_archive/2024_06_29.gmi b/content/blogs/finger_archive/2024_06_29.gmi
deleted file mode 100644
index 97326ee..0000000
--- a/content/blogs/finger_archive/2024_06_29.gmi
+++ /dev/null
@@ -1,21 +0,0 @@
-$ touch -t 06290440 fuwn
-$ printf "\n\n" && cat /dev/art
-
-
-く__,.ヘヽ.　  /　,ー､ 〉
-　　　　　＼ ', !-─‐-i　/　/´
-　　　 　 ／｀ｰ'　　　 L/／｀ヽ､
-　　 　 /　 ／,　 /|　 ,　 ,　　　 ',
-　　　ｲ 　/ /-‐/　ｉ　L_ ﾊ ヽ!　 i
-　　　 ﾚ ﾍ 7ｲ｀ﾄ　 ﾚ'ｧ-ﾄ､   !ハ|　 |
-　　　　 !,/7 '●'　  ´i●ﾊ  iソ|  |　　　
-　　　　 |.从"　　_　　 ,,,, / |./ 　 |
-　　　　 ﾚ'| i＞.､,,_　,.イ / 　.i 　|
-　　　　　 ﾚ'| | / k_７_/ﾚ'ヽ,　ﾊ.　|
-　　　　　　 | |/i 〈|/　 i　,.ﾍ |　i　|
-　　　　　　.|/ /　ｉ： 　 ﾍ!　　＼　|
-　　　 　 　 kヽ>､ﾊ 　 _,.ﾍ､ 　 /､!
-　　　　　　 !'〈//｀Ｔ´', ＼ ｀'7'ｰr'
-　　　　　　 ﾚ'ヽL__|___i,___,ンﾚ|ノ
-　　　　　 　　　ﾄ-,/　|___./
-　　　　　 　　　'ｰ'　　!_,.:
diff --git a/content/blogs/finger_archive/blog.json b/content/blogs/finger_archive/blog.json
deleted file mode 100644
index 2148303..0000000
--- a/content/blogs/finger_archive/blog.json
+++ /dev/null
@@ -1,11 +0,0 @@
-{
-  "priority": 2,
-  "posts": {
-    "2024_06_27": {
-      "name": "June 27th, 2024"
-    },
-    "2024_06_29": {
-      "name": "June 29th, 2024"
-    }
-  }
-}
\ No newline at end of file
diff --git a/content/blogs/news/Finger_Gateway.gmi b/content/blogs/news/Finger_Gateway.gmi
deleted file mode 100644
index a8c5278..0000000
--- a/content/blogs/news/Finger_Gateway.gmi
+++ /dev/null
@@ -1,6 +0,0 @@
-# Finger Gateway
-
-This capsule now supports proxying Finger servers!
-
-=> /finger Gateway access here!
-=> /finger/fuwn.me Try it!
\ No newline at end of file
diff --git a/content/blogs/news/blog.json b/content/blogs/news/blog.json
deleted file mode 100644
index 181335d..0000000
--- a/content/blogs/news/blog.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "priority": 1,
-  "description": "The [Inconsistently Updated] Update Log of This Gemini Capsule",
-  "posts": {}
-}
\ No newline at end of file
diff --git a/content/blogs/technology/C++.gmi b/content/blogs/technology/C++.gmi
deleted file mode 100644
index f95c434..0000000
--- a/content/blogs/technology/C++.gmi
+++ /dev/null
@@ -1,4 +0,0 @@
-# C++
-
-=> /web/www.neilhenning.dev/posts/yourownconstantfolder/?class=post-content Your Own Constant Folder in C/C++
-=> https://justine.lol/endian.html The Byte Order Fiasco
\ No newline at end of file
diff --git a/content/blogs/technology/Compilers.gmi b/content/blogs/technology/Compilers.gmi
deleted file mode 100644
index 3267197..0000000
--- a/content/blogs/technology/Compilers.gmi
+++ /dev/null
@@ -1,3 +0,0 @@
-# Compilers
-
-=> https://diekmann.uk/blog/2024-06-25-statically-known-undefined-behaviour.html How gcc and clang handle statically known undefined behaviour
\ No newline at end of file
diff --git a/content/blogs/technology/Forth.gmi b/content/blogs/technology/Forth.gmi
deleted file mode 100644
index 0986735..0000000
--- a/content/blogs/technology/Forth.gmi
+++ /dev/null
@@ -1,14 +0,0 @@
-## "Stories"
-
-=> https://groups.google.com/g/comp.lang.forth/c/ThWiGXwKqv4 A Forth Story
-
-## Resources
-
-=> http://www.forth.org/ Forth Interest Group Home Page
-=> https://forth-standard.org/ Forth
-=> http://theforth.net/ the Forth Net
-=> http://www.complang.tuwien.ac.at/forth/program-links.html Links to Forth Programs
-=> https://github.com/uho/docker-forth Docker images for popular Forth systems
-=> http://forthworks.com/ ForthWorks (HTTP)
-=> gemini://forthworks.com/ ForthWorks (Gemini)
-=> gopher://forthworks.com:70/ ForthWorks (Gopher)
\ No newline at end of file
diff --git a/content/blogs/technology/Gemini.gmi b/content/blogs/technology/Gemini.gmi
deleted file mode 100644
index 938d4a0..0000000
--- a/content/blogs/technology/Gemini.gmi
+++ /dev/null
@@ -1,87 +0,0 @@
-# Gemini
-
-## Why Gemini?
-
-I've decided to move my personal websites, along with some other projects, over to the Gemini protocol for a number of reasons (in no specific order):
-
-* Gemini-based capsules are easy to maintain
-* Gemini-based capsules are fun to maintain!
-* The Gemini capsule limits tracking by design
-* The primary Gemini text format provides no way to display intrusive ads of any kind, or any other unneeded fluff and annoyances
-* The community is awesome. I love seeing the motivation and movement behind this project. There's such passion.
-* The development-sphere: The Gemini development community is huge for how small the project itself is, and I'm glad to be a part of it.
-
-## Resources
-
-### Utilities
-
-GemRest: A development studio focused on delivering high performance, Gemini-oriented utilities. Organised by Fuwn (me)!
-
-=> gemini://gem.rest GemRest
-
-### Clients
-
-Lagrange: An amazing desktop GUI client for Gemini and Gopher
-
-=> gemini://skyjake.fi/lagrange/ Lagrange
-
-Sydney: Vim-like, Command-line Gemini Client
-
-=> https://github.com/gemrest/sydney Sydney
-
-Amfora: A very nice, feature-rich, and easy-to-use CLI client for Gemini
-
-=> https://github.com/makeworld-the-better-one/amfora Amfora
-
-Bollux: A fun little CLI client for Gemini written entirely in Bash that packs a punch
-
-=> https://sr.ht/~acdw/bollux/ Bollux
-
-Elaho: An elegant IOS Gemini client which I personally use
-
-=> gemini://elaho.glv.one
-
-### Proxies
-
-September: A high performance Gemini-to-HTTP proxy written in Rust, focused on accessibility and speed and function
-
-=> https://github.com/gemrest/september September
-=> https://fuwn.me/proxy/fuwn.me My (Fuwn) live instance of September, and personal website
-
-Mozz.us and Vuples.one Portals: Simple and intuitive
-
-=> https://portal.mozz.us portal.mozz.us
-=> https://proxy.vulpes.one proxy.vulpes.one
-
-### Frameworks & Servers
-
-Windmark: An elegant and highly performant async Gemini server framework, written by me! (Fuwn)
-
-Windmark is similar to Gig, but much, much faster, and written in Rust.
-
-=> https://github.com/gemrest/windmark Windmark
-
-Gig: A Go framework for developing and deploying dynamic (or static) Gemini capsules
-
-=> https://github.com/pitr/gig Gig
-
-Agate: A purely static Gemini server written in Rust
-
-=> gemini://gem.limpet.net/agate Agate
-
-### Windmark Modules
-
-Windmark Comments: A comment engine module for Windmark
-
-=> https://github.com/gemrest/windmark-comments Windmark Comments
-
-### Capsules
-
-=> gemini://gemini.circumlunar.space Project Gemini
-=> gemini://medusae.space medusae.space gemini directory
-=> gemini://gem.acdw.net acdw's gemini cottage
-=> gemini://gem.chriswere.uk Chris's gemini capsule
-=> gemini://gemini.barca.mi.it The Amazing Fnt400's Gemini Capsule
-=> gemini://hexdsl.co.uk The Home of HexDSL
-=> gemini://envs.net envs.net
-=> gemini://rawtext.club rawtext.club
\ No newline at end of file
diff --git a/content/blogs/technology/Go.gmi b/content/blogs/technology/Go.gmi
deleted file mode 100644
index 29162c1..0000000
--- a/content/blogs/technology/Go.gmi
+++ /dev/null
@@ -1,50 +0,0 @@
-=> https://www.ardanlabs.com/images/gopher-kart/other-gophers.png
-
-To kick it off: Go is funny language. I have a hard time taking it seriously, and that's not because of the name, but because of the way it "feels". Don't get me wrong, Go is a **great** tool to have under your belt, but it just feels very ... "childish" ... to **me**.
-
-Other than the chills I get whilst working with it, I think Go is a pretty nifty language, and I'm sure you'll pick up on that further down in this blog post. If anything, the above statements were icebreakers, but also my genuine feelings. :=
-
-Go has the "I can do anything! just not very well ..." [0] feeling to it, and that is very much true! I don't write software in Go because it's "blazing fast!" or "great on memory!". I write software in Go because it's "fast!" to write in.
-
-> [0] Having the aforementioned quality is not particularly a bad thing, I think it actually benefits Go!
-
-Now, here are some pros and cons that I have gathered up during my experience with the language:
-
-These are in no particular order, and solely **my** opinions.
-
-## Pros
-
-Reasons for anyone to learn or to use Go!
-
-* Fast enough: Go isn't Rust fast, but it's not Node.js slow.
-* There are **lots** of resources. (books, documentation, libraries, tutorials, et cetera)
-* It's quite easy to pick up. (having had prior experience with C-like programming languages)
-* Go can do just about anything you pin at it.
-* It runs on Plan 9!
-
-## Cons
-
-Nitpicks, not deal-breakers!
-
-* Garbage collected: This isn't necessarily a hard-con, but it contributes to more memory overhead that I'd prefer not to waste. (not as much as Node.js, though)
-* Go can feel *too* simple stupid at times, and not in a KISS way.
-* The dependency management and "package manager" is downright creepy: `$ go get ...` seems extremely pre-mature and underdeveloped, even many years into Go's life
-
-One thing you might see a lot when there is talk about Go is the claim that Go hasn't "found it's niche" or "it has no real purpose". To that I say: Go's niche is its simplicity, its ability to introduce someone into the compiled language space, and to develop software with speed.
-
-## Who Would I Recommend Go To?
-
-People who ...
-
-* don't have much time for boilerplate material,
-* people who want to get their foot into the lower-level side of programming, (or compiled languages)
-
-and dare I say it ... anyone!
-
-## Resources
-
-=> https://golang.org/ golang.org
-=> https://interpreterbook.com/ Writing An Interpreter In Go by Thorsten Ball
-=> https://compilerbook.com/ Writing A Compiler In Go by Thorsten Ball
-=> https://go.dev/wiki/Plan9 Go Wiki: Go on Plan 9
-=> https://9lab.org/plan9/go/ Plan9/Go
\ No newline at end of file
diff --git a/content/blogs/technology/Gopher.gmi b/content/blogs/technology/Gopher.gmi
deleted file mode 100644
index 9a13d75..0000000
--- a/content/blogs/technology/Gopher.gmi
+++ /dev/null
@@ -1,23 +0,0 @@
-# Gopher
-
-## Resources
-
-### Clients
-
-phetch: Similar to Amfora over in Gemini land in the aspect that it is a feature-rich and easy-to-use CLI client
-
-=> https://github.com/xvxx/phetch phetch
-
-Gopher: A straightforward Gopher client for IOS
-
-=> gopher://forthworks.com/1/iOS/gopher
-
-### Gopherholes
-
-=> gopher://bitreich.org/1/lawn The Gopher Lawn
-=> gopher://gopherpedia.com Gopherpedia
-=> gopher://gopher.floodgap.com/1/gopher Floodgap Systems
-=> gopher://forthworks.com/1/ ForthWorks
-=> gopher://sdf.org/1/ SDF
-=> gopher://hngopher.com/1/ Hacker News
-=> gopher://kamalatta.ddnss.de Plan 9 (9front) from Gopherspace
\ No newline at end of file
diff --git a/content/blogs/technology/I2P.gmi b/content/blogs/technology/I2P.gmi
deleted file mode 100644
index 1bee2d6..0000000
--- a/content/blogs/technology/I2P.gmi
+++ /dev/null
@@ -1,14 +0,0 @@
-# I2P
-
-This capsule is available as an I2P eepsite.
-
-=> http://fuwn.i2p/?i2paddresshelper=umaux4l3q3j33pfsz3mzxk6o5c7f6lu47wln5vo5nqvv5nyufgra.b32.i2p Eepsite (I2P)
-
-## Other Cool Personal I2P Eepsites
-
-=> http://plan9.i2p/?i2paddresshelper=sCwR46B4IOAPQbPBd9dqm4VTrZO1PD3eGlEJdYAKFmYMdRG0QFif2ND7K1pZlGJGsZlR70-aGJwBU4YtkCSPv10qubxggFOzNwOeoW0qen9kdzg4BdF46U7ngzYZ2eIniIIl55LplsfSU~iVmil--5SWTaq-UpsjW7CHokipoK6eEfGsZixUygDGJAaPHxKopq2sf-dzZaOdXlupMppmGUUJ9-C3ygJzCfolozZukNVp~PMSas3noTVakogRagtcaWpYaAhiNfK2SGKDiQLbLN1MVXcNftqyRp7wrO7jpgZ7oL89D-I9SGJL5Q41VPd4LIXzlkJNbHUxQZhXTI3Q~jrs24DdtF9TNllaZHIpLmL0xg-pKBLoE6eAuEVIhbr3OuzbgN20X1M2WVpkcikuYvTGD6koEugTp4C4RUiFuvegXpl53bRfUzZZWmRyKS5i9MYPqSgS6BOngLhFSIW69zJ0N7Y9XsnnFGwP-C8O4sba534Kf7Xj4NKeB0rnfSo4BQAEAAcAAA%3d%3d#!sig%3dmGRazwfCrgM7dqRpIjhRJ-Y4lf~vltleBw1KgOY-eNNZDdPa0grrYY80OCLn6k4KTG4Yci-kBIkHRdXxXir-CQ%3d%3d plan9.rocks
-=> http://aiwnios.i2p/?i2paddresshelper=1reMaIXK~wBerFbzgqa2lklPXUCChAVYi-VJu1gE2LvWt4xohcr~AF6sVvOCpraWSU9dQIKEBViL5Um7WATYu9a3jGiFyv8AXqxW84KmtpZJT11AgoQFWIvlSbtYBNi71reMaIXK~wBerFbzgqa2lklPXUCChAVYi-VJu1gE2LvWt4xohcr~AF6sVvOCpraWSU9dQIKEBViL5Um7WATYu9a3jGiFyv8AXqxW84KmtpZJT11AgoQFWIvlSbtYBNi71reMaIXK~wBerFbzgqa2lklPXUCChAVYi-VJu1gE2LvWt4xohcr~AF6sVvOCpraWSU9dQIKEBViL5Um7WATYu9a3jGiFyv8AXqxW84KmtpZJT11AgoQFWIvlSbtYBNi71reMaIXK~wBerFbzgqa2lklPXUCChAVYi-VJu1gE2LvWt4xohcr~AF6sVvOCpraWSU9dQIKEBViL5Um7WATYu2Qb4TUyMLD8etroqUPtlmC1zOS00xSEiVftAbw~tUUQBQAEAAcAAA%3d%3d#!sig%3dhGWCEWntBItiqlbmJhn1nL1-WRU-lpuicb-fGRUs46vonbqGMXjjjfsE-LM9NdzPxv5pTSXmhBh8cXvgoHIiBw%3d%3d Aiwnios.com
-=> http://pixelchan.i2p/?i2paddresshelper==xws-c~-JSHVlSrjHUhqIrVgoe3gy5QQB~bYKFLXlfd-F-HUpApid1r-MGCpt05dlBrRPn~R8OfY8DBM4rCUAfr2miK-wxs0q-GazQUNuTNW8sXgYtOoqaP14zPQB6gXr6WtIDXyYehDCXVI4~tbZBPlTGl7V0CYg4KjcnnGCMLVHF6LSdtJEEkbe2lCCnDFEYpWkj5Z9lUrYyRfp0MYyqvkhEHcBbKExb53L1~dSdAobhV1vmm1pdL81aBRreCFrGZyHZHjX1cv-tEInWyoQlArsH~7zaHGkCooONmITlpd8zfCwPxR4oQ3Zta4lTI7VGWjIW4HWQAzzVNiNV1FRkHX04CY6XkVFebzPm8nv-wDGHE2sWhyoyoCyX43OHSmXdfTgJjpeRUV5vM-bye~7AMYcTaxaHKjKgLJfjc4dKZfHrfsbOl5FRXm8z5vJ7~sAxhxNrFocqMqAsl-Nzh0plwJntRx8C-pPBS9EXQq18e87vOtUF4~9UBg-UVewCJMtBQAEAAcAAA== Pixelchan
-=> http://git.plan9.i2p/?i2paddresshelper=5BxhVRDoO3GO73yHs9HuMdZtD5q7WudwVwlKvl-m-KhhyuoyLVsRsJ0rJdKmmgsIKlLOzw00LHrIRQXib3Sqk6p9sfldWN2d~d~zRhyRk8QJzMmq3qwblyc-tEy8rIr3cLlEIerlGL16qA6yTQsZt9onAnimdFmOWtcSYtPws-xPMGJOnyhWVL7f42Mvoo~8k9RqOuf1MQCKa4VAK4GLms5xu~ImcWWv6X20vtsKlfCk5thyGtLvYwgunUMU1snWyc1p-i-Y1MpKXLvZE6FhRyLS~zC5UM8BpthdRQNhtrVtvS4y6adpBpq7dHGhPPyK89FrpTL6Ktum2xsGesqWKFQB4437KSa8L40XUJOhRawK4z6gwLkcmpEvE22HLcX5VAHjjfspJrwvjRdQk6FFrArjPqDAuRyakS8TbYctxfm1GcV7-ykmvC-NF1CToUWsCuM-oMC5HJqRLxNthy3F-TTlGgY-11F~NjSI1EV0fW4MNjAtg2u4O1G4lHzB2hOTBQAEAAcAAA== git.plan9.rocks
-=> http://nadezhda-project.i2p/?i2paddresshelper=ThxzHY6RRn6XnK~dWxcIxtZQUkNkAWh4b6TPGwG9-v5OHHMdjpFGfpecr91bFwjG1lBSQ2QBaHhvpM8bAb36~k4ccx2OkUZ-l5yv3VsXCMbWUFJDZAFoeG-kzxsBvfr-ThxzHY6RRn6XnK~dWxcIxtZQUkNkAWh4b6TPGwG9-v5OHHMdjpFGfpecr91bFwjG1lBSQ2QBaHhvpM8bAb36~k4ccx2OkUZ-l5yv3VsXCMbWUFJDZAFoeG-kzxsBvfr-ThxzHY6RRn6XnK~dWxcIxtZQUkNkAWh4b6TPGwG9-v5OHHMdjpFGfpecr91bFwjG1lBSQ2QBaHhvpM8bAb36~k4ccx2OkUZ-l5yv3VsXCMbWUFJDZAFoeG-kzxsBvfr-ThxzHY6RRn6XnK~dWxcIxtZQUkNkAWh4b6TPGwG9-v5OHHMdjpFGfpecr91bFwjG1lBSQ2QBaHhvpM8bAb36~gCPTdxvLbAKskafy3JmOlBGCX27BdzHAcNqqPwlbj5lBQAEAAcAAA== Nadezhda Project Rus
-=> http://meow.i2p/?i2paddresshelper=0h7p7eyv7M5cMbyo9Vm28OyKC3jhY56R6DPhVavOOcbSHunt7K~szlwxvKj1Wbbw7IoLeOFjnpHoM-FVq845xtIe6e3sr-zOXDG8qPVZtvDsigt44WOekegz4VWrzjnG0h7p7eyv7M5cMbyo9Vm28OyKC3jhY56R6DPhVavOOcbSHunt7K~szlwxvKj1Wbbw7IoLeOFjnpHoM-FVq845xtIe6e3sr-zOXDG8qPVZtvDsigt44WOekegz4VWrzjnG0h7p7eyv7M5cMbyo9Vm28OyKC3jhY56R6DPhVavOOcbSHunt7K~szlwxvKj1Wbbw7IoLeOFjnpHoM-FVq845xtIe6e3sr-zOXDG8qPVZtvDsigt44WOekegz4VWrzjnG0h7p7eyv7M5cMbyo9Vm28OyKC3jhY56R6DPhVavOOcbSHunt7K~szlwxvKj1Wbbw7IoLeOFjnpHoM-FVq845xlG7YBRY2y5OtCrj7mC7ygzq2IZ4wr61pdmUlryV1sVvBQAEAAcAAA== meow.i2p
diff --git a/content/blogs/technology/Maths.gmi b/content/blogs/technology/Maths.gmi
deleted file mode 100644
index 85a2970..0000000
--- a/content/blogs/technology/Maths.gmi
+++ /dev/null
@@ -1,4 +0,0 @@
-# Maths
-
-=> https://zachartrand.github.io/SoME-3-Living/ How does a computer/calculator compute logarithms?
-=> https://tylerneylon.com/a/mind_model/mind_model.html A Model of a Mind
\ No newline at end of file
diff --git a/content/blogs/technology/Nix.gmi b/content/blogs/technology/Nix.gmi
deleted file mode 100644
index 88f501c..0000000
--- a/content/blogs/technology/Nix.gmi
+++ /dev/null
@@ -1,3 +0,0 @@
-# Nix
-
-=> /web/www.theregister.com/2024/05/14/nix_forked_but_over_politics/?id=article Nix forked, but over politics instead of progress
\ No newline at end of file
diff --git a/content/blogs/technology/OCaml.gmi b/content/blogs/technology/OCaml.gmi
deleted file mode 100644
index 15c6ce7..0000000
--- a/content/blogs/technology/OCaml.gmi
+++ /dev/null
@@ -1,4 +0,0 @@
-## Resources
-
-=> https://www2.lib.uchicago.edu/keith/ocaml-class/why.html OCaml for the Skeptical
-=> https://softwareengineering.stackexchange.com/questions/62685/why-isnt-ocaml-more-popular Why isn't OCaml more popular?
\ No newline at end of file
diff --git a/content/blogs/technology/Rust.gmi b/content/blogs/technology/Rust.gmi
deleted file mode 100644
index 9a79bc0..0000000
--- a/content/blogs/technology/Rust.gmi
+++ /dev/null
@@ -1,4 +0,0 @@
-## Resources
-
-=> https://ceronman.com/2021/07/22/my-experience-crafting-an-interpreter-with-rust/ My experience crafting an interpreter with Rust
-=> https://notgull.net/device-afd/ \Device\Afd, or, the Deal with the Devil that makes async Rust work on Windows
\ No newline at end of file
diff --git a/content/blogs/technology/Tor.gmi b/content/blogs/technology/Tor.gmi
deleted file mode 100644
index b965e95..0000000
--- a/content/blogs/technology/Tor.gmi
+++ /dev/null
@@ -1,35 +0,0 @@
-# Tor
-
-If you'd like to visit this site (Gemini not available) over Tor, visit:
-
-=> http://fuwnme4wbs5x36jjf2usedw2zscozwhazykhyfkjsmudtb7egs3mb7yd.onion/ fuwn.me
-
-## Hidden Wiki Links
-
-=> http://zqktlwiuavvvqqt4ybvgvi7tyo4hjl5xgfuvpdf6otjiycgwqbym2qad.onion/ Original Hidden Wiki
-=> http://jaz45aabn5vkemy4jkg4mi4syheisqn2wn2n4fsuitpccdackjwxplad.onion/ OnionLinks v3
-=> http://bj5hp4onm4tvpdb5rzf4zsbwoons67jnastvuxefe4s3v7kupjhgh6qd.onion/ Yet Another Hidden Wiki
-=> http://xsglq2kdl72b2wmtn5b2b7lodjmemnmcct37owlz5inrhzvyfdnryqid.onion/ The Hidden Wiki
-=> http://qrtitjevs5nxq6jvrnrjyz5dasi3nbzx24mzmfxnuk2dnzhpphcmgoyd.onion/ Pug's Ultimate Dark Web Guide
-=> http://torlinksge6enmcyyuxjpjkoouw4oorgdgeo7ftnq3zodj7g2zxi3kyd.onion/ TorLinks
-=> http://darkfailenbsdla5mal2mxn2uz66od5vtzd5qozslagrfzachha3f3id.onion/ dark.fail
-=> https://dark.fail/ dark.fail (WWW)
-=> http://tortaxi7axhn2fv4j475a6blv7vwjtpieokolfnojwvkhsnj7sgctkqd.onion tor.taxi
-=> https://tor.taxi/ tor.taxi (WWW)
-
-## Search Engines
-
-=> http://juhanurmihxlp77nkq76byazcldy2hlmovfu2epvl5ankdibsot4csyd.onion/ Ahhmia
-=> http://xmh57jrknzkhv6y3ls3ubitzfqnkrwxhopf5aygthi7d6rplyvk3noyd.onion/ Torch
-=> https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ DuckDuckGo
-
-## VPNs
-
-=> http://stormwayszuh4juycoy4kwoww5gvcu2c4tdtpkup667pdwe4qenzwayd.onion cryptostorm
-=> https://www.privateinternetaccess.com/ Private Internet Access (WWW)
-
-## Miscellaneous
-
-If you'd like direct links to more onion sites, please visit the following page:
-
-=> https://hiddenwikis.com/ Hidden Wiki and Dark Web Links
\ No newline at end of file
diff --git a/content/blogs/technology/Unix-like.gmi b/content/blogs/technology/Unix-like.gmi
deleted file mode 100644
index 5cb3c5f..0000000
--- a/content/blogs/technology/Unix-like.gmi
+++ /dev/null
@@ -1,3 +0,0 @@
-# *nix (Unix-like)
-
-=> https://sortix.org/blog/posix-2024/ POSIX 2024 Changes
\ No newline at end of file
diff --git a/content/blogs/technology/Web.gmi b/content/blogs/technology/Web.gmi
deleted file mode 100644
index 36f6337..0000000
--- a/content/blogs/technology/Web.gmi
+++ /dev/null
@@ -1,4 +0,0 @@
-# Web
-
-=> https://tonyalicea.dev/blog/understanding-react-compiler/ Understanding React Compiler
-=> https://ladybird.org/ Ladybird
\ No newline at end of file
diff --git a/content/blogs/technology/blog.json b/content/blogs/technology/blog.json
deleted file mode 100644
index d58ec59..0000000
--- a/content/blogs/technology/blog.json
+++ /dev/null
@@ -1,26 +0,0 @@
-{
-  "priority": 3,
-  "description": "Thoughts and Resources of the Programming Languages and Technologies I Actively Use and Have Used",
-  "posts": {
-    "Go": {
-      "author": "Fuwn",
-      "created": "2021. 07. 19.",
-      "last_modified": "2024. 06. 17."
-    },
-    "Forth": {
-      "author": "Fuwn",
-      "created": "2022. 04. 21.",
-      "last_modified": "2022. 04. 21."
-    },
-    "OCaml": {
-      "author": "Fuwn",
-      "created": "2021. 07. 23.",
-      "last_modified": "2021. 07. 23."
-    },
-    "Rust": {
-      "author": "Fuwn",
-      "created": "2021. 07. 23.",
-      "last_modified": "2021. 07. 23."
-    }
-  }
-}
\ No newline at end of file
diff --git a/content/blogs/the_daily/airpods_4_anc.gmi b/content/blogs/the_daily/airpods_4_anc.gmi
deleted file mode 100644
index fce9fb3..0000000
--- a/content/blogs/the_daily/airpods_4_anc.gmi
+++ /dev/null
@@ -1,13 +0,0 @@
-# The AirPods 4 with ANC are impressive!
-
-I've owned a few sets of AirPods since their initial release, and they've always been some of my favourite audio appliances. With the new AirPods Pro 2 and AirPods 4 released, I thought it was time to pick up a new pair.
-
-I initially purchased the AirPods Pro 2, but the pair I received had the infamous audio imbalance issue where the audio panning is constantly stronger to one side or the other. In my case, the audio balance was noticeably skewed to the left. I wasn't about to give up in the case of a one-off defect, so I picked up another pair the next day and returned the first pair. The second pair also had the same issue …. At this point, I didn't want to try my luck a third time, so I opted for mostly a side grade, the AirPods 4 with ANC (active noise-cancelling).
-
-From what I know, the AirPods 4 with ANC is missing very few features compared to the AirPods Pro 2. Most prominently, they lack the clinical hearing aid and hearing test functionality and the ability to adjust the volume using the stem controls on each AirPod. If I missed any other significant features, it likely wouldn't matter to most people, but I don't *think* I did.
-
-Even though I often use both designs throughout the day, I still find myself returning to the classic more and more. I highly prefer the classic AirPod design without the silicon ear tips over the Pro design, so I wasn't bothered by this tradeoff. With the AirPods 4 with ANC being an even better choice this generation, I could finally and confidently ditch those annoying ear tips.
-
-I've been testing the active noise cancellation on the AirPods 4 for about a week now, and they are impressive. They aren't 1:1 with the Pros since they lack that silicon ear tip to seal the audio, but they are **very** close. The AirPods 4 do an excellent job at cancelling out low and steady sounds and are also effective for higher frequency sounds. The active cancellation range does get noticeably better the further you move out, with anything about a metre out typically being silent, and anything closer in depends on its frequency. I'd rate the AirPods Pro's ANC at around 7.5‒8/10, the AirPods 4 at 6‒6.5/10 for high-frequency sounds, and again at 7.5‒8/10 for low and steady sounds.
-
-Some other compliments I have are that the battery life is great and lasts me a fantastic amount of time, the charging case is nice and small for pocketing, and the shape of the AirPods makes for a comfortable and secure fitment.
diff --git a/content/blogs/the_daily/blog.json b/content/blogs/the_daily/blog.json
deleted file mode 100644
index 513737f..0000000
--- a/content/blogs/the_daily/blog.json
+++ /dev/null
@@ -1,41 +0,0 @@
-{
-  "priority": 0,
-  "description": null,
-  "posts": {
-    "nvme_troubles_part_1": {
-      "description": null,
-      "author": "Fuwn",
-      "created": "2024. 06. 17.",
-      "last_modified": "2024. 06. 19.",
-      "name": "NVMe Troubles Part 1."
-    },
-    "nvme_troubles_part_2": {
-      "description": null,
-      "author": "Fuwn",
-      "created": "2024. 06. 17.",
-      "last_modified": "2024. 09. 03.",
-      "name": "NVMe Troubles Part 2."
-    },
-    "nvme_troubles_part_3": {
-      "description": null,
-      "author": "Fuwn",
-      "created": "2024. 09. 03.",
-      "last_modified": "2024. 09. 03.",
-      "name": "NVMe Troubles Part 3."
-    },
-    "airpods_4_anc": {
-      "description": null,
-      "author": "Fuwn",
-      "created": "2024. 10. 24.",
-      "last_modified": "2025. 02. 12.",
-      "name": "The AirPods 4 with ANC are impressive!"
-    },
-    "fixing_a_broken_time_machine_disk": {
-      "description": null,
-      "author": "Fuwn",
-      "created": "2025. 04. 18.",
-      "last_modified": "2025. 04. 18.",
-      "name": "Fixing a Broken Time Machine Disk"
-    }
-  }
-}
diff --git a/content/blogs/the_daily/fixing_a_broken_time_machine_disk.gmi b/content/blogs/the_daily/fixing_a_broken_time_machine_disk.gmi
deleted file mode 100644
index 295532a..0000000
--- a/content/blogs/the_daily/fixing_a_broken_time_machine_disk.gmi
+++ /dev/null
@@ -1,32 +0,0 @@
-I don't know how, but the primary Time Machine disk I use for my MacBook Pro became completely broken.
-
-About a month back, I started getting occasional alerts on my Mac letting me know that one of my drives could not be decrypted. I dismissed this message for quite some time as I had changed nothing and noticed no differences in my day-to-day Mac experience. I can't remember for what reason, but at some point I wanted to check out my Time Machine backups or configuration and realised that Time Machine hadn't completed a successful backup in several weeks.
-
-My first thought was to use Disk Utility's First Aid option, which only led to confusion. Below is a copy of First Aid's output.
-
-```
-Erasing “My Passport for Mac” (disk6s2) and creating “My Passport for Mac”
-
-Preparing to erase APFS Volume content
-Checking mount state
-Erasing APFS Volume disk6s2 by deleting and re-adding
-Deleting APFS Volume from its APFS Container
-Unmounting disk6s2
-Erasing any xART session referenced by XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
-Deleting Volume
-An internal error has occurred. : (-69623)
-
-Operation failed…
-```
-
-Something was wrong with the Time Machine disk.
-
-My next step in troubleshooting this issue was to try to repair the drive from a Debian VM. Running `lsblk` did not show the drive, but running `lsusb` did. Running any command to interact with the drive other than `lsusb` didn't register the drive, while `dmesg` showed that the drive was being recognised. I tried GParted just for the sake of it, but of course, it didn't work either. `usbreset` also did not make any difference, not that it should have given any previous indication.
-
-Going back to macOS was next. First, I ran `diskutil unmountDisk /dev/disk6`, then `diskUtil eraseDisk JHFS+ "My Passport for Mac" GPT /dev/disk6`. The output of this command, "You cannot manually format an existing APFS Container disk", gave me a hint as to what my next logical steps should be: deleting the APFS container.
-
-> I'll preface that the following is a destructive operation, but as this Time Machine disk is rolling, the data would have been lost regardless, so I decided to proceed.
-
-Using the previous clue, I ran `sudo diskutil apfs deleteContainer /dev/disk6`, successfully erasing the APFS container and restoring the disk to a mostly usable state. However, the disk was not yet 100% ready to be used as a Time Machine disk and required further formatting to appear in the Time Machine menu. Thankfully, this was trivial, and I accomplished it by erasing the disk and formatting it as APFS through Disk Utility. The disk was now ready to use and worked as expected.
-
-I'm unsure why there weren't any existing articles on this issue, or maybe I didn't look hard enough. Either way, if you stumble upon this blog post with a similar issue, I hope you were able to follow my briefly outlined steps and resolve any problems you may have encountered. If you happened upon this post without having gone through any similar headache and read it for the sake of learning, I hope you also found it insightful, or at least entertaining.
diff --git a/content/blogs/the_daily/nvme_troubles_part_1.gmi b/content/blogs/the_daily/nvme_troubles_part_1.gmi
deleted file mode 100644
index 35eb19e..0000000
--- a/content/blogs/the_daily/nvme_troubles_part_1.gmi
+++ /dev/null
@@ -1,29 +0,0 @@
-# NVMe Troubles Part 1.
-
-This is the second time my primary NVMe drive has failed on me in some way in the past couple of months. I’m going to go ahead and dump this here on AniList, because it was the first page that was open on my iPad.
-
-I wanted to create a temporary partition where I would install NixOS, just for fun to see if I would make the switch from Arch. During the resize, I was met with an error that I had inode discrepancies for a file and a folder. Of course, this was what I assumed to be related to source controlled temporary blob storage caches. I honestly should’ve been expecting this, as I have seen a ton of Btrfs related source control issues regarding inode discrepancies, especially with git and Chromium’s messy file system dumps.
-
-Anyway, I spent probably a good 3–4 hours trying to fix this inode discrepancy, but I was getting nowhere. Eventually. I had the smart idea to run a SMART test, but this literally froze my system and eventually led to me completely turning off my system. SMART *shouldn’t* be problematic if prematurely terminating any processes, so I went ahead and did it.
-
-Long story short, my drive was nuked … or at least I thought.
-
-I could not boot into anything. Nothing would work. Between this phrase and the following paragraph, I was checking every possible forum, video, and thread, and they were all dead ends. I started to search for drive cloning methods, and I was a few clicks away from purchasing a new NVMe along with an M.2 drive cloning rig. I was even close to resorting to data recovery services if I so had to.
-
-The first thing I tried was my GParted "LiveCD" USB drive, and this should always be anyone’s go to anyway. Well, GParted would not even boot. I don’t actually know why this was the case, even now, but something about the Wi-Fi drivers on their Debian release wasn’t working. I don’t even use Wi-Fi in the first place, and this shouldn’t be coming from my NVMe situation, since this is a LiveCD. After some trial and error, I realised that loading the environment into RAM got it to boot. GParted could not even see my NVMe, after all of that.
-
-I backed out to the BIOS, and the BIOS couldn’t see my NVMe a bit. Eventually, after a series of power cycling and leaving the NVMe to rest a few minutes, (this probably didn’t help) I was able to get the BIOS to recognise the drive. I tried to run a self-test, but that self-test failed every single time.
-
-Now, knowing that the NVMe is still visible to the motherboard, I booted back into GParted, but now, even my RAM trick wasn’t working. This too, after a few power cycles, was solved and able to boot. I’m not sure why.
-
-As I make this post, I was successfully able to mount the supposedly "failed self-test" ridden drive, and I am able to see the entirety of my root file system.
-
-What did I learn? I’m never choosing Btrfs again … *maybe*. In theory, it's great, but in practice it seems to lack stability in seemingly simple cases like this. (?) I think I'll go with XFS for NixOS, so I can stay on the edge, but Ext4's stability is appealing, and I've used Ext4 for a great deal of other devices and servers before in confidence. I still look at Btrfs with hope, but I just can't look at it with the same kind of hope after this nightmare scenario. I’ll also purchase one or two extra NVMes just in case, and perform regular full-disk backups. And I now want to switch to NixOS more than ever just so I can get rid of this broken Btrfs partitioned file system.
-
-=> https://media1.tenor.com/m/2eFcSj58UhwAAAAC/head-bang-frustrated.gif
-
-## Addendum
-
-This blog thread continues on in the second part!
-
-=> /blog/the_daily/nvme_troubles_part_2 NVMe Troubles Part 2.
\ No newline at end of file
diff --git a/content/blogs/the_daily/nvme_troubles_part_2.gmi b/content/blogs/the_daily/nvme_troubles_part_2.gmi
deleted file mode 100644
index ba3aa75..0000000
--- a/content/blogs/the_daily/nvme_troubles_part_2.gmi
+++ /dev/null
@@ -1,46 +0,0 @@
-=> /blog/the_daily/nvme_troubles_part_1 Previously on The Daily: NVMe Troubles Part 1.
-
-# NVMe Troubles Part 2.
-
-OK! I've managed to boot back into my Btrfs filesystem. The bitrot (I guess) is still present, but I don't mind. I think I'll end up moving my secondary OS over from my primary NVMe to my secondary NVMe, then create a NixOS install in-place of that partition, clone my essential files over from my primary NVMe's Arch install, and then nuke the Arch (Btrfs) partition for good.
-
-=> https://i.imgur.com/5WiE6Xs.png
-=> https://i.imgur.com/nyJ2IPN.png
-
-## Addendum
-
-I failed to mention the information about my Windows partition and what troubles came with it! I also failed to mention that I was unable to boot into my primary Arch Linux installation because systemd-boot had been wiped from my EFI boot order. Here is that discussion continued.
-
-I have a small Windows 11 partition that I exclusively use for gaming. This partition is actually running AtlasOS, a modified Windows "distribution", but that isn't too important. I don't keep anything on this install other than games and a browser.
-
-Throughout my scrambling to revive my NVMe, and after I had been able to get my BIOS to recognise the NVMe, the only boot entry that was available other that my GParted live USB was the Windows Boot Manager entry belonging to this OS. I don't know why this was the case, but I assume that it was some safety mechanism for Windows to wipe out the rest of the order, since I have had Windows overwrite my boot entries before.
-
-Anyway, at some point, I tried to launch into Windows using this boot entry, but I was getting instant system failures. After trying to get through about three times, I was prompted with a new screen that gave me a few options, such as navigating back to my BIOS interface, or trying to boot into Windows. I tried booting back into Windows, and I was met with a BSOD so fast that I couldn't even see the message properly. I went ahead and tried to record my screen using my phone, and I was able to retrieve the BSOD with an error status of 0xc0000001, and some information telling me that my Boot Configuration Data was in a terrible state.
-
-At this point, I gave up, as both the information on Windows' system failure screen and the information I found online was letting me know that I'd had to flash a Windows installation media to a USB to access any usable troubleshooting tooling. Thankfully, skipping over some that I've already in the original post above, I was able to boot into my primary Arch Linux installation and use it like nothing ever happened, minus the bit-rotted directory.
-
-Fast-forward about a day. I'd like to play Wuthering Waves, so I have to boot into my Windows install. Windows still doesn't work, so I have to fix that.
-
-I got around to flashing the AtlasOS installation media to a spare USB and getting into the troubleshooting menu, and after attempting the automatic rescue, a load of command-line tools, and more guides, still, nothing could bring back my system. My final resort was to try the System Restore functionality of Windows.
-
-I'll preface this segment by outright stating that I have not once ever had a successful interaction with the System Restore feature. I've had two instances where a Windows installed potentially could have been saved by one, but in neither case did the System Restore either help, or even work due to the System Restore point itself being corrupt. In the past, I have disabled this feature from the first available moment, as to not waste my time and "drive space".
-
-Whatever, I'll give it a try. I opened the system restore menu, and I was extremely surprised to see that I had a few points I could restore from. The latest one was from either the 8th or 9th of June, 2024, so that would be about ten days away as of the writing of this addendum.
-
-> If anyone is wondering, this System Restore point was one made by some version of the Microsoft Visual C++ Redistributable, and I actually remember that the Lossless Scaling application from Steam requested this resource.
-
-The System Restore feature has this feature that allows you to view the programs affected from this would be system restore, so I clicked it. Apparently, some registry, and I'm not sure exactly which, since I've been hit with a boat load of these types of messages by now, but some registry was corrupted and beyond saving, so I could not check which programs would be affected by this would be System Restore point.
-
-That doesn't inspire confidence, but screw it, it can't hurt to try it anyway, right? So I give the installation media the go ahead to try and apply the restore point. What do you know it, the system goes through a short, roughly three minute process of applying this restore point, and then another short reboot, and I'm back in my Windows installation as it was the day it left me.
-
-From what I was informed by Windows, System Restores don't touch your personal documents, and I don't keep any in this partition anyway, but I now had my system fully back in operation. Between the less than ten days between now and the System Restore point's capture date, the only part of my system that changed was literally the removal of the Visual C++ Redistributable. So System Restore **is** a valuable feature!
-
-Let's reflect. Why does a SMART status check render an NVMe unrecognisable, wipe the first boot entry (systemd-boot, in this case), cause Windows to destroy its own BCD (Boot Configuration Data), and more? (I could go on, but I've already written about it!) Who knows! I don't think we'll ever understand the black system that we call practical computing.
-
-> Thanks, Lossless Scaling for requiring Visual C++!
-
-## Addendum #2
-
-This blog thread continues on in the third part!
-
-=> /blog/the_daily/nvme_troubles_part_3 NVMe Troubles Part 3.
\ No newline at end of file
diff --git a/content/blogs/the_daily/nvme_troubles_part_3.gmi b/content/blogs/the_daily/nvme_troubles_part_3.gmi
deleted file mode 100644
index 328a4ea..0000000
--- a/content/blogs/the_daily/nvme_troubles_part_3.gmi
+++ /dev/null
@@ -1,31 +0,0 @@
-=> /blog/the_daily/nvme_troubles_part_2 Previously on The Daily: NVMe Troubles Part 2.
-
-# NVMe Troubles Part 3.
-
-This may not be the crash and burn scenario you were expecting after this three part series, but you might be surprised to learn that the NVMe drive is still up and running months later after some "questionable treatment".
-
-I'll also mention that the events of this post are about two months old, but the process wasn't too complicated that I'd forget the details. You'd also expect that I would have gotten around to finally fixing the Btrfs partition just before I wanted to install the long awaited NixOS, but, no, I actually just had a spurt of motivation sometime in the AM.
-
-## The Repair
-
-At this point in my Btrfs filesystem saga, I had tried all but cloning-wiping-restoring my partition and/or NVMe and `btrfs check --repair`. I can't recall the exact message, although, with the amount of times I've seen it at this point, I should, but the message that `btrfs check --repair` usually gives is something along the lines of "Only run this command if you are OK with losing your data or a Btrfs developer tells you to."—I think. I didn't want to deal with the cloning BS, so I'll bite the bullet and go with Btrfs's obscure repair functionality that **absolutely no one** advises using.
-
-To prepare, I wanted to save at least some of my data. I don't actually care about any directories on my system apart from my home directory and some `/etc/` files, so I'll back them up accordingly.
-
-During my backup endeavours, I tried a few methods, but ultimately, I wasn't satisfied with any of the results. One method was `rsync`-ing everything, another was zipping everything into an archive, and I also tried plain copying. One annoyance was that I was cloning from a Linux filesystem to a NTFS one, which was giving me all kinds of pain with file permissions and other metadata. I also ditched `rsync` and zipping in the end, because they didn't produce the expected results in one way or another. Backing up from userland is not fun, I guess. That, and I already had sunk a few hours into the ordeal, so it just wasn't worth my time.
-
-By this stage, I think my exact thoughts were "Screw it, `--repair` can't be that bad. It exists for a reason." I run the forsaken `btrfs check --repair` without any remorse. Maybe it was the adrenaline, but the repair felt like it had gone through almost instantly. It couldn't have been longer than around a minute or two, at the absolute most.
-
-In these moments of post-repair bliss, I ran `btrfs check` to verify if the repair had done anything at all, and the previous errors were nowhere to be seen. I also did some digging in the mounted filesystem, and everything seemed to look and function just how I left it. Booting back into Arch also went fine, not that I couldn't before, but I was just making sure I hadn't screwed anything up again.
-
-Functionality, I gained nothing, since the filesystem and drive still worked perfectly fine, even with the inode errors screaming at me; however, I'd now finally be able to modify the drive through GParted. If I hadn't mentioned already, GParted runs a `btrfs check` before any operations on a Btrfs partition, which is why I'd eventually need to repair the partition to continue on with my plans to install NixOS, so I spared future me the trouble.
-
-## The Aftermath
-
-I used my system like normal for a few weeks, after which I went on a month long holiday abroad, away from my rig, and I wasn't about to attempt to install NixOS via SSH, although, the steps to do so are documented within the NixOS installation instructions.
-
-Spoiler alert, but I did install NixOS, and I'm currently writing this post on it. It's definitely the best Linux distribution I've used so far, and just from the short experience I've had with it, I can tell you that I can't see myself ever using anything else. I might write a post about it soon, so keep an eye out for that.
-
-## Conclusion
-
-I won't go as far as to say use `btrfs check --repair`, but if a filesystem has strictly inode-related errors, I think it might be the quickest, and possibly even safest, way to fix them. I could have just gotten lucky, but I'm not one to tempt fate, so I'll just leave it at that.
\ No newline at end of file