keybase / keybase/client

Can't provide Twitter proof, doesn't see my tweet

Open
#3,420 1 comment 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

Providing the logs here. If perhaps I did something wrong, there was no feedback from the app for me to correct my error, so that would be helpful. Or even if this is a known issue, I might suggest that more feedback be provided to the user so we don't get caught in the endless loop of clicking "Y" and then having it not work, with the only option to just say "n" and cancel the process out entirely.

my log id: 6474fa2628332d4ee3aa881c

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

No source file, test, or entry point is named. Start by investigating log id 6474fa2628332d4ee3aa881c and reproducing the Twitter proof flow; done means identifying why the tweet is not detected or adding actionable feedback when the proof cannot be found.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.