Twitter OAuth Beta Has Started - This is how it looks
blog.inuda.com
blog.inuda.com
I doubt banks will accept generic identity providers in the near future, but I can see them allowing known players in the consumer internet space to provide multi-factor identification.
At the least they could let you identify yourself with another provider and then add additional factors on their side.
Why would users trust an app that has access to their direct messages?
An app can access anything public through the existing API anyway without authentication.
The only difference here is that you can allow apps your trust to access your private data (or functions, like sending tweets) without giving out your password. As such it's a big step in the right direction.
Twitter apps have been one of the worst offenders for the username/password anti-pattern because of Twitter's use of HTTP-Auth for the API.
* your app can perform more API calls without IP-based rate limiting (which can be a real problem when using the Google App Engine due to shared IPs between apps)
* you can be sure that the user is who he/she claims to be (without a DM hack), which is important for some apps