Discussion: Question: OAuth authorization for non-web applications?

Currently, the OAuth authorization endpoint requires a valid redirection URI to point to a web application that finishes the authorization.

Are there any plans to offer an endpoint for non-web applications?

For example, google's APIs allow you to use a redirect_uri of "urn:ietf:wg:oauth:2.0:oob" to indicate that there *is* no redirect, but instead the authorization server presents the authorization code to the user so that they can copy/paste it into the application in question.

Any chance something like this might happen?
Seems like it should be easy enough to support.
On a related note, can "localhost" always be allowed as a redirect URL regardless of the configured one for local testing?
So, what's the plan for non-web apps?