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,
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, Twitter
http://twitter.com/episod
On Tue, Apr 27, 2010 at 2:06 AM, livibetter livibet...@gmail.com wrote:
I have
I got your reply and I replied.
But I have an input to add. If an application developer switch to
ReadWrite from Read-only.
I don't think twitter should apply it (ReadWrite) 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
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
It seems to me that if a developer changes the permissions an app
requests ALL previous users should be asked to reauthorize on their
next usage (if the app typically worked on a server or without user
interaction then the developer will have to recontact users.
As a user I don't want
Did you acquire a new token before trying to post again? I'm not
positive, but if you didn't, it may be that the old token only had
read permissions and didn't get updated to read/write when you changed
your settings.
On Apr 23, 7:17 am, Jeremy jehe...@gmail.com wrote:
Hi all!
I am having an
Trying to track this bug down. Will update the thread when we've figured it
out or otherwise.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Fri, Apr 23, 2010 at 7:06 AM, Berto mstbe...@gmail.com wrote:
Did you acquire a new token before trying to post again? I'm
