# Reserve usernames containing forum name by default

**URL:** https://meta.discourse.org/t/reserve-usernames-containing-forum-name-by-default/101016
**Category:** UX
**Created:** [October 31, 2018, 10:28pm UTC](https://meta.discourse.org/t/reserve-usernames-containing-forum-name-by-default/101016 "2018-10-31T22:28:04Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [October 31, 2018, 10:28pm UTC](https://meta.discourse.org/t/reserve-usernames-containing-forum-name-by-default/101016/1 "2018-10-31T22:28:05Z")

</div>

Continuing the discussion from ["Block" renamed to "Silence"](https://meta.discourse.org/t/block-renamed-to-silence/73991/16):

> [@Specifically, what does “Silence” do?](https://meta.discourse.org/t/specifically-what-does-silence-do/287184/6):
>
> I needed to get a user to change his username (because he used our forum’s name as his user name)

My hunch is that this is quite common and it wasn’t until recently that I noiced that there is quite a simple way to prevent this: just add `*<forumname>*` to the reserved usernames. Done.

Wouldn’t it be a great service to forum admins if every new discourse instance would create this reservation by default?

* * *

As an aside: I meant to create this topic in #Contribute > UX but for unknown reasons I can only choose between #Contribute > Feature and #Uncategorized

 ![Screenshot_20181031-232355](https://global.discourse-cdn.com/meta/original/3X/1/6/169ae977d5050327f63cfdf3bba463a50e0c219c.jpeg)

I suppose I’ll be able to fix the category as soon as I’ve posted this and I will do so, but I wanted to quickly mention this UI bug.
