OAuth 2.0 is the next evolution of the OAuth protocol and is not backwards compatible with OAuth 1.0. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices - wikipedia 
The specification and associated RFCs are developed by the IETF OAuth WG - ietf.org
# Desktop applications Desktop applications cannot participate directly in OAuth 2.0 flows, however the embeddable browser controls available in most frameworks make it possible to work around this limitation.
Desktop applications should use the implicit client-side flow, hosting the process within a browser control. For redirect_uri, a value of:
https://stackexchange.com/oauth/login_success
should be used. Upon a successful authentication, access_token will be placed in the url hash as with a standard implicit authentication - stackexchange
# Authorization Code Flow
Many scenarios require the 'Authorization Code' flow. Authorization Code is for apps running on a web server, browser-based and mobile apps. which is described in this article - aaronparecki.com
# Livecode's OAuth2 Script Library
This is the Livecode IDE's oAuth2 handler can be found in the script-only stack library:
stack "com.livecode.script-library.oauth2"
It is located in the Livecode IDE's library folder:
Contents/Tools/Toolset/libraries/
in the file:
oauth2.livecodescript
The main handler can be found in this
gist
Youcan see a tutorial about how to use this library for the Slack API here - lessons.livecode.com
# See also
- Using oAuth with dreamfactory.com
- OAuth 2 Simplified - aaronparecki.com
- Specification - oauth.net