Last modified: 2012-03-03 17:03:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8257 - AntiSpoof blocks usernames too aggressively
AntiSpoof blocks usernames too aggressively
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AntiSpoof (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-12-14 03:33 UTC by Aryeh Gregor (not reading bugmail, please e-mail directly)
Modified: 2012-03-03 17:03 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-12-14 03:33:00 UTC
As discussed at URL, AntiSpoof is too aggressive because it's only a one-pass
normalization.  For instance, L = i because L = l = I = i.  A number of users
have complained because they couldn't sign up with their new name anymore, and
doubtless many others have been distressed to find name after name "taken".  The
reasonable solution, again as discussed in the URL, would be using the
normalization as a first pass, and then doing a more intensive pairwise
comparison to figure out whether the specific characters are similar
non-transitively.  L = l and maybe l = i, but L != i.
Comment 1 Mike.lifeguard 2009-06-18 02:50:36 UTC
Is this still relevant? I haven't heard complaints about too-aggressive matching, only not-aggressive-enough matching (c.f. imposter series on checkuser-l etc).
Comment 2 Mike.lifeguard 2009-06-18 02:51:07 UTC
Also, the URL is dead.
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-06-18 13:49:28 UTC
Of course you haven't heard complaints about too-aggressive matching, because the affected users are unregistered.  They either picked a different name and forgot about it, or gave up.  Not-aggressive-enough matching will only hurt registered users, and in particular established users who trolls want to impersonate, so they'll be much more likely to make a fuss.

URL fixed.
Comment 4 Mike.lifeguard 2009-12-31 05:24:18 UTC
(In reply to comment #3)
> URL fixed.

Thank you.

I tested this, with the same result as initially reported. I'm not sure the must-contain-letters rule makes a lot of sense. What was the original motivation?

Comment 5 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-12-31 19:08:13 UTC
I don't know.  I assume someone was just throwing together some rules and picked whatever seemed to make sense at the time.  There are a heck of a lot of Unicode code blocks.  For a couple of years it was blocking all [[hangul]] names by mistake, IIRC.

Note You need to log in before you can comment on or make changes to this bug.