keybase / keybase/keybase-issues
Support for secondary email ids
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
During sign up, there's no way to add any other email id apart from auto-generated userid@keybase.io. And my messages to userid@keybase.io aren't being sent through, despite both me and recipient tracking each other. This then leads to downloading and opening up the GPG Suite (in Mac), and manually modifying the keychain to include email address already being used. This step is too technical for the target keybase.io crowd (none of my friends did it).
Also, this doesn't play very well with Mac Mail integration of GPG suite, which automatically encrypts messages to an email address if a public key is found in the GPG Keychain. So, now one has to manually encrypt messages and copy paste them etc.
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
The issue does not identify any files, tests, or entry points, so begin by locating the sign-up flow and the Mac Mail/GPG Suite integration. Done should allow a user to add a secondary email address and use it for messaging and encryption without manually editing the GPG keychain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- authentication, desktop, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100