This makes the new enforcement date Thursday, June 30th, 2011.
> When the new permission is enforced we will return an HTTP 403 Forbidden error with the response body:
> {"errors":[{"code":93,"message":"This application is not allowed to access or delete your direct messages"}]}
The format of the error message differs from the one described in the following page.
http://dev.twitter.com/pages/responses_errors
I'm hoping it to be consistent.
Best,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
> --
> 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
4. Design updates to the OAuth screens to improve compatibility across devices.5. A lightweight OAuth screen flow for devices which are slow or incompatible with the new screens.