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

On Aug 9, 8:07 am, chinaski007 <chinaski...@gmail.com> wrote:
> I should have taken my own advice when I ranted about Basic Auth being
> far more reliable than OAuth.
>
> On Aug 8, 3:37 pm, Josh Roesslein <jroessl...@gmail.com> wrote:
>
>
>
> > 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.
>
> > On Sat, Aug 8, 2009 at 2:56 PM, Adam Loving <adamlov...@gmail.com> wrote:
>
> > > 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:
> > > > 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???
>
> > --
> > Josh

Reply via email to