Version 0.4c and Change of Development Team
We just released version 0.4c of coComment.
Firefox extension
The most important part of this release certainly is the official release of our firefox extension. Have a look at it at save yourself the trouble to press the bookmarklet all the time. As an added feature, the firefox extension also provides an automatic notification whenever a new comment is made to one of your conversations.
We also did some bug fixes for better support of MovableType and Wordpress and added support for Journalspace, CommunityServer, Kulando and Clagnut.
Last but not least, we added a feature that allows blog integrators to track all comments, even from users that are not using coComment (we already added this to this blog).
New development team
At the same time we have to inform you that the current development team is replaced with a new one. As of now, Dominik ‘hilti’ Hiltbrunner, Jean-Claude ‘JC’ Brantschen, Roger ‘jegi’ Jegerlehner and me, Peter ‘Merlin’ Balsiger, will not be a part of coComment any more.
Good-Bye and have fun.
RSS feed
April 28th, 2006 at 13:29
whats happen with this development team?
April 28th, 2006 at 13:32
Teamwechsel bei Cocomment?
Komisch, wieso gehen bei cocomment insgesamt 4 Entwickler von einem Tag auf den anderen von Bord? Wer steckt dort eigentlich sonst noch dahinter? Bis jetzt hatte ich immer das Gefühl das seien diejenigen die Cocomment entwickelt und lanciert haben?
A…
April 28th, 2006 at 14:13
love the software. much thanks
April 28th, 2006 at 15:31
@leumund: the tech team has handed over the project to new guys in Geneva. cocomment’s is now around 10 people, with early members like nico (product dev), marco (business dev), steph (communication & community), chris (clientside javascript), leif (java dev), christophe (sotfware architect), guillaume (crawling specialist) and myself (now project lead) still working on creating a better app for you all!
As you might know coComment started inside the ideas incubator of Swisscom (swiss national phone operator) and will soon become an independent company. This move - a very usual one - is part of that transition, and we will have more information about all that pretty soon, stay tuned!
April 28th, 2006 at 16:29
love the new tag field, it works really well, thanks for the new plug-in.
April 28th, 2006 at 20:06
Oh, this is gonna be sweet to play with! Great work, cocomment team!
April 28th, 2006 at 23:07
This is wonderful. Been waiting for this for a long time. Kudos for your hard work.
April 29th, 2006 at 04:21
Excellent extension, catches a couple of bugs that the script doesn’t.
Sad to see the team go out but all the best to you guys and welcome to the new team.
Finally, what do you mean by blog integrators, track all comments?? I don’t get that part.
April 29th, 2006 at 07:47
Extension feedback: shouldn’t alert user when the comment added to the conversation is his own.
ChronoCracker: it means that if your blog is “integrated” then coCo will also track comments by non-coCo users on it.
April 29th, 2006 at 08:05
This extension is an excellent idea, it will really simplify the use of coComment.
Good move guys!
April 29th, 2006 at 10:31
The grasemonkey script wasn’t working for me anyway and this is great! Thanks to Tara for bringing it to my attention….love and peace, sometimes,… B.
April 29th, 2006 at 11:04
@chronocracker and @steph: Currently, the new feature that allows all comments to be tracked does not seem to be documented anywhere (or is it just me that can’t find it anywhere?). We’ll have to fix that asap
I’ll be back with some draft instructions…
April 29th, 2006 at 11:45
@mocha: I wanted to propose the team to turn the documentation into a wiki so people could contribute. Do you think that would be a good idea?
April 29th, 2006 at 15:48
The creation of a doc wiki would be a great help.
April 29th, 2006 at 16:58
Sure, I think turning this into a wiki would be a great idea!
Of course, that doesn’t mean we get out of documenting new features in the first place
April 29th, 2006 at 17:46
Yes, Laurent, I think it would be a good idea!
April 29th, 2006 at 19:46
coComment Helps Us Remember What We’ve Said
I was actually thinking of something like this. I was going to make it my first RoR project but that might just be to ambitious. Anyways, plain and simple, coComment is the only service that allows you to enjoy the full potential of blog comments on t…
April 29th, 2006 at 23:58
The following is just a quick draft updating the instructions for embedding coComment into your blogs. With this new approach, you will be able to track *all* the comments posted, not just the ones by fellow coComment users.
This first section you can skip, if coComment already extracts the correct information automatically. You only need it if the automatic extraction on your blog does not work or does not work reliably. This step is already documented in more detail at http://cocomment.com/integrate
<script type=”text/javascript”>
var blogTool = “MyBlogManufacturer”;
var blogURL = “http://www.domain.com/~myblog”;
var blogTitle = “My Blog”;
var postURL = “http://www.domain.com/~myblog/?p=42″;
var postTitle = “This is Roger’s “great” post”;
var commentTextFieldName = “messageTextArea”;
var commentButtonName = “SubmitButton”;
var commentAuthorLoggedIn = true;
var commentAuthor = “Douglas Adams”;
var commentFormName = “commentForm”;
</script>
In the following second section you’ll see the two additional attributes that you will need to include in the script tag if you want to track all comments:
<script id=”cocomment-fetchlet”
trackAllComments=”true”
src=”http://www.cocomment.com/js/enabler.js”>
</script>
Note that in this example I linked to the new enabler.js file instead of the cocomment.js file. Pointing directly to the cocomment.js file should work as well, but I hope loading the enabler.js file first will provide a performance benefit. If you try this new track all comments feature with both possible configuration options, pointing to the enabler.js and to the cocomment.js then please let us know whether you notice a performance difference.
Also, keep in mind that this is an experimental feature. We are curious what your experiences will be, how well it will work and where it will break
Chris
April 30th, 2006 at 00:09
Since I can’t post the example code here without screwing up the formatting and I can’t update the Blog Integration page right now, I’ve posted a quick draft over on the forum:
http://www.cocomment.com/forum/viewtopic.php?pid=1436#p1436
For blogs that embed coComment using these new attributes, it should now be possible to track *all* comments.
Chris
April 30th, 2006 at 10:56
[…] Dewayne already pointed this out a few posts back, but in case you missed it - my favourite service, coComment, has released an extension for Firefox. Had this running for a couple of days now, and I haven’t got a single niggle to report. Loving it. […]
April 30th, 2006 at 22:24
[…] Today I learned, via Easton Ellsworth, that CoComment has made its system much less labor-intensive. They’ve debuted the CoComment Firefox extension, which automatically updates your CoComment account as you leave a blog comment! The only extra step beyond making the blog comment is adding tags – and that’s optional. […]
May 1st, 2006 at 03:35
Sorry to hear of your departure from development, Merlin. Will you still be on the coComment team?
May 1st, 2006 at 09:50
@mocha: I edited your comment so the script should be visible here (yes yes I know
May 1st, 2006 at 16:14
No, I will not be part of the coComment team anymore. Same is true for most other previous developers.
May 1st, 2006 at 20:25
Awesome update guys. Thanks.
Two things.
1) Why does a blog have to be “integrated” to track all comments? It’s technologically feasible without it. See http://co.mments.com/. Maybe the guy running that site should be part of the new team.
2) I would love the ability to subscribe to comments of users *by tag*. Say I have a group of friends and we have a club called TechNerds. If I could subscribe to each of their coComments pages but only their TechNerds tag it would be a great way for us to push the things we’re commenting on to each other (but not everything we’re commenting on). Did that make sense?
Thanks again for the awesome service.
-Jeremy
May 1st, 2006 at 21:12
Regarding 1)… One doesn’t replace the other. I see them as two distinct features. Crawling for comments after they have been added will never be as comprehensive and reliable as tracking the comments as they are posted. Crawling is the next best thing where tracking at the source is not possible. We decided to implement the tracking first, since it offers ultimately the better user experience.
2) Yes, that makes sense. We need feeds for tags.
Chris
May 2nd, 2006 at 01:14
Merlin, I’m sorry to hear of your departure as you have been a great help to my issues with coComment. Good luck with whatever you are doing and I look forward to meeting the new members of the team.
May 3rd, 2006 at 21:09
[…] The coComment blog announced the release of coComment version 0.4c, which includes a Firefox extension. We just released version 0.4c of coComment . . . The most important part of this release certainly is the official release of our firefox extension. Have a look at it at save yourself the trouble to press the bookmarklet all the time. As an added feature, the firefox extension also provides an automatic notification whenever a new comment is made to one of your conversations. […]
May 5th, 2006 at 06:39
I’ve got some issues with it. I blog daily on a blog platform that doesn’t work well with it, and I wouldn’t complain, but it’s actually stopping me from posting an entry (not a comment) to the platform while the extension is enabled. It took me hours to figure it out, but once I disabled the plugin I could again post to the platform.
My email is robyn *at* sleepyblogger.com if you want to discuss this or you want to troubleshoot this issue.
May 5th, 2006 at 07:13
Duzins, I’ve sent you an email.
May 5th, 2006 at 09:02
RE: FF Extension
Just wondering if anyone else is experiencing some difficulty submitting or hitting the submit button on various forms? …specifically, ones that don’t have integration w/ coComment directly. Is it because of the the FF 1.5.0.3 update?
May 5th, 2006 at 10:41
I’ve never seen that happening and haven’t heard about it from anybody else. Can you provide some URLs where this is happening?
May 5th, 2006 at 11:39
I hope in next version, I can set or the extension can auto-converte the time.
Because the popup says “07:34 new comments relates to xorms”, but the time on my timezone is 18:34
May 5th, 2006 at 18:10
BTW, I tried http://co.mments.com/ . For some blogs, it has better user experience because it’s fast and easy to get and track all comments. BUT for some blogs I usually visit, it can do nothing but just a bookmark.
May 5th, 2006 at 20:12
@Chris/Mocha:
Assuming your FF is 1.5.0.3. Turn off the extension, then go to http://www.cingularme.com/do/public?l=en-US&v=cingular … then just press the Submit button. It should bring you back to the same page w/ error message.
Now, turn on the extension and go to the same link above. Try hitting submit. Let me know how it goes…
HTH
Sherwin
May 5th, 2006 at 23:12
I see! Thanks! I’ll fix!
May 6th, 2006 at 04:00
No no no… Thank you! =)
May 6th, 2006 at 04:02
BTW. I don’t know if Steph forwarded you one of my other findings/issues… but here you go, http://www.justamemo.com/archives/2006/04/my_findings_on_cocomment_movable_type/
May 6th, 2006 at 08:41
I’ll go and take a look…
May 9th, 2006 at 15:14
A bit of feedback about the extensions (more like a list of features I’d like it to have):
- I’d like to turn off new comments auto-checking. I tried setting it to a time of 0 minutes, didn’t work.
- Anyway, the popup is a bit annoying. I’d like to turn it off by default.
Eeerm… that’s it. Quick, uh? Keep the good work.
May 31st, 2006 at 14:35
@RinzeWind… which popup do you mean? Not sure whether this is a feature or a bug !?