Feature request: proving multiple accounts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
It is common IME for people to have several GitHub accounts.
Unless I'm doing something wrong, it doesn't seem possible to prove several GitHub accounts with keybase at the moment:
$ keybase version
Client: 2.3.0-20180710171051+64615d6258
Service: 2.3.0-20180710171051+64615d6258
$ keybase prove github yyy
You already have a proof for xxx@github; overwrite? [y/N] N
▶ ERROR Not confirmed
However, I think the underlying "management" code is already there, because multiple PGP keys can be added for example: why not multiple GitHub accounts?
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 prove github yyy command and trace the existing proof-management path, including how it handles multiple PGP keys. Determine how multiple GitHub accounts should coexist without overwriting an existing proof, then verify that proving and managing several accounts works as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100