4 ms·
> You send a message and it either goes where it’s supposed to, or you get an error message back. That’s it, that’s email. It’s simple. It works. Except when
by Navarr 15y ago
> You send a message and it either goes where it’s supposed to, or you get an error message back. That’s it, that’s email. It’s simple. It works.
Except when you DON'T. Except when the mail server is broken, except when the error message you get is ENTIRELY CRYPTIC.
Email works. That's it. It doesn't work WELL, It just works. That's why it needs to be fixed.
> But sometimes I just want to send a fucking message, not “make a TODO.” Boom, I just “broke” the new email.
Though I think you're fairly right about this one - you're also wrong. You're making whoever you're messaging a TODO. "Read This" Email has become a TODO list, you can't fix that - not without a new mail protocol that takes that into account and separates the todos from the messages. Certainly a client could do this but a client can never ever be smart enough to get it right all the time.
- icebraining 15y agoThough I think you're fairly right about this one - you're also wrong. You're making whoever you're messaging a TODO. "Read This" Email has become a TODO list, you can't fix that - not without a new mail protocol that takes that into account and separates the todos from the messages. Certainly a client could do this but a client can never ever be smart enough to get it right all the time. Separating TODOs from messages reliably can be done using MIME. You do not need a new protocol for that, just define a format and give it a custom MIME type.
- Navarr 15y agoNo but you DO need a new protocol for the mess that is mime types in emails, and the two popular open access protocols IMAP and POP - which are atrocious.
- ori_b 15y agoOr a header. Mail supports custom headers. X-Todo-Item: true Boom. You now have a way of knowing that this email is a todo item.