Scobleizer Weblog

Daily link July 31, 2007

Why I don’t recommend Cocomment

I remember why I uninstalled Cocomment months ago. It often interfered with my ability to write comments.

Here’s what’s going on. I just tried to upload a comment over on CNET, and another one here to respond to someone. But Cocomment is giving me an error message on both and keeping my comments from uploading.

Cocomment should NEVER keep a comment from being posted. Even if the service is down. But it does. It’s very frustrating.

Until I stop seeing these kinds of error messages I can not recommend Cocomment which pains me greatly because it provides a great deal of utility when it does work.

To be fair, they are loading up version 2 today. Hopefully that fixes this bug. But for now it’s frustrating me to no end. Luckily I have a browser that doesn’t have Cocomment loaded. Praise be Parallels on the Mac!

34 Comments »

  1. Robert,
    Have you tried Commentful? Commentful?

    I use it for the same purpose as you’re using CoComment and I think it works great. It integrates well with the Firefox browser too.

    Brent

    Comment by Brent Evans — July 31, 2007 @ 3:12 pm

  2. I’ve used a competitor called co.mments.com which launched right after Cocomment and missed a lot of the hype.

    It’s a very simple and far less intrusive service. You add a simple browser bookmarklet to your links bar which you click whenever you are reading a blogpost whose comments you want to track (you don’t have to write a comment).

    Any new comments in those posts get added to your RSS feed for tracking. The very rare time the service is down, you just lose the ability to track not to comment.

    Works on blogs, Flickr, Digg, Upcoming

    Highly recommended.

    Comment by Conor O'Neill — July 31, 2007 @ 3:23 pm

  3. TojaBoya, as we used to say in our family! I had CoComment on my Flock browser and gave it up. Then when you told me you were trying it, I put it back, this time on Firefox. Now I am back to using Flock without CoComment. Agreed that it works well when it works, but it just messes up too often.

    Comment by francine hardaway — July 31, 2007 @ 3:30 pm

  4. Whoops! That was supposed to be Toja Boja, which is a contraction for “I told you so.” I made it unrecognizable, didn’t I?

    Comment by francine hardaway — July 31, 2007 @ 3:30 pm

  5. I love(d) coComment but the Firefox plugin breaks Google Analytics reports. I was dearly hoping 2.0 would fix this but it doesn’t. Sigh.

    As an alternative, I also use co.comments which works well. The only thing I miss is the instant automatic notification in Firefox. However subscribing to an RSS feed is a decent alternative.

    Comment by Andy C — July 31, 2007 @ 3:48 pm

  6. I have been using coComments successfully for the last couple of days. I have not run into any problems so far, but I don’t think I am commenting as heavily as you are.

    It is interesting to see that you are having issues at your usage rate.

    I do like the concept of the service - it can be difficult keeping track of numerous comments on a variety of blogs.

    Comment by Thomas — July 31, 2007 @ 3:57 pm

  7. Sorry to hear that Robert - my hopes went up when you blogged about them a few days ago.

    Hopefully some enterprising microISV out there will come up with a solution for this. Maybe it’s time to stop trying to make web browsers into something they are not and just give people a tool on their desktops that does the same thing.

    BTW, coComments broke trying to leave this comment…

    Comment by Bob Walsh — July 31, 2007 @ 4:27 pm

  8. The thing I don’t like about it is that comments made by coComments members aren’t saved to my blog, but they ARE saved to the coComments server. What a way to ruin a conversation…

    Comment by Julie — July 31, 2007 @ 4:30 pm

  9. I just experienced the same with my Firefox plugin. ‘Cannot post comment’
    Thought when clicking the X in the CoComment bar it is disabled for this post only.

    Also realized Google Analytics not working. I’ll give them till tomorrow to fix it. Otherwise i will be gone.

    Comment by Markus Tressl — July 31, 2007 @ 4:32 pm

  10. I apologize you experienced some trouble with coComment. We are uploading the new version (v2) today. Though we did as much testing as possible, some bugs, such as this one, may show up. Please let us know if you come across anything else and we will try fixing it as soon as we can. Thanks! coComment Team

    Comment by Kristina Serafim — July 31, 2007 @ 4:47 pm

  11. Yep, I removed them from my Firefox plugins and I’m dropping them. That’s ridiculous. I lost 3 different comments at places because of their ridiculous outage. I have liked them, but that kind of garbage makes them dead to me.

    Comment by Frank Roche — July 31, 2007 @ 6:32 pm

  12. Well said Robert. I’ve been looking for a way to track comments and gave CoComment a shot after you mentioned it. But I had some issues actually submitting a comment while using it and that’s unacceptable no matter how useful it is.

    =Ryan
    rstewart@adobe.com

    Comment by Ryan Stewart — July 31, 2007 @ 6:49 pm

  13. […] to post comments on certain blog platforms it doesn’t understand.  I think this is the trouble Scoble is having. More critical is that it interferes with the slick javascript that runs Google […]

    Pingback by I Miss CoComment : Web Strategy Thoughts — July 31, 2007 @ 7:27 pm

  14. […] blog readers through their comments—left the development server today for version two. While not everyone was forgiving the hiccups in the transition, overall this site promises to promote interaction and niche […]

    Pingback by BlogSchmog » CoComment — July 31, 2007 @ 9:08 pm

  15. Hi Robert -

    I’d be interested to see your co-comment at CNET if you try again. I’m interested in any opportunities continue the discussion.

    bernie.mcginn@cnet.com

    - Bernie

    Comment by Bernie McGinn — July 31, 2007 @ 9:42 pm

  16. I installed (then quickly uninstalled) CoComment earlier today after the Firefox extension brought my browser to its knees. The browser slowed to a crawl, I couldn’t post comments, and things were just not good at all.

    I like the idea of CoComment though. I comment on a lot of blogs and it’d be nice to have a way to know when others respond to what I’ve said. Maybe I’ll try again when CoComment fixes the bugs and has an extension and service that actually works reliably.

    Comment by Anthony Papillion — July 31, 2007 @ 10:22 pm

  17. From their site:
    Please Note: coComment is currently in early Beta testing. Please bear with us as we refine and improve the service! If you have any suggestions please do not hesitate to contact us.

    I guess we need to give them some more time. I really hope they come up with a solution that doesn’t break.

    Comment by Vivek Sonny Abraham — August 1, 2007 @ 1:53 am

  18. Same thing happens to me. Less when I’m in Firefox but it still happens.

    Comment by Tinu — August 1, 2007 @ 1:56 am

  19. […] Why I don’t recommend Cocomment « Scobleizer (tags: cocomment web20 blog comments) […]

    Pingback by links for 2007-08-01 « My Weblog — August 1, 2007 @ 3:20 am

  20. I’ll second http://co.mments.com/

    I tried coComments when it first launched, but wasn’t impressed as it only seemed to show me other comments left by coComments users. co.mments.com will show me all the comments left on a post.

    And as you click on a bookmarklet independently of posting a comment, it won’t ever get in the way of you leaving a comment! (and you can track comments on posts that you haven’t commented on yourself)

    Comment by Adrian McEwen — August 1, 2007 @ 3:27 am

  21. Mr. Scoble - In looking at the CoComment bookmarklet there seems to have been an update made somewhere along the line. A DIIF points out some refined stuff and IF you like the concept of CoComment you might try the bookmarklet. I’m using it in Safari (look! it’s not like it’s eggplant) and have had nothing but good experiences. If the plugin is ruining things give the bookmarklet a shot and maybe, just maybe the relationship will be preserved until they can issue a healthier update. Or, not.

    Comment by gwhiz — August 1, 2007 @ 6:42 am

  22. Quick update: We are finishing up the migration to v2 and we expect to have the new version up on August 2nd, Thursday. In the meantime, bear with us as we’re trying to eliminate any potential glitches associated with the transition. We’re very excited to show you v2, so come and check it out later this week!!!

    Comment by Kristina Serafim — August 1, 2007 @ 1:08 pm

  23. And one more thing … please don’t hesitate to contact us with any questions or suggestions. We will do our best to make the process as smooth as possible. Thanks! coComment Team

    Comment by Kristina Serafim — August 1, 2007 @ 1:11 pm

  24. I didn’t experience the blocking Robert did, but I did notice trouble logging in to cocomment today, and then the page seemed to be missing some old comment threads I had– at least now I know why, assuming some growing pains during 2.0 switchover?

    Comment by Doug Haslam — August 1, 2007 @ 1:58 pm

  25. I’m starting to get frustrated, but am not going to give up just yet. I’ll give it a full week.

    Comment by Shaine — August 1, 2007 @ 5:49 pm

  26. […] Why I don’t recommend Cocomment « Scobleizer “Cocomment should NEVER keep a comment from being posted. Even if the service is down. But it does. It’s very frustrating. Until I stop seeing these kinds of error messages I can not recommend Cocomment.” (tags: comment+tracking tools problems) […]

    Pingback by links for 2007-08-02 at contentious.com — August 1, 2007 @ 5:54 pm

  27. I love the idea of cocomment, but it slows down my browser tremendously. I’m having trouble opening more than 5 tabs (and usually I have around 20 open).

    Anyone the same problem?

    Comment by Patrick — August 2, 2007 @ 2:11 am

  28. coComment V2 Beta is now live! Please check it out. We’ve added many new features, which we’ve been told makes coComment the most sophisticated conversation tracking tool out on the market. Some of the features we suggest to try include:
    1. My coComment (Your personal page with overview of your conversations, your community and what’s hot in the conversational space)
    2. My Conversations (Updates on your conversations and the ones from your friends, groups, favorites plus invitations sent by your buddies to join interesting conversation)
    2. My Community (Your friends, groups, favorites, followers and conversational neighbors
    3. My Groups: Starting point to share conversations by interest, only with selected people (private) or extend interactions for your audience
    4. Sidebar: Navigate efficiently from any one conversation to another
    5. Comment Anywhere: Start a conversation on any webpage, comment on and share with your community interesting information anywhere on the web

    Please let s know if you have any questions or feedback! Thanks, coComment Team

    Comment by Kristina Serafim — August 2, 2007 @ 8:57 am

  29. […] Why I don’t recommend Cocomment Technorati tags: cocomments, firefox, extensions 21b0 […]

    Pingback by The End of CoComment — August 2, 2007 @ 9:38 am

  30. When it interfered with my online purchases, it was bye bye cocoment!
    Jamie

    Comment by Terinea Weblog — August 2, 2007 @ 9:46 am

  31. @Jamie: I just tried leaving a comment on your blog, but was not able to. Anyhow, what I wanted to communicate is that we understand your frustration with experiencing some issues with coComment over the last few days. As we’ve indicated in prior posts, we were migrating to the new version, V2 Beta. Though we did extensive testing and tried eliminating any issues associated with transitioning to the new version, we understand this may have caused some glitches. V2 Beta is now live and we think you’ll find that we’ve added significant improvements and new features to the service. We encourage you to check it out and please let us know if there’s anything we can do to make the experience better. Thanks! The coComment Team

    Comment by Kristina Serafim — August 2, 2007 @ 9:57 am

  32. I just dumped it too. it kept slowing everything down and bringing up boxes under boxes..sorry gone.

    Comment by Rob Evans — August 3, 2007 @ 7:16 am

  33. Ok, we got the message from few of you with comments about the new interface, etc. As a result, today we have made a change to the system so that we retain the advantages of the new (cleaner interface, more functionality) with the simplicity and extensibility of the old Conversation Tracking. Let us know what you think please. Thanks! coComment Team

    Comment by Kristina Serafim — August 3, 2007 @ 10:51 am

  34. […] Ik ben schijnbaar niet de enige die er zo over […]

    Pingback by Cocomments vernieuwd · Bakkel dot com — August 3, 2007 @ 1:26 pm

  35. A few days ago, I removed the coComment extension from my browser because the new version seemed to trouble more than the old version.

    Comment by Avinash — August 10, 2007 @ 8:03 am

  36. @Avinash: Can you please tell us what type of problems you are having? We’ve solved most of the known bugs and will definitely try to fix the issues you’re experiencing. Feel free to e-mail me at kristina@cocomment.com. Thanks!

    Comment by Kristina — August 10, 2007 @ 8:36 am

RSS feed for comments on this post. TrackBack URI

Leave a comment

© Copyright 2007
Robert Scoble
robertscoble@hotmail.com
My cell phone: 425-205-1921


Robert Scoble works at PodTech.net (title: Vice President of Media Development). Everything here, though, is his personal opinion and is not read or approved before it is posted. No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.


Login
Blog at WordPress.com .