Comments are a strange part of blogging. I love ‘em, and I hate ‘em. The majority of comments I get seem to fall into the camp of: “Gee, Micah, I really liked what you wrote.”

But, the comments I love are the ones that extend the discussion. Sometimes those comments spill over onto Twitter, or direct emails, or lunch discussions the next day. And those are the comments that I would love to capture. Those comments I would love to extend beyond my blog. Those comments I would love to make interactive.

When I started to get back involved with the Colorado tech scene, I got to know one of the founders of Intense Debate, Josh Morgan. Fantasic guy. Clearly in over his head, but a hard worker. His partner, Jon Fox, is a brilliant developer, but needed direction. Still I really liked what they were doing.

So, I added Intense Debate.

After a couple of weeks, Intense Debate began to really bog down performance wise. Plus, it didnt have trackback support.  Knowing the guys, I finally made the decision to pull it off my blog, and go back to the default comments. I explained why (performance and lack of trachback support). I figured the default comment system would be good enough.

Over the months, I watched Disqus continue to grow and Intense Debate languish. “They will do what they are going to do,” I thought to myself. “I hope that ends up positive.”

And, Disqus continued to innovate and extend their reach. And, finally, Disqus got funded.

And while there has been minimal innovation with Intense Debate, Disqus has continued to add features and even developed an API (which as a non-technical person always means to me that one can do more cool stuff with the product).

And, even more importantly, more and more of the blogs that I interact with were using Disqus.

Still, I stayed loyal, and added no comment system to my blog.

Fast forward several months.

My blog has grown. Many times, I get a dozen or so comments on posts. Its no 100+ that some people get, but its more than 1 or 2. So, I started reviewing comment systems again.

For those that dont know, I run business development at Lijit Networks, and one of my roles is finding additional content sources for our technology to index. At Lijit, we are content agnostic. We will index any RSS/OPML feed or URL.

I often say, “Google wants to index everything. At Lijit, we only index the information you care about.” So, if you want to index Disqus or Intense Debate comments, we want to make it easy.

So, I emailed Daniel Ha over at Disqus and Tom Keller at Intense Debate.

Five minutes later, I got an email back offering development and business development support. Access to a private API, basically whatever we needed. (It didnt hurt that Daniel and his business partner were both UCDavis–my alma mater–*ahem* almost grads).

I was completely amazed at the speed and willingness of Daniel to make sure that the two companies worked well together and produced a superior integration.

And even then, I didnt add Disqus. I stayed true to my word, not adding any comment system.

This post: http://www.jangro.com/a/2008/04/08/hacking-disqus/ became the straw that broke the camel’s back for me personally.

Why? Because the community had begun to choose which comment system they wanted to use by hacking it, and if you read the comments, Daniel jumped right in and has taken some of the hacks, and integrated them into the system. Disqus had embraced the community right back.

Then, with the addition of video comments (something I want to play with, and would rather do than write a comment), Disqus became too good to not use.

So what does that mean? Its simple enough. In this world we all work in, if you dont embrace (and be embraced by the community) you cannot succeed. If you dont continually innovate, you cannot succeed.

Moral to the story: If you dont embrace the community, and you dont innovate, you die.

And that is why I chose to add Disqus comments to this blog. Will they stay? I dont know. It will depend on if Daniel and team continue down their current path. Could Intense Debate produce something that is interesting enough for me to walk away from Disqus? Sure, and frankly, I hope they do. But, for now, Disqus it is.

Popularity: 8% [?]

Share and Enjoy:
  • Suggest to Techmeme via Twitter
  • RSS
  • Twitter
  • FriendFeed
  • Digg
  • StumbleUpon
  • Yahoo! Buzz
  • Reddit
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • email
  • Ping.fm
  • Great post, and you touched on one of the things that has impressed me with the Disqus team, their strong dedication to the end user. Lots of companies preach customer service 2.0, not that many practice it.

    PS: You should pitch me on Lijit some time, I've seen it around the place, both for a post + I might even run it on The Inquisitr.
  • Duncan, I would love to pitch you, in fact we have a new business development guy who should be setting up a call with all of us...You might know him, he is a good dude.

    I really like to think that understanding the importance of community engagement is the difference maker for many companies. And, of course, that Lijit has a pretty cool product that is focused on supporting and partnering with publishers.

    (ok, enough pitching...)

    Look forward to talking to you soon.
  • Micah, I just caught this post and wanted to sincerely say thanks. I try to stay active within the community because I understand, as a web enthusiast/early adopter, how it feels to reach out to a service and be ignored. We have the luxury of dealing with an incredibly vocal userbase. If we do something wrong, they'll tell us. If we manage to make them happy, the let everyone know. I love this.

    Regardless of what service you decide on using, it's been a pleasure learning from your feedback. Based on some of the notes you made about improving our SEO, I've been dong a lot of reading and have consequently learned a bunch.

    BTW, regarding trackbacks, we're in the designing stages of something very cool. I am very excited about this one and I hope you'll agree.

    Oh, and go Ags. ;)
  • Thanks Daniel. I hope that the message is read loud and clear. I stay a fan (just like folks will stay a fan of lijit) as long as we continue to listen to the community and innovate (publicly - which when focusing on internal issues can be hard).

    I am a big fan of having two players in a space that continually push each other to be better. I hope that Intense Debate and Disqus continue to have this type of relationship.

    Good luck!

    Oh, and go Ags. (I hope your mom is going to make you go back and finish.)
  • Daniel, please consider joining a wider discussion about how comments should be routed back to blogs rather than coming up with a Disqus only solution. There's been some early discussion amongst Habari and WordPress developers, and one of the founders of ZicZac recently started http://www.commentback.org/ to enable further discussion, with the aim of developing a standard. I even sent you an email about it a while back :)
  • I was just checking this out this morning. Thanks for the link.
  • I don't know the disqus guys but I do know Jon and the rest of the team behind Intense Debate and I wouldn't count them out just yet :)
  • Jon blows me away with his skills, and like you, I dont count anyone out. I just want to see innovation, innovation, innovation, and then some innovation. And even more so, interaction with the community. Which is the same for EventVue, buddy!

    The web has become community driven. We all need to understand and embrace that.
  • You should expect groundbreaking innovations from Intense Debate - you'll be blown away soon enough. We hope to have you back - as Rob said, I wouldn't count us out just yet!
  • I certainly look forward to the innovations and new features. Usage is highly important as well. Go get 'em!
  • I went through an "Intense Debate" as well, and ultimately it was a technical factor that pushed me toward Disqus (the API integration of comments on the backend). But Daniel's ever-presence made me feel good about relying on a third party for something so critical where I might have just stayed with the old school comments.

    Both things are slipping. The API version is lagging in features and Daniel has been more absent. I totally appreciate how busy Daniel is, but it's important and I hope he can find a way to balance that.

    I've seen hints on Twitter that the API version is getting updated. I'm happy to see that as I was getting worried.

    As for the community presence, at this point it's got to be you, Daniel. Find a way to work it out.
  • Thanks Scott.

    A balance if priorities will always be difficult, but I'm trying. We've been expanding both service and team, but our releases are still on track.

    I like to be tranparent in what we're doing: the API plugin is undergoing a lot of design right now. We hope to get that released in June. This is not a "company-endorsed" ETA, but rather just my personal assessment.

    I really appreciate the support.
  • Dude, I completely agree. I think one of the best things a company can do is get out there, meet their users, and listen. Your users will tell you what they want.

    It'll take some work to get out there and form a relationship with them but when you do it will be the most important thing you ever did.
  • Justin,

    It has been eye opening for me at Lijit. I have spoken to all kinds of users, both in terms of size, stature and subject expertise. All of them, as I am sure many people are with any third party, leery of giving up a critical component of their publication to a third party.

    So to help alliviate that, we are fanactial about support and listening.

    Like any good relationship its how the relationship is protected when things go wrong versus when things are easy and simple. Hopefully, I am learning more about that every day, and acting on it.
  • Gee Micah, I really liked what you wrote.

    Ahem. I mean .. cheers. Before this post, I'd only come into contact with Intense Debate. It'd be good if one of their people come and comment here, give some alternative feedback.

    Was just thinking, the more "hackable" a 3rd Party product is, the less likely it is that people will want to change. Intense Debate is very easy to pull in and out of a blog at the moment. But if you invest time in an API, like Disqus .. it's just one more little step that ties you to the product.

    I'm off to check out Disqus more.
  • I don't see this as a competition between DISQUS and Intense Debate. Both services have their advantages and disadvantages. What's happening instead is that we, the content producers, and we, the commenters, are being torn apart by the "Comment Divide".

    Either producers integrate both services DISQUS and Intense Debate, (remove that FriendFeed comment system on blogs... useless IMO) and have the best of both worlds.
  • I thought about this concept. Basically, I would allow readers to
    comment as they want, ID, Disqus or FF.

    But, its impossible to have the cross pollination of content, given
    that ID and Disqus are both companies looking to eventually generate
    revenue...
  • Ahh, good point.

    Sooner or later, if they both decide to start charging for their services (or a premium), we'll end up spending more than we ought to be. Then we'll have to drop support of one service, and goodbye all comments.

    Hmm, they really must join the Open Comments Workgroup and develop well "open comments". http://open-comments.org

    Sigh...
  • In talking with both Tom and Daniel, they seem very open to the idea
    of creating a "bill of rights" for commenters. I think its a great
    step in the right direction...
  • Ah yes, I've read about that. It is very interesting actually, and Intense Debate initiated the idea and the discussion. It's great news that the two are open to collaborating in any form. Truely "Community", or "Open". Gone with the old of keeping to oneself.

    Can't wait what else they can do together. (And can't wait SezWho and Outbrain to join these two... )
blog comments powered by Disqus