Hi Shy,
When authenticated methods correctly reflect the whitelisting and
unauthenticated methods do not the most common cause is a client side
issue where the authentication is not being sent. This is the case
with browsers, who wait for an HTTP 401 and then respond with
credentials. Some HTTP libraries do this as well (.NET comes to mind).
If you let us know what library/language you're using we might be able
to help. Another good thing to do is take a look at your request
headers … if there is no Authentication header you're not authenticated.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 19, 2009, at 9:39 AM, Shy Cohen wrote:
My app, running under my white-listed creds, was hitting the 100/hr
rate limit. I thought that maybe my white-listing did not go into
effect, but TweetDeck was showing that I have 20K calls left. I ran
the Twitterizer sample, and it was working fine too, showing the quota
to be 20K. I was baffled. I started playing with this a little and I
believe I finally found the issue!
It seems that calls to fetch data about the currently logged in user
(e.g. http://twitter.com/statuses/user_timeline.xml) are subject to
the 20K rate limit, while calls to fetch other users' data (e.g.
http://twitter.com/followers/ids.xml?user_id=<id>&page=<page>) are
counted against the IP (or something else, but not the creds I’m
providing).
Is this correct? If so, what’s the reason behind it?
Also, is there a way to get around this without white-listing my
(dynamically assigned) IP address?
Thanks,
Shy.
