Skip to content
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

allow the user to prefer no more than one avatar per person in a room #3768

Closed
grahamperrin opened this issue Apr 29, 2017 · 7 comments
Closed
Assignees
Labels
A-Avatar O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users Sponsored T-Enhancement

Comments

@grahamperrin
Copy link

label:ui/ux

Enhancement request

Description

If I understand correctly: #106 assumes that where person A sets their avatar for the first time, the green circular A – not the set avatar – should persist for messages that were posted by that person before the change.

From the perspective of person B I find that confusing. For me the avatar of a person is simply, essentially, the graphical representation of the user or the user's alter ego or character; I associate an avatar:

  • with a user
  • not with a point, or a range, in time.

For me, to find multiple avatars for myself, or for any other person, on a single timeline, is counterproductive. It goes against my wish to form a mental picture of a person. Multiple avatars = multiple personalities, which might be what's intended by person A, but such inconsistencies make it difficult for me to put thing in context.

Adding a user preference should satisfy both:

  • people prefer to see multiple avatars per-person on a single timeline
  • people (like me?) who prefer to see just one per person on the timeline.

Thanks

Clarification

This request is not to discourage any writer from changing his or her avatar.

This request is to allow the reader to see just one avatar for the writer: the avatar that was most recently preferred by the writer.

Cross references

#660 – User Settings refinements
#106 – Historical user avatars can be buggy
#2984 – General UX Thread

@lampholder
Copy link
Member

I'm of a similar mind, but it is interesting that the first reaction was a thumbs-down - do some users have a strong preference for enforcing temporal avatar associations?

@lampholder lampholder added S-Tolerable Low/no impact on users feature P3 labels Apr 30, 2017
@ara4n
Copy link
Member

ara4n commented Apr 30, 2017

temporal avatars and displaynames are a very conscious choice in Matrix (just as in twitter & facebook they aren't temporal). Matrix rooms are effectively an immutable record of a conversation, which may be on the public record. Showing the correct avatars for historical conversations are critical, in my opinion, to correctly reflect the conversation that happened (especially if that conversation happened to be about the avatars, which happens relatively often)!

This is why we very deliberately preserve them. Of course, a client could chose to ignore historical avatars if it so desired, and if someone added an option to riot to do that we'd probably merge it, but it's far from vital imo.

@grahamperrin
Copy link
Author

@turt2live turt2live self-assigned this Feb 15, 2022
@turt2live turt2live added Sponsored O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience and removed P3 labels Feb 15, 2022
@turt2live
Copy link
Member

ftr: we have a labs flag for this coming up. matrix-org/matrix-react-sdk#7815

@T-bond
Copy link

T-bond commented Feb 16, 2022

uconfusing.ture gets merged, I hope that it will be optional. I also like very much the historical avatars, and I always wanted that in other messengers.

I can see the usefulness of showing only one avatar per user, especially in large public rooms, where you maybe not know everybody, it could get confusing if multiple avatar are shown.

@turt2live
Copy link
Member

part of the reason for the labs flag is to explore which preference, if any, the product team has based on user feedback. Generally we shy away from adding options, preferring instead to make sensible decisions in favour of the product direction.

@t3chguy
Copy link
Member

t3chguy commented Jun 8, 2022

Closing in favour of #22336

@t3chguy t3chguy closed this as completed Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Avatar O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users Sponsored T-Enhancement
Projects
None yet
Development

No branches or pull requests

7 participants