Confusing user experience while tracking someone with an incomplete(?) proof
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Invited a friend, they accepted and set up keys and a few proofs. Tried to track from command-line. Got a scary message that their twitter verification failed (though the other proofs succeeded). Visiting their keybase.io profile, I saw nothing about a twitter identity for the person.
Speculating, I expect that this was because they had started to verify their twitter, but hadn't yet posted a proof.
I followed them anyway, but I assume that that means that I accepted the twitter sig that had not actually been posted to Twitter.
As a user, I would expect that tracking my friend would have shown me only the proofs they had completed, and match the identities I would see on their profile on keybase.io.
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 reproducing the behavior through command-line tracking for a user with an incomplete Twitter proof, then compare the result with that user's keybase.io profile. Done means incomplete proofs are not presented as verified and tracking shows the same identities as the profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100