-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Use consistent color generation for nicks (XEP-0392) #1191
Comments
Right now profanity shows the online status by color of the nickname in the occupants list. Will this behavior remain? |
Good point. Your suggestion makes sense. I can also see me implementing it as a setting. |
According to the XEPs business roules it SHOULD be optional anyways:
* Implementations SHOULD allow the user to turn off any colorization
completely.
*Implementations SHOULD implement the Color Vision Deficiency profiles
and SHOULD allow the user to choose any of these profiles or to disable
the correction.
* Implementations MUST NOT share the Color Vision Deficiency correction
settings with other entities.
…On 25.09.2019 02:59, Michael Vetter wrote:
Good point. Your suggestion makes sense. I can also see me implementing it as a setting.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1191 (comment)
|
Which means generally turning of this color feature, not individual for the roster/occupants. |
Implement settings for redgreen and blue blindness. Regards #1191
Is done now in developemtn, including color vision deficiancy. Regards profanity-im/profanity#1191
`/roster color on|off` to enable or disable XEP-0392 also for the roster. Regards #1191
`/occupants color on|off` to enable or disable XEP-0392 also for the MUC occupants. Regards #1191
Colors for the roster and occupants can now also be enabled! |
Expected Behavior
Have a consistent color for nicknames (etc).
Current Behavior
Use the color defined in the theme.
Solution
We should implement XEP-0392.
The text was updated successfully, but these errors were encountered: