Your thoughts are welcome and I can help reassure you that what you describe is actually the case. The area where there's some question and bugs is that once you've gone through the process of re-establishing a r/w capable access token, it might take a bit for the cache to cough out the access token with the elevated privileges. Our implementation is such that each access token issued has the r/w flag on it, based on the state of the client application at the time of issuance.
Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 7:22 AM, livibetter <livibet...@gmail.com> wrote: > I got your reply and I replied. > > But I have an input to add. If an application developer switch to > Read&Write from Read-only. > > I don't think twitter should apply it (Read&Write) to all users who > have granted the app to read-only. This could be seen as a (slight) > security issue only, though I don't think this will cause any problem, > but you never know. One could happen is, some user grant a app for > reading and the user pretty sure, the app is Read-only. If the > developer of app decides to switch to R&W, then post to user's > timeline? Or what if the app gets hacked? The hacker can switch to > R&W, then current app users will all be affected. > > Just my thoughts to add. > > > On Apr 27, 9:27 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > Thanks for the help everyone. It seems to take a bit to fall out of our > > caches right now. We'll be sussing out a bug fix when it's possible. > > > > Taylor Singletary > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > > > > > On Tue, Apr 27, 2010 at 2:06 AM, livibetter <livibet...@gmail.com> > wrote: > > > I have just met the same situation. I created my app with Read only, > > > then I used with that for a while. Later, I wanted to post, so I > > > switched to Read and Write. I kept re-requesting the access token, but > > > that didn't work. > > > > > The user still have "read-only" in their Setting/Connection tab. > > > > > Revoke, then authorize app again. Problem solved. (This make sense, > > > because user didn't give app the permission to write at first place.) > > > > > Hope this helps. > > > > > On Apr 23, 8:17 pm, Jeremy <jehe...@gmail.com> wrote: > > > > Hi all! > > > > > > I am having an issue with one of my apps. I set it up correctly I > > > > think, when I do tests through the API console onhttp:// > > > dev.twitter.com/console, > > > > it posts just fine, and my app has read/write access level. > > > > > > However on my site, whenever I try to post a new tweet, the tweet > > > > process seems to go without any error messages, but nothing gets > > > > posted on my twitter account. > > > > I have checked it with Firebug, there is in fact an error, I get a > 401 > > > > Unauthorised status forhttps:// > api.twitter.com/1/statuses/update.json. > > > > It says "Read-only application cannot POST". > > > > > > I consequently changed my app settings, and indeed it was read only > at > > > > first, but even after changing it to read/write, the problem remains. > > > > Any idea where it could come from? What can I do to solve the issue? > > > > > > Thank you! > > > > > > -- > > > > Subscription settings: > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
