Search gives non-intuitive results for partial non-usernames
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.18-20161219185928+7868d49
The search (in both GUI and cmd line) gives weird results for partial searches.
This is probably easier with examples:
% keybase search james | egrep 'ill|jwt'
jwt twitter:elzzon
% keybase search jamesa | egrep 'ill|jwt'
illiterat twitter:jamesantill github:james-antill facebook:james.antill http:://www.and.org
% keybase id jwt
▶ INFO Identifying jwt
✔ public key fingerprint: 4B8D AA7B CA0F 3016 D5E9 942C B083 FB0E F609 051B
✔ "elzzon" on twitter: https://twitter.com/elzzon/status/695473558743605248 [cached 2017-01-16 13:31:37 EST]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two keybase search commands in the issue and compare their results with the corresponding keybase id lookup. Trace the search entry point used by both the GUI and command line, then identify the intended behavior for partial non-usernames. Done means the same partial-search cases no longer produce the reported non-intuitive matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100