I'm testing #xmpp with #snikket today. It was straight forward to install the server. Like 10minutes. I was very impressed!!

But then the problem started… with #encryption key managment problem.

Basically I wanted to write to a #quicksy user (aka myself) and that didn't work because of some 'Aucun appareil pour qui chiffrer ce message n'a été trouvé. Recherche d'appareils en cours…'

I know that there is a lot of work to improve the situation. I'm open to report bugs, but I have no idea if it should be done in snikket, quicksy, gajim, kaidan …

@lascapi

Note, that Gajim, Snikket and Quicksy only support OMEMO1 ("oldmemo"), while Kaidan only does OMEMO2 ("twomemo"). In theory, everything should be fine between the first three.

@debacle arff !! OK, know I understand better. 😖

I didn't remember that there is two version of omemo and I think I didn't saw that mentioned in the XMPP client. For exemple quicksy only say Omemo in the menu to choose "clear/omemo/openpgp" encryption.

Thank you for your help.

@lascapi I have the same issue. Unlet you let your server to do StartTLS, you may only encrypt with traditional TLS. In this case, the S2S port goes from 5269 to 5270, and you need to write differen SRV record on DNS.

This is what you can do to mitigate, otherwise, everything you will get is that the XEP jungle will hit you, and each server implements its own XEP list....

@uriel thanks for the feed back. 🙏
@uriel I love your picture profil by the way. 😊

@lascapi thanks. I am a big fan of the fifth element...

Multipass!

@[email protected]
Unfortunately parts of your message are frencrypted. Is it the famous "not encrypted for your device" thing?
I wonder that you have this between quicksy and snikket. Those clients are both known to support omemo well.

@martin sorry, I had been lazy! 😅

It's more cryptic than that.
It's : ''No device has been found to encrypt this message. Searching for devices…''

I tried to deactivate the Omemo encryption but that didn't work. 🫤