4 ms·
> Let's design the successor to email on top of HTTP You can stop there, I've heard enough. Not everything is hypertext.
by thesuitonym 3mo ago
> Let's design the successor to email on top of HTTP
You can stop there, I've heard enough. Not everything is hypertext.
- andros 3mo agoUsually, informed people only read the headline.
- beej71 3mo agoAnd HTTP transports many, many more things than hypertext. It seems like a sensible choice for this use case in terms of capabilities.
- inigyou 3mo agoWhy, 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.
- beej71 3mo agoSince 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.
- jjice 3mo agoFrom 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.