The bad news is that in order to actually get someone to hire me, I need to start writing applications that will easily indicate to people who are doing the hiring, “See, I know what I’m doing even though I have no professional experience with this!”

This is, as you might imagine, a little time-consuming.

I also have been working on a bunch of other projects, including updating Designated Nerd, my tech consulting/programming website, which is going to get a lot crazier in the months to come. Lots of back-end stuff I need to work on, but we’ll see how it all goes.

I’ll probably post a bit more here when I’ve got some real, published projects to show off, or when something colossally awesome/stupid happens to me.

But for now, I’m just going to have to put up the “PARDON OUR DUST” banner.

I liked their service. It was simple, it worked solidly, and the price for unlimited backup was pretty reasonable. And then.

There was some fooferal today because Mozy decided to can their unlimited service, and introduce tiered data pricing. I couldn’t remember quite how much I had backed up with them, so I went to check and see exactly how much it was, remembering it was around 100GB.

Huh, I thought when I looked at at my data total. Why is it only 80MB?

Turns out when I installed an update to the Mozy Mac client shortly before I left for Spain in early December, it wiped out all of my backup settings. The only thing that was being backed up for almost two months was my calendar database.

This, as you can imagine, severely pissed me off.

I hadn’t bothered to check that the Mozy client was backing up what I’d told it to backup because that’s just not a setting you think a company’s own software would obliterate, especially after being solid for 2 years.

But somehow, they managed to do it, and I was left flapping in the breeze until the end of Unlimited backup made me actually look at how much (or more accurately, how little) data I had been storing with them.

I chatted with one agent who told me that the files were still on the server, and if I reset my backup settings it would realize what files were already backed up, and only upload the files that were necessary.

When I got a newer version of the backup software up and running, I checked to see how big the upload was going to be. 133 GB, or basically, the entire contents of my hard drive, an upload that would take days at best.

A second agent attempted to reassure me that no, the data really was there, it would compare what was already on the server to what my software was trying to upload and the full upload wouldn’t be anywhere near 133GB.

And I realized: I didn’t believe him. I COULDN’T believe him because his company’s product had fucked up so, so badly that there was no way I could trust what they were telling their employees and in turn their employees were telling me.

I couldn’t trust that what I thought I’d backed up was actually there, and I couldn’t trust that anything I would back up in the future would ever be there. Online backup software is based primarily on trust, and they’d completely blown it.

So I canceled my account, and started the sloooooow process of re-uploading all my data to one of their competitors.

To their credit, Mozy didn’t put up a fight about refunding me the money I paid for December and January, and they offered their apologies. I said thanks, but I really hoped that whatever idiot let that code out into the wild got fired.

I did not add, though I was thoroughly tempted to, “out of a cannon.”

I took one guy’s statement in a review about being able to control the volume with the remote to mean it was the volume on the monitor, but after trying and failing to get my remote set up, I went back and realized he was controlling the volume through his Home Theater PC, not his actual monitor. The monitor doesn’t even have an IR receiver. Oops.

I’m super, super excited to pay the return shipping and restocking fees that dumbass move earned. I’m still debating if I want to order a different one online or break down and rejoin Costco for their far more generous return policy.

At least I had two better pieces of technology news today, which helped mitigate my expensive stupidity:

1) I got my iPhone replaced for free after the lock button finally died completely, 10 days before the warranty ran out. I won’t go into the details because it got a bit complicated, but hey, brand refurbished phone!

2) I got my new dual-network setup up and running with a minimum of issues, so now I have my regular network and my N-Only network ,which is SUPER fast and means I can transfer files about three times faster than I could before. Basically, I can transfer an SD episode of Futurama in its entirety in 2 minutes. Win!

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.

And frankly, I’m not going looking for the seven comments that didn’t make it. I feel like a 99.5% success rate on something this complicated is good enough, particularly given how much time I already sank into getting it this far.

But the good news is there are now comments going back to 2003, about a year after I started this blog. It’s kind of amazing to realize that although posting has fallen off substantially over time, I’ve been writing this blog for almost eight years.

Like most internet things I eventually get into, I resisted for quite a while, not quite seeing the point of it until some of my friends who seemed to get it faster really got into it.

But I think after following a few people for a bit, I see where a fun space for it lies between a blog and Facebook and a direct line from my brain to the internet.

Plus, I’ve been functionally unemployed since March. There’s really only so long you can resist a complete time-killer like Twitter when you’re unemployed for months at a time.

We’ll see how I get the hang of it over the next few weeks, but the good news is that the limits of the format dictate that even when what I post is not amusing, it’ll at least be short.

For some reason, though, I’m not as angry. Probably helps that Chaplin is sleeping on my feet right now and not in an animal hospital, doped to the gills and recovering from surgery.

Probably helps that I’ve finally made a decision to move forward on getting out of showbiz. Probably helps that I feel like I’m on the right path, trying to learn something new instead of just flailing around.

I also think I’m done with actual weight resolutions – I’ve lost 86 pounds and would like to lose the 14 more that would a) take me to an even 100 and b) put me at a BMI of 25, but I feel like that’s going to be a long, frustrating process that’s not really worth making New Year’s Resolutions over. Better to focus on time goals that, while promoting weight loss, feel somewhat more achievable in the space of a year.

So, in the hopes that publicly stating what I want to do this year will give me some motivation to actually do it, my New Year’s Resolutions:

1. Finish redesigning my damn website by the end of January.

The blog is actually fine – it’s the main site that’s a travesty, not updated since 2003. I’ve taken about four stabs at redesigns that have never actually launched, and I am completely out of excuses for why it hasn’t. Happening by the end of January, dammit.

2. Lower my 10k elliptical time to consistently under an hour.

The frustrating part about this is that my ability to do this varies from machine to machine – I’ve actually done this on a couple of machines, but on the machine I use regularly, I’ll need to cut a minute a mile off my time to make it happen. I think over a year, I can do it.

3. Lower my 2 mile swim time to under 1 hour 10 minutes, and start swimming 4km from time to time.

4km is about 3/4km farther than 2 miles. I want to be swimming 5k’s at some point, but I know I’ve got to get my stamina back up quite a bit from where it is now – having the flu absolutely killed a lot of the progress I made this year in terms of building up stamina. Just got to keep putting down the building blocks.

4. Learn as many new programming languages as possible, with the goal of having a working iPhone application before I go back to school in September.

I’m going to be doing a lot of self-directed learning over the next few months, so I think I need to set a goal to give me some motivation to actually get off my ass and learn things. I think I’ve got a good idea for a program, so we’ll see how it goes.

5. Remember that if my plans and resolutions don’t work out, there are always more plans to be made.

I’m already moving from Plan B (TV mogul) to Plan C (professional nerd), and Plan C has many sub-plans of its own. I just have to remember to keep going with the flow, and try to make enough money to keep myself and Chaplin fed and sheltered in the meantime.

And that’s it. Hopefully everyone has a fun evening tonight, and hopefully 2010 starts off with a nice Northwestern Outback bowl win tomorrow morning, and next year we get into an even better bowl that doesn’t start at eight in the goddamn morning.

Happy New Year!

Until I was 28, I thought I was going to make movies and TV for a living.

Until I was ____, I thought I was going to be a professional computer nerd.

—

Life has taken a lot of twists and turns for me since the writers’ strike of 2007-2008. Since that strike began on November 5, 2007, I have spent almost twelve of these last 24 months unemployed.

Part of that was the strike. Part of that was my decision to move into the production line and out of working directly for producers, which is an inherently more volatile career path.

But much of it has been the way the bottom has absolutely fallen out of filming in L.A. The combination of the strike starting a rearrangement of the way the business works and the economy in general going down the tubes has contributed to a precipitous drop in filming here. There’s just no work.

I realized a couple months ago as I was making my bajillionth phone call looking for work that I have not received one phone call back since June. June was also my last interview, for a job I had locked down until an actor decided to put in a good word for his niece, and then she had it locked down.

I’ve offered to take PA jobs again, but they’re not looking to take someone with as much experience in higher-up jobs as I have. In some cases, they think it’s because I think I’m above the scut work (which I don’t, I wouldn’t be applying for a PA job if I did), and in some cases, it seems they think I’ll outshine them (with the people who are insecure enough to actually worry about this, that might be a more valid concern).

Everywhere I look in terms of what my skills can get me in the entertainment business, I either see jobs that are so severely overworked and underpaid that I would rather work at Starbucks again than take them, because at least at Starbucks I would get health insurance, or nothing at all.

And frankly, the way things are going right now with the economy and the out-of-state filming incentives and the studios and networks freaking the fuck out about every last penny, I don’t see that scenario changing in the next 18-24 months at the absolute earliest.

Sometimes, you just wake up and realize that the universe is trying to tell you something. And the universe is telling me it’s time to do something else with my life.

—

And now, a brief comic interlude:

Click to enlarge.

From Amazing Super Powers.

—

I’ve always been a pop-culture nerd, but I wasn’t a serious computer nerd until the last 3-4 years. I learned some HTML programming in college, and really enjoyed it, but the complete time-sink that is working in entertainment pulled me off the track that would have kept me learning more about programming.

While the primary technical things that I’ve done in the last few years have involved technical troubleshooting and working as an ad-hoc IT Guy, what I really want to learn about is how to make computers do what I want them to.

And to do that, I need to learn how to program. I need to learn about architecture and C++ and the vagaries of programming for different platforms. I really want to learn how to take some ideas I have for programs and turn them into reality, from start to finish.

This, however, will require a fair amount of school. Right now I’m on step 0.1, taking some very basic classes at the community college level, trying to figure out exactly where my interests take me in terms of how I want to program.

My ultimate goal is a Masters’ in Computer Science. I’m in the middle of a choose-your-own-adventure bit of figuring out how that’s going to happen, but I do know that I’m sure as shit not going back to school just to get a second Bachelor’s.

I’m putting together an application to Stanford to start next fall, since a) they have an extraordinarily strong program and b) they are one of the only well-respected Graduate-level CS programs that will actually accept people who don’t have a CS undergrad background as long as they’re willing to learn.

It’s an extremely competitive program, so I have a fairly comprehensive backup plan standing by. I’ll get into it at some point down the road if need be.

If I do somehow manage to get into Stanford, however, I expect to hear a lot of this [note: mp3 link].

—

I’ve talked to a fair number of you guys about all this in differing degrees of depth, but I felt like I really needed to try and bring everything together in one place, almost more for my own purposes than to try and clarify it for everyone else.

I certainly won’t say I’m never working in entertainment again. If someone offered me a job right now that would help me keep my union health insurance even a bit longer, I’d take it in a second. But I don’t see my future in production anymore, and that’s where things have changed.

This is a path that’s been slowly coalescing over the last few months, and has picked up a lot of steam since about Labor day, when I finally accepted that I probably wouldn’t work in entertainment for much of the rest of the year.

It took a long time for the pieces to come together well enough for me to see them, but once they did, my way forward became much, much clearer. I’ve got a plan, or really a bunch of plans all leading in the same direction.

Now all I have to do is try and figure out how to get there from here.

Thank Jeebus I’m paranoid and made a second backup on a different disk before I blew away the main drive. That’s what’s reimporting to my computer at the moment. If I didn’t have that, I’d be completely screwed.

What kills me is that I’d just gotten the computer to boot off the cloned drive half an hour earlier, and there were zero signs the drive was about to die. Second I hooked it up after installing Snow Leopard, it started clicking and refusing to spin up, dead as a doornail.

Now I just have to hope to hell this copy works right when it’s done importing in…1 hour and 15 minutes.

Edit, 2am: Couple nasty bugs in the 10.6.0 version that took me a while and a bunch of Googling to squash, but I think I’ve got the nastiest issues squared away. And even if I don’t…I’m going to bed.

I’m leaving tomorrow to visit dad and Ray Ann in Idaho and of course, last night one of the speakers on my laptop decided it didn’t want to go on the trip.

A few seconds of popping, and then an unbelievably high pitched squealing that did not stop until I turned the computer off were all I needed to send me running to the Apple store.

I knew I was probably going to lose the computer for a few days for the repair, so I ran a backup and went to do one final sync of my iPhone…and the whole thing went nuts.

The phone didn’t sync right, I had to restore from a backup, the whole thing was just so annoying. Luckily after considerable fiddling I got it to work, but I was still re-syncing all my music when I got to the Apple store.

The speaker was pretty clearly a hardware issue, so they’re going to fix it. Of course, it’s a 5-7 day turnaround, so I just sucked it up and handed over my computer, asking them to run every diagnostic they has so if anything else was screwy, it’d at least get fixed now.

Godspeed, little computer.

So now I get to have another laptop-less vacation because of a hardware issue (my video card crapped out at Christmas, if you recall).

I think this one will be a little more survivable for 2 reasons – the iPhone is considerably easier to use as a standalone device than the crackberry was, and the fact that it’s Idaho instead of Connecticut also helps.

It’s biking and hiking and fishing and rafting, and not sitting and eating and sitting and eating. It’s the fact that I’m driving and can hop in my own car if my folks start to drive me nuts and just go out.

All that to say: I’m off to Vegas tomorrow morning, then up to Idaho on Wednesday. Hope you all have a good week, and I apologize if I’m slightly incommunicado.