Commenter Thread

Comments on What to do? by Michael Cain

GftNC, most of the Olmsted links are dead, or will be come Sep 30. Some maintenance will be required.

So, adversarial AI training, out in the wild. What could possibly go wrong?

Spam filters are part of each hosting service's "secret sauce". Wherever we end up, I can pretty much guarantee that legitimate comments will still go into spam, but for a different set of unknown reasons.

GftNC, updating my archive takes minutes and can be done right up until Typepad shuts the servers down. No real reason to stop posting and/or commenting yet. Most convenient timing might be when lj decides he's ready to move the last several posts and comments to the new site; I can update my archive and provide him with a file with those posts/comments that WP will import.

Just a thought, that if the archive site is also WordPress, all WP sites require some amount of ongoing maintenance even if the content doesn't. That's just the way WP has set things up. At some point, one or more of the WP version, the PHP version, the theme version, or the widgets version will get out of whack and the site will just stop running.
Each of the long-running blogs I follow that run on WP eventually puts up a post saying, "We have to upgrade. Sh*t will be broken."
WP's current import function appears to be robust enough that loading the old content is just tedious, not difficult. And can be done after the new site is running.

Back in the day they would have worked with WordPress to migrate anyone that chose to move There was a certain sensitivity to just killing people's content.... I am curious, I will look later, to see if anyone is offering migration.
GoDaddy, where I rent my domain and cloud server, offers to migrate sites from other platforms to WordPress for a fee. GoDaddy will do pretty much anything for a fee :^)
Typepad.com hasn't signed up new customers for Moveable Type sites for five years now. Two years ago, they came close to shutting down the Moveable Type service. I seem to recall from then that they offered to migrate people to a WordPress service under the same corporate umbrella. Guess they're on the "well, we warned you" plan this time.
I tested the WordPress import function against a subset of my archive today, and it worked fine. I think we're down to where it's just going to be tedious now.

Since there are a number of readers interested...
Typepad's export function appears to be broken, at least for content as large as Obsidian Wings'. I have updated my software for scraping the site content the hard way -- Typepad added more stuff to discourage scraping. I've updated my site archive to this morning and put a copy up in the cloud where the editors can access it. There may be some hiccups, but this was (imo) the critical step to preserve the site's history.
I admit to a certain amount of curiosity about how many other long-running blogs there may be for whom the export function is broken, who don't have access to a stubborn old software guy?

...and am about to order a buckwheat husk pillow.
This is the brand I got most recently. There was a very faint dried plant material sort of odor for a few days. On the higher end price for a pillow, but I expect to use it for >10 years.

Priority item from my perspective... Verify the Typepad export function still works. Last time around, the Typepad update that fixed export broke my code that had scraped the site contents the hard way. If the export function is broken again, fix my code and scrape content newer than what I got previously. Once that's done, retrieve any images hosted by Typepad that are newer than my last checkpoint. Once there's a safe copy of the content, the rest is just details :^) I'll take on this task and let select people know when I have put a copy in a public place.

My initial opinion is that moving ObWi to a WordPress site is straightforward. That's not necessarily the same as either simple or easy. I'll write something more detailed in the morning for people to pick at.