Conversations: Same Nickname in MUC

[Nebukadneza]

Hey,

when using Conversations in a carbons scenario, one might also join the same MUC from both resources. The MUC allows two resources connected from the same account to carry the same nickname. If i try to change my nickname to the nickname of the other resource i connect to the MUC with, Conversations says "Nickname already in use".

This also has a second implication: My phone will beep all the time when i chat in the MUC using my desktop/laptop jabber client ;). If the nicknames of Conversations and Computer would match, one could make an exception for this so no notification will be generated -- or maybe it already magically works?

Thanks for your work on this contribution to a free, distributed and secure communication infrastructure!
-Dario Ernst

[iNPUTmice]

This is a bug in prosody. The 'nickname is already in use' message is a direct result of an error reported by the server. I ran into this issue while developing and testing this however I hadn't had time to report this to the prosody bug tracker.
I'm not entirely sure on the exact circumstances but I believe this only happens when you try to change your nick while already in the muc. Joining a MUC with a nick which is already used by another client of yourself works. I'm using this myself.

On a side note I think there is another bug in ejabberd where you will be kicked out of the room if one of your clients disconnects. And there might be other bugs. I ran into a couple of MUC-same-nick-twice-bugs while developing. Unfortunately this was a rather stressful phase for myself so I could research and report them.

[Nebukadneza]

Ah, okay, i haven't had understood that.

Is there some way of joining a MUC with another nick with Conversations? With my most-used MUC, i simply changed the nickname of my desktops client to the account name (which seems to be what Conversations uses as default nick?), so thats at least a workaround, and yes, bogus beeping now ceased ;)

Thanks for your clearification!
-Dario

[akomakom]

I feel that this is still an issue (and I am also on Prosody).

This problem does not occur with another client (Xabber) because it permits one to specify the spelling of the nickname at join time (something that Conversations does not, see #914, also rejected). Thus with Xabber I can use the same nick from multiple clients at the same time, and with Conversations I cannot.

[iNPUTmice]

@akomakom the issue you linked specifically says that

You can enter the full jid into the join conference like [email protected]/mynick

[SamWhited]

You can enter the full jid into the join conference like [email protected]/mynick

This is what I always do, but it's not a very discoverable solution. Maybe changing the placeholder text in the conference address field to read [email protected]/nickname would help?

[akomakom]

@iNPUTmice you're right, I missed that. Probably others will as well.