338:
encyclopedia, not enforce the rules for their own sake. Not once have you even articulated what actual damage I'm doing to that mission with these socks, unless you're just going to repeat Black Kite's garbage that the truth or importance of accusations like this change depending on who is making them (a view which is as stupid as saying the result of 2+2 depends on the colour of chalk used). And remember, lest you haven't been paying attention too closely, Black Kite has an excuse for acting that way. That doesn't mean you have to be so gullible. So, unless you want to make the quite extraordinary claim that it wouldn't be an improvement to
Knowledge (XXG) to have an open and transparent investigation into whether or not the notoriously disruptive user Betacommand is, at this very minute, editing articles as the user Werieth, in defiance of a community ban, that was arrived at after many thousands of man hours of drama and diverted editor attention and no less than three arbitration cases (and, with all irony, a multitude of confirmed socks used to ..... evade blocks!), then you had better believe that only thing you need to concern yourself with how I raise my concerns, is what you can do to help me. I don't trust any Wikipedians, and I don't wish any of them to know my email (nor do I expect to have to take the time to create email accounts just to be able to raise serious concerns like this). So, I choose the most convenient way for me. It's up to you if you choose to put the rules, or inconveniencing me, or any other bullshit reason, above the primary goal here. So get with the program already - the rules won't matter in the end. When this gets written up in a blog at a certain site that likes nothing better than to criticise the more dysfunctional aspects of Knowledge (XXG), just like this nonsense, then your excuses and pleas as to why you failed to do the right thing really won't matter. In that narrative, the one you cannot control with blocks, you will be painted as either part of the solution, or part of the problem. If you want to know what it feels like to be in the latter group, well, I'm sure you already know of a few people you could ask.
256:
repeated efforts to reform him, the community eventually decided he should be banned. He is ignoring the community. As he always did. Black Kite disagreed with that outcome to the end. The only thing I've done with any of these socks, is point out the many similarities between the two accounts. Same interests. Same behaviour. Same experience. Same views. Same approach to DR. Same approach to critics. Same goddam everything, which is why nobody, not one person, is even bothering to highlight any hole in the case. Werieth wants me to shut up. Black Kite wants me to shut up. Kww, another NFCC hardliner, even blocked me to shut me up. What does it take for you to figure it out? Seriously, you need to sort your act out here, otherwise the next time you here about this probably will be in a
Wikipediocracy blog. Don't for a second think that Wereith/Betacommand will care if the ensuing controversy/embarrassment ends your Knowledge (XXG) career. Any of you. Including you Black Kite (although I know his ego won't allow him to even entertain the thought that he could be out-manouvred by a half-wit like Beta). He is interested in one thing, and one thing only, his continued ability to edit Knowledge (XXG). And thanks to you, he's getting his fix. The only problem is, other people, and more importantly the quality of the encyclopedia, is suffering (wherever you stand on NFC, the net negative to the project's quality of Betacommand's buggy/error-ridden/not my problem/my way or the highway approach to editing was recognised by most editors in the end, even those who opposed bans to the end). Admins are actually supposed to care about that sort of thing, and more importantly, act to stop it. That's what I was led to expect, anyway. Maybe people like
454:). He is only attacking me (and now you) to deflect attention from the fact that he knew Betacommand's history better than anyone, and is therefore in the best position of any responding admin to quickly put to bed the accusation that Betacommand has returned as Werieth. If there was a single hole in the case, he would have spotted it already, exploiting it to maximum effect to make this whole issue go away as fast as possible, and let his old pal Beta get on with his good work of being his useful idiot. But there are no holes, sadly for him. That's why all he's interested in is 'shooting the messengers'. Ironic, to say the least.
87:), the better. When I finally find someone in your ranks who is not stupid enough to be taken in by the fact that he uploads a few non-free book cover images whenever these suspicions are raised as the world's lamest 'cover' story (he's doing it right now FFS, right this very second straight after asking you to shut me up), I will list each and every one of you (and other assorted useful idiots who actively assist you), along with the reasons why I think they participated in this farce.
18:
487:
Hi LHvU. Editors who don't believe that they are edit-warring summarily removing an associated talk-page notice and leaving an indignant comment is commonplace. In this particular case, issuing such notice in relation to an ongoing SPI discussion served no useful purpose; denoting it as 'harassment'
135:) - I so desperately want to find the reason why this guy is 'agnostic' about the possibility one of the most disruptive and time-sinking editors has returned, but I fear it is just going to be slave to the rules type stupidity - I suspect had he been here he would have just blocked this account per
190:
of what he is doing, so he can go straight into the Floq column. Although I suppose having a black and white view of sock puppetry is probably one of the entry requirements for SPI clerking - nuanced approaches like weighing up whether catching
Betacommand evading a hard earned ban is going to be
255:
sort of bull? Black Kite is an NFCC hardliner. Betacommand made hundreds of thousands of NFCC enforcement edits. His ban evading sock account
Werieth is on his way to making hundreds of thousands of NFCC enforcement edits. After many thousands of man hours, after epic levels of discussion and
337:
You're sorry? I don't think so. You can hide behind the rules all you want, but unfortunately for mindless automatons like yourself, there's always one rule that's really going to fuck you in the ass if you don't wake up and smell the coffee once in a while - WP:IAR. You are here to build an
322:
I'm sorry, but there are ways to raise concerns about sockpuppetry and block evasion without engaging in sockpuppetry and block evasion yourself. I suggest you e-mail your findings to a
Wikipedian you trust instead of creating throwaway accounts to post on their talk page.
175:) - fuck knows. A guy who makes blocks like this in the middle of Huggle powered vandal fighting sprees is clearly not giving much thought to anything at all. He probably hasn't even got the first clue he is blocking the person who is capable of laying out the evidence he
509:
If someone else socks to complain of this though, they're a legitimate target to be blocked, talkpage-blocked, erased from history and even for other previously uninvolved editors to be threatened with instant blocks for merely discussing them on their own talk pages.
391:
imprimatur (and disclosing where they came from), after having checked these diffs. These are good and relevant diffs, appropriate to that SPI, although workload means that I (or the SPI admin) have no time to discover them for
215:
blog - they love finding out about how
Knowledge (XXG) can't really deal with complex moral situations like this, and they lap up examples of cut your nose off to spite your face crap like this.
362:: their talk page access has been blocked, the diffs have been removed from the SPI page and they have threatened to block any other editor who repeats this. It has falsely been claimed that
229:
I appreciate that you provided some diffs to back up your assertions on the SPI, but you can't keep creating a new account every time you get blocked and expect admins to look the other way.
22:
191:
worth more to
Knowledge (XXG) than just chalking up the fifty billionth DUCK block is for others to possess, if that sense is even present here at all.
267:
152:
270:) is a sign of the sort of admin that can be expected in future - who takes stupidity in matters like this to almost professional levels.
437:
172:
132:
84:
399:
is to be blocked, then I can understand why. However we only remove talk: access in exceptional circumstances. I see no reason why
370:
have been the subject of a CU linking them to a blocked editor (an editor who cannot be named). This is untrue. That CU was for a
451:
100:
455:
396:
384:
380:
363:
359:
339:
303:
271:
216:
192:
70:
289:
261:
159:? Seriously, I'm actually wondering what goes through someone's mind to think that serves any purpose whatsoever.
146:
116:
26:
478:
515:
431:
408:
257:
142:
94:
328:
234:
166:
126:
78:
49:
445:
90:
474:
44:
I've blocked you indefinitely as it appears that this account is being used for block evasion.
511:
427:
404:
64:
519:
497:
493:
482:
463:
412:
347:
332:
324:
311:
297:
279:
238:
230:
224:
200:
162:
122:
74:
53:
45:
34:
441:
302:
My mistake. It seemed to me to be the only rational explanation for doing what you did.
367:
354:
Mark, what would such a "trusted
Wikipedian" do with such an email? Future Perfect has
212:
506:
So if
Werieth is a sock, admins who share Betacommand's view on NFC will protect him.
110:
469:
Only bc/triangle would delete a correctly posted notification of a AN discussion as
60:
489:
374:
editor some time ago, with no indication to relate them to these accounts today.
73:), who has made thousands of article space edits, is in fact the banned editor
155:) - retardation? Wannabe admin? General stupidity? And seriously, wtf even is
103:) - NFCC hardliner, thus wiki-corruption of the ends justify the means sort.
25:
regarding an issue with which you may have been involved. Thank you. --
106:
59:
Good. The more admins that try and stop me from exposing the fact that
211:
I am at this point even considering writing this up whole farce for a
139:, just like the last time (if he disagrees, he can say so here).
288:
Oh god no! Why the fuck would I want to be an admin? --
470:
252:
187:
176:
156:
136:
23:
Knowledge (XXG):Administrators' noticeboard/Incidents
440:) - don't waste your time trading insults with
379:You rightly asked at the SPI page for diffs.
8:
488:is neither inappropriate nor idiosyncratic.
403:have been blocked from posting these diffs.
186:Actually, yes, sadly, apparently he is
7:
21:There is currently a discussion at
14:
251:Can I expect them to see through
16:
387:'s diffs to the SPI page under
1:
520:11:02, 17 December 2013 (UTC)
498:07:55, 17 December 2013 (UTC)
483:21:44, 16 December 2013 (UTC)
464:02:59, 13 December 2013 (UTC)
413:12:14, 13 December 2013 (UTC)
383:provided these. I re-posted
348:02:38, 13 December 2013 (UTC)
333:02:15, 13 December 2013 (UTC)
312:02:41, 13 December 2013 (UTC)
298:02:29, 13 December 2013 (UTC)
280:02:08, 13 December 2013 (UTC)
239:01:30, 13 December 2013 (UTC)
225:01:26, 13 December 2013 (UTC)
201:01:33, 13 December 2013 (UTC)
179:apparently would like to see.
54:00:52, 13 December 2013 (UTC)
35:23:48, 12 December 2013 (UTC)
538:
456:Formal Appointee Number 6
397:Formal Appointee Number 6
385:Formal Appointee Number 6
381:Formal Appointee Number 6
364:Formal Appointee Number 6
360:Formal Appointee Number 6
340:Formal Appointee Number 6
304:Formal Appointee Number 6
272:Formal Appointee Number 6
217:Formal Appointee Number 6
193:Formal Appointee Number 6
459:
343:
307:
275:
220:
196:
293:aka The Red Pen of Doom
30:aka The Red Pen of Doom
471:"remove harassment"
119:) - see BlackKite.
294:
31:
529:
295:
292:
32:
29:
20:
19:
537:
536:
532:
531:
530:
528:
527:
526:
290:
258:TheRedPenOfDoom
143:TheRedPenOfDoom
42:
27:
17:
12:
11:
5:
535:
533:
525:
524:
523:
522:
507:
501:
500:
485:
475:LessHeard vanU
424:
423:
422:
421:
420:
419:
418:
417:
416:
415:
393:
376:
375:
351:
350:
320:
319:
318:
317:
316:
315:
314:
244:
243:
242:
241:
213:Wikipediocracy
208:
207:
206:
205:
204:
203:
181:
180:
160:
140:
120:
104:
41:
38:
13:
10:
9:
6:
4:
3:
2:
534:
521:
517:
513:
508:
505:
504:
503:
502:
499:
495:
491:
486:
484:
480:
476:
472:
468:
467:
466:
465:
461:
457:
453:
450:
447:
443:
439:
436:
433:
429:
414:
410:
406:
402:
398:
394:
390:
386:
382:
378:
377:
373:
369:
365:
361:
357:
353:
352:
349:
345:
341:
336:
335:
334:
330:
326:
321:
313:
309:
305:
301:
300:
299:
296:
287:
286:
285:
284:
283:
282:
281:
277:
273:
269:
266:
263:
259:
254:
250:
249:
248:
247:
246:
245:
240:
236:
232:
228:
227:
226:
222:
218:
214:
210:
209:
202:
198:
194:
189:
185:
184:
183:
182:
178:
174:
171:
168:
164:
161:
158:
154:
151:
148:
144:
141:
138:
134:
131:
128:
124:
121:
118:
115:
112:
108:
105:
102:
99:
96:
92:
89:
88:
86:
83:
80:
76:
72:
69:
66:
62:
58:
57:
56:
55:
51:
47:
39:
37:
36:
33:
24:
512:Andy Dingley
448:
434:
428:Andy Dingley
425:
405:Andy Dingley
400:
388:
371:
355:
264:
169:
149:
137:this request
129:
113:
97:
81:
67:
43:
15:
325:Mark Arsten
231:Mark Arsten
163:Mark Arsten
123:Floquenbeam
75:Betacommand
46:Mark Arsten
442:Black Kite
188:well aware
372:different
368:Arnhem 96
91:BlackKite
452:contribs
438:contribs
356:de facto
268:contribs
173:contribs
153:contribs
133:contribs
117:contribs
101:contribs
85:contribs
71:contribs
392:myself.
358:banned
177:himself
61:Werieth
40:Blocked
490:Aquegg
291:TRPoD
28:TRPoD
516:talk
494:talk
479:talk
460:talk
446:talk
432:talk
409:talk
395:If
366:and
344:talk
329:talk
308:talk
276:talk
262:talk
253:this
235:talk
221:talk
197:talk
167:talk
157:this
147:talk
127:talk
111:talk
95:talk
79:talk
65:talk
50:talk
107:Kww
518:)
496:)
481:)
473:.
462:)
411:)
389:my
346:)
331:)
310:)
278:)
237:)
223:)
199:)
52:)
514:(
492:(
477:(
458:(
449:·
444:(
435:·
430:(
426:@
407:(
401:I
342:(
327:(
306:(
274:(
265:·
260:(
233:(
219:(
195:(
170:·
165:(
150:·
145:(
130:·
125:(
114:·
109:(
98:·
93:(
82:·
77:(
68:·
63:(
48:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.