Kyle Marek

Perhaps they'd offer advice on the developers' mailing list? See: https://pidgin.im/cgi-bin/mailman/listinfo/devel

I was experiencing this issue with my build of Conversations 1.19.3 (unmodified source code). While testing this, I unintentionally found that switching to Unencrypted and back to OMEMO is necessary...

I have been experiencing this lately (actually after my "upgrade" to dev branch in testing #63, but without updating Conversations), and a friend/user complained about experiencing this after updating Conversations...

I forgot to point out that I also haven't upgraded carbons since gkdr/carbons@35dd48de17003ba9d17e2b413bc6d762d506d0fc. I'll report back if experience the issue after upgrading.

Fast result! As of 530c61474ba0b9e5542e2bf936f75988df93da15 and gkdr/carbons@153b45c425894d1990a2fb7237fdc0309023cacf, with two Pidgin devices logged in, I did not recieve my own messages on each Pidgin if it was sent from the other...

Just randomly reproduced again on this same run. Sadly, there is a lack of information to present. Debug window (note the reception of the stanza is logged): ``` (19:44:27) jabber:...

Once it starts, I do not receive my own messages sent from another device to _any_ of my contacts.

My friend, who isn't up-to-date, gets Conversations's fallback text (remember #57 when testing this). I am using the later commits mentioned, and I don't even see the fallback text for...

I've updated my clients to 2ea47f488ba80910121f4f007f6c56400e856509. Due to the seemingly random nature of the bug, I think I'll have to follow up after more usage. However, it seems to be...

It took a while but the issue reproduced on one of my Pidgin/lurch client after running for about 24 days with an uninterrupted connection to the server. Messages I send...