Voorkom dat Google OAuth2-gebruikers gebruikersnaam "user1", "user2" krijgen...?

[ToddZ]

I prefer (thus far anyway) to run my forum showing usernames vs. real names, and I’ve made the real name field optional.

But some of my Google OAuth2 (“Sign in with Google”) users have gotten what are apparently default usernames of “User1”, “User2”, etc.

I really don’t like having these generic defaults in the mix.

It looks like this occurs here on meta as well:

I don’t know why this happens for a few Google OAuth2 users but not for most. I’d welcome any insight.

I suppose I could rethink my emphasis on usernames. But is there any way to prevent this “User[X]” behavior, short of disabling Oauth2 signups?

[chapoi]

@ToddZ

I don’t know why this happens for a few Google OAuth2 users but not for most. I’d welcome any insight.

Bit of guesswork on my part, but could it be that their usernames contained spaces or special characters? That’s not allowed in Discourse usernames.

But @pmusaraj will know a lot better, I’m curious too now

[pmusaraj (Penar Musaraj)]

I am pretty sure this is coming from this site setting

If unchecked, the username picker will default to userN, especially if the user doesn’t have a display name in their upstream account.

Security 1, convenience 0

[ToddZ]

@pmusaraj

If unchecked, the username picker will default to userN, especially if the user doesn’t have a display name in their upstream account.

Thank you! This exact explanation would be a useful addition to the option text.

I may end up checking that box. Since people can edit the suggested names, the risk seems low.

[lindsey (Lindsey Fogle)]

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?

[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.