search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
900 stars 37 forks source link

Feature request: verification through LinkedIn #1852

Open davearcher opened 8 years ago

davearcher commented 8 years ago

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...

DeftNerd commented 8 years ago

I would love LinkedIn too. One possibility is that in your LinkedIn profile, you can set up to 3 website URL's. Maybe linking to your keybase URL would be good enough? Like you said though, it isn't a signed block.

blakev commented 8 years ago

You could easily add a regular expression in your summary, which is publicly visible, that contains a verification SHA like the twitter handler.

<<keybase.io:blakev:MxBpC7PxksZuISjW2JvH-y2VDQZXkFOBzogn>>

awakeman commented 8 years ago

linkedin has "updates" (think faceook status updates) and "posts" (basically a blog post), both of which can be set to be published publically. The standard method could be used here easily enough.

svanzoest commented 8 years ago

Related/dup of #1115