[twitter-dev] Re: OAuth + Mobile nightmare

2009-10-09 Thread twittme_mobi
Hi all, any update on this?it is still not clear when mobile applications could migrate ot OAuth and how long we could use basic auth? Thanks! On Sep 4, 3:36 pm, twittme_mobi nlupa...@googlemail.com wrote: in addition to storing the access token somewhere , wouldn't it be better if twitter

[twitter-dev] Re: OAuth + Mobile nightmare

2009-09-04 Thread twittme_mobi
in addition to storing the access token somewhere , wouldn't it be better if twitter deliver mobile friendly version of the oauth pages? On Aug 19, 12:14 am, JDG ghil...@gmail.com wrote: That's what you should be doing. There's no reason to get a new Access Token every time. Per the OAuth

[twitter-dev] Re: OAuth + Mobile nightmare

2009-08-19 Thread André Arruda
Great, thanks everyone :) On Tue, Aug 18, 2009 at 7:14 PM, JDG ghil...@gmail.com wrote: That's what you should be doing. There's no reason to get a new Access Token every time. Per the OAuth spec, you should probably code your app to handle an expired token gracefully. The spec states that

[twitter-dev] Re: OAuth + Mobile nightmare

2009-08-18 Thread Otávio Ribeiro
no.. just the same problem. On Mon, Aug 17, 2009 at 3:09 PM, AArruda arrud...@gmail.com wrote: I've been developing a Java/MIDP Twitter client for the past two months, and i still need a couple more months to publish a beta version. A few days ago i found out that the update source (app name)

[twitter-dev] Re: OAuth + Mobile nightmare

2009-08-18 Thread André Arruda
I'm thinking about storing the access token in the phone so the user won't have to go through all the auth process everytime the program is opened. I hope i won't find any new surprises by doing this. 2009/8/18 Otávio Ribeiro otavio.ribe...@gmail.com no.. just the same problem. On Mon, Aug