There are several users by the names that has a similar username to the one you have been renamed to. They are currently inactive, so they should not cause any issues. However, if they do return and confusion arises, you may need to request another username change.
Documentation
edit- Description
This template is used on WP:CHUS to notify renamed users about AntiSpoof conflicts that arise while renaming. Currently, there is no official policy regarding the renaming of users to usernames that hit the AntiSpoof filter; said policy is currently being discussed at m:Talk:Steward_requests/Username_changes#Accounts_with_similar_usernames.
This template should only be used when the requested username collides with a similar username belonging to an account that is not active. The unofficial guidelines are:
- If the similar usernames have made no edits and are over six months old, the request can be processed.
- If the similar usernames have made less than 15 edits and the last edit/log entry was over a year ago, the request can be processed.
- If the similar usernames have made more than 15 edits, is less than six months old, or when the last contribution was less than a year ago, decline the request.
If the request hits the AntiSpoof filter but can otherwise be processed, go ahead and rename the user, and be sure to use this templated message in your "Done" summary.
- Usage
The template takes at least two mandatory parameters. The num
parameter indicates the number of usernames that collide with the target username. For example, if the AntiSpoof filter returns "Foo Bar" and "FooBar" as similar usernames, the num
parameter should be 2.
In most circumstances, only one username collides with the target username, so the num
parameter will usually be 1.
Only use integers! Please do not use written form, as the template will not recognize it!
The next parameters are simple numerical integers. They should be given the usernames that collide with the target username in question. Input only the username, without the "User:" prefix, and no links. The template will produce links to Special:CentralAuth automatically.
For example, "Foo Bar" and "FooBar" will be added to the parameters 1
and 2
, respectively. It doesn't really matter what order they're in, as the ordering only affects which usernames are mentioned first in the output.
Up to 7 usernames are supported by this template. If there are more than that (and I'm pretty sure there won't be), again, input the amount of clashing usernames in num
. Then, instead of using the regular parameters, use additional
. Said parameter will not automatically generate links to Special:CentralAuth, although it can handle an unlimited number of usernames. Thus, you will need to manually add links to Special:CentralAuth in additional
(on an upside, it means that any sort of wikimarkup can go in the parameter, since it won't look weird when rendered inside a link, but I see no reason why you'd do that).
This template must be substituted!
- Examples
- Fancy boxes not included.
1. If "Foo" was the only clashing username:
{{subst:User:K6ka/Similar username notice|num=1|Foo}}
Which produces:
2. If "Foo" and "Foo Bar" were clashing usernames:
{{subst:User:K6ka/Similar username notice|num=2|Foo|Foo Bar}}
Which produces:
3. If "Foo", "Foo Bar", and "Foo Foo" were clashing usernames:
{{subst:User:K6ka/Similar username notice|num=3|Foo|Foo Bar|Foo Foo}}
Which produces:
4. If "Example", "Example2", "Example3", "Example4", "Example5", "Example6", "Example7", and "Example8" were clashing usernames:
{{subst:User:K6ka/Similar username notice|num=8|additional=[[Special:CentralAuth/Example|Example]], [[Special:CentralAuth/Example2|Example2]], [[Special:CentralAuth/Example3|Example3]], [[Special:CentralAuth/Example4|Example4]], [[Special:CentralAuth/Example5|Example5]], [[Special:CentralAuth/Example6|Example6]], [[Special:CentralAuth/Example7|Example7]], and [[Special:CentralAuth/Example8|Example8]]}}
Which produces: