keybase / keybase/keybase-issues
Account Problems
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I got in to some account problems.
I registered my first time with my username: dschense
I played with the settings and the certs and got some problems with them. After that i wanted to reset the Account to start from scratch. But i locked the account because of old PGP-certs.
I got something like this:
"eldest called on user with existing eldest KID"
"add a PGP key" via website doesn't work. I tried both "I need a public key" and "I have one already"
After reading a lot i got the hint to delete my account and register it new with one more invite. So I did.
But after deleting the account I cant register it new with the same name because the system tells me that the nick (dschense) i want to take is already taken.
So I registered a new Account (jens_walser) and tested the stuff what was wrong. Now I know what i did wrong with the testing account.
Now my question is:
Is it possible to delete the account "dschense" completely from your system so thats possible for me to register again ? I just need one account and this one with the right user name.
Greez
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 by reviewing the website flows for account deletion, registration, nickname availability, and PGP-key settings described in the report. Reproduce the behavior with the affected account states if possible, then determine whether a deleted nickname can be released and how the reported errors should be handled. Done means the expected account and nickname behavior is confirmed and covered by an appropriate change or documented resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100