I’ve been looking for a job in San Francisco very hard for the last couple months since I got up here. I’ve had nibbles, I’ve had bites.

And then, I had the events of the last week.

A few weeks ago, I’d applied for what sounded like a really ideal job at The Nerdery, a great, developer-driven, Minnesota-based company that’s aggressively expanding its Chicago office. Their website did an excellent job of making it sound like an absolutely ideal place to work. I had a first interview that I thought went very well, and I turned in a code sample I was pretty happy with.

I hadn’t heard from them before I left for Chicago, so I was a little disappointed, because the idea of moving back to Chicago to take such a great job had just seemed so perfect. I hadn’t realized how badly I wanted to move back until I was presented with the realistic possibility of doing so.

And then, after I dropped a check-in email to HR on Sunday, the chaos began.

I had my second interview with the Nerdery Monday morning, and loved it. They told me everything I wanted to hear, including that this page of raves from their employees was, in the experience of my interviewers, true. I left very, very excited about that prospect.

Apparently, that excitement set off some sort of alarm that only HR people can hear, because by the time Tuesday afternoon rolled around, I had booked three interviews with SF companies, had two, gotten a second rounder with one of those two and pulled a code sample out of my ass for that one, too.

Between the interviews, conversations with friends and family, and assorted negotiations I’ve done over the last few days (and maybe some yelling at the terrible Northwestern secondary Saturday night), my voice is completely shot. I slept about 10 hours out of 72.

Then the Nerdery’s offer hit my inbox.

I am very happy to announce that this morning I accepted a position as an Interactive Developer with the Nerdery’s Chicago office. I’ll be starting the week after Thanksgiving (when I’ll have to do a week of orientation at HQ in Minnesota).

I’ll be sad to leave San Francisco – This town has been exceptionally good to me in my short time here, and I’ve very much enjoyed my time in the city. I’m so glad I moved up here, even if it was for a short time, because it accelerated my learning in a way that I don’t believe would have been possible if I’d stayed in LA.

Moving up here absolutely put me in the mind frame and gave me the impetus to bring up my skill set far and fast enough that I was able to get this job, and for that, I can never thank San Francisco enough.

But Chicago is home. I may have grown up in DC, but I have never felt as home anywhere as I have in Chicago. The fact that I am jumping for joy to move there in the goddamn dead of winter after 8 years in California probably says something about how much I missed the place.

[By the way, Chicago folk: I will preemptively warn you that I will be whining about the cold this year. Next year, I'll have my tolerance for the cold back and I'll shut the fuck up, but please, spot me a winter.]

The logistics of all this are kind of nuts. The current plan is to leave SF on November 12, with my car towing a trailer full of my crap minus about 90% of my furniture, and my dad (who VERY generously offered to help with the driving so long as I didn’t make him miss his 75th birthday party, a concession I thought was entirely fair) and Chaplin keeping me company in the car.

We’re shooting to arrive in Chicago on November 16th, though that will change if the weather gets bad along the drive. Trying to find an apartment is already in motion — god, rent in Chicago is so delightfully cheap — and hopefully I’ll have that squared away before I show up.

I am exhausted. I am emotionally wrung out after the rollercoaster I’ve been on for the last week or so. I have so much insanity ahead of me.

But I am so, so happy about this job and this move.

I can’t just post a video for Via Chicago, because that would be way too easy. So instead, a fond audio farewell to California with an enjoyably random video.

Between Chaplin being doped up on painkillers for a kidney issue and me being massively sleep-deprived, I’m not sure which one of us is going to become convinced he can talk first.

Click to enlarge. Or really, don’t. Even shrinky-dinked, you get a nice little taste of the clusterfuckyness.

A lot of folks I know who started their blogs out on Blogger have used HaloScan for commenting since before Blogger implemented comments. Since HaloScan is shutting down in the next few days, you’d think you might want to move all your old comments to Blogger.

Good luck.

There’s really no practical reason why someone at Blogger can’t write some sort of comments parser to handle the XML files that HaloScan spits out, but so far, they haven’t. If you want to get it done right now, the only way I found to make it work is a ridiculously cumbersome process.

Basically, that process is to import everything into a WordPress blog where it can all be properly combined, then re-export it, run it through python script, and upload it back into Blogger.

I’ve decided to write up the entire procedure I went through both as an exercise in writing documentation and in order to help anyone else who’s crazy enough to want to try this. If you think you have the patience for this (or would just like to see exactly how insane I am), hit the “read the rest” link that follows.

I will warn you that there’s a pretty decent degree of difficulty on this: There is at least some command line usage involved. There is setting up of a local host on your computer (albeit a dead-easy to use one). There is a LOT of trial and error in this process, and you have to be comfortable with recognizing when things just didn’t work and you need to start over, or at least take several steps back.

This is also very time consuming. The main reason I had time to futz with all this is that I am currently unemployed.

Also, be sure to read this all the way through these instructions and check out the known issues before you get started. There might be a dealbreaker in there, and I’d really hate for anyway to get halfway through this ridiculous process and realize that they wasted half a day for something they can’t use.

I’d like to say up front that this would absolutely not be possible without the work of Justin Watt (you’ll see why in steps 4/6), and if this works, you should totally donate to his beer fund.

If you can accept all those caveats, here are the instructions I’ve put together based on how I got this to (finally) work. I’ve tried to make it as clear as possible, but some of this stuff gets pretty complicated.

.

Step 1: Install XAMPP on your computer.

XAMPP is a free local server with PHP and MySQL tools built right into it, and which works on Windows, OS X, and Linux (and Solaris if you REALLY want to get out there).

You can also run it as a webserver, but for the purposes of this set of instructions, I’m actually keeping it off-line so that the blog I’m doing this on for a friend of mine remains unpublished (since he only allows selected readers on Blogger).

.

Step 2: Install WordPress on your XAMPP Local Host.

Great set of instructions here for Windows XP. The main difference for setting it up for OS X is actually in the installation of XAMPP, which the XAMPP website covers pretty simply. Note that when you’re in Applications > XAMPP folder, you’ll see a shortcut to the “htdocs” folder that you’ll want to dump all the WordPress stuff into.

One thing I did notice when I did a Get Info on it is that the “htdocs” folder is marked read-only for “everyone”, and you’ll want to make sure it’s marked read/write so that your XAMPP server can access it.* On the Mac, hit command-I to Get Info on the folder, then at the bottom of the window that opens up you’ll see dropdown menus that will allow you to change the permissions easily.

*- Again, I’m assuming you will NOT be putting the WordPress workaround on the Web, because there are huge security issues with marking a file as read/write for everyone on a live server, and I would STRONGLY recommend against doing this if you’re working with a live server.

.

On the sidebar of WordPress’s admin page, there’s a Tools > Import feature, and one of the types of blogs you can choose is Blogger. You’ll have to sign in with your Google Account to authorize the import, but once you’ve done that, the rest of the process is automated.

I encountered two minor issues with the importer. The first was that there were about 15 or so posts that didn’t come over, which had to be manually re-added. Out of 2300, I was pretty much okay with that, but going through and figuring out which posts were missed was kind of a pain in the ass.

The second issue was that for some reason the WordPress tool to import from Blogger pulled an extra “>” in at the beginning of every. single. post. from a BlogSpot blog. It’s a little annoying, but it’s also kind of good as an indicator of what posts have been imported and/or reimported.

I will note – about a year ago I imported the blog you’re reading now to WordPress from a Blogger blog about I’d been publishing via FTP for years, and didn’t have the “>” issue. Don’t know if it’s a new bug in the import tool or if it’s something to do with BlogSpot, but the issue was there.

.

Step 4: Make sure all your Blogger posts have the Post Number somewhere in them.

The easiest way to do that is to go into your Blogger template add the following bit of code in right after the <$BlogItemBody$> string:

<font color=”[your blog's background color]“>postID=<$BlogItemNumber$></font>

Making it the same color as your background will make it visible to the script that needs to pull the post ID number, but invisible to anyone actually looking at your site (unless they happen to highlight it). I tried doing this as an anchor but the script wasn’t able to pull it, it’s got to be right in the actual post.

If you don’t mind the postID for every post being visible to your readers while you perform all this nonsense, you can just put in postID=<$BlogItemNumber$> .

.

This page has two totally invaluable PHP scripts for this process written by Justin Watt: “wp-get-blogger-post-IDs” and “import-haloscan.” Run step 2 in that page’s instructions to download, install, and run the “wp-get-blogger-post-IDs” script. This will pull in all your post IDs that you set up a minute ago so that the comments can be matched to the appropriate post.

Here’s the bad news if you have a protected blog: You WILL have to make your Blogger blog temporarily available to anyone if it’s not already through the Settings > Permissions tab on Blogger.

You don’t have to allow any search engine indexing or anything, it just takes the “this blog is open to invited readers only” wall down temporarily, so unless someone knows your URL and specifically goes to look at it in the short bit where the wall is down, there’s nothing to be concerned about.

The good news is that Blogger automatically preserves your readers list so that the second you’re done getting all the info you need, you can immediately turn that protection back on.

NOTE: I did notice when running the PHP scripts on the XAMPP local server that that they can be a little slow, so your wall of protection may need to be down for up to an hour or more, depending on how many posts you have.

.

Step 6: Put your HaloScan Export files in the “htdocs/wordpress” file and number them sequentially.

If you have more than one HaloScan export file, go ahead and number them sequentially so they can be imported as “export1.xml”, “export2.xml”. Then place those files in your main htdocs/wordpress file.

I will note, when I imported 1400 comments to over 2 exports to this blog via WordPress, it did it just fine, but it choked on trying to import all 8,000+ comments at once on the blog I’m working with on this giant mess.

For my friend’s blog, I wound up just importing each export file one at a time, throwing all the others in a folder I marked “exports” so I knew where they were, but the script would ignore them. You can keep them numbered sequentially so you can keep track of which ones you’ve already imported, just only have one at a time in the main “wordpress” folder.

.

Step 7: Run import-haloscan.php.

Remember this page where you got the “wp-get-blogger-post-IDs” script? Well, the second script on that page, import-haloscan.php, is the second piece of this, located in that page’s Step 3. Follow that page’s instructions on how to download, install, and run that script.

The “import-haloscan” script takes all the post IDs you brought in and matches them up with the comments in your HaloScan Export file(s).

.

Step 8: Check and make sure your comments imported correctly.

Make sure the number of comments you imported for each post matches up. You may have a very few missing comments – When I did it for this blog, I lost 7 out of around 1400 comments, and frankly, I’d rather have 99.5% than none.

However, if you’re missing a ton of comments, then you might want to try deleting all the comments (which can be done in bulk from the “comments” tab on the sidebar) and reimporting each export file one at a time.

.

Step 9: Export from WordPress.

Now that you’ve gotten all your posts and comments linked up and in one place, it’s time to start getting them back over to Blogger.

Go to Tools > Export, and hit the “Download Export File” button. All your posts and their comments will export as a big XML file to your default download directory.

.

Step 10: Download the Google Blog Converters App Engine.

The Data Liberation Front has put together a series of Python scripts that will translate the XML WordPress puts out into something that Blogger can understand. You can download a big old folder of scripts from their Google Code page.

Note that you do need to have a recent version of Python installed for it to work, but most recent OS’s come with a version that will work pre-installed. If you don’t have Python installed, here’s a link to the Python site which will give you more info on how to make that happen.

.

Step 11: Fire up your command line.

On OS X, Terminal works fantastically for this because you can just drag and drop the files you need.

Once Terminal is up and running, drag the “wordpress2blogger.sh” script from the “bin” file in the big downloaded file o’scripts into the terminal window. You’ll see a plus sign to let you know that the script is able to be added, and then the script’s name will just show up in the window.

Then, drag in the XML document that exported from WordPress into the terminal window using the same procedure. Once both are added, hit enter. The script will think for a minute, then spit out an enormous amount of text into the terminal window.

.

Step 12: Create the document to upload to Blogger.

Edited to add 02.18.10: Excellent tip from Kevin in the comments that will allow you to skip part of this step:

When executing the command line version, you can automatically capture the terminal output instead of letting it scroll by and then re-selecting/editing. On any *nix system like OSX or linux you just redirect the output into a file with “>”.

sh wordpress2blogger.sh > mynewfile.txt

Back to our regular programming….

In Terminal, go to Shell > Export Text As. This will export everything in the Terminal window as a .txt file. However, you’ll need to go in and do a couple things before it’s ready for upload. If you’re using another command line interface, you can also just do a select all on all text and paste it into a blank document.

Open this .txt document in your favorite text Editor – I prefer TextWrangler because it’s got an option to soft-wrap text so you don’t have to scroll sideways for miles.

At the top of the document, select everything before the “<?xml version=’1.0′…” and delete it, since that’s just stuff that was only relevant to the terminal.

Go down to the very bottom of the document, and make sure you delete the “[your username]‘s-Computer:~ [your username]$”. This is also only something that is useful to the Terminal.

Once you have deleted both of these items, do a Save As… and make sure to save it as a .xml file, and use a name that will allow you to distinguish it as the file that needs to be uploaded to Blogger, like “WordPress Export For Upload To Blogger.xml”.

.

Step 13: Upload the file to Blogger…in a test blog.

I would strongly, strongly recommend setting up a test blog before you re-upload everything to your main blog, since in order to do so, you’re basically going to have to nuke your main blog.

I set up a test blog on BlogSpot that I restricted so that only my friend and I could see it, then uploaded the XML file generated in Step 12. This allowed me to check that all the posts and comments had made it over – Which was good because the first time I tried it, I realized I’d screwed something up and managed to only import comments prior to 2004, and had to go back several steps.

If your upload succeeds and everything looks good in your test blog…

.

Step 14: Backup, then nuke the content on your main Blogger Blog.

Again, I cannot emphasize enough: Backup, backup, backup. Things go sideways. You want a backup of everything. To backup your Blogger Blog, go to Settings > Basic and at the top there’s a link to Export Blog. Click that, and then click the big old button that says “Download Blog.”

Make sure you note where that file is and possibly rename it something like “Backed up main blog” so you can find it if things go wrong.

Once you have that file completely downloaded, you will need to delete all your existing posts so that you don’t wind up with either a) duplicates or b) posts with comments which won’t import because they were marked as duplicates.

To do this go to Posting > Edit Posts. Click on Select All, and you’ll be told that you’ve selected all the visible posts on the screen, and asked if you’d like to select all [however many] posts you have. Click to select all [however many] of your posts, then scroll down to the bottom of the screen and click “Delete Selected.”

Your template will be unaffected, this will just get rid of all your content (Don’t panic, we’re bringing it back in with…)

.

Step 15: Upload the file to your main Blogger blog.

If you got it working for your test blog, this should work for your main blog. You may have to remove some residual HaloScan commenting code (and add some Blogger code back in) from your template to get all the comments to show up properly, but you should be good to go, except for the Known Issues listed below.

.

KNOWN ISSUES

1. This only works with comments that have actually been exported by HaloScan – Once you’ve upgraded to Echo, it spits out a totally different type of XML file that cannot be read by the “import-haloscan” script and unfortunately I’m not enough of a code monkey yet to remedy this myself.

2. The Python parser to go from the exported WordPress to your Blogger re-upload seems to only parse the GMT dates/times that WP spits out, not the actual times stuff was posted (the WP-generated export file contains both pieces of data). Depending on where you live, you can wind up with all your posts up to 12 hours off. For me and my friend, this wasn’t a big issue, but for some people whose blogs are more timestamp-sensitive, this may be a dealbreaker.

3. If you have a blog with a restricted readership, be sure to note that in Step 5 you will need to make it temporarily available to everyone.

4. Two minor issues with WordPress’s Blogger Import tool (failing to import a very few old posts; randomly adding a “>” to every single imported post from BlogSpot) are detailed in Step 3.

—–

Phew.

I am absolutely open to suggestions of how I could have done this more easily, but I did quite a bit of digging around and couldn’t even find instructions for a process this ridiculous and cumbersome, let alone anything simpler.

Hope this helps a few people out, or at least inspires the folks at Blogger to finally put together a HaloScan comment importer. Because this method is completely insane.

• I’m bored out of my mind and am slowly feeling my sanity slip away as I go deeper into my fourth month of unemployment?
• I’m coming down with something?
• My increasingly unbearable bed is causing me to sleep so poorly that I actually feel worse when I wake up?

I’m at least trying to do something about #1 and #3 – I decided to take a couple computer science classes in the fall at my friendly local community college to prevent my brain from turning completely to mush, and to do so online so I can keep going even if I do get a job.

I also decided it’s time to break down and crack into some super-on-ice-pretend-they-don’t-exist funds and get a new mattress, just to be able to get a decent night’s sleep for once.

I’m just going to have to cross my fingers it’s not #2.

Anyway, Chaplin is back and doing much, much better after having his abscess drained. I get to try to toss an antibiotic pill down his throat twice a day now. This is an addition to our routine that he is decidedly not in favor of, but which will hopefully prevent a recurrence of the abscess.

And now, just for giggles, a picture of him in the bed I bought him – technically a dog bed since he’s so huge he wouldn’t fit in a normal cat bed:

He resolutely ignored the bed until the night before I would have been able to return it, and now is sleeping in it all the time. He does have a sense of humor about these things.

The entire trail is 22 miles each way, and I have to bike 2 miles each way to get to the trail. If I’d done the whole thing, I would have gone 48 miles.

Instead, I went all the way to the South end, about two miles south of the Redondo Beach pier. This was about 5 miles South of where I stopped the last time I rode the trail, which was a significantly larger gap than I had realized, so I was a lot more tired by the time I reached the South end when I thought.

The wind was whipping pretty good coming back North, so I think that’s part of what tired me out so much. I think I also need to bring more than a granola bar along to refuel.

I wasn’t really hungry per se, but I noticed I got a lot more tired than I did during my last ride that far South, during which my friends and I stopped for brunch. Pancakes and Guinness are apparently a far more efficient fuel than one wee granola bar.

But I managed to get all the way back to the Santa Monica pier, which is just over 18 miles north of Redondo (and about 3/4 of a mile north of where I got on) before my the combination of the setting sun and my body saying “GET OFF THE BIKE!” determined that I should probably head home.

I wound up breaking down and buying a comically overpriced 20oz Gatorade at the S.M. pier, and I felt WAY better after that, so perhaps I shall invest in some for my next ride.

However, I did 39 miles total, which is nothing to sneeze at, and about 80% of the entire way. We’ll see how many of my limbs I can actually move tomorrow, but for right now, I’m pretty happy I managed to go as far as I did.

However, it is not ideal when your horse randomly decides to break into a trot coming down a hill and you have to try and pull hard enough to stop him with just one hand because the other holds your very expensive camera. That was fun.

By the way, remember how I said I was going out with the Old Fart Bike Brigade 2: Electric Jewgaloo? They’re in way better shape than the Atlanta crowd. I got totally dusted by four guys over the age of seventy biking up a looooong but gentle incline.

They even managed to go up one hell of a steep hill at the end. I took one look at the hill and said, “This is No Country For Young Whippersnappers.” My dad and one other guy agreed with me, and all three of us felt really old.

Also, I need a better seat. Ow.

If I could run on a treadmill without incurring extreme pain, I feel like it would be maybe an eight or nine minute mile. Nothing to write home about, but certainly not as horrifyingly slow as a 13 minute mile.

Then, you arbitrarily reset sometime after I’ve gone a mile and a half into the 3.1 miles I need to finish my gym triathlon, and I have no idea how much further I have to go.

I wound up doing another mile and a half after I noticed it had reset and still coming in at 1:59, but I probably could have made it to 1:55 if I had actually known how far I’d gone in the few minutes between when I saw I’d crossed 1.5 miles and when I noticed it had reset.

Bah. I’ll probably do one more of these before I try my Batshit Crazy Plan of doing a full Olympic-length gym triathlon during the Olympics. That’ll be double the distance I’ve been doing, and will therefore probably take about four hours.

At least I was able to verify that I’ve dropped my swim time to just over 15 minutes to do 15 laps from just over 18 minutes to do 15 laps. Yay, progress!