keybase / keybase/client

Twitter proof not detected

Open
#18,767 2 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

Hi,

I did post it, twice actually, deleted the first one and tried the next day, but it didn´t work, I received an email asking to create a ticket here, could you please help? thanks!

image

https://twitter.com/royzumbado
@royzumbado

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 with the issue report, its screenshot, and the linked Twitter account; no source file, test, or entry point is identified. Reproduce the failed Twitter proof flow and trace the existing proof-detection path, with the issue resolved when a valid proof is detected or the failure has a documented cause and regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
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.