Mastodon

Friends of Slack, a couple desktop-client things:

1. Huddles should prevent the screen saver — I am talking on the computer.
2. Defaulting to “Automatically leave huddles” when the screen saver starts (when paired with above) is a very bad software default

(please fix one of the above, thx)

I’ve been to far too many family funerals in the past couple of years.

When my time is up (far, far from now) I hope that whoever speaks offers the listeners a message of acceptance and peace — not one of fire and brimstone, not one of conditional love through unconditional allegiance.

Take care of each other, y’all ❤️

A few Eleventy build server image optimization tests for the project I’m currently working on (×1088 images):

formats: webp, auto =>
❄️ cold cache: 4m 33s
🔥 warm cache: 36s

formats: avif, webp, auto =>
❄️ cold cache: 11m 32s
🔥 warm cache: 38s

Do y’all think the AVIF build cost is worth it if the build server cache is ~always warm?

my partner got me a 3D printer for christmas and it’s the first “magic technology feeling” I’ve had in a very long time—a glimpse at what a star trek replicator might feel like.

any good recommendations for useful or fun prints?

Eleventy End of Week Update:

⛴️ Pre-release v3.0.1-alpha.1 https://github.com/11ty/eleventy/releases/tag/v3.0.1-alpha.1 (Import Attributes, Relative assets)
🦴 Big efficiency wins in Fetch v5.0.2 (beta) https://github.com/11ty/eleventy-fetch/releases/tag/v5.0.2-beta.1
🏞️ In progress: Image v6 https://github.com/11ty/eleventy-img/milestone/22?closed=1 (hook directly into sharp for adv processing)

to everyone suggesting that I change the code to do some kind of harm to their web site (humorous or not)—no, I will not be doing that.

I think we can all agree that it would be wrong to cause production harm to another organization or company’s web site—right?

1. use this web component, it has zero dependencies, weighs 4KB, shipped in 2018—still works great

2. OR, you can use this react component—it has many dependencies, requires a transpiler, weighs 200KB+, uses outdated react best practices from 3 months ago

you gotta choose #2, right? otherwise they’re gonna make fun of you

For years there has been a stinky cloud of web performance misinformation and propaganda coming from folks in the React community.

So much so that apparently a 57 score on Lighthouse is “fast” (even with 1160ms of TBT and a 5.4s LCP).

(There is *some* nuance here, of course—but we haven’t graduated to those discussions yet!)

If you too want to pretend that your slow web site is fast, use this handy guide: https://www.zachleat.com/web/lighthouse-deception/

Having a sizeable following on social media hardens you—in the same way that any small measure of power might.

At our worst we think of this as a suit of armor, a sort of mental toughness.

At our best we mourn this as a loss of compassion, a subtraction of our humanity and connectedness.