I think without a moderation step for the text field it would be prone to abuse so I would go with the drop down list and have users suggest new ones to be added when needed.
I will see how much time I have to volunteer to this but I’d break it down to the following. Which obviously would change as worked on but a rough outline of the work:
1. Add pronouns to user settings. Make it available in the Graphql API as such:
Pronouns being a new data type called
UserPronouns with an ID and Text. For example:
With the options in a dropdown:
None <- default, doesn't store anything against the user
2. Display pronouns on profile and channel page
We’d then surface the pronouns next to the name on a profile page:
And as a tag like ‘English’ and ‘Mature’ on the channel page (if present)
3. Streamline chat bubbles in preperation for pronouns badge
I think we could streamline the chat bubbles like suggested in this thread before adding pronouns to the chat. This will make the work more easy to break up.
4. Add pronouns to chat with privacy settings
In the user settings we would need to have some way to specify where the pronouns are now shown. This could be checkboxes:
- Show pronouns on profile/channel pages
- Show pronouns in chat
These would be defaulted to ‘true’.
We could see this surfaced in the data by added these fields to
UserPronouns. We’d now have:
The profile/channel pages would need to be updated to respect this new option.
We would then need to add a badge for the pronouns to the chat again respecting the privacy controls.