On Wed, May 18, 2011 at 11:37 AM, Jon Colverson <jjc1...@gmail.com> wrote: > > Also on the subject of granularity, it would be great if the app could > request DM access but make it optional, such that users can turn it > off on the authorization page. If the user declines it then the app > would be able to ask them to reauthorize if they later try to use the > DM feature of the app.
Agreed. I'm really disappointed with this change. Asking users to reauthorize is a burden on both developers and users. Existing users already gave their permission for apps to access private messages. The lead time for developers to respond to this change is ridiculously short. In my opinion, Twitter should have allowed users finer grained control over permissions, allowing them to selectively remove "private message" permissions for existing apps. An app should be able to request a set of default permissions. Users should be able to accept the defaults, or selectively deny individual permissions. If an app has optional "private message" features, it must request "private message" permission from *all* users. Either that or register multiple apps for each set of appropriate permissions, which is confusing and difficult for users and developers to manage. Is it too late to re-think this, Twitter? -Marc -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
