Own messages sometimes aren't received in group

[anthonybilinski]

Follow up from qTox/qTox#5481 (comment).

Normally when calling tox_conference_send_message we receive tox_callback_conference_message from our own message. Sometimes (1/10 connects with one of my groups) running off toxcore dd539800eea8cfc70d6cb14a7fd0ddefb2082cd1 #1267, after tox_conference_send_message is called without error, tox_callback_conference_message is never called.

All other peers in the group still receive the message. Reconnecting to the group (network disconnect and reconnect without closing client) fixes the issue.

[iphydf]

Does this happen with 0.2.8 or is this a recent regression?

[anthonybilinski]

I saw a friend that ran into the same symptom of not seeing his own messages in a a couple times on Windows 10, running Toxcore v0.2.3 with qTox v1.16.3, but didn't look into it too deeply at the time, so I'm not sure if tox_callback_conference_message was still being missed.

The case of me not seeing my messages I only saw post-v0.2.8 when running on #1267, where I verified that no tox_callback_conference_message was called. I also had a friend who was running on #1267 and hit a case where he couldn't see my messages in one of our groups, but could see his own and the other peers'. Him leaving and reconnecting to the group fixed the issue.

I haven't been using groups nearly as much, so can't easily check repro rate on 0.2.8.

[anthonybilinski]

This could be related to #961, in which I don't receive my own messages, but also my peers don't receive my messages.

[iphydf]

It's a bit strange to be "receiving" your own messages. This should probably be changed in the API and clients should just display the message themselves.

[anthonybilinski]

For what it's worth, qTox does not rely on receiving our own group messages anymore, so this "bug" is irrelevant to us.