swrobel

Reply I received from GMO Registry to the email I sent them yesterday:

On September 24, 2026, between UTC 16:11 and 21:54, some .shop domain names intermittently could not be resolved. This was caused by an issue in our system resources in our zone generation system, which resulted in some domain names being temporarily missing from the .shop zone. The issue has been resolved, and DNS resolution has been stable since UTC 21:54.

Depending on DNS caching, some users may have continued to see errors for up to one hour after the issue was resolved. Registration data, including nameserver settings, was not changed or lost, and domain name holders do not need to take any action.

The cause has been identified and corrected, and we are implementing additional measures to prevent a recurrence.

We sincerely apologize for the inconvenience caused.

...and down again!

Seems like they're coming back up... Still not sure what caused this, or where it's monitored.

6-3 with Thomas, Alito & Gorsuch dissenting

Did we decide ZFS is good after all this time?

Wantrapreneurs

Why would it keep the notification history after they’ve been dismissed, though? There’s no user-facing way (that I’m aware of) to access a history of dismissed notifications.

For some reason I thought 1.1.1.1/1.0.0.1 already wouldn’t resolve archive.[today|is|ph] anyway

Sir, this is an Arby’s

Dokku = steep learning curve according to your comparison chart? As a longtime Heroku user, I’d have to disagree.

Yeah, P30D as presumably intuitive to non-technical users has me chuckling

Also, knowing that TODAY > signup + P30D transpiles to TODAY > signup + 30.days in Ruby. Which one is more readable?

Always wonder why companies see suing people as a better course of action than hiring them.

That’s the bummer for me. The primary place I’d like to use this is surfing. Too much time to think, and too few practical ways to record those thoughts.