keybase / keybase/keybase-issues
Twitter proof fails
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I'm having problems verifying my twitter proof.
I realised that my existing proof (which worked in the past) wans;t recognized by Keybase any more.
The tweet was still there though.
So I created a new one but still it can/t bve found.
Is there a known problem?
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing verification with the existing Twitter proof and the newly created proof, then inspect the Keybase proof-verification entry point and any related logs. Done means identifying whether the failure is caused by Twitter retrieval or Keybase recognition and documenting a confirmed fix or actionable diagnosis.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100