Sign-in via Twitter requires very broad permissions
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
When using Twitter to sign in users through Static Web Apps, the permissions requested by the app seem extremely broad. Is there is any reason the app needs all these permissions? i.e. I can see no reason for nearly all of these permissions....
- See Tweets from your timeline (including protected Tweets) as well as your Lists and collections.
- See your Twitter profile information and account settings.
- See accounts you follow, mute, and block.
- Follow and unfollow accounts for you.
- Update your profile and account settings.
- Post and delete Tweets for you, and engage with Tweets posted by others (Like, un-Like, or reply to a Tweet, Retweet, etc.) for you.
- Create, manage, and delete Lists and collections for you.
- Mute, block, and report accounts for you.

Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.