<?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: Plurk, Twitter, BrightKite, Hellotxt, Ping.fm, FriendFeed et al can they work together?</title>
	<atom:link href="http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/</link>
	<description>Web standards, accessibility  and such like with a bias toward  Government web sites</description>
	<pubDate>Sat, 22 Nov 2008 08:55:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-37050</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Fri, 27 Jun 2008 01:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-37050</guid>
		<description>As for the MUCH LARGER picture (beyond Nickcowie.com), think about mimicing real-conversation, as those avoid interference organically.</description>
		<content:encoded><![CDATA[<p>As for the MUCH LARGER picture (beyond Nickcowie.com), think about mimicing real-conversation, as those avoid interference organically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-37048</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Fri, 27 Jun 2008 00:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-37048</guid>
		<description>Hmmm... So much to unravel.
Search engines solve everything.


:::: One search to unite them all ::::

Perhaps:

1) Design a search for post with "yourname/handle" &#38; reply:ondate.

2) Add-in a way to pull them all down (daily interval,) and there goes.

3) For the visitor, a cookie can remember searches.



Regarding content integrity: 
Design a tiered-comment system with expound on post or "sidebar" option.</description>
		<content:encoded><![CDATA[<p>Hmmm&#8230; So much to unravel.<br />
Search engines solve everything.</p>
<p>:::: One search to unite them all ::::</p>
<p>Perhaps:</p>
<p>1) Design a search for post with &#8220;yourname/handle&#8221; &amp; reply:ondate.</p>
<p>2) Add-in a way to pull them all down (daily interval,) and there goes.</p>
<p>3) For the visitor, a cookie can remember searches.</p>
<p>Regarding content integrity:<br />
Design a tiered-comment system with expound on post or &#8220;sidebar&#8221; option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Cowie &#187; Twitter, Plurk and FriendFeed as discussion tools.</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36326</link>
		<dc:creator>Nick Cowie &#187; Twitter, Plurk and FriendFeed as discussion tools.</dc:creator>
		<pubDate>Sat, 14 Jun 2008 16:30:56 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36326</guid>
		<description>[...] up from my previous post on Conversation vs Noise. This is about carrying out discussions, this is not about status updates like &#8220;I just had [...]</description>
		<content:encoded><![CDATA[<p>[...] up from my previous post on Conversation vs Noise. This is about carrying out discussions, this is not about status updates like &#8220;I just had [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Buchanan</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36309</link>
		<dc:creator>Ben Buchanan</dc:creator>
		<pubDate>Sat, 14 Jun 2008 08:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36309</guid>
		<description>I think we need an aggregation format that includes two key concepts:
1) Definitive source, and
2) Definitive/monitored comment location.

So, you could post on your blog and feed readers could provide a link back to the blog page for comments. You could post on twitter and other services could flag themselves as "comments not monitored" and link to Twitter. Or, we'll get a service which purely handles comments. So all other services can ingest the comments from that definitive source and display them in situ; replies go to the comment service (which just has to track a URI and comments to that URI).

I signed up for ping.fm the other day and found myself thinking... "no way am I going to monitor plurk for comments, i'm already watching twitter and pownce and a blog and flickr and livejournal and facebook and......."</description>
		<content:encoded><![CDATA[<p>I think we need an aggregation format that includes two key concepts:<br />
1) Definitive source, and<br />
2) Definitive/monitored comment location.</p>
<p>So, you could post on your blog and feed readers could provide a link back to the blog page for comments. You could post on twitter and other services could flag themselves as &#8220;comments not monitored&#8221; and link to Twitter. Or, we&#8217;ll get a service which purely handles comments. So all other services can ingest the comments from that definitive source and display them in situ; replies go to the comment service (which just has to track a URI and comments to that URI).</p>
<p>I signed up for ping.fm the other day and found myself thinking&#8230; &#8220;no way am I going to monitor plurk for comments, i&#8217;m already watching twitter and pownce and a blog and flickr and livejournal and facebook and&#8230;&#8230;.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36306</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 14 Jun 2008 06:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36306</guid>
		<description>I know, I was tempted to remove the standard comment form from this blog. But most people do not have a FriendFeed account. &lt;a href="http://disqus.com" rel="nofollow"&gt;Disqus&lt;/a&gt; was an option but I will stick with the old school method for the time being, that is what I expect most of the typical visitors to this blog expect.</description>
		<content:encoded><![CDATA[<p>I know, I was tempted to remove the standard comment form from this blog. But most people do not have a FriendFeed account. <a href="http://disqus.com" rel="nofollow">Disqus</a> was an option but I will stick with the old school method for the time being, that is what I expect most of the typical visitors to this blog expect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Brock</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36305</link>
		<dc:creator>Jordan Brock</dc:creator>
		<pubDate>Sat, 14 Jun 2008 05:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36305</guid>
		<description>I know ... in the end it's easier not to comment.

Actually, I had a moment's confusion when I was going to write the previous comment ... should I comment here, or on FriendFeed. All too confusing :)</description>
		<content:encoded><![CDATA[<p>I know &#8230; in the end it&#8217;s easier not to comment.</p>
<p>Actually, I had a moment&#8217;s confusion when I was going to write the previous comment &#8230; should I comment here, or on FriendFeed. All too confusing :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36302</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 14 Jun 2008 05:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36302</guid>
		<description>Jordan that is what I am talking about, the level of noise or echo from a single post. I managed to generate 36 entries in my &lt;a href="http://www.profilactic.com/mashup/nickobec" rel="nofollow"&gt;lifestream&lt;/a&gt; on &lt;a href="http://www.profilactic.com/" rel="nofollow"&gt;profilatic&lt;/a&gt; with 3 posts to ping.fm or hellotxt.

And the big question is where would you comment on @lu_lu#&#038;8217;s photo? Twitter or Flickr and would you miss any discussion carried out on Plurk, FriendFeed etc.</description>
		<content:encoded><![CDATA[<p>Jordan that is what I am talking about, the level of noise or echo from a single post. I managed to generate 36 entries in my <a href="http://www.profilactic.com/mashup/nickobec" rel="nofollow">lifestream</a> on <a href="http://www.profilactic.com/" rel="nofollow">profilatic</a> with 3 posts to ping.fm or hellotxt.</p>
<p>And the big question is where would you comment on @lu_lu#&#038;8217;s photo? Twitter or Flickr and would you miss any discussion carried out on Plurk, FriendFeed etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Brock</title>
		<link>http://nickcowie.com/2008/plurk-twitter-brightkite-hellotxt-pingfm-friendfeed-et-al-can-they-work-together/#comment-36298</link>
		<dc:creator>Jordan Brock</dc:creator>
		<pubDate>Sat, 14 Jun 2008 05:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=243#comment-36298</guid>
		<description>The problem that I have with ping.fm and the like, and in fact a lot of aggregators in general, is that if you follow a person on a number of services, then there's all of a sudden an incredible amount of noise being generated. Not to pick on @lu_lu in anyway, but the other day I saw the same mini-blog about a flickr photo she posted on Twitter, Plurk, Friendfeed (four times), her RSS feed and then my Flickr contacts feed. 

I can see the need for these services, but it's forcing me to choose one service to use as a consumer/friend, because otherwise I'm filtering out an incredible of noise. And currently, for me at least, it's looking like it's going to be twitter that wins.</description>
		<content:encoded><![CDATA[<p>The problem that I have with ping.fm and the like, and in fact a lot of aggregators in general, is that if you follow a person on a number of services, then there&#8217;s all of a sudden an incredible amount of noise being generated. Not to pick on @lu_lu in anyway, but the other day I saw the same mini-blog about a flickr photo she posted on Twitter, Plurk, Friendfeed (four times), her RSS feed and then my Flickr contacts feed. </p>
<p>I can see the need for these services, but it&#8217;s forcing me to choose one service to use as a consumer/friend, because otherwise I&#8217;m filtering out an incredible of noise. And currently, for me at least, it&#8217;s looking like it&#8217;s going to be twitter that wins.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
