Reserved Usernames

AI-generated summary

The discussion revolves around the feature of reserving usernames in Discourse. nahtnam initially asks if there’s an option to reserve usernames, and riking mentions that it already exists as a fixed list but suggests changing it to a SiteSetting. However, there’s no UI to add to the list, and the current workaround is to suspend users who sign up with reserved names or register accounts for every desired username.

Omni emphasizes the need for a tool to reserve usernames, as suspending users can be traumatic and inefficient. codinghorror adds the feature to the 1.4 release plan, and mbauman confirms that it was implemented as a site setting called “reserved usernames.”

Hey!

Is there an option for reserving usernames? I cant find it. There should be a textarea where we can just have a list of reserved usernames where users cant sign up with those.

5개의 좋아요

This already exists somewhere in the code, but it’s just a fixed list with entries like admin and staff.

Changing it to a SiteSetting could make sense.

4개의 좋아요

Is there a way to add to that list through the UI?

That would be what “changing it to a site setting” means.

1개의 좋아요

Ok… Is there a temporary work-around for this? Where in the code is this?

The workaround is to suspend anyone who signs up with that name.

1개의 좋아요

Then when it comes time to make an account with that username, what would I do?

1개의 좋아요

You could just register an account for every username you want to reserve, and then just hand over the details to whoever you were reserving that username for.

I guess thats the only way. :frowning:

I was looking into this not too long ago.
It would be helpful to have a tool which allows Discourse admins to reserve usernames.

Suspending a user right after they join could be traumatic, or simply leave a bad taste in their mouth. In my honest opinion, users should not be punished due to selecting a username they were originally allowed to choose.

Sure, there are some who do not view this as punishment. However, it’s hard enough to simply get people to join a website. Adding more work into the mix could push the user away, recreating an account. Going further into this, the user who was suspended upon joining might have a loud enough voice which could push away others.

The next course of action would be for an administrator to create user accounts for every username they wish to reserve. This seems inefficient, as not only does creating an account take more time than adding a string to a list, but the result leads to data based off the account. The account’s data would no longer be genuine, and would more than likely have to be reset to preserve authenticity.

I’m sure that the Discourse project has many priorities, and a feature like this would be rather low on the totem pole. However, I am crossing my fingers to one day see this available.

1개의 좋아요

I thought @riking added a reserved username feature? Am I mis-remembering?

No, it already existed, and I was looking at expanding it, but never got around to it.

I actually forgot which source file it’s in…

2개의 좋아요

I agree with omni. This is something other forums have (SMF forum).

1개의 좋아요

I added this to the 1.4 release plan.

3개의 좋아요

Yes. It should be a setting.

이런 기능이 실제로 구현된 적이 있나요?

수정: 아, 그렇군요. 여기서 검색하기 전에 사이트 설정을 먼저 검색해 보았어야 했습니다. 적절하게도 reserved usernames(예약된 사용자 이름)이라는 이름의 사이트 설정이 있네요!

1개의 좋아요