keybase / keybase/client

All twitter proofs show as unreachable, but proof posts remain up

Open
#24,397 9 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

Every person I follow with a twitter proof shows as unreachable, and many I ask report the same.

The proofs are still on twitter and can be viewed from the link on someone's profile.

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 reproducing the report from a Keybase profile with a Twitter proof, using the proof link to confirm that the post remains viewable while the proof is marked unreachable. Trace the proof verification entry point and determine why valid, accessible proofs fail; done means current Twitter proofs are reported as reachable.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.