keybase / keybase/keybase-issues
Bios can contain URLs
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
As of this writing, https://keybase.io/agl contains just a public key with no completed proofs.
An unsuspecting user might look at this page, see "https://www.imperialviolet.org" in the bio and read it as a website proof. I don't know if this user is actually Adam Langley, but I note that this user has 10 trackers despite having no identity proofs, which might reflect legitimate confusion.
I would feel better if the user page clarified that the statements of bios, including URLs, have not been validated in any way. It may be worth prohibiting URLs in the user information for this and other reasons. I would also feel better if there was a note explicitly stating "this user has completed no identity proofs" for such users.
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 reviewing the user page and the way bios, URLs, and identity-proof status are presented. Done means the page clearly distinguishes unvalidated bio statements from completed proofs and reflects an agreed decision on whether URLs should be prohibited.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100