3 ms·
Very interesting: > JMAP is not designed around a persistent network socket, so it’s perfect for webmail clients that connect, do stuff, then disconnect This
by nothrabannosir 8y ago
Very interesting:
> JMAP is not designed around a persistent network socket, so it’s perfect for webmail clients that connect, do stuff, then disconnect
This would allow implementing JMAP in serverless architecture, e.g. self hosting on AWS lambda. That should be very cheap and significantly lower the barrier to self hosting (not needing to manage a box, just providing aws credentials).
Think of what it takes to truly decentralise email. There are technical hurdles, but also some fundamental ones:
- other providers mark you as spam because you’re unknown
- you need an always on server to actually get your incoming mail
This would at least solve the second problem. If we can develop a product like mailinabox (Which has its flaws but it’s the right idea), but instead of asking for a fresh vm, it just asks for aws credentials, that could be pretty solid.
Hopefully one day we can give the people back their control over their means of communication. This seems like a step in the right direction!
- elcomet 8y agoI'm not sure I understand: JMAP is designed for communication between the client and the mail server. But you still would need a mail server, always on, to receive the incoming mail from other servers, right ? Did I miss something about JMAP?
- jasonmunro 8y agoNope, you are exactly correct. JMAP is just a much more modern and efficient way to connect clients and servers to access E-mail.
- tjoff 8y agoWhy? Mail is decentralized already. Part from relying on DNS. And you seem very eager to put everything in the amazon basket.
- jannes 8y agoIf everyone hosts their email with Amazon it's gonna be quite centralised.
- pjc50 8y agoThe first problem is actually the more serious one, sadly.