In the UX category, users discussed a significant issue where the signup process auto-populates the username field with generic suggestions like userN when email-based suggestions are disabled. JammyDodger highlighted that this creates a poor experience, resulting in forums populated by indistinct accounts (e.g., @user763). They proposed leaving the username field blank instead, allowing users to create their own names or utilize external generators, a practice already used in some admin signups. ToddZ strongly supported this, noting that generic usernames are rarely helpful and suggesting an optional setting if the current behavior must be retained. brenna12 echoed these sentiments, explaining that despite adding custom text to inform users the field is editable, many still accept the default UserXYZ style usernames. The discussion concluded with zogstrip announcing that the feature has been implemented via Discourse PR #36830, effectively fixing the bug and allowing the field to remain blank at signup.
Pulling this out into a separate topic as this is proving to be a significant bugbear on a site I’m involved with:
I think leaving it blank would be a much smoother signup experience as no one wants a forum populated by indistinct usernames (@user763, @user764, @user765), so the suggestions are rarely (if ever) helpful.
This would be a good solution for my community too, the username field auto-populates with an available username (in UserXYZ style). Although this field is editable, and I have added some custom text to make new users aware of this, we are still getting a lot of new users with default usernames 
Would be very happy to see this introduced! 
This topic was automatically closed after 20 hours. New replies are no longer allowed.
