blogging

Moving baty.blog to Micro.blog

A few times every year I get the bug to move my blogging to WordPress. I mean, WordPress has it all, and more, right? For a week or two, having it all feels good. But then, the “…and more…” part starts to rub me the wrong way, and the cracks start to show. Gutenberg shmutenberg! And plugins nagging me to “Upgrade to Premium!”. Jetpack. Ridiculous extra markup and CSS. It’s all too much.

Yesterday, I logged into the WordPress control panel and was greeted with the “Welcome to WordPress 6.9!” screen. Fine with me, but there was nothing new that I needed, and I carried on.

This morning, I was prompted to upgrade WordPress to 6.9. Say what? Sure enough, the blog was running 6.8.3 again. I have no idea why, and that bothered me enough that I started thinking about where I might move it.

Also yesterday, I re-started my Micro.blog subscription as a lighter-weight way to “micro blog”. It occurred to me that I was really only microblogging with WordPress anyway, so what about using Micro.blog for baty.blog instead of on a separate domain (micro.baty.blog).

So that’s what I’m doing. At some point today, I’ll change the domain here to baty.blog and put in a few redirects. Once again, I apologize for the churn.

I’m thinking of migrating off Mastodon instances and using Ghost or Micro.blog as my Fediverse identity. Ghost isn’t ready, so I’ll need to wait to see. I hesitate to admit that I’m hung up on domain choice. I assumed micro.baty.net but too long? Maybe just use “@jack@baty.blog”?

I’m typing this in MarsEdit for posting to Micro.blog and makes me feel nostalgic.

I’ve been feeling the urge to have a separate microblog again, so I’ve dusted off the ol' Micro.blog account. Let’s see what happens.