<?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>TweetMeme Blog &#187; Programming</title>
	<atom:link href="http://blog.tweetmeme.com/category/programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tweetmeme.com</link>
	<description>Finding what is hot on twitter</description>
	<lastBuildDate>Sun, 22 Nov 2009 19:04:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Michael Jackson top stories on twitter</title>
		<link>http://blog.tweetmeme.com/2009/06/25/michael-jackson-top-stories-on-twitter/</link>
		<comments>http://blog.tweetmeme.com/2009/06/25/michael-jackson-top-stories-on-twitter/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 22:52:18 +0000</pubDate>
		<dc:creator>Sarah Blow</dc:creator>
				<category><![CDATA[Channels]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[michael jackson]]></category>
		<category><![CDATA[mj]]></category>

		<guid isPermaLink="false">http://blog.tweetmeme.com/2009/06/25/michael-jackson-top-stories-on-twitter/</guid>
		<description><![CDATA[

This evening whilst at a roller disco (don&#8217;t ask!) i heard the news that Michael Jackson had been taken to hospital and early reports were pronouncing him dead.
In order to keep up with the stories and what was becoming news I went back to the Michael Jackson channel that I creates to follow the news [...]]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img zemanta-action-dragged" style="margin: 1em; display: block;">
<div class="wp-caption alignleft" style="width: 157px"><a href="http://commons.wikipedia.org/wiki/Image:Michael_Jackson_1984.jpg"><img title="Michael Jackson, cropped from :Image:Michael J..." src="http://upload.wikimedia.org/wikipedia/commons/0/04/Michael_Jackson_1984.jpg" alt="Michael Jackson, cropped from :Image:Michael J..." width="147" height="224" /></a><p class="wp-caption-text">Image via Wikipedia</p></div>
</div>
<p>This evening whilst at a roller disco (don&#8217;t ask!) i heard the news that Michael Jackson had been taken to hospital and early reports were pronouncing him dead.</p>
<p>In order to keep up with the stories and what was becoming news I went back to the Michael Jackson channel that I creates to follow the news around his concerts. No surprise but it&#8217;s now starting to fill up with the latest confirmed and unconfirmed stories.</p>
<p>Keep up to date with it here: <a href="http://michaeljackson.tweetmeme.com">Michael Jackson Channel</a></p>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweetmeme.com/2009/06/25/michael-jackson-top-stories-on-twitter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tweetmeme API</title>
		<link>http://blog.tweetmeme.com/2009/03/04/tweetmeme-api/</link>
		<comments>http://blog.tweetmeme.com/2009/03/04/tweetmeme-api/#comments</comments>
		<pubDate>Wed, 04 Mar 2009 17:15:17 +0000</pubDate>
		<dc:creator>Nick Halstead</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[restful]]></category>
		<category><![CDATA[tweetmeme]]></category>

		<guid isPermaLink="false">http://blog.tweetmeme.com/?p=57</guid>
		<description><![CDATA[The twitter firehose is a LOT of data, TweetMeme spends it&#8217;s life sifting through finding all the URL&#8217;s resolving millions of shortened URL&#8217;s (e.g. http://bit.ly, http://tinyurl.com) in the process. Once resolved we go grab the title of the story, and also do a lot of clever stuff to get images/videos + the body of text [...]]]></description>
			<content:encoded><![CDATA[<p>The twitter firehose is a <strong>LOT</strong> of data, <a href="http://www.tweetmeme.com">TweetMeme</a> spends it&#8217;s life sifting through finding all the URL&#8217;s resolving millions of shortened URL&#8217;s (e.g. http://bit.ly, http://tinyurl.com) in the process. Once resolved we go grab the title of the story, and also do a lot of clever stuff to get images/videos + the body of text (i.e. the description of the story).</p>
<p>We thought it would be useful to expose this data via a set of API calls which developers could use to improve their twitter applications who do not wish the massive burden of processing all the data that TweetMeme does.</p>
<p>From Today we launch 3 simple methods that expose a small part of our dataset, these will hopefully be followed by more that allows data-mining around the unique resolved-stories dataset we have.</p>
<p>If you want to dive straight into the technical description please go visit our <a href="http://www.tweetmeme.com/apidoc.php">API page</a></p>
<p>The three calls we have exposed so far are,</p>
<ul>
<li>url_info &#8211; This allows developers to take any URL posted to twitter and get back the title, category, tweet count, date posted and the resolved URL.
<li>
<li>recent &#8211; Grabs the most <strong>recent</strong> stories from Tweetmeme</li>
<li>popular &#8211; Grabs the most <strong>popular</strong> stories from Tweetmeme</li>
</ul>
<p>If you wish to get updates on further developers follow <a href="http://www.twitter.com/tweetmemedev">tweetmemedev</a> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweetmeme.com/2009/03/04/tweetmeme-api/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
