Open Kharkiv07 opened 8 years ago
It appears to have something to do with capitalization, from a cursory look.
For reference, these are:
Curious... they're two together...
Both those requests now only show one conflict from AntiSpoof - and that's the name on the request itself. (And yes, I'm querying Wikipedia directly)
Possibly related to a difference in code between ApiAntiSpoof::execute() and AntiSpoofHooks::asAbortNewAccountHook(...) in the MediaWiki AntiSpoof extension.
160196 also doesn't show 2 similar usernames.
OK, so quick summary of my findings:
Reference | Example | Normalised | Discovered on Creation | Discovered on API |
---|---|---|---|---|
Requested Name | Name 00 | v2:NAME00 | N/A | N/A |
Conflict 1 | Name-00 | v2:NAME00 | Yes | No |
Conflict 2 | Name00 | v2:NAME00 | Yes | No |
This is an upstream problem, but I'll try and reproduce the issue locally.
Great, so there's a centralauth version of AntiSpoof too:
Opened a Phabricator task for this issue.
I ran into this today with 223123.
Urgh.
Both the requested account and the existing account are reporting the same normalised name, and both passing the AntiSpoof check, on both enwiki and mswiki (where the conflicting account is registered).
The existing account only exists on mswiki, no other wikis (incl. loginwiki).
I'll try and set up a centralauth+antispoof wiki somewhere and see if I can recreate this reliably for the phab task.
More requests with antispoof issues from what I've handled: 279250, 292208, 292325, 270660, 279099, 292315, 288385. I've noticed this often, I'll keep track of them and put them here periodically as long as it's useful.
I've had two requests today where the ACC anti-spoof checker did not label them as flagged-user needed, but when I went to create them I couldn't because of too similar accounts already existing.