Hi Matt, while being an improvement over the old oauth form, this form still does not tell the user all she needs to know. In particular, it hides the fact that the app will have almost total control over their twitter account.
In my experience, most users are totally unaware of this fact. Of course, from a developer's point of view everything that will stop user's from authorizing their apps will always be greeted with skepticism. However, I hope that Twitter will sooner or later inform users that authorizing an app with read/write access can be potentially very dangerous -- and doing so in the oauth form would be the best place to do so. Or we could just hope that we will never see any malicious Twitter apps. Best regards, Stefan -- 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
