[twitter-dev] A new permission level

2011-05-20 Thread Frank Ash
Did anyone else change their permission on Twitter to rwdm and now their app doesn't show anything? I changed mine, and today I had to reauthorized my account because nothing would load inTo the app. Now it works as usual after I re added my info. Am I the only one? could possibly just be a

Re: [twitter-dev] A new permission level

2011-05-19 Thread Adriaan Pelzer
Hi Matt, I have started implementing these changes. The app's permissions setting is set to Read, Write DM (the new one). However, when the user gets redirected to the auth page, it still indicates that the app will not be able to read or send DM's. Is this something that will automatically

[twitter-dev] A new permission level

2011-05-19 Thread Frank Ash
I wish they would just tell the developers to go to hell in a way and let us know they hate us instead of doing these back handed attacks on our apps all the time. This has very very little to do with privacy. Especially for the developer that wants to abuse accounts, this doesn't stop them and

Re: [twitter-dev] A new permission level

2011-05-19 Thread Damon Parker
On that day when your users open up our various clients and see issues with direct messages I suggest you insert your own DMs to your users with succinct descriptions to the root of the problem and links to further info. It looks like there is no way to prevent having to update apps for those

Re: [twitter-dev] A new permission level

2011-05-19 Thread TJ Luoma
On Thu, May 19, 2011 at 5:18 PM, Frank Ash nut...@gmail.com wrote: To disguise this as a security issue is laughable at best and a bit insulting. As USAmericans learned after 9/11/2001, you can push through just about any policy you want if you wrap it up as security. It's just astounding to

[twitter-dev] A new permission level

2011-05-19 Thread Frank Ash
Yes janol, everything but twitters official apps will fail. This is specifically aimed at client apps. It is a way to specifically Target client apps because it deals only with DM's which are mostly viewed through client applications. And specifically you said even tweetdeck, I would say

[twitter-dev] A new permission level

2011-05-19 Thread Frank Ash
I'll give an example for people using multiple accounts. From a customer point of view. I have 12 Twitter accounts, and I use 3 separate clients for different things. When this comes out I will have to re-authorize 36 times over these 3 apps alone. And they won't work until I do. If I was a

Re: [twitter-dev] A new permission level

2011-05-19 Thread Damon Parker
Frank- Correct me if I'm wrong, but the applications won't quit working altogether. You'll get a 403 error when trying to access DMs through the API. Everything else should work as normal. Has there been a better official answer if this affects Twitter's own apps other than this: Will

[twitter-dev] A new permission level

2011-05-19 Thread Frank Ash
Cartmetrix, We don't know for sure what will happen. That's kinda the problem. My guess is we all prepare now by making our app request rwdm access, then when the switch takes effect any token that has been changed with this update will then need to be reauthorized. Not effecting us now, but

Re: [twitter-dev] A new permission level

2011-05-19 Thread Damon Parker
Frank- http://dev.twitter.com/pages/application-permission-model-faq The way I read the FAQ posted is _only_ apps requiring DM read access will be affected under the following endpoints: /1/direct_messages.{format} /1/direct_messages/sent.{format} /1/direct_messages/destroy.{format}

[twitter-dev] A new permission level

2011-05-19 Thread Frank Ash
That would be much better cartmatrix but either way, its a negative and unnecessary to take this approach. I am still a bit sceptical that everything will still work fine, just if they try to send a DM it will fail to a 403 error. There is language in the post that suggests both outcomes as

[twitter-dev] A new permission level

2011-05-18 Thread Matt Harris
Hey everyone, We recently updated our OAuth screens to give users greater transparency about the level of access applications have to their accounts. The valuable feedback Twitter users and developers have given us played a large part in that redesign and helped us identify where we can do more.

Re: [twitter-dev] A new permission level

2011-05-18 Thread Jim Cortez
Matt, You say: This means applications which use xAuth and want to access direct messages must send a user through the full OAuth flow. What if the client using xAuth has no browser and therefore cannot go through oAuth? Does this mean that direct messages cannot be accessed? Is there a

Re: [twitter-dev] A new permission level

2011-05-18 Thread Tom van der Woerdt
Sounds good! Also sounds like you folks are finally trying to get rid of xAuth :-) Of course, for desktop (and mobile) applications this will mean that they will have to integrate the normal OAuth flow. Yay!. In the past, I've seen several occurrences where popular clients weren't affected

Re: [twitter-dev] A new permission level

2011-05-18 Thread M. Edward (Ed) Borasky
-- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdos Quoting Matt Harris thematthar...@twitter.com: Hey everyone, We recently updated our OAuth screens to give users greater transparency about the level of

Re: [twitter-dev] A new permission level

2011-05-18 Thread Andrew W. Donoho
On May 18, 2011, at 12:01 , Matt Harris wrote: We know this will take some time so we are allowing a transition period until the end of this month. Gentlefolk, This is way too short an amount of time to implement OAuth and transition mobile users off of an xAuth based client.