<?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: Should I worry that Twitter.com has no obvious revenue model?</title>
	<atom:link href="http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/</link>
	<description>One foot in the muck, the other in utopia</description>
	<pubDate>Tue, 02 Dec 2008 11:28:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Ric</title>
		<link>http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/#comment-154970</link>
		<dc:creator>Ric</dc:creator>
		<pubDate>Mon, 25 Feb 2008 12:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/#comment-154970</guid>
		<description>I actually think that Twitter will/should be replaced by an XMPP product - hopefully itself, but Jabber is too good for this sort of thing to not be used ...</description>
		<content:encoded><![CDATA[<p>I actually think that Twitter will/should be replaced by an XMPP product - hopefully itself, but Jabber is too good for this sort of thing to not be used &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danno</title>
		<link>http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/#comment-154757</link>
		<dc:creator>Danno</dc:creator>
		<pubDate>Sun, 24 Feb 2008 23:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/02/24/should-i-worry-that-twittercom-has-no-obvious-revenue-model/#comment-154757</guid>
		<description>Meeehhh, I'm not worried.

If Twitter goes away, someone'll come up with something similar that works in a more distributed fashion, like, some sort of XMPP package that ties into a simple CMS.  The Twittering will just be redirected through a Jabber compatible chatting protocol or something.

Then, people will set up Twitter-clone providers and all the popular ones'll provide the same sort of update stream thing that lets the third parties hook in and do nifty things like reminders and other value added stuff.

That is to say, I don't think Twitter's value is in the service but in the idea.</description>
		<content:encoded><![CDATA[<p>Meeehhh, I&#8217;m not worried.</p>
<p>If Twitter goes away, someone&#8217;ll come up with something similar that works in a more distributed fashion, like, some sort of XMPP package that ties into a simple CMS.  The Twittering will just be redirected through a Jabber compatible chatting protocol or something.</p>
<p>Then, people will set up Twitter-clone providers and all the popular ones&#8217;ll provide the same sort of update stream thing that lets the third parties hook in and do nifty things like reminders and other value added stuff.</p>
<p>That is to say, I don&#8217;t think Twitter&#8217;s value is in the service but in the idea.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
