chore: update meta

src/posts/2023/displaying-listening-data-from-apple-music-using-musickit.md

@@ -203,7 +203,7 @@ 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.
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/albums-artists.jpg&w=1000', 'Albums and artists', 'image-banner', 'lazy' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/albums-artists.jpg&w=1000', 'Albums and artists', 'image-banner', 'lazy' %}
 
 [^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.

src/posts/2023/fastmail-handling-inbound-email-with-regex-filters-now-with-chatgpt.md

@@ -9,7 +9,7 @@ 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.
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/fastmail-workflow.jpg&w=1000', 'A diagram of my Fastmail workflow', 'image-banner', 'eager' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/fastmail-workflow.jpg&w=1000', 'A diagram of my Fastmail workflow', 'image-banner', 'eager' %}
 
 ## Alias-specific rules
 

src/posts/2023/from-ics-to-json-surfacing-anticipated-albums.md

@@ -64,6 +64,6 @@ Rendering the output is as simple as:
 
 {% endraw %}
 Leaving us with:
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/album-releases.jpg&w=1000', 'Albums I\'m looking forward to', 'image-banner', 'eager' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/album-releases.jpg&w=1000', 'Albums I\'m looking forward to', 'image-banner', 'eager' %}
 
 [^1]: At this point, a dev playground.

src/posts/2023/now-page-grouping-episodes-of-same-show.md

@@ -12,7 +12,7 @@ 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.
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/grouped-tv.jpg&w=1000', 'Grouped TV episodes', 'image-banner' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/grouped-tv.jpg&w=1000', 'Grouped TV episodes', 'image-banner' %}
 
 {% raw %}
 

src/posts/2023/now-playing-eleventy-netlify-edge-functions-emoji.md

@@ -168,6 +168,6 @@ 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.
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/now-playing.jpg&w=1000', 'Now playing', 'image-banner', 'lazy' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/now-playing.jpg&w=1000', 'Now playing', 'image-banner', 'lazy' %}
 
 [^1]: Plus explicit conditions matching David Bowie and Minor Threat.

src/posts/2023/optimizing-for-performance-with-eleventy.md

@@ -126,6 +126,6 @@ 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:
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/page-speed.jpg&w=1000', 'Pagespeed scores for coryd.dev/now', 'image-banner' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/page-speed.jpg&w=1000', 'Pagespeed scores for coryd.dev/now', 'image-banner' %}
 
 [^1]: It's easy, flexible and helps mitigate my lack of an eye for design by providing safe baselines.

src/posts/2023/road-to-madness-apple-music-charts.md

@@ -132,7 +132,7 @@ _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.
 
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/charlie.jpg&w=1000', 'Charlie Day standing in front of charts', 'image-banner', 'lazy' %}
+{% image 'https://coryd.dev/.netlify/images/?url=/media/blog/charlie.jpg&w=1000', 'Charlie Day standing in front of charts', 'image-banner', 'lazy' %}
 
 "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.