--- Comment #10 from Steven Walling <> ---
(In reply to Tyler Romeo from comment #9)
> (In reply to Jon from comment #6)
> > Out of interest why does this matter? I  seem to have missed the problem
> > here.
> > 
> > If I register with the username "an  unusual username" and it gets corrected
> > to "An unusual username" in my opinion as long as if I login with username
> > "an  unusual username" and it still logs me in as that user (if it doesn't
> > then in my opinion that is the bug here) it shouldn't be a problem.
> What if you register "this__is__my__username" and it gets corrected to "This
> is my username"?

This is part of the problem. This is basically the first time I've heard this
brought up. On the Design list where this was brought up, I don't think anyone
shared a list of everything canonicalization currently does? 

On top of that, no one knows how often any of these cases *actually happen*.
It's entirely possible that hundreds of thousands of new account creators
register with lowercase via mobile, and less than 1,000/year do with
underscores. Or the opposite. Or neither. We don't know. 

The fact that the problem is partially undefined and definitely unmeasured
makes it difficult for people who care about having a clean, not annoying user
experience accept that we should throw additional warnings and barriers at so
many users during a critical step. 

> Also, when a username is canonicalized, it is passed through
> $wgAuth->getCanonicalName(), which could do literally *anything* to the
> username depending on what authentication extension you have installed.

We can't design a case for "literally anything". We can only design for what we
might reasonably think would happen to users.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to