408 Request Timeout on oAuth Calls to API

[AccountingSoftwareGuy]

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???

[Rich]

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:

[Adam Loving]

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).

[Adam Loving]

I'm pulling my hair out. 1000s of Twibes users can't log in. Twibes
uses oAuth from App Engine. Calls to http://twitter.com/oauth/request_token
have been consistently timing out for 3 days now.

Is there any work around or way to get approved access?

On Aug 8, 11:51 am, AccountingSoftwareGuy <virga.rob...@gmail.com>
wrote:

[Josh Roesslein]

Oauth has been on and off through out this DoS attack. Sometimes it work sometimes not.
Only work around right now is to fall back to basic auth. It might not be a bad idea
having basic auth in place of emergency of OAuth going offline. Sure the user will need to supply
username/pass, but at least they can use your service. Once Oauth is online then you could disable
basic auth.

--
Josh

[chinaski007]

I should have taken my own advice when I ranted about Basic Auth being
far more reliable than OAuth.

[chenyuejie]

My app works well locally(use OAuth), but does not work in AppEngine,
seem they are still restrict large request from same IP.

Yes, Twitter missed a chance to propagate OAuth, but they didn't ruin
it :)

[Carlo Zottmann]

Yes, Twitter staff, please respond: any update on the oAuth situation?

Thanks,
Carlo

http://TwerpScan.com