<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: WP Plugin: iG:coComment</title>
	<atom:link href="http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<pubDate>Sat, 22 Nov 2008 11:27:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Amit Gupta</title>
		<link>http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/#comment-282550</link>
		<dc:creator>Amit Gupta</dc:creator>
		<pubDate>Mon, 08 May 2006 06:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/#comment-282550</guid>
		<description>Yeah well, as per my discussions with one of the devs on coComment, I asked him to put an option so that all comments on a post can be tracked instead of just those made by coComment users &#38; he said that it'll come soon. This feature is now available. And with this plugin, you won't have to click on the bookmarklet, if the blog admin has enabled either the auto-enable or track all comments(enabled by default) option.</description>
		<content:encoded><![CDATA[<p>Yeah well, as per my discussions with one of the devs on coComment, I asked him to put an option so that all comments on a post can be tracked instead of just those made by coComment users &amp; he said that it&#8217;ll come soon. This feature is now available. And with this plugin, you won&#8217;t have to click on the bookmarklet, if the blog admin has enabled either the auto-enable or track all comments(enabled by default) option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lelia Katherine Thomas</title>
		<link>http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/#comment-274411</link>
		<dc:creator>Lelia Katherine Thomas</dc:creator>
		<pubDate>Thu, 04 May 2006 16:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2006/05/02/wp-plugin-igcocomment/#comment-274411</guid>
		<description>coComment is a good idea, actually, but until it becomes entirely automated and more widespread (which is going to be hard for them to accomplish, I believe it) it is worthless, in my mind. I tried it, and remembering to use the bookmarklet all the time was a complete pain in the ass. And this--offering a coComment option with your site's comments--seems like a bad idea. A ton of users have a hard enough time understanding what a Gravatar is, much less coCommenting.

Also, let's face it, it's easy to track a user's blogosphere activities if you pay attention to their del.icio.us links and several other thingss; it's no truly hidden secret mostly. Now, posting on &lt;i&gt;other&lt;/i&gt;, non-blog sites is a different matter. Like in forums, group sites (e.g. deviantART, MySpace, etc.).</description>
		<content:encoded><![CDATA[<p>coComment is a good idea, actually, but until it becomes entirely automated and more widespread (which is going to be hard for them to accomplish, I believe it) it is worthless, in my mind. I tried it, and remembering to use the bookmarklet all the time was a complete pain in the ass. And this&#8211;offering a coComment option with your site&#8217;s comments&#8211;seems like a bad idea. A ton of users have a hard enough time understanding what a Gravatar is, much less coCommenting.</p>
<p>Also, let&#8217;s face it, it&#8217;s easy to track a user&#8217;s blogosphere activities if you pay attention to their del.icio.us links and several other thingss; it&#8217;s no truly hidden secret mostly. Now, posting on <i>other</i>, non-blog sites is a different matter. Like in forums, group sites (e.g. deviantART, MySpace, etc.).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
