Good point, Evan.
In the mean time -- if you go and explicitly reject your access token on
http://twitter.com/settings/connections and then re-negotiate it on the "my
token" feature on dev.twitter.com, you should be able to get around this
On Mon, Aug 16, 2010 at 9:29 AM, Evan Anderson <ejdander...@gmail.com>wrote:
> I've seen that read, read + write access is based on access tokens,
> and you can request new access tokens if you update your settings.
> However, It seems that the access tokens Twitter gives you explicitly
> on an app's settings page don't update to reflect this when you update
> your app's access settings. I was just curious if the twitter dev team
> was aware of this and any indication if they will update the access
> tokens in the future to reflect an app's access setting.
> Evan Anderson