-
jcast
Hey I've been trying to get more people aboard XMPP, overall much better experience than I expected, even if a bit of holding newbies by the hand is needed.
-
jcast
Some feedback
-
jcast
I use several devices, with multiple apps, for testing to a great extent. Aside some apps not fully suporting multidevice yet, some "Not encrypted for this device" errors are sometimes simply because the other user did not verify fingerprints.
-
jcast
At least it seems
-
jcast
New users - and I suppose we want many of those - may need to be educated. Make the UI hint optionally (opt-out?) by sending an automated message when a new device is added eg "I just added a new device, please review fingerprints".
-
jcast
Also more unified experience of where to find and review own and other's fingerprints would really help towards users showing each other the way around OMEMO
-
jcast
Across apps that is
-
emus
jcast: there is a xep automatic trust management I think
-
emus
jcast: thanks for reporting
-
jcast
> jcast: there is a xep automatic trust management I think In a chat involving Conversations, Gajim and Dino 0.3 (backport) I somehow got these errors on both desktop clients after it initially worked. Unsure what caused my Conversations peer to stop encrypting for those. Fixed after fully trusting my own fingerprints mutually from Conversations and sending messages to my peer from the desktop clients.
-
jcast
Sorry the fully trust thing is in Gajim, not conversations
-
jcast
Encryption worked across all clients June 19, and after a pause in communication, July 14th onwards messages were not encrypted by both my own Conversations client and my peer's Conversations client, to both desktop clients.
-
jcast
Did not mean to report this as an issue though, just dropping the UI/UX improvement suggestions. If more details are needed, I'll be happy to provide. Thanks for your time!