XMPP does have something that breaks my heart: it bounds encryption to a very specific client. So forget about migrating to something else and keeping your history somehow. Which is very sad for supposedly interoperable protocol.
Why would an organization use OMEMO if it doesn’t fit their requirements? OMEMO isn’t necessary for encrypting xmpp communications. Also, I get the concern that only the original client will have a full history of the user, but most people don’t need a complete chat history. Or put another way, wanting a complete, unencrypted chat history is relatively orthogonal to wanting perfect forward secrecy.
XMPP does have something that breaks my heart: it bounds encryption to a very specific client. So forget about migrating to something else and keeping your history somehow. Which is very sad for supposedly interoperable protocol.
Are you talking about omemo and a scenario where you buy a new device and want to sync your entire history from the server?
Most clients also offer OpenPGP which has the properties you are looking for.
You don’t even need another device. You might just want to try another client app. You’d be screwed. That’s very, very sad.
That is how perfect forward secrecy is supposed to work.
That’s a terrible UX. If you have a protocol independent from clients, at least the chat database backup should be standardized. It’s not.
That means you’ll forever get stuck to one client. This is absolutely terrible for any organization.
Why would an organization use OMEMO if it doesn’t fit their requirements? OMEMO isn’t necessary for encrypting xmpp communications. Also, I get the concern that only the original client will have a full history of the user, but most people don’t need a complete chat history. Or put another way, wanting a complete, unencrypted chat history is relatively orthogonal to wanting perfect forward secrecy.