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