I was wondering what the official stance was on rate limiting of
verify_credentials?

According to the API documentation it isn't (API rate limited =
false):
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials

I did however note that it was rate limited during the DDoS attack
earlier in the year:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/2d68c74567bc9809/ed0c484f66809740?hl=en&lnk=gst&q=verify_credentials+rate+limiting#ed0c484f66809740

I also saw indications of rate limiting as recently as Oct 3:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e4052d52e722378a/0f22a5aaf424745d?hl=en&lnk=gst&q=verify_credentials+rate+limiting#0f22a5aaf424745d

Just trying to plan ahead and not assume anything ...

Thanks,

Scott

Reply via email to