<?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>The Future of the Internet -- And How to Stop It &#187; twitter</title>
	<atom:link href="http://futureoftheinternet.org/category/twitter/feed" rel="self" type="application/rss+xml" />
	<link>http://futureoftheinternet.org</link>
	<description>Jonathan Zittrain is Professor of Law at Harvard Law School and co-founder of the Berkman Center for Internet and Society at Harvard Law School</description>
	<lastBuildDate>Mon, 08 Mar 2010 23:09:35 +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>Breaking the 140 barrier</title>
		<link>http://futureoftheinternet.org/breaking-the-140-barrier</link>
		<comments>http://futureoftheinternet.org/breaking-the-140-barrier#comments</comments>
		<pubDate>Thu, 25 Jun 2009 03:09:02 +0000</pubDate>
		<dc:creator>jz</dc:creator>
				<category><![CDATA[Future of the Internet]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://futureoftheinternet.org/?p=792</guid>
		<description><![CDATA[Twitter only allows 140 characters per tweet.  The founders explain that they expected interconnection with mobile phone text messaging &#8212; SMS &#8212; from the start, and that it could be expensive to have longer tweets broken into mutiple messages when people pay per SMS.  As Dom Sagolla explains:
Messages longer than 160 characters (the common SMS [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter only allows 140 characters per tweet.  The founders explain that they expected interconnection with mobile phone text messaging &#8212; SMS &#8212; from the start, and that it could be expensive to have longer tweets broken into mutiple messages when people pay per SMS.  As <a href="http://twitter.com/dom">Dom Sagolla</a> <a href="http://www.140characters.com/2009/01/30/how-twitter-was-born/">explains</a>:</p>
<p style="padding-left: 30px;">Messages longer than 160 characters (the common SMS carrier limit) were split into multiple texts and delivered (somewhat) sequentially. There were other bugs, and a mounting SMS bill. The team decided to place a limit on the number of characters that would go out via SMS for each post. They settled on 140, in order to leave room for the username and the colon in front of the message.</p>
<p>Of course, 140 characters is now part of the lore and essence of Twitter.  It&#8217;s as sacrosanct as McDonald&#8217;s having two arches (despite starting with only one) or a Swiss Army knife folding up.  (An <a href="http://blog.shortyawards.com/post/92658703/twitter-fools-day">April Fool&#8217;s joke</a> had the company appearing to offer &#8220;Twitter Premium&#8221; with 160 characters and 50,000 instant followers.)</p>
<p>But there could be good reason to stretch the limit &#8212; or allow for a slightly more nuanced set of data behind a tweet &#8212; and not just because 140 characters <a href="http://qifanabki.com/2009/06/17/twitter-140-character-limit-foils-major-breakthrough-in-iran-election-controversy/">might cut off key information</a> (to be sure, an Onion-ey link) and have only half a thought re-tweeted before it&#8217;s fully completed.  In fact, the &#8220;retweet&#8221; &#8212; expressed as &#8220;RT @[source] [source's original tweet]&#8221; &#8212; is a great case study on why.  As <a href="http://www.danah.org">danah boyd</a> et al <a href="http://www.danah.org/papers/TweetTweetRetweet.pdf">explain</a>, retweeting is one of several &#8220;behavioral conventions&#8221; arising from Twitter users themselves.  Twitter itself does not have a special &#8220;RT&#8221; functionality; it&#8217;s just two letters that many people have come to use to say that they&#8217;re repeating something they saw elsewhere &#8212; and giving attribution for it.</p>
<p>With the 140 character limit, though, the &#8220;RT&#8221; and attribution have to fit too.  An original tweet that&#8217;s already near the limit will have to be shortened for it to work.  And if someone retweets further, the cycle continues.  Danah &amp; Co. have some great examples in their draft of ways in which that retweeting can inadvertently distort or even negate the original message.</p>
<p>Twitter has already shown a willingness to adopt users&#8217; conventions.  The use of @___ at the beginning of a tweet to communicate with a user became so common that it made sense for Twitter to put a special link on each user&#8217;s home Twitter page to view &#8220;@replies&#8221; from others.  For retweeting, Twitter could choose not to count RT @___ against the 140 character limit.  That could cause some tweets to be truncated when forwarded to SMS, or divided into two messages, which was an original reason why the limit was adopted.  But that might be worth it at this point.  Or, Twitter could start implementing metadata for tweets.  Already it records a timestamp and source for a tweet (since people can inject tweets into the system in so many different ways, not just at twitter.com.)  Retweets could become part of that metadata, not necessarily fully transmitted as part of the full message itself.  That way, the 140 character limit could be maintained, but people could still follow the genealogy of an idea, right back to its source &#8212; just the way that the &#8220;in-reply-to&#8221; link on twitter.com lets someone unravel an entire conversation with just a click.  And being able to lengthen a tweet in special circumstances could, if applied to URLs, also help avoid the need for <a href="http://en.wikipedia.org/wiki/URL_shortening#Criticism">the risky phenomenon of URL shorteners</a>. <strong>[Update 10 August 2009: <a href="http://tr.im">tr.im</a> just <a href="http://www.msnbc.msn.com/id/32363898/ns/tech_and_science-tech_and_gadgets/">announced it is folding</a>; shortened links will work for awhile but not forever.]</strong></p>
<p>Twitter is a foundational technology.  By that I don&#8217;t mean it&#8217;s (necessarily) revolutionary, just that it&#8217;s a building block.  Its open APIs <a href="http://futureoftheinternet.org/could-iran-shut-down-twitter">allow</a> it to be baked into all sorts of other services, and like other <a href="http://yupnet.org/zittrain/archives/13#1">foundational technologies</a> &#8212; say, <a href="http://yupnet.org/zittrain/archives/13#6">PC operating systems</a>, or <a href="http://yupnet.org/zittrain/archives/13#5">Internet protocol</a> &#8212; it&#8217;s evolving comparatively slowly.  Even MediaWiki, the software behind Wikipedia, hasn&#8217;t changed all that quickly.  Too much is built on top of it, both technologically and in users&#8217; practices, to change it hastily.  So that&#8217;s one reason just to let it sit as is.  But by giving a little more breathing space for attribution &#8212; to let people more readily build on others&#8217; ideas through retweeting &#8212; Twitter could help assure an even wider spectrum of use, even if its founders <a href="http://www.theonion.com/content/news_briefs/twitter_creator_on_iran_i?utm_source=a-section">didn&#8217;t happen to think</a> it could be used so comprehensively or seriously.</p>
]]></content:encoded>
			<wfw:commentRss>http://futureoftheinternet.org/breaking-the-140-barrier/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
