4 ms·
Pessimistically for telemetry, but I suspect some of them are Javascript apps in a lightweight shell that have actual technical difficulties making a TCP IMAP c
by mappu 6y ago
Pessimistically for telemetry, but I suspect some of them are Javascript apps in a lightweight shell that have actual technical difficulties making a TCP IMAP connection.
- njhaveri 6y agoYeah, I think difficulty making an IMAP connection is one reason. I think the biggest reason has been to decorate more features on top of the backing email service, like adding Snooze support to an arbitrary IMAP account (so the server can un-snooze a message at the scheduled time). That being said, there are security/privacy implications to that model, and I wouldn't personally use an app that works this way. That's why Mimestream was built as a traditional client.
- scintill76 6y agoDoing TCP from a "native" JS app should be pretty easy[1] (caveat: I haven't tried.) I'd think the cost of running a proxy server would be enough motivation to figure this out, for any developer whose primary reason is as simple as technical difficulties with JS and TCP. I think it more likely the other responses such as doing heavy indexing that won't work as nicely on the clients. [1] https://stackoverflow.com/questions/41674063/is-it-possible-to-create-a-tcp-client-with-electron https://stackoverflow.com/questions/41674063/is-it-possible-...