<?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 Details SXSW Traffic Preparation Measures</title>
	<atom:link href="http://www.centernetworks.com/twitter-sxsw/feed" rel="self" type="application/rss+xml" />
	<link>http://www.centernetworks.com/twitter-sxsw</link>
	<description>Web 2 and Social Media News and Reviews</description>
	<lastBuildDate>Sat, 21 Nov 2009 01:50:56 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-16591</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-16591</guid>
		<description>Thank god Alex stopped blaming Rails as being the scalability roadblock to Twitter.</description>
		<content:encoded><![CDATA[<p>Thank god Alex stopped blaming Rails as being the scalability roadblock to Twitter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KwangErn</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-16592</link>
		<dc:creator>KwangErn</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-16592</guid>
		<description>Twitter is definitely one step closer to IRC 2.0 ;D</description>
		<content:encoded><![CDATA[<p>Twitter is definitely one step closer to IRC 2.0 ;D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grendel</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-16765</link>
		<dc:creator>Grendel</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-16765</guid>
		<description>It&#039;s always amusing to watch those who don&#039;t understand enterprise-scale architecture try to slap bandaids around the outside of the huge, bleeding wound. I can&#039;t think of a worse architecture for what is essentially a messaging platform. Maybe in Twitter 2.0 they can replace it with cans and strings.</description>
		<content:encoded><![CDATA[<p>It&#8217;s always amusing to watch those who don&#8217;t understand enterprise-scale architecture try to slap bandaids around the outside of the huge, bleeding wound. I can&#8217;t think of a worse architecture for what is essentially a messaging platform. Maybe in Twitter 2.0 they can replace it with cans and strings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Cascio</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-17035</link>
		<dc:creator>Joe Cascio</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17035</guid>
		<description>Just a question/suggestion. It would help my app make fewer requests if I could get more than 100 records in result sets. As it is, to get all followers or following I have to sit in a loop hitting the API time after time to get a complete result. Not sure if this would help overall cycles needed, but it would certainly help web hits.
</description>
		<content:encoded><![CDATA[<p>Just a question/suggestion. It would help my app make fewer requests if I could get more than 100 records in result sets. As it is, to get all followers or following I have to sit in a loop hitting the API time after time to get a complete result. Not sure if this would help overall cycles needed, but it would certainly help web hits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Booth</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-17036</link>
		<dc:creator>Nick Booth</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17036</guid>
		<description>It&#039;s astonishing that one event is big enough to prompt them to address capacity.</description>
		<content:encoded><![CDATA[<p>It&#8217;s astonishing that one event is big enough to prompt them to address capacity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.centernetworks.com/twitter-sxsw/comment-page-#comment-17038</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-17038</guid>
		<description>Nick, SXSW is essentially why Twitter is successful. Last year, Twitter was relatively obscure until Leo Laporte and Robert Scoble promoted like crazy at SXSW.

I still don&#039;t quite understand Twitter but that&#039;s ok. I&#039;m still curious about whether or not young people who grew up with IM, MySpace, Twitter actually use it (I&#039;m a college student and I see absolutely no use for it).</description>
		<content:encoded><![CDATA[<p>Nick, SXSW is essentially why Twitter is successful. Last year, Twitter was relatively obscure until Leo Laporte and Robert Scoble promoted like crazy at SXSW.</p>
<p>I still don&#8217;t quite understand Twitter but that&#8217;s ok. I&#8217;m still curious about whether or not young people who grew up with IM, MySpace, Twitter actually use it (I&#8217;m a college student and I see absolutely no use for it).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
