How to organize re-authorize via Twitter? That is, the user already 1N time gave access for the application, did things and went out (logout). Now he comes again presses the button "login" and clearly does not want more time to get to the page with the confirmation of the legality of the actions of our apps, and want to enter the system. So how to organize it?
To store secret key in cookies and don't want to, because it somehow nebezpecna, are there any other ways? Twitpic, for example, loginit no questions asked of the user that is currently logged in to Twitter (if the course already has been confirmed for a twitpic account), there is a suspicion that he's looking cookies twitter.com.