In using the : http://twitter.com/account/rate_limit_status.format
command, there seems to be some inaccuracies. In testing when all the clients I've played with have told me my limit for the hour has been exceeded, when I try the API command it tells me I have Remaining Hits - 87. I've tried this a few times and it appears that when the API is exceeded, the remaining hit count is not displayed correctly, i.e. 0. Also is there some kind of lag. If I have Twhirl or Spaz open and post a few tweets, and then issue the API command, the remaining hits do not seem to go down accordingly. Any ideas? Colin