So if a user authorizes an app for read access, the app can switch to read/write at any time without asking the users permission? Is this true? Anyone from Twitter have any input on this?
On Sun, Jan 30, 2011 at 11:04 AM, Patrick Kennedy <[email protected]> wrote: > Tim - > > 1. Changing from read to read/write won't change you API consumer > keys or tokens. > > 2. Your application's users don't authorized for read or read/write; > they merely use your application, which you offer as read or > read/write to the world. That is to say, if it's read, your > application can only read its tweets, and if read/write, it can both > read its own tweet and post to the world. > > I'd say go ahead and switch to read/write, given the fact that you now > want that functionality. > > ~Patrick > > On Sat, Jan 29, 2011 at 10:24 PM, Tim Bull <[email protected]> wrote: >> We must be about the only developers in the universe that requested >> users grant only read access when we first got people to connect >> http://trunk.ly to Twitter (I think of the 40 or so apps authorized on >> my account, Trunk.ly is the only one that asks for Read only). Never >> ask for more access than you need is my philosophy. >> >> Doh! >> >> Of course now, we want to add some Tweet out functions which require >> users grant us Write access. >> >> A couple of questions for the Twitter people. >> >> 1. If we change the access in the application from read to read/write >> does this reset the API key, or will it stay the same (hoping it stays >> the same). >> 2. How can I work out if existing users have authorised us for read/ >> write? I looked at >> http://developer.twitter.com/doc/get/account/verify_credentials >> but it doesn't show me what access they have. Do I have to write, >> fail, force them to step through OAuth then post? Or is there a way of >> knowing before hand it will fail and asking them to upgrade? >> >> Thanks, >> >> Tim >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
