--- layout: post title: "Distributed commenting: Disqus, Echo and IntenseDebate" created: 1278092773 categories: - Web 2.0 - Social Media tags: - comments - Echo - Disqus - IntenseDebate - Posterous - JanRain - identity ---
I start a lot of my posts these days with a reblog using Posterous. Thus, a lot of permalinks end up over on my "asides" blog, because a lot of the "comment" activity ends up either over there, or on Twitter.
My particular dual website problem might not be solved by this, but it's clear that keeping track of the discussion around blog posts is very much a distributed issue. Don't even get me started on the "Share with Note" in Google Reader that leaves comments stranded over in Reader where post authors are unlikely to to see them :P
The three big systems that I'm aware of at the moment are Disqus, Echo, and IntenseDebate.
On the Bootup Labs and Bootup Entrepreneurial Society WordPress blogs, I went with IntenseDebate. It's my favourite system mainly because I know the Automattic team and I trust them to do what's right for the web long term. Being part of Automattic also removes the (immediate) need to monetize heavily, so they can focus on features and support.
Disqus is very similar to IntenseDebate. In fact, I think it's great that they were being developed at around the same time, because I think the teams competing against each other spurred development and features. Disqus is VC funded, and so is trying a number of different monetization strategies. They have a paid VIP program, although pricing isn't disclosed.
I found a great compare and contrast blog post between Disqus and IntenseDebate that goes feature by feature. At the time (May 2009), IntenseDebate didn't support Facebook or Twitter logins, although they added them both. I have a hard time telling the two systems apart - any passionate users of either system want to point out killer features (or missing ones)?
Echo is the only system without a free option: you can get a 30 day free trial and then switch to either a $10 or $100 month version. Of course, it is fundamentally a very different system. While they do have "JS Kit" (their former name) accounts, this is very much de-emphasized in favour of only using distributed logins from other systems. As well, it aggregates "comments" from elsewhere - whether the comment is a link on Delicious, Friendfeed, Facebook, etc. etc. This has more in common with Trackbacks, but in the Echo system, it is highly integrated and seems more natural than the other two that are "comments first". Finally, Echo doesn't currently write back to the native comment system, using only a JavaScript plugin. This has implications for SEO, and implications for me really wanting to have my own copy of the comment should the service in the sky "go away" :P
On the Drupal side of things, only Disqus and Echo have plugins available, at http://drupal.org/project/disqus and http://drupal.org/project/jskitcomments respectively. From a technology perspective, I like the real time nature of Echo and the general direction that it is heading -- it's almost like having Friendfeed embedded under each post. But, the JavaScript only plugin and the lack of free option for personal bloggers makes it a no go. Since there currently isn't an IntenseDebate plugin for Drupal, I'm going to go with Disqus for now, even though I would rather support the Automattic team.
UPDATE: I just realized after re-reading the Disqus module description, that it will *import* comments from Drupal, but it does not then write those comments back to the native comment system. So, in Drupal, we have zero options for a distributed comment system that writes back / syncs with native comments.
Lastly, the interesting thing about all these comment systems is that in reality, they are about identity. Rather than using an account on one site, or commenting anonymously, it's about re-using identifiers from widely used systems. Whether it is the commenting profile itself, or a third party like Facebook or Twitter.
Since this is the case, tools like Janrain Engage (Drupal module here) should also be considered if you are trying to "solve" getting more comments, and in particular more authenticated comments.
I'm using it here on this site, and just turned off anonymous commenting to experiment more fully with it. This means it should be easy for you to use the "native" comments, but still allow people to easily login and start commenting. You do have to allow unmoderated account creation on the site you intend to use it.