351:
shouldn't ban an account for purely being similar to another account. You can monitor edits, ban if something illegal shows up, but seriously, this "pre-emptive strike" is just nonsense. Hypothetically speaking, even if the same person behind this account was behind the other extremely similar account, shouldn't the clean, markless record hold weight against fears of evil to come? Isn't rehabilitating and accepting a former vandal more important than preventing a possible re-occurrence? Why should such a person be continually punished for past misdeeds, instead of being re-accepted? These people deserve good faith, not bans. A warning? Totally in order once an offense has occurred. A ban? totally in order if account has multiple offenses through conducted by its editors. However, why allow these people to re-edit once their bans wear off if the turn around, create a similar account, and work? I have read the Its The Cookie
Monster's page, talk page history and contributions. The only issue is the possible violation of what wikipedia is not (a social networking site). This is more than deserving of a slap on the wrist, and a warning. The BACON EXPLOSION account also shows no wrong, and I am not sure why that account was banned either! The log says "abusing multiple accounts". Neither the BACON EXPLOSION page or the Its the Cookie monster show or have shown any evidence of this. But saying that they did, why would that matter? Why have limited block times (eg. 6 months) for IP's creation of accounts if its illegal to have an account if you have been a vandal at any time? By this system, it would be impossible to overturn a new leaf. Therefore, the block of BACON EXPLOSION makes no sense, the block of Its the Cookie Monster makes no sense, and finally, my proposed block makes no sense by extension. Thank you for allowing my to support my own case.
413:
433:
350:
Why would such a thing be relevant? So what if another account is extremely similar, this account is still as clean and pure as a dove. No vandalization, or anything else that would warrant a ban or a block. Just as you can't throw the Son of a criminal in Jail for being related to a felon, you
177:
367:
170:
197:
216:
21:
363:
158:
340:
240:
443:
359:
297:
66:
59:
129:
322:
275:
17:
291:
105:
314:
267:
423:
400:
371:
326:
86:
287:
47:
153:
355:
318:
271:
420:
307:
260:
392:
User is advised to request unblock under the original account if he's looking for a new start.
398:
412:
302:
255:
286:
the username combined, I'm just about 100% sure that TSCotCM is one and the same as
432:
393:
42:
234:
227:
223:
210:
203:
190:
184:
164:
123:
116:
112:
99:
92:
79:
73:
53:
387:Clerk, patrolling admin and checkuser comments
300:) which is in turn a sock of BACON EXPLOSION.
8:
140:Report date September 30 2009, 02:22 (UTC)
360:The Second Coming of The Cookie Monster
154:The Second Coming of The Cookie Monster
7:
18:Knowledge:Sockpuppet investigations
28:
341:Defending yourself against claims
431:
411:
335:Comments by accused parties
424:17:36, 30 September 2009 (UTC)
372:03:05, 30 September 2009 (UTC)
327:02:22, 30 September 2009 (UTC)
1:
438:This case has been marked as
401:15:44, 1 October 2009 (UTC)
464:
379:Comments by other users
288:Its the Cookie Monster
253:Evidence submitted by
282:Given both the edits
146:Suspected sockpuppets
419:Blocked and tagged.
417:Administrator note
396:
450:
449:
394:
375:
358:comment added by
346:
455:
435:
428:
427:
415:
374:
352:
345:
336:
310:
305:
263:
258:
245:
243:
206:
180:
178:deleted contribs
156:
134:
132:
95:
69:
67:deleted contribs
45:
463:
462:
458:
457:
456:
454:
453:
452:
446:automatically.
353:
337:
308:
303:
261:
256:
219:
193:
173:
152:
151:
143:
141:
108:
82:
62:
43:BACON EXPLOSION
41:
40:
37:
35:BACON EXPLOSION
26:
25:
24:
22:BACON EXPLOSION
12:
11:
5:
461:
459:
451:
448:
447:
442:. It has been
436:
409:
408:
404:
403:
389:
388:
383:
381:
380:
348:
347:
331:
280:
279:
249:
247:
246:
148:
147:
142:
139:
137:
136:
135:
36:
33:
31:
30:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
460:
445:
441:
437:
434:
430:
429:
426:
425:
422:
418:
414:
406:
405:
402:
399:
397:
391:
390:
386:
385:
384:
378:
377:
376:
373:
369:
365:
361:
357:
344:
342:
334:
333:
332:
329:
328:
324:
320:
316:
312:
311:
306:
299:
296:
293:
289:
285:
277:
273:
269:
265:
264:
259:
252:
251:
250:
242:
239:
236:
233:
229:
225:
222:
218:
215:
212:
209:
205:
202:
199:
196:
192:
189:
186:
183:
179:
176:
172:
169:
166:
163:
160:
155:
150:
149:
145:
144:
138:
131:
128:
125:
122:
118:
114:
111:
107:
104:
101:
98:
94:
91:
88:
85:
81:
78:
75:
72:
68:
65:
61:
58:
55:
52:
49:
44:
39:
38:
34:
32:
23:
19:
439:
416:
410:
382:
349:
338:
330:
301:
294:
283:
281:
254:
248:
237:
231:
220:
213:
207:
200:
194:
187:
181:
174:
167:
161:
126:
120:
109:
102:
96:
89:
83:
76:
70:
63:
56:
50:
29:
407:Conclusions
354:—Preceding
235:investigate
124:investigate
198:block user
191:filter log
87:block user
80:filter log
224:CheckUser
211:block log
204:spi block
113:CheckUser
100:block log
93:spi block
444:archived
421:MuZemike
368:contribs
356:unsigned
315:contribs
298:contribs
268:contribs
171:contribs
60:contribs
20: |
440:closed
395:Nathan
323:review
276:review
241:cuwiki
130:cuwiki
304:Dylan
257:Dylan
16:<
364:talk
339:See
319:logs
292:talk
272:logs
185:logs
159:talk
74:logs
48:talk
309:620
284:and
262:620
228:log
165:tag
117:log
54:tag
370:)
366:•
325:)
321:,
317:,
274:,
270:,
230:)
217:CA
119:)
106:CA
362:(
343:.
313:(
295:·
290:(
278:)
266:(
244:)
238:·
232:·
226:(
221:·
214:·
208:·
201:·
195:·
188:·
182:·
175:·
168:·
162:·
157:(
133:)
127:·
121:·
115:(
110:·
103:·
97:·
90:·
84:·
77:·
71:·
64:·
57:·
51:·
46:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.