If you're new here, you may want to subscribe to my RSS feed. You can even subscribe by email! Thanks for visiting!
I was one of the early joiners of CoComment. I even posted about when it was first un-launched — Robert Scoble blogged about it and all of a sudden the folks at CoComment suffered a landslide of server traffic as everyone and his dog tried to join, an effect known in tech circles as the ’slashdot’ effect, named after the slashdot website which, if it posts something about someone, very often causes that someone’s server to crash because thousands of visitors follow the link from slashdot within minutes of it being posted.
So I have recently been diligently ‘tracking’ conversations I have on typepad blogs (because typepad blogs don’t seem to offer an ‘email me if any further comments are added to this post’ option, unlike Wordpress blogs.
I use Firefox as my default browser and despite logging in to coComment via the toolbar button, none of my conversations are tracked. Nothing in the last week and a half that I have been diligently tracking…
Very frustrating! Anyone else experiencing this?
{ 1 trackback }
{ 11 comments… read them below or add one }
Bryan Person, Bryper.com 08.06.06 at 1:15 am
Lee:
I was thinking about blogging about this topic myself. I finally set up CoComment a few days ago, and I’m equally unimpressed.
It’s not tracking my conversations either, and it hasn’t removed a conversation I asked it to stop tracking.
The concept is a very good one, but the execution, in this case, is not up to par.
–Bryan Person
Blog: Bryper.com
Podcast: NewCommRoad.com
Owen Lystrup 08.06.06 at 3:40 am
Same thing has happened to me as well.
Lee 08.06.06 at 11:43 am
What makes a service like coComment so necessary is that typepad don’t offer a ’subscribe to comments’ option. If they did I’d have no reason to use them.
Christophe 08.06.06 at 8:00 pm
Hi Lee,
Sory for the troubles. We will investigate this and fix it ASAP.
Could you please point us to a blog where you experienced this behaviour ?
Thanks
Christophe 08.06.06 at 8:06 pm
One more thing: in cocomment, your comment to this post is not linked to a profile: it looks like you are currently not logged in cocomment: could you please check that ?
Thanks.
Lee 08.06.06 at 9:12 pm
Hi Christophe,
Try http://www.stuartbruce.biz/2006/08/office_2007_roc.html
for a post that didn’t track (but I seem to have problems with all typepad blogs).
Have logged in now and even though I don’t normally track my own conversations on my own blog, or those conversations on blogs where there is a ’subscribe to comments’ option (usually on a wordpress blog), I have subscribed to this one.
Off the top of my head I can’t remember any others, but I’ll start noting them from now on.
Oh, there may have been one on this site:
http://andreaweckerlecopywriting.typepad.com/new_millennium_pr/2006/07/humor_links_dat.html
Christophe 08.06.06 at 10:27 pm
The problem comes from the fact that you are not actually logged in cocomment. I will investigate in the server what is hapenning here.
Thanks
Owen Lystrup 08.07.06 at 4:19 pm
Christophe,
I’m always logged into coComment and I have a problem where I track a comment, but it doesn’t show me when a new comment has been added to the conversation. I always have to troll through every comment I made and see which were updated.
It’s kind of monotonous.
Sebastian 08.07.06 at 4:34 pm
Christophe, I have to say, actually, kudos to the relaunch. I had tried cocomment in the beginning but then switched to co.mment. The new release is much better although it still has trouble catching super save comments (www.vowe.net, http://www.sixtus.net). Keep it up.
Christophe 08.08.06 at 4:11 pm
Thanks Sebastian,
We are working hard to improve the service but the diversity of the web make it difficult to reach the 100% support. The most reliable solution is to have the blog integrated (as Lee is doing) so we are 100% sure to get the right information, even if the commenter is not a cocomment user.
However, we will investigate the blogs you suggested to see if we can extend our support.
Lee 08.10.06 at 6:09 am
Hats off to Christophe, who is working behind the scenes with me to sort this out. It is potentially a cookie problem. Thanks, mate!