Haloscan

» see haloscan.com as it lived, on the wayback machine

~ the goodbye ~

i remember haloscan from the 2005 to 2008 window. i was at university in ankara then, on a fresh ttnet adsl line and reading more english-language tech blogs than was strictly defensible for someone preparing for the otoyol of computer engineering coursework. the haloscan widget was the small underlined line that sat beneath almost every blogspot post i clicked on. it always read "comments" with a number in parentheses next to it. you clicked it and a popup window opened with the thread inside.

anyway, blogger.com did not have native comment support until late in the decade, so the way you added a comment box to your blogspot template was to paste a haloscan script tag and let the widget fill in. it was free. it carried small ads sometimes. the threads lived on haloscan's servers, not on your blog, which is the detail that turned out to matter later.

the company was founded in 2002 and ran on a small team out of california. it was bought by js-kit in july 2008 for an undisclosed amount, mike arrington at techcrunch covered the deal in a short post. js-kit was already shipping a richer comment product and the plan from day one was to migrate the haloscan installed base over. by 2009 the new owner had rebranded the whole company as echo. by february 2010 the migration deadline had moved from optional to forced. on 19 february the haloscan servers went dark, the announcement said the hardware was physically failing and there was no choice. bloggers were given a window to export their threads as xml and either pay echo's per-month rate or walk away.

the long memory of haloscan is the empty comment widget on dead blogs. open an archived blogspot from 2006 today and the "comments (0)" link will sit there forever, the popup it pointed at has not existed for sixteen years. a lot of the conversation underneath the early blogosphere got pushed into that one xml export and most bloggers never imported it anywhere.

~ the chronicle ~

~ what the widget did ~

the technical pitch was almost the whole appeal. blogger.com had been bought by google in 2003 and the comment system on the platform was still thin for years after. haloscan slotted in with one script tag and added a comment counter plus a styled popup with trackbacks bolted on. the trackback feature was the part that mattered for the blog-conversation era, because it let one post notify another that it had linked to it, which is how the long blogroll chains formed.

this part was more for english-language bloggers than for me, anyway. the widget was free to host but the bandwidth costs on haloscan's side scaled with how many blogs ran it. by 2007 the service was reportedly serving a meaningful slice of every blogspot pageview, which is the part that made js-kit interested in buying it.

~ how the migration ended it ~

js-kit's plan was to flip the free haloscan tier into the paid echo subscription. echo's pitch was richer, real-time updates, social media reposts, threading that looked more like 2009-era forums than 2003-era guestbooks. the catch was the price tag. echo charged a monthly fee per site. haloscan had charged nothing.

the blog reaction was rough. chip bennett's farewell post on 11 february 2010 read like a public divorce letter, several other bloggers wrote near-identical posts that same week. the most common move was to migrate to disqus, which was still free and which already had a wordpress plugin most bloggers could install in an afternoon. a smaller group moved to intensedebate. an even smaller group went back to whatever native comment system their platform offered.

~ the long tail ~

js-kit's own product did not survive long. echo discontinued comment hosting entirely in 2012 and pivoted toward social-media integration tools, the whole pipeline that started with haloscan in 2002 was unplugged inside ten years.

the broader story is that the third-party blog comment widget was always going to be the wrong layer. when wordpress.com and blogger.com finally shipped first-party comments, the script-tag-in-the-template pattern became surplus. disqus survived by pivoting from a widget into a network with its own logged-in identity, intensedebate got absorbed by automattic and quietly maintained. haloscan was the version that did not pivot. its name now mostly lives on as a footnote in the broken comment links of the long blogspot archive.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »