From e1ec4a112907f4aebad56b2b388eceb3969e6e88 Mon Sep 17 00:00:00 2001
From: Pinapelz <yukais@pinapelz.com>
Date: Fri, 12 Jun 2026 18:30:42 -0700
Subject: unify microblog

---
 src/components/FormattedDate.astro                 |   7 +-
 src/components/Header.astro                        |   1 +
 src/content/blog/micro-blog-merged.md              |  12 ++
 src/content/config.ts                              |  21 ++-
 src/content/micro/01-hello-world.md                |  28 ++++
 src/content/micro/02-china-town-fair/gloves.webp   | Bin 0 -> 431668 bytes
 src/content/micro/02-china-town-fair/index.md      |  24 ++++
 .../micro/02-china-town-fair/inside-ctf.webp       | Bin 0 -> 1020876 bytes
 .../micro/02-china-town-fair/outside-ctf.webp      | Bin 0 -> 355348 bytes
 src/content/micro/03-power-bank-recall.md          |  24 ++++
 src/content/micro/04-yt-music-rewind.md            |   8 ++
 src/content/micro/05-procon2-hid-tool.md           | 155 +++++++++++++++++++++
 src/content/micro/06-first-sdvx-18/18.webp         | Bin 0 -> 339632 bytes
 src/content/micro/06-first-sdvx-18/index.md        |   9 ++
 src/content/micro/07-arcade-monsters-sd/cab1.webp  | Bin 0 -> 506938 bytes
 src/content/micro/07-arcade-monsters-sd/cab2.webp  | Bin 0 -> 379430 bytes
 .../micro/07-arcade-monsters-sd/danevo.webp        | Bin 0 -> 384012 bytes
 src/content/micro/07-arcade-monsters-sd/index.md   |  55 ++++++++
 src/content/micro/07-arcade-monsters-sd/view1.webp | Bin 0 -> 952802 bytes
 src/content/micro/07-arcade-monsters-sd/view2.webp | Bin 0 -> 436422 bytes
 src/content/micro/08-ffxiv-patch-7-4.md            |  33 +++++
 src/content/micro/09-dbox-review.md                |  16 +++
 src/content/micro/10-discord-rant.md               |  24 ++++
 .../11-hundred-lines-last-defense-playlog/index.md |  31 +++++
 .../playtime.png                                   | Bin 0 -> 25402 bytes
 src/content/micro/12-april-playlog.md              |  95 +++++++++++++
 src/content/micro/13-dac-vs-wireless-dap.md        |  78 +++++++++++
 src/pages/index.astro                              |  24 ++++
 src/pages/micro/[...slug].astro                    |  20 +++
 src/pages/micro/index.astro                        |  54 +++++++
 src/pages/rss.xml.js                               |  14 +-
 31 files changed, 725 insertions(+), 8 deletions(-)
 create mode 100644 src/content/blog/micro-blog-merged.md
 create mode 100644 src/content/micro/01-hello-world.md
 create mode 100644 src/content/micro/02-china-town-fair/gloves.webp
 create mode 100644 src/content/micro/02-china-town-fair/index.md
 create mode 100644 src/content/micro/02-china-town-fair/inside-ctf.webp
 create mode 100644 src/content/micro/02-china-town-fair/outside-ctf.webp
 create mode 100644 src/content/micro/03-power-bank-recall.md
 create mode 100644 src/content/micro/04-yt-music-rewind.md
 create mode 100644 src/content/micro/05-procon2-hid-tool.md
 create mode 100644 src/content/micro/06-first-sdvx-18/18.webp
 create mode 100644 src/content/micro/06-first-sdvx-18/index.md
 create mode 100644 src/content/micro/07-arcade-monsters-sd/cab1.webp
 create mode 100644 src/content/micro/07-arcade-monsters-sd/cab2.webp
 create mode 100644 src/content/micro/07-arcade-monsters-sd/danevo.webp
 create mode 100644 src/content/micro/07-arcade-monsters-sd/index.md
 create mode 100644 src/content/micro/07-arcade-monsters-sd/view1.webp
 create mode 100644 src/content/micro/07-arcade-monsters-sd/view2.webp
 create mode 100644 src/content/micro/08-ffxiv-patch-7-4.md
 create mode 100644 src/content/micro/09-dbox-review.md
 create mode 100644 src/content/micro/10-discord-rant.md
 create mode 100644 src/content/micro/11-hundred-lines-last-defense-playlog/index.md
 create mode 100644 src/content/micro/11-hundred-lines-last-defense-playlog/playtime.png
 create mode 100644 src/content/micro/12-april-playlog.md
 create mode 100644 src/content/micro/13-dac-vs-wireless-dap.md
 create mode 100644 src/pages/micro/[...slug].astro
 create mode 100644 src/pages/micro/index.astro

(limited to 'src')

diff --git a/src/components/FormattedDate.astro b/src/components/FormattedDate.astro
index 1bcce73..fd9f7a6 100644
--- a/src/components/FormattedDate.astro
+++ b/src/components/FormattedDate.astro
@@ -1,14 +1,15 @@
 ---
 interface Props {
-	date: Date;
+	date: Date | string | number;
 }
 
 const { date } = Astro.props;
+const formattedDate = date instanceof Date ? date : new Date(date);
 ---
 
-<time datetime={date.toISOString()}>
+<time datetime={formattedDate.toISOString()}>
 	{
-		date.toLocaleDateString('en-us', {
+		formattedDate.toLocaleDateString('en-us', {
 			year: 'numeric',
 			month: 'short',
 			day: 'numeric',
diff --git a/src/components/Header.astro b/src/components/Header.astro
index d8a68b0..14ff099 100644
--- a/src/components/Header.astro
+++ b/src/components/Header.astro
@@ -94,6 +94,7 @@ import { SITE_TITLE } from '../consts';
     <HeaderLink href="/">Home</HeaderLink>
     <HeaderLink href="/blog">Blog</HeaderLink>
     <HeaderLink href="/about">About</HeaderLink>
+    <HeaderLink href="/micro">Micro</HeaderLink>
     <HeaderLink href="/rss.xml">RSS</HeaderLink>
   </nav>
   <div class="logo">
diff --git a/src/content/blog/micro-blog-merged.md b/src/content/blog/micro-blog-merged.md
new file mode 100644
index 0000000..47e633b
--- /dev/null
+++ b/src/content/blog/micro-blog-merged.md
@@ -0,0 +1,12 @@
+---
+title: 'Microblog Unification'
+description: 'TLDR: This blog will now also host stuff on my old microblog'
+pubDate: 'Jun 12 2026'
+---
+Quite some time ago, I started writing and posting about more random stuff on my microblog. This was previously hosted on `micro.pinapelz.moe`, and as the yearly renewal of the domain came around I decided to re-evaluate a number of the ways I was running things.
+
+One of these things was realizing that it doesn't make sense to maintain 2 seperate blogs, it would be far easier if I had a single deployment pipeline and one place that hosts what I write.
+
+As a result, `/micro` will host random and sporadic content, and the RSS feed will be updated to also contain these posts.
+
+That's all for now!
diff --git a/src/content/config.ts b/src/content/config.ts
index b4e86c9..e2c62ca 100644
--- a/src/content/config.ts
+++ b/src/content/config.ts
@@ -18,4 +18,23 @@ const blog = defineCollection({
 	}),
 });
 
-export const collections = { blog };
+const micro = defineCollection({
+	// Type-check frontmatter using a schema
+	schema: z.object({
+		title: z.string(),
+		description: z.string(),
+		// Transform string to Date object
+		pubDate: z
+			.string()
+			.or(z.date())
+			.transform((val) => new Date(val)),
+		updatedDate: z
+			.string()
+			.optional()
+			.transform((str) => (str ? new Date(str) : undefined)),
+		heroImage: z.string().optional(),
+	}),
+});
+
+
+export const collections = { blog, micro };
diff --git a/src/content/micro/01-hello-world.md b/src/content/micro/01-hello-world.md
new file mode 100644
index 0000000..e481c00
--- /dev/null
+++ b/src/content/micro/01-hello-world.md
@@ -0,0 +1,28 @@
+---
+title: "Hello World - Why This"
+description: ''
+pubDate: Dec 1 2025
+---
+I think having control of your own data is great. The same is true for decentralized social media. I've always been a primary user of microblog platforms (like Twitter/X). Having experienced both the traditional and "decentralized" approaches to microblogs, they both have some particular shortcoming in terms of what I want to get out of "social media".
+
+## Twitter/X
+This is fairly self explanatory. The rebranding of Twitter to X and Musk's new ownership of the platform shifted the direction of the platform to be ever more political. X Premium boosting visibility is also something I wasn't a particular fan of. You can't view anything without signing in either, so goodbye viewing stuff anonymously. There's just a lot of "features" here I'm not a fan of. Needless to say, there's a lot of reasons to not post stuff there.
+
+
+## Fediverse
+I initially moved to the `Fediverse` (on Misskey/Sharkey). Interoperability between different platforms is very cool, and the wide variety of platforms to choose from means that picking any platform never made me feel like "missing out" elsewhere.
+
+However, this in itself has a problem. If you create an account on someone else's instance, you are a part of their *walled garden*. Now I'm sure that they are a wonderful person who equally values data ownership/agency, however it doesn't change the fact that someone else holds your content/data and you rely on them for that service.
+
+So then the alternative here is self-hosting a single person instance. This solves everything, **BUT** the fact that its quite expensive to pay for the bandwidth + storage if you are a small instance and end up federating with a lot of instances. This wasn't a compromise I wanted, since the name of the game with the Fediverse is being able to connect cross-platform. Great if you have the resources, but not particularly worth it for a single person starting fresh. There's not really a good way to handle this right now, which is why federation with a very large platform like Threads is limited.
+
+## Bluesky
+`Bluesky` is one of the drop-in alternatives for Twitter. Its built on the AT-Protocol, which does actually solve a lot of the problems of ActivityPub (Fediverse) in terms of handling small self-hosted instance with large ones.
+AtProto allows you to host a `PDS (Personal Data Server)` which stores all your own posts, profile info, and follows. This boils down to meaning that you really only need to be responsible for serving your own content, which you also own on your own machine. There's also a lot of fine-grain features that help with not getting overwhelmed by firehose traffic.
+
+While this is great, the issue is that the service is not truly "federated" (yet?). Its still early days for the platform and protocol, Most people are still on `bsky.social`. This means that to get anything to read at all you'd still need to pull from the big central relay. Even if we were successful in this, its not entirely clear what the costs would be for running all these components together (is it even worth it for a single person?). I think AtProto is promising, but its still early days and who knows where it'll go...
+
+# Now What
+Its time to try something new. From a surface view the idea of [IndieWeb](https://indieweb.org/) is a good solution from the perspective of creating the content. You basically just build a website/blog (which nowadays is dirt cheap to host something static), you then just add some special HTML ([microformats](https://indieweb.org/microformats)) and now you've got a common protocol similar to a post (only now you can leverage the power of HTML/CSS and customize it however you want). Then implemtning [webmentions](https://indieweb.org/Webmention) gives the ability for other people to interact with your content. Using a bridging/syndication service like [Bridgy Fed](https://fed.brid.gy/) you can post to the Fediverse and Bluesky as well as allow others from there to interact with your post.
+
+So that's what this is. Let's see how it goes.
diff --git a/src/content/micro/02-china-town-fair/gloves.webp b/src/content/micro/02-china-town-fair/gloves.webp
new file mode 100644
index 0000000..fd42b6c
Binary files /dev/null and b/src/content/micro/02-china-town-fair/gloves.webp differ
diff --git a/src/content/micro/02-china-town-fair/index.md b/src/content/micro/02-china-town-fair/index.md
new file mode 100644
index 0000000..6f4ae84
--- /dev/null
+++ b/src/content/micro/02-china-town-fair/index.md
@@ -0,0 +1,24 @@
+---
+title: "China Town Fair"
+description: 'One of the most legendary arcades in history'
+pubDate: Dec 2 2025
+---
+Visited New York during the Thanksgiving break and had a chance to stopped by one of the most legendary landmarks North American arcade gaming history.
+
+{{< figure src="outside-ctf.webp" alt="China Town Fair Outside" >}}
+
+Also yep you're reading that right, it indeed once home to a [dancing chicken as well as one that played tic tac toe](https://davidpotorti.substack.com/p/the-dancing-chicken).
+
+But apart from just being an old arcade, it was also home to one of the largest competitive arcade game fighting scene (Marvel vs Capcom, Street Fighter, etc.). Many of NAs top players frequented this arcade. However, as we all already know video arcades began to die down during the early 2000s and China Town Fair was no exception having closed in 2011.
+
+Then it re-opened under new management and became a complete shell of its former self. These days its pretty much all redemption slop in there. Very few actual "games" in there; there's a DDR A3 cab, PIU, a singular jubeat with a broken audio mod, a fully broken down SDVX Nemsys, and 3 Wangan 5DX+ (not sure what happened to the 4th one).
+
+{{< figure src="inside-ctf.webp" alt="China Town Fair Inside" >}}
+
+Anyways, its pretty tiny in there and feels like its not doing amazing. A single credit for jubeat was like 3-4 USD I think, and one of the machines to reload cards was fully broken down (tbh just go to Round1 and play).
+
+If you want some actual rhythm games though, walk like 6 minutes and the newly opened "Akiba House" store has private networked maimai DX, WACCA (modded), and CHUNITHM.
+
+{{< figure src="gloves.webp" alt="Chinese maimai gloves" width="300" >}}
+
+Also I was absolutely not ready for the New York winter temps. Thankfully I always keep my rhythm game gloves on me which saved my hands from freezing.
diff --git a/src/content/micro/02-china-town-fair/inside-ctf.webp b/src/content/micro/02-china-town-fair/inside-ctf.webp
new file mode 100644
index 0000000..d08d15f
Binary files /dev/null and b/src/content/micro/02-china-town-fair/inside-ctf.webp differ
diff --git a/src/content/micro/02-china-town-fair/outside-ctf.webp b/src/content/micro/02-china-town-fair/outside-ctf.webp
new file mode 100644
index 0000000..aacc4e2
Binary files /dev/null and b/src/content/micro/02-china-town-fair/outside-ctf.webp differ
diff --git a/src/content/micro/03-power-bank-recall.md b/src/content/micro/03-power-bank-recall.md
new file mode 100644
index 0000000..1fa80af
--- /dev/null
+++ b/src/content/micro/03-power-bank-recall.md
@@ -0,0 +1,24 @@
+---
+title: "INIU Power Bank Gets Recall"
+description: ''
+pubDate: Dec 2 2025
+---
+It would seem that I, along with what seems like the entirety of [Reddit](https://www.reddit.com/r/amazonprime/comments/1pcq5ug/how_to_get_customer_support_for_recall_iniu/) bought the same cheap 10000mAh power bank and now its getting recalled.
+
+I wonder if it has anything to do with the poor quality they found in that viral [Haribo Powerbank](https://www.lumafield.com/first-article/posts/whats-hiding-inside-haribos-power-bank-and-headphones). Not sure since I've had this one for a long time. I guess I really got what I paid for, shame cause it really is super slim and works well.
+
+**But I'd definetly prefer for it not to blow up on me**
+
+Here's the full notice:
+
+>Dear Amazon Customer,
+>
+>We have learned of a potential safety issue regarding certain product(s) that our records indicate you purchased through the Amazon.com website.
+>
+>For more details on what you should do, please contact INIU at recall@iniu.shop.
+>
+>Product: INIU Portable Charger, Slimmest 10000mAh 5V/3A Power Bank, USB C in&out High-Speed Charging Battery Pack, External Phone Powerbank Compatible with iPhone 16 15 14 13 12 Samsung S22 S21 Google iPad etc
+>
+>If you made this purchase for someone else, please notify the recipient immediately and provide them with the information.
+>
+>We regret any inconvenience this may cause you but trust you will understand that the safety and satisfaction of our customers is our highest priority.
diff --git a/src/content/micro/04-yt-music-rewind.md b/src/content/micro/04-yt-music-rewind.md
new file mode 100644
index 0000000..19ab97c
--- /dev/null
+++ b/src/content/micro/04-yt-music-rewind.md
@@ -0,0 +1,8 @@
+---
+title: "YouTube Music Recap 2025"
+description: ''
+pubDate: Dec 3 2025
+---
+Its all Bandori. At least 75% of that MyGO!!!!! listening time was probably Haruhikage since I came back to Bandori and had to catch up before watching Ave Mujica anime.
+
+{{< figure src="https://files.catbox.moe/tsquqc.jpg" alt="YouTube Music Recap Top 5 Artists In Order: MyGO!!!!!, Yumenokessho, Ave Mujica, KMNZ, Roselia" width="300" >}}
diff --git a/src/content/micro/05-procon2-hid-tool.md b/src/content/micro/05-procon2-hid-tool.md
new file mode 100644
index 0000000..88f5fd4
--- /dev/null
+++ b/src/content/micro/05-procon2-hid-tool.md
@@ -0,0 +1,155 @@
+---
+title: "Enable HID Mode on Nintendo Pro Controller 2"
+description: 'Script for enabling HID on Procon2 Devices'
+pubDate: Dec 5 2025
+---
+Switch 2 Pro Controller is very comfy in my hands, but unfortunately it didn't work out of box on PC (Linux) for me like it's predacessor. Until there's actual better driver support for this thing in the kernel (or Valve does something), here's a hacky Python script to initialize HID-mode on the controller 
+
+```python
+# I only tested this script on Linux w/ Steam but in theory it shoud work on Windows?
+import usb.core # install pyusb first: pip install pyusb
+import usb.util
+import time
+import sys
+
+VENDOR_ID = 0x057E
+PRODUCT_IDS = {
+    0x2066: "Joy-Con (L)",
+    0x2067: "Joy-Con (R)",
+    0x2069: "Pro Controller",
+    0x2073: "GCN Controller"
+}
+
+USB_INTERFACE_NUMBER = 1
+
+INIT_COMMAND_0x03 = bytes([0x03, 0x91, 0x00, 0x0d, 0x00, 0x08, 0x00, 0x00, 0x01, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF])
+UNKNOWN_COMMAND_0x07 = bytes([0x07, 0x91, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00])
+UNKNOWN_COMMAND_0x16 = bytes([0x16, 0x91, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00])
+REQUEST_CONTROLLER_MAC = bytes([0x15, 0x91, 0x00, 0x01, 0x00, 0x0e, 0x00, 0x00, 0x00, 0x02, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF])
+LTK_REQUEST = bytes([0x15, 0x91, 0x00, 0x02, 0x00, 0x11, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF])
+UNKNOWN_COMMAND_0x15_ARG_0x03 = bytes([0x15, 0x91, 0x00, 0x03, 0x00, 0x01, 0x00, 0x00, 0x00])
+UNKNOWN_COMMAND_0x09 = bytes([0x09, 0x91, 0x00, 0x07, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00])
+IMU_COMMAND_0x02 = bytes([0x0c, 0x91, 0x00, 0x02, 0x00, 0x04, 0x00, 0x00, 0x27, 0x00, 0x00, 0x00])
+OUT_UNKNOWN_COMMAND_0x11 = bytes([0x11, 0x91, 0x00, 0x03, 0x00, 0x00, 0x00, 0x00])
+UNKNOWN_COMMAND_0x0A = bytes([0x0a, 0x91, 0x00, 0x08, 0x00, 0x14, 0x00, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x35, 0x00, 0x46, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00])
+IMU_COMMAND_0x04 = bytes([0x0c, 0x91, 0x00, 0x04, 0x00, 0x04, 0x00, 0x00, 0x27, 0x00, 0x00, 0x00])
+ENABLE_HAPTICS = bytes([0x03, 0x91, 0x00, 0x0a, 0x00, 0x04, 0x00, 0x00, 0x09, 0x00, 0x00, 0x00])
+OUT_UNKNOWN_COMMAND_0x10 = bytes([0x10, 0x91, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00])
+OUT_UNKNOWN_COMMAND_0x01 = bytes([0x01, 0x91, 0x00, 0x0c, 0x00, 0x00, 0x00, 0x00])
+OUT_UNKNOWN_COMMAND_0x03 = bytes([0x03, 0x91, 0x00, 0x01, 0x00, 0x00, 0x00])
+OUT_UNKNOWN_COMMAND_0x0A_ALT = bytes([0x0a, 0x91, 0x00, 0x02, 0x00, 0x04, 0x00, 0x00, 0x03, 0x00, 0x00])
+
+def send_usb_data(ep_out, ep_in, data, description=""):
+    try:
+        ep_out.write(data)
+        time.sleep(0.01)
+        try:
+            response = ep_in.read(32, timeout=100)
+            hex_resp = " ".join([f"{x:02x}" for x in response])
+            print(f"[{description}] Response: {hex_resp}")
+        except usb.core.USBError as e:
+            if e.errno == 110:
+                print(f"[{description}] No response (Timeout)")
+            else:
+                print(f"[{description}] Read Error: {e}")
+
+    except usb.core.USBError as e:
+        print(f"[{description}] Write Error: {e}")
+        raise
+
+def set_player_leds(ep_out, ep_in, led_mask):
+    command = [
+        0x09, 0x91, 0x00, 0x07, 0x00, 0x08, 0x00, 0x00,
+        led_mask,
+        0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
+    ]
+    send_usb_data(ep_out, ep_in, bytes(command), f"Set LED Mask: 0x{led_mask:02x}")
+
+def connect_usb():
+    print("Searching for Nintendo Switch Controllers...")
+    def match_device(dev):
+        return dev.idVendor == VENDOR_ID and dev.idProduct in PRODUCT_IDS
+    dev = usb.core.find(custom_match=match_device)
+    if dev is None:
+        raise ValueError("Device not found")
+
+    product_name = PRODUCT_IDS.get(dev.idProduct, "Unknown Device")
+    print(f"Found {product_name} (ID: {dev.idProduct:04x})")
+    if dev.is_kernel_driver_active(USB_INTERFACE_NUMBER):
+        try:
+            print("Detaching kernel driver...")
+            dev.detach_kernel_driver(USB_INTERFACE_NUMBER)
+        except usb.core.USBError as e:
+            sys.exit(f"Could not detach kernel driver: {e}")
+    try:
+        dev.set_configuration()
+        print("Configuration set.")
+    except usb.core.USBError as e:
+        print(f"Error setting configuration: {e}")
+    try:
+        usb.util.claim_interface(dev, USB_INTERFACE_NUMBER)
+        print(f"Interface {USB_INTERFACE_NUMBER} claimed.")
+    except usb.core.USBError as e:
+        sys.exit(f"Could not claim interface: {e}")
+    cfg = dev.get_active_configuration()
+    intf = cfg[(USB_INTERFACE_NUMBER,0)]
+    ep_out = usb.util.find_descriptor(
+        intf,
+        custom_match = lambda e:  usb.util.endpoint_direction(e.bEndpointAddress) == usb.util.ENDPOINT_OUT)
+
+    ep_in = usb.util.find_descriptor(
+        intf,
+        custom_match =
+        lambda e: usb.util.endpoint_direction(e.bEndpointAddress) == usb.util.ENDPOINT_IN
+    )
+
+    if not ep_out:
+        sys.exit("Could not find OUT endpoint")
+
+    print(f"Found Endpoint OUT: 0x{ep_out.bEndpointAddress:02x}")
+    print("Starting Initialization Sequence...")
+
+    try:
+        send_usb_data(ep_out, ep_in, INIT_COMMAND_0x03, "Init 0x03")
+        send_usb_data(ep_out, ep_in, UNKNOWN_COMMAND_0x07, "Unknown 0x07")
+        send_usb_data(ep_out, ep_in, UNKNOWN_COMMAND_0x16, "Unknown 0x16")
+        send_usb_data(ep_out, ep_in, REQUEST_CONTROLLER_MAC, "Req MAC")
+        send_usb_data(ep_out, ep_in, LTK_REQUEST, "Req LTK")
+        send_usb_data(ep_out, ep_in, UNKNOWN_COMMAND_0x15_ARG_0x03, "Unknown 0x15")
+        send_usb_data(ep_out, ep_in, UNKNOWN_COMMAND_0x09, "Unknown 0x09")
+        send_usb_data(ep_out, ep_in, IMU_COMMAND_0x02, "IMU 0x02")
+        send_usb_data(ep_out, ep_in, OUT_UNKNOWN_COMMAND_0x11, "OUT Unknown 0x11")
+        send_usb_data(ep_out, ep_in, UNKNOWN_COMMAND_0x0A, "Unknown 0x0A")
+        send_usb_data(ep_out, ep_in, IMU_COMMAND_0x04, "IMU 0x04")
+        send_usb_data(ep_out, ep_in, ENABLE_HAPTICS, "Enable Haptics")
+        send_usb_data(ep_out, ep_in, OUT_UNKNOWN_COMMAND_0x10, "OUT Unknown 0x10")
+        send_usb_data(ep_out, ep_in, OUT_UNKNOWN_COMMAND_0x01, "OUT Unknown 0x01")
+        send_usb_data(ep_out, ep_in, OUT_UNKNOWN_COMMAND_0x03, "OUT Unknown 0x03")
+        send_usb_data(ep_out, ep_in, OUT_UNKNOWN_COMMAND_0x0A_ALT, "OUT Unknown 0x0A Alt")
+        set_player_leds(ep_out, ep_in, 0x0F)
+
+        print("Controller initialization sequence complete! All LEDs should be on.")
+
+    except Exception as e:
+        print(f"Error during sequence: {e}")
+
+if __name__ == "__main__":
+    try:
+        connect_usb()
+    except ValueError as e:
+        print(e)
+    except Exception as e:
+        print(f"Unexpected error: {e}")
+```
+**Steps**
+
+0. (Optional) First Create a virtual environment
+1. Install pyusb via `pip install pyusb`
+2. Plug your Pro Controller 2 in via USB
+3. Run the script
+
+If all 4 of the player indicator LEDs light up (the square ones near the charging port), then that means you should be good to go!
+
+You'll need to re-run this script each time you plug/unplug or restart your machine.
+
+This is pretty much a copy of the [online Procon 2 Enabler Tool](https://handheldlegend.github.io/procon2tool/) but WebHID is dodgy on the Firefox fork I'm using, plus its annoying having to open this page each time.
diff --git a/src/content/micro/06-first-sdvx-18/18.webp b/src/content/micro/06-first-sdvx-18/18.webp
new file mode 100644
index 0000000..83768f7
Binary files /dev/null and b/src/content/micro/06-first-sdvx-18/18.webp differ
diff --git a/src/content/micro/06-first-sdvx-18/index.md b/src/content/micro/06-first-sdvx-18/index.md
new file mode 100644
index 0000000..bd5c34d
--- /dev/null
+++ b/src/content/micro/06-first-sdvx-18/index.md
@@ -0,0 +1,9 @@
+---
+title: "First MXM 18 Cleared!"
+description: ''
+pubDate: Dec 6 2025
+---
+Cleared my first 18 difficulty chart in {{< hashtag "sdvx" >}}
+
+Albeit its not a very difficult one, but I think I'm finally starting to chip away at the 17-18 difficulty wall.
+{{< figure src="18.webp" alt="Sound Voltex Enchant 6 Clear" width="500" >}}
diff --git a/src/content/micro/07-arcade-monsters-sd/cab1.webp b/src/content/micro/07-arcade-monsters-sd/cab1.webp
new file mode 100644
index 0000000..6f30510
Binary files /dev/null and b/src/content/micro/07-arcade-monsters-sd/cab1.webp differ
diff --git a/src/content/micro/07-arcade-monsters-sd/cab2.webp b/src/content/micro/07-arcade-monsters-sd/cab2.webp
new file mode 100644
index 0000000..6b5f02f
Binary files /dev/null and b/src/content/micro/07-arcade-monsters-sd/cab2.webp differ
diff --git a/src/content/micro/07-arcade-monsters-sd/danevo.webp b/src/content/micro/07-arcade-monsters-sd/danevo.webp
new file mode 100644
index 0000000..c15d1f5
Binary files /dev/null and b/src/content/micro/07-arcade-monsters-sd/danevo.webp differ
diff --git a/src/content/micro/07-arcade-monsters-sd/index.md b/src/content/micro/07-arcade-monsters-sd/index.md
new file mode 100644
index 0000000..6c502e6
--- /dev/null
+++ b/src/content/micro/07-arcade-monsters-sd/index.md
@@ -0,0 +1,55 @@
+---
+title: "Arcade Monsters"
+description: 'A view of Arcade Monsters in San Diego'
+pubDate: Dec 18 2025
+---
+If you live in Socal and are also into arcade gaming (both retro and modern), one of the great weekend day-trips I've found is taking the Pacific Surfliner train down to San Diego. 
+
+# Getting There
+There are a number of departures in the morning, and while not as fast as a car when there's no traffic, you can save your energy and do other stuff on the train. The timetable also works nicely since you can pretty much get there around opening if you want to beat the crowds.
+
+Once you get there, you can either take the trolley or walk 20 minutes to the arcade. I prefer the walk since you can grab some food/coffee on the way.
+
+Plus the view is excellent.
+
+{{< figure src="view1.webp" alt="Ocean view from the Pacific Surfliner" width="700" >}}
+{{< figure src="view2.webp" alt="Ocean view from the Pacific Surfliner" width="700" >}}
+
+# Value
+So is this trip worth it and what is the cost?
+
+Arcade Monsters games operate all on "Free Play", you pay a set fee for entry and can stay for as long as you'd like. Its $25 to enter, or $35 if you want to be able to leave and come back.
+
+Since there aren't exactly a lot of "retro" arcades anymore, I'll compare the value proposition here to Round1:
+
+At Round1 a standard rhythm games is roughly 8.6 credits per play. If we estimate the value of a Round1 credit to be around $0.15 (assuming standard non-member $120 package for 777 credits), this would put 1 play at around $1.29. This means it takes roughly 20 plays to hit $25.
+
+Let's also say that a single play at any rhythm game takes roughly 10 minutes. Assuming you continuously played games This means $25 of Round1 credits would last you roughly 3.3 hours. So just this on its own, without considering anything else I'd say that this is great value just on its own. 
+
+But if you were to include transportation costs, assuming around $60 for a round-trip ticket via train, it becomes a little more difficult to justify since for the same price since you'd be able to play 46 rounds of something else at Round1.
+
+However, with the variety of games in there (even rarer ones), I'd say this is still an excellent trip. I personally could easily stay 5+ hours in there (cause I'm a degenerate and they also sell food + drinks in there).
+
+{{< figure src="cab1.webp" alt="Arcade Cabinets" width="500" >}}
+
+# Quality
+Most of the retro stuff is very well maintained and in great working condition. Also many of the modern games are networked and have card saving features.
+
+However, it'd be dishonest to say that these cabs are in excellent condition:
+- The Sound Voltex knobs are basically falling off, the switches don't feel great
+- The pads ghosts on Dancerush and the navigation keys are broken
+- FutureTomTom drums have sensitivity issues
+- Small things like how the stool for Ongeki doesn't match the height of the standard seat.
+
+Also it gets busy in there and is also a popular spot for families (kids get loud).
+
+{{< figure src="cab2.webp" alt="Arcade Cabinets" width="500" >}}
+
+# Conclusion
+Overall, as a once in a while its great value. You get to try out a ton of games, some of which are even considered rare to come by in Japan. If you also just want to go in and hardcore grind out some CHUNITHM, I can see that as a pretty good option too.
+
+Check out the list of games [here](https://zenius-i-vanisher.com/v5.2/arcade.php?id=9155&section=games#games)
+
+{{< figure src="danevo.webp" alt="Arcade Cabinets" width="500" >}}
+
+{{< hashtag "arcade" >}}
diff --git a/src/content/micro/07-arcade-monsters-sd/view1.webp b/src/content/micro/07-arcade-monsters-sd/view1.webp
new file mode 100644
index 0000000..b7463ba
Binary files /dev/null and b/src/content/micro/07-arcade-monsters-sd/view1.webp differ
diff --git a/src/content/micro/07-arcade-monsters-sd/view2.webp b/src/content/micro/07-arcade-monsters-sd/view2.webp
new file mode 100644
index 0000000..21956d9
Binary files /dev/null and b/src/content/micro/07-arcade-monsters-sd/view2.webp differ
diff --git a/src/content/micro/08-ffxiv-patch-7-4.md b/src/content/micro/08-ffxiv-patch-7-4.md
new file mode 100644
index 0000000..bcee492
--- /dev/null
+++ b/src/content/micro/08-ffxiv-patch-7-4.md
@@ -0,0 +1,33 @@
+---
+title: "Playlog: FFXIV Dawntrail Patch 7.4 Thoughts (spoilers)"
+description: 'Playlog #1'
+pubDate: Dec 19 2025
+---
+*This is primarily focused on the content of the patch, not so much the features they've added.*
+
+# Story
+- Mistwake Dungeon was a good difficulty. Although I'm not a fan of the electricity star AOEs, very hard to read for no apparent reason. Please just stick with the old one.
+- Cutscene quality def. got better. As in animations and uniqueness.
+- Love the look and feel (Treno). There's a ton of good spots for "gpose-ing". Music is nice too.
+- Seriously Krile? You parents were the ones who dropped you into the Source. I don't think they'd care if you wanted to stay in the Source (just make up your mind) -> well glad that got sorted out
+- "Hell on Rails" Trial (Doomtrain) is very nicely designed. Its got some nice unique mechanics, the "sucking" mechanic definetly trips you up the first time because the distance to move back + timing has been tuned so that you need to pre-position for it.
+- The transition from inside the engine to outside was really cool!!! This is probably one of my top normal trials now.
+- The instance battle was well done too. The roleplaying part was on point, and when it was finally time to fight a real boss you get to play as yourelf (I think this is the best flow). Love the idea using the spriggan to avoid Behemoth's meteor.
+- Cool so we just get to keep the key. If this were any bit realistic, we've surely learned that no one this powerful should be allowed to keep the key on themsleves 24/7. Because surely the WoL being the most powerful being will never run rogue with a interdimensional travel capable tool. Then again, seeing how stuff gets stolen all the time in the story... Well I guess it can go either way.
+- I'm guessing this key is gonna be how the writers justify being able to travel to new worlds for post-Zodiark/Hydaelyn story. Its fine I guess, but a little disappointing it isn't something more unique.
+- And what do you know. Ascians. I hope we get something unqiue for 8.0... I guess thats fine but please lets not have it just be SHB all over again.
+
+# Raid
+- "Feral Fandom" -> Yep thats FF14 NA playerbase for you.
+- Heavyweight 1 (Vamp Fatale) Raid was cool and unique, but a bit too flashy imo. That Half Moon is needlessly large, wish we'd stop with mechanics that are designed to trick people even when read correctly.
+- Heavyweight 2 (Xtremes) I take it back, this is the one with the blinding effects MY EYES. Fire and water one after another. This is a pretty hard normal fight actually (the first time you run it blind). Really punishing for bad AOE placement positions since you can effectively be cut off from the team.
+- Holy wow these cutscenes are in serious need of voice acting. Its a good story but so dry and awkward without it.
+- Heavyweight 3 (Tyrant). Really? Behemoth again, double dipping from the instance battle. There's so many other cool FF monsters. I like the arena, it fits the guy well, all about history of the Arcadion/tradition. Fight is underwhelming and too easy imo, apart from 1 single trick mechanic that can cause a wipe...
+- Heavyweight 4 (Lindwurm). EVERYTHING BURNS. This fight was honestly too easy, zero deaths everything can be read. 2nd phase was underhelming.
+- Overall the story here while not as in depth and relevant to the story as Endwalker raids, still had a nice little twist at the end I def did not expect. Enjoyed it!
+
+# Misc
+- The new Frontline map is "dangerous". Overall the new capturing point system is far better than a non-interruptable interact like in Onsal Hakir. The snowman and aurora events are also good, and I think they come in right when they're needed too (to spice things up/allow for a turning point). 
+- The map design however is far too complex, all these bridges and everywhere and invisible walls. It does add a lot of chokepoints but also makes it difficult to navigate from point A -> B (but partially I guess this is done cause the map does feel smaller than Onsal).
+
+{{< hashtag "ffxiv" >}}
diff --git a/src/content/micro/09-dbox-review.md b/src/content/micro/09-dbox-review.md
new file mode 100644
index 0000000..90a4370
--- /dev/null
+++ b/src/content/micro/09-dbox-review.md
@@ -0,0 +1,16 @@
+---
+title: "DBOX Movie Seats"
+description: ''
+pubDate: Dec 31 2025
+---
+There's a thing here in Canada where certain theaters have these special seats that rumble and move in motion with whats happening on screen.
+
+I recently saw the new Avatar (Fire and Ash) in one of these seats. It wasn't a bad experience but given the markup, I don't think its worth it:
+
+- First it is fun (sometimes). For example when they were flying through the air, the seat would tilt in the motion of them flying. Or when there was an explosion/gunfire, the seat would rumble
+- However, for me I think they overdid it at times, literately the seat would move and rumble for the smallest things. So it was kind of like a constant thing throughout the whole film. For me its a bit annoying
+- For the $10-15 extra (I think I paid a bit more cause the movie was also in 3D), I'd much rather just go to a theater that has the big comfy recliner seats
+- I think for the right movie (maybe something heavy on action or horror) this could be a solid purchase if its a movie you're really looking forward to
+- Or I also know that some people see movies multiple times, so maybe this can be a good option for a 2nd viewing?
+
+Generally, though... I think I'll live without them.
diff --git a/src/content/micro/10-discord-rant.md b/src/content/micro/10-discord-rant.md
new file mode 100644
index 0000000..d7050e8
--- /dev/null
+++ b/src/content/micro/10-discord-rant.md
@@ -0,0 +1,24 @@
+---
+title: "Discord Rant"
+description: ''
+pubDate: Feb 19 2026
+---
+We've seen time and time again that there is "no such thing as a free lunch". The same is true for Discord.
+
+1. Offer a service that is much better than all the competitors
+2. Attract a bunch of users
+3. Burn VC money
+4. Repeat 1-3 until its time to pay them back
+5. Figure out how to make money
+
+Nitro doesn't fund the platform, hosting free voice and screenshare is more expensive than you think. Ultimately, any choice of software for me boils down to "what value do I get out of it". 
+
+Look, free is free, and nothing can and will ever beat the value of free. There's still plenty of reasons to move even if you are a free user, but that's not the point of this. What I want to take a look at is what value you are actually getting as a paying user.
+
+If you wanted to take advantage of ALL of Discord's features, such as the higher quality screen share + audio or vanity for servers; you need to buy Nitro and boost your server. Nitro comes out to $99.99 a year for Nitro and around $490 a year for the 14 boosts to Tier 3. For me, it feels like the company if scavenging for opportunities to make money, making features like server banners and vanity links paid (which I suppose is how capitalism works, but for what you get at that price point it seems ridiculous). Even if we lower it down to no Nitro and just 2 boosts to get the additional custom emoji slots on a server, **that's still around $6 a month**.
+
+Let's say you do opt for this $6 price point. Is it good value? I suppose it depends. I can spin up Teamspeak 6 and Matrix on a CPX11 for 6 Euros a month from Hetzner. Services that give me all the features from the start without all the paywalling BS. In fact, Discord can capture this as well if they changed their pricing model, but I believe their too deep into this situation where they now have to fund the free users or risk everyone migrating elsewhere.
+
+Not to mention, the Discord client has gotten progressively worse over the years, all these accessories and animations do is lag out the client which they don't even seem to understand the codebase of anymore.
+
+What Discord sells is convenience, regardless of the Face ID or data collection, the value is not there and hasn't been there from a "running a small community" perspective. There's much better options where you have much more agency over your data, as well as have more fine-grain control over optimizing cost. I suppose you can think of it as going to McDonalds or actually making dinner.
diff --git a/src/content/micro/11-hundred-lines-last-defense-playlog/index.md b/src/content/micro/11-hundred-lines-last-defense-playlog/index.md
new file mode 100644
index 0000000..b94d630
--- /dev/null
+++ b/src/content/micro/11-hundred-lines-last-defense-playlog/index.md
@@ -0,0 +1,31 @@
+---
+title: "Playlog: Hundred Lines Last Defense Academy"
+description: 'Playlog #2'
+pubDate: Mar 17 2026
+---
+After about a year of playing on and off, I've finally finished all 100 (and 1, counting the first one). In total it took roughly 105 hours or so.
+{{< figure src="playtime.png" alt="105 hours or more played" >}}
+
+## Core Mechanics
+- This is basically a visual novel, there's very little fun to be had if you are a "cutscene skipper". If you enjoyed Kodaka's other works like Danganronpa then you'll be right at home.
+- There's a bunch of smaller "minigames" but are mostly a one-off thing, they feel mostly like an afterthought (+25)
+
+## Structure
+- There's 2 main parts of the game, the battling and the story itself
+- The battling itself has a decent amount of strategy to it, and you can in fact easily lose if you're not careful for some of them
+- In my opinion though given how little variety there is it kinda gets old fast, luckily the 2nd half of the game lets you skip battles you've already done
+- As far as the story goes, its standard visual novel stuff but with a Kodaka twist. Each ending belongs to a particular "route" which is centered around a particular storyline, each one is also explicitly named in the game's flowchart. (+20)
+
+## Content
+- The story itself is quite good, but not all the routes are really worth doing if you just want what I consider to be the "core" of the plot. Some of them basically lead to nothing and are there just for fun.
+- Everyone has to play through `Last Defense Academy 1` which basically acts as a very long prologue for the actual game
+- **Not Necessary:** Serial Battles Route (PLEASE skip this one, the game forces you to play unskippable battles and it forshadows literately the tiniest thing), Box of Blessings, Conspiracy (does nothing but is very quick to do), Romance, Comedy, V’ehxness Route (mainly character building), Reset Route
+- I would recommend playing through the prologue, then explicitly following a guide for the `Last Defense Academy 2nd Scenario`, then if you still want more start the S.F Route and follow a guide to unlock the pre-requisite routes while you progress through that. Everything else is largely optional IMO and is just for world-building. (12)
+
+## Technical Execution
+Its fine overall. You can def. tell they didn't have as big of a budget as Danganronpa to work with. There were some issues with leaving the game in suspense for too long on Switch but no major performance issues (+15)
+
+## Presentation
+Was good since I'm a Danganronpa fan. I would've liked to see a few more tracks or at least variations in boss fights. It does get a bit repetitive after 100 times... Still a surprising number of lines were voiced so props to them! (+14)
+
+**(86/100)**
diff --git a/src/content/micro/11-hundred-lines-last-defense-playlog/playtime.png b/src/content/micro/11-hundred-lines-last-defense-playlog/playtime.png
new file mode 100644
index 0000000..bde1097
Binary files /dev/null and b/src/content/micro/11-hundred-lines-last-defense-playlog/playtime.png differ
diff --git a/src/content/micro/12-april-playlog.md b/src/content/micro/12-april-playlog.md
new file mode 100644
index 0000000..da05672
--- /dev/null
+++ b/src/content/micro/12-april-playlog.md
@@ -0,0 +1,95 @@
+---
+title: "Playlog: April 2026 (No Sleep for Kaname Date, Xenoblade 1 DE, Catherine Full Body)"
+description: 'Playlog #3'
+pubDate: Apr 26 2026
+---
+I've gotten quite good at actually making progress on my backlog. Turns out the answer was to just uninstall all social media and get rid of doom scrolling. I invested in a rudimentary capture card as well so that I can have my Switch games show up as an application on my PC rather than having to swap display inputs (which makes it easy to get up and running for a quick session).
+
+```bash
+mirror-switch () {
+    dev=${1:-/dev/video6}
+    nohup ffplay -f v4l2 -framerate 100 -video_size 1920x1080 -i "$dev" \
+        -fflags nobuffer -flags low_delay -framedrop >/dev/null 2>&1 &
+}
+```
+The delay is actually pretty good, I'm able to play something like Fall Guys on it just fine! Now onto the playlog.
+
+# No Sleep for Kaname Date – From AI: The Somnium Files
+This is a spin-off game that takes place in between the first and second AI: The Somnium Files game. Its relatively short.
+
+![](https://files.catbox.moe/8rhr2j.jpg)
+
+## 1. Core Mechanics
+The game has a similar style to the first and second game, where you enter Sommnium (the dream world) of people to uncover some truth. However, it also introduces an escape room mechanic where you need to solve puzzles to escape a given room. This is essentially the same mechanic as what's in the "Zero Escape" series, so much so that each escape room opens with the same "Seek a way out" screen.
+
+![](https://files.catbox.moe/hz2jxm.img)
+
+For the puzzle solving, that's just entirely dependent on how good you are at reading between the lines. For most of them, once you eventually do figure out how to do it you'll feel dumb not noticing earlier. The Sommnium exploration segment though is still in my opinion plagued with the issue of where you are sort of just "guessing and checking" based on very loose clues. I suppose that's intended, but I wish that the correct options to pick become a bit more apparent not just from exploring around Sommnium but also from clues in the real outside world. (+32)
+
+## 2. Structure
+The progression of the story is near identical to the first and second game. You read through the story visual novel style, then jump into Sommnium. Only now it alternates between Sommnium and an escape room. The challenges in both are well designed and interesting, but I personally felt that some of the escape rooms were a bit random? I mean the rooms bared little relevance to the AI The Sommnium world for the most part (which I wish it did). (+20)
+
+## 3. Content
+The game follows Kaname Date and AIBA the AI-Ball, who are investigating a new case where Iris Sagan (from the first game) goes missing. A mysterious figure named Akemi tells Iris that she is participating in the "Third Eye Game".
+
+The story explains some details of what's been going on between the first and second game. Even the tiny details. The story is pretty self-contained for the most part, and its sorta like a mini-adventure. There is indeed an actual twist like every Uchikoshi game so pay attention to your surroundings. Very enjoyable to play through (+15)
+
+## 4. Technical Execution (15)
+No issues here, plays great on the Switch 2. (+15)
+
+# 5. Presentation (15)
+In my opinion, the game is a bit on the short side considering the price point. The content is good though. I'd say grab it if its on sale for 40 USD rather than 50 USD (+13)
+
+**92/100**
+
+---
+# Xenoblade 1: DE
+Covers the base game, not including the DLC.
+
+![](https://files.catbox.moe/2hfxo4)
+
+## 1. Core Mechanics
+Combat is much more simple than the second game and for me it sorta gets repetitive quick. Found myself avoiding monsters towards the end of the game. I'd say definetly try playing different characters to keep things fresh. The friendship tree thing is kind of useless and confusing, same with the gemstones. It just feels like they aren't really needed and just add onto the things to do. In my opinion they should've kept it to just upgrading gear and obtaining arts. (+28)
+
+## 2. Structure
+This game is grindy. Doesn't matter what people say, you do need to stop and kill stuff as well as do side quests otherwise the enemy level outpaces you fast. This kinda got old for me so what I did was I would grind levels on casual mode and then switch back to normal mode when progressing through the story. Other than that the progression in the game is fairly linear and follows a central plot. The one side quest that may be worth doing is restoring Colony 6 which sorta acts like a big sidequest spanning multiple chapters in the story. Other than just for world building, much of the sidequests are just fetch-quests and are kind of drab. (+15)
+
+## 3. Content
+I thought the story was just alright for me. It does end up being quite "anime", I would say it only really ramps up towards the last couple chapters. Before that we're largely just adventures, adventuring around. It does provide good context for the second game. Shulk as a character definetly has some serious plot armor, even in some cases he just sorta comes back from the dead. Still, I do think the story is worth seeing (+15)
+
+## 4. Technical Execution
+No issues here, plays great on the Switch 2. (+15)
+
+# 5. Presentation
+The voice acting and dialogue... it certainly leaves something to be desired. Well the second game sorta suffered the same issue. I played on full English though. YMMV. (+10)
+
+**83/100**
+
+---
+# Catherine Full Body
+It's a puzzle game. But more erotic.
+
+![](https://files.catbox.moe/o1169e.jpg)
+
+## 1. Core Mechanics
+Absolutely no qualms here. Its a genius little puzzle game with lots of strategy involved. You'd really have to watch some footage of it to understand how it works. (+35)
+
+![](https://files.catbox.moe/7atzn3.png)
+
+## 2. Structure
+For me, the puzzles aren't too repetitive. There's a nice break in between each one, and each night (after a set of puzzles) you get to watch a bit more of the story. Most of the game outside of the puzzle takes place in the "stray sheep" bar, the best way I can describe it is like Persona 3/4/5 "Free Time" where you can go around talking to your friends or others in the bar. Despite the small area there's a fair amount of extra lore here, since you'll start noticing that many of the people you talk to are also the ones appearing in your nightmare.
+
+The only thing I didn't like is that it wasn't really clear who you had to talk to if you wanted to "progress time". It may seem a bit confusing, but essentially once you have done everything in the bar, people get up and leave and new people walk in (this effectively progresses the night in free-time). (+23)
+
+## 3. Content
+The story of the game revolves around the main character *Vincent*. Its a short game about dealing with societal pressures. I say that but the game is quite funny, and it doesn't take too long to beat. Vincent himself is a bit of a bozo, most of the game is linear and decided for you up until the very end. Essentially the game has you answer questions that make you reflect on your personal morals, then at the end this decides which ending you get. I don't think this is a bad thing, but I would've liked to see more player agency at different points of the game rather than only at the end. Not a huge deal though (+13).
+
+## 4. Technical Execution
+The only thing that annoyed me was that for some reason the spike blocks are kinda laggy on the Switch 2? Not sure why. (+14)
+
+## 5. Presentation
+Based on the start of the game I thought this game would be extremely "goon-bait" but actually it wasn't. Very fun with lots of replayability (in terms of challenge yourself to puzzles + multiplayer) (+15)
+
+If you see this game on sale, definelty give it a try. Not sure if its worth at full-price but when its on sale for less than 10 bucks its a steal!
+
+**95/100**
diff --git a/src/content/micro/13-dac-vs-wireless-dap.md b/src/content/micro/13-dac-vs-wireless-dap.md
new file mode 100644
index 0000000..4970366
--- /dev/null
+++ b/src/content/micro/13-dac-vs-wireless-dap.md
@@ -0,0 +1,78 @@
+---
+title: "Portable Audio: Phone, Wireless DAC, or DAP"
+description: 'A comparison of portable audio solutions'
+pubDate: May 3 2026
+---
+
+Supposedly, there's been a [resurgence in the popularity of the iPod](https://www.facebook.com/APNews/videos/secondhand-sales-of-apple-ipods-are-surging-four-years-after-it-was-killed-off-w/1278247987103509/) in the recent months for all sorts of reasons. While I'm well aware of "MP3 Players", such as the original iPod and the old Sony Walkman, these are not devices I grew up using. As a "new-gen" audiophile myself, getting a DAP (Dedicated Audio Player, its the new term for these sort of devices as they can play much more than just MP3s) was certainly an interesting idea. However, modern day audiophiles now have an arsenal of methods to enjoy music, even when it comes to portable playback.
+
+> **PREFACE**
+>
+> I'll assume that you already have some basic audiophile knowledge, and that you have your own reasons for maintaining an audio library independent of streaming services.
+
+I've reduced it down to 3 main categories: 1. Using your phone with a dongle DAC (Digital to Analog Converter), 2. Wireless DAC (via Bluetooth), 3. Dedicated DAP. Now that I own one of each, I'd like to share my opinions on each one.
+
+# Phone with Dongle DAC
+This is probably something most people are familiar with so I won't go into too much detail. 
+```diff
++ easy access to streaming services
++ excellent user interface (software)
++ excellent audio quality so long as you don't buy a SUPER cheap dongle
+- distractions whether from notifications or having to fiddle with app
+- drains your battery
+- dongles/cables are annoying when tethered to your phone
+- if you maintain your own music library, it will take up additional storage/use data (especially for FLACs)
+- minimal physical button media controls
+```
+
+# Wireless DAC
+A wireless DAC is exactly what it sounds like. Rather than a traditional dongle DAC that plugs into your phone, a wireless DAC connects to your phone over Bluetooth. Your headphones/IEMs then plug into the DAC itself which is what makes it a wireless experience.
+
+This effectively allows you to use any IEM or Headphone as a wireless one, and provides a largely tangle free experience since you're free to leave the DAC in your pocket while you take your phone out to do things.
+
+For reference I have the FiiO BTR7, so most of the points below will be focused on that.
+
+```diff
++ connects to phone, so easy streaming, great UI
++ largely tangle-free, you can take your phone in and out of your pockets without the dongle getting in the way
++ can also be used as a wired DAC with PC or phone
++ EQ customization, even if your phone doesn't support it software-wise
++ support for high bit-rate coding technologies (such as Sony's LDAC which supports up to 990kbps) (1)
++ drives high-impedance headphones
+- still drains your battery a lot
+- have to charge it, or else its no better than a dongle DAC
+- better physical button media controls, but for most DACs its minimal
+- can get pricey (relatively to what you are getting)
+- you still need to use data/storage whether you are streaming or listening to files
+```
+`(1) If you're on iOS only AAC is supported, thanks Apple (250-260kbps)`
+
+This option alone has been excellent for using my IEMs on the go just for the sake of not having to fiddle with a dongle. Usually the battery life on these things are fantastic, and they last a really long time. Most streaming services also likely won't exceed 990kbps regardless, so its not a huge compromise either.
+
+The biggest caveat here is that it suffers from a lot of the same issues with battery and data/storage usage that listening from a smartphone has.
+
+# Dedicated Audio Player
+There is a wide variety of DAPs out there. Some of them even run Android which almost makes them a phone. I'll focus more on a budget option, that being the Snowsky Echo Mini.
+
+```diff
++ distraction free listening, hassle free in terms of tangling
++ physical buttons to control media + volume
++ stores your music, doesn't take up storage
++ EQ customization
++ looks cool :)
+- need to charge it or else its a brick
+- can get pricey as well, but lots of budget friendly options
+- you'll probably have to buy a micro-sd or equiv. to expand the storage on it
+- need to manually add music to it (duh...)
+- doesn't do streaming (2)
+```
+> Side Note
+>
+> Depending on how expensive your DAP is it may have other limitations such as only supporting a certain bit depth or not supporting ReplayGain. If you don't have a decently organized library this can be annoying to work around
+
+`(2) Some DAPs also have the option to do music streaming, although in my opinion that largely defeats the whole purpose since it would probably be more worth it to pick up a cheap phone just for that`
+
+Another benefit of the Echo Mini is that it can also be used as a dongle DAC if necessary. The main caveat here is that you need to be good about maintaining/tagging your audio library, and of course you don't get any audio from your phone (although that's a plus in terms of cutting out distractions for me, if I need to take a call I'll just use the built-in speaker as is)
+
+# Conclusion
+I find myself using my DAP the most, since it doesn't drain my phone's battery and has been helpful in training my patience in terms of not doomscrolling (since I literately will not be able to hear the audio). Although I do usually bring the wireless DAP along too on most days in case I want to watch a video or something. Both devices are tiny so its no big deal.
diff --git a/src/pages/index.astro b/src/pages/index.astro
index c2129e0..3886d8f 100644
--- a/src/pages/index.astro
+++ b/src/pages/index.astro
@@ -9,6 +9,11 @@ import FormattedDate from "../components/FormattedDate.astro";
 const posts = (await getCollection("blog")).sort(
   (a, b) => a.data.pubDate.valueOf() - b.data.pubDate.valueOf()
 );
+
+const microposts = (await getCollection("micro")).sort(
+  (a, b) => a.data.pubDate.valueOf() - b.data.pubDate.valueOf()
+);
+
 ---
 
 <!DOCTYPE html>
@@ -50,6 +55,22 @@ const posts = (await getCollection("blog")).sort(
           }
         </ul>
       </section>
+      <h2>Recent MicroPosts</h2>
+      <section>
+        <ul>
+          {
+          microposts
+              .slice(-5)
+              .map((post) => (
+                <li>
+                  <FormattedDate date={post.data.pubDate} />
+                  <a href={`/micro/${post.slug}/`}>{post.data.title}</a>
+                </li>
+              ))
+              .reverse()
+          }
+        </ul>
+      </section>
       <h1>
         👋 Greetings, Adventurer
       </h1>
@@ -58,6 +79,9 @@ const posts = (await getCollection("blog")).sort(
         archive my thoughts and processes on various topics or projects. It'll pretty much
         just be whatever I feel like writing about, posts will be very infrequent so don't expect much.
       </p>
+      <p>
+          Blog posts are regular long form writing about some technical concept, MicroPosts are all over the place and are usually quite unstructured. The RSS feed combines both of these.
+      </p>
       <p>Check out the main site as well: <a href="https://pinapelz.com">pinapelz.com</a></p>
       </p>
     </main>
diff --git a/src/pages/micro/[...slug].astro b/src/pages/micro/[...slug].astro
new file mode 100644
index 0000000..0ad6f8b
--- /dev/null
+++ b/src/pages/micro/[...slug].astro
@@ -0,0 +1,20 @@
+---
+import { CollectionEntry, getCollection } from 'astro:content';
+import BlogPost from '../../layouts/BlogPost.astro';
+
+export async function getStaticPaths() {
+	const posts = await getCollection('micro');
+	return posts.map((post) => ({
+		params: { slug: post.slug },
+		props: post,
+	}));
+}
+type Props = CollectionEntry<'micro'>;
+
+const post = Astro.props;
+const { Content } = await post.render();
+---
+
+<BlogPost {...post.data}>
+	<Content />
+</BlogPost>
diff --git a/src/pages/micro/index.astro b/src/pages/micro/index.astro
new file mode 100644
index 0000000..7393216
--- /dev/null
+++ b/src/pages/micro/index.astro
@@ -0,0 +1,54 @@
+---
+import BaseHead from '../../components/BaseHead.astro';
+import Header from '../../components/Header.astro';
+import Footer from '../../components/Footer.astro';
+import { SITE_TITLE, SITE_DESCRIPTION } from '../../consts';
+import { getCollection } from 'astro:content';
+import FormattedDate from '../../components/FormattedDate.astro';
+
+const posts = (await getCollection('micro')).sort(
+	(a, b) => a.data.pubDate.valueOf() - b.data.pubDate.valueOf()
+);
+---
+
+<!DOCTYPE html>
+<html lang="en">
+	<head>
+		<BaseHead title={SITE_TITLE} description={SITE_DESCRIPTION} />
+		<style>
+			ul {
+				list-style-type: none;
+				padding: unset;
+			}
+			ul li {
+				display: flex;
+			}
+			ul li :global(time) {
+				flex: 0 0 130px;
+				font-style: italic;
+				color: #646464;
+			}
+			ul li a:visited {
+				color: #8e32dc;
+			}
+		</style>
+	</head>
+	<body>
+		<Header />
+		<main>
+			<section>
+				<ul>
+					{
+						posts.map((post) => (
+							<li>
+								<FormattedDate date={post.data.pubDate} />
+								<a href={`/micro/${post.slug}/`}>{post.data.title}</a>
+							</li>
+						))
+					}
+				</ul>
+			</section>
+		</main>
+		<Footer />
+	</body>
+</html>
diff --git a/src/pages/rss.xml.js b/src/pages/rss.xml.js
index 6fed721..83f4946 100644
--- a/src/pages/rss.xml.js
+++ b/src/pages/rss.xml.js
@@ -3,15 +3,21 @@ import { getCollection } from 'astro:content';
 import { SITE_TITLE, SITE_DESCRIPTION } from '../consts';
 
 export async function GET(context) {
-	const posts = await getCollection('blog');
-	posts.sort((a, b) => new Date(b.data.pubDate).getTime() - new Date(a.data.pubDate).getTime());
+	const blogPosts = await getCollection('blog');
+	const microPosts = await getCollection('micro');
+	const posts = [...blogPosts, ...microPosts];
+	posts.sort(
+		(a, b) =>
+			new Date(b.data.pubDate).getTime() -
+			new Date(a.data.pubDate).getTime()
+	);
 	return rss({
 		title: SITE_TITLE,
 		description: SITE_DESCRIPTION,
 		site: context.site,
 		items: posts.map((post) => ({
 			...post.data,
-			link: `/blog/${post.slug}/`,
+			link: `/${post.collection}/${post.slug}/`,
 		})),
 	});
-}
\ No newline at end of file
+}
-- 
cgit v1.2.3