<?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:go='http://ns.gigaom.com/'
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: How Twitter Could Crash and Burn</title>
	<atom:link href="http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/</link>
	<description></description>
	<lastBuildDate>Fri, 25 May 2012 20:12:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: djacobs</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72548</link>
		<dc:creator><![CDATA[djacobs]]></dc:creator>
		<pubDate>Thu, 05 Jun 2008 13:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72548</guid>
		<description><![CDATA[@yanis
Yes reliability is always an issue, but it shouldn&#039;t be a problem has it is with Twitter.]]></description>
		<content:encoded><![CDATA[<p>@yanis<br />
Yes reliability is always an issue, but it shouldn&#8217;t be a problem has it is with Twitter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72547</link>
		<dc:creator><![CDATA[Luke Hoersten]]></dc:creator>
		<pubDate>Thu, 05 Jun 2008 00:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72547</guid>
		<description><![CDATA[&lt;a href=&quot;http://twoorl.com&quot; rel=&quot;nofollow&quot;&gt;Twoorl&lt;/a&gt; is a cool Erlang twitter clone which is quite simple and very speedy! I hope my friends move there because you don&#039;t realize how slow twitter is until you try something else!]]></description>
		<content:encoded><![CDATA[<p><a href="http://twoorl.com" rel="nofollow">Twoorl</a> is a cool Erlang twitter clone which is quite simple and very speedy! I hope my friends move there because you don&#8217;t realize how slow twitter is until you try something else!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yanis</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72546</link>
		<dc:creator><![CDATA[yanis]]></dc:creator>
		<pubDate>Thu, 05 Jun 2008 00:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72546</guid>
		<description><![CDATA[djacobs,

Twitter has changed and evolved over time - it has moved into short messaging rather than short blogging.

And reliability is *always* an issue at some point for any rapidly growing service.]]></description>
		<content:encoded><![CDATA[<p>djacobs,</p>
<p>Twitter has changed and evolved over time &#8211; it has moved into short messaging rather than short blogging.</p>
<p>And reliability is *always* an issue at some point for any rapidly growing service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: djacobs</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72545</link>
		<dc:creator><![CDATA[djacobs]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 13:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72545</guid>
		<description><![CDATA[Reliability is an issue for Twitter, but that doesn&#039;t mean it&#039;s going to be an issue for any competition. In all honesty, it&#039;s a silly issue to have, especially with the technology that&#039;s available, it should have been scalable since day one. Some sort of redundancy should have been set in place, instead of having a single point of failure.]]></description>
		<content:encoded><![CDATA[<p>Reliability is an issue for Twitter, but that doesn&#8217;t mean it&#8217;s going to be an issue for any competition. In all honesty, it&#8217;s a silly issue to have, especially with the technology that&#8217;s available, it should have been scalable since day one. Some sort of redundancy should have been set in place, instead of having a single point of failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NatalieMac</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72544</link>
		<dc:creator><![CDATA[NatalieMac]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 05:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72544</guid>
		<description><![CDATA[Well, using a &quot;serious infrastructure&quot; like Amazon Web Services isn&#039;t going to work - that&#039;s what Twitter is already using.

Twitter and lots of other web services that all go down every time Amazon Web Services go down.]]></description>
		<content:encoded><![CDATA[<p>Well, using a &#8220;serious infrastructure&#8221; like Amazon Web Services isn&#8217;t going to work &#8211; that&#8217;s what Twitter is already using.</p>
<p>Twitter and lots of other web services that all go down every time Amazon Web Services go down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72543</link>
		<dc:creator><![CDATA[Brendan]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 02:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72543</guid>
		<description><![CDATA[The solution isn&#039;t actually that simple. Twitter isn&#039;t just a short messaging system any more - and folks just aren&#039;t grasping that.

Like the armchair experts claiming to have the answer to all the outage issues, they just don&#039;t take all of the factors into consideration.

It&#039;s API has created an entire sub-culture of applications and tools. If you seek to &quot;replace&quot; twitter then you either have to create the same kind of creative environment, or you risk simply becoming yet another footnote in the &quot;failed competition&quot; office pool.

Sure, Twitter isn&#039;t perfect. Reliability is a real issue - but the solutions to that aren&#039;t simply &quot;more horespower&quot;.

Anyone taking on Twitter needs to thoroughly understand what they have achieved thus far. And that isn&#039;t anywhere on your list.]]></description>
		<content:encoded><![CDATA[<p>The solution isn&#8217;t actually that simple. Twitter isn&#8217;t just a short messaging system any more &#8211; and folks just aren&#8217;t grasping that.</p>
<p>Like the armchair experts claiming to have the answer to all the outage issues, they just don&#8217;t take all of the factors into consideration.</p>
<p>It&#8217;s API has created an entire sub-culture of applications and tools. If you seek to &#8220;replace&#8221; twitter then you either have to create the same kind of creative environment, or you risk simply becoming yet another footnote in the &#8220;failed competition&#8221; office pool.</p>
<p>Sure, Twitter isn&#8217;t perfect. Reliability is a real issue &#8211; but the solutions to that aren&#8217;t simply &#8220;more horespower&#8221;.</p>
<p>Anyone taking on Twitter needs to thoroughly understand what they have achieved thus far. And that isn&#8217;t anywhere on your list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tiffany</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72542</link>
		<dc:creator><![CDATA[tiffany]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 01:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72542</guid>
		<description><![CDATA[keep in mind that many people have accounts on plurk, twitter and pownce. many of my twitter friends are also hardcore pownce users. pownce is where they share files. twitter is where they chitchat.

i think plurk is in a good spot right now. for me, it&#039;s slightly more complex than twitter, but not too much so. i just wish they&#039;d divorce it from the browser and the computer. half of my twitters are SMS on the go.]]></description>
		<content:encoded><![CDATA[<p>keep in mind that many people have accounts on plurk, twitter and pownce. many of my twitter friends are also hardcore pownce users. pownce is where they share files. twitter is where they chitchat.</p>
<p>i think plurk is in a good spot right now. for me, it&#8217;s slightly more complex than twitter, but not too much so. i just wish they&#8217;d divorce it from the browser and the computer. half of my twitters are SMS on the go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: djacobs</title>
		<link>http://gigaom.com/collaboration/how-twitter-could-crash-and-burn/#comment-72541</link>
		<dc:creator><![CDATA[djacobs]]></dc:creator>
		<pubDate>Tue, 03 Jun 2008 20:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=2477#comment-72541</guid>
		<description><![CDATA[I was looking into. The most difficult part is finding a way to make revenue. But as you can easily tell, social networks have a hard time creating revenue. If a site like Twitter claims to get a huge portion of it&#039;s traffic (heard 90%) from it&#039;s API service, it&#039;s going to make it hard to monetize ads.]]></description>
		<content:encoded><![CDATA[<p>I was looking into. The most difficult part is finding a way to make revenue. But as you can easily tell, social networks have a hard time creating revenue. If a site like Twitter claims to get a huge portion of it&#8217;s traffic (heard 90%) from it&#8217;s API service, it&#8217;s going to make it hard to monetize ads.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

