keybase / keybase/keybase-issues
Uploading a public key could be clearer
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
INTRO: I'm fairly new to encryption and keys. I've had my keys for a while now but haven't really used them, because there isn't much code for me to sign, and I don't know many people who have keys to trade. But I find the concept of keybase really interesting and appreciate what it could do if it grew. Coming from that background I haven't shared my key with anyone and so, as a new user, I was a bit confused when I went to upload my pubkey. The site really helped me with commands to use in the CLI. I read up on the commands and learned a lot, but when I had gotten my key and went to copy it to the popup on the site I didn't know what to paste.
What I would like: In the popup where I pasted my public key I would have been helped if there was a text telling me to copy the entire output of the gpg command. I't wasn't obvious to me if I should include the start and end message and the version. I had to go look at other (allready uploaded) keys to see how they looked. For me as a new user that text would have been helpfull.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the public-key upload popup in the Keybase website and review the existing GPG command guidance. Update the popup so users know to paste the entire public-key command output, including its beginning and ending markers and version information; done when that instruction is clear before submission.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, design
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100