Recently Slack updated its scopes, and the last step of the migration states:
"Change your app’s authentication URL to look like this: https://slack.com/oauth/v2/authorize?client_id=XXX"

This URL has changed, and it seems that new Slack apps cannot use this library.

Documentation page: https://api.slack.com/authentication/oauth-v2

There are a couple issues open right now that suggest a general restructuring of GAM code, which I agree would be good. However, one simple fix that would help both with code structure and readability of contributed code is a style guide that could be enforced during PR review.

The main file is over 13k lines, at this point, and lacks a consistent style and structure throughout, making it diff

The current README example is out of date as Twitter now used OAuth2. Would it be possible to update the README with an example for the OAuth2 Twitter API?

Hi,

In order to be able to use this in my Django Project, I need to be able to use the default Django decorator '@login_required()', which will redirect a user to a 'LOGIN_URL', while providing GET parameter 'next=/page-we-came-from/' after a successfull login has been performed. One the login has been performed, and the redirection to the page we came from has succeeded, the system should see t

I just started using OAuth2 on MacOS 10.15.4 talking to Slack using the embedded authorisation mechanism. Slack prompts for a workspace, followed by a username/password combination and a cookie is used to bypass this on subsequent attempts. Because it may be desirable to validate multiple connections or change accounts, etc. the cookie may need to be cleared.

Although

`let storage = HTTPCo

Not all built-in actions are listed in action doc. Will there be an update? Below are actions found in type definition.

  export const REDIRECT_SUCCESS: string;
  export const USER_LOADED: string;
  export const SILENT_RENEW_ERROR: string;
  export const SESSION_TERMINATED: string;
  export const USER_EXPIRING: string;
  export const USER_FOUND: strin

You indicate Native SFSafariViewController iOS/MacOS in documentation.

The line of code below doesn't work on Xamarin.mac

Then call the following line in your iOS AppDelegate FinishedLaunching method;

SimpleAuth.NativeSafariAuthenticator.Activate ();

app just hangs on Xamarin.mac when trying to authenticate I line above used.

please assist

1. add small steps regarding build and use the demo server
2. call out how to config Keys.hs in order to make the demo server work

The old client showed a description of the different game types (phantom-x, murder party, etc.) when mousing over them.
Can also add it in the client on mouseover when hosting games or maybe in the details part on the right. Info should be somewhere easily accessible in the client at least, because it's not obvious what most of the game types do.