<?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 is Broken! (UPDATE 3)</title>
	<atom:link href="http://www.seanstoner.com/blog/2008/04/21/twitter-is-broken/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seanstoner.com/blog/2008/04/21/twitter-is-broken/</link>
	<description>My irreverent musings on the nature of things . . . .</description>
	<lastBuildDate>Sun, 22 Aug 2010 19:04:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Christine</title>
		<link>http://www.seanstoner.com/blog/2008/04/21/twitter-is-broken/comment-page-1/#comment-436</link>
		<dc:creator>Christine</dc:creator>
		<pubDate>Mon, 28 Apr 2008 21:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.seanstoner.com/blog/2008/04/19/twitter-is-broken/#comment-436</guid>
		<description>You have no incentive to make it work if it is free.  That is the down side to all of us relying on something that is free to use.  It is ironic that it is quite similar to issues that Blogger had years ago (like in 2000) when they couldn&#039;t keep the servers running properly.

Sad, but true.  I guess we get what we pay for ....</description>
		<content:encoded><![CDATA[<p>You have no incentive to make it work if it is free.  That is the down side to all of us relying on something that is free to use.  It is ironic that it is quite similar to issues that Blogger had years ago (like in 2000) when they couldn&#8217;t keep the servers running properly.</p>
<p>Sad, but true.  I guess we get what we pay for &#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.seanstoner.com/blog/2008/04/21/twitter-is-broken/comment-page-1/#comment-310</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sun, 20 Apr 2008 04:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.seanstoner.com/blog/2008/04/19/twitter-is-broken/#comment-310</guid>
		<description>Twitter always has this problem after performing any kind of maintenance, and yet they apparently don&#039;t have the foresight to have someone monitoring their support channel on getsatisfaction.com. It took over nine hours before they bother to post a note saying they are aware of the problem, when, no doubt, the problem has been ongoing since last night&#039;s maintenance. Also, they failed to update the twitter_status account *again*. They keep having the same &quot;display issues&quot; over and over, even if the reasons are different, and never appear to learn how to be more aggressively handle customer service.</description>
		<content:encoded><![CDATA[<p>Twitter always has this problem after performing any kind of maintenance, and yet they apparently don&#8217;t have the foresight to have someone monitoring their support channel on getsatisfaction.com. It took over nine hours before they bother to post a note saying they are aware of the problem, when, no doubt, the problem has been ongoing since last night&#8217;s maintenance. Also, they failed to update the twitter_status account *again*. They keep having the same &#8220;display issues&#8221; over and over, even if the reasons are different, and never appear to learn how to be more aggressively handle customer service.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

