Changes between Version 16 and Version 17 of SiteUpgradeProposal/UserClearance


Ignore:
Timestamp:
Jul 29, 2012, 11:08:19 PM (12 years ago)
Author:
Steffen Hoffmann
Comment:

mark one more check as available in AccountManagerPlugin

Legend:

Unmodified
Added
Removed
Modified
  • SiteUpgradeProposal/UserClearance

    v16 v17  
    2828 * 2: plan: use REGEXP combined with 1
    2929 * 3: plan: use REGEXP combined with 1 + 2
    30  * 4: solved: use `username_char_blacklist = : []` - note the blank in-between
     30 * 4: solution: use `username_char_blacklist = : []` - note the blank in-between
    3131 * 5: plan: best to approach with a blacklist of character sequences, each on a line, read from a dedicated wiki page
    3232 * 6: ''more discussion required'': not easily done by blacklisting or similar code, maybe moderation (#843) is the best approach here, but that would largely obsolete the other points and shift all the burden towards moderators, what might or might not be acceptable
    33  * 7: plan: extend existing checks towards being optionally case-less
     33 * 7: solution: use `username_dup_case = true` to extend existing checks towards being optionally case-less (''since [11829]'')
    3434
    3535Of course that doesn't help for existing accounts, and we need to called the following users for clearance: