Twitter proof not detected
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I ran:
C:\Users\Fernando\AppData\Local\Keybase>keybase prove twitter ferrybig3
You already have a proof for ferrybig3@twitter; overwrite? [y/N] y
Please publicly tweet the following, and don't delete it:
Verifying myself: I am ferrybig on Keybase.io. en5h3CWvDI5OI2ONmU9fmqKkZfd-UYHT1
_yA / https://keybase.io/ferrybig/sigs/en5h3CWvDI5OI2ONmU9fmqKkZfd-UYHT1_yA
Check Twitter now? [Y/n] y
Couldn't find posted proof.
Check Twitter again now? [Y/n] y
Couldn't find posted proof.
Check Twitter again now? [Y/n] y
Couldn't find posted proof.
Check Twitter again now? [Y/n]
Couldn't find posted proof.
Check Twitter again now? [Y/n] y
Couldn't find posted proof.
Check Twitter again now? [Y/n] y
Couldn't find posted proof.
Check Twitter again now? [Y/n] y
Even though I posted my proof at https://twitter.com/ferrybig3/status/836494638244630528, it still fails to detect it properly
my log id: 6723e633521c2bc4833a161c
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 with the reported keybase prove twitter ferrybig3 command and the posted proof at the linked Twitter status, then use log id 6723e633521c2bc4833a161c to investigate why the proof lookup fails. Done means the posted proof is detected successfully during the command flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100