# Discourse dislikes my full name

**URL:** <https://meta.discourse.org/t/discourse-dislikes-my-full-name/129173>\
**Category:** Feature\
**Created:** [September 21, 2019, 3:36am UTC](https://meta.discourse.org/t/discourse-dislikes-my-full-name/129173 "2019-09-21T03:36:26Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**Post date:** [September 21, 2019, 6:17pm UTC](https://meta.discourse.org/t/discourse-dislikes-my-full-name/129173/7 "2019-09-21T18:17:57Z")

</div>

> [@louquillio](#):
>
> 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.

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.

Here’s how I have them set:

 ![54%20AM](https://global.discourse-cdn.com/meta/original/3X/1/9/190282f163b5fcb6edf9b098fcd3b0c2fb8e0185.png)

to get:

 ![18%20AM](https://global.discourse-cdn.com/meta/original/3X/f/f/ff55585334ac1c626d851d94196a702e933be8cc.png)

My username is also suppressed, like yours, for the reason explained by Jeff [above](https://meta.discourse.org/t/discourse-dislikes-my-full-name/129173/2). 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.

---

_[View the full topic](https://meta.discourse.org/t/discourse-dislikes-my-full-name/129173)._