A ‘frighteningly ambitious’ way to improve email
thenextweb.com
thenextweb.com
I think the actual solution will turn out to be something like this http://en.wikipedia.org/wiki/Internet_Mail_2000
The important difference is that the master copy of the email resides at the sender, which means it is possible for them to update and revise it. With current SMTP the moment send is hit, the message is gone which is why band aids like this inboxpro approach exist.
For example I could imagine adding a header to emails that gives a canonical url for it and some cryptographic information as well as the original body. If the recipient is using regular SMTP and mail clients then things remain as today. If they are using the new system then the recipient client can make requests for updates, give queue time information, ask for tagging etc and automatically reflect those changes in what it shows.
There are systems with retraction capabilities for senders (e.g. Bloomberg MSG, though it is no competitor on price). But I haven't seen anything like a system which would downgrade messages already seen by others, etc.
But then why call it frighteningly ambitious or ambitious at all?
Anyway, I'm always more impressed by people who can do great things within the confines of established procedure. It isn't nearly as hard to differentiate when you start from scratch.
I implied for the title of the post (given by OP) being opposite to what impressive is within confines of established procedure. No?
Presumably the system would only kick in for threads of discussion initiated by others and not yourself. So if you send an email, any replies to it would behave as normal.
However, I have to strongly object to the expired emails feature. The worst part about being an entrepreneur are the people that never reply back. Not a yes. Not a no. Rejection I can handle. But the people who stop responding or never responded create a lot of heartburn in my life. And the same goes for trying to maintain a social life. Having an acquaintance or new friend never respond to an invite for coffee or a beer is incredibly frustrating.
Any system that would increase the number of emails that go unresponded to is a bad system.
How about instead, you reply by saying "too busy right now, maybe check back with me in 6 weeks?" I've found that cuts down dramatically on the number of unwanted requests. People that really care will check back. Others won't. And you can always escalate the rejection from there.
> The email will disappear into the ‘Expired’ box and the sender will receive a friendly notification that they can move it back to the queue, change it to a different format, or delete it altogether and maybe just give me a call
While I don't agree with this particular "frighteningly ambitious" take on the issue I do agree with that the above quote represents an issue that needs solving. In my opinion, forcing the sender to conform their email to a format of your choosing simply isn't scalable. The reason email is so well used today is because it's so simple to use. This adds a layer of complexity to the people trying to communicate with you that I think would just lead to fewer people attempting to communicate with you (which could in fact be what you want).
I've spent some time building my own "frighteningly ambitious" solution (I'm actually planing on doing a Show HN on Monday or Tuesday). Essentially, the idea is that right now it's the people emailing you that control your inbox. Our solution is to give users control over when and from whom they receive email. It puts you in actual control over you inbox for the first time. For those interested check out https://lightermail.com. Would love to get your opinion.
And frankly if you want to contact them, this kind of velvet rope is precisely what they want.
Granted, the emails were all sent from a shared hosting account, the mail server of which I had no control over as far as certificates and reputation were concerned. But my feeling is that anything I could have done to improve my Xmas greetings' success rate would have been exactly what spammers also try to do.
Aggressive filters assume everyone is a bad actor until proven otherwise, and I think that's a problem. Our quality of life is degraded whenever we make this calculation.
Having said that, I still signed up for the beta. Because I'm a primadonna.
I would love to see a system that does automatic spam classification (like gmail), but if you get auto-classified as spam, then you get the challenge-response, as a last ditch effort to get through the spam filter.
This is why it's generally bad practice to reply to an email telling the sender it is spam.
It depends on what you prioritize. I prioritize avoiding false-positives, so my spam filter of choice reflects that.
My current spam system (spamstopshere.com) does return bounce/reject messages depending on what filter the email triggers.
As for the original idea, backscatter is to be avoided at all costs. Nobody likes bounce messages and so forth for mail they never sent. Much better to reject mail at SMTP time, than generate backscatter to the alleged envelope sender after the fact.
I get a lot of spam, so manually reading a spam folder is not a feasible solution.
Thank you "motherpowers" for sending the email titled "Happy Birthday" to "leepowers". For a faster response time please re-formulate your birthday greeting as a series of yes/no questions and re-send.
So being able to whitelist senders would be a requirement.
My dream is that in a few months I will open my Inbox Pro app in the morning and answer 20 Yes/No questions using just my left thumb...
I'm not sure what this would accomplish. Reading and comprehending email is not difficult. The difficult part is thinking through an inquiry and responding intelligently. "Can we move up the launch date a week?" This is a yes/no question that anyone can understand. But actually exploring an answer to this question can require considerable mental effort. There's very little utility in having this message display in a slightly different format with a checkbox.
Then again, it doesn't fully accommodate the way I use my work email, personally. I'm on a number of mailing lists at work where I don't personally respond to most of the email --- but I read a lot of them anyway, in part to keep abreast of what's going on, and in part to be able to exercise my own judgment about whether I should jump in. That's an awkward fit for a workflow that assumes that every email calls for some kind of response.
--Please feel free to ignore the following email rant.--
Email is a pretty impressive digital translation of the written letter. And for cases where a letter written by hand on paper would work well, email works even better. As long as by better you mean faster and without paper or stamps or penmanship. The SMTP protocol is over 30 years old and still going strong; that's pretty amazing. But email kind of sucks, too.
Frankly, most people aren't good at writing letters. Simply creating a meaningful subject line is difficult. And keeping a conversation germane to the stated subject is also difficult; folks often talk about multiple topics in a typical conversation. To review long conversations, one must read awkwardly from bottom to top, opposite normal English reading direction. Adding someone to a conversation in progress is also awkward. Sending another message (a correction or addition to your last message) before the person (or people) you're talking with replies creates confusion as a reply can only be made to one or the other message, dropping parts of the conversation. Attachments can be problematic. Clearly, spam the likes of which we see today was never anticipated by SMTP's authors, and neither has anyone come up with an especially successful solution to it. We've all just come to accept spam as part of the background noise, filtering the polluted stream, rather than removing the decomposing carcasses from the upstream source.
Creating an alternative that addresses its shortcomings would be ambitious. And I think many people were frightened by Wave, which addressed many of email's shortcomings but was disruptive in the way so many people like to claim they admire but will almost always shun in practice (kind of like how folks always claim to love to root for the underdog, unless it's Haiti). I'm not saying Wave was perfect, but it had great potential. And as far as genuinely ambitious attempts at improving email (or the kind of conversing we typically do with email), I can't think of another example.
I say abandon "fixing email" and come up with a new solution altogether. Start with a clean slate. Form a coop or nonprofit foundation that will control the standard for 5-10 years until everything's ironed out, then release the source code so people and providers can use it to replace email and people don't have to depend on one group of people. At this point I'm willing to try anything, as I'm sick of email, I HATE it with every fiber of my being. Spam and delayed newsletter bombing is taking up hours of my time each week.
And the cost in bandwidth and wasted time email and its spam problem impose on us cannot be understated. We really do need something new.
The idea that you could come up with an alternative messaging solution is beyond silly. Why would people use it? Any migration would require both systems to run in parallel but unless the new system incorporated every feature of the current email infrastructure people would simply not bother. And if it incorporated every feature then the abuse would migrate over too.
Better skeumorphism of mail? Sure, like refactor and split mail from postage parts completely? Chris, can we connect with you over email? (the irony, ha!)
[Disclosure: I work for the project linked above.]
If you let a coder (or, *shudder*, a user) specify the importance of her alert,
give her a little pull-down menu that has choices ranging from "nice to know" to
"white-hot urgent," and nine times out of ten, she'll choose "NOW NOW NOW
URGENT ZOMGWEREALLGONNADIE!"
- Cory Doctorow, EpochInterestingly enough, the average response time for a yes/no question is by far the longest (5 days vs 3 days for a long email).
Shouldn't responding to simple yes/no be much faster than reading a long message?
There is also a emotional aspect in terms of everybody being told very explicitly that they are not important enough for an immediate reply.
In the worst case, a sender gets a message saying "that email you sent to Tom last week has been auto deleted. You can resubmit and maybe Tom will adress it later". It might be the honest truth, but I can't imagine a lot of people, especially customers or managers, would enjoy such a message.
As mentioned there is interesting elements, but ultimately it seems too engineer oriented and with a bad user experience for senders.
One of the problems with emails is that the sender don't understand what is happening to the receiver in terms of added work to perform, so this adds the feedback needed to the system.
About the "expire" feature, it is a lot of time I think gmail should have something like that. "Sorry this email remained in the user inbox for N days, the user was not able to reply so please send it again if it is important, or make it shorter and easier to reply for the user by improving it".
Btw I'm part of the problem as I tend to write very long emails. That's the issue. Emails should be short, and conceived so that the sender will have an easy time to reply something meaningful using a small fraction of his/her time.
That's probably more of a cultural problem than a technological one. However when I realized email was going to kill my productivity I stopped replying to most of the messages that hit my inbox.
I wonder if this could be useful here.
http://www.telescopictext.com/ (Context: https://twitter.com/rgherrmann/status/300311324905324545)
It would definitely have to be automatically generated to be viable, as in no more effort than to write a normal long email. But doing that automatically is a hard problem.
Hmmm...I use gmail to filter stuff I don't really need to read right away ("filter messages like this"), and priority inbox is specifically to find the email you really want to read between all of the other stuff. Why straw-man the competition?
In any case, there is definitely room for email "types" (tags, labels, etc.) that can be implemented in custom x-headers and then get added to the right inbox/queue.
The communication back to the sender is an interesting thing though. If the sender is using something like this, and they autorespond...
Ultimately I think the real solution is a personal assistant.
Another approach to the problem of huge volumes of mail is to classify your senders at the point of contact by giving them different email addresses. That lets you check one mail address frequently (for close and valuable contacts only), and one email address every few days (for casual contacts, website contact, mailing lists etc), and only give out the important email to those whom you trust to use it appropriately (i.e. never publish it). This helps considerably to cut down volume which you see every day.
Email's strength is that it is a distributed free-form medium which can contain any sort of content. Trying to enforce structuring content with simplistic templates like this is just wasting the sender's time instead of yours - why give them the email address in the first place if you don't have time to read and respond properly? Why not have a web form which imposes structure and emails you the result, or an FAQ on a website?
While I agree there are huge problems with email as it stands, I'd say they're more to do with identity and sufficiently sophisticated semantic processing of incoming mail for those who receive a lot of it, not with the structure of email itself (which is admirably simple and has served remarkably well), or lack of hints as to contents (NB any such hints in the control of senders will be abused mercilessly by spammers).
If this were true, the solution would be dead simple - stop reading email.
The problem is that not all email is created equally. There are some emails that are incredibly important and most that are not. The problem is that it's impossible to sort it ahead of time.
More to the point, I like this idea. I like that it focuses on the perspective of those who send you emails. I feel that many people trying to solve this idea would look to changing how inboxes handle messages or look to changing the user interface of email systems.
But instead, this solution actually helps reduce email by responding to senders. That's a unique approach. Very out of the box.
But it's true that it's "frighteningly ambitious" to try and tackle this problem on the sender's side. I could see this failing if the majority of senders are the type to simply send off an email and not check for a while, which would ignore the automated message query. However, if a majority of users do pay attention to it, they can edit their email options and hopefully make life easier for the receiver.
Excellent idea. I hope it develops into a full startup.
I 'invented' it… :-)
This solution would seem to work in cases when the recipient has the power in the relationship. But what about the other X% when he's the underling? Wouldn't the cost of pissing off those individuals outweigh the benefit of increased productivity?
In other words - it can probably work for Bill Gates, but not for the rest of us.
In fact, that is what I did with every investor and journalist that emailed me. I replied to most within minutes.
Consider, instead, a pull notification system. The first time a sender emails the recipient they are sent a link (also in the recipient's signature) to a page providing expected response times for various email forms along with the option to convert your already-sent email into a short-response form, e.g. yes/no.
This is pretty much what Inbox Pro already does, no? I tested it by sending an email, and got an automated response:
> Hi [my name],
> Your email is #85 in Boris Veldhuijzen van Zanten's inbox. You can __optimize your message__ so it will be easier to answer.
Clicking the link leads to a webpage showing average response times for Yes/No questions (5 days), Short questions (I think 14 hours?), Long questions (3 days), and FYIs (3 days). I converted my message into an FYI and submitted it.
I think the only difference in what you proposed is your version limits it to "the first time a sender emails the recipient", while this system would presumably give the same treatment to future emails from me.
I've read about a very similar phenomena over at http://en.wikipedia.org/wiki/Attention_economy.
"One way this might be implemented is by charging senders a small fee per e-mail sent, often referred to as a "Sender Bond." It might be close to free for an advertiser to send a single e-mail message to a single recipient, but sending that same e-mail to 1000 recipients would cost him 1000 times as much. A 2002 experiment with this kind of usage-based e-mail pricing found that it caused senders to spend more effort targeting their messages to recipients who would find them relevant, thus shifting the cost of deciding whether a given e-mail message is relevant from the recipient to the sender (Kraut 2002)."
In many work environments email is used to shuttle the responsibility for tasks between people. We've all felt that relief on sending an email. You feel like you've performed a valuable task, made some progress in work that may have very few visible milestones. As the recipient we tend to take the same view and feel as if each email adds to our list of work. Some imaginary clock starts ticking when you receive the email and stops only when you reply.
I think the first thing you need to do is remove the implied hand-over that comes with and email. Remind yourself that just because the sender sent an email, it doesn't mean you must do anything about it. Take a step back and think about what it is you need to achieve and then look to your email to support those activities.
If it were my project, I would now brainstorm and focus on how to make the User Experience better on the Sender end. He mentions that he plans to eventually have an iPhone/Android App (aka UI of some sort on the Senders End), which I think is a 'must' in terms of facilitating a good User Experience for the Sender.
http://img267.imageshack.us/img267/3313/imagekm.png
Give more power to benevolent senders. I've had similar thoughts.
I don't want to waste other people's time, but the current email protocol forces me to. There is no way to specify if your email is...
1. "Check this out sometime during the week, it's funny stuff, if you have time. You need a 24"+ screen and 10 mins, so don't even look at this email on your phone"
2. "I NEED A REPLY ASAP, ARE YOU THERE?"
It appears as a (1) on your phone and I have no power over that to make things easier for the recipient... (other than perhaps send an email at a specific time which is less likely to interrupt your work)
But basically every e-mail client implements some kind of Priority/Importance header, that solves your problem. Nobody uses it though, and the few times someone decides to set "high priority" it might be in their opinion but not in mine. A more complex system won't see more adoption.
For all #1 items, IM the link. It is temporary, and ephemeral.
For all #2 items, email them.
Email clients could offer instant messaging style interface for this kind of messages. Instead of seeing list of subjects, then selecting a message etc you would directly see the actual question and just answer it.
Screenshots to brad@thenextweb.com would be greatly appreciated. This is definitely not the experience we want you to have on our site.
iPad 3. I think, what it is, is that the grey sidebar had your "TNW" logo with some fancy left-to-right fade-in effect, which cycled around again and again while it was caching data. Not meant to be a flash, but that's what it amounted to. Now, it just stays grey until it loads. Thanks for changing that.
Still annoyingly takes up 25% of the screen and doesn't let me zoom.
http://prezi.com/w5if2h-bcbcd/ncsu-noemail-why-you-couldshou...