Support the Comment API or I Won’t Comment


Support the comment API.  Support it so I can read and reply to comments about your post.  Support it from your blog and support it from your blog reading software.  Scoble is hardheaded about full-text support in RSS.  I happen to agree with his perspective, but I’ll go one step further… feeds (or clients) that do not include Full-Text AND the comment API infuriate me. 


On the server side this includes Scoble’s feed, Mark Cuban’s feed, the google groups newgroup feeds, etc.  The list goes on.  On the client side its a big reason why I won’t download Saucereader or pay money for newsgator and a HUGE reason why RSS Bandit is so cool.  This, combined with posting support from w:Bloggar means I never have to really leave my reading client and wait for a web page to load… Unless, or course, I’m trying to see what Scobles readers are ranting about for a specific post. 


Sure, I could subscribe to the “Comment Feed”, but then I have to try and make the connection between the comments and the post.  You lose context, break up the flow of reading blogs with comments, and force me to leave a speedy client to reply. 


My hardheaded statement: I won’t read your users comments or leave my own comments on your blogs if you don’t support the comment api and I certainly won’t use your blog reading software.

Comments (10)

  1. Ryan Farley says:

    Josh. I could not agree more. I feel the same way. As soon as I find I have to leave my reader (RSS Bandit) I get all irritated and usually don’t both commenting.

  2. I agree with Josh. Blog and aggregator software that do not support the CommentAPI really don’t go well with me. I find that if a blog does not support it I usually just don’t comment and I espcially don’t read post comments. Also, I refuse to use a reader anymore that doesn’t support it.

  3. I agree with Josh. Blog and aggregator software that do not support the CommentAPI really don’t go well with me. I find that if a blog does not support it I usually just don’t comment and I espcially don’t read post comments. Also, I refuse to use a reader anymore that doesn’t support it.

  4. Anand says:

    You read my mind Josh. One of the features I like with Sharpreader is its support for Comment RSS and the neat way I can read the comments and directly relate the content to the post.

    But then not all blogging software support comment rss on the server. So I have to live with not having comment rss in my blog..:-(

  5. J.P. says:

    RE: the comments, I am with you on this one, this is easy to do and benefitial. But, it does have a cost. You see, I dont think that this method of including comments in the RSS feed is strictly compliant with the RSS standard. Sure there are a bunch of things that people include in their RSS feed (I have seen dare’s feed) that will WORK in aggregators, but just keep in mind that its not necessarily part of the standard.

    (This comment brought to you by clicking on the comments link in RSS Bandit)

    J.P.

  6. jledgard says:

    As an end user, for the most part, I could care less about specific implementation details and the standard. I just want general improvements. 🙂

  7. Brian Beatty says:

    I use NewsGator and FetchLinks <a href=’http://graemef.com/?q=project/fetchlinks‘>http://graemef.com/?q=project/fetchlinks</a>

    It follows the link to grab the page of the blog

  8. jledgard says:

    Looks cool. But it still requires an extra navigation to the page and doesn’t have posting support right?

  9. Simon Phipps says:

    The problem with this, Josh, is that the area of commenting is still in rapid evolution, so if you make an early decision that it’s standardised you’ll lock yourself out of whatever innovations happen while it’s evolving, such as the use of captchas (you commented to http://www.webmink.net/2004/05/blog-spam-solved.htm about them) or of federated identity proofs. There’s always a fine balance involved in any declaration of standardisation as we both know, but to decide to opt out at this stage would be a mistake, in my view.

    S.

  10. jledgard says:

    I’ll admit. There is still a lot that could be improved in the area of commenting and I’m sure a lot will continue to change. My perspective though, speaking purely as an end user here, is that moving to a system that requires me to view a web page to comment is taking a step backwards in terms of usability. Of course, at this point maybe our conversation should have moved to a forum/newgroup. 🙂