Thank you. This is not in the C# library I'm using, but I'll configure it manually.
Do you by any chance know whether updating status counts against the rate limit? I wrote a little test program for playing around with the API, that simply posts the time as a status message every 30 seconds. Sometimes, when I go online and check the status messages, they stop abruptly, but the client doesn't give me a 404 error. Is this evidence of reaching the limit? I will try and check this using the method you pointed out, but if you by any chance know the answer to this question, help would be appreciated. -Maximz2005 On Dec 1, 8:23 pm, Cameron Kaiser <[EMAIL PROTECTED]> wrote: > > I started exploring the Twitter API in C# yesterday, and I have a > > question. Is it possible to find out how many requests out of the > > maximum 70 per hour have been already used up? Twhirl does this > > somehow, and they say that this counter will be the same in all > > Twitter applications, so I assume there's an API method for doing > > this. > > > I'm using the Yedda Twitter C# library, so you can just answer me with > > an API method name, and that'll work for me. > > I don't know anything about that particular library, but look at > > http://apiwiki.twitter.com/REST+API+Documentation > > under rate_limit_status. > > -- > ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [EMAIL PROTECTED] > -- Burglar alarms: For the man who has everything! > ----------------------------
