Implement group chat duplicate name deconfliction similar to 2.7.7

Description

In Spark 2.7.7 when you joined a room and your name already existed, it would automatically assign you a serialized name and allow entry. In 2.8.x it will refuse entry and create a ghost user. If you attempt to join the room again it will join you to the ghost user, but the listed users in the room will be erratic. This was resolved in a nightly where the ghost user is no longer created, but you are still refused entry into the room. If your backing authentication system does not allow modification of your nickname, you have no way to enter the room without significant administrative effort.

Environment

Any

Activity

Show:
Leslie R. Thomas
January 15, 2017, 3:46 AM

Tested good with 2.8.2.954.

Thanks, Good work Guus.

wroot
January 14, 2017, 9:44 AM

Not exactly automatic like in 2.7.7 version. This requires an input from a user. Though i like this better. Maybe not everyone will like to be just User2. You can add some explanation to your nick so others would know who you are exactly, like John-TheNewGuy, etc. I will let Leslie to evaluate and close this ticket. Can be tested with 952 build http://www.igniterealtime.org/downloads/nightly_spark.jsp

Fixed
Your pinned fields
Click on the next to a field label to start pinning.

Priority

Major

Assignee

Guus der Kinderen

Reporter

Leslie R. Thomas