this post was submitted on 17 Apr 2024
75 points (97.5% liked)
hexbear
10194 readers
1 users here now
Now that the old Hexbear fork has been officially abandoned, this community will be used as a space for meta-discussion on the site itself.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There is a difference between Username and Display Name. You can't "change" your username and it has different character requirements and is used for authentication. Display Name can be changed at any time using the Default UI and can be what ever you want and is not used for authentication.
Hexbear replaces the text field for Display Name with the pronouns drop down. It then combines your username with your pronouns and saves it in your display name field.
If you have API access you can update your display name to whatever you want because the UI is what enforces the pronouns not the server (as you identified).
The display name is used externally by other instances so it needs to remain compatible for federation. That way pronouns are displayed for users on other instances.
I'm not really sure if you can add validation to the field without breaking external users display names.
It's doesn't seem so difficult to me, we just have to check if local users have valid pronouns (valid in the sense of it's in a list that can be checked by a computer lol, not ideal but yeah) in their requested display name when they try to use the
save_user_settings
api. According to makotech222 elsewhere in the thread we actually used to have validation like this but the code got lost in an update