keybase / keybase/keybase-issues

Improvements in the process of account verification

Open
#2,377 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I saw a strange thing in the process of confirmation twitter account.
If you specify a user name, but do not send a tweet with confirmation, the link to the user will appear in a profile, despite the fact that the confirmation has not been published on Twitter. I think this may confuse some users.
(I have not tested it with other accounts, but I think it will be something similar)

If you then attempt to verify your twitter account through the keybase CLI, you will get a message like below:

> $ keybase prove twitter
> > You already have a proof for gregsonar@twitter; overwrite? [y/N]

It seems to me, then it takes some improvement - not publish a link to the unconfirmed profile at all, or report that the account is added, but not yet confirmed in terminal too.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the described Twitter account verification flow in the profile and with the keybase CLI command `keybase prove twitter`. Compare the displayed profile link and terminal message before and after confirmation; done means the unconfirmed account is not presented as verified and the CLI state is consistent.

Written by the indexing model from the issue text.

Assessment

Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.