The problem is that I'm designing an app for cases where twitter.com is inaccessible by the user because of regional bandwidth restrictions - so oauth would not work. The api mentions that "Session cookies and parameter-based login are known to work but are not officially supported." so am hoping that someone here can point me in the right direction on that.
Otherwise I'll just have to store user passwords - which is not ideal. On Mar 9, 5:10 pm, Cameron Kaiser <[email protected]> wrote: > > Basically what I am trying to do is to login using basic > > authentication the first time, then to store the cookie I retrieve and > > use that to login for future requests - meaning that my users do not > > have to re-enter their passwords each time they make any request and I > > don't have to directly store user's passwords. > > This is not currently possible with the API. Wait for OAuth (shouldn't be > long, they are currently concluding the closed test). > > -- > ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [email protected] > -- Born free. Taxed to death. > -------------------------------------------------
