The other day I switched Linux distros, wiped disk, and somehow realised that OMEMO is a weird freaky thing and now I cannot see any message from my computer, even though I have everything visible on my Conversations Android app.
I don’t want to get angry again, but… yeah, this is terrible, terrible UX. Seems like OMEMO somehow encrypts for each device differently, and now all messages are “locked”. Which is weird, because messages are still there, just “locked”.
Can I somehow import a backup from my Android app? Is there anything that can be done? My guess is that, probably not, otherwise I would have gotten a popup or something in the login process, “would you like to sync your messages?”, but nothing happened.
XMPP supremacists, please! Give me a solution! I was organizing important projects with multiple people. Getting locked out of all that information is terrible.
Otherwise, then I really feel I can see XMPP disappearing now… and for a very good reason.
OMEMO by design does not allow old messages to be decrypted by a new device. However, anything going forward should sync between all XMPP clients that implement proper XEPs. The server also has to support the XEPs. But if you’re using OMEMO, then you should also already have the other XEPs required for proper messaging experience. Specifically, the XEP for syncing messages across clients is Message Carbons.
Matrix is able to decrypt past messages on new devices, but that’s because it stores your keys (encrypted) on the server and does a bunch of funky key fetching and passing between sessions to allow message decryption from new verified sessions. OMEMO does not have this function.
That is very sad. I’ll be migrating out of XMPP. It’s intolerable that one cannot recover messages that are still there; or that even moving from one client to another implies you lose all of your history.
@[email protected] in this case, it was designed explicitly as a security feature. It’s not uncommon for end-to-end encrypted services to have this limitation. Signal has it, for example. Only way you can keep your message history with Signal is to migrate it directly from installation to installation, and it doesn’t sync old messages when setting up the desktop client.
Signal has recently added the message sync option when linking a new desktop client.
@[email protected] Did not know that. Must be very recent.
Aside from that, it makes sense that it took Signal a while to get the sync feature because Signal ONLY stores messages locally. XMPP stores them on the server. I would expect to be able to access that information from anywhere. What’s the point of doing so anyway? Let me at least import the keys so I can unlock those messages. But it seems like you can’t.
Pretty sure that has been a feature for at least 2 years. It seems like a reasonable compromise.
This is a security feature. Other communication mechanisms having the keys somewhere else not owned by you is rather something I wouldn’t stand. And to me it’s unsafe that messages would be kept way long on the servers.
On xmpp the sync happens from server to all syncing clients, and the proper XEPs need to supported in both the client and the server.
Then losing all your project’s history, while also forcing you to stick to a single, unofficial (because there is no official) XMPP client for the rest of your life because there are no standardized multiplatform backups. I’m sorry but no.
You may call it a feature. I call it a huge fat bug.
This is a problem a lot of secure/private projects have tbh, they get so into the details that it’s just a miserable user experience.
@unknowing8343 @projectmoon
You can try Signal. It’s private, popular, and feels modern too 🤩
I do use Signal. Everyone should have Signal for telephone contacts. But for the other stuff… I’d rather use a decentralized system.
[email protected] it also seems that Conversations now has the ability to preserve message history when moving devices. Of course this is different than moving between clients, but it’s a step in the right direction.