Oh, nice.  I was unable to get into my client over the last few days, but
followed the suggestion of clearing your cookies in Safari and it works fine
now.  Thanks

On Sat, Aug 8, 2009 at 2:15 AM, Rich <[email protected]> wrote:

>
> I still can't get mobile safari to oAuth, some people obviously are as
> I can see the number of users occassionally go up in the oAuth clients
> page
>
> On Aug 8, 4:08 am, Chris Corriveau <[email protected]> wrote:
> > Hi Mike what version of FF are you running? I'mable to use 3.5 now,
> > but Twitter may have changed something after I was Able to login and
> > get my cookie set.
> >
> > -----------------
> > Chris-
> >
> > On Aug 7, 2009, at 6:21 PM, Mike Lewis <[email protected]> wrote:
> >
> >
> >
> >
> >
> > > Genevate,
> >
> > > Still doesn't work for me in FF
> >
> > > On Aug 7, 3:15 pm, Genevate <[email protected]> wrote:
> > >> Firefox oAuth issue seems to be fixed now. Not sure for how long
> > >> but I
> > >> can actually login.
> >
> > >> Chris-
> >
> > >> On Aug 7, 5:29 pm, Rich <[email protected]> wrote:
> >
> > >>> 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 withFirefoxand 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
>

Reply via email to