Check to see if oauth is authorized

[sferik]

Check to see if oauth is authorized

[pengwynn]

Interesting. I coulda swore that verify_credentials used to be excluded from rate limiting but according to the docs is is not. I'll take a look at adding something like this. Unless you beat me to it with a patch with tests :-)

I would beat you to it with a patch and and tests, but I am fairly new to ruby, and have no clue at how to make gems or patch them for that matter.

[sferik]

The gem provides a verify_credentials method that you can already use to do this.

The problem is that the verify_credentials method was taking hits against the API limit.

[sferik]

It looks like you're just calling Twitter's account/verify_credentials resource, which is the same resource used by the gem's verify_credentials method. Can you explain why one method counts against the rate limit but the other does not?

No, I can't. This could have already been patched too. This bug was placed back in june. I think at the time the verify_credentials was going through a different call that was against the API limit.

[sferik]

According to Twitter's documentation the account/verify_credentials resource is rate limited: http://dev.twitter.com/doc/get/account/verify_credentials

So, it's not surprising to me that calling the verify_credentials method subtracts one from your available rate limit hits. What I don't understand is how your method avoids paying this cost. According to my testing, they both do: https://gist.github.com/2153582e5786957a8ee7

Can you reproduce these results?