ToddZ prefers displaying usernames over real names on his forum and has made the real name field optional. However, some Google OAuth2 users are assigned default usernames like ‘User1’, ‘User2’, which he dislikes. This issue also occurs on meta.Discourse. chapoi speculates that this might happen if the original username contains spaces or special characters. pmusaraj explains that this behavior is due to a site setting that, when unchecked, defaults to ‘userN’ if the user lacks a display name in their upstream account. ToddZ suggests improving the option text to include this explanation and considers enabling the setting. lindsey proposes leaving the username field blank instead of suggesting ‘userN’ when the email-based suggestion is disabled, and ToddZ agrees, preferring users to create their own usernames or use a generator API. He suggests an optional setting to cater to different preferences.
Wanneer e-mailadres gebruiken voor gebruikersnaam en naam suggesties is uitgeschakeld, kunnen we het gebruikersnaamveld leeg laten bij registratie in plaats van userN voor te stellen — we hebben iets soortgelijks gedaan bij het registreren van onze beheerdersaccounts op nieuwe Discourse-sites.
Is dat iets waarvan u denkt dat u het ook voor uw siteleden zou willen zien, @ToddZ?
I would much prefer that, myself. I’d rather see people mash the keyboard and come up with a nonsense username (or hook into a username generator API) than end up with a bunch of userN.
I can’t quite imagine a reason to prefer userN, but if I’m missing something, maybe an optional setting could make everyone happy.