<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Beware: Twitter updated their API a&#160;bit</title>
	<atom:link href="http://cdevroe.com/notes/twitter-json-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://cdevroe.com/notes/twitter-json-update/</link>
	<description>Personal thoughts and notes.</description>
	<pubDate>Fri, 21 Nov 2008 21:53:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Ben Ward</title>
		<link>http://cdevroe.com/notes/twitter-json-update/#comment-26255</link>
		<dc:creator>Ben Ward</dc:creator>
		<pubDate>Thu, 29 Mar 2007 16:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://cdevroe.com/notes/twitter-json-update/#comment-26255</guid>
		<description>Ah yes, this has mildly broken &lt;a href="http://ben-ward.co.uk/widgets/twitgit" rel="nofollow"&gt;Twitgit&lt;/a&gt; as well. I was doing a crude comparison of the relative_created_at string between tweets and only outputting a â€˜5 minutes agoâ€™ header when the value changed â€”Â producing rather nicer grouping.

Thankfully JavaScript handles it in a fairly graceful way and the header now just reads â€˜undefinedâ€™ followed by all 20 tweets, which sure beats the whole thing falling over.

There's an update to Twitgit in occasional development at the moment, although the pressure's on 'cause the Twitterific guys have pulled off a blinder with v2, and have every single feature I want in Twitgit, bar it being a widgetâ€¦</description>
		<content:encoded><![CDATA[<p>Ah yes, this has mildly broken <a href="http://ben-ward.co.uk/widgets/twitgit" rel="nofollow">Twitgit</a> as well. I was doing a crude comparison of the relative_created_at string between tweets and only outputting a â€˜5 minutes agoâ€™ header when the value changed â€”Â producing rather nicer grouping.</p>
<p>Thankfully JavaScript handles it in a fairly graceful way and the header now just reads â€˜undefinedâ€™ followed by all 20 tweets, which sure beats the whole thing falling over.</p>
<p>There&#8217;s an update to Twitgit in occasional development at the moment, although the pressure&#8217;s on &#8217;cause the Twitterific guys have pulled off a blinder with v2, and have every single feature I want in Twitgit, bar it being a widgetâ€¦</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Devroe</title>
		<link>http://cdevroe.com/notes/twitter-json-update/#comment-26248</link>
		<dc:creator>Colin Devroe</dc:creator>
		<pubDate>Thu, 29 Mar 2007 15:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://cdevroe.com/notes/twitter-json-update/#comment-26248</guid>
		<description>Stuart:  Yeah, I should have mentioned that it has been changed throughout any of their public outputs.  Good point.</description>
		<content:encoded><![CDATA[<p>Stuart:  Yeah, I should have mentioned that it has been changed throughout any of their public outputs.  Good point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://cdevroe.com/notes/twitter-json-update/#comment-26247</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Thu, 29 Mar 2007 15:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://cdevroe.com/notes/twitter-json-update/#comment-26247</guid>
		<description>That's also happening on the xml output too so I'll be having to update tweetyPy asap.</description>
		<content:encoded><![CDATA[<p>That&#8217;s also happening on the xml output too so I&#8217;ll be having to update tweetyPy asap.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
