Okay, thanks for the response. Victoria
On Jun 24, 11:07 am, Taylor Singletary <taylorsinglet...@twitter.com> 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 type. Applications set to > "desktop" cannot dynamically present a oauth_callback on the request token > step (unless the value of oauth_callback is equal to "oob" for PIN-code > out-of-band OAuth), while apps set to "client" have the ability to > dynamically set an oauth_callback as they see fit. When saving an > application in "client" mode, one must provide a placeholder callback URL > even though it's a best practice (and valid OAuth) to set the oauth_callback > explicitly. > > @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor > Singletary > > On Fri, Jun 24, 2011 at 9:00 AM, Andrew W. Donoho > <andrew.don...@gmail.com>wrote: > > > > > > > > > > > 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 an experiment with an xAuth enabled application can > > answer this question. It could go either way. That said, I expect that the > > authorization paths, due to the different routes, are independent for xAuth > > and the OAuth path. (I believe the app type is really a choice between > > three-legged browser OAuth and PIN OAuth.) > > > Twitter folks need to answer this question. > > > Good luck. > > > Anon, > > Andrew > > ____________________________________ > > Andrew W. Donoho > > Donoho Design Group, L.L.C. > > a...@ddg.com, +1 (512) 750-7596, twitter.com/adonoho > > > Knowing is not enough; we must apply. > > Willing is not enough; we must do. > > -- Johann Wolfgang von Goethe > > > -- > > Twitter developer documentation and resources:https://dev.twitter.com/doc > > API updates via Twitter:https://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >https://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
