This is brilliant in its simplicity. It would be very feasible to implement on a single web server, but what are some ways to extend it into a protocol?
If multiple servers mirror an email thread, how does one edit what he has already sent/posted? I think this can be done by using a public key encryption scheme, so that only the person who published it with their key can edit it on the multitude of servers that share this new email protocol.
We are developing external and internal communication tool that has all the features that you have described.
It called Discourse - http://www.discoursehq.com
We are releasing new version on 3rd of October that is more flexible and generic then current one - if anyone would like a beta invite please let me know!
I have no idea what you are talking about. I thought that TC was about hardware enforced binary signing. TPM could store encryption keys so it might somehow be applicable to managing e-mail identities, but unsend? I can't figure how it fits to the picture.
10 comments
[ 3.3 ms ] story [ 25.4 ms ] threadIf multiple servers mirror an email thread, how does one edit what he has already sent/posted? I think this can be done by using a public key encryption scheme, so that only the person who published it with their key can edit it on the multitude of servers that share this new email protocol.
As far as outside the corporate environment, the reason email persists is:
1) Email is robust
2) Email is distributed, and not controlled by any one entity
Email is almost like the bittorrent of communication, at least in my mind.
How could I prove that you wrote me what you wrote me in the first place if you could edit your email after I received it?
Email is not facebook, people.
The article says that e-mail is not Facebook/Google+ and that this is a bug.
We say that e-mail is not Facebook/Google+ and that this is a feature.