It’s a sad day for me right now – I’ve had to strip the coComment integration code out of the blog. After chasing down errors for the past couple of days, I finally came back around to my original suspect, and sure enough removing coComment from the equation seems to solve all problems. (I probably would have isolated the problem a bit sooner, but conflicts with extensions and browser-caching issues were muddying the waters. That and I was panicking – my pretty blog was broken and I didn’t know why!)
Hopefully this is just a temporary measure.
I love coComment and all it does, and am still an avid supporter of the system, but at the moment full integration is breaking things with a *bit* more frequency than I am really happy with. This is especially taking into consideration the non-coCo users of this blog who are still in the majority, despite my constant harping-on about coCo! Here at Bright Meadow more than half the fun often happens in the comments – if you can’t comment, well, it’s just not cricket.
coComment first came to my attention around the same time as another comment-tracking system. That other system, MyComment, relied on the blog-owner to have a plugin that enabled a commenter to track any comments he’d/she’d made on that blog. coCo, in a subtle but important distinction, relies on the commenter to have a bookmarklet/extension on their end. Comments are tied (primarily) to the commenter and only secondarily to a particular blog. A blog-owner needs to know nothing about coComment, and perhaps more importantly, to do nothing – if a commenter wants to track their own conversations it is, quite sensibly, up to them.
This functionality excited me and still does – though I publish an RSS feed for the comments on this blog (found here), and though I get email notifications of all comments made, tracking comments is hard when I am at work as I don’t have access to a feed reader, or to webmail. With the integration however, I just have to periodically check a single webpage to be notified of any new comments made across Bright Meadow.
This isn’t the only reason I use coComment, or decided to integrate it into the blog, but it is the bit that is going to be affected most by my current decision.
I don’t anticipate this decision being final – hopefully in a day or so I’ll be able to put the integration code back in and all will once again be well and shiny in my commenting world. This is the price you pay for playing with beta technologies. Sometimes things have to go on a little safari before they work properly. Sometimes new and fantastical beasts are found. Other times you get stuck in the swamps and need to be rescued. It’s this exploration that makes it exciting!
As I said, here’s hoping Bright Meadow can be fully integrated again soon 🙂
*1* Blogs have a page of their own that conversations get added to – Bright Meadow’s is here. Each individual post/conversation thread also gets a page, as does each commenter. A veritable smorgasbord of options on how you can track conversations!Back