keybase / keybase/keybase-issues
Feature request: verification through LinkedIn
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'm thinking that one way to make key base.io more visible might be to appeal to audiences outside the core reddit / hacker news / developer that current verification appeals to. LinkedIn might be a good place to get such broader appeal. While there's no easy place in a linkedin profile to add a signed block for verification, it may be possible to use the Advice for Contacting part of the profile, or even (gasp!) stegging the signed block into the profile image (though that would take some guidance for many users). So, though I'm not sure the best way _how_ to do it, the _what_ of the feature request sounds simple...
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation files, tests, or entry points are named. Start by clarifying which LinkedIn profile mechanism should support verification and how it would fit the existing Keybase verification flow; the issue is done only once the supported workflow and acceptance criteria are defined.
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