<?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: What We Now Know from the &#8220;Twitter Epic Tweet Scandal&#8221;</title>
	<atom:link href="http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/feed/" rel="self" type="application/rss+xml" />
	<link>http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/</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: Mark Dykeman</title>
		<link>http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/comment-page-1/#comment-14221</link>
		<dc:creator>Mark Dykeman</dc:creator>
		<pubDate>Thu, 04 Mar 2010 16:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/#comment-14221</guid>
		<description>Boy, I hope you are wrong.  I think you might be right.</description>
		<content:encoded><![CDATA[<p>Boy, I hope you are wrong.  I think you might be right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Braindead Techcast Ep. 17: From one end of stupid to the other end of stupid - SeanPAune.com</title>
		<link>http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/comment-page-1/#comment-14217</link>
		<dc:creator>The Braindead Techcast Ep. 17: From one end of stupid to the other end of stupid - SeanPAune.com</dc:creator>
		<pubDate>Thu, 04 Mar 2010 08:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/#comment-14217</guid>
		<description>[...] Merion spy-cam suit – Philly.com Israelis Nix Op After Facebook Fiasco – Wired: Danger Room What We Now Know from the “Twitter Epic Tweet Scandal” – SiliconANGLE Criminal Penalties Coming For US Internet Companies That Don’t Protect Human [...]</description>
		<content:encoded><![CDATA[<p>[...] Merion spy-cam suit – Philly.com Israelis Nix Op After Facebook Fiasco – Wired: Danger Room What We Now Know from the “Twitter Epic Tweet Scandal” – SiliconANGLE Criminal Penalties Coming For US Internet Companies That Don’t Protect Human [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Furrier</title>
		<link>http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/comment-page-1/#comment-14193</link>
		<dc:creator>John Furrier</dc:creator>
		<pubDate>Wed, 03 Mar 2010 22:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/#comment-14193</guid>
		<description>It is so clear to me the monetization path for twitter - it&#039;s so obvious and clear as day... developer community.  that is why they pulled back on Al3x&#039;s epic tweet in my opinion.  They really didn&#039;t want to disrupt the rebuilding of trust in the developer community.  

I think that MG should have done a better job not to use that tweet out of context knowing how much harm it would do to Twitters big developer event.. imo MG didn&#039;t need to disrupt twitter for pageviews - that&#039;s just me.  MG hangs with those guys and turns out might have hurt his trust with them.  If I was Twitter I&#039;d be pissed.

Also the irony is that twitter is asking people to use their product in social media and yet they are restricting their own people of using their own product.  Bizzare twist there.</description>
		<content:encoded><![CDATA[<p>It is so clear to me the monetization path for twitter &#8211; it&#8217;s so obvious and clear as day&#8230; developer community.  that is why they pulled back on Al3x&#8217;s epic tweet in my opinion.  They really didn&#8217;t want to disrupt the rebuilding of trust in the developer community.  </p>
<p>I think that MG should have done a better job not to use that tweet out of context knowing how much harm it would do to Twitters big developer event.. imo MG didn&#8217;t need to disrupt twitter for pageviews &#8211; that&#8217;s just me.  MG hangs with those guys and turns out might have hurt his trust with them.  If I was Twitter I&#8217;d be pissed.</p>
<p>Also the irony is that twitter is asking people to use their product in social media and yet they are restricting their own people of using their own product.  Bizzare twist there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kosso</title>
		<link>http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/comment-page-1/#comment-14189</link>
		<dc:creator>kosso</dc:creator>
		<pubDate>Wed, 03 Mar 2010 21:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://siliconangle.com/blog/2010/03/03/what-we-now-know-from-the-twitter-epic-tweet-scandal/#comment-14189</guid>
		<description>I was at the recent Twitter API developers meetup at Twtter HQ and naturally the subject of *that* tweet came up.

Here’s a video I recorded showing the ‘official’ response to all this, explaining what was meant and what we can expect to come:

http://tech.phreadz.com/x/3FAE09P30G3G/</description>
		<content:encoded><![CDATA[<p>I was at the recent Twitter API developers meetup at Twtter HQ and naturally the subject of *that* tweet came up.</p>
<p>Here’s a video I recorded showing the ‘official’ response to all this, explaining what was meant and what we can expect to come:</p>
<p><a href="http://tech.phreadz.com/x/3FAE09P30G3G/" rel="nofollow">http://tech.phreadz.com/x/3FAE09P30G3G/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

