Hacker News new | ask | show | jobs
by thesuitonym 1 day ago
> Let's design the successor to email on top of HTTP

You can stop there, I've heard enough. Not everything is hypertext.

3 comments

And HTTP transports many, many more things than hypertext. It seems like a sensible choice for this use case in terms of capabilities.
Why, what advantage does adding the extra layer bring? You can just open a socket and send JSON to it, you know, you don't need this layer. But if the layer brings advantages then you should, but you have to explain the advantages.
Since it's email, we probably want to send content of several different types, and MIME is baked into HTTP. And the commonality with email-style headers is nice, as well.
From the first paragraph:

>The goal is not to replace the current mail system, heaven forbid!, but to learn, have fun and discover current technologies to swap out every element: sending, receiving, gateway, keys, and so on.

It's all for fun.

Usually, informed people only read the headline.