keybase / keybase/keybase-issues
User can't assign a profile photo unless user has a Twitter account
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
- Create a Keybase account
- Upload a public key
- Upload a photo
Expected Results:
Uploading a photo is an atomic method of claiming identity, but it is not a verification. For any user who has accomplished any verification, the visual identification claim should be possible.
Actual Results:
A photo cannot be uploaded. It can only be imported from the Twitter account.
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
Reproduce the issue using the listed Keybase account, public-key upload, and photo-upload steps, then trace why photo assignment is limited to Twitter imports. Compare the behavior for users who have completed another verification. Done means an eligible non-Twitter user can upload a public profile photo while the existing identity and verification rules remain intact.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100