<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: twhirl and the Twitter API rate limit</title>
	<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/</link>
	<description>notes on twhirl, AIR, Flex, RIA and web development</description>
	<pubDate>Fri, 21 Nov 2008 17:29:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: thomasknoll</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-485</link>
		<dc:creator>thomasknoll</dc:creator>
		<pubDate>Wed, 27 Aug 2008 23:05:57 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-485</guid>
		<description>Compulsiveguile,

I believe what you are experiencing is the result of a new API change by twitter, that we have a solution for and will be releasing very soon. Unfortunately, the only current way to work around this, is to set up twhirl to open links in your browser, and then do your following, deleting, favoriting from the website. But we'll have a fix fairly soon.</description>
		<content:encoded><![CDATA[<p>Compulsiveguile,</p>
<p>I believe what you are experiencing is the result of a new API change by twitter, that we have a solution for and will be releasing very soon. Unfortunately, the only current way to work around this, is to set up twhirl to open links in your browser, and then do your following, deleting, favoriting from the website. But we&#8217;ll have a fix fairly soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: compulsiveguile</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-484</link>
		<dc:creator>compulsiveguile</dc:creator>
		<pubDate>Wed, 27 Aug 2008 07:46:00 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-484</guid>
		<description>Does anyone have a definitive solution to the whole "limit exceeded" message? I can't follow anyone new through Twhirl because of this stupid API issue. 

Please help! If you have any solutions, please email me!</description>
		<content:encoded><![CDATA[<p>Does anyone have a definitive solution to the whole &#8220;limit exceeded&#8221; message? I can&#8217;t follow anyone new through Twhirl because of this stupid API issue. </p>
<p>Please help! If you have any solutions, please email me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What&#8217;s [Not] Up With Twitter Today? &#124; netZoo.net &#124; WOOZradio</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-417</link>
		<dc:creator>What&#8217;s [Not] Up With Twitter Today? &#124; netZoo.net &#124; WOOZradio</dc:creator>
		<pubDate>Mon, 07 Jul 2008 14:21:03 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-417</guid>
		<description>[...] users have grown accustomed to daily instances of &#8220;stress,&#8221; &#8220;overload,&#8221; faulty API limits exceeded, and random appearances of the now infamous fail whale. Many have forecast the demise of [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] users have grown accustomed to daily instances of &#8220;stress,&#8221; &#8220;overload,&#8221; faulty API limits exceeded, and random appearances of the now infamous fail whale. Many have forecast the demise of [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed S (NextInstinct)</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-407</link>
		<dc:creator>Ed S (NextInstinct)</dc:creator>
		<pubDate>Tue, 01 Jul 2008 18:13:25 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-407</guid>
		<description>Has Twitter communicated with you at all yet? 

I hope the VC's and suits don't push them from 
cool social geeks to insular, and unfocu$ed.</description>
		<content:encoded><![CDATA[<p>Has Twitter communicated with you at all yet? </p>
<p>I hope the VC&#8217;s and suits don&#8217;t push them from<br />
cool social geeks to insular, and unfocu$ed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shelly</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-406</link>
		<dc:creator>shelly</dc:creator>
		<pubDate>Tue, 01 Jul 2008 05:21:15 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-406</guid>
		<description>A "hide" button for Friendfeed would be brilliant. *nods*

Meanwhile, I'd also love to see Plurk integration at some point. *nods*</description>
		<content:encoded><![CDATA[<p>A &#8220;hide&#8221; button for Friendfeed would be brilliant. *nods*</p>
<p>Meanwhile, I&#8217;d also love to see Plurk integration at some point. *nods*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Thoughts &#124; Twitter is Taking Too Long To Respond</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-403</link>
		<dc:creator>Mike Thoughts &#124; Twitter is Taking Too Long To Respond</dc:creator>
		<pubDate>Fri, 27 Jun 2008 15:54:08 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-403</guid>
		<description>[...] right now because the limit on requests is so low it just takes too long to stay up to date. twhirl announced this morning that Twitter is messing with something that threw off their auto-leveling requests to the Twitter [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] right now because the limit on requests is so low it just takes too long to stay up to date. twhirl announced this morning that Twitter is messing with something that threw off their auto-leveling requests to the Twitter [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Do The Fail Whale &#171; NDNL</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-402</link>
		<dc:creator>Do The Fail Whale &#171; NDNL</dc:creator>
		<pubDate>Fri, 27 Jun 2008 15:01:20 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-402</guid>
		<description>[...] Twitter also changed the request for replies on its API so that third-party apps like Twhirl don&#8217;t work anymore either. That leaves us [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Twitter also changed the request for replies on its API so that third-party apps like Twhirl don&#8217;t work anymore either. That leaves us [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edd Dumbill</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-401</link>
		<dc:creator>Edd Dumbill</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:52:01 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-401</guid>
		<description>Maybe you could use the downtime to sneak some more FriendFeed features in? I'm jonesing for the "Hide" button.

Thanks for thwirl and keep up the good work. I paid for Twitterific, but seem to be spending all my time in thwirl.</description>
		<content:encoded><![CDATA[<p>Maybe you could use the downtime to sneak some more FriendFeed features in? I&#8217;m jonesing for the &#8220;Hide&#8221; button.</p>
<p>Thanks for thwirl and keep up the good work. I paid for Twitterific, but seem to be spending all my time in thwirl.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Buckbee</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-400</link>
		<dc:creator>Michael Buckbee</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:37:55 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-400</guid>
		<description>I've had my requests set to 10/hr for the last week and it seems that I'm still constantly in the "limit exceeded pausing 5 minutes" status. 

At this point Twhirl is near useless due to API limitations.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had my requests set to 10/hr for the last week and it seems that I&#8217;m still constantly in the &#8220;limit exceeded pausing 5 minutes&#8221; status. </p>
<p>At this point Twhirl is near useless due to API limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-399</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:02:35 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/06/27/twhirl-and-the-twitter-api-rate-limit/#comment-399</guid>
		<description>Coding Monkeys are weak, The super fu ninja's can get this straightened out faster.</description>
		<content:encoded><![CDATA[<p>Coding Monkeys are weak, The super fu ninja&#8217;s can get this straightened out faster.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
