@nprofile1q... @nprofile1q... how do you define "nice and modern looking"? We are currently rewriting our chat interface and any input is welcome :)

@nprofile1q... sure, you're welcome :) happy debugging :)

@nprofile1q... Monal currently only supports omemo legacy (in the siacs namespace).

@nprofile1q... @nprofile1q... yes, that is possible and we can even ship updates even though it won't be accessible in the appstore for new installs (in that case it would need a new SMS code which won't work anymore anyways).

To bring some perspective into this: according to the appstore statistics, Quickly iOS has about 600 users currently (and only 1.8k downloads ever, including later uninstalls).

That's almost nothing compared to the >50k users of Monal iOS.

While there are a hand full of solutions (local users donating a Sim with SMS flat + cheap android device to route through SMS for their country for example), I fully understand @nprofile1q... here: according to the user count it doesn't seem worth the effort.

@nprofile1q... setting up a @nprofile1q... server is dead easy.

But as an #xmpp client developer I might obviously be biased.
On the other hand I'm a happy xmpp user since 2015 and only later in 2020 joined the Monal team.

@nprofile1q... @nprofile1q...
When did you test Monal the last time? It changed a *lot* in the last few years. We basically rewrote everything of the underlying framework (xmpp parser, pubsub handling, push handling etc.) and are now half way through the process of rewriting the whole ui (currently working on the chat ui).

The new chat ui will bring us reactions, rich message replies, stickers etc. But the old ui is still stable and usable in day to day live.

@nprofile1q... thanks! Not sure. I thing the bug was present in both.

See Herr for the logging part: https://github.com/monal-im/Monal/wiki/Introduction-to-Monal-Logging

Please send the log via email to [email protected]

@nprofile1q... the question is: could you try again, if the false regenerating of your keys still happens and if so maybe provide a logfile?

It should be fixed IMHO, but you never know...

@nprofile1q... because there is now way to know if the old device was wiped after the migration or if there are now two devices with identical omemo deviceids and keys.

Two devices having the exact same identity will cause encryption/decryption problems. And there are also the security implications of the duplicated keys along with your chat partners not being able to determine if your device was cloned or is still only one single device.

@nprofile1q... sure, but imho that bug has already been fixed several month ago. It was related to apple not returning a stable ID from an api supposed to do exactly that.

We used that ID to regenerate the keys after device migration.

We now generate and store our own ID in the password storage, to detect if the device was migrated.