On May 18, 1:01 pm, Matt Harris <thematthar...@twitter.com> wrote: > If you do need access to direct messages: you will need to edit your > application record onhttps://dev.twitter.com/appsand change the permission > level of your application to “Read, Write and Direct Messages”. The new > permission will not affect existing tokens which means existing users or > your app or service will need to reauthorize. >
1. Despite the added dev time and complexity, from a user perspective I thank Twitter for increasing the granularity of security. Yes most devs don't misuse it but it only take one bad apple. 2. I have changed the permission level for my application. When I view the permission on https://twitter.com/settings/applications is shows "read, write, and private message access" despite the fact that I have not updated the existing token. This is misleading to the user. They might think their current token is RWPM but it is really only RW. I understand the complexities in reporting this accurately, but it will lead to confusion. 3. I have not seen a method we can effectively test this besides changing our code and waiting for PMpocalypse. Nor found a way to obtain the current permissions of the token in use. Having access to either would give me more confidence that my app won't break come June 14th. Thanks, Mark Pavlidis -- 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
