Yeah, killin' .my nerd addiction. l'm always cycling thru ALZ, AccessForever, and DevHut.

Then general surfing.

Yeah, and then I clicked on a link to DevHut.net (Daniel Pinneault's site) and got:

Insufficient Storage - The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. There is insufficient free space left in your storage allocation. Additionally, a 507 Insufficient Storage error was encountered while trying to use an ErrorDocument to handle the request.

Sounds like someone needs to up his disk quota. Oops. :)

What's going on in the Access world right now! Hope I'm not next. [Knock on wood]

Daniel's back up now. Must have just been a short glitch.

Donald wait... do people still use the term "surf" the web? I thought that went the way of "Information Superhighway" back in like 2003. LOL

Back when www stood for World Wide Wait?

Update on Mike's site:

Status Update (2026-05-19)
The site has been down longer than I initially expected. Here's a brief update on where things stand.

I have been self-hosting this blog on an open-source publishing platform since I first started it in 2020. My latest understanding of the attack strongly suggests it was due to a platform vulnerability. What's more, the vulnerability was reported to the team that supports the platform. They fixed the vulnerability, rolled it out on their official hosting site, and then published the patch to their open source project.

In the age of AI-assisted development, the time from patched vulnerability in an open-source project to weaponized exploit is rapidly moving from months/weeks to days/hours. In that reality, even patching the day a release ships (already an ambitious goal) may not be fast enough anymore. The window between "publicly known" and "publicly exploited" is shrinking every day.

With that emerging reality in mind, I've decided to migrate the site to the platform vendor's fully-managed hosting service. Managed customers receive patches for responsibly-reported vulnerabilities before those vulnerabilities are even publicly acknowledged. That's a feature that self-hosting simply can't match.

Unfortunately, I don't have a firm restoration date yet. Migrating to the vendor platform likely extends that timeline. I'll post another update when I have a better idea of when the site will be back online.

Thanks for your patience.

Good to see he's been able to get back up and running.