Re:How to fix email while still keeping email
by lucian1900 on Sunday April 15, 2012 @06:37AM
(#3843353)
Actually, email as a standard is horrific. It would be worth the effort to replace it just to move to something more consistent.
> If you want JSON messaging included, you could build a client that reads that specific MIME type and interprets it differently than other messages
This is literally what I suggested in the article.
Re:How to fix email while still keeping email
by sliverstorm on Sunday April 15, 2012 @03:27AM
(#3843080)
The only properly-focused criticisms of email I've read go along the lines of "Email is uselessly robust". I don't personally agree, but what I'm getting at is I agree with your message. E-mail is fundamentally a messaging infrastructure; do with it what you will. If you don't like your inbox filling up- that's not an inherent flaw of RFC-5321 (and related RFC's).
We don't need to add more cruft to email itself. If you want to create extra protocols for doing different things using email as a medium, go ahead. Email is extendable, as Microsoft, Gmail, Xobni, etc have shown.
Long story short, you can do whatever the hell you want with email. It's not perfect, but it's a really great messaging framework. You can send any message you like, to whomever you like. How the recipient interprets that message is up to them (ie their client).
EDIT: just wrote this up since I'm sick of repeating myself: http://blog.killtheradio.net/technology/email-is-not-broken-...