An update on folo’s move “home”

Y’all, I had some most-excellent news from riddenword last night: he and his tech have been able to transfer what we’ve put here since Friday, apparently intact, back to “main” folo in one swell foop!

Woohoo for that — you have no idea how I was dreading having to do it manually, post-by-post and comment-by-comment. They’ve arranged for me to get back in now too, so I’ll be spending some time over there this morning, confirming that it’s really as intact as our first peeks-in late last night suggested. (Intact, that is, up to the moment they did the test transfer.)

Last evening, the two of them also sent word to the rest of the World Wide Web that it can find us at folo.us again — but it’ll take about 24 hours for that information to “propagate” to servers everywhere. So while it does, we’ll just sit tight here, avoiding misdirected landings at the wrong address. (Some of you IT-savvy folks like Bud Fox and Hatfield and jester will understand this process much better than I do, no doubt.) 

Anyhow, at some point this evening, we’ll close the threads to new comments and let our tech department perform the final transfer (which shouldn’t take long at all), and then riddenword or I will give the word to “Come On Home to Your Dearly-Beloved Edit Button.”

RAH!

lotus

2 Responses to “An update on folo’s move “home””

  1. Cujo359 Says:

    My link to Folo still points to the new node name, but I still end up here. I’m sure when things are ready we will no longer be redirected here.

  2. lotus Says:

    Hiya, Cujo. Yeah, our internal redirect from there to here is still on, but we can’t do one from here to there because WordPress doesn’t allow that.

    riddenword explains to me that, what with hosting nearly 3 million blogs around the world, they don’t dare allow that kind of thing, because if they did, pretty soon they’d have a globe-sized bowl o’ cyber-spaghetti.