254:
username that is not being actively used to be usurped if the target user is given an opportunity to object and does not do so. If you object to being usurped, please log in to your account and make an edit on your user talk page (https://en.wikipedia.org/User_talk:TARGET_USERNAME) stating that you object to usurpation. Any objection on your part will prevent usurpation. If you do not object to usurpation, you may log in to your account and make an edit on your user talk page stating that you approve the usurpation request. If you would like to be renamed to a different username, you may file a username change request at (https://en.wikipedia.org/Special:GlobalRenameRequest). If you do not respond, the request may be fulfilled no sooner than ONHOLD_DATE. Your account will be renamed to a generic username—"TARGET_USERNAME (usurped)". No edits or data will be lost, and you will still be able to log in and edit under your new username. Thank you for your time. Best regards, YOUR_USERNAME
253:
Hello TARGET_USERNAME, I am sending you this email to inform you that another user would like to usurp, or "take over", your username on
Knowledge, because they would like to use it to edit. The changing username guideline (https://en.wikipedia.org/Wikipedia:Changing_username/Guidelines) allows a
126:
Check whether or not the requested account has edits or log entries (with the exception of user creation). If there are edits, add {{CUU|contribs=yes}}. If there are logs, {{CUU|logs=yes}}. Occasionally, global renamers have made concessions when the edits are very few and only to userspace; make
71:
These tasks require a modicum of trust. If a global renamer must double-check an editor's statements, that editor's assistance is not useful. Errors resulting from carelessness or misunderstanding of policy are often easily corrected, but are nevertheless frustrating because the demands of the
59:
processes are complicated and tedious; accordingly, several editors have agreed to do some of the requisite footwork to keep the processes organized and efficient. Those offering assistance should familiarize themselves with
72:
position are few. No such issues, or any of deliberate misconduct, have yet arisen; should one occur, a global renamer will probably ask that the editor discontinue their contributions to these pages.
216:
When commenting, remember to make all relevant notes at once, and avoid useless conversation. A global renamer has commented that these clutter up the page, and are detrimental.
140:
Check the blocklog of the requesting editor. If there are recent or a significant number of blocks, make note of them. This also applies to
Arbitration Committee sanctions.
182:
Administrators — check for deleted edits by the requested name. If they do not exist, modify the template to read {{CUU|dcontribs=no}}, if they do, {{CUU|dcontribs=yes}}.
127:
note of these. Also note that requests to usurp an account that have edits on other projects, or do not have a local account on the
English Knowledge, must be made at
105:
If the requesting editor wishes to make the first letter lowercase, make note that the MediaWiki software automatically capitalizes the first letter: {{CHU|autocap}}.
250:
If the requested account in a usurpation request has enabled email, it is suggested that the following message (or similar) be sent to inform them of the request:
134:
Check the number of edits by the requesting editor. Too few edits is a bar to usurpation. There is not, however, a defined amount, but 400 edits is a safe minimum.
108:
If the request is seeking to modify underscores/spaces, make note that the software treats underscores and spaces the same: {{CHU|underscore}}.
95:. If it does, but qualifies for usurpation, add {{CHU|usurp|username}}. If the requested account does not qualify, add {{CHU|taken|username}}.
153:
Ensure that the request is placed under the correct date heading; the correct date is determined by when the target account was notified,
242:
who comment on these pages do not have the authority to accept or decline requests. This authority lies only with a global renamer.
119:
56:
128:
61:
84:
203:
Make note if the rename to take place was requested by the editor in question. If not, add {{CHU|notused|username}}.
210:
144:
176:
52:
17:
137:
Check the creation date of the requested username; if it is newer than six months, add {{CUU|new=yes}}.
266:
99:
65:
219:
Notify users when a comment is made on the page for them. You may use the "Ping user" link, or the
102:, if not: {{CHU|inappropriate}} or, for promotional requests specifically: {{CHU|promotional}}.
143:
Check the talk page of the requested username for a notice. If there is not one there, add {{
8:
193:
92:
35:
239:
42:
27:
150:
Check the e-mail of the requested username. If it exists, send the e-mail shown below.
197:
260:
223:
83:
118:
80:
Please note that many of these tasks are automatically done by bots.
186:
111:
Only add notes on requests when something mentioned above occurs.
157:
when the request was placed. The correct date header format is
233:
147:}}. Consider making note of for whom the request was made.
168:''Requests left here will be filled no earlier than .''
175:
If the requested username does not exist, move it to
98:
Ensure that the requested username complies with the
91:
Check to see if the requested username exists, using
245:
75:
209:In addition, please watchlist the talk page here (
68:look at when deciding whether to grant requests.
113:Notes are not needed on fully compliant requests.
258:
213:) to be notified of policy and process changes.
200:}}. Severely malformed requests may be removed.
206:Move new requests to the bottom of the page.
14:
259:
129:meta:Steward requests/Username changes
192:Fix malformed requests to fit with {{
23:
24:
278:
211:Knowledge talk:Changing username
64:as a decent idea of the factors
179:and format with that template.
13:
1:
62:Changing usernames guidelines
7:
18:Knowledge:Changing username
10:
283:
145:subst:usurpation requested
25:
229:template to do this.
164:== Month Day, Year==
93:Special:CentralAuth
238:Users who are not
274:
267:Knowledge clerks
228:
222:
194:subst:Renameuser
45:
38:
282:
281:
277:
276:
275:
273:
272:
271:
257:
256:
255:
248:
240:global renamers
236:
226:
220:
189:
123:
100:username policy
88:
78:
66:global renamers
53:username change
49:
48:
41:
34:
30:
22:
21:
20:
12:
11:
5:
280:
270:
269:
252:
247:
244:
235:
232:
231:
230:
217:
214:
207:
204:
201:
188:
185:
184:
183:
180:
172:
171:
170:
169:
166:
165:
159:
158:
151:
148:
141:
138:
135:
132:
122:
117:
116:
115:
109:
106:
103:
96:
87:
85:Normal renames
82:
77:
74:
47:
46:
39:
31:
26:
15:
9:
6:
4:
3:
2:
279:
268:
265:
264:
262:
251:
243:
241:
225:
218:
215:
212:
208:
205:
202:
199:
195:
191:
190:
181:
178:
174:
173:
167:
163:
162:
161:
160:
156:
152:
149:
146:
142:
139:
136:
133:
130:
125:
124:
121:
114:
110:
107:
104:
101:
97:
94:
90:
89:
86:
81:
73:
69:
67:
63:
58:
54:
44:
40:
37:
33:
32:
29:
19:
249:
237:
154:
112:
79:
70:
50:
198:subst:usurp
120:Usurpations
187:Both pages
57:usurpation
234:Authority
28:Shortcuts
261:Category
196:}} or {{
36:WP:CHU/A
43:WP:CHUA
177:WP:CHU
246:Email
76:Tasks
16:<
224:ping
55:and
51:The
155:not
263::
227:}}
221:{{
131:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.