I'm not sure why Twitter doesn't start with creating a seperate API password like FriendFeed does. This would allow all the existing services to continue operat

I'm not sure why Twitter doesn't start with creating a seperate API password like FriendFeed does. This would allow all the existing services to continue operating (user just has to change their password on the services to the API password) and would allow the user to generate a new API password when they wanted those services to stop. OAuth is definitely a good thing to get to, but they aren't going to be able to turn off the access they are giving right now overnight when their OAuth implementation is done.