Will the Twitter sign-in stop working on June 1st?

Twitter is forcing all developers to change their sign in procedure by the end of this month.

Previously, Twitter and its developers could use a security protocol called “xAuth,” which basically presents two fields (user name and password) to a user when that user wants to let an application access his or her Twitter account. Mac and iOS clients Twitterrific, Tweetbot, and Hibari have been using xAuth for a clean and simple log-in. Among other things, the developer of the client application can control the look of the log-in screen.

Now, however, Twitter is forcing all developers, by the end of the month, over to a more recently developed protocol named Oauth. Under Oauth, a user must leave a native application, launch a browser, go to Twitter, and enter his or her credentials there. Twitter than calls back and gives the application a token (a random number, essentially), which says this client has the right to respond on behalf of this user.

@Tim - Will we get a timely update to the Twitter sign-in on Vanilla, or do you recommend disabling at the end of the month (and how would that affect existing users?)