Yeah, to tell you the truth the no notice thing has completely ruined my weekend trying to re-factor broken production code thanks to this. Jesse
On Sat, Jul 18, 2009 at 4:46 AM, Swaroop <rh.swar...@gmail.com> wrote: > > This is occurring with OAuth as well. verify_credentials is now being > limited to 15 calls/hour. I really wish they had informed us in > advance, at least not a day before weekend. > > On Jul 18, 11:07 am, Jesse Stay <jesses...@gmail.com> wrote: > > I asked the same thing of Alex - waiting to hear back. This method is > still > > very useful for verifying users haven't changed their passwords since the > > last time the script was run. Also, in Alex's own words, OAuth isn't > ready > > for production yet, last I heard so probably shouldn't go that route > either > > (or is it?). > > Jesse > > > > On Sat, Jul 18, 2009 at 1:37 AM, J.D. <jeremy.d.mul...@gmail.com> wrote: > > > > > I can see why this api should be limited, but it seems (from the > > > outside, I'm sure maybe there are other reasons) like if the > > > credentials are correct, it shouldn't count against the limit. Only > > > limit if the attempts are bad (someone is fishing). > > > > > J.D. >
