https://bugs.kde.org/show_bug.cgi?id=495748
--- Comment #9 from Joshua Goins <j...@redstrate.com> --- > I would strongly recommend checking Connection::encryptionEnabled() on the > client side after Connection::connected() or Connection::ready() are emitted This seems sensible and easy to do, I'll look into adding guards around that. I didn't know that it was possible to libQuotient to turn E2EE off in that situation, I had assumed it's always on (assuming it's built with it) -- You are receiving this mail because: You are watching all bug changes.