I have a startup idea I'm working on which will make considerable use of Twitter. At the moment, I'm trying to figure out the best way to post Tweets from my web application on behalf of a user when they perform a specific action.<p>These are the options:<p>* When the user performs the action, the application will display the content that will be Tweeted, allowing the user to edit it. When they click the 'Tweet' button the form will post back to my server which will send the Tweet using the Twitter API. This method will require read and write permissions for the application.<p>* The other option is to popup a pre-filled tweet form on Twitter using Twitter's "intent" functionality.<p>The first one seems cleaner from a user interaction POV and has the advantage that my application knows exactly what was Tweeted, however it does require write permissions for the application.<p>So what do you folk think? Do you balk at authorising new, relatively unknown applications with read and write privileges on your Twitter account? Or do you feel that the ability to unauthorize an application if it misbehaves is enough?<p>Should an app offer clear assurances that it will be respectful of your Twitter account as part of the sign up process?
I would definitely tell the user beforehand exactly what they can expect, whichever way you go. To be honest, I still appreciate seeing "we will never sell or use your email for any purposes than login information" (or the likes,) on sites.