Firehose

Every now and then someone says something to the effect of ‘We have this new modern CSS thing. We don’t need to set the z-index to 99999 anymore!’.

I wish to make myself clear. I set my z-indexes to 99999 as a matter of principle, not necessity. You can pry z-index: 99999 from my corpse.

I see people say frequently that they don’t need to support older browsers because ‘everything auto-updates now’. This is a flawed assumption.

There are many reasons why someone might not have up-to-date browsers:

• Their device is too old. This is especially a problem with Apple devices, where the version of Safari is largely tied to the version of the OS.
• They never use their device long enough to trigger an update. I’ve previously had elderly tech-support clients who only used their computer sporadically for emails and banking and therefore didn’t receive updates because they weren’t using their computer long enough for new versions to install.
• They’re using a browser in an embedded context or on a ‘smart’ device, where there is no newer version available.
• Enterprise policies or restrictions don’t yet permit them to update their browser.
• They’re using a browser fork which lags behind in releases.
• They’re on slow/metered connections and have disabled background downloads to save money or bandwidth.
• Assistive technologies they require either lag behind in updates or aren’t supported in newer versions entirely.
• They’ve purposely disabled auto-updates for reasons of security.
• Interventions or censorship prevent them from reaching update servers.
• Their device doesn’t have the necessary storage capacity to perform an update.
• A device in a shared space like a library or school which doesn’t have the budget or capability to keep devices up-to-date.
• They’re running a portable browser from a USB or the like, which must be manually updated.
• They rely on a proxy-based browser which is outdated on the server-side.

You don’t need to support every browser version in perpetuity, but you should take a moment to consider that there are plenty of legitimate reasons folks won’t have the latest and greatest.

If you can, embrace progressive enhancement and graceful degradation.

A good way to start the day is by checking for major npm pwnage.

I like to think of myself less like a human and more like a future case study.

Sometimes I feel useless, but then I recall the experience of trying to use npm’s search functionality and suddenly feel extraordinarily capable.

I’m proud to announce that after spending the better part of half an hour painstakingly tweaking and refining an animation, I’ve decided I don’t like it and that I’m deleting it.

All the tech CEOs went from ‘There is no AI bubble’ to ‘When the AI bubble pops’ real quick.

Non-technical folk will (probably) bungle your email on a custom domain.

Emails are centralised to a few major platforms such as Gmail, Outlook, and iCloud. When you have an address straying from these usuals, people oftentimes get confused, which leads to bouncing emails.

TLDs straying from the familiar .com, .net, and .org are a common cause of issues. Frequently, people add one of the TLDs they’re familiar with after the actual address. For example, an email on my domain vale.rocks might be example@vale.rocks, but some people try to send an email to example@vale.rocks.com.

Another common issue is people assuming all emails end in gmail.com, which leads to addresses such as example@vale.rocks@gmail.com or example@vale.rocks.gmail.com.

You must ensure you know your audience. This probably won’t be an issue with a more technical crowd and is less so when people needn’t manually enter an address and it is instead filled for them, but you should be wary when targeting a casual group.

Don’t lose leads and business because of your snazzy email address.

Sometimes weekends on Bluesky are really dead. Other times, they are extremely active.

I’m yet to discern any patterns or otherwise figure out the cause.

Not every day you get a physical e-mail from the United States.

These rad stickers landed in my letterbox courtesy of one Mat ‘Wilto’ Marquis.

Everyone says OKLCH like ‘Okay El Sea Haich’, yeah?

Popped over to SpaceHey to check out discussion of an early 2000s indie musical project, and I loaded a Windows 3.1 Hot Dog Stand-themed group where the first account I saw had a profile picture with the text ‘this man ate my son’ below a photo of David Dixon’s Ford Prefect.

The web isn’t all bad.

My vacuum cleaner broke, so I got a new Next.js branded one which I can be certain will continue to suck for years to come.

One of my photographs has apparently been used in this AOL article about protecting your garden from frost.

https://www.aol.com/articles/protect-garden-frost-too-tips-173139152.html

I’ve obviously peaked. Things can only go downhill from here.

The Attention Is All You Need Paper and Its Consequences

Something I observed while manually reviewing every single site on PersonalSit.es:

• Websites built with Next.js very rarely have RSS feeds.
• Websites built with React sometimes have RSS feeds.
• Completely static sites almost always have RSS feeds.

Some people are told that they’re a ‘sight for sore eyes’. I’m often told I’m a ‘sore sight for eyes’.

Most AI integrations are like having a backseat driver you didn’t invite into your car.

The chat platform Stoat already has a wordmark, but no logo. Here are some of the concept designs I put together:

Zohran Mamdani is a rare case of a politician not simply being the least bad but instead being genuinely good. I am so glad to see him triumph.

Oh, making an accessible website is too complex for you to bother? Sounds like you aren’t very good at your job then, eh?

I have no allegiance to your platform. I do not build my castle on foundations of sand owned by you. I own my content, and it resides safely in perpetuity within my personal website.

‘You’ve read your last free article’ reads like ‘You’ve taken your last breath’.

I painted this skateboard ~6 years ago and I fear this indicates I’ve long since run out of new ideas.