definetly report the problem. there’s a function for it in the app, 3 points menu on the chat list menu, use it after making those errors show up. tick the contact me box. ceo recommends to also notify himself directly: gist.github.com/…/190ad712965d0f06e17f508d1a45b55…
Comment on What is the current state of Matrix?
hard_zero1@discuss.tchncs.de 2 days agoI’ve last seen it last month. And I have an old chat, where FluffyChat and (“old”) Element show all messages by now, but Element X can’t decrypt many and both Elements report that they can’t guarantee the authenticity of many messages (even my own). For a long time, my chat partner could only read messages I sent via FluffyChat but not those sent by Element. I have not checked if that is still the case.
WhyJiffie@sh.itjust.works 1 day ago
JadedBlueEyes@programming.dev 1 day ago
“can’t guarantee the authenticity of this message” just means it was restored from backup. In the same vein, if you can decrypt a message in any client, it should upload the keys to the message backup so it can be decrypted on other clients, even ones that haven’t logged in.
oranki@sopuli.xyz 1 day ago
Some months ago, I had UTD issues with Element X too. My hs has been up for some years, and the devs claimed they had done a lot to fix UTDs.
I was about to bring the server down, but as a last resort decided to log out all but one Element web session which was able to decrypt the messages and try resetting the key backup. Haven’t had any UTD issues since then.
Maybe worth a try.