Continuing the discussion from Full name isn't shown on post when it matches username:
We’re seeing some users without names on our forum
john_doe
now has a name of John Doe
but the proper name isn’t shown.
The result is that posts in the community aren’t uniform, since so many people have that first_last format.
It would be nice if this were more uniform (even if exact matches still get excluded)
1 Like
john_doe does match John Doe from our perspective.
It’s not making sense to me or my end-users.
I do see why you don’t want to output john_doe john_doe
, but I don’t see the issue with john_doe John Doe
1 Like
Underscore is almost universally used as a space in fields that do not allow spaces. So it is part of the comparison.
I understand the technical comparison. I also understand the stated desire not to print redundant information:
But the implementation is causing confusion and frustration for users in my forum, and on here on meta.
My wish - to dedupe only exact matches. allowing for changes in space and case to be enough to show both pieces of information.
True, this is a duplicate of that topic, and a feature request.