Haloscan going the way of the dinosaur

Haloscan is getting upgraded to Echo:

Once presented with the upgrade message, Haloscan users will have 2 weeks to make a decision. You will have the following two options.

  1. Upgrade to Echo for $9.95/year – all your comment data will be transitioned over automatically
  2. Export your Haloscan comment data and turn off their service

This explains the recent interest in my Importing Haloscan comments into WordPress 2.3 from Blogger post (which is based on my original Importing Haloscan comments into WordPress from Blogger post from June 2005, back when I first moved from Blogger to WordPress).

It’s funny to think that in a small way I’ve helped countless users transition their Haloscan comments (usually embedded in Blogger posts) to WordPress over the past four and a half years, judging by the 203 comments that the two posts above have accumulated. Though it will be a bummer for the few users who are not able to make the transition, and thus lose their comments, I have to say it will be nice to have one less smidgen of code to support.

As an aside, I always get a chuckle out of the following image from Sam Ruby’s Rights vs Responsibilities post:

Since code costs essentially zero to distribute, my first thoughts are not on what rights I want to assert, but what obligations I wish to assume. If you look at software licenses, both commercial and open, this is something that they are careful to enumerate. In most cases, it essentially comes down to: “if it breaks, you get to keep both halves”.

· Blogging