Skip to content

Two users with the the same name appear as the same person #1151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lzmartinico opened this issue Feb 11, 2022 · 24 comments · May be fixed by #1255
Open

Two users with the the same name appear as the same person #1151

lzmartinico opened this issue Feb 11, 2022 · 24 comments · May be fixed by #1255
Labels
area: message rendering bug Something isn't working good first issue Good for newcomers help wanted This issue should be clear enough to work on

Comments

@lzmartinico
Copy link

On zulip-term version 0.6.0, if two users have the same name and send two messages in sequence within the same topic, the messages will be displayed as if coming from the same user

@neiljp
Copy link
Collaborator

neiljp commented Feb 14, 2022

@lzmartinico Thanks for reporting this! I suspect this is present in main also, though have not confirmed.

This should be fairly simple to resolve via comparing user ids rather than names.

@neiljp neiljp added area: message rendering bug Something isn't working labels Feb 14, 2022
@lzmartinico
Copy link
Author

Glad to hear there is an easy fix! Maybe there should be another ticket (or meta ticket), but support for users with the same name is somewhat lacking overall (e.g. when tagging a user through autocompletion, it's impossible to know which one is selected)

@neiljp
Copy link
Collaborator

neiljp commented Feb 14, 2022

@lzmartinico Autocomplete is improved further in the current development version after GSoC, and may well resolve the issue you're describing.

Generally if you have other separate then other issues (or a general issue we can split out) are a good idea - or if you wish to discuss a potential range of issues then it's likely better to raise this in a topic in the #zulip-terminal stream on chat.zulip.org :)

@neiljp neiljp added the good first issue Good for newcomers label Feb 14, 2022
@prah23
Copy link
Member

prah23 commented Feb 14, 2022

@lzmartinico thank you for the feedback!

We have additional autocomplete improvements for tagging users (disambiguation using an appended user ID, #928 for reference), as well as using users' names as private message recipients, currently on the main branch. It will be a part of the next release, but you can also pull that from main as the latest installation as mentioned on our README.

Any additional feedback is highly appreciated!

@Dishti-Oberai
Copy link
Collaborator

Hi all,
I would like to take up this issue.
@zulipbot claim

@zulipbot
Copy link
Member

Hello @Dishti-Oberai!

Thanks for your interest in Zulip! You have attempted to claim an issue without the label "help wanted". You can only claim and submit pull requests for issues with the help wanted label.

If this is your first time here, we recommend reading our guide for new contributors before getting started.

@neiljp neiljp added the help wanted This issue should be clear enough to work on label Apr 29, 2022
@zulipbot
Copy link
Member

zulipbot commented May 9, 2022

@Dishti-Oberai You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!

@Dishti-Oberai
Copy link
Collaborator

I am still working on it

@Sushmey
Copy link
Collaborator

Sushmey commented Aug 28, 2022

Hi is this still an issue? How would you solve the problem of the names being same? Displaying the ids with the names in the sender name instead of just the name?
Screenshot 2022-08-28 at 6 33 48 PM

@neiljp
Copy link
Collaborator

neiljp commented Aug 28, 2022

@Sushmey Thanks for your interest in the project! To clarify based on your doing a capture of the zulip web app, this issue tracker is for zulip-terminal, not the zulip web app. If there is an issue there, then it needs resolving separately, though from the screenshot it seems that if the user profile picture is different then that is one way to show it (or cause the problem). Manually one can also look at the senders, but that's not preferred I expect.

For zulip-terminal, perhaps obviously, we don't have user profiles to distinguish, which I expect is why you suggested the ids?

The other current issue here is that the same 'A0' header (in your case) will be used in ZT for both messages, so it really looks like the messages are from the same user - the sender header is not even repeated. That was the change I was planning to address first. Once we have that, then we'll also be able to distinguish adjacent messages, so could consider adjusting the sender somehow. That'd need to be carefully done, to avoid indicating that the sender name was actually different.

@Sushmey
Copy link
Collaborator

Sushmey commented Aug 28, 2022

Oh thank you for pointing that out! I was under the impression that the web app was the one where the problem could be recreated but it's only where you discuss the problems.

I see that someone in that someone has already solved it? Please let me know so I can try my hand at it
https://chat.zulip.org/#narrow/stream/206-zulip-terminal/topic/.23T1151.20Users.20with.20same.20name.20appear.20as.20same.20person

@Sushmey
Copy link
Collaborator

Sushmey commented Sep 13, 2022

@zulipbot claim

@zulipbot
Copy link
Member

Welcome to Zulip, @Sushmey! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

@Sushmey Sushmey linked a pull request Sep 15, 2022 that will close this issue
4 tasks
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 15, 2022
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 24, 2022
Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

reformatting

using .get() instead of the key and removing commented out code

squashing commits
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 24, 2022
Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

reformatting

using .get() instead of the key and removing commented out code

squashing commits

reformatting

using .get() instead of the key and removing commented out code
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 24, 2022
Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

reformatting

using .get() instead of the key and removing commented out code

squashing commits

reformatting

using .get() instead of the key and removing commented out code
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 24, 2022
Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

squashing all commits in one
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Sep 24, 2022
Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

squashing all commits in one

Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

isort

isort import order

Update boxes.py

Updating boxes.py to pass lint check

Fixes zulip#1151

Update boxes.py

made users_list global by adding global keyword

Update boxes.py

user names now show id even when not adjacent

Update boxes.py

globally defined user_names_counter so it needs to be calculated only once

Update boxes.py

cleaning up the code a bit

Update boxes.py

black reformatting

made function in model.py to get username count

created a class variable in model class so that username count dict is calculated only once and using it to get number of users with same name and display id beside their name

black reformatting

black lint

isort

isort import order

reformatting

using .get() instead of the key and removing commented out code

squashing commits

reformatting

using .get() instead of the key and removing commented out code
@Sushmey
Copy link
Collaborator

Sushmey commented Dec 13, 2022

Hi @SRV332003
I am currently working on this issue with an active PR. If you wish to contribute to the repository, you may work on some other issue.

neiljp pushed a commit to Sushmey/zulip-terminal that referenced this issue Mar 22, 2023
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
neiljp pushed a commit to Sushmey/zulip-terminal that referenced this issue Mar 22, 2023
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
neiljp pushed a commit to Sushmey/zulip-terminal that referenced this issue Mar 22, 2023
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
@zulipbot
Copy link
Member

zulipbot commented Apr 3, 2023

@Sushmey You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!

Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Apr 25, 2023
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
@zulipbot
Copy link
Member

zulipbot commented May 5, 2023

@Sushmey You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!

@zulipbot
Copy link
Member

Welcome to Zulip, @Chan-Dong-Jun! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

@Chan-Dong-Jun Chan-Dong-Jun removed their assignment Feb 3, 2024
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Feb 7, 2024
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
Sushmey added a commit to Sushmey/zulip-terminal that referenced this issue Feb 9, 2024
Users with same name had their adjacent messages displayed under the same
header and no visually discerning feature was available for users with same
name. This solves that.

Fixes zulip#1151.
@zulipbot
Copy link
Member

zulipbot commented Apr 11, 2024

@Sushmey You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!

@vats004
Copy link
Collaborator

vats004 commented Jan 3, 2025

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Jan 3, 2025

Hello @vats004, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

@ellikamishra
Copy link
Collaborator

The code changes published for the above PR seem to be working locally. Issue: different users with same name seem appear as a single user on zulip terminal. Fix: display author_id along with author name to distinguish between users. Image one shows zulip terminal with the latest code of commits by 13th February 2024. Image two shows zulip terminal without the latest code of commits by 13th February 2024:

Image
Distinguishing IDs are visible.
Image(users appear to be same)
Author appears to be same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: message rendering bug Something isn't working good first issue Good for newcomers help wanted This issue should be clear enough to work on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants