Re: How to find out how many API requests have been used?
Thank you.
On Dec 4, 11:00 am, Alex Payne [EMAIL PROTECTED] wrote:
We do limit the number of updates a client can send over a period time
to prevent spammers. That time period may change, and the number of
updates one can post is much higher than most uses would dictate, but
if you really need to be posting that frequently, please apply for
whitelisting to lift the limit:http://twitter.com/help/request_whitelisting.
On Wed, Dec 3, 2008 at 18:17, maximz2005 [EMAIL PROTECTED] wrote:
Today, I've increased the time interval to two minutes, and so far, I
think it's working without problems with posting.
I've just set the interval to 1 minute, do you think it will give me
posting problems?
On Dec 2, 10:13 pm, maximz2005 [EMAIL PROTECTED] wrote:
So if I increased this time interval to a minute or two, do you think
posting would work?
Thanks,
-maximz2005
On Dec 1, 8:57 pm, Cameron Kaiser [EMAIL PROTECTED] wrote:
Do you by any chance know whether updatingstatuscounts against the
rate limit?
It does not.
I wrote a little test program for playing around with the API, that
simply posts the time as astatusmessageevery 30 seconds.
Sometimes, when I go online and check thestatusmessages, they stop
abruptly, but the client doesn't give me a 404 error. Is this evidence
of reaching the limit?
No, it just means it wasn't posted. However, a test like that being
posted
out every 30 seconds over and over could be construed as a runaway bot to
be filtered. You might not want to constantly update that frequently.
--
personal:http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems [EMAIL PROTECTED]
-- I like my women like my coffee: weak, cold and bitter. -- Kevin
Metcalf
--
Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: How to find out how many API requests have been used?
We do limit the number of updates a client can send over a period time to prevent spammers. That time period may change, and the number of updates one can post is much higher than most uses would dictate, but if you really need to be posting that frequently, please apply for whitelisting to lift the limit: http://twitter.com/help/request_whitelisting. On Wed, Dec 3, 2008 at 18:17, maximz2005 [EMAIL PROTECTED] wrote: Today, I've increased the time interval to two minutes, and so far, I think it's working without problems with posting. I've just set the interval to 1 minute, do you think it will give me posting problems? On Dec 2, 10:13 pm, maximz2005 [EMAIL PROTECTED] wrote: So if I increased this time interval to a minute or two, do you think posting would work? Thanks, -maximz2005 On Dec 1, 8:57 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: Do you by any chance know whether updatingstatuscounts against the rate limit? It does not. I wrote a little test program for playing around with the API, that simply posts the time as astatusmessageevery 30 seconds. Sometimes, when I go online and check thestatusmessages, they stop abruptly, but the client doesn't give me a 404 error. Is this evidence of reaching the limit? No, it just means it wasn't posted. However, a test like that being posted out every 30 seconds over and over could be construed as a runaway bot to be filtered. You might not want to constantly update that frequently. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems [EMAIL PROTECTED] -- I like my women like my coffee: weak, cold and bitter. -- Kevin Metcalf -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: How to find out how many API requests have been used?
So if I increased this time interval to a minute or two, do you think posting would work? Thanks, -maximz2005 On Dec 1, 8:57 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: Do you by any chance know whether updatingstatuscounts against the rate limit? It does not. I wrote a little test program for playing around with the API, that simply posts the time as astatusmessageevery 30 seconds. Sometimes, when I go online and check thestatusmessages, they stop abruptly, but the client doesn't give me a 404 error. Is this evidence of reaching the limit? No, it just means it wasn't posted. However, a test like that being posted out every 30 seconds over and over could be construed as a runaway bot to be filtered. You might not want to constantly update that frequently. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* [EMAIL PROTECTED] -- I like my women like my coffee: weak, cold and bitter. -- Kevin Metcalf
Re: How to find out how many API requests have been used?
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!
Re: How to find out how many API requests have been used?
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!
Re: How to find out how many API requests have been used?
Do you by any chance know whether updating status counts against the rate limit? It does not. 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? No, it just means it wasn't posted. However, a test like that being posted out every 30 seconds over and over could be construed as a runaway bot to be filtered. You might not want to constantly update that frequently. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- I like my women like my coffee: weak, cold and bitter. -- Kevin Metcalf
