keybase / keybase/client

Facebook link fails proof

Open
#11,168 0 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

https://www.facebook.com/patrickdevins/posts/10215734611220383

My Facebook proof suddenly stopped working so I created a new link and requested another proof. Reprove seems to still be pending, but I got an email stating that my proof was not valid. The link to my public proof post is above.

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 Facebook proof failure using the public post linked in the issue and reviewing the proof-verification entry points in the Go client. No repository file or test is named, so first locate the Facebook proof flow and its existing tests. Done means the reported proof is accepted or the failure is diagnosed with a clear, reproducible result.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
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.