On Fri, Apr 29, 2011 at 8:55 AM, Andrew W. Donoho <[email protected]> wrote: > Matt, > > I'm speaking as a user but I would like for the user to be able to > separately deny write access to my account. I don't frankly care if the > developer "requires" it. I think most developers just ask for the moon and > get it. Only Twitter can give the user the ability to deny impersonation > access on a per application basis. If the app cannot just run with just read > access, then the user should really know why. In my experience, most > developers just use write access as a mechanism to spread their brand. >
There are a few problems here -- 1) Some applications legitimately need write access to do their work - for example, an auto-unfollower. You seem to discount this example. 2) It is basically not possible to upgrade privileges (with the user's permissions) later, so if an application author thinks they may ever need the privileges, they will ask for write, even if they don't currently need it. 3) You seem to feel that the app author is working against you -- if you really feel that's the case, you, the user, are ultimately in control -- you choose whether to allow the application to have access. Twitter can not reasonably be the arbiter of which apps have legitimate write access -- it depends on the utility to you, the user, and so is a personal decision. (There are examples where apps are malicious and misleading, but that is a very small minority of all applications.) -- 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
