<?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: Twitter Gets A Can Of Site Downtime Whoopassss</title>
	<atom:link href="http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/</link>
	<description>redesign the world</description>
	<lastBuildDate>Mon, 21 Nov 2011 14:09:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Blogging Goodness from the World of Paulus &#187; Blog Archive &#187; Visual impact: Twitter doesn&#8217;t get it</title>
		<link>http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/comment-page-1/#comment-265</link>
		<dc:creator>Blogging Goodness from the World of Paulus &#187; Blog Archive &#187; Visual impact: Twitter doesn&#8217;t get it</dc:creator>
		<pubDate>Sat, 06 Dec 2008 23:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/#comment-265</guid>
		<description>[...] is immensely popular but with a lot moaning and groaning behind the scenes. Number one gripe among users, observers and critics is downtime. It seems that the popularity was not expected and therefore the architecture is no match for the [...]</description>
		<content:encoded><![CDATA[<p>[...] is immensely popular but with a lot moaning and groaning behind the scenes. Number one gripe among users, observers and critics is downtime. It seems that the popularity was not expected and therefore the architecture is no match for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Beermann</title>
		<link>http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/comment-page-1/#comment-165</link>
		<dc:creator>Dale Beermann</dc:creator>
		<pubDate>Fri, 27 Jun 2008 14:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.annoyingdesign.org/blog/2008/06/26/twitter-gets-a-can-of-site-downtime-whoopassss/#comment-165</guid>
		<description>I was thinking about this yesterday while participating in a Twebinar (www.twebinar.com).  Twitter&#039;s Replies feature is down, as is their tracking feature, which makes it really hard to have a conversation (impossible, in fact, using Twitter alone).  Without services like Summize and third party apps like Twhirl, I think that a lot more people would be moving to other services and it would be hard to see Twitter succeeding at all.

But, and this confirms the importance of the current debate on &quot;who owns your friends,&quot; people already have networks of friends on Twitter and nobody wants to rebuild that.  So instead, the conversation during the Twebinar happened on Twitter, with people using one Summize window to track the Twebinar conversations, another to track replies to your own comments, and then either the Twitter website or a third party app to actually respond.</description>
		<content:encoded><![CDATA[<p>I was thinking about this yesterday while participating in a Twebinar (www.twebinar.com).  Twitter&#8217;s Replies feature is down, as is their tracking feature, which makes it really hard to have a conversation (impossible, in fact, using Twitter alone).  Without services like Summize and third party apps like Twhirl, I think that a lot more people would be moving to other services and it would be hard to see Twitter succeeding at all.</p>
<p>But, and this confirms the importance of the current debate on &#8220;who owns your friends,&#8221; people already have networks of friends on Twitter and nobody wants to rebuild that.  So instead, the conversation during the Twebinar happened on Twitter, with people using one Summize window to track the Twebinar conversations, another to track replies to your own comments, and then either the Twitter website or a third party app to actually respond.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

