Category: Tech

Posted on
by

Way back in the year 2000, I bought a domain name to move my personal website from the school web server to someplace I could keep it visible after graduating. I picked Hyperborea.org from an adventure movie I’d seen years earlier, wanting something that sounded fantastic but wasn’t Atlantis, which had already been done to death (and besides, it was taken). In 2002, I set up the first version of this blog, running on b2/cafelog. At the time, Katie and I both posted here. She later moved to LiveJournal, then stopped blogging, then set up again at Feral Tomatoes.

Somewhere along the line I bought KVibber.com and set it up to redirect to my main site. Then in 2022 I rebuilt it as a simple Indieweb-style profile, figuring that while Hyperborea was a digital home, it really wasn’t a digital identity. I’ve been using that in various online profiles ever since, but kept most of the actual stuff on the existing site while I dithered over what to keep where.

Eventually I decided I wanted to move over to the newer domain.

The Eleventy parts were easy: I just needed to change some parameters and rebuild. The hand-crafted parts were relatively easy: global search and replace.

And of course redirecting each section to the new site as I moved it.

Search indexes are slowly shifting over. Google so far has decided to keep pointing to some of the older pages even though those pages redirect to the new ones.

The blog…is complicated. WordPress and ClassicPress use a database for some things and files for others. Plus I’m using the ActivityPub Plugin to make the blog visible on the Fediverse, which brings its own set of complications. I was relieved to see that copies of posts previously federated at the old site do in fact show up correctly on the new site’s Fediverse view.

One thing I decided on early on: I was going to use a subdomain this time instead of a folder, because too many things (some plugins, .well-known files, etc) assume your blog is running at the top level of the site.

I did a first pass Wednesday night to copy the files and database, set up the new config, run all those search-and-replace actions, and kick the metaphorical tires. Since then I’ve been spot-checking things here and there, and the new site seems fine so far.

I tried running the ActivityPub migration, but it doesn’t seem to have sent any followers over. And when I look at the old @kelson profile in Mastodon, it says it’s moving to…@kelson, instead of to @k2r. Most likely it’s either an incompatibility with ClassicPress or another problem with running in a subfolder. I’ll give it another stab tomorrow, but there are only about 5 followers at the moment, and I can just DM everyone if I really need to.

Then I can self-destruct the ActivityPub view on the old site, and once that’s done, I can redirect the blog to the new location.

Better Late Than Never

I’m kicking myself for taking so long. I should’ve just moved wholesale over to KVibber.com back in 2022. By waiting until 2026, I’ve left the new location without proof of having existed before the slop era. (I’m still writing articles myself, not using an “AI,” so all the mistakes in this post are my own.) Unless someone looks up the old hyperborea.org version of a page on the Wayback Machine, but they shouldn’t have to know to do that.

But the old name is awkward and hard to spell, and apparently some of the creepy groups that have weird obsessions with the myths it came from are more substantial than the historical footnotes I thought they were back in the day.

Posted on
by

I’ve been using the excellent ActivityPub Plugin for WordPress to connect this blog to the Fediverse for several years now, and it keeps getting better. The plugin makes any WordPress blog also work like a Mastodon server, so you can follow and interact from any site running Mastodon, Akkoma, Pixelfed (image posts only, of course), Snac or my favorite, GoToSocial.

Last year some features started breaking on here as WordPress and ClassicPress diverged, and I put some stop-gap fixes in place. I never quite got around to debugging it in my spare time, though. So I was very happy to see that starting with the 7.8.3 release a couple of weeks back, ActivityPub for WordPress now explicitly checks for ClassicPress to fall back to a compatibility mode!

You still need to trick it into thinking it’s on WordPress 6.5 or later (ClassicPress 2 split off from WordPress 6.2), but the latest version fixes all the problems I’d been working around on this site, including broken comment forms and missing images on the Fediverse view of a post.

Update: I missed a scenario with filtering comment authors in comment_reply_link. I’ve manually worked around it for the moment, and when I have a chance I’ll either do a proper bug report or suggest a proper fix.

So I’d like to give a shout-out to Matthias Pfefferle and the ActivityPub Plugin team and say: thanks for fixing it!

And if anyone reading this wants to connect their WordPress or ClassicPress site directly to the Fediverse (rather than just cross-posting or auto-posting links), this plugin is still the best way to do it.

On a related note…

I finally got around to fixing Share Classicly so it won’t add its link to the Fediverse view of a post. (Aside from cutting the clutter, boosting would make more sense anyway.) That’s the plugin I made that adds a ShareOpenly link to each post, so your readers can share to a Micropub, Mastodon, Bluesky, etc. account.

Posted on
by

In retrospect, it’s wild that so many tech people who were hyper-aware of the fact that Microsoft’s dominance in the 1990s and 2000s was due to more to marketing (“never underestimate Microsoft on marketing”) than technical merits…fell for the idea that a “marketplace of ideas” would coalesce around the best ideas, and not just the loudest ones.

Posted on
by

I can go with your scifi/fantasy story’s super-impossible thing being associated with an eclipse. It’s activating or deactivating people’s super-powers? Sure! Certain magic spells can only be cast during an eclipse? Sure! The moon transforms into cheese? OK, whatever. (pun not intended)

But please, please get the basic mechanics right! Continue reading →

Posted on
by

I really wish GNOME’s “Oh No! Something went wrong!” screen would let me restart just the crashed components instead of forcing me to log out completely. Or let me decide if I’m willing to continue without whatever crashed. If the audio broke, and I’m not doing anything that needs sound right now, it shouldn’t block me! — just like if the extension I’m

Heck, I’d even settle for just being able to interact with the applications that are still running. I can see them on the overview, and the thumbnails still update! Fortunately I haven’t had it happen while I was editing something, but I’d sure like to be able to click on “save” if I need to!

When I first started using Linux, it was a lot less stable than it is today, but when something broke, I always felt like I could fix it. Even if a window manager crashed, I could relaunch it and pick up where I left off.

I keep coming back to GNOME, but it has an infurating tendency to weld the hood shut on things that “just work” most of the time, because you should never need to fix that issue! (See also: Geary not offering manual sync, GNOME Software wanting to reboot the system when you update Firefox, etc.)

Posted on
by

Automattic has announced that they are “realigning” their contributions to WordPress due to fending off “attacks” from the “community” and WP-Engine.

Automatticians who contributed to core will instead focus on for-profit projects within Automattic, such as WordPress.com, Pressable, WPVIP, Jetpack, and WooCommerce. Members of the “community” have said that working on these sorts of things should count as a contribution to WordPress.

In the interest of, as you put it, “secur[ing] the future of WordPress for generations to come,” I trust you’ll be releasing the WordPress trademark, core project management and the infrastructure at WordPress.org, (the latter of which which CEO Matt Mullenweg has repeatedly pointed out that he owns personally) over to the community so you can “focus on for-profit projects within Automattic” without the distraction of the wider WordPress ecosystem.

Either that, or you’ve just told the entire WordPress community — excuse me, “community,” I forgot to include the scare quotes you so meticulously included throughout your article — that we should never trust you to have the community’s interests at heart, only your own.

I suppose this means I should start looking for alternatives to the handful of Automattic-built plugins I’m still using, as it sounds like I shouldn’t anticipate them continuing to be maintained.

Update January 10: It gets worse. Mullenweg just deactivated the accounts of several high-profile people at WordPress-adjacent companies who dared to question his leadership, in a post that goes increasingly off the rails.

Posted on
by

Back in 2002, I set up this blog on b2. A year later, b2 updates had stagnated, I migrated it to a fork of b2 called WordPress.

In the intervening 21 years, WordPress has gone on to power a huge fraction of the web. But in my opinion the project has lost its way, starting with the move to the Gutenberg block editor in 2018 and trying to become everything to everyone instead of just really good blogging software.

In response to the Block Editor merge, another project forked WordPress to create ClassicPress. Initially it was more or less WordPress Minus Gutenberg, but they’ve continued to do their own development as well, from cleaning up old complex code to improving the way media management works. I sorta kept up with it for a while, but finally decided to really evaluate it this month, and it’s actually really good! So I migrated a couple of test blogs, then Katie’s Feral Tomatoes.

Then I started looking at what it would take to migrate this 22-year-old, 3,255-post behemoth of a blog. (And that’s after moving a bunch of posts to other parts of my site, and deleting a bunch of no-longer-useful posts like ‘Migrated from 1.1 to 1.2. Let me know what’s broken.” or “Check out this weird link!” with no commentary (especially when the weird link is long-dead by now anyway).

Continue reading →

»All pages site-wide with this tag