Some of you may have noticed that Windypundit was unavailable for parts of Saturday.
It turns out that my hosting provider migrated Windypundit to a new server sometime in the last week or so. Normally, they’d also change the entries in the nameserver, which is the server that provides the link between the “windypundit.com” domain name and the IP address of the server that hosts my content. However, for reasons too boring to go into, I use a third-party company for nameservice, so my hosting provider has no way to make the change.
They are aware of this issue, and sometime last week they sent me an email explaining exactly what changes I had to make…which I kept meaning to do.
Anyway, for much of the past week, when you or I pointed our browsers at windypundit.com, we were using the old server, not the new one. That lasted until sometime on Saturday, when they finally shutdown the old server, and Windypundit went off the air.
I’ve changed the nameserver entries to point to the new server, and that’s where you’re reading this. There was still a problem, however. You see, the copy of Windypundit on the new server was made several days ago, so it didn’t have anything recent, including my post about the Tweet-up meeting at the Fairmont hotel, the comments to that post, and drafts of several other posts I had started.
By poking around in the Google and Bing page caches, I managed to put the tweet-up meeting post back together, along with everyone’s comments (although the dates are off). But since they were never published where Google can find them, I can’t think of any way to get back the drafts of my new blog posts.
Update: I probably also lost emails from the past week too, so if you were trying to send me something, please send it again.