We ran into the same question with WIP where initially it was all based on Telegram usernames, but we then made having a Telegram account optional. Same with BetaList where we only used Twitter OAuth, but more recently added regular signups.
There isn’t a super clean solution.
What I ended up doing is letting the user choose their own username, but pre-fill it with their OAuth service name if available.
It hasn’t lead to any issues.
One extra benefit is that it gives people an incentive to sign up early to claim their desired username.
We ran into the same question with WIP where initially it was all based on Telegram usernames, but we then made having a Telegram account optional. Same with BetaList where we only used Twitter OAuth, but more recently added regular signups.
There isn’t a super clean solution.
What I ended up doing is letting the user choose their own username, but pre-fill it with their OAuth service name if available.
It hasn’t lead to any issues.
One extra benefit is that it gives people an incentive to sign up early to claim their desired username.
It's very possible I'm just thinking it will create issues of users with name overlap complaining that their names are not available.
The extra benefit of driving people to sign up early is actually a pretty nice incentive.
Thanks for the feedback.