Screenshot / Code Snippet
It's hard to miss these days - the Code of Conduct is about to change. It will emphasize the importance of using the correct pronoun when referring to a user in third person. This most often comes up in chat, and some users already have information about which pronouns to use in the 'about' field in their chat profile, especially when that is not already clear from their username and/or avatar. Version 2.0 of the script performs the same feat on Q&A pages, but uses the Q&A profile instead.
In the Teachers' Lounge, an idea was proposed to pull that information from the user profile into the chatroom itself through a userscript. Stack Exchange Chat hasn't received updates in quite a while, so this idea isn't likely to be implemented soon. A userscript like this is the next best thing.
Installation / configuration
It's a userscript which means you need a userscript manager installed in your browser if you don't have one already. Just Google for Violentmonkey or Tampermonkey, how to install them depends on your browser.
After installation, you can reload this very page and check my usercard to verify if the script has been installed:
To edit your chat profile to add your own pronouns, go to chat, click your username in the top bar and then the edit link for the 'about' field:
Editing your Q&A profile works similarly, but you can also click this link, change your profile and click "Save and copy changes to all public communities".
The script looks (case-insensitive) for the following ways of specifying pronouns:
- A link to Pronoun Island, e.g. 'http://my.pronoun.is/he'
- An explicit specification starting with 'Pronouns:' and ending with a period, newline, or just the end of the text, e.g. 'Pronouns: they/them.'
- Pronouns joined by forward slashes, e.g. 'she/her'; a full list of supported pronouns can be found here which is sourced from Pronoun Island. If your pronouns aren't in the list, feel free to mention them here or make a pull request. Do note that some of the pronouns listed here are likely to yield false positives because they're specialized terminology (e.g. vi/vim).
Tested with Violentmonkey in Firefox and Tampermonkey in Chrome on macOS, but it's likely to work on all browsers and platforms. (Please let me know if it doesn't!)
Post a comment or answer here, or create an issue/pull request on GitHub.