Keybase GUI doesn't distinguish between failed server or host proof validation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Right now if a proof fails to verify on my profile in the Keybase client, it says "Your proof could not be found, and Keybase has stopped checking..." and I'm presented with the option to delete the proof or recheck it. When I navigate to the Keybase.io website, my proof is validated, and this error only occurs on Wi-Fi which blocks the website Keybase is trying to check.
There should be a distinction in the UI for when a proof fails a local check vs. when a proof fails a server-based check.
Keybase GUI Version: 1.0.18-20170208085427+dc66461
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 Keybase GUI proof-validation flow and reproduce the failure on Wi-Fi that blocks the website being checked. Trace how local and server-based validation failures are reported; done means the UI distinguishes those cases and offers appropriate actions for each.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100