I'm seeing similar behavior on Twibes.com, where 100s if not 1000s of my users cannot log in.
I can rarely get to the login page, what is concerning, is that I curl the URL, the page is returned immediately. Safari and Firefox spin for 30-60s before rendering the page (if ever). On Aug 8, 12:09 pm, Rich <rhyl...@gmail.com> wrote: > We've got a similar oAuth issue. My application can get as far as the > login screen, but consistently.. and I mean 100% of the time fails on > the Allow button. It doesn't even get as far as the redirect screen > (so it's not a problem with us handling the redirect). > > If they want us to use oAuth instead of Basic Auth then oAuth should > be a total priority to keep up and running. > > Now I understand not everyone is suffering from this problem, but a > little more communication as to why this is happening to some people > all the time would be useful please. > > On Aug 8, 7:51 pm, AccountingSoftwareGuy <virga.rob...@gmail.com> > wrote: > > > Our app has been down for almost 2 days now...every call we make to > > the Twitter API returns a 408 Request Timeout. > > > When can we expect this to be working normal again???
