More OAuth2 Providers

[riptl]

Twitch (#19)
OAuth documentation
Getting current user (Same for APIv5 and New API)

[riptl]

Twitter (#16)
OAuth documentation
Getting current user

[riptl]

rip indent f6c4a49 GitHub merge tool is useless

[riptl]

No need for PR anymore, this is best done manually.

Twitch

• Authorize https://id.twitch.tv/oauth2/authorize
• Token https://id.twitch.tv/oauth2/token
• Scope user_read
• Current User https://api.twitch.tv/kraken/user
• Username Field name
• Username Prefix: none

Twitter

• Authorize https://api.twitter.com/oauth/authorize
• Token https://api.twitter.com/oauth/access_token
• Scope: none
• Current User https://api.twitter.com/1.1/account/verify_credentials.json?skip_status=true&include_email=false
• Username Field screen_name
• Username Prefix: none

[nektro]

The reason Twitch and Twitter have not been implemented is because of their non-standard OAuth2 flows., Although I really do appreciate you finding the proper endpoints, it really helped.

When using the Twitter endpoints, they request an extra header with a value that seems Twitter specific and I am still looking into it.

For Twitch the problem is 2 fold in both public versions of their API dubbed kracken and helix respectively. The kracken API requires a non-standard use of the Authorization header at the access_token endpoint. Usually this wouldn't be a problem, but a use of the Authorization header has already been added in the way that the header is used. And when using the helix API, the /user endpoint has been removed and only exposes /users which wraps the JSON output in an array.