Open Bug 1372631 (bmo-login-names) Opened 7 years ago Updated 3 months ago

Allow login_name to be changed to any unique string provided the user has at least one additional email address

Categories

(bugzilla.mozilla.org :: Email Notifications, enhancement)

Production
enhancement
Not set
normal

Tracking

()

People

(Reporter: dylan, Unassigned)

References

(Depends on 3 open bugs, Blocks 3 open bugs)

Details

(Keywords: bmo-ux, Whiteboard: [october-2019-bmo-triage])

1. Accounts can be renamed to not include an '@', provided there is a verified and preferred email in the profile's additional emails table.
2. It will not be possible to register a new account without an /@/, this can be accomplished later.
Depends on: 1372638
No longer depends on: bmo-multi-emails
Why should there be a requirement for an additional email address? I don't recall any mention of such a requirement in the discussion in bug 218917.

I;'m curious as to the logic behind requiring an additional email address. Personally, I prefer to limit the addresses I provide to third parties to limit my risk exposure. Requiring me to give up yet another address simply to avoid exposing my address seems partly counter-productive. Perhaps I'm not grasping the entire concept, however, which is why I ask.
My bug was duped here but the original description of this bug is so short that it is not possible for me to say to what extent it may be a dupe.

A more detailed description with examples may be sufficient to discourage me and others from generating further dupes.
I would concur. A suitable name here would be something like "allow non-email address usernames in BMO" or something to that effect.

Still wondering about the multiple email address requirement, though...
Depends on: bmo-multi-emails
Blocks: 1352571
Alias: bmo-login-names
Assignee: nobody → dylan
I'm taking this as I'll probably be doing this in the harmony branch on my own time, if some other things pan out.
Keywords: bmo-ux
Blocks: 1476503
Depends on: 1501693
Type: defect → enhancement
Assignee: dylan → nobody

I concur with Mike and was outraged when I first sign in with github and noticed that my information was leaked. However, I will also give the administrators this much credit: technically a data skimming bot would need to create an account here in order to see the email addresses.
Not that that's exactly difficult, but at least it's not COMPLETELY AND UTTERLY PUBLIC. Just behind the digital equivalent of a cardboard door with a papier-mâché lock.
Is there anything I can do to help move this along? Also, can you make it so that it will still recognize users that login with github even if the username is not the github email (even if the email has to be somewhere on the account)?

Duplicate of this bug: 1850984
Duplicate of this bug: 1859343
Duplicate of this bug: 1864717
You need to log in before you can comment on or make changes to this bug.