Last modified: 2008-10-19 18:47:55 UTC
AntiSpoof would block the vandal "User:Something." from being created if "User:Something" already exists for example. But this only works on one wiki. Please make AntiSpoof run it's checks at both the local and global level to stop confusable global usernames. Kylu says this necessitates a whole new extension: "<kylu> you'd need a whole new extension to implement antispoof in ca"
One issue (there are possibly more):
* Unifying manually where a conflict occurs. Most probably this should be permitted, since users merging accounts manually are probably OK.
I think this would make AntiSpoof require CentralAuth to be installed, if you simply modified AntiSpoof. You could test for CentralAuth, but it might be better to simply fork AntiSpoof instead into a CA-specific modification: This way, you have one codebase to test and not worry about if a fix to one side breaks something on the other. Bugfixes can be ported.
A fork of AntiSpoof shouldn't be necessary - AntiSpoof could simply check for the presence of CentralAuth, and additionally run its checks against the global account list. A single codebase is a good thing :)
*** This bug has been marked as a duplicate of bug 15545 ***