<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A call for twitter clients interoperability</title>
	<atom:link href="http://webtropic.cc/2009/04/17/a-call-for-twitter-clients-interoperability/feed/" rel="self" type="application/rss+xml" />
	<link>http://webtropic.cc/2009/04/17/a-call-for-twitter-clients-interoperability/</link>
	<description>Musings on social media, web technologies and start-ups.</description>
	<lastBuildDate>Fri, 23 Apr 2010 14:21:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Metablogging.gr &#187; Blog Archive &#187; Θεωρία twitter</title>
		<link>http://webtropic.cc/2009/04/17/a-call-for-twitter-clients-interoperability/#comment-384</link>
		<dc:creator>Metablogging.gr &#187; Blog Archive &#187; Θεωρία twitter</dc:creator>
		<pubDate>Sat, 04 Jul 2009 17:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://webtropic.cc/?p=439#comment-384</guid>
		<description>[...] A call for twitter clients interoperability [...]</description>
		<content:encoded><![CDATA[<p>[...] A call for twitter clients interoperability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ageor</title>
		<link>http://webtropic.cc/2009/04/17/a-call-for-twitter-clients-interoperability/#comment-380</link>
		<dc:creator>ageor</dc:creator>
		<pubDate>Fri, 19 Jun 2009 21:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://webtropic.cc/?p=439#comment-380</guid>
		<description>You have my vote!

Groups clearly need to be included in the platform, like in FriendFeed. As a second best choice, clients will talk to http://socialwhale.com/. Its twitter clone but extended API could potenially fill the void until, unavoidably Twitter meets the demand. I would leave interoperability to be the third choice, although maybe the most viable for now (if I remember correctly, SocialWhale has already announced TwitDeck groups import). 

It reminds me of the endless FFd wishlist until FFd met many of them with their new UI. Either twitter will follow or, yet again, suffer from its own success.</description>
		<content:encoded><![CDATA[<p>You have my vote!</p>
<p>Groups clearly need to be included in the platform, like in FriendFeed. As a second best choice, clients will talk to <a href="http://socialwhale.com/" rel="nofollow">http://socialwhale.com/</a>. Its twitter clone but extended API could potenially fill the void until, unavoidably Twitter meets the demand. I would leave interoperability to be the third choice, although maybe the most viable for now (if I remember correctly, SocialWhale has already announced TwitDeck groups import). </p>
<p>It reminds me of the endless FFd wishlist until FFd met many of them with their new UI. Either twitter will follow or, yet again, suffer from its own success.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
