Great, I'll watch and collect emails.

Very good to target HN demographics :o)

Yeah, censoring the email addresses would be nice. Ah well.. 37 people now have my email. :)

Cool demo, but the evil me considers connecting it up to the production mailing cluster we have and seeing how it would handle a few hundred messages a second....

I would be interested to know what kind of performance you do get out of this (i.e. messages a second) as I've been writing code to do some SMTP handling in python and been looking for a way to speed it up.

From scanning the source, if a websocket connection is backlogged, messages sent to it are dropped. So I'd imagine it'd handle it fine :)

I'm imagining an in-browser game where people have to zap the incoming spam emails in real time.

I like how it get's around the problem of storing images people send before serving the <img> tag to the browser (for people who don't want to look: it doesn't store the images at all - it serves them in the same websocket stream using data: urls)

Pretty cool! This is making me want to have a closer look at Go. Thanks for sharing.

I think there is a big XSS hole in the current front end. There is no escaping of input from email sent to it.

Edit: Oops I'm wrong, I think it is escaped on the server. How are people including images?

Email attachments?

Can't display non-English characters.

The application cannot handle the character encoding that you sent it. Go does not have a standard library for converting arbitrary character encodings to UTF-8. Perhaps this will demo will illustrate the need for such a library.

Libraries exist. I just didn't link one in out of laziness.