- {% image './src/assets/img/404.jpg', title, 'image__banner', 'eager' %}
+ {% image 'https://coryd.dev/.netlify/images/?url=/assets/img/404.jpg&w=1000', title, 'image__banner', 'eager' %}
What kind of idiots do you have working here?
Hurry up and skip out on the room service bill!
diff --git a/src/pages/about.md b/src/pages/about.md
index b8d85858..572dfd7a 100644
--- a/src/pages/about.md
+++ b/src/pages/about.md
@@ -13,7 +13,7 @@ permalink: /about.html
{%- capture about_alt -%}{{ meta.siteName }} - image by David Neal / @reverentgeek{%- endcapture -%}
- {% image './src/assets/img/avatar.png', about_alt, '', 'eager' %}
+ {% image 'https://coryd.dev/.netlify/images/?url=/assets/img/avatar.png&w=600', about_alt, '', 'eager' %}
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 0af07abd..469adf80 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,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=1200', 'Albums and artists', 'image__banner', 'lazy' %}
+{% 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' %}
[^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 c85654c2..78f36e9a 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,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=1200', 'A diagram of my Fastmail workflow', 'image__banner', 'eager' %}
+{% 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' %}
## 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 b5638983..50b2d42a 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
@@ -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=1200', 'Albums I\'m looking forward to', 'image__banner', 'eager' %}
+{% 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' %}
[^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 582f10cf..a15d4a61 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,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=1200', 'Grouped TV episodes', 'image__banner' %}
+{% 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' %}
{% 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 b89f89eb..4dfa8608 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,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=1200', 'Now playing', 'image__banner', 'lazy' %}
+{% 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' %}
[^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 a725a748..8cc00b17 100644
--- a/src/posts/2023/optimizing-for-performance-with-eleventy.md
+++ b/src/posts/2023/optimizing-for-performance-with-eleventy.md
@@ -137,6 +137,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=1200', 'Pagespeed scores for coryd.dev/now', 'image__banner' %}
+{% 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' %}
[^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 90c69765..92b18098 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,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=1200', 'Charlie Day standing in front of charts', 'image__banner', 'lazy' %}
+{% 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' %}
"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/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 37fabadd..9ac2e690 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,7 @@ 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].
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/scrobbler.png&w=1200', 'A diagram of the scrobbling architecture', 'image__banner', 'eager' %}
+{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/scrobbler.png&w=1000', 'A diagram of the scrobbling architecture', 'image__banner', 'eager' %}
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/on-getting-tattooed.md b/src/posts/2024/on-getting-tattooed.md
index 471488b3..f789b77b 100644
--- a/src/posts/2024/on-getting-tattooed.md
+++ b/src/posts/2024/on-getting-tattooed.md
@@ -27,7 +27,7 @@ My parents started getting tattooed in their 50s, thinking it would be a cheaper
Each piece was important to me when I got it and remains important to me now. They're references to and reminders of important moments and I enjoy every session[^6]. But, for now, my shoulder is sore.
{% capture fallbackIcon %}{% tablericon "photo" "A photo of the Sturgill Simpson-inspired half sleeve referenced above." %}{% endcapture %}
-{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/half-sleeve.jpg&w=1200', 'A photo of the Sturgill Simpson-inspired half sleeve referenced above.', 'image__banner', 'eager' %}
+{% image 'https://coryd.dev/.netlify/images/?url=https://f001.backblazeb2.com/file/coryd-dev-images/blog/half-sleeve.jpg&w=1000', 'A photo of the Sturgill Simpson-inspired half sleeve referenced above.', 'image__banner', 'eager' %}
[^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!