<?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: Twitter API Lowers Authenticated Request Limit to 30 Per Hour</title>
	<atom:link href="http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/feed/" rel="self" type="application/rss+xml" />
	<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/</link>
	<description>Not just another WordPress weblog</description>
	<pubDate>Fri, 21 Nov 2008 03:40:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Anis</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-9399</link>
		<dc:creator>Anis</dc:creator>
		<pubDate>Thu, 06 Nov 2008 04:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-9399</guid>
		<description>It has long been looking for this information, Thank you for your work.</description>
		<content:encoded><![CDATA[<p>It has long been looking for this information, Thank you for your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-279</link>
		<dc:creator>Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 10 Jun 2008 12:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-279</guid>
		<description>[...] and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble [...]</description>
		<content:encoded><![CDATA[<p>[...] and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: twhirl and Other Twitter Clients Exceeding Usage Limits &#124; Will Johnston &#124; Mind Muse</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-238</link>
		<dc:creator>twhirl and Other Twitter Clients Exceeding Usage Limits &#124; Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 27 May 2008 01:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-238</guid>
		<description>[...] Twitter&#8217;s recent change to their API means that your favorite Twitter client might not be working properly.  My (not personally verified) understanding is that the IM clients (GTalk, AIM, etc.) aren&#8217;t working at all right now, and many people have been reporting problems with twhirl.  Typically the user receives a message stating &#8220;limit exceeded&#8221; or something to that effect. [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter&#8217;s recent change to their API means that your favorite Twitter client might not be working properly.  My (not personally verified) understanding is that the IM clients (GTalk, AIM, etc.) aren&#8217;t working at all right now, and many people have been reporting problems with twhirl.  Typically the user receives a message stating &#8220;limit exceeded&#8221; or something to that effect. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Smith</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-237</link>
		<dc:creator>Paul Smith</dc:creator>
		<pubDate>Tue, 27 May 2008 00:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-237</guid>
		<description>Thanks much for this. I was going nuts with the near constant over limit messages on Twhirl! Despite my patience being tested, I'm staying. It's worth it, overall, for the people, the connections, the new knowledge. Wish I knew coding and could help!</description>
		<content:encoded><![CDATA[<p>Thanks much for this. I was going nuts with the near constant over limit messages on Twhirl! Despite my patience being tested, I&#8217;m staying. It&#8217;s worth it, overall, for the people, the connections, the new knowledge. Wish I knew coding and could help!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
