4 ms·

I like many of the idea's but the real work is thinking how you would use this in practice. For example take some typical scenarios and imaging how they would w

I like many of the idea's but the real work is thinking how you would use this in practice. For example take some typical scenarios and imaging how they would work in this post-SMTP world. (1) I'm talking to someone on the phone and I want to give them my "email address". What would this look like? (2) I sell canned soup in a store and want to put something on the can. What would this look like? (possible a QR code with an identity and a stamp?) (3) How would you go setting up a "mail list" for a club with minimal friction, especially if everyone doesn't have their phone with them.

upofadown 5y ago
The identity here would be based on cryptographic signatures so it would look ultimately have to look like some sort of key fingerprint. For example, an OpenPGP identity contains one or more email addresses. So the fingerprint is all you need to give anyone. In practice this can be provided in the form of a QR code. There is even a standard way to do this. A secure mail list running on a server has to reencrypt the message to each recipent (it has access to the messages). So you would give the mail list server something like a key fingerprint. The original signatures would ideally survive the trip through the server.