keybase / keybase/keybase-issues
Suggestion: LinkedIn
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Not sure how/whether you'd be able to access verification text remotely, unless it was placed in a user's public profile somewhere (see https://www.linkedin.com/in/peterbance - perhaps a paragraph in the "Summary" section?), but I use LinkedIn far more than any other "social" systems.
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
No repository file, test, or entry point is identified. Start by reviewing how Keybase handles remote verification and whether a LinkedIn public profile, such as the linked profile's Summary section, can provide suitable verification text; done requires an agreed LinkedIn verification design and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100