The tokens are definitely short-lived, and I don't think there is a way to use them on the server side. It's likely not meant to be a simple implementation of oAuth.
On Apr 17, 3:12 pm, Shannon Whitley <[email protected]> wrote: > I spoke with the devs at Chirp and I'm planning to use the token during the > auth process. They confirmed that it is short-lived though. > > > > On Sat, Apr 17, 2010 at 2:43 PM, Abraham Williams <[email protected]> wrote: > > My understanding is the @Anywhere access tokens are short lived of only a > > few hours. Maybe Twitter can confirm that. > > > Abraham > > > On Sat, Apr 17, 2010 at 10:10, mike <[email protected]> wrote: > > >> Sort of wondering the same thing. After authenticating, you'll notice > >> your browser stores a cookie called twtter_anywhere, which I believe > >> contains the request token. > > >> Would love to be able to use that request token to make Twitter API > >> calls, but have no idea how to get the token secret. > > >> Thanks in advance. > > >> On Apr 17, 1:03 pm, aztroboy <[email protected]> wrote: > >> > Hi! I just managed to use @Anywhere on a website for authentication. > >> > Now, I would like to know how do I get the Access Token and the Token > >> > Secret with @Anywhere. I've successfully made the "signin with > >> > Twitter" example. However after I've got the user information, I don't > >> > know any method that can give me his access tokens. Is there some way > >> > to do it? > > >> > thank you in advance. > > >> > -- > >> > Subscription settings: > >>http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > > -- > > Abraham Williams | Developer for hire |http://abrah.am > > PoseurTech Labs | Projects |http://labs.poseurtech.com > > This email is: [ ] shareable [x] ask first [ ] private.
