You may not have noticed, but with Twitter, if you request a token while
you already have one, you'll simply get back the one you already have.


On 9/3/10 6:47 PM, Bernd Stramm wrote:
> On Fri, 3 Sep 2010 01:27:34 -0700 (PDT)
> Ken <> wrote:
>> I thought I had found a solution, albeit a horrendously ugly one:
>> redirect them to, but even that doesn't
>> work.
>> If you are looking for reliable, don't log them in with OAuth - except
>> once, the first time, when you store their token.
> Indeed.
> If you already have the token, why would you make them log in? 
> If you get a new token every time they visit your 3rd party ("consumer")
> site, you generate a lot of authorized tokens, ALL of which are valid
> for the rest of eternity, or until twitter decides that it should be
> possible to invalidate tokens. 
> Bernd

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to