3 ms·
Hilariously, we have the need for the opposite... SEC requires record keeping of written communication. HIPAA covered industries face a similar plight. There is
by exabrial 6y ago
Hilariously, we have the need for the opposite... SEC requires record keeping of written communication. HIPAA covered industries face a similar plight. There is no great chat solution for this... RocketChat is a mess, it used mongodb as a backend and the server side requires roughly 512mb of RAM per user. Mattermost is not much better, it also uses a terrible database choice and has similar scalability issues, and the license is a minefield. Both have major usability issues. Both crash a lot.
I do appreciate E2E encryption for some narrow use cases, but it is not the end-all-be-all.
- vlmutolo 6y agoIt’s not like E2EE is required for Matrix (or Element). It’s just on my default, which is great.
- brunoqc 6y agoAlso, it's only on by default for 1-on-1 conversations.
- neiljohnson 6y agoIt’s on by default for 1:1s _and_ private rooms. Though nothing in the protocol demands an encrypted room so unencrypted 1:1s, say, are entirely possible.
- Reelin 6y agoI would think that ideally you would want E2E encryption that was on by default for everything. Then rather than turn it off, you would also want the ability to configure a server to effectively MITM everything (and the client to cooperate in this, and notify the user about it). Such an arrangement is more or less what happens with key escrow, a feature which I believe at least one self hosted cloud stack offers (sorry I can't remember its name off the top of my head).