Twitter in their infinite wisdom decided to implement a limit on the
verify_credentials API call.
I believe its 15 calls per hour.
They have since come to their senses and said they will be rolling
back to the previous behavior. However, as yet they still haven't done
it. But personally, I wish
What is happening?
This rollback is taking far too long for something that has affected a
lot of people!
On Jul 25, 2:32 pm, Dewald Pretorius wrote:
> Doug,
>
> I would prefer to adopt OAuth instead of writing code for Basic Auth.
>
> So, you guys need to move OAuth out of public beta into full
What do you mean the change won't affect OAuth? My application has
been suffering from this issue ever since you made the limit change.
My application has the ability to use either Basic or OAuth. My
twitter users get blocked with the 403 error after a few minutes of
usage because they reach the 1
Why will it not apply to OAuth? OAuth is having this problem too!!
Not happy!
On Jul 23, 12:15 am, Doug Williams wrote:
> Scott,This change will only affect Basic Auth, and will not affect OAuth
> applications.
>
> Thanks,
> Doug
>
>
>
> On Tue, Jul 21, 2009 at 4:27 PM, Scott wrote:
>
> > Than
