I poured a 4-shot breve latte just in case, flipped the switch at https://dev.twitter.com/apps, and was delighted when:
- shipping Twittelators already deployed can use and continue to get valid RW XAUTH Tokens - those XAUTH tokens still work - New RWDM tokens are correctly given to new in-house builds of Twittelator So, I can totally relate to the feeling of "Am I about to hose 1 million users?" but, especially with the enhancements due this week from Twitter, I think we can all make a smooth transition to the new flow. On May 27, 11:31 pm, Ed Finkler <funkat...@gmail.com> wrote: > Fellers, > > For testing as we prep our apps for the switch to PIN-based auth, I'd like > to change the default access level to "Read, Write, & Private Message". > However, I'm concerned this will disable xAuth for existing users > immediately, rather than once we hit June 30. > > Can I do this, or should I register a new application? Or do I have other > options? > > Thanks, > > -Ed -- 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
