<?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>dtsn &#187; TweetTabs</title>
	<atom:link href="http://dtsn.co.uk/category/tweettabs/feed/" rel="self" type="application/rss+xml" />
	<link>http://dtsn.co.uk</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 17 Aug 2010 13:18:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TweetTabs &amp; @Anywhere</title>
		<link>http://dtsn.co.uk/2010/07/14/tweettabs-anywhere/</link>
		<comments>http://dtsn.co.uk/2010/07/14/tweettabs-anywhere/#comments</comments>
		<pubDate>Wed, 14 Jul 2010 19:52:11 +0000</pubDate>
		<dc:creator>daniel</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[TweetTabs]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[dtsn]]></category>
		<category><![CDATA[@Anywhere]]></category>

		<guid isPermaLink="false">http://dtsn.co.uk/?p=787</guid>
		<description><![CDATA[<div class="tweetmeme_button" style="float: right; margin: 3px 0px 0px 10px;">
			<br />
				<br />
			
		</div>
<p><em>This was presented at Devnest 9</em>&#8230;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin: 3px 0px 0px 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdtsn.co.uk%2F2010%2F07%2F14%2Ftweettabs-anywhere%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif&amp;source=dtsn&amp;style=normal&amp;service=is.gd&amp;hashtags=%40Anywhere,TweetTabs&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><em>This was presented at <a href="http://twitterdevelopernest.com/2010/05/devnest-%E2%80%93-london-twitter-developer-nest-9/">Devnest 9</a></em></p>
<p>Developers of Twitter probably heard of @Anywhere when it was launched at Chirp, it includes componants which will enhanch a web page. Which for twitter increases the engagement for their users. These componants are cool, but hardly anything to get excitited about. @Anywhere contains a fantastic secret underneth it&#8217;s hood and thats a fully JS-API. Thats right a method to interface with the Twitter API entirely in JavaScript. This is because @Anywhere provides the means to authenticate a user via OAuth using their new Twitter Connect window.</p>
<p>Authenticated users can achieve a lot more using the API, therefore the JS-API now lets you practically do anything that the regular API can. This is really exciting because it means that i can finally turn TweetTabs into a fully Twitter client built entirely in JavaScript.</p>
<p>Here&#8217;s a quick example of how easy it is to post a status update using @Anywhere:</p>
<pre name="code" class="js">
twttr.anywhere(function(T) {
if (T.isConnected()) {
T.status.Update(‘hello world’);
}
});
</pre>
<p>You can find a lot more information regarding @Anywhere over on the <a href="http://dev.twitter.com/anywhere">@Anywhere dev page</a>. You can also get a full list of <a href="http://platform.twitter.com/js-api.html">support methods</a>.</p>
<h2>TweetTabs</h2>
<p>So how does this all fit in with TweetTabs? Quite simply TweetTabs was never quite finished, i always intended it to be a fully Twitter Client and not just the search client that it became, this is because Twitter at the time of writing TweetTabs didn&#8217;t support any methods of OAuth through JavaScript. But now it does, so i&#8217;ve implemented it.</p>
<p>You can check out a very alpha version (which is my proof of concept) at <a href="http://beta.tweettabs.com">http://beta.tweettabs.com</a>. Please give feedback, I fully intend on integrating @Anywhere fully into TweetTabs.</p>
<h2>Downsides</h2>
<p>The real big problem with the JS-API part of @Anywhere is that it is not supported (at all), there is very little documentation and most of it has changed since it was released. So it really is down to trial and error!</p>
<h2>Slides</h2>
<p>Here are the slides from the talk.</p>
<p><object id="__sse4716451" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="355" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=dtsn-devnest9-100709020920-phpapp02&amp;rel=0&amp;stripped_title=dtsn-devnest9" /><param name="name" value="__sse4716451" /><param name="allowfullscreen" value="true" /><embed id="__sse4716451" type="application/x-shockwave-flash" width="425" height="355" src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=dtsn-devnest9-100709020920-phpapp02&amp;rel=0&amp;stripped_title=dtsn-devnest9" name="__sse4716451" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://dtsn.co.uk/2010/07/14/tweettabs-anywhere/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TweetTabs, A Story</title>
		<link>http://dtsn.co.uk/2009/06/17/tweettabs-a-story/</link>
		<comments>http://dtsn.co.uk/2009/06/17/tweettabs-a-story/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 22:09:51 +0000</pubDate>
		<dc:creator>daniel</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Prototype]]></category>
		<category><![CDATA[TweetTabs]]></category>

		<guid isPermaLink="false">http://dtsn.co.uk/?p=574</guid>
		<description><![CDATA[<div class="tweetmeme_button" style="float: right; margin: 3px 0px 0px 10px;">
			<br />
				<br />
			
		</div>
<p>For everyone who follows me on&#8230;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin: 3px 0px 0px 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdtsn.co.uk%2F2009%2F06%2F17%2Ftweettabs-a-story%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif&amp;source=dtsn&amp;style=normal&amp;service=is.gd&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>For everyone who follows me on twitter or knows me personally would know that yesterday I launched something that i have been working on for a very long time. <a href="http://tweettabs.com">TweetTabs</a> is a way of tracking real-time twitter trends and searches, and has been my little project since i first started on it back in Easter. The idea came from the lack on online real-time ways to interface with twitter, the premise is simple, i wanted an easy way to search for things in twitter which constantly updated, so TweetTabs was born. </p>
<p>The initial application was written in about 2 hours entirely in JavaScript, it later went through a number of huge revisions especially over the Easter weekend. It gained quite a lot of features, and then lost them. I wrote an entire OAuth module in JavaScript, then realised that you can’t authenticate headers. The project was basically done apart from one of the most complicated features. Then my life changed, I broke up with my long term girlfriend, of 5 years, and had to move back home with my parents. Even though this didn’t dent my enthusiasm for the project it definitely affected the timescales.</p>
<h2>How it works</h2>
<p><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://dtsn.co.uk/wp-content/uploads/2009/06/image-thumb.png" width="480" height="310" /></p>
<p>TweetTabs is a very simple idea, but it takes a very long time to solve the problems it presents. The entire application is written in JavaScript, this gets around the notion of having a API limit for your twitter searches, you are now only limited by your I.P. address, which has a much higher (not declared) limit. For every tab TweetTab hits twitter to fetch the data, this is controlled by our adaptive pollrate. Put simply this means that each tab can work out the optimum time to fetch more data from twitter. We try and limit the number of times TweetTabs hits twitter in the hour, mostly so that you don&#8217;t reach your API limit (it is possible, and I did it a lot in testing), and we don&#8217;t overload twitter.</p>
<p> <object width="480" height="360"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=5208057&amp;server=vimeo.com&amp;show_title=0&amp;show_byline=0&amp;show_portrait=0&amp;color=00ADEF&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=5208057&amp;server=vimeo.com&amp;show_title=0&amp;show_byline=0&amp;show_portrait=0&amp;color=00ADEF&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="480" height="360"></embed></object>
<p><a href="http://vimeo.com/5208057">TweetTabs Screencast</a> from <a href="http://vimeo.com/user546294">Daniel Saxil-Nielsen</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
<h2>Coverage</h2>
<p>So now TweetTabs has been launched and has had loads of positive feedback and has been covered on loads of huge sites:</p>
<ul>
<li><a title="http://www.techcrunch.com/2009/06/16/tweettabs-is-an-awesome-way-to-search-twitter/" href="http://www.techcrunch.com/2009/06/16/tweettabs-is-an-awesome-way-to-search-twitter/">http://www.techcrunch.com/2009/06/16/tweettabs-is-an-awesome-way-to-search-twitter/</a> </li>
<li><a title="http://mashable.com/2009/06/16/tweettabs/" href="http://mashable.com/2009/06/16/tweettabs/">http://mashable.com/2009/06/16/tweettabs/</a> </li>
</ul>
<h2>Dedications</h2>
<p>I don’t know whether this is normally done for releasing products, but I feel it is appropriate, I would like to mention everyone who helped with the process along the way. Starting firstly with <a href="http://twitter.com/nickhalstead" target="_blank">@nickhalstead</a>, who supported me the whole way (and sorry it took so long). <a href="http://twitter.com/nicktelford" target="_blank">@nicktelford</a> who was there to bounce ideas of and to find lots of bugs just before we were about the launch. <a href="http://twitter.com/alexforrow" target="_blank">@alexforrow</a> for writing a really good deployment script, which merges all the files and obfuscates them. All the great people that tested it along the way: <a href="http://twitter.com/chris_alexander" target="_blank">@chris_alexander</a>, <a href="http://twitter.com/craigyd" target="_blank">@craigyd</a>, <a href="http://twitter.com/amykate" target="_blank">@amykate</a> and <a href="http://twitter.com/girlygeekdom" target="_blank">@girlygeekdom</a> (who is probably the one who answers <a href="http://twitter.com/tweettabs" target="_blank">@tweettabs</a> questions online). </p>
<p>TweetTabs is built using <a href="http://prototypejs.org" target="_blank">Prototype</a> and the JavaScript framework, and is powered by <a href="http://tweetmeme.com">TweetMeme</a>, and <a href="http://twitter.com" target="_blank">Twitter</a>.     </p>
]]></content:encoded>
			<wfw:commentRss>http://dtsn.co.uk/2009/06/17/tweettabs-a-story/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

