Encrypt messages at rest

(#967) Feature Declined privacy security

Thread

Comment by @spectrapulse
RexSystem 1 vote originally by @spectrapulse on GitHub 1 reply
I don't see why adding this much complexity is necessary as it just sounds like extra steps with no amount of improved security or privacy regardless without making the entire thing E2E which has other problems. Also, This is not Telegram... It's also not WhatsApp... E2EE doesn't make sense for the platform and in my opinion for what it is trying to be it might even make it worse. If that's a concern you should either be using one of those solutions you mentioned or Matrix. This wouldn't add or improve the situation just make it more complex for no reason.
Comment by @frolleks
RexSystem 1 vote originally by @frolleks on GitHub OP
before you start raging over i initially was obsessed with telegram's transport protocol until i realized that its just a glorified tls implementation, i'll close this as messages are transported via tls anyway and encrypting messages on the server while also having keys on the server only adds complexity indeed