On Jun 23, 11:34 am, "Andrew W. Donoho" <[email protected]> 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 to return a user's capabilities to what they once had.
Thanks for the response, although I don't think we're talking about the same thing. 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? Thanks, Victoria -- 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
