The new http://pgpasc.org is up! Check it out, add yourself to the Hall Of Fame and read the all—new PGP guide!
@mxstbr Very cool. Solves one of the biggest issues with PGP. Using similar convention for Pulse Device ID / bios in Heartbeat.
-
-
@aral not sure if it actually does anymore, see the discussion here: https://github.com/mxstbr/pgp.asc/issues/18 … thanks for the support though! -
@mxstbr It can simplify the experience: 1. I write an email 2. My client checks domain of recipient for pgp.asc 3. Boom, I can encrypt :) -
@aral that would be the goal. I have no idea why this doesn’t exist with keyservers/–base already… -
@aral i.e. 1. Write Email 2. Get key for recipient 3. If exists on key servers, encrypt, otherwise show warning. -
@mxstbr Yeah, exactly. I had a huge debate with folks at the Circumvention Tech Summit last year about this. This is the UX issue with PGP. -
@aral if there was an easy–to–use email client that did this, I bet PGP use would immediately go up. -
@mxstbr So I’d say stick with it. Even if we have blockchain-based systems, etc., this would be a good *layer* of discovery to have. -
@aral layer of discovery is a good term for it, because I don’t think it can be a layer of verification, which it sells itself as right now. - 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.