<?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: Pushing the limit</title>
	<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/</link>
	<description>notes on twhirl, AIR, Flex, RIA and web development</description>
	<pubDate>Wed, 23 Jul 2008 18:37:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Nick Wilsdon</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-384</link>
		<dc:creator>Nick Wilsdon</dc:creator>
		<pubDate>Fri, 20 Jun 2008 10:25:07 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-384</guid>
		<description>@JB 

I've improved the situation a bit in Twhirl by reducing the number of API calls it makes to 30/hr (under settings/network). That has stopped the content freezing. 

However I'm still missing some updates which are in the web site but not on the application so it's not 100% fixed. I still must be limited in the amount of data I can update Twhirl with.

As I said before, I only following a couple of hundred people so I'd guess those with higher follower numbers are loosing even more data. I know Twitter is not responsible for the applications, but this all has the effect of making the system appear very flaky (on top of the downtime). I've missed replies to me on a few occasions which isn't great for a communication platform.</description>
		<content:encoded><![CDATA[<p>@JB </p>
<p>I&#8217;ve improved the situation a bit in Twhirl by reducing the number of API calls it makes to 30/hr (under settings/network). That has stopped the content freezing. </p>
<p>However I&#8217;m still missing some updates which are in the web site but not on the application so it&#8217;s not 100% fixed. I still must be limited in the amount of data I can update Twhirl with.</p>
<p>As I said before, I only following a couple of hundred people so I&#8217;d guess those with higher follower numbers are loosing even more data. I know Twitter is not responsible for the applications, but this all has the effect of making the system appear very flaky (on top of the downtime). I&#8217;ve missed replies to me on a few occasions which isn&#8217;t great for a communication platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-345</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Mon, 09 Jun 2008 16:06:09 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-345</guid>
		<description>I am also not doing any of these things, and am getting paused all the time. I am not running another Twitter client. I minimally click on Twhirl buttons. I do all my looking-up on the web and not through Twhirl. I send 2 or 3 Tweets an hour, at most, and I get locked out constantly. It's making me pretty frustrated.</description>
		<content:encoded><![CDATA[<p>I am also not doing any of these things, and am getting paused all the time. I am not running another Twitter client. I minimally click on Twhirl buttons. I do all my looking-up on the web and not through Twhirl. I send 2 or 3 Tweets an hour, at most, and I get locked out constantly. It&#8217;s making me pretty frustrated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Wilsdon</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-337</link>
		<dc:creator>Nick Wilsdon</dc:creator>
		<pubDate>Thu, 05 Jun 2008 13:08:31 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-337</guid>
		<description>Sorry typo - meant a "couple of hundred people". I'm following 216 atm and none of them are high volume.</description>
		<content:encoded><![CDATA[<p>Sorry typo - meant a &#8220;couple of hundred people&#8221;. I&#8217;m following 216 atm and none of them are high volume.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Wilsdon</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-336</link>
		<dc:creator>Nick Wilsdon</dc:creator>
		<pubDate>Thu, 05 Jun 2008 13:07:43 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-336</guid>
		<description>&#62;Why does my twhirl say I exceeded the limit?

Sorry but this is complete rubbish. I'm not doing any of these things and the API limit is still pausing Twhirl every few minutes. Bottom line, this is happening if you follow a couple of people. Twitter have given everyone a very low API limit and have rendered Twhirl useless.</description>
		<content:encoded><![CDATA[<p>&gt;Why does my twhirl say I exceeded the limit?</p>
<p>Sorry but this is complete rubbish. I&#8217;m not doing any of these things and the API limit is still pausing Twhirl every few minutes. Bottom line, this is happening if you follow a couple of people. Twitter have given everyone a very low API limit and have rendered Twhirl useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Johnston &#124; Mind Muse</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-322</link>
		<dc:creator>Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 27 May 2008 01:54:07 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-322</guid>
		<description>&lt;strong&gt;twhirl Stop Working?  Here&#8217;s a Fix....&lt;/strong&gt;

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 peo...</description>
		<content:encoded><![CDATA[<p><strong>twhirl Stop Working?  Here&#8217;s a Fix&#8230;.</strong></p>
<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 peo&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Smith</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-321</link>
		<dc:creator>Paul Smith</dc:creator>
		<pubDate>Mon, 26 May 2008 06:38:46 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-321</guid>
		<description>This is a few weeks into Twitters frequent outage issues, those seem to have eased up, but I'm now getting this limit exceeded message multiple times a day, with no difference in my usage, not other clients, sometimes right after starting up. What's going on? Could it be because of FriendFeed?</description>
		<content:encoded><![CDATA[<p>This is a few weeks into Twitters frequent outage issues, those seem to have eased up, but I&#8217;m now getting this limit exceeded message multiple times a day, with no difference in my usage, not other clients, sometimes right after starting up. What&#8217;s going on? Could it be because of FriendFeed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 787c590b675d</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-286</link>
		<dc:creator>787c590b675d</dc:creator>
		<pubDate>Fri, 09 May 2008 08:53:21 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-286</guid>
		<description>&lt;strong&gt;787c590b675d...&lt;/strong&gt;

787c590b675d48033865...</description>
		<content:encoded><![CDATA[<p><strong>787c590b675d&#8230;</strong></p>
<p>787c590b675d48033865&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waarom Ik Niet Meer Kan &#8220;Tweeten&#8221; &#124; novoblog.be</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-183</link>
		<dc:creator>Waarom Ik Niet Meer Kan &#8220;Tweeten&#8221; &#124; novoblog.be</dc:creator>
		<pubDate>Mon, 14 Apr 2008 06:47:47 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-183</guid>
		<description>[...] Get Satisfaction loopt er al een discussie over dit probleem. Lees de uitleg over de limieten op de blog van [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Get Satisfaction loopt er al een discussie over dit probleem. Lees de uitleg over de limieten op de blog van [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-174</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Fri, 11 Apr 2008 15:09:45 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-174</guid>
		<description>What you say makes sense, except... I sometimes see 'limit exceeded' the first time I start twhirl in the morning, and the paused state persists for 15, 20 minutes... yeah. Not good. I have no browser extensions, no other clients, not left running at home, nothing. I don't doubt twhirl might be a victim rather than cause, but the explanation above doesn't account for what I see. Am I missing something?</description>
		<content:encoded><![CDATA[<p>What you say makes sense, except&#8230; I sometimes see &#8216;limit exceeded&#8217; the first time I start twhirl in the morning, and the paused state persists for 15, 20 minutes&#8230; yeah. Not good. I have no browser extensions, no other clients, not left running at home, nothing. I don&#8217;t doubt twhirl might be a victim rather than cause, but the explanation above doesn&#8217;t account for what I see. Am I missing something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crazy6108</title>
		<link>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-172</link>
		<dc:creator>crazy6108</dc:creator>
		<pubDate>Fri, 11 Apr 2008 06:26:30 +0000</pubDate>
		<guid>http://blog.twhirl.org/2008/01/04/pushing-the-limit/#comment-172</guid>
		<description>Wow! Cool news!Sounds a little weird, but interesting anyway. what do you guys think about it?</description>
		<content:encoded><![CDATA[<p>Wow! Cool news!Sounds a little weird, but interesting anyway. what do you guys think about it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
