keybase / keybase/client

Unable to authenticate twitter account with leading _

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

I was unable to authenticate a twitter account with leading "_" character. When I changed my twitter public name from "georgeteo" to "georgeteo", authentication suceeded.

Steps to reproduce:

  1. Change twitter account name to something with leading "_"
  2. Revoke twitter proof if necessary
  3. Attempt to prove new twitter account name with leading "_"

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

The issue names no files, tests, or entry points. Start by reproducing Twitter authentication with a username beginning with an underscore, then locate the authentication path handling the Twitter proof. Done means accounts with leading underscores can authenticate successfully, with regression coverage for that username format.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.