keybase / keybase/keybase-issues
Twitter proof failed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Web-based and command line -- tried to verify thru keybase a bit too early (Before tweet was posted) subsequent attempts on cmd line and web failed until I created a new post, waited a minute for it to propagate thru twitter servers, then tried verify again.
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 failed Twitter proof through both the web interface and command line after an attempt made before the post propagated. Compare verification behavior before and after creating a new post and waiting, then trace the relevant verification flow. Done means a proof remains verifiable after an initially premature attempt or the failure is clearly diagnosed.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, security, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100