keybase / keybase/client

Unable to track the Twitter proof

Open
#12,875 2 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

Hi,

Below is the proof for user cloc:
https://twitter.com/ChiragLocham/status/1018828526433308678

Kindly resolve.

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 checking the reported Twitter proof URL and the issue's surrounding Keybase proof-tracking flow; no repository file, test, or entry point is named. Done means identifying why this proof cannot be tracked and confirming the proof is handled correctly, with a focused regression test if the relevant test location is found.

Written by the indexing model from the issue text.

Assessment

Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.