Last modified: 2013-09-04 05:18:00 UTC
Some of the usernames that currently exist would not be accepted by the current system if registed today, this includes: * Usernames with the letter "/" in them * Usernames that start with a lower case letter I've made a list of these usernames using maintenance/checkUsernames.php and put the log in /home/wikipedia/logs/checkUsernames.log (linked in the url to this bug) These should Ideally be changed by local beaurocrats of these wikis using the Special:Renameuser extension which as of 2005-09-19 needs to be modified to accept invalid input to be useful for this.
Unless avar still has the listing, there's nothing further we can do about this bug (if it hasn't been done already in the last 2 years).
Well, there is - we can generate another listing using his script, or another script, and advise those users of the need to rename their accounts. (Special:Renameuser will now accept "invalid" username input for the original username, provided that the user row exists...)
Please don't close bugs just because they're old.
*** Bug 3501 has been marked as a duplicate of this bug. ***
For another example, see the usernames with double spaces referred to in dupe bug 3501.
*** Bug 5230 has been marked as a duplicate of this bug. ***
This is related to bug 323; assuming a properly-coded Special:Renameuser, renaming users with invalid names should cause all their edits to display in Special:Contributions.
AFAIK this would only work if the rev_user field in the revision table or the r_user field in the archive table is not 0. The above values are always 0 for edits from before the introduction of the Phase II software, as shown at: http://en.wikipedia.org/wiki/User:Nemo_bis/Bug_323_revisions It would also not work where duplicate usernames are involved such as "Larry_Sanger" and "Larry Sanger". In the latter case, those usernames should ideally be merged.
* Rename users of which their edits have a _user higher than 0 in the other tables and do not conflict with an existing username ** If proof is found that they are the same, merge users ** If user is still active rename to something else with their permission * Otherwise: Leave it be for now That should clean up most cases, right ?
Related URL: https://gerrit.wikimedia.org/r/64243 (Gerrit Change Idb4b84b853f4f86e90a470e937af9017cee15e44)
Related URL: https://gerrit.wikimedia.org/r/64246 (Gerrit Change Idb4b84b853f4f86e90a470e937af9017cee15e44)
Related URL: https://gerrit.wikimedia.org/r/64247 (Gerrit Change Idb4b84b853f4f86e90a470e937af9017cee15e44)
Created attachment 12333 [details] Output of checkUsername reedy@terbium:~$ grep \: checkUsernames.log -c 1193 1193 bad usernames on all WMF wikis List grouped by dbname attached
MariaDB [enwiki_p]> select * from user where user_name = 'ɑʀʇʉʀɵ'\G *************************** 1. row *************************** user_id: 3103938 user_name: ɑʀʇʉʀɵ user_real_name: user_password: user_newpassword: user_email: user_options: user_touched: user_token: user_email_authenticated: user_email_token: user_email_token_expires: user_registration: 20061226002342 user_newpass_time: user_editcount: 39 1 row in set (0.03 sec) --- "ɑʀʇʉʀɵ" gets transformed to "Ɑʀʇʉʀɵ".
(In reply to comment #14) > "ɑʀʇʉʀɵ" gets transformed to "Ɑʀʇʉʀɵ". A more recent example of that was [[user:ɱ]] (now Ɱ), with the lowercase "latin small letter m with hook / left-tail m" that didn't get consistently normalised to its capitalised/uppercase version. I can't find the bug for that, if any was filed, but it may require a core fix first hence a separate report.
