# 注册时提供空白用户名建议而非“UserN”

**URL:** <https://meta.discourse.org/t/offering-blank-username-suggestions-rather-than-usern-at-signup/391542>\
**Category:** UX\
**Tags:** fixed, signup\
**Created:** [2025年十二月17日 10:39 UTC](https://meta.discourse.org/t/offering-blank-username-suggestions-rather-than-usern-at-signup/391542 "2025-12-17T10:39:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [2026年一月8日 10:03 UTC](https://meta.discourse.org/t/offering-blank-username-suggestions-rather-than-usern-at-signup/391542/5 "2026-01-08T10:03:05Z")

</div>

> [@brenna12](#):
>
> 非常乐意看到这个功能被引入！🙂

它\_现在\_已经可以了 😉

> <https://github.com/discourse/discourse/pull/36830>
>
> When \`use\_email\_for\_username\_and\_name\_suggestions\` is disabled, the username sug…gester was falling back to generic usernames like "user1", "user2", etc. These suggestions are rarely helpful as they create indistinct usernames that users often accept without modification, resulting in forums populated with "user763", "user764", etc.
> 
> This change adds an \`allow\_generic\_fallback\` option to \`UserNameSuggester.suggest()\`. When set to false, it returns nil instead of falling back to generic "userN" usernames. The OAuth authentication flow now uses this option, leaving the username field blank so users must choose their own meaningful username.
> 
> Ref - https://meta.discourse.org/t/391542

---

_[View the full topic](https://meta.discourse.org/t/offering-blank-username-suggestions-rather-than-usern-at-signup/391542)._