31:
270:. If the user can demonstrate that the target account belongs to them (usually by confirming the request while signed in as that account) usurpation requests can be performed immediately regardless of the presence of edits by the target account. This also covers situations where the requester creates the account they wish to be renamed to, erroneously believing this necessary to the rename process.
123:. If a user wishes to stop using a personally identifying username (e.g. their real name or a name connected to it) this request should usually be performed. It should be noted, though, that the rename log will contain a permanent record of the name and that total privacy is only possible by creating a new account. See also
315:. If the target username has good faith edits which were not immediately reverted, and the account owner has not explicitly consented to the rename, then usurping is generally not approved except to resolve SUL conflicts, when this may be done as a matter of discretion.
276:. If the target account consents to the usurpation, the request can be performed immediately regardless of the presence of edits attributed to the target account. This should only be done if confusion will not result (the target account should not be a well-known user).
327:. To ensure that good use is made of popular usernames, usurpation is reserved for established users. It is expected that an account requesting usurpation will have existed for several months and made non-trivial contributions to the encyclopedia.
190:. Changing usernames puts a lot of strain on the server, causing watchlist lag and even possibly causing a database lockdown. If there's no evidence that a user will stick with the new username, performing the rename is probably not a good idea.
206:. When there are many editors opposing the rename (for good reason), it is apparently a controversial issue. It would probably be better to gain consensus for it first at the appropriate venues (by discussing changes to the username policy on
133:. It is generally helpful if users are known by the same name across Wikimedia projects with a single user login (SUL). With single login implemented, renames and usurpation are the best way to achieve this.
196:. If the request is so confusing that the person requesting it may not be aware of the consequences, or has listed several different and confusing requests, asking them directly what they would prefer
161:
104:
139:. If a user would simply prefer another username, and there is no common sense reason (or reason listed below) to decline the request, renaming is typically appropriate.
280:
249:
321:. If the target username was created recently, usurpation is probably premature. It is expected that the target username will have existed for at least 6 months.
357:
264:
are now reallocated during renaming. As such the presence of deleted contributions by the target account is not, in most cases, a bar to usurpation.
54:
309:. Forced usurpations are not performed. If the target account registers an opposition to usurpation, the request will not be performed.
174:
rulings, renaming might cause confusion. Generally, approval should be sought from ArbCom before renames are performed in these cases.
218:
372:
38:
342:
220:
93:
347:
352:
89:
96:. Renames are a matter of discretion and renamers may depart from the guidelines where there is good reason to do so.
99:
211:
171:
207:
157:
spaces or capitalisation changes to an existing username. These may be performed even for brand new users.
337:
17:
46:
181:
150:
114:
85:
146:
184:
to the extent where their new username would be blockable, the rename will not be performed.
8:
124:
71:
63:
50:
366:
300:
290:
297:
Target account has made significant edits to another project
331:
287:
Target account's primary wiki is not the
English Knowledge
49:
may apply. Substantive edits to this page should reflect
358:
Knowledge:On privacy, confidentiality and discretion
162:When changing usernames is probably inappropriate
364:
325:Account requesting usurpation is not established
256:Target account has no (or no significant) edits
105:When changing usernames is probably appropriate
226:As a pre-note, remember, for usurpations, if
178:New username is a username policy violation
145:. The software prohibits users who are not
113:. Where a user's present name violates the
84:This page consists of guidelines as to how
45:Editors should generally follow it, though
268:Both accounts are owned by the same person
200:renaming them is a good course of action.
37:This page documents an English Knowledge
343:Knowledge:Changing username/Usurpations
299:. Such a request should be referred to
289:. Such a request should be referred to
281:When usurping is probably inappropriate
170:. If a user is currently restricted by
94:Knowledge:Changing username/Usurpations
14:
365:
348:Knowledge:Changing username/Assistance
180:. If the target username violates the
117:, renames should usually be performed.
250:When usurping is probably appropriate
307:Target account objects to usurpation
100:Guidelines applicable to all renames
25:
353:m:Steward requests/Username changes
23:
188:Too many previous username changes
111:Present name is a policy violation
90:Knowledge:Changing username/Simple
53:. When in doubt, discuss first on
24:
384:
153:from creating usernames that add
29:
373:Knowledge behavioral guidelines
13:
1:
242:" to vacate the abc name for
234:, it is necessary to rename "
7:
338:Knowledge:Changing username
18:Knowledge:Changing username
10:
389:
319:Target username is too new
303:for a Steward to consider.
293:for a Steward to consider.
219:Additional guidelines for
61:
55:this guideline's talk page
313:Target username has edits
131:Eliminating SUL conflicts
274:Target username consents
210:, bringing it up at the
168:Arbitration restrictions
204:Controversial renames
172:Arbitration Committee
88:approach requests at
39:behavioral guideline
221:usurpation requests
137:Personal preference
240:User:abc (usurped)
194:Confusing requests
125:m:Right to vanish
82:
81:
380:
151:account creators
74:
33:
32:
26:
388:
387:
383:
382:
381:
379:
378:
377:
363:
362:
334:
283:
258:to any project.
252:
224:
182:username policy
164:
143:Trivial renames
121:Privacy reasons
115:username policy
107:
102:
86:global renamers
78:
77:
70:
66:
58:
30:
22:
21:
20:
12:
11:
5:
386:
376:
375:
361:
360:
355:
350:
345:
340:
333:
330:
329:
328:
322:
316:
310:
304:
294:
282:
279:
278:
277:
271:
265:
259:
251:
248:
223:
217:
216:
215:
201:
191:
185:
175:
163:
160:
159:
158:
147:administrators
140:
134:
128:
118:
106:
103:
101:
98:
80:
79:
76:
75:
67:
62:
59:
44:
43:
34:
15:
9:
6:
4:
3:
2:
385:
374:
371:
370:
368:
359:
356:
354:
351:
349:
346:
344:
341:
339:
336:
335:
326:
323:
320:
317:
314:
311:
308:
305:
302:
298:
295:
292:
288:
285:
284:
275:
272:
269:
266:
263:
262:Deleted edits
260:
257:
254:
253:
247:
245:
241:
237:
233:
229:
222:
213:
209:
208:its talk page
205:
202:
199:
195:
192:
189:
186:
183:
179:
176:
173:
169:
166:
165:
156:
152:
148:
144:
141:
138:
135:
132:
129:
126:
122:
119:
116:
112:
109:
108:
97:
95:
91:
87:
73:
69:
68:
65:
60:
56:
52:
48:
42:
40:
35:
28:
27:
19:
324:
318:
312:
306:
296:
286:
273:
267:
261:
255:
243:
239:
235:
231:
230:is usurping
227:
225:
212:village pump
203:
197:
193:
187:
177:
167:
154:
142:
136:
130:
120:
110:
83:
36:
47:exceptions
51:consensus
367:Category
332:See also
236:User:abc
232:User:abc
228:User:xyz
214:, etc.).
64:Shortcut
92:and at
72:WP:CHUG
301:m:SRUC
291:m:SRUC
238:" to "
198:before
16:<
155:only
244:xyz
149:or
369::
246:.
127:.
57:.
41:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.