keybase / keybase/client

how to nuke accounts?

Open
#7,977 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

as described in #184, accounts can be nuked.
How can this be facilitated?

For the scenario:

  • The User has no access to the email account associated to their keybase username
  • The User does know it's email address
  • The user doesn't have any authenticated device or none which the user could login

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

Start by reviewing linked issue #184 and the account-nuking behavior it describes. Determine the supported recovery path for users without email access or an authenticated device, then define acceptance criteria for facilitating it; the issue is done when that path is implemented or explicitly documented.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.