matrix-org / matrix-spec

The Matrix protocol specification
Apache License 2.0
196 stars 96 forks source link

user configurable display name colors #835

Open HarHarLinks opened 3 years ago

HarHarLinks commented 3 years ago

Suggestion This suggestion already exists as a feature request by @compu42 to element at vector-im/element-meta#841. Since it requires an MSC, I will summarize here. This feature should be considered optional.

There are a couple reasons for supporting this feature, including:

Implementation ideas and details:

Counter-arguments

amytimed commented 2 years ago

I think this should be implemented and would greatly benefit Matrix

HarHarLinks commented 2 years ago

For reference, in the last couple versions (at time of writing) of Element Android https://github.com/vector-im/element-android/pull/2614, it is possible to "Override nick color" of all users including yourself on a per-room basis by entering a CSS style #ABCDEF hex color value. There is a PR that mirrors the same function in the react-sdk (i.e. Element Web/Desktop): https://github.com/matrix-org/matrix-react-sdk/pull/5626

k8ieone commented 2 years ago

What's required to turn this into an MCS PR? This feature is totally a must-have!

TheRedXD commented 1 year ago

Alright, why in the world is this still an open issue and nobody has taken care of it?

In my humble opinion, the colors should be role-based or at least be changeable by the user itself, but I would prefer for them to be role-based. Upon creating a role, a user could assign it a color, so that you do not need to click on the profile to see what role this user has. It would simply be color-coded!

This implementation would give the colors an actual purpose rather than just be a randomly assigned color that you can't really change.

I'd like to see this added and in my opinion, this would greatly benefit the matrix.org experience!

epicEaston197 commented 1 year ago

I am appalled that this has not been implemented yet. is there any good reason why this has not been implemented yet? and it seems like it's such a simple feature Like it's just epicEaston197

KitsuneRal commented 1 year ago

What's required to turn this into an MCS PR? This feature is totally a must-have!

The process is published here: https://spec.matrix.org/latest/proposals - anybody caring about the feature beyond leaving a "why is this not implemented" comment is welcome to write a Markdown document and submit it along the lines of that process.

sublimeclemency commented 1 year ago

i am looking forward to this feature!

unknown-user-9246102101 commented 1 year ago

Order of application of potential colors are important.

  1. Default - Current rules applied, hash theme dependent
  2. User supplied self colorization IF set. Can minimize user intentionally bad colors or theme inapplicable by having preset hex codes in alongside a color picker and an extra click to custom at end of listing.
  3. Room Admin of a particular Group/Role IF enabled to override user supplied to use particular colorpicker OR default hash.
  4. Room Admin of a particular User which overrides all previous to use specific or default.
  5. Accessibility settings to apply to a Role and then User.
fevers commented 8 months ago

What's required to turn this into an MCS PR? This feature is totally a must-have!

The process is published here: https://spec.matrix.org/latest/proposals - anybody caring about the feature beyond leaving a "why is this not implemented" comment is welcome to write a Markdown document and submit it along the lines of that process.

This was originally submitted as a proposal, and was subsequently transformed into a pull request for unknown reasons. I can't speak for anyone else here, but personally I don't understand why you would expect me to believe that wouldn't happen again, even if I did go to the trouble of figuring out how to follow the abstruse and unwieldy proposal process.

morguldir commented 7 months ago

This was originally submitted as a proposal, and was subsequently transformed into a pull request for unknown reasons. I can't speak for anyone else here, but personally I don't understand why you would expect me to believe that wouldn't happen again, even if I did go to the trouble of figuring out how to follow the abstruse and unwieldy proposal process.

If you’re referring to the repo move, both issues like this one, changes to the spec, and proposals used to live in the same repository. They changed that, and now the original repo is just for proposals, while the spec and things that aren’t a full proposal yet live here