We are going to roll this change back and re-evaluate how we can better accomplish our goals. There are problems and shortcomings of this strategy that we need to mitigate.
I will update this thread when we have a concrete plan to share. I do not have a definite date or time for the rollback but it should be soon. As always, thanks for your patience. Thanks, Doug On Mon, Jul 20, 2009 at 6:22 PM, Jesse Stay<[email protected]> wrote: > The problem is so long as they are complaining on some of our apps they are > complaining on all our apps and there's no way of telling which app caused > it. In addition, it would be nice if OAuth-authorized apps were exempt from > this limit. Stopping a potential cracker is as simple as turning off their > OAuth in that case. > > Jesse > On Mon, Jul 20, 2009 at 9:15 PM, Scott <[email protected]> wrote: >> >> Doug, I would also like to know if this can be changed to trigger only >> on incorrect credentials. I check to make sure a user hasn't >> deactivated my app connection every time they load a page, so these 15 >> calls gets used up rather quickly. I've started to get some >> complaints due to this error and would prefer not to rewrite my code. > >
