Hey All,

   Definitely experiencing OAuth issues as well.  Still in development
on my local machine but I keep getting time out errors upon trying
authenticate Oauth here:



  So I could keep things going (and keep coding), my quick workaround
was to sign into twitter.com first, and then let my app authorize
oauth that way. This has worked, but I think its because  I've set my
app to "sign-in-with twitter". You can do so on your app config page
on twitter (http://www.twitter.com/apps/). Not sure if this will help

 The big issue is that I know other peoples (and their users) are
still unable to authorize the Oauth tokens, so hopefully that gets
resolved soon.

  Keep up the good work Twitts. Crossing my fingers this isn't an
ongoing issue.

On Aug 16, 6:41 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> Everyone,
> Please see the updated post on status.twitter.com 
> -http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-c....
> We are continuing to assess the issue and will report back when we know more.
> Thanks for your patience, Ryan
> On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yar<hweeb...@gmail.com> wrote:
> > Can you confirm if OAuth access is the only known issue? I feel silly
> > repeating the same question over and over again: "Even /
> > rate_limit_status calls are timing out on my server. I have no API
> > access *at all*".
> > --
> > Hwee-Boon
> > On Aug 17, 5:21 am, Chad Etzel <jazzyc...@gmail.com> wrote:
> >> We've asked the keeper-o-the-blog to post something to that effect.
> >> Hopefully it will appear soon.
> >> -Chad
> >> On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretorius<dpr...@gmail.com> wrote:
> >> > Can you at the very least PLEASE publish something on
> >> > status.twitter.com about the API being down and/or very unresponsive
> >> > at times, so that I have a link where I can refer my users, so that
> >> > they can see I am not shitting them?
> >> > Dewald

Reply via email to