new blog post, tagging recent blog posts

content/blog/2024/dedicated-instant-messaging-was-better.md

@@ -7,6 +7,10 @@ reply_to:
   author: flamedfury
   title: Instant Messaging
 subtitle: This didn't start out as a rant about Discord, but it sure ended that way.
+categories:
+  - Internet
+tags:
+  - social media
 ---
 
 fLaMEd's post about instant messaging programs got me thinking about my own IM journey. I'm too young to really have experienced the peak AIM and MSN days, but I did use MSN/Windows Live Messenger in the late 00s to keep up with some online friends I had met through various forums. Eventually, I moved to Skype as that is what all my IRL friends were on at the time. I was also on Curse Voice for the brief time it existed, mostly for voice calls during League of Legends matches. As Skype started dying out, I moved over to Discord in 2016, which made me a pretty early adopter.  

content/blog/2024/happy-belated-js-naked-day.md

@@ -0,0 +1,35 @@
+---
+title: "Happy (Belated) JS Naked Day"
+date: 2024-04-26T17:12:11-07:00
+year: "2024"
+subtitle: Woah three blog posts in a week(ish) is unheard of
+categories:
+  - Internet
+tags:
+  - smallweb
+  - web development
+---
+
+[JS Naked Day](https://js-naked-day.org/) happened this week, and as usual, I'm fashionably late. I decided to permanently remove a significant portion of the JavaScript from my site as it was affecting load times. There wasn't a whole lot of JavaScript to begin with, which made this pretty easy to implement. What I did have was the following:
+
+## 1. A script to randomly select from an array of quotes to display in the sidebar on each page load
+
+I just removed this as I just wasn't finding it amusing anymore. Maybe it will return later, who knows? Certainly not me.
+
+## 2. A script to change the avatar frame color in the sidebar
+
+I had originally implemented this using Hugo's templates, as I described in my post [Recreating the Windows Live Messenger Avatar in CSS](/blog/2024/02/windows-live-avatar-css), but opted for JavaScript instead because I wouldn't need to constantly rebuild my site. I had said rebuilding periodically was a waste of compute time, which was kind of bullshit because instead I was wasting the compute time of every visitor on every page load. So now I've gone back to the template approach, and build my website periodically every hour, unless I push out an update before then. Previously this was done with a bash script, but I rewrote it in python to separate the build step from the updating from git step so that I could do each at different intervals.
+
+## 3. Status.cafe widget
+
+I love status.cafe, it's a really easy way to get some dynamic content on your static website. The downside of this is that every page load is hitting m15o's servers twice: first to grab the linked JavaScript file and then to run it and grab a second json file with the actual status information. This took about 1.1s to complete from beginning to end, again, *on every page load*. To speed things up, I hacked together a partial template in Hugo that downloads the json file directly on build, using Hugo's [resources.GetRemote](https://gohugo.io/functions/resources/getremote/) function.
+
+## 4. Webmentions.js
+
+Webmentions.js is just a way to display webmentions that you've received. Which is pretty handy, except I receive almost zero webmentions. The ones I do receive often come from Mastodon via [Brid.gy](https://brid.gy/), which I've come to realize is [problematic from a privacy standpoint](https://brainbaking.com/post/2023/05/why-i-retired-my-webmention-server/). I'm going to remove my webmention support for a lot of the reasons listed in this post, which mirrors my experience with them. The places I get reactions to the stuff I write on my website are the places where I go and manually post links, usually Mastodon and the [32bit cafe](https://discourse.32bit.cafe), and it's just easier to reply to people on there. There's no real reason to syndicate those replies on my site. If I really care about adding webmention support again, I can probably find a way to do it during the website build rather than live via JavaScript.
+
+## 5. tinylytics
+
+This is the only JavaScript file I'm keeping. I really like the simplicity of tinylytics. I get to see what pages are most popular and an overall viewcount, and it's not at all intrusive. It loads behind the scenes on each page so it does not affect load times, and if you were to block JavaScript it does not lessen the user experience at all.
+
+I'm not opposed to using JavaScript, but the cool stuff I was doing with it could be just as easily done with my static site generator. JavaScript may make a return to my website if I find something else cool to do with it, but for now I will just enjoy the super fast load times!

content/blog/2024/music-discovery-is-weird.md

@@ -5,6 +5,8 @@ year: "2024"
 subtitle: "Algorithms suck, except when they don't"
 categories:
   - Life
+tags:
+  - music
 ---
 
 As a teenager, the music I listened to was music my dad shared with me, music my friends would play when we would hang out, or music from video games and movies I liked. I remember spending time on Pandora creating stations based off my favorites in hopes I could find something similar I liked. I would discover a few songs this way but otherwise didn't have much luck. As a result, I find I just listen to the same stuff over and over again, but there is so much music out there, I want to find more! But how?

themes/dreamcast/layouts/partials/tags.html

@@ -2,6 +2,6 @@
 {{ with .GetTerms $taxonomy }}
     {{ range $k, $_ := . -}}
         {{ if $k }}, {{ end }}
-        <a class="tag" href="{{ .RelPermalink }}">#{{ .LinkTitle }}</a>
+        <a class="tag" href="{{ .RelPermalink }}">{{ .LinkTitle }}</a>
     {{- end }}
 {{ end }}

themes/dreamcast/static/css/main.css

@@ -123,7 +123,7 @@ a.tag {
 }
 
 a.tag:hover, a.tag:active {
-    color: var(--secondary-link-hover);
+    text-decoration: underline;
 }
 
 a.category {