<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Including Everything Blog &#187; TweetDeck</title>
	<atom:link href="http://includingeverything.net/tag/tweetdeck/feed/" rel="self" type="application/rss+xml" />
	<link>http://includingeverything.net</link>
	<description>A blog dedicated to and including everything</description>
	<lastBuildDate>Mon, 30 Nov 2009 19:04:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Should Twitter offer a paid service?</title>
		<link>http://includingeverything.net/general/should-twitter-offer-a-paid-service/</link>
		<comments>http://includingeverything.net/general/should-twitter-offer-a-paid-service/#comments</comments>
		<pubDate>Wed, 26 Nov 2008 19:09:38 +0000</pubDate>
		<dc:creator>Will</dc:creator>
				<category><![CDATA[General Posts]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[TweetDeck]]></category>
		<category><![CDATA[Tweetie]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Twitter API]]></category>
		<category><![CDATA[TwitterBerry]]></category>
		<category><![CDATA[Twitterific]]></category>

		<guid isPermaLink="false">http://includingeverything.net/?p=143</guid>
		<description><![CDATA[submit_url = 'http://includingeverything.net/general/should-twitter-offer-a-paid-service/';Recently I&#8217;ve had the opportunity to play around with Twitter API and several services/software pieces that integrate with Twitter.  Until recently, I hadn&#8217;t run into any issues with the limitations of the Twitter API and how many connections a user is allowed access to in a given window of time.
So why couldn&#8217;t Twitter [...]]]></description>
			<content:encoded><![CDATA[<p><div style="float:left; margin: 0px 10px 5px 0px;"><script type="text/javascript">submit_url = 'http://includingeverything.net/general/should-twitter-offer-a-paid-service/';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script></div>Recently I&#8217;ve had the opportunity to play around with Twitter API and several services/software pieces that integrate with Twitter.  Until recently, I hadn&#8217;t run into any issues with the limitations of the Twitter API and how many connections a user is allowed access to in a given window of time.</p>
<p>So why couldn&#8217;t Twitter release a premium level of its service that grants paid users a greater level of access to the platform, additional features, more API connections, etc?  This seems the logical next step.  The main service would remain free as it always had (even I didn&#8217;t need to upgrade until now), but a handful of the Twitter power users would benefit from near-real-time Twitter updates with applications such as TweetDeck and mobile devices for the iPhone or BlackBerry such as Tweetie, Twitterific and TwitterBerry.</p>
<p>Here is some simple math that I&#8217;ve worked out.  The numbers seem fairly reasonable so far and I welcome comments on this model.  TwitDir reports 3,328,420 twitterers that they know as of today.  I&#8217;ll use this as the base number for my calculation.  If we estimate that there are 3.3 million Twitterers out there sharing ideas, and only 5% of them are power users that require a more powerful level of Twitter power (166,421), paying only $2.99/mo&#8230;</p>
<table border="0" cellspacing="0" cellpadding="0" width="248">
<col width="102"></col>
<col width="146"></col>
<tbody>
<tr height="20">
<td width="102" height="20"><strong>Users:</strong></td>
<td width="146">3,328,420</td>
</tr>
<tr height="20">
<td height="20"><strong>5% paying:</strong></td>
<td>166,421</td>
</tr>
<tr height="20">
<td height="20"><strong>$2.99/mo</strong></td>
<td><span style="color: #008000;">$497,598.79</span></td>
</tr>
<tr height="20">
<td height="20"><strong>$4.99/mo</strong></td>
<td><span style="color: #008000;">$830,440.79</span></td>
</tr>
</tbody>
</table>
<p><br/>That&#8217;s almost a half a million dollars of revenue for Twitter and all they had to do was scale up a few servers and spend a few hours coding the management/login area for users.  Hardly anything else needs to change.  The infrastructure has already been layed out and is operational.  If they wanted to, they could charge $4.99/mo for a different tier of service and offer other incentives to those users that required even more.</p>
<p>I&#8217;ve found myself leaving TweetDeck open on both my Mac (home) and Windows PC (work) and constantly use Tweetie on my iPhone.  There go all my API connections for the hour&#8230;they&#8217;re used up in about 30 minutes even with moderate usage.</p>
<p>The bottom line, would we pay for this service?  Is it so necessary to the way that we network now that users would jump into paying for it, or do we only use it now because it&#8217;s free?  My vote is for the same level of service to remain free, but offer additional options to their already-ginormous user base.</p>
<p>Comments welcome.</p>
<div style="float: left; width: 42px; padding-right: 10px; margin: 0 10px 0 0;">
		<script type="text/javascript">
		<!--
		digg_url = "http://includingeverything.net/general/should-twitter-offer-a-paid-service/";
		digg_bgcolor = "#FFFFFF";
		digg_skin = "";
		digg_window = "new";
		digg_title = "Should+Twitter+offer+a+paid+service%3F";
		digg_media = "news";
		digg_topic = "";
		digg_bodytext = "Recently I&#8217;ve had the opportunity to play around with Twitter API and several services/software pieces that integrate with Twitter.  Until recently, I hadn&#8217;t run into any issues with the limitations of the Twitter API and how many connections a user is allowed access to in a given window of time.So why couldn&#8217;t Twitter release a premium...";
		//-->
		</script>
		<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script></div><div style="clear:both;"></div>]]></content:encoded>
			<wfw:commentRss>http://includingeverything.net/general/should-twitter-offer-a-paid-service/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

