Hi DuBose,
The account looks whitelisted. The most common issue when using
authenticated requests is that you're calling a method that does not
require authentication and your HTTP library is not sending it. I have
seen some reports of this with .NET languages. Take a look at this old
discussion and see if it helps:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1b1628f31b25717e/b2c2aaa1f80bc9bf?lnk=gst&q=.NET+basic+auth#b2c2aaa1f80bc9bf
If not you might want to try using a proxy like Charles [1] so
you can verify the requests are being sent with an Authorization header.
Thanks;
— Matt Sanford
[1] - http://www.charlesproxy.com/
On Apr 23, 2009, at 08:02 AM, DuBose Cole wrote:
I was wondering if anyone else has encountered problems with the rate
limit while whitelisted. I recieved whitelisting authorization for my
app development, but my rate still shows up as 100 per hour. After
running into this problem and reading about some database issues a
while back, I applied again, got accepted and have encountered the
same issue. I'm making authenticated calls in my code using my white
listed id (@dubosecole). I'm using basic authorization and not OAuth,
are there any other steps anyone can suggest?
I'm using it for network visualization/message transmission analysis
rates in a relatively simple vba package and this rate limit issue is
seriously slowing down development.
Any help anyone can provide would be appreciated.
Thanks,
DuBose
