4 ms·
>We fix it by building smart clients. If you allow me to pick an interesting remark from this post: I think the idea of embedding instructions in the payload o
by evaneykelen 15y ago
>We fix it by building smart clients.
If you allow me to pick an interesting remark from this post: I think the idea of embedding instructions in the payload of an email is an interesting one. For instance an email could contain text and a link to a Pivotal Tracker story while at the same time it could contain a JSON payload which tells my augmented email client to render the story and allow me to interact with it. The post makes a good point in that email as a protocol is not broken but that the problem lies with today's email clients.
- 7952 15y agoI agree that payloads are an interesting idea; but would be a security nightmare. As soon as you load a URL based on an email, you are leaking information to the sender. You could restrict the types of content, but all you end up with is RSS.
- evaneykelen 15y agoIt could be implemented in a secure way, without using a URL as you mentioned. The email client could support plug-ins (Thunderbird does I believe), the user would authorize the plug-in to connect with his Pivotal account and the data inside the JSON payload would be used to render a Pivotal story. With other words: an augmented email client could do things with payloads inside emails that are far beyond what email clients do nowadays and I believe it can be done in a secure manner.