keybase / keybase/client

Addendum: Common technical questions about keys on Keybase

Open
#8,218 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

On adding a new device or creating a paper key a notification email is sent out with an addendum:

Addendum: Common technical questions about keys on Keybase

[...]

What happens if I wipe/restore a mobile install of Keybase?

Our mobile app isn't ready, but we're answering this in advance.

Your keybase keys are never sent into iCloud/Google backups, which is cool. But that means you'll need to provision all over again, whenever you reset & wipe a phone, or buy a new phone. Keep that in mind and make sure you have a computer with Keybase installed or paper key handy.

I just installed the keybase mobile app, so I think the mobile app is ready and that sentence should be removed from the addendum.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the notification email template containing the “Common technical questions about keys on Keybase” addendum. Remove the sentence saying the mobile app is not ready, then verify the generated addendum no longer includes that outdated statement.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.