It also doesn't seem to be working properly on Mobile Safari either on the iPhone
On Aug 7, 10:12 pm, Ryan Sarver <[email protected]> wrote: > Brian, > > Thanks for letting us know. We will try to dig in on the OAuth issues and > see if we can come up with any solutions. > > Best, Ryan > > On a side note, we are seeing more issues with Firefox and very few with > Safari but we are exploring > > > > On Fri, Aug 7, 2009 at 1:40 PM, Brian Knoth <[email protected]> wrote: > > Thanks for update Ryan, but I got to tell you, I have not gotten a single > > oAuth request through from our app since early yesterday morning before the > > original attack. It's not intermittent, it's really nothing. Now, out app is > > hosted in EC2, so I'm not sure if that is making a difference with any IP > > blacklisting. > > > Brian > > > On Fri, Aug 7, 2009 at 4:37 PM, Ryan Sarver <[email protected]> wrote: > > >> We are noticing a number of people are experiencing issues with OAuth. > >> There is nothing inherently broken with OAuth, instead the issue is tied to > >> API calls periodically timing out due to the attack. All calls, including > >> unauthenticated calls are experiencing the same problems. > > >> We are working to resolve this and all the other API-related issues and > >> will keep you informed as we make progress. > > >> Best, Ryan > > >> On Fri, Aug 7, 2009 at 10:59 AM, AdamHertz <[email protected]> wrote: > > >>> Ours recurred this morning, as well. > > >>> On Aug 7, 10:49 am, Rich <[email protected]> wrote: > >>> > Mine has re-occured... if you're going to force people to use oAuth > >>> > from now on, at least get it running again fast! > > >>> > On Aug 7, 2:22 pm, Brian <[email protected]> wrote: > > >>> > > Our app is still experiencing oAuth denial issues since the DDOS > >>> > > problem yesterday. Has anyone heard any update to this problem? or > >>> is > >>> > > there some action that app developers need to take to get back in > >>> > > business? > > >>> > > Thanks, > >>> > > brian
