You shouldn't have a database containing Twitter usernames and passwords. I recommend purging that database immediately and then re-evaluate the problem from the perspective of someone without usernames and passwords.
Taylor On Tue, Feb 1, 2011 at 2:51 AM, Archia <tomarchib...@gmail.com> wrote: > I have a web application to allow clients to update information for their > recordings (music) which are then listed on another site. I'd like to > include an area to allow them to update their Twitter status. Given that > each client already signs in to the current application, and (some of) their > Twitter usernames and passwords are already in a database, it would be good > if they did not need to log in to Twitter as well and select 'Allow' each > time they visit that area of the application. Is it possible to bypass the > Sign in with Twitter step on connect.php and somehow send their username and > password, or at least only require this once and store their credentials in > the database to be used thereafter? > > Thanks! > > -- > 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