keybase / keybase/keybase-issues

Newly proven account triggers suggestion to track someone I already track

Open
#1,737 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Here's what happened:
1. Followed a user on Twitter who had not yet proven their Twitter identity for Keybase
2. Tracked the user on Keybase
3. When they proved their Twitter identity on Keybase, I received an email with the subject, "@ on twitter (your friend) just signed their account," containing the text, "You follow @ on twitter, and now you both have public keys on Keybase, with signed twitter connections. This is cryptographic utopia! You should consider tracking them, which commences a signed record of their public key and identity announcements. ..."

The problem is, I already track this user on Keybase. Before sending these emails, a check against the list of already tracked users should be performed.

Contributor guide

No contributing guide indexed for this repository

Research direction

Trace the account-proving flow that sends the Twitter identity email and inspect how existing Keybase tracking is represented. Reproduce the sequence from the issue, then verify that users already being tracked no longer receive the suggestion email while newly tracked users still do.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.