<?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/"
	xmlns:media="http://search.yahoo.com/mrss/">

<channel>
	<title>Open Parenthesis &#187; Group</title>
	<atom:link href="http://www.openparenthesis.org/tag/group/feed" rel="self" type="application/rss+xml" />
	<link>http://www.openparenthesis.org</link>
	<description>Because these are the early days of a long revolution . . .</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:13:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>ReTweeter 0.9.1 Released</title>
		<link>http://www.openparenthesis.org/2009/02/10/retweeter-091-released</link>
		<comments>http://www.openparenthesis.org/2009/02/10/retweeter-091-released#comments</comments>
		<pubDate>Tue, 10 Feb 2009 16:22:48 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[Group]]></category>
		<category><![CDATA[microblog]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[ReTweet]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.openparenthesis.org/?p=1062</guid>
		<description><![CDATA[Photo by Andrea Mercado Thanks to Karen Huffman (@slakm) who raised some issues she was having with an installation of ReTweeter, I&#8217;ve tracked down the bug and uploaded and released 0.9.1. Turns out that in late December of 2008, the Twitter API servers started sending a 417 Status Code response to many clients, including ReTweeter. [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_1063" class="wp-caption alignright" style="width: 275px"><a href="http://www.flickr.com/photos/prettydaisies/476136116/"><img src="http://www.openparenthesis.org/wp-content/uploads/2009/02/tweet.jpg" alt="Photo by Andrea Mercado" title="tweet" width="240" height="180" class="size-full wp-image-1063" /></a><p class="wp-caption-text">Photo by Andrea Mercado</p></div>
<p>Thanks to <a href="http://www.linkedin.com/in/khuffman">Karen Huffman</a> (<a href="http://twitter.com/slakm">@slakm</a>) who raised some issues she was having with an installation of <a href="/code/twitter-api">ReTweeter</a>, I&#8217;ve tracked down the bug and uploaded and released 0.9.1. </p>
<p>Turns out that in late December of 2008, the Twitter API servers started sending a 417 Status Code response to many clients, including ReTweeter. (See Alex Payne&#8217;s <a href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/7be3b64970874fdd">announcement</a> on the Twitter API Google Group and <a href="http://groups.google.com/group/twitter-development-talk/msg/e94b88b5d8dc87ce">this message from Tom Morris</a> which identified the necessary fix for CURL based clients). </p>
<p>In addition to squashing that bug, this update also better handles error responses from the Twitter API in general, which is to say it actually identifies to the user what status code was returned to enable better troubleshooting. </p>
<p>Remember to copy your settings from your old version before overwriting with the new. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.openparenthesis.org/2009/02/10/retweeter-091-released/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
	<enclosure url="http://www.openparenthesis.org/wp-content/uploads/2009/02/tweet.jpg" length="19574" type="image/jpeg" /><media:content url="http://www.openparenthesis.org/wp-content/uploads/2009/02/tweet.jpg" width="240" height="180" medium="image" type="image/jpeg" />	</item>
	</channel>
</rss>

