<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Video: The Conversation &#8211; Centralization In, Decentralization Out</title>
	<atom:link href="http://www.centernetworks.com/conversation-centralization/feed" rel="self" type="application/rss+xml" />
	<link>http://www.centernetworks.com/conversation-centralization</link>
	<description>Web 2 and Social Media News and Reviews</description>
	<lastBuildDate>Sat, 21 Nov 2009 01:50:56 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: centernetworks</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17114</link>
		<dc:creator>centernetworks</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17114</guid>
		<description>&lt;p&gt;
Thanks Corvida - I am totally for showing the comments on FF - just push to the source for adding. It&#039;s really that simple.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>
Thanks Corvida &#8211; I am totally for showing the comments on FF &#8211; just push to the source for adding. It&#8217;s really that simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayson</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17115</link>
		<dc:creator>Jayson</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17115</guid>
		<description>I like what you said it works wonders in keeping everything centralized awesome post.</description>
		<content:encoded><![CDATA[<p>I like what you said it works wonders in keeping everything centralized awesome post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahsheen Porter</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17313</link>
		<dc:creator>Rahsheen Porter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17313</guid>
		<description>This sounds all well and good, but it reminds me of a discussion I had recently regarding the FriendFeed Comments plugin. The core of the issue is that everyone is not using the same platform to run their blog. This automatically multiplies the work the FriendFeed development team would have to do. 

The only things I can think of that would serve to decrease the number of variables involved are assuming every blog runs Disqus or has a separate comment feed in place for each post.

Either way, I still don&#039;t see why the burden is being placed on FriendFeed. Yes, they have provided a means for discussion to happen away from the blog. Readers apparently have found commenting in FF easier and more convenient. 

Also, people are finding posts they never would have before. Why comment on the blog itself when you can leave a comment on the item left by your &quot;friend&quot; directly in FF?

Lastly, it appears that FriendFeed has provided an extensive API. I only looked over it briefly, but it seems to me they have provided the tools for anyone to do exactly what is being asked for any blogging platform in existence. 

Maybe I&#039;m missing something, but it appears they have done their part already.


</description>
		<content:encoded><![CDATA[<p>This sounds all well and good, but it reminds me of a discussion I had recently regarding the FriendFeed Comments plugin. The core of the issue is that everyone is not using the same platform to run their blog. This automatically multiplies the work the FriendFeed development team would have to do. </p>
<p>The only things I can think of that would serve to decrease the number of variables involved are assuming every blog runs Disqus or has a separate comment feed in place for each post.</p>
<p>Either way, I still don&#8217;t see why the burden is being placed on FriendFeed. Yes, they have provided a means for discussion to happen away from the blog. Readers apparently have found commenting in FF easier and more convenient. </p>
<p>Also, people are finding posts they never would have before. Why comment on the blog itself when you can leave a comment on the item left by your &#8220;friend&#8221; directly in FF?</p>
<p>Lastly, it appears that FriendFeed has provided an extensive API. I only looked over it briefly, but it seems to me they have provided the tools for anyone to do exactly what is being asked for any blogging platform in existence. </p>
<p>Maybe I&#8217;m missing something, but it appears they have done their part already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maxwell</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17346</link>
		<dc:creator>Maxwell</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17346</guid>
		<description>spot freaking on.</description>
		<content:encoded><![CDATA[<p>spot freaking on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corvida</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17347</link>
		<dc:creator>Corvida</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17347</guid>
		<description>Well said Allen! Awesome video and something that users of FriendFeed should really take into consideration. Not only that, the devs of FriendFeed should also take a look at this. While you can&#039;t make everyone happy, you can do your part and help out. Thanks for posting this :D</description>
		<content:encoded><![CDATA[<p>Well said Allen! Awesome video and something that users of FriendFeed should really take into consideration. Not only that, the devs of FriendFeed should also take a look at this. While you can&#8217;t make everyone happy, you can do your part and help out. Thanks for posting this :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I cant use my name?!</title>
		<link>http://www.centernetworks.com/conversation-centralization/comment-page-#comment-17619</link>
		<dc:creator>I cant use my name?!</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17619</guid>
		<description>Almost... but not quite... the comment being left at FriendFeed should be &lt;strong&gt;offered&lt;/strong&gt; back to the source, yes, (the source might not always accept it), then the entire conversation brought back to FriendFeed, Digg, wherever... but if the source deletes a comment, or in some cases rejects the comment as not good enough to be displayed, then the user should still have a forum where their voice can be heard. Plain and simple. Even FriendFeed does not have this down perfectly... nobody does.

What you are suggesting is a move whereby users have to go and provide personal information all over the internet just to interact around content. (Or in cases of Flickr, or YouTube, etc., sign up for an account) It goes both ways as far as &quot;trapping&quot; things go...  Many times people want to have conversations with their friends, not with some blogger they have never heard of, regardless of if that person wrote the article being discussed. Your idea is neat, but it&#039;s more focused on an &lt;strong&gt;idealistic&lt;/strong&gt; solution rather than a &lt;strong&gt;technical&lt;/strong&gt; one. Furthermore, it&#039;s one that risks attacking users for their willingness to engage something they find interesting based solely on the conduit with which they elect to do so. 

Users/Readers are people; People have rights. Plain and simple. The rights to &quot;own&quot; their comments, the rights to leave those comments in places they see fit. I agree that an open dialogue is needed in this space, and that nobody has the perfect solution (not friendfeed, not favorit, not shyftr, not disqus, NOBODY)... it will require a lot of compromise by a lot of web services and sources working together for the USERS. Getting the source in on the party is a given, you&#039;re spot-on about that (&lt;em&gt;and a separate widget for displaying a services comments above or below a blogs comments is a far cry from a &quot;solution&quot; as far as I&#039;m concerned&lt;/em&gt;).  But what you are suggesting really abandons the user&#039;s rights. If people had to give their email address out and continually fill out form after form of name, website, captcha, login, etc. etc. then the conversation will simply be stifled and die.  I&#039;m sure &lt;strong&gt;nobody&lt;/strong&gt; wants that.

This video is a great contribution the bigger picture though! No doubt about that.  But it still falls short of being &quot;right&quot;, in my opinion.

* UPDATE* : P.S.  In trying to post my comment here I&#039;ve been given a hard time by your commenting system already. It harks right back to everything I was illustrating about the conversation eventually being stifled... Note my inability to simply post my comment as &quot;Matt&quot;, cuz that&#039;s my name, but heaven forbid the system think I&#039;m trying to impersonate another &quot;Matt&quot;...  lol. ;)</description>
		<content:encoded><![CDATA[<p>Almost&#8230; but not quite&#8230; the comment being left at FriendFeed should be <strong>offered</strong> back to the source, yes, (the source might not always accept it), then the entire conversation brought back to FriendFeed, Digg, wherever&#8230; but if the source deletes a comment, or in some cases rejects the comment as not good enough to be displayed, then the user should still have a forum where their voice can be heard. Plain and simple. Even FriendFeed does not have this down perfectly&#8230; nobody does.</p>
<p>What you are suggesting is a move whereby users have to go and provide personal information all over the internet just to interact around content. (Or in cases of Flickr, or YouTube, etc., sign up for an account) It goes both ways as far as &#8220;trapping&#8221; things go&#8230;  Many times people want to have conversations with their friends, not with some blogger they have never heard of, regardless of if that person wrote the article being discussed. Your idea is neat, but it&#8217;s more focused on an <strong>idealistic</strong> solution rather than a <strong>technical</strong> one. Furthermore, it&#8217;s one that risks attacking users for their willingness to engage something they find interesting based solely on the conduit with which they elect to do so. </p>
<p>Users/Readers are people; People have rights. Plain and simple. The rights to &#8220;own&#8221; their comments, the rights to leave those comments in places they see fit. I agree that an open dialogue is needed in this space, and that nobody has the perfect solution (not friendfeed, not favorit, not shyftr, not disqus, NOBODY)&#8230; it will require a lot of compromise by a lot of web services and sources working together for the USERS. Getting the source in on the party is a given, you&#8217;re spot-on about that (<em>and a separate widget for displaying a services comments above or below a blogs comments is a far cry from a &#8220;solution&#8221; as far as I&#8217;m concerned</em>).  But what you are suggesting really abandons the user&#8217;s rights. If people had to give their email address out and continually fill out form after form of name, website, captcha, login, etc. etc. then the conversation will simply be stifled and die.  I&#8217;m sure <strong>nobody</strong> wants that.</p>
<p>This video is a great contribution the bigger picture though! No doubt about that.  But it still falls short of being &#8220;right&#8221;, in my opinion.</p>
<p>* UPDATE* : P.S.  In trying to post my comment here I&#8217;ve been given a hard time by your commenting system already. It harks right back to everything I was illustrating about the conversation eventually being stifled&#8230; Note my inability to simply post my comment as &#8220;Matt&#8221;, cuz that&#8217;s my name, but heaven forbid the system think I&#8217;m trying to impersonate another &#8220;Matt&#8221;&#8230;  lol. ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
