←back to thread

309 points StalwartLabs | 1 comments | | HN request time: 0.001s | source
Show context
sylens ◴[] No.45674189[source]
We need better client support for JMAP. Apple Mail, Thunderbird, Outlook (as if), and so on. I'm surprised some of the smaller ones like Canary or Spark don't implement it as a product differentiator.
replies(3): >>45674372 #>>45675000 #>>45675410 #
frumplestlatz ◴[] No.45675410[source]
There isn’t really a great motivating feature or use-case driving client or server adoption.

To be honest, I’m not sure why end-users would want JMAP for e-mail access.

It would be interesting if they do successfully roll out all of these additional RFC proposals providing a cohesive “groupware” protocol covering calendering, contacts, file shares, etc, we see notable server implementations, and interest is enough to drive client support.

That’s a lot of “ifs”.

replies(1): >>45675438 #
tjoff ◴[] No.45675438[source]
Because IMAP is horrible, it is another driving reason why we are moving towards the dystopian world of webmail.
replies(1): >>45675451 #
frumplestlatz ◴[] No.45675451{3}[source]
Horrible how, exactly?

People say things like that, and I wonder if I’ve just been living in a gilded tower of using Apple Mail with decent IMAP server implementations.

I’m also pretty familiar with the wire protocol and its implementation — it’s never struck me as particularly horrible.

A new protocol isn’t likely to solve the problem of poorly implemented clients and servers — e.g. Google doesn’t really care about good IMAP support, so they’re unlikely to care much about JMAP, either. They just want you to use their webapp.

replies(2): >>45675546 #>>45675944 #
1. ◴[] No.45675546{4}[source]