Typing in MUC shows "Typing from another device"

[ge0rg]

When I'm in a MUC with full-screen converse (3.3.3), and I start typing, I see "Typing from another device" displayed, despite not being active in any other client at the same time. Is it possible that this was introduced with #802, and that the internal logic sees the MUC reflection as "I'm typing" without checking whether this was initially sent by converse?

Maybe this asks for a complete block of self-typing in MUCs, or at least tracking of our own CSN message IDs so we can ignore them?

[jcbrand]

What server are you using? Is there a MUC where I can test this? I haven't seen this myself yet.

The code naively assumes any incoming CSN messages are from other devices.

[ge0rg]

I've tested it with a self-hosted 3.3.3 on the prosody MUC ([email protected]) and on another MUC running on chat.yax.im.

[jcbrand]

I just tested with the Prosody MUC and can confirm that I received <composing> and <paused> CSN messages (by looking in the dev console), but I did NOT get any "Typing from another device" notifications, I didn't get any CSN notifications at all.

I remember there already being a check for message IDs to filter out dupes, so this makes sense to me.

Are you able to replicate reliably?

[Zash]

I too see this, using mod_conversejs on my development Prosody.

[guusdk]

I'm seeing the same thing in an Openfire-based MUC.

[jcbrand]

I've disabled the typing from another device CSN messages. To keep this feature we would need to keep track of the ids of these notifications which seems like unnecessary complexity given the negligible value of this feature.

[jcbrand]

Reopening since I realised we can check whether the incoming CSN is a carbon copy and show the notification based on that.

[ge0rg]

You won't get Carbons for 'groupchat' messages, only for MUC-PMs and for direct messages.