Same issue here. The username/password version of my client works, but not
the oAuth version. It just times out when redirecting back. It's weird
because some of my users can get through, but none of my accounts can.
On Thu, Aug 6, 2009 at 5:00 PM, Sam Street wrote:
>
> My app also dies strai
My app also dies straight during auth http://twicli.com/auth
On Aug 6, 10:45 pm, Rich wrote:
> Especially annoying seeing as I've gone totally oAuth now. I don't
> blame Twitter, just the idiots that initiated the DDoS attack
>
> On Aug 6, 10:33 pm, Andreu Pere wrote:
>
> > The same behaviour
Especially annoying seeing as I've gone totally oAuth now. I don't
blame Twitter, just the idiots that initiated the DDoS attack
On Aug 6, 10:33 pm, Andreu Pere wrote:
> The same behaviour for my application. When the app wants to start the oAuth
> workflow in order to authenticate and login th
The same behaviour for my application. When the app wants to start the oAuth
workflow in order to authenticate and login the user, the server returns a
timeout from https://twitter.com/oauth/authenticate?parameters
On Thu, Aug 6, 2009 at 11:24 PM, Rich wrote:
>
> I can't get oAuth to authenticat
I can't get oAuth to authenticate on any of my clients either. It
works when the client has previously authenticated... but trying to
get a new token it fails when clicking 'Allow'
On Aug 6, 7:42 pm, stephane wrote:
> It's probably linked to the current DDOS but the authentication flow
> shows
