Luke Dashjr

20.04 config: ```yml ### ### ejabberd configuration file ### ### The parameters used in this configuration file are explained at ### ### https://docs.ejabberd.im/admin/configuration ### ### The configuration file is written...

I physically find my child and he shows me he didn't get any of my recent messages. From Psi+ to Conversations.

Can't risk lost messages this weekend, so it'll have to wait :/ Just plain text "chat" type messages. Both users were online (and are 24/7). Both users also have multiple...

Sender: Psi+ 1.5.1484 on Gentoo. (Recipient's other client: Psi 1.3-5build1 from/on Ubuntu 20.04) I have the Psi+ OMEMO plugin on the sender, but I don't know if it was enabled...

Confirmed that the recipient's Psi+ *did* receive the messages that prompted this initial report. Also been having issues with 20.04, with another child having two Psi+s yet only receiving messages...

Latest for Ubuntu focal (which that system runs) is Psi 1.3-5build1 or Psi+ 1.4.554-4 (which it is now running)

>Anyway, in your specific case, maybe a dirty patch is easier than explaining your users, or tweaking client configuration. This small patch customizes it for your specific case. Notice it's...

Duplicates appear to be carbons. Any easy way to not affect internally-generated stuff?

Maybe a better solution would be to force all c2s connections to the same priority, and strip /resource specifiers on c2s packets?

>The core XMPP RFCs specify how to address individual devices vs. accounts. This is used for various use cases. Breaking such essential rules in order to work around client issues...