The last step of the OAuth dance (exchanging request_token for access_token) will give you an oauth_token and oauth_token_secret. You'll just have to sign your requests with those. Cf this page for more information: http://dev.twitter.com/auth#auth-request
If you're not familiar with the concept of signing your requests with OAuth, you should take a look on one of these libraries: http://dev.twitter.com/pages/libraries Finally, the X-FeatureRateLimit-Reset header has nothing to do with your access_token validity. Cf Rate Limiting documentation: http://dev.twitter.com/pages/rate-limiting Arnaud / @rno <http://twitter.com/rno> On Mon, Apr 18, 2011 at 11:02 AM, ton <[email protected]> wrote: > dear Arnaud, > > I've read what you've proposed. thanks for the info > Storing info is no problem in either application. (what is the name > used in the API documentation for the user-access token.?) > > - The problem is: How to give the app authenticated access to the user > account without going to the process (inclusive logging in) > > - Is there an url build up for that like > > http://www.twitter.com?consumerkey=...&consumersecret=....&account=.......&xyz=... > .. > > - Related question: if the timerbased limit-reset takes place do you > need a to login again or can you just start posting again. > > > On Apr 18, 6:29 pm, Arnaud Meunier <[email protected]> wrote: > > Hey Ton, > > > > There was a similar discussion on this ML a few days ago: > http://bit.ly/icFfcC > > > > We do not expire access_token (unless a user explicitly rejects you app) > so > > you don't have to go through the whole OAuth dance once someone approved > > your app. Store your user's access_token and implement a session handling > > system. > > > > Arnaud / @rno <http://twitter.com/rno> > > > > > > > > > > > > > > > > On Mon, Apr 18, 2011 at 5:20 AM, ton <[email protected]> wrote: > > > Hi. I've made an app (for browser and mobile device and Desktop) It > > > works fine but every time I start the app I have to get a new > > > PINnumber from Twitter. > > > > > Is there a way to trust an application once and use the given > > > trustdata for all the subsequent uses? > > > Best rgds, > > > Ton > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
