I agree that this seems like a bug and added my thoughts to the issue report.
Abraham 2009/8/9 Jeff Dairiki <dair...@dairiki.org> > > On Sun, Aug 09, 2009 at 03:50:44PM -0700, David Cramer wrote: > > > > So short story I've been changing our application from Read to Read/ > > Write access, and I cannot get it working. I've checked and double > > checked the app settings, and it asks for "read and update access" on > > the authorize page. Once authorized, however, it continues to say > > "Read-only application cannot POST". > > It seems that once an oauth token has been issued , twitter will/can > not change its permission level. If there is a valid read-only oauth > token for a particular user, if you send the user to the authorize > page requesting read/write access, you get back that existing token, > with access rights unchanged (still read-only). > > The only way (that I've been able to figure out) to "upgrade" a user's > access from read-only access to read/write is to have the user visit > their "settings->connections" page, revoke access to your app, then go > through the authentication process again. Then you get back a new > oauth token, and it will have the requested access level. > > > I filed a ticket on this a month or so ago: > > http://code.google.com/p/twitter-api/issues/detail?id=814 > > The response was WontFix. (Personally, I still maintain this is a bug.) > > Jeff > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Fairbanks, Alaska, United States