News for hackers. Stuff that matters.
Re:Email is not broken: It’s a framework, not an application by tferris on Sunday April 15, 2012 @05:22AM (#3843228)
Couldn't upvote this more.

I am fed up with posts telling me email is broken and a new disruptive tech will be the cure. Email is an open protocol, decentralized, providing optional security.

Shortcomings—or rather call them additional requirements—can be solved with tools keeping email focussed on async text-based communication. Want to send large files? Dropbox. Want more automation? Improve the client side and/or write scripts. Want less spam? Don't distribute your address or sign-up everywhere.

If you don't like your inbox being a todo-list you should change something—maybe your job, profession or your work environment but it's definitely not email. I have got rarely todos in my inbox.

For me, email is—if you mind a set of rules—an efficient way of communication which is documented. You can easily and asynchronously discuss and agree on topics in a transparent manner with one or more participants, again: with an open and decentralized technology, no middleman anywhere. Sometimes obviously it's better to meet folks face to face.

Now tell me, which tool can do this? What do you want to improve?

This whole email is broken thing is just done for the sake of getting attention, making a lame conference presentation "disruptive" or getting some crappy todo app funded.

Re:Email is not broken: It’s a framework, not an application by sbov on Sunday April 15, 2012 @10:20AM (#3843736)
Agreed:

Anyone who claims "email is a bad TODO list" is an email problem is missing the forest for the trees. This isn't an email problem. It's a problem inherit in any communication medium.

If you sit in an IRC channel that can become a TODO list too. For snail mail, the coffee table you throw everything onto is a TODO list. For people who receive a lot of phone calls, their voicemail is a TODO list.

Re:Email is not broken: It’s a framework, not an application by icefox on Sunday April 15, 2012 @09:26AM (#3843640)
> Want less spam? Don't distribute your address or sign-up everywhere.

Around 1999 or so I noticed someone trying to send spam to every common name on my mail server. I had never given out my email address and yet here I was getting spam just because I had a server. Even if I heavily obfuscate my email address on my website such as with this hack http://icefox.github.com/js_email_link_hack/ I would still get spam because this attack vector.

Re:Email is not broken: It’s a framework, not an application by flogic on Sunday April 15, 2012 @01:30PM (#3844137)
Yeah you can't really avoid spammers getting your address. That said, it's pretty much a solved problem.
Re:Email is not broken: It’s a framework, not an application by ams6110 on Sunday April 15, 2012 @01:14PM (#3844109)
Something like fail2ban could deal with this.
Re:Email is not broken: It’s a framework, not an application by Jamiecon on Sunday April 15, 2012 @11:24AM (#3843856)
This.

Only partially related, but I'm sick of people coming up with more, 'better' ways to communicate which are then embraced by a subset of my friends and colleagues. My email arrives on my phone, on my laptop, on my (and any) PC, in an easy to read, indexable, exportable and simple format, wherever I am in the world, in near real time. I have had the same email address for ~ 12 years and with Google's spam filter I get zero spam. I actively manage mailing list subscriptions and have no problems there either.

Seriously, for people asking where their jet pack is - take a step back and think about all of that.

It's infuriating for me that my friends choose to use Facebook, Twitter DMs, any number of 'groundbreaking' proprietary messaging apps and a million other message transports (don't get me started on iMessage). Email is a message, in text format (with optional binary attachments), between a number of people. Nothing more, nothing less.

The world has bigger problems to solve.

Re:Email is not broken: It’s a framework, not an application by steeleduncan on Sunday April 15, 2012 @10:53AM (#3843793)
A glut of "email is broken" posts just before the YC decision day and just after Paul Graham's "Frighteningly Ambitious Startup Ideas" essay smacks of insincerity.

I can imagine email software that does exciting things with JSON data in emails, but I wouldn't alter the underlying protocol.

Re:Email is not broken: It’s a framework, not an application by fluorid on Sunday April 15, 2012 @11:18AM (#3843842)
Great post and we found the hidden agenda of this "email is broken" propaganda. It's sad that the VC/startup business heavily relies on hype to drive interest and valuation.

Nethertheless, I welcome that seemingly a lot do not blindly follow this BS.

Re:Email is not broken: It’s a framework, not an application by protomyth on Sunday April 15, 2012 @01:32PM (#3844141)
> Want less spam? Don't distribute your address or sign-up everywhere.

Quite a lot of spam isn't my e-mail address on mailing lists or sign-ups, it is people I know getting a virus or downloading an app that uploads their address book. I have an e-mail only used with friends that gets an amazing amount of spam (not a common name).

E-mail has problems because it isn't one thing. E-Mail is SMTP, IMAP, POP3, and whatever weird thing Exchange is doing.

I really don't see a replacement since we seem to be in the "closed system" stage of social media much like we once were in the same stage with e-mail (e.g. MCI could not send e-mail to AOL). Variants of IM might have worked but the open versions really didn't make it to everyone.

Re:Email is not broken: It’s a framework, not an application by defdac on Sunday April 15, 2012 @06:06AM (#3843304)
Thanks for this. I had a hard time articulating why email is not broken, and you pretty much sums it all up.
Re:Email is not broken: It’s a framework, not an application by oskarth on Sunday April 15, 2012 @06:20AM (#3843327)
Email was not designed to be used the way we use it now. ...my inbox is a todo list, and email is the way things get onto it. But it is a disastrously bad todo list. ...it seems unlikely that people in 100 years will still be living in the same email hell we do now. And if email is going to get replaced eventually, why not now? ...some of the most powerful people are all at the mercy of email too. [1]

Your posts reminds me of someone arguing to keep the oral tradition going instead of switching to writing.

I am not saying anyone has suggested anything close to the equivalent of writing, but there is definitely a fundamental problem with email that can't just be solved by a couple of perl scripts and rules. I would also assume one's career choice is a premise for making better tools and protocols - anything else seems kind of backwards. If the president was forced to work in a public market space, would you tell him to change career if he remarked on how he couldn't get anything done?

There is a difference in saying email should be killed forever and that it should be replaced by something else for certain usages, just as twitter and Facebook replaced portions of email. Incidentally though, such a replace could likely render email useless for many people.

1: http://paulgraham.com/ambitious.html

Re:Email is not broken: It’s a framework, not an application by vog on Sunday April 15, 2012 @08:10AM (#3843500)
> Email was not designed to be used the way we use it now. ...my inbox is a todo list

So we should not use email as a TODO list, but keep a separate TODO list. Email is not broken, it's just the wrong tool for keeping TODO lists.

I would never have thought of (mis)using email for a TODO list, and I'm astonished to read from various famous people (not just pg) that they're seriously doing that. Maybe this is a typical mistake of Internet beginners, but why are so many experienced and very busy people doing such a huge organizational mistake, every day?

There are lots of tools for keeping a TODO list. For my personal purposes, a plain text file works flawlessly. [1] Bigger organizations use various forms of issue trackers, or use a simple Wiki to simulate an issue tracker.

[1] http://news.ycombinator.com/item?id=3830247

Re:Email is not broken: It’s a framework, not an application by cturner on Sunday April 15, 2012 @08:41AM (#3843566)
If you get lots of emails, then you won't always have time to follow up on all of them. Somtimes the mere task of comprehending the email to create todos from it takes energy, and you don't always have energy to do that immediately. So the emails queue. Effectively the emails become tasks. After several weeks of high load you find your inbox is crammed with lots of things you mean to get around to but you're exhausted.

This is a common problem for busy people and has no obvious solution. One way we try to tackle hard problems is by identifying them, and then having open discussion.

    > or use a simple Wiki to simulate an issue tracker.
    > For my personal purposes, a plain text file works
    > flawlessly. 
The mechanisms you're talking about don't scale to situations where you're being hit by a firehose of emails and calls, but where you have to have concentration periods as well. e.g. technical role that's customer-facing.

My current solution is multi-layered, and starts with a text file. But it's not the simple problem that you make it out to be.

Re:Email is not broken: It’s a framework, not an application by fluorid on Sunday April 15, 2012 @09:10AM (#3843613)
The common problem you describe is still not about email.

The real cause lies in people with deficits in time management, organisational skills and leadership.

If you have too many projects/threads going on with too many people time to change: do fewer projects, focus, delegate, give people goals rather than nitty-gritty todos, basically stop micro-managing, find talented peers and trust them.

Re:Email is not broken: It’s a framework, not an application by cturner on Sunday April 15, 2012 @09:34AM (#3843653)
There are mechanisms through which some limitations of email can be worked around, but there are still problems with email.

Technologies lend themselves to particular use and misuse, and when we see a repeating patterns of abuse, it's reasonable to focus on the technology and talk about what we can do differently.

The original post is talking about email as a series of protocols and ignoring the culture of email as we use it in day-to-day use. It's a nerdy rant that dismisses a problem space by forcing a new definition on the language, rather than addressing the problems that people suffer. The chap I relied to continues the tone by insulting people who are dealing with the queue.

Email is the monitoring messages that clog up my inbox. It's the reasonable expectation of response that happens when somebody sends me an email, unlike with my phone where I leave voicemail turned off or a colleague can take a call and I can know that ownership has shifted. Email is the ease with which a difficult-to-understand message is sent and the exhaustion created by comprehending it. It's the poor integration with task management. It's the awkwardness around tracking ownership of an issue that's sent to a group list. It's spam. It's the compromises you make to avoid spam. It's how awkward it is to implement IMAP, and the multiple eccentricities of different IMAP servers, and how woeful POP is. It's Lotus Notes and Exchange, and being forced to use them.

Re:Email is not broken: It’s a framework, not an application by nkassis on Sunday April 15, 2012 @10:27AM (#3843748)
I think people are looking at it the wrong way, it's not problems with email it's the fact that email is flexible, decentralized, reliable that makes it possible to use it for any of these tasks.

The asynchronous messaging that email provides is it's killer feature that would need to exist for any of the features (todo,task management,calendering...) that you mention would need to work well. But the underlying mechanism of email is still working fine and I don't think that should change.

I agree with the article, the client is where this should go with maybe some thing similar to the W3C and Browser vendors (This isn't perfect but it works) agreeing to protocols.

Re:Email is not broken: It’s a framework, not an application by vog on Friday April 20, 2012 @05:14AM (#3867099)
> find talented peers and trust them.

This is the most important advice, I think. Although delegating, etc. is very important, too.

Re:Email is not broken: It’s a framework, not an application by gbog on Sunday April 15, 2012 @11:18AM (#3843845)
When I read this piece from Paul Graham, I wondered if he had an assistant (I mean a flesh and bones personal assistant). Is that that assistant are too expensive nowadays in the West? If I were a powerful influencer with enough money, I'd consider hiring an assistant to help me filter these mails. He or she will probably be easier to train than a Bayesian filter...

Automatisation is not the last word for every human activities. Many people are struggling to find a job. Many could do this kind of task efficiently, and even enjoy it.

Maybe I have a different point of view because I live in China, where labor is cheaper, but for instance here if you have a kid and don't wish to change 100% of his diapers, you can just pay someone to do so, it is cheap enough and many people are happy to do this for you (it is often better paid and always safer than working in iPad factories).

"Externalizing" some tasks to other people also means you have a life with more and deeper human contacts. Surely, these human being must be handled much more carefully than a "web service", you have to smile to them and consider their problems. Sometime you have to do compromise and accept a less than perfect outcome. Sometime you have to manage these people that work for you. But this is life.

Re:Email is not broken: It’s a framework, not an application by fluorid on Sunday April 15, 2012 @11:44AM (#3843889)
Good point, it reveals a lack of organizational and leadership skills. If one is so wanted that his inbox is quickly full either he has to reduce workload or hire staff and delegate.
Re:Email is not broken: It’s a framework, not an application by flogic on Sunday April 15, 2012 @01:40PM (#3844158)
Yea he should probably hire an assistant. Good secretaries can light saber through bullshit. That said, I can't afford a secretary and my inbox is completely out of control. It's won. I've lost. There is virtually nothing I can do about it at the moment.
Re:Email is not broken: It’s a framework, not an application by Zak on Sunday April 15, 2012 @02:07PM (#3844217)
In what way is it out of control? I may be working on things that can help with this problem.

Is it just that you're communicating with too many people? Do most of the emails require action, or are some of them things you don't even want to read?

Re:Email is not broken: It’s a framework, not an application by flogic on Tuesday April 17, 2012 @05:40PM (#3855145)
All of the above.
Re:Email is not broken: It’s a framework, not an application by Gormo on Sunday April 15, 2012 @02:36PM (#3844289)
> but there is definitely a fundamental problem with email that can't just be solved by a couple of perl scripts and rules

And what is that problem? Yeah, email makes a poor to-do list, but if everyone around you is eating soup out of top hats, then you need to rethink soup bowls, not top hats. Tinkering with email doesn't help you make a better to-do list.

Re:Email is not broken: It’s a framework, not an application by ams6110 on Sunday April 15, 2012 @01:22PM (#3844123)
I agree with the entire sentiment as well, but would point out one flaw: You send a message and it either goes where it’s supposed to, or you get an error message back.

Generally yes, assuming everything between you and the recipient is properly configured, but it's not guaranteed. It's possible to send an email had it just disappears. No bounce, no delivery. It doesn't happen often, and as far as I know it's never happened to me, but there's nothing in the protocol that guarantees delivery or guarantees notification of delivery failure.

That said, this is not a big enough problem to require a new protocol or a change to the existing protocol, or in any other way be worth "fixing." If you are building something that requires guaranteed delivery of messages, don't build it on SMTP.

Re:Email is not broken: It’s a framework, not an application by gnaffle on Sunday April 15, 2012 @03:16PM (#3844401)
Nothing on the internet is guaranteed. Everything is at some point a leaky abstraction.

While it's possible for a mail to just disappear (or more often, automatically be sorted into a spam folder) the protocol is designed to be quite robust in how responsibilities for delivery are passed on to servers delivering the message.

Re:Email is not broken: It’s a framework, not an application by raintrees on Sunday April 15, 2012 @01:26PM (#3844133)
Doesn't this argue for a TCP-type implementation of "Did you get that or shall I resend?" ala Read Receipts? (On top of SMTP, that is...)
Re:Email is not broken: It’s a framework, not an application by TheCondor on Sunday April 15, 2012 @10:14AM (#3843723)
Documented?

Email is a good asynchronous messaging protocol, it's not a great one though. I'd say authentication would be a requirement for such a protocol to be great. I think the next logical step of content protection (encryption) is free if you have authentication and most would want it too. You also don't know if a message has been received, ignored, or blocked by a spam filter.

It's good, it does manage to work and deliver billions of messages a day. And it works pretty well. It's infuriating when it doesn't though.

Re:Email is not broken: It’s a framework, not an application by EvilTerran on Sunday April 15, 2012 @10:38AM (#3843765)
What's wrong with layering, say, GPG on top of email if you want authentication or encryption?
Re:Email is not broken: It’s a framework, not an application by steeleduncan on Sunday April 15, 2012 @11:24AM (#3843857)
Indeed. A great protocol is a flexible protocol, and restricting email to one authentication and/or encryption protocol would prevent it from adapting to advances in cryptography.