On two separate Discourse instances — one that I admin — I’ve not been able to get my full name “Lou Quillio” to display. It does, however, display here on meta.
I flipped a lotta bits trying to figure out why. enable_names, prioritize_username_in_ ux, etc. How these are set (and whether a profile even has a full name) doesn’t always behave as I’d expect, but there’s still some edge case with my particular name.
The full name on my profile displays on posts if I change it to
But in my Discourse instances, when I add that final “o” with nothing after it, my full name vanishes from posts. Makes no sense. Gotta be a bug.
Added: Could it be because my collapsed, lower-cased full name matches my username, as “Tom Jones” matches tomjones?
I could change it to anything at all, but Discourse is the only case where I have to — in order to both keep my traditional username and fulfill my policy of always using my real name.
It really shouldn’t do the suppression silently. If this behavior is documented somewhere, my considerable Google Fu didn’t find it.
But I’d settle for the behavior seen here: If the stripped, case-insensitive Full Name matches the username, display only the Full Name. That’s preferable because a user can start typing @lou and autocomplete takes over.
Which combination of name settings does Meta use to achieve
There are site settings where admins can decide whether to prioritize name or username in discussions. So you can fix this on your own discourse instance but admins of other instances might have other preferences.
My username is also suppressed, like yours, for the reason explained by Jeff above. I like it, and in fact on my instance we have a real name policy and nearly all staff appear like this because their username and name are the same.