+ 
{% else %}
- 
+ 
{% endif %}
diff --git a/src/_includes/partials/media/music/recent.liquid b/src/_includes/partials/media/music/recent.liquid
index c4400d7e..23108c0b 100644
--- a/src/_includes/partials/media/music/recent.liquid
+++ b/src/_includes/partials/media/music/recent.liquid
@@ -3,7 +3,24 @@
{% capture alt %}{{ item.title | escape }} by {{ item.artist }}{% endcapture %}
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
- 
+ 
- 
+
+
{{ book.title }}
{% if book.rating %}{{ book.rating }}
{% endif %} diff --git a/src/pages/main/books/index.html b/src/pages/main/books/index.html index 08ab7dcb..e80816e5 100644 --- a/src/pages/main/books/index.html +++ b/src/pages/main/books/index.html @@ -18,7 +18,24 @@ schema: books {% capture alt %}{{ book.title }} by {{ book.authors }}{% endcapture %}
+
diff --git a/src/pages/main/music/artists/artist.html b/src/pages/main/music/artists/artist.html
index 2ea7fc3a..f6cc272b 100644
--- a/src/pages/main/music/artists/artist.html
+++ b/src/pages/main/music/artists/artist.html
@@ -19,7 +19,24 @@ schema: artist
{% tablericon "arrow-left" "Go back" %} Go back
- 
+ 
- 
+ 
- 
+ 
+
[^1]: There are some good options to do this, but there aren't a _ton_ and the age of some of the apps is concerning. [Marvis](https://appaddy.wixsite.com/marvis) is far and away your best choice here.
[^2]: Making sure that you update the values you obtained, including the path to your downloaded `.p8` file.
diff --git a/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md b/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
index d4e989aa..3784d355 100644
--- a/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
+++ b/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
@@ -9,7 +9,25 @@ I've been using Fastmail for years now and have explored a number of different a
For now, I've approached filtering my mail by applying regular expressions to reasonably broad categories of incoming mail[^2]. My thinking with this approach is that will scale better over the long term by applying heuristics to common phrases and patterns in incoming mail without the need to apply rules to senders on a per address or domain basis.
-
+
## Alias-specific rules
diff --git a/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md b/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
index 939f5a45..5dc409d6 100644
--- a/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
+++ b/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
@@ -66,6 +66,24 @@ Rendering the output is as simple as:
Leaving us with:
-
+
[^1]: At this point, a dev playground.
diff --git a/src/posts/2023/now-page-grouping-episodes-of-same-show.md b/src/posts/2023/now-page-grouping-episodes-of-same-show.md
index 44679f42..3713ca5a 100644
--- a/src/posts/2023/now-page-grouping-episodes-of-same-show.md
+++ b/src/posts/2023/now-page-grouping-episodes-of-same-show.md
@@ -12,7 +12,23 @@ I made a minor update to how I'm normalizing TV data for display on my now page.
By _minor_ I mean one of those things that may well break inexplicably depending on where the data lands. Instead of returning a normalized array based directly off the data returned by [Trakt](https://trakt.tv)'s API I'm instead collecting episodes in an array, checking as I iterate through the response to see if an episode of the same show exists and replacing that object with a mutated object designed to display the range of episodes watched for the show.
-
+
{% raw %}
diff --git a/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md b/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
index 613242d1..86358514 100644
--- a/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
+++ b/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
@@ -168,6 +168,24 @@ Finally, if the page this all lives on is loaded by a client without JavaScript
All of this, yields the single line at the bottom of this image — updated on each visit.
-
+
[^1]: Plus explicit conditions matching David Bowie and Minor Threat.
diff --git a/src/posts/2023/optimizing-for-performance-with-eleventy.md b/src/posts/2023/optimizing-for-performance-with-eleventy.md
index 0974ba4b..99c678f8 100644
--- a/src/posts/2023/optimizing-for-performance-with-eleventy.md
+++ b/src/posts/2023/optimizing-for-performance-with-eleventy.md
@@ -126,6 +126,24 @@ For this page in particular, the images that are rendered above the fold are set
All of these boilerplate steps leave us with a quick to load, accessible and resilient site:
-
+
[^1]: It's easy, flexible and helps mitigate my lack of an eye for design by providing safe baselines.
diff --git a/src/posts/2023/road-to-madness-apple-music-charts.md b/src/posts/2023/road-to-madness-apple-music-charts.md
index becb6a4c..b0b6e769 100644
--- a/src/posts/2023/road-to-madness-apple-music-charts.md
+++ b/src/posts/2023/road-to-madness-apple-music-charts.md
@@ -132,7 +132,25 @@ _Cool_[^4]. GitHub triggers a rebuild of the site every hour, Netlify builds it,
There are some significant issues with this approach: it doesn't capture listens to an album in a loop (like me playing the new Outer Heaven record today — hails 🤘). It can get wonky when my diff function hits a track order that elicits a false positive return value.
-
+
"But Cory there's last.fm." I hear this, I love last.fm, but I've got concerns about its age, ownership and maintenance. I don't want to be on the wrong end of a scream test when the wrong (right?) server rack gets decommissioned.
diff --git a/src/posts/2024/adventures-in-self-hosting-data.md b/src/posts/2024/adventures-in-self-hosting-data.md
index f82aba00..be08b71f 100644
--- a/src/posts/2024/adventures-in-self-hosting-data.md
+++ b/src/posts/2024/adventures-in-self-hosting-data.md
@@ -24,7 +24,25 @@ Trakt's backups are in JSON so I went to work coercing them into CSVs to upload
- For movies I wanted to track when I last watched them, title, year, my play count and whether I'd collected it or considered it a favorite.
- For TV shows I kept a similar data set and linked it to an episodes table via the `tmdb_id`. I used this ID to link out to [TMDB](http://themoviedb.org) and simplify my image URLs.
-
+
The watched data for [my now page](https://coryd.dev/now) is now sourced from these tables and I've built out [a dedicated watching page](https://coryd.dev/watching/). The hero image is randomly selected from my favorite movies at built time, as are the 6 TV shows and movies in their respective favorite sections.
diff --git a/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md b/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
index 3aac4de3..e449d90f 100644
--- a/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
+++ b/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
@@ -9,7 +9,23 @@ I've written before about [embedding music into my site](https://coryd.dev/posts
I could have kept depending on Last.fm and — don't get me wrong — I love Last.fm. It's one of those valuable, legacy services that's hanging on with a rich user base and historical recommendations. I'm going to keep scrobbling data there and to ListenBrainz[^1].
-
+
What I've long wanted is something that sits on infrastructure I control, stores my own data and lets me present roughly the same data. Given that Plex will issue outbound webhooks, I thought I'd set up an edge function over at Netlify and point a webhook at it to see what I could do with the inbound payload. What Plex sends is fairly lightweight and ended up needing to be read in from form data on the `POST`, but it was enough to work with.
diff --git a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
index 207d3ea9..12f32982 100644
--- a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
+++ b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
@@ -14,7 +14,23 @@ To simplify file uploads to B2, I mount the bucket for my site using [Mountain D
My music charting feature relies on JSON maps of artist and album metadata — if a new artist or album isn't present in either, it assumes that the image it needs is in the format of `artist-name.jpg` or `artist-name-album-name.jpg`. I store the canonical copies of these image files in a separate GitHub repo and have Hazel watch the `artist` and `album` directories contained therein. It renames the files to match the aforementioned format, strips characters that typically break URLs and copies them to my mounted B2 Bucket.
-
+
---
diff --git a/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md b/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
index 22687958..b83fcbb0 100644
--- a/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
+++ b/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
@@ -29,7 +29,25 @@ I had data for each, structured as JSON. I wrote some ugly node scripts (I'll sp
I imported those CSVs into their respective tables, and worked my way to connections between the tables that look like this:
-
+
The connections between the tables allow me to query data specific to a given listen's artist or album — data is stored in a given table where it makes the most sense: artist `mbid`s with artists, `genre`s with artists and so forth. I can then retrieve that data, provided I have a valid listen, using Supabase's select syntax: `artists (mbid, image)` or `albums (mbid, image)`.
diff --git a/src/posts/2024/on-getting-tattooed.md b/src/posts/2024/on-getting-tattooed.md
index 1324d4aa..7b52463d 100644
--- a/src/posts/2024/on-getting-tattooed.md
+++ b/src/posts/2024/on-getting-tattooed.md
@@ -28,7 +28,25 @@ Each piece was important to me when I got it and remains important to me now. Th
{% capture fallbackIcon %}{% tablericon "photo" "A photo of the Sturgill Simpson-inspired half sleeve referenced above." %}{% endcapture %}
-
+
[^1]: My wife got the same piece done — there was one pointing to the driveway of the house we got married at. It burned down in the Butte fire.
[^2]: She got elected!
diff --git a/src/posts/2024/this-is-my-favorite-band.md b/src/posts/2024/this-is-my-favorite-band.md
index 0bca3128..c53a98b2 100644
--- a/src/posts/2024/this-is-my-favorite-band.md
+++ b/src/posts/2024/this-is-my-favorite-band.md
@@ -7,7 +7,25 @@ tags:
---
I've called the same band my favorite for a long time and, the older I get, the less likely I feel that designation is to change.
-
+
This is my favorite band: [NoMeansNo](https://en.wikipedia.org/wiki/Nomeansno).
diff --git a/src/posts/2024/what-song-is-in-your-head.md b/src/posts/2024/what-song-is-in-your-head.md
index 72bc78d0..d3e4d62f 100644
--- a/src/posts/2024/what-song-is-in-your-head.md
+++ b/src/posts/2024/what-song-is-in-your-head.md
@@ -6,7 +6,25 @@ tags: ['music']
---
I saw this carved into a table in Austin once and it — like many songs — has been stuck in my head ever since. I'll get hooked on a song and circle back to that roughly carved message.
-
+
I've had songs and albums stuck in my head dating back to my childhood, primarily tracks from [*The Traveling Wilburys Vol. 1*](https://en.wikipedia.org/wiki/Traveling_Wilburys_Vol._1) — Tweeter and the Monkey Man, Handle With Care — they all take turns getting stuck in my head.
+
{{ artist.name_string }}
{%- if artist.favorite -%} diff --git a/src/pages/main/watching/movie.html b/src/pages/main/watching/movie.html index 752ec7ad..dbb11f43 100644 --- a/src/pages/main/watching/movie.html +++ b/src/pages/main/watching/movie.html @@ -12,7 +12,25 @@ schema: movie {%- endcapture -%} {% tablericon "arrow-left" "Go back" %} Go back
+
{{ movie.title }}
{% if movie.rating %}{% endif %} diff --git a/src/pages/main/watching/show.html b/src/pages/main/watching/show.html index 23e89e9e..13de7dc6 100644 --- a/src/pages/main/watching/show.html +++ b/src/pages/main/watching/show.html @@ -13,7 +13,25 @@ schema: show {% assign lastWatched = show | getLastWatched %} {% tablericon "arrow-left" "Go back" %} Go back
+
{{ show.title }}
{% if lastWatched %}{% endif %} diff --git a/src/posts/2023/displaying-listening-data-from-apple-music-using-musickit.md b/src/posts/2023/displaying-listening-data-from-apple-music-using-musickit.md index 10bd4f21..73565c27 100644 --- a/src/posts/2023/displaying-listening-data-from-apple-music-using-musickit.md +++ b/src/posts/2023/displaying-listening-data-from-apple-music-using-musickit.md @@ -203,7 +203,25 @@ The templating for my site is all written in [liquid.js](https://liquidjs.com) a We have an object containing arrays of objects — we iterate through each object for the appropriate section (tracks aren't displayed at the moment) and build the resulting display[^3]. This isn't perfect by any means, but, it does provide a nice little visualization of what I'm listening to and `240` tracks feels adequate as a rolling window into that activity. -
+
[^1]: There are some good options to do this, but there aren't a _ton_ and the age of some of the apps is concerning. [Marvis](https://appaddy.wixsite.com/marvis) is far and away your best choice here.
[^2]: Making sure that you update the values you obtained, including the path to your downloaded `.p8` file.
diff --git a/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md b/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
index d4e989aa..3784d355 100644
--- a/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
+++ b/src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md
@@ -9,7 +9,25 @@ I've been using Fastmail for years now and have explored a number of different a
For now, I've approached filtering my mail by applying regular expressions to reasonably broad categories of incoming mail[^2]. My thinking with this approach is that will scale better over the long term by applying heuristics to common phrases and patterns in incoming mail without the need to apply rules to senders on a per address or domain basis.
-
+
## Alias-specific rules
diff --git a/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md b/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
index 939f5a45..5dc409d6 100644
--- a/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
+++ b/src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md
@@ -66,6 +66,24 @@ Rendering the output is as simple as:
Leaving us with:
-
+
[^1]: At this point, a dev playground.
diff --git a/src/posts/2023/now-page-grouping-episodes-of-same-show.md b/src/posts/2023/now-page-grouping-episodes-of-same-show.md
index 44679f42..3713ca5a 100644
--- a/src/posts/2023/now-page-grouping-episodes-of-same-show.md
+++ b/src/posts/2023/now-page-grouping-episodes-of-same-show.md
@@ -12,7 +12,23 @@ I made a minor update to how I'm normalizing TV data for display on my now page.
By _minor_ I mean one of those things that may well break inexplicably depending on where the data lands. Instead of returning a normalized array based directly off the data returned by [Trakt](https://trakt.tv)'s API I'm instead collecting episodes in an array, checking as I iterate through the response to see if an episode of the same show exists and replacing that object with a mutated object designed to display the range of episodes watched for the show.
-
+
{% raw %}
diff --git a/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md b/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
index 613242d1..86358514 100644
--- a/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
+++ b/src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md
@@ -168,6 +168,24 @@ Finally, if the page this all lives on is loaded by a client without JavaScript
All of this, yields the single line at the bottom of this image — updated on each visit.
-
+
[^1]: Plus explicit conditions matching David Bowie and Minor Threat.
diff --git a/src/posts/2023/optimizing-for-performance-with-eleventy.md b/src/posts/2023/optimizing-for-performance-with-eleventy.md
index 0974ba4b..99c678f8 100644
--- a/src/posts/2023/optimizing-for-performance-with-eleventy.md
+++ b/src/posts/2023/optimizing-for-performance-with-eleventy.md
@@ -126,6 +126,24 @@ For this page in particular, the images that are rendered above the fold are set
All of these boilerplate steps leave us with a quick to load, accessible and resilient site:
-
+
[^1]: It's easy, flexible and helps mitigate my lack of an eye for design by providing safe baselines.
diff --git a/src/posts/2023/road-to-madness-apple-music-charts.md b/src/posts/2023/road-to-madness-apple-music-charts.md
index becb6a4c..b0b6e769 100644
--- a/src/posts/2023/road-to-madness-apple-music-charts.md
+++ b/src/posts/2023/road-to-madness-apple-music-charts.md
@@ -132,7 +132,25 @@ _Cool_[^4]. GitHub triggers a rebuild of the site every hour, Netlify builds it,
There are some significant issues with this approach: it doesn't capture listens to an album in a loop (like me playing the new Outer Heaven record today — hails 🤘). It can get wonky when my diff function hits a track order that elicits a false positive return value.
-
+
"But Cory there's last.fm." I hear this, I love last.fm, but I've got concerns about its age, ownership and maintenance. I don't want to be on the wrong end of a scream test when the wrong (right?) server rack gets decommissioned.
diff --git a/src/posts/2024/adventures-in-self-hosting-data.md b/src/posts/2024/adventures-in-self-hosting-data.md
index f82aba00..be08b71f 100644
--- a/src/posts/2024/adventures-in-self-hosting-data.md
+++ b/src/posts/2024/adventures-in-self-hosting-data.md
@@ -24,7 +24,25 @@ Trakt's backups are in JSON so I went to work coercing them into CSVs to upload
- For movies I wanted to track when I last watched them, title, year, my play count and whether I'd collected it or considered it a favorite.
- For TV shows I kept a similar data set and linked it to an episodes table via the `tmdb_id`. I used this ID to link out to [TMDB](http://themoviedb.org) and simplify my image URLs.
-
+
The watched data for [my now page](https://coryd.dev/now) is now sourced from these tables and I've built out [a dedicated watching page](https://coryd.dev/watching/). The hero image is randomly selected from my favorite movies at built time, as are the 6 TV shows and movies in their respective favorite sections.
diff --git a/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md b/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
index 3aac4de3..e449d90f 100644
--- a/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
+++ b/src/posts/2024/building-a-scrobbler-using-plex-webhooks-edge-functions-and-blob-storage.md
@@ -9,7 +9,23 @@ I've written before about [embedding music into my site](https://coryd.dev/posts
I could have kept depending on Last.fm and — don't get me wrong — I love Last.fm. It's one of those valuable, legacy services that's hanging on with a rich user base and historical recommendations. I'm going to keep scrobbling data there and to ListenBrainz[^1].
-
+
What I've long wanted is something that sits on infrastructure I control, stores my own data and lets me present roughly the same data. Given that Plex will issue outbound webhooks, I thought I'd set up an edge function over at Netlify and point a webhook at it to see what I could do with the inbound payload. What Plex sends is fairly lightweight and ended up needing to be read in from form data on the `POST`, but it was enough to work with.
diff --git a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
index 207d3ea9..12f32982 100644
--- a/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
+++ b/src/posts/2024/handling-images-with-b2-netlify-image-cdn-hazel-mountain-duck.md
@@ -14,7 +14,23 @@ To simplify file uploads to B2, I mount the bucket for my site using [Mountain D
My music charting feature relies on JSON maps of artist and album metadata — if a new artist or album isn't present in either, it assumes that the image it needs is in the format of `artist-name.jpg` or `artist-name-album-name.jpg`. I store the canonical copies of these image files in a separate GitHub repo and have Hazel watch the `artist` and `album` directories contained therein. It renames the files to match the aforementioned format, strips characters that typically break URLs and copies them to my mounted B2 Bucket.
-
+
---
diff --git a/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md b/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
index 22687958..b83fcbb0 100644
--- a/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
+++ b/src/posts/2024/improving-my-self-hosted-scrobbling-implementation.md
@@ -29,7 +29,25 @@ I had data for each, structured as JSON. I wrote some ugly node scripts (I'll sp
I imported those CSVs into their respective tables, and worked my way to connections between the tables that look like this:
-
+
The connections between the tables allow me to query data specific to a given listen's artist or album — data is stored in a given table where it makes the most sense: artist `mbid`s with artists, `genre`s with artists and so forth. I can then retrieve that data, provided I have a valid listen, using Supabase's select syntax: `artists (mbid, image)` or `albums (mbid, image)`.
diff --git a/src/posts/2024/on-getting-tattooed.md b/src/posts/2024/on-getting-tattooed.md
index 1324d4aa..7b52463d 100644
--- a/src/posts/2024/on-getting-tattooed.md
+++ b/src/posts/2024/on-getting-tattooed.md
@@ -28,7 +28,25 @@ Each piece was important to me when I got it and remains important to me now. Th
{% capture fallbackIcon %}{% tablericon "photo" "A photo of the Sturgill Simpson-inspired half sleeve referenced above." %}{% endcapture %}
-
+
[^1]: My wife got the same piece done — there was one pointing to the driveway of the house we got married at. It burned down in the Butte fire.
[^2]: She got elected!
diff --git a/src/posts/2024/this-is-my-favorite-band.md b/src/posts/2024/this-is-my-favorite-band.md
index 0bca3128..c53a98b2 100644
--- a/src/posts/2024/this-is-my-favorite-band.md
+++ b/src/posts/2024/this-is-my-favorite-band.md
@@ -7,7 +7,25 @@ tags:
---
I've called the same band my favorite for a long time and, the older I get, the less likely I feel that designation is to change.
-
+
This is my favorite band: [NoMeansNo](https://en.wikipedia.org/wiki/Nomeansno).
diff --git a/src/posts/2024/what-song-is-in-your-head.md b/src/posts/2024/what-song-is-in-your-head.md
index 72bc78d0..d3e4d62f 100644
--- a/src/posts/2024/what-song-is-in-your-head.md
+++ b/src/posts/2024/what-song-is-in-your-head.md
@@ -6,7 +6,25 @@ tags: ['music']
---
I saw this carved into a table in Austin once and it — like many songs — has been stuck in my head ever since. I'll get hooked on a song and circle back to that roughly carved message.
-
+
I've had songs and albums stuck in my head dating back to my childhood, primarily tracks from [*The Traveling Wilburys Vol. 1*](https://en.wikipedia.org/wiki/Traveling_Wilburys_Vol._1) — Tweeter and the Monkey Man, Handle With Care — they all take turns getting stuck in my head.