I believe one of the original goals of Conversations was to be an “always on” messenger. In fact until recently they never really indicated contacts or own status, if I remember correctly, prefering to act like WhatsApp/etc in that you send message without caring if someone is online, offline, away, etc.
this of course causes issues when Conversations actually goes offline and can’t receive messages… Which should be rare but can happen (go on a flight, drain battery, turn off phone, etc).
Chatty will handle being offline fine and can retrieve offline messages.
so depending on circumstances, some messages might get lost sometimes… Message carbons will help, e.g. in my case I keep a XMPP client always on at home, but since my server also has MAM that’s less of an issue. So basically, YMMV
Glitches… hard to describe… I need to come up with a more “formalized” testing method, otherwise I just know what sometimes some clients aren’t getting OMEMO-encrypted messages. It’s better than it used to be, but libpurple still has issues I think. Sorry to be so vague… like I said I need to formalize my testing and submit some actual bug reports.
In Conversations, there’s a padlock icon at the top of the chat window that tells you if you have OMEMO activated. Unencrypted messages while that padlock is “locked” will also be highlighted in red with some text telling you it’s unencrypted.
Pidgin (desktop XMPP client) has only the title bar of the chat window saying OMEMO, with no other indication. Some messages do appear when an unencrypted message comes in to the effect that the message is unencrypted even though the conversation is supposed to ne encrypted.
Chatty… Doesn’t have much in the way of UI for OMEMO yet. In my tests, I’ve manually installed lurch by compiling it from source. It does seem to enable a setting to enable/disable OMEMO in the “Chat details” settings of the conversation, but that toggle doesn’t seem to do anything at the moment. Still a work in progress it seems.