3 ms·
> Probably the biggest thing is that it translates a traditional document-based data structure (mailboxes via IMAP) into a stateless, streaming transactional da
by ultramancool 11y ago
> Probably the biggest thing is that it translates a traditional document-based data structure (mailboxes via IMAP) into a stateless, streaming transactional data structure.
So why can't this be done on the client side? Are you telling me that to avoid storing more data on the clients, they should give up their privacy to whoever operates the server? Not like Outlook or Thunderbird take a substantial amount of time to do most operations. Is this a good tradeoff for them?
I understand, yes, technically adept users can run the server, but there's still many who won't, who will use your server or someone else's server and be required to make this tradeoff.
Of the products you mention - yes, yours is the only one I'd consider and for this very reason, I can run the middle server myself. I just have to think about those people who won't do it though.
- niccaluim 11y agoHaven't such users already "given up" their privacy by having their email hosted by a third party?
- ultramancool 11y agoFor some, it's adding another party, for others it's introducing a 3rd party at all. Still a problem either way.
- coldtea 11y ago>I understand, yes, technically adept users can run the server, but there's still many who won't, who will use your server or someone else's server and be required to make this tradeoff. So? How's that different (if anything it's much better) than using Gmail or Outlook on the cloud? Besides, nobody is "required" to do anything. You can always run some Thunderbird or any other desktop client without a cloud component.