The order of operations was: * Twitter supported basic auth only. * Twitter forced all new apps, including native apps, to use OAuth. Existing basic auth apps

The order of operations was: * Twitter supported basic auth only. * Twitter forced all new apps, including native apps, to use OAuth. Existing basic auth apps were allowed to continue working without modification. * Twitter rolled out xAuth specifically to allow native app developers to provide non-shitty user experiences. * Twitter finally forced all apps off of basic auth. I don't think there's a single native app that chose the web-based OAuth workflow over xAuth. They were at one point in a position to move forward with only the OAuth web flow, but they chose to roll out xAuth after they were requiring all new apps to use the OAuth web flow. Now they're taking away privileges from xAuth apps without providing a solution to the problem xAuth was created to solve in the first place. And they're giving developers 2 weeks to figure out what to do and do it. It's not surprising that developers are upset.