keybase / keybase/keybase-issues
third-party verification api
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
It'd be cool if keybase supported some sort of API for allowing sites to support verification.
Keybase would have a verification option where you supplied your username, and a link to the site's location for the api. Keybase would query that api with the username, and the site would return the user's proof. This way, keybase doesn't have to implement each site manually, instead allowing the sites themselves to support keybase.
The query would look something like this:
`GET https://domain.name/kbapi/proof/`
to which the site would respond with the same file that would normally go in `.well-known`.
Because the api would not require any authentication (it only serves static content), the proofs would be available to everyone.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the proposed GET /kbapi/proof/ endpoint and the existing .well-known proof format described in the issue. Define the API contract, verification behavior, and integration scope; done requires an agreed design because no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100