Hey Mike,
Sorry to hear you were having problems there. If the credentials were being
rejected we would have returned an X-Warning header in the response letting
you know.
There is more information about this in our rate limiting documentation:
https://dev.twitter.com/docs/rate-limiting#rest
We are aware rate limits are being reported incorrectly. We are tracking the
issue on the API tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1728
Matt
On Tue, Jul 6, 2010 at 10:10 AM, Johnson wrote:
> I want to know what's the metrics of this dynamic logout.
> I have several twi
Just a sidenote: This can be coincidental. Unless you try several dozen times
with each client, no valid inference can be drawn from the tests.
Pascal
On Jul 6, 2010, at 18:46 , Johnson wrote:
> I notice that the rate limit is application specific. I've tried a few
> clients, some of them goes t
We're looking into this rate limiting issue.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, Jul 6, 2010 at 7:45 AM, Jeff Randall wrote:
> On Jul 6, 9:23 am, "M. Edward (Ed) Borasky" research.net> wrote:
> > Quoting artesea :
> >
> > > Finally have access again,
Quoting artesea :
Finally have access again, with the time to reset now at 15:27 (around
an hour).
Ryan
Ouch - sounds like my IP address got blocked then.
Speaking of rate limiting, I was trying to learn the Twitter API and
Net::Twitter by making "six degrees of twitter" that would figure out
how many hops it was from Account A to Account B when I ran up against
limiting.
The way I had thought of doing it was basically the list of whom a
person
You probably wouldn't use the streaming API 20k times/hr. You would
open one connection and consume data from it during that hour.
---Mark
http://twitter.com/mccv
On Sun, Jan 3, 2010 at 12:15 AM, Joel Hughes wrote:
> Hi all,
> thanks for your responses.
>
> John, I did take a look at the
