In user PM's, the user should get the same color & server nick as the role in the topmost common server
When PM'ing users, currently users get a white color regardless of server roles and the account nick.
This creates a slight danger of impersionation.
I do understand that PMs are a separate part from servers, and it creates a difficulty, to give the user a nick color based on a role, since the user could have multiple common servers. But I have a solution to that:
I have a suggestion, and that is that the user should, in PM's, get the same color (and server nick), as the color & nick he has in the common server most topmost in the user's UI.
With "topmost", I mean how the user has arranged the server (by dragging and releasing the server icons). So servers higher up get "priority" over lower servers, so the end user can himself choose which servers are "most important".
So imagine I have a green role nicknamed "Sebastian" in Server A, and my PM partner has a red role in Server A with nickname "GoodUser".
Aswell, I have a blue role in Server B with nickname "Sebbe", and my PM partner has a purple role in Server B with nickname "BestGuy".
If I have arranged server A over server B in my UI, and my PM partner has arranged server B over server A in his UI then:
In my UI, my nick should be "Sebastian" in green and my PM partner should have a red "GoodUser" nick.
In his UI, my nick should be blue "Sebbe", and his nick should be purple "BestGuy" on his screen.
It should of course always pick the topmost common server and use it, so just because im roleless in server A, shouldn't mean it should skip to server B, instead it should use the default roleless color for that server. But if there is no common servers between my and a PM user, then the user's name should be default white.
-
This could be toggled in the settings, perhaps? And also I think that it should skip the servers with neutral colors. I support this! Sounds like a very unique idea.
0 -
The reason I think it should not skip servers with neutral colors, is because to avoid the risk of impersionation. Basically, the algoritm should choose the topmost common server and use that.
If the user doesn't want that server to be chosen, he could pull it down in the UI, put it below another common server.
This is also a change that can be implemented purely client-side, so no change of server code is required.
Setting could be good, but then it should be default on.
0
댓글을 남기려면 로그인하세요.
댓글
댓글 2개