Skip verifying proofs for unavailable sites
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
If a certain identity provider is generally unavailable, the client should not attempt to verify proofs against it.
For example if Facebook.com is down, or blocked via /etc/hosts, Keybase shouldn't fail verifying someone's identity if their other proofs are still available.
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
No files, tests, or entry points are named. Start by locating the client’s proof-verification flow and how unavailable identity providers are handled; reproduce the Facebook or blocked-provider case, then verify that other available proofs still succeed without treating the unavailable provider as a failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100