Twitter provider always redirects to Oauth authorization screen

Nobody has claimed this yet.

Logging in with twitter always redirects to Oauth authorization screen even when the user has provided authorization previously. This seems to the result of twitter API changing endpoint's behavior as announced here: https://twittercommunity.com/t/recent-changes-to-twitter-s-oauth-login-flow-and-api-endpoints/94943

> Impact
>
> Applications that previously called the /oauth/authenticate endpoint (after a user had signed-in and granted access to their user token via the /oauth/authorize endpoint) will now always show an interstitial screen checking that the user wishes to authorize the application to have access to their user token. This is a change in behaviour - previously, once the authorization was granted once, apps could effectively skip this step in the process by calling the alternate endpoint.
>
> If your app has already obtained access tokens for a user account, you may wish to utilize the /account/verify_credentials endpoint to check that the user remains authenticated, without directing the user to the sign-in flow.

Unfortunately there isn't much goth can do in this regard. I'm leaving this here for future reference.

The report concerns Goth's Twitter provider and the /oauth/authenticate, /oauth/authorize, and /account/verify_credentials endpoints; begin by reviewing the Twitter OAuth flow against the linked Twitter announcement. The issue says there is little Goth can do and is left for reference, so it provides no concrete completion criteria.

Written by the indexing model from the issue text.