Last modified: 2013-09-18 06:57:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T56251, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54251 - Antispoof complaint
Antispoof complaint
Status: VERIFIED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-17 23:55 UTC by Tristan Verheecke
Modified: 2013-09-18 06:57 UTC (History)
2 users (show)

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


Attachments

Description Tristan Verheecke 2013-09-17 23:55:05 UTC
I don't know the workings of Antispoof, but it seems to me that it was created for something specific; to distinct Admins or maybe other important users from others. However it effects all usernames, which to me just is not approriate. i wanted to register with my favorite username "lLenn" only to be told that "LLenn" (note: double capital l) and that it resembles the username "Lienn". Now, I can understand the importance of this tool, but please, either have a blacklist of words to check against or just remove this extension.
Comment 1 Sam Reed (reedy) 2013-09-18 00:15:40 UTC
There's no way you can have lLenn if LLenn already exists, irregardless of 

MediaWiki is case insensitive on the first character, so lLEnn and LLenn are the same.

How can we have a blacklist? It's purposely there to prevent "versions" of the same name (spammers "prentending" to be other users)
Comment 2 Tristan Verheecke 2013-09-18 00:31:10 UTC
Sry, a small grammarmistake on my part, the "and that it" after the brackets shouldn't be there. I meant to say: Only to be told that "LLenn" resembles "Lienn".
Comment 3 Tristan Verheecke 2013-09-18 00:37:29 UTC
But, you know, nevermind, not that I can be pissed off at the developers for implementing stupid shit because they're scared of spammers. So I apologize. So, how's it going with captha? Have robots surpasses the humaneye yet?
Comment 4 p858snake 2013-09-18 01:09:29 UTC
(In reply to comment #1)
> How can we have a blacklist? It's purposely there to prevent "versions" of
> the
> same name (spammers "prentending" to be other users)

Well sysops can override it if they want, But I doubt there are many cases.


(In reply to comment #3)
> But, you know, nevermind, not that I can be pissed off at the developers for
> implementing stupid shit because they're scared of spammers. 

It's more than spammers, Personally I don't want someone to create a name visually similar to mine by using a exotic unicode character to the likes.
Comment 5 Tristan Verheecke 2013-09-18 01:27:09 UTC
(In reply to comment #4)
> It's more than spammers, Personally I don't want someone to create a name
> visually similar to mine by using a exotic unicode character to the likes.

I understand, I always disliked the fact that somebody else got to register my username before me and maybe that's why I freaked out this time, because it's the first time I'm told that somebody else has the same nick similar to mine. After some thinking, I have cooled down and can understand the reasons behind it.

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


Navigation
Links