keybase / keybase/client

Twitter/X and Reddit proofs are no longer working

Open
#27,225 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

Hi Keybase team!

Currently, if you redo or add a new Twitter / X proof, Keybase can no longer detect it properly.

Here is my proof: [https://x.com/YourOnlyONEofcl/status/1810223880948125851](https://x.com/YourOnlyONEofcl/status/1810223880948125851)

It's the same with Reddit, a few weeks ago it just broke and it can no longer find it.

Here is my proof: [https://www.reddit.com/r/KeybaseProofs/comments/6f02jd/my_keybase_proof_redditlaibcoms_keybaseyukino/](https://www.reddit.com/r/KeybaseProofs/comments/6f02jd/my_keybase_proof_redditlaibcoms_keybaseyukino/)

Thank you!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue with the linked X and Reddit proofs and trace the proof-verification entry point in the Go client. Done means newly added or redone proofs from both services are detected correctly; the issue does not name specific files or tests.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.