sourceforge: IdeaTorrent

Written by astara the 14 Mar 12 at 01:00.

And instead of disallowing lowercase usernames , support at least the standard MS supports -- of Preserving but ignoring case. -- that will prevent problems with case issues, or ID's differing only in case.

It would be more user friendly and smarter -- especially to allow those who had uppercase user names to login without having to go through email recovering when they aren't ssure what email account a login went to ..... *whistling innocently***.....

And instead of disallowing lowercase usernames , support at least the standard MS supports -- of Preserving but ignoring case. -- that will prevent problems with case issues, or ID's differing only in case. It would be more user friendly and smarter -- especially to allow those who had uppercase user names to login without having to go through email recovering when they aren't ssure what email account a login went to ..... *whistling innocently***.....

Written by lindaathena the 4 Apr 12 at 20:29.

I used to login with 'LindaAthena'. It was saved in 3 separate browsers.

I had to use password retrieval to login because the login screen would not accept my original signup username. You may never have allowed upper-case in usernames, but it was accepted and quietly converted to lower case behind the scenes -- so this was transparent to us. If you believe they were never allowed, I would bet the change was in the front-end web code -- that it, internally changed a typed name to all lower case before storing it or comparing it against the userbase.

Perhaps passwords used to be case insensitive, and that was changed, so someone decided to also strip the case lower-code for entering user names?

Whatever the case, if you only accept lower case user names, then good user-interface design would dictate that you would ignore case (and always convert to lower case before doing compares). I have a feeling that might be what was done, but that it also was done for passwords. Someone noticed that case was ignored in passwords fixed it, and noticed the same issue with logins and "fixed" that too.

It also might be related to moving to HTML5, using UTF-8 instead of iso-8859-1. In the latter, changing case was a simple as "|" (or) with 0x20. But it's a bit more involved in UTF-8.

I used to login with 'LindaAthena'. It was saved in 3 separate browsers. I had to use password retrieval to login because the login screen would not accept my original signup username. You may never have allowed upper-case in usernames, but it was accepted and quietly converted to lower case behind the scenes -- so this was transparent to us. If you believe they were never allowed, I would bet the change was in the front-end web code -- that it, internally changed a typed name to all lower case before storing it or comparing it against the userbase. Perhaps passwords used to be case insensitive, and that was changed, so someone decided to also strip the case lower-code for entering user names? Whatever the case, if you only accept lower case user names, then good user-interface design would dictate that you would ignore case (and always convert to lower case before doing compares). I have a feeling that might be what was done, but that it also was done for passwords. Someone noticed that case was ignored in passwords fixed it, and noticed the same issue with logins and "fixed" that too. It also might be related to moving to HTML5, using UTF-8 instead of iso-8859-1. In the latter, changing case was a simple as "|" (or) with 0x20. But it's a bit more involved in UTF-8.