TL;DR:
"Social Websites" should add fields for public crypto keys such as GPG.
Problems:
* no easy way to communicate securely with random people on the internet.
* PGP, GPG etc... rely on people signing each others' keys, which doesn't work if there is no "network overlap" between you and the person you want to communicate with.
* there are public listings of keys, but anybody can publish a fake key, that is why you are supposed to rely on key siging (and remove old keys). e.g.: These are obviously not all RMS': http://pgp.mit.edu/pks/lookup?search=richard+stallman
* in 2015, alt/internet identities are sometimes as important, if not more, than real human identities. I don't care who's behind a github repo, still I might need to communicate securely to them about a security hole in their code.
* it's a big world, I often want to communicate with people I have never met and with whom I have no "network overlap".
* existing attempts at solutions obviously aren't working. I have invited all my friends, their dogs, and their cats to https://keybase.io, less than a handful have added their key to it.
Solution:
"social websites" should add fields for PGP/GPG and other crypto public signatures. Any website that has user ids that are now considered as internet identity should add these, so HN, reddit, twitter, lobste.rs, linkedin, google plus, facebook etc...
Some already allow for ssh public keys (e.g.: https://api.github.com/users/dorfsmay/keys, and you cannot encrypt a message larger than the key with an ssh public key in case you wondered), why not add other keys? This should be simple.
(I agree, direct support instead of going over a central page would be nice, but I don't think it would do much to fix adoption)