<?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: Why Twitter Should Worry about Seesmic&#8217;s Acquisition of Ping.FM</title>
	<atom:link href="http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/feed/" rel="self" type="application/rss+xml" />
	<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/</link>
	<description>Computer Science meets Social Science</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:10:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Official Apple iPhone 4 Video- New Design Display and Video Chat &#171; Silicon Angle TV</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-25637</link>
		<dc:creator>Official Apple iPhone 4 Video- New Design Display and Video Chat &#171; Silicon Angle TV</dc:creator>
		<pubDate>Tue, 31 Aug 2010 09:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-25637</guid>
		<description>[...] Why Twitter Should Worry about Seesmic&#8217;s Acquisition of Ping.FM (101) [...]</description>
		<content:encoded><![CDATA[<p>[...] Why Twitter Should Worry about Seesmic&rsquo;s Acquisition of Ping.FM (101) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-18959</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Thu, 13 May 2010 11:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-18959</guid>
		<description>twitter vs ping!

&lt;a href=&quot;http://www.speaker.nu&quot; rel=&quot;nofollow&quot;&gt;telefonförsäljning&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>twitter vs ping!</p>
<p><a href="http://www.speaker.nu" rel="nofollow">telefonförsäljning</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Seesmic With Ping.fm Attractive For A Twitter Acquisition? &#124; Skeptic Geek</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-11707</link>
		<dc:creator>Is Seesmic With Ping.fm Attractive For A Twitter Acquisition? &#124; Skeptic Geek</dc:creator>
		<pubDate>Tue, 12 Jan 2010 06:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-11707</guid>
		<description>[...] bought Ping.fm enabling status updates across 50 social networks. Mark Hopkins elaborated on why this is a threat to [...]</description>
		<content:encoded><![CDATA[<p>[...] bought Ping.fm enabling status updates across 50 social networks. Mark Hopkins elaborated on why this is a threat to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Essel</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-11064</link>
		<dc:creator>Mark Essel</dc:creator>
		<pubDate>Tue, 05 Jan 2010 11:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-11064</guid>
		<description>Excellent post.
What we&#039;re seeing is a decentralization but connected real time update system emerging. Individually businesses are motivated by self interests to replicate real time status connection.

Twitter may have been the first technological evolution of the nervous system on the Net (there are arguable precursors), but technology has quickly replicated to other locations. The standard is in place for updates, reads, searches, etc.

As independent developers, can we assume interconnectivity of statuses between nearly all services in the coming years? I think so, and likely with a variant of the twitter API as it is currently implemented.</description>
		<content:encoded><![CDATA[<p>Excellent post.<br />
What we&#8217;re seeing is a decentralization but connected real time update system emerging. Individually businesses are motivated by self interests to replicate real time status connection.</p>
<p>Twitter may have been the first technological evolution of the nervous system on the Net (there are arguable precursors), but technology has quickly replicated to other locations. The standard is in place for updates, reads, searches, etc.</p>
<p>As independent developers, can we assume interconnectivity of statuses between nearly all services in the coming years? I think so, and likely with a variant of the twitter API as it is currently implemented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: modemlooper</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-10938</link>
		<dc:creator>modemlooper</dc:creator>
		<pubDate>Tue, 05 Jan 2010 04:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-10938</guid>
		<description>LMHO! I read your bio &quot;former editor at Mashable&quot; then read this anti-twitter post and said no wonder your a former editor since Cashmore has his tongue so far up Twitter&#039;s a** he can taste the rainbow.</description>
		<content:encoded><![CDATA[<p>LMHO! I read your bio &#8220;former editor at Mashable&#8221; then read this anti-twitter post and said no wonder your a former editor since Cashmore has his tongue so far up Twitter&#8217;s a** he can taste the rainbow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Furrier</title>
		<link>http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/comment-page-1/#comment-10883</link>
		<dc:creator>John Furrier</dc:creator>
		<pubDate>Mon, 04 Jan 2010 23:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/01/04/why-twitter-should-worry-about-seesmics-acquisition-of-ping-fm/#comment-10883</guid>
		<description>Seesmic was a video commenting company that raised a boatload of cash and they were failing bad.  Then they bought twhirl and combined with the Twitter explosion saved the company.  

Some VCs need to learn from this in that if you&#039;re going to give a company lots of Series A and B financing make sure it&#039;s enough to capture or jump on a growth curve.  Seesmic is a great example of them dumping Plan A and B and going with Plan C.  That is why I always argue that it&#039;s helpful to keep the founder around because of that creativity and vision often leads the entrepreneur in the right area.  

Either raise very little or more than enough to arbitrage the market.</description>
		<content:encoded><![CDATA[<p>Seesmic was a video commenting company that raised a boatload of cash and they were failing bad.  Then they bought twhirl and combined with the Twitter explosion saved the company.  </p>
<p>Some VCs need to learn from this in that if you&#8217;re going to give a company lots of Series A and B financing make sure it&#8217;s enough to capture or jump on a growth curve.  Seesmic is a great example of them dumping Plan A and B and going with Plan C.  That is why I always argue that it&#8217;s helpful to keep the founder around because of that creativity and vision often leads the entrepreneur in the right area.  </p>
<p>Either raise very little or more than enough to arbitrage the market.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

