Opened 10 years ago

Last modified 4 years ago

#10541 new defect

Make XMPP MUC Username case-sensitive

Reported by: prauscher Owned by: deryni
Milestone: 3.0.0 Component: XMPP
Version: 2.5.5 Keywords:
Cc: mic159, Morgil

Description

Following szenario:

  • 2 Users: USER and user
  • you are USER

# user renames himself to anotherusername

pidgin will think now that you are anotherusername and enable Highlights and your Username to anotherusername.

PS: Sorry, i found no better way to write...

Change History (6)

comment:1 in reply to: ↑ description Changed 9 years ago by mic159

Replying to prauscher:

Following szenario:

  • 2 Users: USER and user
  • you are USER

# user renames himself to anotherusername

pidgin will think now that you are anotherusername and enable Highlights and your Username to anotherusername.

I have also run into this issue.

User 1 enters room as testUser. User 2 enters room as testuser.

User 2 renames to someName. Both users chat windows say "You are now known as someName" even though it was only User 2.

Everyone using pidgin sees User 1's nick removed from the participant list, and be replaced with 'someName', and User 2's original nick with the lowercase letter remains.

From now on, both users receive alerts when someone mentions User 2's name (even if User 1 changes their own name afterwards).

comment:2 Changed 8 years ago by Morgil

I am experiencing a problem that seems to have the same cause:

One user is in a room with two devices and he uses the name someName on one of them and SomeName? on the other one. When he leaves the room with someName, SomeName? is also removed from the user list, although the displayed user number is correctly decreased by one.

Closing and reopening the window helps, but until then that user is "invisible" and it's only possible to see that he's online by comparing the user number with the displayed number (or if he writes something, of course).

comment:3 Changed 8 years ago by darkrain42

  • Milestone set to 3.0.0

Based off investigating this a long time ago, this is due to some limitations in libpurple core about detecting when a change is happening to "the user" (it does some UTF8 case-insensitive comparisons, which are inappropriate for XMPP)

comment:4 Changed 8 years ago by darkrain42

Ticket #13754 has been marked as a duplicate of this ticket.

comment:5 Changed 5 years ago by djfun

Not only case-sensitivity seems to be a problem but also a trailing space character (#16059). My understanding is that libpurple (purple_conv_chat_rename_user, purple_conv_chat_set_nick, ..) call purple_normalize for the room nick. XMPP (jabber_normalize in jutil.c) treats the incoming string (the room nick) as domain, which is why all characters in it get turned into lowercase and a trailing space character gets stripped.

comment:6 Changed 4 years ago by chemistrydioxide

Ticket #13660 has been marked as a duplicate of this ticket.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!