4 ms·
From JMAP description on github: > It aims to be compatible with the IMAP data model, Unlike this project, I think user requirements should drive the protocol
by vpeters25 11y ago
From JMAP description on github:
> It aims to be compatible with the IMAP data model,
Unlike this project, I think user requirements should drive the protocol's design, not a need to be compatible with SMTP/IMAP.
- rgbrgb 11y agoCompatibility with the rest of the network is a user requirement.
- brongondwana 11y agoYes, this. You need to remain compatible with the rest of the world. IMAP plus every extension in the world isn't even that awful, if everyone supported all of them. The problem is that they don't, so you have massive complexity of servers to support.
- vpeters25 11y agoIt should not be, that's the main premise of my idea: create a new email protocol that completely replaces both SMTP and IMAP based on actual use cases instead of being constrained by 40+ years of legacy protocols and extensions. Client and servers using this protocol would not be required to implement SMTP/POP/IMAP at all, bridge services could be built for that.
- NeutronBoy 11y agoIt sounds like a good decision, but you've just replaced protocol complexity for implementation complexity. At least a single group of designers and programmers can work through protocol complexity. Implementation complexity is going to impact everyone who tries to implement it - any many of them will just give up.