<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.1.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>coComment blog</title>
	<link>http://blog.cocomment.com</link>
	<description>The blog of the coComment team</description>
	<pubDate>Wed, 25 Jan 2012 10:58:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>
	<language>en</language>
			<item>
		<title>Service termination</title>
		<link>http://blog.cocomment.com/2012/01/25/service-termination/</link>
		<comments>http://blog.cocomment.com/2012/01/25/service-termination/#comments</comments>
		<pubDate>Wed, 25 Jan 2012 10:58:24 +0000</pubDate>
		<dc:creator>coComment team</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2012/01/25/service-termination/</guid>
		<description><![CDATA[Dear CoComment User
We are sorry to hereby formally inform you that we will stop the CoComment service according the the Terms of Use per 31.3.2012.
After around 5 years of the CoComment service we had to decide to terminate the service per 31.3.2012 due to the economical perspective of the service and the lack of options [...]]]></description>
			<content:encoded><![CDATA[<p>Dear CoComment User</p>
<p>We are sorry to hereby formally inform you that we will stop the CoComment service according the the Terms of Use per 31.3.2012.</p>
<p>After around 5 years of the CoComment service we had to decide to terminate the service per 31.3.2012 due to the economical perspective of the service and the lack of options and opportunities.</p>
<p>The service will be switched off at 31.3.2012 at midnight 12:00 am.</p>
<p>We thank you for your comprehension.</p>
<p>Swisscom AG<br />
Strategy &#038; Business Development<br />
Venturing<br />
3050 Bern, Switzerland</p>
<p> <a href="http://www.cocomment.com/terms">http://www.cocomment.com/terms</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2012/01/25/service-termination/feed/</wfw:commentRss>
		</item>
		<item>
		<title>coComment on Opera</title>
		<link>http://blog.cocomment.com/2009/08/07/cocomment-on-opera/</link>
		<comments>http://blog.cocomment.com/2009/08/07/cocomment-on-opera/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 05:54:39 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2009/08/07/cocomment-on-opera/</guid>
		<description><![CDATA[A nice solution from QuarterToHappiness (based on a script from Brian Benzinger) to get coComment automatically activated on Opera. Have a look in our forum.
]]></description>
			<content:encoded><![CDATA[<p>A nice solution from QuarterToHappiness (based on a script from <a href="http://www.solutionwatch.com/313/comment-tracking-with-cocomment/">Brian Benzinger</a>) to get coComment automatically activated on Opera. Have a look in our <a href="http://www.cocomment.com/forum/viewtopic.php?id=703">forum</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2009/08/07/cocomment-on-opera/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Firefox 3.5</title>
		<link>http://blog.cocomment.com/2009/08/04/firefox-35/</link>
		<comments>http://blog.cocomment.com/2009/08/04/firefox-35/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 09:56:18 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2009/08/04/firefox-35/</guid>
		<description><![CDATA[I know it took a VERY long time before we get it released, but, finally, it is ready now: our Firefox extension has been upgraded to support Firefox 3.5.
If you already have our extension in Firefox 3.0, then you simply have nothing to do to get it working when you upgrade to Firefox 3.5.
If you [...]]]></description>
			<content:encoded><![CDATA[<p>I know it took a VERY long time before we get it released, but, finally, it is ready now: our Firefox extension has been upgraded to support Firefox 3.5.</p>
<p>If you already have our extension in Firefox 3.0, then you simply have nothing to do to get it working when you upgrade to Firefox 3.5.</p>
<p>If you are already using Firefox 3.5, you need to go to our <a href="http://www.cocomment.com/tools/capture">web site</a> to install our browser extension.</p>
<p>The features are exactly the same as with the previous version: track your conversation (with or without commenting), share an interesting conversation with friends, &#8230;.</p>
<p>Enjoy commenting !</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2009/08/04/firefox-35/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Maintenance</title>
		<link>http://blog.cocomment.com/2009/03/31/maintenance/</link>
		<comments>http://blog.cocomment.com/2009/03/31/maintenance/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 07:15:45 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[service]]></category>

		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2009/03/31/maintenance/</guid>
		<description><![CDATA[coComment service will be unavailable today from 9am GMT to 12am GMT for a maintenance.
We will do our best to reduce the maintenance time and get the service up and running as soon as possible.
Sorry for the inconvenience.
]]></description>
			<content:encoded><![CDATA[<p>coComment service will be unavailable today from 9am GMT to 12am GMT for a maintenance.<br />
We will do our best to reduce the maintenance time and get the service up and running as soon as possible.</p>
<p>Sorry for the inconvenience.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2009/03/31/maintenance/feed/</wfw:commentRss>
		</item>
		<item>
		<title>RSS feeds</title>
		<link>http://blog.cocomment.com/2009/02/04/rss-feeds/</link>
		<comments>http://blog.cocomment.com/2009/02/04/rss-feeds/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 08:43:13 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[features]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2009/02/04/rss-feeds/</guid>
		<description><![CDATA[coComment provides a large variety of RSS feeds: conversations, comments, tag filtering, groups, blog, &#8230;&#8230;
It is quite difficult to display all those feeds on the conversation pages without confusing users: to make it simple, we have created a dedicated page were you can find all your feeds and get the URL you need: http://www.cocomment.com/rssPromote
coComment enable [...]]]></description>
			<content:encoded><![CDATA[<p>coComment provides a large variety of RSS feeds: conversations, comments, tag filtering, groups, blog, &#8230;&#8230;<br />
It is quite difficult to display all those feeds on the conversation pages without confusing users: to make it simple, we have created a dedicated page were you can find all your feeds and get the URL you need: http://www.cocomment.com/rssPromote</p>
<p>coComment enable private conversations: in this case, only you and member of a private group can see the comments. To enforce the security, you have two sets of RSS feeds: public and private feeds. The public feeds will not display any private content. You can share public feeds with anyone, but we recommend that you keep the private feeds links for your eyes only <img src='http://blog.cocomment.com/wp/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2009/02/04/rss-feeds/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Tracking conversations</title>
		<link>http://blog.cocomment.com/2009/01/25/tracking-conversations/</link>
		<comments>http://blog.cocomment.com/2009/01/25/tracking-conversations/#comments</comments>
		<pubDate>Sun, 25 Jan 2009 11:13:40 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2009/01/25/tracking-conversations/</guid>
		<description><![CDATA[Tracking conversation is the core of coComment. And this is not an easy task as in most cases there is no structured way to extract the comments from an article. The only solution is then to get the page and extract the comments from the HTML code.
When working with a limited number of blogs, this [...]]]></description>
			<content:encoded><![CDATA[<p>Tracking conversation is the core of coComment. And this is not an easy task as in most cases there is no structured way to extract the comments from an article. The only solution is then to get the page and extract the comments from the HTML code.</p>
<p>When working with a limited number of blogs, this can looks easy. But when it comes to millions on blogs, this is becoming a hard job as many blogs are customized and do not follow a standard HTML structure for the content. It can also be that from time to time a major blog platform is updated and the basic structure of the pages is changed.</p>
<p>This is exactly what happened recently with one of the most popular blog platform. And, although we were still able to track a big proportion of the conversations, we had some issues on some blogs where comments where either not identified properly, or ended up being duplicated, creating invalid notification of updated conversations. Thanks to <a href="http://aquaculturepda.edublogs.org/">Sue Waters</a> who reported the problem to us, we have been able to identify the issue and fix it immediately. Our database is now being cleaned as we extract the correct conversations: you might get some invalid notification when we fix a conversation you are tracking, but this side effect will not last for long.</p>
<p>Whenever you identify that we are not tracking properly a conversation, do not hesitate to send us an email to integration_AT_cocomment.com or notify us on our Twitter account (@cocomment). We will do our best to fix it ASAP.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2009/01/25/tracking-conversations/feed/</wfw:commentRss>
		</item>
		<item>
		<title>coComment HotForWords vs Danny Comment Contest</title>
		<link>http://blog.cocomment.com/2008/12/16/cocomment-hotforwords-vs-danny-comment-contest/</link>
		<comments>http://blog.cocomment.com/2008/12/16/cocomment-hotforwords-vs-danny-comment-contest/#comments</comments>
		<pubDate>Tue, 16 Dec 2008 10:54:30 +0000</pubDate>
		<dc:creator>coComment team</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2008/12/16/cocomment-hotforwords-vs-danny-comment-contest/</guid>
		<description><![CDATA[Well, at long last I hear you say, we are able to announce the winners.
I&#8217;m sorry it&#8217;s taken so long to get this done &#8230; due to staff changes and the rather rapid disappearance of the contest site we had some trouble getting the data to finally confirm the winners.
We were delighted with the response [...]]]></description>
			<content:encoded><![CDATA[<p>Well, at long last I hear you say, we are able to announce the winners.</p>
<p>I&#8217;m sorry it&#8217;s taken so long to get this done &#8230; due to staff changes and the rather rapid disappearance of the contest site we had some trouble getting the data to finally confirm the winners.</p>
<p>We were delighted with the response to the competition and hope you enjoyed participating.  I&#8217;m sure it won&#8217;t come as any surprise, since you can all read the comments, that the majority view was in favour of Marina &#8230; but Danny came a very close second with support from a vociferous minority.</p>
<p>Anyway, to the winners &#8230;</p>
<p><strong>HIGHEST RATED VIDEO</strong></p>
<p>A close competition for this one but, finally, you decided that the winner was &#8230; <strong>Marina FTW</strong></p>
<p><strong>MOST CREATIVE VIDEO</strong></p>
<p>OK, we admit it, this is more than a little subjective but we did take into account everyone&#8217;s comments to make sure that our views concurred with yours, which they did.</p>
<p>The winner was &#8230; <strong>Marina Best</strong></p>
<p><strong>MOST ACTIVE COMMENTER</strong></p>
<p>This one was, of course, the easiest to score and the winner by some margin, despite losing some of her comments, was &#8230; <strong>Spicy</strong></p>
<p>The prizes will be sent out by the promotional company but, if you haven&#8217;t received them in 2-3 weeks, please let us know.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2008/12/16/cocomment-hotforwords-vs-danny-comment-contest/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Service maintenance</title>
		<link>http://blog.cocomment.com/2008/11/24/service-maintenance-2/</link>
		<comments>http://blog.cocomment.com/2008/11/24/service-maintenance-2/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 07:54:29 +0000</pubDate>
		<dc:creator>coComment team</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2008/11/24/service-maintenance-2/</guid>
		<description><![CDATA[We are experiencing some issues with our infrastructure and we have to put the service down.
We will notify you as soon as the service is up again.
Sorry for the inconvenience.
UPDATE: The service is up again. Again, sorry for the outage.
]]></description>
			<content:encoded><![CDATA[<p>We are experiencing some issues with our infrastructure and we have to put the service down.<br />
We will notify you as soon as the service is up again.</p>
<p>Sorry for the inconvenience.</p>
<p>UPDATE: The service is up again. Again, sorry for the outage.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2008/11/24/service-maintenance-2/feed/</wfw:commentRss>
		</item>
		<item>
		<title>coComment reaches agreement with JS-Kit</title>
		<link>http://blog.cocomment.com/2008/11/10/cocomment-reaches-agreement-with-js-kit/</link>
		<comments>http://blog.cocomment.com/2008/11/10/cocomment-reaches-agreement-with-js-kit/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 16:58:04 +0000</pubDate>
		<dc:creator>coComment team</dc:creator>
		
		<category><![CDATA[commenting]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2008/11/10/cocomment-reaches-agreement-with-js-kit/</guid>
		<description><![CDATA[I&#8217;m delighted to announce that, contrary to rumours circulating recently, coComment has not been acquired by JS-Kit but that we HAVE entered into a partnership agreement which will assist both companies and offer our users more functionality.
We are going to focus on our tracking business for users and will be launching our new coComment PRO [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m delighted to announce that, contrary to rumours circulating recently, coComment has not been acquired by JS-Kit but that we HAVE entered into a partnership agreement which will assist both companies and offer our users more functionality.</p>
<p>We are going to focus on our tracking business for users and will be launching our new coComment PRO solution for Brand Owners very shortly.</p>
<p>In future &#8230;</p>
<p>- coComment will distribute JS-Kit Comments, Ratings, &#038; Polls<br />
- All JS-Kit conversations will be automatically tracked by coComment</p>
<p>All existing sites using coComment comments to power conversations on their sites will continue to be fully supported.  We do intend to migrate but only once we are able to do so seamlessly and without inconvenience to the site.</p>
<p>This is an exciting time for both companies as we grow and offer more products and services to our customers.</p>
<p>As ever, please let us know what you think and feel free to ask any questions.  Following is a simple FAQ addressing some of the already presented ones &#8230;</p>
<p><strong>Will I lose comment powering on my site ?</strong></p>
<p>No, absolutely not.  coComment will continue to power comments on your site until you decide to migrate or we are able to do so in a way that the migration requires no change to your site.</p>
<p><strong>I want to add some JS-Kit functionality (polls, ratings, pre-moderation etc)</strong></p>
<p>Please contact us to discuss a migration plan … most of these can be added very simply.</p>
<p><strong>What will this mean to me in terms of traffic ?</strong></p>
<p>As ever, we can’t guarantee that an audience will visit your site but this deal will massively increase the size of the potential audience on coComment.  Since coComment only ever allows commenting ON YOUR SITE this has the potential to significantly increase visitors if your content and conversations prove popular.</p>
<p><strong>Why are you doing this ?</strong></p>
<p>coComment started offering outsourced comment powering because, in some cases, this was the simplest or only way to gather the comment data.  We believe we’ve built a market-leading comment engine but it’s not our core business and we would prefer to focus our efforts on comment management for users and data provision to brand owners whilst giving our sites the ability to benefit from a company solely focussed on their needs.</p>
<p><strong>Has JS-Kit acquired coComment ?</strong></p>
<p>No.  This is a partnership agreement for the benefit of coComment, JS-Kit and our respective customers.</p>
<p><strong>Who are JS-Kit ?</strong></p>
<p>JS-Kit is the fastest growing provider of outsourced social network tools to sites.  Currently offering comments, ratings, polls and more to over 600,000 sites including AOL/Userplace (300,000 sites), eVite (comments on over 200 million invitations annually) and WorldNow, JS-Kit is also the recent acquirer of the HaloScan business.  They have just announced their latest successful funding round and are therefore stable and continuing to grow despite the current circumstances.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2008/11/10/cocomment-reaches-agreement-with-js-kit/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Technorati integration</title>
		<link>http://blog.cocomment.com/2008/11/03/technorati-integration/</link>
		<comments>http://blog.cocomment.com/2008/11/03/technorati-integration/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 14:17:05 +0000</pubDate>
		<dc:creator>lec</dc:creator>
		
		<category><![CDATA[oops]]></category>

		<guid isPermaLink="false">http://blog.cocomment.com/2008/11/03/technorati-integration/</guid>
		<description><![CDATA[As some of you reported, our integration with Technorati is currently not working. Both claiming a blog and getting your comments indexed by Technorati are affected.
The issue is not from our side and we have contacted them to see how we can solve this issue. We will keep you informed as soon as we have [...]]]></description>
			<content:encoded><![CDATA[<p>As some of you reported, our integration with Technorati is currently not working. Both claiming a blog and getting your comments indexed by Technorati are affected.<br />
The issue is not from our side and we have contacted them to see how we can solve this issue. We will keep you informed as soon as we have more details.</p>
<p>Sorry for the inconvenience.</p>
<p>UPDATE: The update is that there is no update. No answer from Technorati so far&#8230;&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cocomment.com/2008/11/03/technorati-integration/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
