If you call rate_limit_status authenticated as yourself and return is greater then 100 then it is your account. You can also make the same call unauthenticated from the IP.
[1] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0rate_limit_status On Mon, Apr 27, 2009 at 11:07, Dossy Shiobara <do...@panoptic.com> wrote: > > On 4/27/09 11:25 AM, Matt Sanford wrote: > >> This is why we added the X-RateLimit-* headers, so you can check the >> status on the actual calls you perform and not need to make another >> call. Those should tell you your current limit when calling the ids >> method. >> > > OK, I know what's on the wiki re: rate limit policy, but what I'm actually > observing appears to contradict it. > > Many of the requests coming back are showing that the limit is 100 for each > user, but I thought my IP was whitelisted, which the wiki says should take > precedence over the user's rate limit. > > So, what is the policy? Perhaps it's just my Twitter ID @dossy that's been > whitelisted, but not my IP? How could I confirm this? > > > -- > Dossy Shiobara | do...@panoptic.com | http://dossy.org/ > Panoptic Computer Network | http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
