FB verification 500s if denying "Posts" scope
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I authorised Keybase to access my public data, but unchecked "Posts" because I'm making a public post — why should I grant access to all posts?
Somewhat unsurprisingly, this caused a "Error 500. Something is not right. We will look into it." error message. More unfortunately, there isn't a way to re-do the flow, from what I can tell?
Ideally Keybase should not need the "Posts" scope, but I can understand if that is hard due to platform limitations.
(btw, thanks for the great service!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Facebook verification flow and how it handles a denied "Posts" scope. Reproduce the authorization with that scope unchecked, then verify it no longer returns a 500 and that the user can retry the flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100