<?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>Broadcasting 2.0 &#187; 2009 &#187; July &#187; 08</title>
	<atom:link href="http://www.broadcasting20.org/2009/07/08/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.broadcasting20.org</link>
	<description>Emerging technologies for one-to-many telecommunications</description>
	<lastBuildDate>Mon, 22 Mar 2010 18:28:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Royalty-Free Public Domain &#8211; A path towards Ubiquity</title>
		<link>http://www.broadcasting20.org/2009/07/08/royalty-free-public-domain-a-path-towards-ubiquity/</link>
		<comments>http://www.broadcasting20.org/2009/07/08/royalty-free-public-domain-a-path-towards-ubiquity/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 20:04:01 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[Infrastructures]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[MMB]]></category>
		<category><![CDATA[patents]]></category>
		<category><![CDATA[publicdomain]]></category>
		<category><![CDATA[royalties]]></category>
		<category><![CDATA[royaltyfree]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.broadcasting20.org/2009/07/08/royalty-free-public-domain-a-path-towards-ubiquity/</guid>
		<description><![CDATA[I read this excellent story some time ago in Vanity Fair titled &#8220;An oral history of the Internet&#8220;. I believe that one of the reasons why the Internet is what it is now comes from the fact that the Web is a royalty-free technology. And that does not happen by itself. To produce RF-tech these [...]]]></description>
			<content:encoded><![CDATA[<p>I read this excellent story some time ago in Vanity Fair titled &#8220;<a href="http://www.vanityfair.com/culture/features/2008/07/internet200807">An oral history of the Internet</a>&#8220;. I believe that one of the reasons why the Internet is what it is now comes from the fact that the Web is a royalty-free technology. And that does not happen by itself. To produce RF-tech these days, one has got to fight for it and give up potential revenue streams. That is what the CERN team did. <strong>Robert Cailliau</strong> says<strong>:</strong></p>
<blockquote>
<p><i>&#8220;At one point</i> <span class="sc"><i>cern</i></span> <i>was toying with patenting the World Wide Web. I was talking about that with Tim one day, and he looked at me, and I could see that he wasn’t enthusiastic. He said, Robert, do you want to be rich? I thought, Well, it helps, no? He apparently didn’t care about that. What he cared about was to make sure that the thing would work, that it would just be there for everybody. He convinced me of that, and then I worked for about six months, very hard with the legal service, to make sure that</i> <span class="sc"><i>cern</i></span> <i>put the whole thing in the public domain.&#8221;</i></p>
</blockquote>
<p>The least we can say is that the strategy worked. The Web is now ubiquitous.</p>
<p>Is there a lesson here for creating the mobile broadcast system of tomorrow?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.broadcasting20.org/2009/07/08/royalty-free-public-domain-a-path-towards-ubiquity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Broadcasting the Twittersphere</title>
		<link>http://www.broadcasting20.org/2009/07/08/twitter-bandwidth/</link>
		<comments>http://www.broadcasting20.org/2009/07/08/twitter-bandwidth/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 05:14:19 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[Infrastructures]]></category>
		<category><![CDATA[User Generated Media]]></category>
		<category><![CDATA[broadcasting 2.0]]></category>
		<category><![CDATA[DAB]]></category>
		<category><![CDATA[datacasting]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[radio]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.broadcasting20.org/2009/07/08/twitter-bandwidth/</guid>
		<description><![CDATA[I think that Twitter and micro-blogging in general have properties that could be exploited along with broadcasting services. I’ll write my thoughts about this later on. As a first step in this reflexion, I’d like to estimate the total bandwidth of Twitter, that is, how many kilobits per second are being Tweeted on average. I [...]]]></description>
			<content:encoded><![CDATA[<p>I think that Twitter and micro-blogging in general have properties that could be exploited along with broadcasting services. I’ll write my thoughts about this later on.</p>
<p>As a first step in this reflexion, I’d like to estimate the total bandwidth of Twitter, that is, how many kilobits per second are being Tweeted on average.</p>
<p>I made a similar exercise some time ago with regards to the blogosphere in a post titled “<a href="http://www.broadcasting20.org/2006/03/13/broadcasting-the-blogosphere-30-million-voices-for-the-price-of-one-2/">Broadcasting the Blogosphere: 30 million voices for the price of one!</a>”.</p>
<p>So I found some twitter services that provide relevant data. For example, <a href="http://www.tweespeed.com/speeds.jsp?period=hour&amp;duration=168">TweeSpeed</a> is an instant speed meter that shows the current number of tweets per minute. A graph showing the speed per hour during the last week is also available. A quick look at that graph now suggests that 700.000 tweets per hour would be a reasonable approximation for last week’s average, excluding the peek caused by the “Michael Jackson Effect”. <a href="http://www.twitpocalypse.com/">Twitpocalypse</a> currently reports 221 tweets per second which results in a similar value (221*60*60 =795.600 tweets per hour ). On another front, the recent HubSpot <a href="http://blog.hubspot.com/Portals/249/sotwitter09.pdf">State of the Twittershpere</a> report provides similar amounts on a daily basis instead of per hour. I suspect that this is a mistake. I’ll be pessimistic and take the largest number. The Hubspot report also informs on the distribution of actual tweet length. I’ll average the tweet length to 110 characters per tweet.</p>
<p>So the math goes like this:</p>
<p style="text-align: center;">110ch * 1byte/ch * 700k/hour = 77 Mbytes/hour</p>
<p style="text-align: center;">or</p>
<p style="text-align: center;"><font size="5"><span style="font-size: 18px;">TOTAL TWITTER BANDWIDTH = 170 kbps !</span></font></p>
<p style="text-align: center;">
<div style="text-align: left;">
  Again, very surprising results! The current Twitter bandwidth is barely higher than a typical Internet or DAB radio station. The whole Twittershpere would only require to sacrifice a couple of off-air DAB stations in every market. I feel that very innovative datacasting/social applications could be built based on this!
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.broadcasting20.org/2009/07/08/twitter-bandwidth/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

