<http://schema.org/articleBody>
"When you authorize a third-party application access to your Twitter account, do you know exactly which pieces of your account \u2014 direct messages, for instance \u2014 the application gains access to? Twitter has introduced new permissions features to provide more clarity and help you make informed decisions before you click the \"Authorize app\" button.\nBeginning Wednesday, you will see a new permissions screen with a comprehensive list of actions that the third-party application will be able to do once a connection is authorized.\nThe permissions screen will inform you whether the application is requesting to read your tweets, see who you follow, update your profile, post to Twitter on your behalf, access your direct messages or all of the above. You won't have granular control over allowing an application to perform one activity and not another, but the list is intended to encourage you to think before you authorize access.\nTwitter is also requiring applications that access your direct messages \u2014 arguably the most sensitive information of all \u2014 to be a bit more responsible. These applications will need to explicitly ask for your permission again. Plus, Twitter is revoking direct message access from applications that do not need access to that information.\n\"By the end of the month, applications that do not need access to your direct messages will no longer have it, and you can continue to use these apps as usual,\" Twitter corporate communications staffer Jodi Olson writes on Twitter's blog.\nOlson indicates that the permissions updates were implemented in response to requests from users and developers.\nWill the additional information make you think twice before you grant access to third-party Twitter apps?\n\n\n\n"^^<http://www.w3.org/2001/XMLSchema#string>
<http://mashable.com/2011/05/18/twitter-permissions/>