[twitter-dev] Re: Switching Application Type to "Browser"

2011-06-26 Thread Victoria
Okay, thanks for the response. Victoria On Jun 24, 11:07 am, Taylor Singletary wrote: > Changing your application type has no effect on existing access tokens. If a > key has the xAuth permission granted to it, xAuth can be performed using the > API key regardless of the setting for application

Re: [twitter-dev] Re: Switching Application Type to "Browser"

2011-06-24 Thread Taylor Singletary
Changing your application type has no effect on existing access tokens. If a key has the xAuth permission granted to it, xAuth can be performed using the API key regardless of the setting for application type. Applications set to "desktop" cannot dynamically present a oauth_callback on the request

Re: [twitter-dev] Re: Switching Application Type to "Browser"

2011-06-24 Thread Andrew W. Donoho
On Jun 23, 2011, at 20:14 , Victoria wrote: > If I change Application Type to "Browser" (on the > https://dev.twitter.com/apps/edit/ > page), will this negatively affect the xAuth process currently used in > the production version of my Twitter client? Victoria, Only Twitter or

[twitter-dev] Re: Switching Application Type to "Browser"

2011-06-23 Thread Victoria
On Jun 23, 11:34 am, "Andrew W. Donoho" wrote: > As I understand it, the authorization tokens that exist do not change. They > will just stop being authorized to send or read direct messages. IOW, old > tokens are being limited in a new way. Your new version will be able to switch > to new tokens