Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
To be clear, some really great community members have these names, but they're everywhere now. And with the right characters you can create some really annoying overlaps: https://github.com/LemmyNet/lemmy/issues/3790
Enough of them floating around now that I'll probably do a PR for my favorite client to filter them out.
This reminds me of a situation previously where a user's pronoun wasn't visible to another user because their client did not show display names
A solution for this that doesn't alienate usernames with pronouns and non-latin languages will be tricky IMO, to be honest I'd just leave it as-is since the fancy display names I've seen so far aren't excessive or abusing unicode modifiers.
Just because people use display names for that doesn't mean display names are a good place to indicate pronouns, and it especially doesn't mean that having a client use usernames is alienating anyone who currently puts non-name data in a name field.
I'd much rather there be a dedicated field where it can be treated with the importance it deserves and not just lumped in with other miscellany as a kludge.