[twitter-dev] Re: Bug with the new DM authorization and the /oauth/authenticate method
I have exactly the same problem; I changed the settings for my app to RWD, but when going through the oAuth flow the app still says it can't access direct messages (and I get a 93 error). Screenshots: http://moby.to/cn9dtw I have many users of my app. Hope this will be fixed soon. Michiel On Jul 1, 12:41 am, Laurent Quérel laurent.que...@yoono.com wrote: Hi all, My twitter app (a firefox/chrome extension in 'browser mode') uses the method /oauth/authenticate in the oauth process. I changed the access level of my app to read, write direct messages to conform to the new rules about DM access. I observe an error 93 when the application try to read DM and the authenticate page continue to display that my app has no access to DM... If I replace /oauth/authenticate by /oauth/ authorize this issue disappears. Is it normal? Laurent -- 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
[twitter-dev] Error in following response
Hi, I've looked to see if this has been asked before, maybe I've missed it, but I notice a problem in the 'following' tag of a user in a replies stream. This value seems to be incorrect. It is either empty, true or false at the moment but does not seem to be right in many cases. This is a problem, because I want to start making a visual and functional distinction in my replies stream between people the user does and does not follow, in order to combat replyspam. Again I apologize if this is a repost of an existing problem. Michiel
