If you use oauth/authorize instead of oauth/authenticate they will be
prompted by the allow/deny page everytime instead of skiping back to your
application. Is that what you want to do?
Abraham
On Tue, Apr 20, 2010 at 19:56, Jonathon Hill wrote:
> Taylor,
>
> The problem with that is when I get
Taylor,
The problem with that is when I get my request token and redir to the
authorization page, if I'm logged in to Twitter.com it skips right on
by and redirects back to my app, so there's no opportunity to register
on my site as a *different* Twitter user, except for deliberately
going to twit
While oauth/authenticate with force_login=true does force users to
provide credentials, oauth/authenticate leaves them logged into
twitter, which is somewhat dangerous from a shared or public computer.
oauth/authorize used to behave differently - it didn't leave users
logged in. However, that
cha
