Wikipedia:Administrators' noticeboard/Archive146

Source: Wikipedia, the free encyclopedia.
Noticeboard archives
Administrators' (archives, search)
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60
61 62 63 64 65 66 67 68 69 70
71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
101 102 103 104 105 106 107 108 109 110
111 112 113 114 115 116 117 118 119 120
121 122 123 124 125 126 127 128 129 130
131 132 133 134 135 136 137 138 139 140
141 142 143 144 145 146 147 148 149 150
151 152 153 154 155 156 157 158 159 160
161 162 163 164 165 166 167 168 169 170
171 172 173 174 175 176 177 178 179 180
181 182 183 184 185 186 187 188 189 190
191 192 193 194 195 196 197 198 199 200
201 202 203 204 205 206 207 208 209 210
211 212 213 214 215 216 217 218 219 220
221 222 223 224 225 226 227 228 229 230
231 232 233 234 235 236 237 238 239 240
241 242 243 244 245 246 247 248 249 250
251 252 253 254 255 256 257 258 259 260
261 262 263 264 265 266 267 268 269 270
271 272 273 274 275 276 277 278 279 280
281 282 283 284 285 286 287 288 289 290
291 292 293 294 295 296 297 298 299 300
301 302 303 304 305 306 307 308 309 310
311 312 313 314 315 316 317 318 319 320
321 322 323 324 325 326 327 328 329 330
331 332 333 334 335 336 337 338 339 340
341 342 343 344 345 346 347 348 349 350
351 352 353 354 355 356 357 358 359 360
361 362
Incidents (archives, search)
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60
61 62 63 64 65 66 67 68 69 70
71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
101 102 103 104 105 106 107 108 109 110
111 112 113 114 115 116 117 118 119 120
121 122 123 124 125 126 127 128 129 130
131 132 133 134 135 136 137 138 139 140
141 142 143 144 145 146 147 148 149 150
151 152 153 154 155 156 157 158 159 160
161 162 163 164 165 166 167 168 169 170
171 172 173 174 175 176 177 178 179 180
181 182 183 184 185 186 187 188 189 190
191 192 193 194 195 196 197 198 199 200
201 202 203 204 205 206 207 208 209 210
211 212 213 214 215 216 217 218 219 220
221 222 223 224 225 226 227 228 229 230
231 232 233 234 235 236 237 238 239 240
241 242 243 244 245 246 247 248 249 250
251 252 253 254 255 256 257 258 259 260
261 262 263 264 265 266 267 268 269 270
271 272 273 274 275 276 277 278 279 280
281 282 283 284 285 286 287 288 289 290
291 292 293 294 295 296 297 298 299 300
301 302 303 304 305 306 307 308 309 310
311 312 313 314 315 316 317 318 319 320
321 322 323 324 325 326 327 328 329 330
331 332 333 334 335 336 337 338 339 340
341 342 343 344 345 346 347 348 349 350
351 352 353 354 355 356 357 358 359 360
361 362 363 364 365 366 367 368 369 370
371 372 373 374 375 376 377 378 379 380
381 382 383 384 385 386 387 388 389 390
391 392 393 394 395 396 397 398 399 400
401 402 403 404 405 406 407 408 409 410
411 412 413 414 415 416 417 418 419 420
421 422 423 424 425 426 427 428 429 430
431 432 433 434 435 436 437 438 439 440
441 442 443 444 445 446 447 448 449 450
451 452 453 454 455 456 457 458 459 460
461 462 463 464 465 466 467 468 469 470
471 472 473 474 475 476 477 478 479 480
481 482 483 484 485 486 487 488 489 490
491 492 493 494 495 496 497 498 499 500
501 502 503 504 505 506 507 508 509 510
511 512 513 514 515 516 517 518 519 520
521 522 523 524 525 526 527 528 529 530
531 532 533 534 535 536 537 538 539 540
541 542 543 544 545 546 547 548 549 550
551 552 553 554 555 556 557 558 559 560
561 562 563 564 565 566 567 568 569 570
571 572 573 574 575 576 577 578 579 580
581 582 583 584 585 586 587 588 589 590
591 592 593 594 595 596 597 598 599 600
601 602 603 604 605 606 607 608 609 610
611 612 613 614 615 616 617 618 619 620
621 622 623 624 625 626 627 628 629 630
631 632 633 634 635 636 637 638 639 640
641 642 643 644 645 646 647 648 649 650
651 652 653 654 655 656 657 658 659 660
661 662 663 664 665 666 667 668 669 670
671 672 673 674 675 676 677 678 679 680
681 682 683 684 685 686 687 688 689 690
691 692 693 694 695 696 697 698 699 700
701 702 703 704 705 706 707 708 709 710
711 712 713 714 715 716 717 718 719 720
721 722 723 724 725 726 727 728 729 730
731 732 733 734 735 736 737 738 739 740
741 742 743 744 745 746 747 748 749 750
751 752 753 754 755 756 757 758 759 760
761 762 763 764 765 766 767 768 769 770
771 772 773 774 775 776 777 778 779 780
781 782 783 784 785 786 787 788 789 790
791 792 793 794 795 796 797 798 799 800
801 802 803 804 805 806 807 808 809 810
811 812 813 814 815 816 817 818 819 820
821 822 823 824 825 826 827 828 829 830
831 832 833 834 835 836 837 838 839 840
841 842 843 844 845 846 847 848 849 850
851 852 853 854 855 856 857 858 859 860
861 862 863 864 865 866 867 868 869 870
871 872 873 874 875 876 877 878 879 880
881 882 883 884 885 886 887 888 889 890
891 892 893 894 895 896 897 898 899 900
901 902 903 904 905 906 907 908 909 910
911 912 913 914 915 916 917 918 919 920
921 922 923 924 925 926 927 928 929 930
931 932 933 934 935 936 937 938 939 940
941 942 943 944 945 946 947 948 949 950
951 952 953 954 955 956 957 958 959 960
961 962 963 964 965 966 967 968 969 970
971 972 973 974 975 976 977 978 979 980
981 982 983 984 985 986 987 988 989 990
991 992 993 994 995 996 997 998 999 1000
1001 1002 1003 1004 1005 1006 1007 1008 1009 1010
1011 1012 1013 1014 1015 1016 1017 1018 1019 1020
1021 1022 1023 1024 1025 1026 1027 1028 1029 1030
1031 1032 1033 1034 1035 1036 1037 1038 1039 1040
1041 1042 1043 1044 1045 1046 1047 1048 1049 1050
1051 1052 1053 1054 1055 1056 1057 1058 1059 1060
1061 1062 1063 1064 1065 1066 1067 1068 1069 1070
1071 1072 1073 1074 1075 1076 1077 1078 1079 1080
1081 1082 1083 1084 1085 1086 1087 1088 1089 1090
1091 1092 1093 1094 1095 1096 1097 1098 1099 1100
1101 1102 1103 1104 1105 1106 1107 1108 1109 1110
1111 1112 1113 1114 1115 1116 1117 1118 1119 1120
1121 1122 1123 1124 1125 1126 1127 1128 1129 1130
1131 1132 1133 1134 1135 1136 1137 1138 1139 1140
1141 1142 1143 1144 1145 1146 1147 1148 1149 1150
1151 1152 1153 1154 1155 1156 1157 1158
Edit-warring/3RR (archives, search)
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60
61 62 63 64 65 66 67 68 69 70
71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
101 102 103 104 105 106 107 108 109 110
111 112 113 114 115 116 117 118 119 120
121 122 123 124 125 126 127 128 129 130
131 132 133 134 135 136 137 138 139 140
141 142 143 144 145 146 147 148 149 150
151 152 153 154 155 156 157 158 159 160
161 162 163 164 165 166 167 168 169 170
171 172 173 174 175 176 177 178 179 180
181 182 183 184 185 186 187 188 189 190
191 192 193 194 195 196 197 198 199 200
201 202 203 204 205 206 207 208 209 210
211 212 213 214 215 216 217 218 219 220
221 222 223 224 225 226 227 228 229 230
231 232 233 234 235 236 237 238 239 240
241 242 243 244 245 246 247 248 249 250
251 252 253 254 255 256 257 258 259 260
261 262 263 264 265 266 267 268 269 270
271 272 273 274 275 276 277 278 279 280
281 282 283 284 285 286 287 288 289 290
291 292 293 294 295 296 297 298 299 300
301 302 303 304 305 306 307 308 309 310
311 312 313 314 315 316 317 318 319 320
321 322 323 324 325 326 327 328 329 330
331 332 333 334 335 336 337 338 339 340
341 342 343 344 345 346 347 348 349 350
351 352 353 354 355 356 357 358 359 360
361 362 363 364 365 366 367 368 369 370
371 372 373 374 375 376 377 378 379 380
381 382 383 384 385 386 387 388 389 390
391 392 393 394 395 396 397 398 399 400
401 402 403 404 405 406 407 408 409 410
411 412 413 414 415 416 417 418 419 420
421 422 423 424 425 426 427 428 429 430
431 432 433 434 435 436 437 438 439 440
441 442 443 444 445 446 447 448 449 450
451 452 453 454 455 456 457 458 459 460
461 462 463 464 465 466 467 468 469 470
471 472 473 474 475 476 477 478 479 480
481 482 483 484
Arbitration enforcement (archives)
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60
61 62 63 64 65 66 67 68 69 70
71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
101 102 103 104 105 106 107 108 109 110
111 112 113 114 115 116 117 118 119 120
121 122 123 124 125 126 127 128 129 130
131 132 133 134 135 136 137 138 139 140
141 142 143 144 145 146 147 148 149 150
151 152 153 154 155 156 157 158 159 160
161 162 163 164 165 166 167 168 169 170
171 172 173 174 175 176 177 178 179 180
181 182 183 184 185 186 187 188 189 190
191 192 193 194 195 196 197 198 199 200
201 202 203 204 205 206 207 208 209 210
211 212 213 214 215 216 217 218 219 220
221 222 223 224 225 226 227 228 229 230
231 232 233 234 235 236 237 238 239 240
241 242 243 244 245 246 247 248 249 250
251 252 253 254 255 256 257 258 259 260
261 262 263 264 265 266 267 268 269 270
271 272 273 274 275 276 277 278 279 280
281 282 283 284 285 286 287 288 289 290
291 292 293 294 295 296 297 298 299 300
301 302 303 304 305 306 307 308 309 310
311 312 313 314 315 316 317 318 319 320
321 322 323 324 325 326 327 328 329 330
331 332 333 334
Other links

Rollback help needed

I recently indef'd yet another sock of banned user Codyfinke (

96
19:13, 18 May 2008 (UTC)

i've looked through some of the edits yet to be rolled back, and I know that as a matter of principle, we do not allow editing by blocked users, however some of the un-rolled-back edits; I can't see where some of them aren't improvements. I endorse the block, and agree it should stay, but do we need to rollback every edit, even those that are ultimately beneficial for the encyclopedia? --Jayron32.talk.contribs 19:23, 18 May 2008 (UTC)
It's a question we've never really resolved: what do we do about good edits by bad people? Policy and practice say we revert - they are banned and leaving their edits up hardly discourages them. But what do we do where reverting is detrimental to the article in question? One suggestion, ludicrous on first glance, was to revert and then make the edits anyway. This works, but is insane. And it is "editing by proxy for a banned user". I can't see a good answer to this conundrum, but Wikipedia has assembled some of the finest minds in the entire world when it comes to collaborative editing... so someone here should know. I hope. ➨ REDVEЯS is now 40 per cent papier mâché 21:22, 18 May 2008 (UTC)
As Redvers said, it's a tricky issue. Personally, I'd say that if an edit is unquestionably beneficial, it should be allowed to stand; we should not cut off our nose to spite our face. However, if the validity of the edit isn't obvious, it's better to err on the side of caution; if the edit was really something that should've been made, someone else will
MySpace substitute to real-life stalking of other editors, and it's important to know which kind one is dealing with. (Specific users deliberately left unnamed; grep the list if you want examples.) For instance, if the reason the user in question has been banned is repeated insertion of hoaxes and subtle misinformation, it's probably a good idea to take even seemingly valid edits from them with a big grain of salt. Similarly, while in some cases a useful solution may be to revert the edits but note them on the article's talk page, for some banned users this will just serve as a form of validation. If in doubt, try to find someone who knows the history of the particular user in question and ask them (possibly off-wiki). —Ilmari Karonen (talk
) 23:41, 18 May 2008 (UTC)
IMO, reverting an otherwise constructive edit simply because a banned user made it is illogical. Regardless of whether or not he/she was blocked, it doesn't change whether the edit was/was not constructive. J.delanoygabsadds 17:08, 19 May 2008 (UTC)
If I recall correctly, some trollish sockpuppets of banned users have deliberately performed "good" actions such as removing BLP violations, in an attempt to trap other editors who revert their edits on sight. No, I'm not going to provide specific diffs, because that's irrelevant to the point I'm trying to make. The bottom line is really pretty simple: You are responsible for your edits, including reverts and rollbacks. SHEFFIELDSTEELTALK 21:03, 19 May 2008 (UTC)

Merge history

Could an admin please history merge

talk
) 20:53, 18 May 2008 (UTC)

  • Done. You may consider editing the article itself, or copy/paste the new content you wrote (no copyright problem, I guess, as the attribution would be to you anyway) with a summary resuming the whole copyediting done. - Nabla (talk) 22:49, 18 May 2008 (UTC)
  • Thankyou. I wasn't comfortable editing the article itself as it was a complete rewrite, and I started with only one paragraph which would probably be reverted.--
    talk
    ) 19:09, 19 May 2008 (UTC)
Resolved
 – AfD already closed, admin already looked into it. -- Kesh

(talk) 21:11, 19 May 2008 (UTC)

I'd like an admin to check the talk for this AfD. I'm not sure where else to take this.

talk
) 22:33, 18 May 2008 (UTC)

There may be some sock-puppetry at work there, but the first keep vote is User:Dhartung, who is most assuredly not a sockpuppet of anyone else. I don't see a need to bring this to AN/I, so I am going to close it as no action required. Horologium (talk) 22:39, 18 May 2008 (UTC)
I wasn't suggesting that Dhartung was a sockpuppeteer. And this isn't AN/I, it's AN. I've removed the resolved template.
talk
) 22:45, 18 May 2008 (UTC)

User:Trees Rock

I've just issued a final warning to Trees Rock (

iridescent
00:28, 19 May 2008 (UTC)

That was not a "joke edit". I ment it, but I withdrew it because I was instructed. Trees RockMyGoal 00:39, 19 May 2008 (UTC)
And How is my Signature a "disruptive edit" as soon as I got that comment I changed It. Trees RockMyGoal 00:49, 19 May 2008 (UTC)
Are you really the right person to be badgering people about their signatures? John Reaves 01:02, 19 May 2008 (UTC)
At nearly 700 characters, Trees Rock's signature was a bit much. - auburnpilot talk 01:16, 19 May 2008 (UTC)
After having to deal with Trees Rock, I do not think he is purposefully being malicious; rather, his inexperience with the project shows through his glaring mistakes. I believe he is well meaning and just needs to learn the ropes, maybe visit
WP:ADOPT before doing anything else. --SharkfaceT/C
01:27, 19 May 2008 (UTC)
Again, we run into a problem where I don't think this is bad faith, but regardless, highly disruptive. If Trees Rock doesn't think the diff in the RfA page is disruptive... then what more can we say? Irid was good to come here, and I hope other admins keep Tree on watch. Another obviously disruptive edit should resort in a short-term block, in an attempt to prevent more disruptive edits without a more serious reflection by the user. Gwynand | TalkContribs 01:37, 19 May 2008 (UTC)
While I hate to be the one who brings this up, even if Trees Rock was able to become properly acquainted with Wiki-policy, inherent problems, such as maturity, could come into play. --SharkfaceT/C 01:56, 19 May 2008 (UTC)
The warning may be a bit rough. But the user is regularly in borderline violation of
WP:NOTMYSPACE, and other concerns have already been raised. In case of further disruption, a short block may be in order. Adoption and the like have shown to have little effect in cases of maturity concerns. As for the biggest signature contest, it's getting ridiculous. Cenarium (talk)
02:08, 19 May 2008 (UTC)
After reviewing this, I would agree that many of Trees Rock's edits seem very Myspacey and borderline disruptive. I support Iridescent's warnings, and would support a short block (to escalate if necessary) for continued disruption after this warning. Keeper | 76 | Disclaimer 21:26, 19 May 2008 (UTC)
According to Trees Rock's Talk page, he has retired as an editor. Corvus cornixtalk 21:40, 19 May 2008 (UTC)

WP:RD/M
vandalism

There's (probably bot-driven) IP vandalism/spam going on over at the Miscellaneous reference desk. It's from a large number of different IPs, but since they are either sock- or meatpuppets, an administrator might want to block them en masse. Angus Lepper(T, C, D) 18:04, 19 May 2008 (UTC)

I think Friday and Atlant are taking care of them. Seraphim♥Whipp 18:05, 19 May 2008 (UTC)
I've semi-protected the page for a few hours. If nobody does it before I do, I'll reset back to move=sysop before the protection expires. Looks like a spambot. - Rjd0060 (talk) 18:12, 19 May 2008 (UTC)
Protection reset. - Rjd0060 (talk) 21:31, 19 May 2008 (UTC)
Another spam attack. Only 1 IP (blocked), but judging on what happened earlier, they would probably just move to another, so I've protected
WP:RD/M for two hours. Can someone reset the protection again when it expires? Thankee. Seraphim♥Whipp
22:33, 19 May 2008 (UTC)

Something wrong with db-club and db-group templates

Resolved

Something has gone wrong with

template:Db-group so that they read "This page may meet Wikipedia’s criteria for speedy deletion as an article about a real person that does not indicate the importance or significance of the subject", whereas they used to read "about a club or group". The last edit to both templates was on 4 April, but I think whatever has gone wrong is more recent than that and is deeper in the template system, because on clicking "edit" I see the words "a club or group" still there. It is causing confusion - I have seen a speedy for a club objected to because "it isn't about a person". JohnCD (talk
) 21:26, 19 May 2008 (UTC)

I'll take a look. Those two are formed through transclusions of the main {{ *** 21:48, 19 May 2008 (UTC)
It comes from this edit to db-bio. The question is: should we modify db-club so that it transcludes db-a7 again, or retarget db-bio to db-a7 ? Cenarium (talk) 21:50, 19 May 2008 (UTC)
I went ahead and changed the template to transclude a7 again, changing db-bio would have wider-reaching consequences if people are now used to it redirecting to its current target. Also, double-transclusions have more impact on the server (
Ɣ ɸ
*** 21:55, 19 May 2008 (UTC)
I also prefer this option. It has already been discussed on the talk page by the way. Cenarium (talk) 22:06, 19 May 2008 (UTC)

Please help with board and table game articles

Resolved

Since

new message that I left there. I don't know if this qualifies as vandalism, but as Barneca has blocked a bunch of sock puppets, and this is a new one with the same editing behavior, I would much appreciate if an admin could have a look. Many thanks! --Craw-daddy | T
| 22:27, 19 May 2008 (UTC)

Blocked. -Chunky Rice (talk) 22:35, 19 May 2008 (UTC)

Bad Old Ones tool - image deletion

After having used this tool Bad Old Ones tool for a bit, I did a test run and found out that it is giving many false "negatives" (images that are actually in use being shown as 'unused'). I've left a 'bug report' for the owner, and have informed

talk
) 05:40, 19 May 2008 (UTC)

This tool is designed for commons use, but it's not designed for use for orphaned fair use. It uses a Commons-only tool called checkusage to determine if it's orphaned or not. Using it from enwiki will not yield good results. Maxim(talk) 12:10, 19 May 2008 (UTC)
If that's the case, then it definitely shouldn't be on any of the en.wiki...only image maintenance pages. It does have one option that should show images on a specific language wiki, but that apparently doesn't work as it's giving false reports. Also, it is stating that Image:X isn't used on any projects, which is clearly incorrect, as they're used here. I'll update my request with DumbBOT to reference this, and remove the use on the en.wiki only maintenance pages.
talk
) 15:18, 19 May 2008 (UTC)

I have removed the link from the "template starters", which are the templates that contains the text that is initially put in the category on creation. These templates are linked from User:DumbBOT/CatCreate. I have not changed the categories that have already been created (please ask someone with popups or similar tools if this is really needed). Tizio 12:29, 20 May 2008 (UTC)

Bromley Page - Can someone Please resolve this ??


user:Diamonddannyboy has been repeatedly adding Darren M Jackson to the Bromley page. Even though the source on the Darren M Jackson is unreliable and also for the following reasons.:

*** 19:18, 23 May 2008 (UTC)

To say nothing of that sig directing to a REALLY weakly-written article. I went to the edit history (to make sure I wasn't going to insult anyone here if I spoke my mind) and I swear I half-expected to find "Catbert" as the main contributor. ...Putting THAT one on my "improve" list...
Gladys J Cortez
00:38, 24 May 2008 (UTC)

Since BCBot's MTC function is currently suspended, it makes sense to temporarily replace the redirect with a brief explanation of the process that links to

20:05, 23 May 2008 (UTC)

Fortune Global 500

Resolved

I thought I would bring it to your attention the edit war on Fortune Global 500. Beenlaw (talk) 19:59, 23 May 2008 (UTC)

Both users have been blocked. That was some edit war...
inthegarden
20:09, 23 May 2008 (UTC)
I would suggest a talking with
WP:SOCK. -- Ricky81682 (talk
) 21:15, 23 May 2008 (UTC)
Time to request for a checkuser? seicer | talk | contribs 01:42, 24 May 2008 (UTC)

Proposed community ban of Betacommand

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Given the comments here, the community has decided to place Betacommand under an editing restriction (the sam korn solution). He is banned from using an automated program to make edits, either on his main account, or bot account. He is also placed on a civility parole, and any edited seen as uncivil by an uninvolved administrator may lead to a block. Failure to comply with either of the restrictions will lead to a block of up to one week. Ryan Postlethwaite 00:28, 25 May 2008 (UTC)

Per discussion at

talk · contribs) and all known aliases/sockpuppets, for a period of three months. If enacted, and per our banning policy, if he tries to evade the ban the block timer will be reset and his ban will start anew. Please see my statement there for my reasoning. —Locke Coletc
22:50, 18 May 2008 (UTC)

  • Support Based on the positive evidence of abusive sock puppetry, continued abuse of bot privileges, harassment of blocking administrators as detailed in my statement, continued incivility and continued failure to recognize and correct his behavior, I support the proposed ban. MBisanz talk 23:01, 18 May 2008 (UTC)
  • Support, clearly exhausted community patience. I'd go for indefinite ban, but that may be considered too harsh by others. Seriously one of the rudest editors I've ever encountered on here. I cannot understand why this hasn't happened long ago.
    talk
    ) 23:05, 18 May 2008 (UTC)
  • slow down someone will surely unblock, and that will be the end of the ban. I'd love to see something happen here, but only more moderate action will have general support.DGG (talk) 23:07, 18 May 2008 (UTC)
  • Oppose this action but support escalating sanctions under individual admin discretion. Ryan P already had this ball rolling, then the universe exploded. Beta needs a series of steps applied by the entire community to realize the consequences of unmodified behaviour. Franamax (talk) 23:10, 18 May 2008 (UTC)
    • I'm sorry, did you miss Betacommand 2? Specifically, Wikipedia:Requests_for_arbitration/Betacommand_2#Betacommand_instructed, where he was already told to remain civil, and violated that, and was told to only operate his bot for approved tasks, and violated that as well? The balls been rolling for a couple of months, but nobody will pull the trigger. —Locke Coletc 01:04, 19 May 2008 (UTC)
      • Actually I haven't missed a heartbeat, Ryan made an unequivocal notice, that looked like a good line in the sand to work from. I'm not unaware of previous history ;) Franamax (talk) 01:31, 19 May 2008 (UTC)
        • You're saying the ArbCom remedy wasn't a line in the sand? If we keep up with giving out warnings without taking any action, we might as well change the Wikipedia:Blocking policy to the Wikipedia:Warning policy. —Locke Coletc 04:08, 19 May 2008 (UTC)
          • Yeah it was, but there was some beach volleyball being played at the same time. ArbCom draws lots of stuff in the sand, some of it sticks, some of it melts. RyanP was poised on action, the Arb decision was there to back him up, the patent evidence was there - now we're getting on to several MB more server space without resolution, and many are focussed on the sock allegation and NFCC, which are far from the point. However, events are lately pointing toward a resolution, which is encouraging. "Mene mene", right? :) Franamax (talk) 04:37, 19 May 2008 (UTC)
            • This definitely isn't about the sock issue (and definitely not NFCC, that's sooooo two months ago), it's about the overall effect his actions have had, and his totally unapologetic attitude (in fact I can't think of a time during this whole situation where he's apologized for his behavior, only that he's tried to skew discussion towards unblocking his bot, his alt and returning to a mostly business-as-usual status). "Mene mene" indeed. :P —Locke Coletc 06:17, 19 May 2008 (UTC)
            • It looks like the only thing ArbCom has done in the sand was to piss its name in Chinese characters: very impressive at first glance, but in the long run useless. ArbCom instructions are useless when ignoring them goes unpunished. Betacommand has ignored just about everything he could possible ignore. Bullzeye's description of Betacommand is the best I've ever come across: "a nuclear powered icebreaker with the throttle stuck on Flank and the Captain asleep in his cabin with his iPod on and a GO AWAY sign on the door." AecisBrievenbus 12:54, 19 May 2008 (UTC)
  • This proposal, along with the rest of this recent Betacommand drama, strikes me as an extreme case of overreaction. I too was taken aback by the sudden revelations everywhere that BC was sockpuppeting, since malicious sockpuppetry by anyone is completely inexcusable - but then I read into it for myself and found that his "puppetry" was limited to a single alternate account that had only crossed paths with his main one once? Please, let's just calm down and let this small incident pass.
    23:15, 18 May 2008 (UTC)
    • Betacommand is blatantly violating the ArbCom remedies from Betacommand 2, and you believe this is an "overreaction"? —Locke Coletc 01:04, 19 May 2008 (UTC)
  • Oppose Would support individual escalating blocks for continued incivility, but this proposal is far too draconian for my taste. Incivility needs to be stopped, but this sort of response is out of proportion to the offense at hand. I would support sanctions, just not this sanction. --Jayron32.talk.contribs 23:17, 18 May 2008 (UTC)
  • Oppose: Ugh...More overreaction. Looking at it, I guess I am not surprised. - Rjd0060 (talk) 23:19, 18 May 2008 (UTC)
    • Yes, clearly overreaction, the community was expecting far too much by thinking he would abide by the Betacommand 2 remedies. —Locke Coletc 01:04, 19 May 2008 (UTC)
  • Question A few days ago I proposed one week, and some people thought it absurdly short and others thought it absurdly long. I propose it again as a basis for discussion. DGG (talk) 23:23, 18 May 2008 (UTC)
  • It was noted above (or on what has forked onto a separate page) that BC has communication difficulties. He tends to do the more drama-prone jobs around here, compounding any communication difficulties which may exist. I'd suggest that none of the commentators here would be able to comport themselves any better than BC has done, if they were to be placed under the same workload as him. We shouldn't be aiming to get rid of Beta, but more to provide him with more support. Much as we appear loath to refer to ourselves as such, we are a community and we need to care of one another, indeed more than we do already. We don't kick people out of the fold for being imperfect.
    inp23
    23:24, 18 May 2008 (UTC)
    This, by the way, is complete nonsense. If someone were somehow forcing him to work in this area, it might be valid, but he chose this work. If he knows he can't handle drama well, it's his responsibility to find areas that he can competently work in. His failure to do so only indicates that the problem is indeed him. Friday (talk) 14:30, 19 May 2008 (UTC)

The Sam Korn solution

I strongly disagree with this action. As in strongly. While I won't call it precipitous (for fear of causing death through hilarity among certain members of the community), I will call it unnecessary. I totally agree without the slightest hesitation that concrete remedies are necessary. I would imagine them to function along the lines of these:
  • Betacommand is not permitted to run bots
    Running bots should be a position of trust. It is plain that Betacommand does not have that trust. Criticism of his bot work has frequently unheeded and met with incivility. This is not good enough. Betacommand has no right to run bots. Any unauthorised bot activity should be met with blocking. I would suggest a minimum of a week.
  • Betacommand is placed upon civility parole
    Betacommand's response to criticism has been totally unacceptable and must change. Any incivility should be met with an appropriate block. I would suggest that a month should be the outside; I do not expect anything less than three days to be the minimum. Unblocking should only be done with great care: I would be horrified if people continued to think that Betacommand can get away with incivility after the events of the last few days.
I don't see the point of a restriction on the use of alternate accounts. If they are abusive, that is already covered. Abuse would include attempting to evade the restrictions of this kind of decision. If they are not abusive, and Betacommand manages to get to a point where he has an account that is not identified with him and behaves acceptably, all the more power to him.
I feel this kind of set of provisions would be more useful than the considerably blunt instrument of a ban. Sam Korn (smoddy) 23:25, 18 May 2008 (UTC)
Based on his defiance of the
BAG ruling related to the nature of his bot's messages, his continued abuse of bot privileges on multiple accounts, and continued incivility, this is also an acceptable sanction. MBisanz talk
23:28, 18 May 2008 (UTC)
Scrap anything else I've said - Sam proposes an unacceptable solution, but it's better than all the alternatives. Churchill would approve. Franamax (talk) 23:32, 18 May 2008 (UTC)
Ditto. DGG (talk) 23:36, 18 May 2008 (UTC)
  • (ec)Support It seems like there's a new thread about BC's behaviour, civility, unauthorized bots, and now sock puppets? His supporters continually say he's being provoked..but that's the problem. If he could control his temper we wouldn't be here. An angry response to a stupid comment is never acceptable. LegoTech·(t)·(c) 23:42, 18 May 2008 (UTC)
    • Support Sam Korn's version. Escalating and calculated sanctions are what are needed here, not a 3-month ban... Sam's sanctions (no bots, civility parole) is perfectly reasonable. --Jayron32.talk.contribs 23:43, 18 May 2008 (UTC)
  • We'll never agree on a complete ban. Forbidding Betacommand to run bots may be acceptable for a week, but a lot of people think that some tasks of BCB are very useful. I propose this as a longer-term alternative :
    • Betacommand is forbidden from bot tasks on any account except Betacommandbot.
    • All the tasks of Betacommandbot must be BAG-approved.
    • Betacommand is on civility restriction.
For, say, three months, then see how it works and discuss again. Cenarium (talk) 23:52, 18 May 2008 (UTC)
I also support Sam Korn's proposal, but we should find an agreement on the duration. Cenarium (talk) 01:06, 19 May 2008 (UTC)
Comment I am reminded of a conversation I had with Betacommand, in which he indicated he had a special relationship with the WMF and/or developers. He indicated that this special relationship permitted him to be granted SUL accounts for him and his bot, among other undescribed privileges, despite not having an admin flag on any WMF wikis. I therefore contemplate if there is an existing
WP:OFFICE or m:Developers ruling that would prevent the community from stopping Betacommand's operation of his bot. If an authorized individual could respond to this comment, indicating whether or not the community has the authority to impose such sanctions, it would help clear up this situation. MBisanz talk
23:54, 18 May 2008 (UTC)
Oppose as being a bit too extreme here. However, Support Sam Korn's proposal - Alison 00:17, 19 May 2008 (UTC)
  • Comment with regard to BCB's useful tasks: it is incumbent on the community to identify the BCB tasks with attention to mission-critical and other tasks and effectively "de-task" BCB with preferably open-sourced alternatives. This would at least defuse the argument over how important the bot is. Franamax (talk) 00:31, 19 May 2008 (UTC)
    • Per Carnildo, his tasks are not significant or important, and even if they were, I disagree that his contributions are somehow relevant in the clear violation of policy. Even Betacommand says his bot won't be performing any tasks for the next thirty days, so a bot restriction wouldn't do much. —Locke Coletc 01:04, 19 May 2008 (UTC)
      • I'm fine with the botops being un-needed, if some relevant authority would confirm that, so much the better. If indeed all BCB tasks are redundant, then BCB should under the circumstances be permanently blocked. If BC wishes to resume botops (which is not evil, a lot of people/projects come to him for help), then there should be some clear parameters, such as defined tasks amd separate bot names for clearly separate tasks, rather than the loosey-goosey "my code is too complex for you to understand" status-(no longer)-quo. But let's quantify where exactly BC/BCB is too valuable to block and eliminate those roadblocks. Then we can address the actions of this editor of themselves. Franamax (talk) 01:58, 19 May 2008 (UTC)
  • Comment The "civility parole" part of Sam Korn's proposal is reminding me of Roman legal history where the most unobeyed laws are the most restated. Besides normal wikipedia civility rules, he's already been placed under further civility restrictions by ArbCom. Unless I am misreading the date, this was only last month. Recommend restating to "Betacommand may actually have to adhere to his civility parole and some related wikipedia policies". Deacon of Pndapetzim (Talk) 00:32, 19 May 2008 (UTC)
  • Support with fire - I support the community ban. Enough is enough. Not only was it proven he violated 3RR with his sockpuppet, but the fact that he has virtually ignored the issue is repulsive. Thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread involving BC also amounts to disruption of the project. I for one am tired of the "Defend Betacommand At All Costs Cabal" and it must end now. - ALLST☆R echo 00:36, 19 May 2008 (UTC)
  • Yeah, a 3 month ban is an overreaction. Sam Korn's idea works for me. naerii - talk 00:38, 19 May 2008 (UTC)

What makes us think he'll change this time? He's been to arbcom twice and it's had little if any affect. If Sam's proposal is adopted, it has to be his absolute last chance; if that doesn't work, I won't hesitate to support a ban. RlevseTalk 00:49, 19 May 2008 (UTC)

  • While I believe Beta's work is quite irreplaceable, a line needs drawing. I'm in favour of Sam's proposal; Beta currently doesn't have the community's trust to run a bot. However, I think, he demonstrates that he can be trusted after three months, I don't see why not to give him back his bot privileges. The biggest issue here is the incivility; if you treat others with respect, they'll treat you the same. And if they don't but you do, they'll get blocked for disruption/incivility/harassment. Maxim(talk) 01:01, 19 May 2008 (UTC)
  • Support Sam Korn's version. Enough is enough. ➪HiDrNick! 01:03, 19 May 2008 (UTC)
  • Comment. Nothing will happen here. BC has deserved a ban for a long time. But even if the community coalesces around a long block, or an outright ban, one of his bodyguards will overturn it unilaterally. It always happens. Why should this time be any different? Bellwether BC 01:05, 19 May 2008 (UTC)
  • Why do you always have to assume an evil cabalist will always do something you won't like? Evaluate the situation without flamethrowing towards someone who supports Beta. Frankly, your communications aren't exactly better than his. Maxim(talk) 01:09, 19 May 2008 (UTC)
  • Support your assertion that my communications are no better than BC's or retract it. It's ludicrous on its face. There's no need to "assume" anything. It's evident that BC has bodyguards that ride to his rescue every time he faces any sanction for his actions. Bellwether BC 01:44, 19 May 2008 (UTC)
  • You just proved my point. You're making unfounded accusations again... Seriously, why can't you be nice to Beta for a change? Trust me, he'll be nice too. Maxim(talk) 12:08, 19 May 2008 (UTC)
  • Support Sam Korn's version. I would support a bot ban for a year. It's not a basic human right be allowed use of a bot. Allow him to only use his main account. And have him on civility probation, although I don't think that will stick... --Pesco (talk) 01:09, 19 May 2008 (UTC)
  • Absolutely positively hell no to the community ban. Nwwaew (Talk Page) (Contribs) (E-mail me) 01:13, 19 May 2008 (UTC)
  • Support Sam Korn's version. I'd like to note, however, that the vast majority of the previous complaints about Betacommand have been either people unhapppy with our image deletion policies (which is not Betacommand's fault), people unhappy with the way the bot works, or people unhappy at Betacommand's incivility. Has anyone in the BC lynch mob forming here had any issues with incivility from the now-blocked alternate account? BC is stuck in an awkward position, only part of which is of his own doing. He cannot turn over a new leaf (because he'll be blocked if he uses a sock) and he can't escape the past because of a group of users who will not let go of the past. Horologium (talk) 01:13, 19 May 2008 (UTC)
  • Comment: I just want to note that Betacommand has already stated that he will not use BetacommandBot for a month, except for one specific, uncontroversial task. See that statement here. I've spoken to BC about this and he said he does indeed have a list of tasks that he will hold off on, for this thirty day period. - Rjd0060 (talk) 01:19, 19 May 2008 (UTC)
  • Comment A ban of a user who has contributed much in the past seems a bit cruel and draconian. --SharkfaceT/C 01:29, 19 May 2008 (UTC)
    • Are you saying that the value of an editors contributions allows him to violate personal attack and sockpuppet policies (amongst others)? That's a slippery slope that nobody should want to go down, but I keep seeing that attitude in discussions about Betacommand and his behavior. —Locke Coletc 01:34, 19 May 2008 (UTC)
  • Strong oppose: Blah. --MZMcBride (talk) 01:35, 19 May 2008 (UTC)
  • Oppose full ban, support Sam Korn's version. It's important for us to remember that blocks and bans should be preventative, rather than punitive--a major point brought up during the initial blocking was that Betacommand has a number of high-speed editing tools at his disposal. By banning the use of these tools for a reasonable amount of time, we ensure that the community has sufficient time to discuss their further use. While I personally have no reason to think that Betacommand is anything but sincere in his offer to refrain from bot editing, the fact that a full-on ban is being seriously discussed tells me that we need something a little more formal in nature. --jonny-mt 01:37, 19 May 2008 (UTC)
  • Support Sam Korn's version of it. Something has to be done. Enigma message 01:47, 19 May 2008 (UTC)
  • Support the burning with fire of any plan which would prohibit a user who participates only in bot work from operating bots, and then masquerade itself as a less harsh alternative than an all out ban. --uǝʌǝsʎʇɹoɟʇs(st47) 01:52, 19 May 2008 (UTC)
Would you also support encouraging said user to make substantive article-space contributions on his own initiative, in areas of his own interest, by manual means? If so, I'll help as best I can. The sole focus of anyone on Wikipedia shouldn't be just to make the computers run faster. Franamax (talk) 02:07, 19 May 2008 (UTC)

Oppose. I'll support graduated remedys here. NonvocalScream (talk) 02:26, 19 May 2008 (UTC)

  • He technically can't be banned now, so let's just concentrate on Sam Korn's remedy. Wizardman 02:28, 19 May 2008 (UTC)
  • Oppose - overreaction Alex Bakharev (talk) 02:40, 19 May 2008 (UTC)
What do you think of Sam Korn's remedy? Franamax (talk) 03:47, 19 May 2008 (UTC)
  • Support This goes on and on and on. Betacommand hasn't shown any self discipline and inspite of his contributions he needs to understand that, like everyone else, he has to respect the rules and other users. Instead he has a long track record of repeatedly breaking the rules and abusing others as he sees fit. That his work has made him a target is no excuse - he should have expected that going in and found more appropriate means to repsond. It seems like nothing applies to this guy and his bot work is a perpetual get of jail free card. Otherwise, someone might just want to get down to it and start work on WP:ßcommand immunity and just lay down some policy that makes it plain that he can do whatever he wants, to whoever he wants, however he wants to do it without fear of sanction or all kinds of wasted discussion. His behaviour is consistently appalling. It is fundamental that the folks who enforce the rules have to follow the rules themselves or face the consequences. Wiggy! (talk) 03:19, 19 May 2008 (UTC)
What do you think of Sam Korn's remedy? Franamax (talk) 03:47, 19 May 2008 (UTC)
  • I could have sworn we deleted CSN so that we could have discussions here and not do votes for banning. Silly me. I oppose the ban. seresin ( ¡? ) 03:29, 19 May 2008 (UTC)
What do you think of Sam Korn's remedy? Franamax (talk) 03:47, 19 May 2008 (UTC)
  • Support Sam Korn's remedy Community banning Betacommand is an overreaction. There are specific problems with Betacommand's behaviour that can be addressed with the proposed remedy and I'm pretty damn sure there is an admin willing to unblock anytime so community banning won't work. If you want him banned you'll need to convince ArbCom to do so.
    talk
    ) 03:57, 19 May 2008 (UTC)
  • Support Sam Korn's remedy. A complete ban would just polarize things more, as Betacommand's defenders would go to even greater lengths to find him a way out, but Sam's remedy is reasonable, appropriate to the situation, and has a chance of resolving the issues. rspeer / ɹəədsɹ 04:55, 19 May 2008 (UTC)

Counting here with my trusty hacksaw, support = 3; oppose = 6; comment/indeterminate = 6; Sam Korn = 16. No consensus maybe, but a pretty clear preference. All figures +/- 4, 95% of the time. Franamax (talk) 04:52, 19 May 2008 (UTC) If anyone disputes my count, please comment and do not change my signed statement, thanks, or just do your own count, thanks. Franamax (talk) 06:34, 19 May 2008 (UTC)

  • At best you have proof that BC was edit warring and breaking the 3RR, but the use of the other account is obviously a mistake. -- Ned Scott 05:23, 19 May 2008 (UTC)
  • (EC with allstar, response to ned scott)I'm not sure this is about a single incident, but rather a pattern of behavior over a long period of time. For the record, I don't believe that there has been any sockpuppetry here at all, but the pattern of incivility needs to be addressed and remediated... --Jayron32.talk.contribs 05:11, 19 May 2008 (UTC)
  • I'm not opposed to addressing those concerns, but the proposals in this thread are based on the SOCK accusations. That is what I am opposing. -- Ned Scott 05:23, 19 May 2008 (UTC)
  • So, because one thing he did wasn't bad enough for you, he should be forgiven for all the others? His violating 3RR with a hidden sock doesn't bother me as much as his violating his ArbCom restrictions with a run of thousands of unapproved, disruptive bot edits on his own account, or any of the frequent uncivil and disruptive edits he has made in the past year. I'd say it's pretty clear that Sam's remedy is mostly about his misuse of bots, not his sockpuppeteering. rspeer / ɹəədsɹ 05:58, 19 May 2008 (UTC)
  • I'm not opposing Sam's remedy. I take no comment (for the time being) on how to handle the bot issues and the civility. -- Ned Scott 06:51, 19 May 2008 (UTC)
  • I understand your concerns Ned, but please look at MB's RFArb subpage where he clearly documents that BC had his rollback revoked on one account and then proceeded to deceive the RFR admins into granting it for his other sock. If that isn't abusive sockpuppetry, I don't know what is. --Dragon695 (talk) 14:50, 19 May 2008 (UTC)
  • Support Sam Korn's version, or at the very least a "bot parole": any rapid editing except that which has been explicitly approved by the Bot Approvals Group is grounds for blocking. He's had far too long a history of unapproved and disruptive bot-like editing. --Carnildo (talk) 07:04, 19 May 2008 (UTC)
    • Support Sam Korn option. Betacommand has been given numerous "don't do it again"s for more than a year, and has systematically disregarded any criticism. His bots are now giving no real benefit to the project, only problems (messing up articles, adding large numbers of edits which then need to be reverted), and we have plenty of bot coders who actually can handle people and follow the rules. Betacommand therefore should not run any bots ever again. That said, I am concerned that this community decision will just end up amounting to nothing. His unapproved DEFAULTSORT bot violated an arbcom ruling only two months old, so how is he going to react to any conditions set forth by mere editors, whom he considers to be trolls and drama queens? Also, given past events, I see it as highly likely that any blocks instituted for violating the conditions will be summarily undone within hours. But I am willing to give it a try. Is he back? (talk) 07:05, 19 May 2008 (UTC)
  • Oppose (god I am so tired of these two), I disagree with the findings of facts above. I have no opinion on Sam's proposal (I have mixed feelings about it). -- lucasbfr talk 07:32, 19 May 2008 (UTC)
  • Support Sam Korn's proposal.
    H2O
    ) 08:48, 19 May 2008 (UTC)
  • Oppose blocking Betacommand. Support banning him from operating bots, either on other accounts (ie, BC2 and BCBot need to be blocked) or on his main account.
    08:53, 19 May 2008 (UTC)
  • Oppose ban, but only because it's never gonna happen; thus, support the Korn Plan. However, sad to say, Sam's proposal can be translated at its core into "The community will now tell Betacommand that we really, really, REALLY mean it this time, and we're NOT kidding. Don't MAKE us turn this Wikipedia around...." We'll find ourselves heading back here soon, I'm afraid, wagging our multiple megabytes of discussion behind us...
    Gladys J Cortez
    09:07, 19 May 2008 (UTC)
    • Actually, I don't think that's true. As far as I'm concerned, my suggestions would mean that Betacommand would not be running bots at all in the foreseeable future. Not just "only uncontroversial bots" -- no bots, no bot flags, no running bots on the main account. That is one of the major problems with Betacommand's editing. As to the incivility point -- the existing remedies have no teeth. This proposal has teeth and I for one would be outraged if people continued undoing blocks of Betacommand without very good reason. I don't see why the options have to be go ahead and do what you like and extreme ban with a kick as you go through the door. Sam Korn (smoddy) 11:51, 19 May 2008 (UTC)
      • To clarify my concern (and please excuse my snark of last night--no more editing after bedtime for me!): Beta has been told--in a freaking ArbCom decision, for Pete's sake, which (even if the findings and remedies haven't any teeth, like in this case) generally amounts to AT LEAST a wake-up call for the individual on the receiving end to alter his/her behavior immediately--to only run bots acceptably; to act civilly, to do A, not to do B. If THAT hasn't stopped him, I question what will--especially since he seems to hold sway over the BAG.. Sam, I think your plan is by far the best-constructed option made available to the community, but I just don't trust that Beta won't find a loophole somehow.
        Gladys J Cortez
        15:15, 19 May 2008 (UTC).
        • Eternal optimism is good for the soul ;-) Sam Korn (smoddy) 15:20, 19 May 2008 (UTC)
  • Support the Korn plan - no involvement with bots - either running them or as part of BAG. ViridaeTalk 09:08, 19 May 2008 (UTC)
  • Oppose Betacommand has himself already 'banned' his bot for any tasks except two uncontroversial, that is enough. I am again stating, I believe he is helpful (at least in the way I have always communicated with him). --Dirk Beetstra T C 09:54, 19 May 2008 (UTC)
  • Do it SKorn's way. An outright ban is just not appropriate here... I think BC's intentions are good, but his communication difficulties often make this hard to see. -- Anonymous DissidentTalk 11:38, 19 May 2008 (UTC)
  • oppose even thouigh we love drama, this has gone way to far. AzaToth 12:06, 19 May 2008 (UTC)
  • This needs to be an arbcom action. Lynchmobs of whoever shows up are not how we determine whether or not someone may edit. I think the time has come that despite his outstanding work with non-free images, Betacommand is too much of a liability. But a neutral arbitration committee needs to make that decision. --B (talk) 12:30, 19 May 2008 (UTC)
  • Oppose. No bloody way! Betacommand has done far more good than harm. He is no longer on the front line of the fair use management, and is going to stay away from BAG and bot policy. Any ban would be because of past issues. Yes, the community really means it this time; but we do not need to demand a pound of flesh to prove we mean it. If in a month he has kept breaking community expectations, it can be sent to arbcom for review.
    chat
    )
    12:35, 19 May 2008 (UTC)
  • Comment Yes, but how many times do we have to keep saying "if in a month"? I've ran out of "if in a month"s long ago and have had to take out a mortgage on new ones - and the economy has gone to hell so all these new "in in a month"s are losing value every day that passes. - ALLST☆R echo 13:04, 19 May 2008 (UTC)
  • Addendum - Just to clarify, the "writing on the wall" reference referred to the silent but inevitable downfall that often awaits a user if they dare to imperiously tip some ancient Wiki-Deity's favorite cow. Based on the number of Reject votes given without any pretense of explanation, I'd say he's about a medium-sized one. Note also that this isn't a statement on his character, merely his status in the community. Bullzeye (Ring for Service) 06:43, 20 May 2008 (UTC)
  • Support Sam Korn Solution - This seems reasonable enough to me. A ban may be unnecessary at this stage. The main problem lies with his bot, so we should be looking at remedies to that rather than banning Betacommand himself at this stage.
    :.
    16:33, 20 May 2008 (UTC)
  • Support Sam Korn solution but oppose a community ban. I have had concerns about BC's behaviour for a while, and expressed those at the RfAr and elsewhere, but am convinced he is a good faith user with serious issues rather than a malintentioned user. The socking issue in and of itself was a red herring in my view. Orderinchaos 17:54, 20 May 2008 (UTC)

Moving forward

There is clearly no consensus for a community ban. Rather than people continuing to "support" or "oppose" the initial proposal for a community ban, we should be moving forward on the issue. - Rjd0060 (talk) 17:06, 19 May 2008 (UTC)

There is no support for a community band. There is substantial support for limiting Betacommand's automated edits. I've already blocked Betacommand's bot account to enact a set of sanctions proposed by Durova that are compatible with the first part of Sam Korn's proposal. A ninety day break from running a bot seems like a reasonable compromise, let us figure a way to fairly review Betacommand's actions during this period and decide how to give him a chance to re-implement bot tasks afterward in an uncontroversial and error-proof way. If successful, we may retain a prolific bot operator and allow ill-will to subside on both sides of the debate. The civility parole may be moot as all editors are expected to maintain a respectful tone in their on-wiki correspondence at the risk of being blocked for profane insults and other childish behavior. ˉˉanetode╦╩ 18:54, 19 May 2008 (UTC)

-

the civility part is not moot, as the "general expectation" doe snot seem to have accomplished anything. The point of it is to give a warning to beta that he is not exempt from it, and that a final warning has been given. Yes, it should be unnecessary, but experience seems to show otherwise.DGG (talk) 18:59, 19 May 2008 (UTC)
Point taken, I only meant to say that the danger of being blocked for gross incivility is a no-brainer. The concept of "civility parole" seems redundant given the circumstances. ˉˉanetode╦╩ 19:20, 19 May 2008 (UTC)
I think civility parole, at least when used by arbcom, is generally taken to mean "no warning necessary" - that any uninvolved admin can issue a short block if he is uncivil. Mr.Z-man 20:52, 19 May 2008 (UTC)
Suffice to say I wasn't clear on the process entailed by civility parole and I agree wholeheartedly with its intent. Thanks to you both for the elaboration :) ˉˉanetode╦╩ 21:17, 19 May 2008 (UTC)
Dude, I'd support a community band. It could be called "Anetode and the Beta Blockers". I'll play drums. :) rspeer / ɹəədsɹ 19:13, 19 May 2008 (UTC)
Lol :) ˉˉanetode╦╩ 19:20, 19 May 2008 (UTC)
I think Durova's suggestions are sensible, though I do not see the need for the account restriction. That seems nothing short of vindictive. Sam Korn (smoddy) 19:31, 19 May 2008 (UTC)
Sam, if you're going to call my proposal vindictive in public, please give the courtesy of a heads up. It isn't helpful when someone of your standing posts such negative speculation. Fortunately other people haven't picked up on the tone, but in a heated discussion such as this one there's a distinct possibility of it being taken the wrong way. DurovaCharge! 22:50, 19 May 2008 (UTC)
Sorry, I phrased that really badly. I am certainly not saying that your proposal or the desire to restrict Betacommand's accounts is rooted in vindictiveness -- it was a terrible choice of words and I apologise for it. I was trying to say that it disputed that the accounts have been used abusively (certainly there was no intent to do so) and therefore that the proposal to restrict the accounts seem more rooted in general emotions towards Betacommand than in necessity. I would, however, urge anyone to follow MBisanz's advice below. Sam Korn (smoddy) 13:16, 20 May 2008 (UTC)
Several users objected to account restrictions on similar grounds. Right now the Quercus basaseachicensis and BetacommandBot accounts are blocked, Betacommand and Betacommand2 are not. Since both proposals require an end to bot runs, I don't see any reason to unblock BetacommandBot and the Quercus account is still under some amount of controversy. Surely two accounts (including one for use on public computers and rc patrol applications) are enough. ˉˉanetode╦╩ 20:42, 19 May 2008 (UTC)
I think Sam is leaving open the door that Betacommand, could, if he wanted to, exercise his RTV and start a new account, unconnected to his former activities. My opinion would be that if he did so, he would need to stop using the Betacommand account, per
WP:SOCK
:

If you have a negative track record and you have decided to make a genuine, clean, and honest, new start, and do not wish it to be tarnished by your prior conduct, you can simply discontinue using the old account(s), and create an unconnected new account which becomes the only account you then use, and is used in a good manner. By "discontinue", it is suggested that the old account is noted as being inactive, in order to prevent the switch being interpreted as an attempt to abusively sock puppet.

MBisanz talk 20:47, 19 May 2008 (UTC)
Dubious. The Korn Solution is running at nearly 2:1 support. Let's not squeltch the discussion here prematurely. ➪HiDrNick! 19:24, 19 May 2008 (UTC)
For what it's worth, I don't think much will come out of this discussion. However, I think it is very fair to say that there is wide support for (a) placing BetaCommand on civility parole and (b) giving him less leeway even if that means being harsher with him than with the average user. There was little made of the block he received on April 22nd, just a few days after the end of the arbitration case. Not only was the block lifted inappropriately soon, it was also lifted despite BetaCommand's absolute refusal to admit he'd done anything wrong. Sure, anytime BetaCommand slips up, all the people he's aggravated over the years want him to go down but, hey, that's the hand he's been dealt and it's not like he's got no responsibility in this. So if you're BetaCommand, no alternate account for you, no quick unblock for any civility-related block, no reverts except in cases of blatant vandalism, no putting yourself in conflict situations. Pascal.Tesson (talk) 21:09, 19 May 2008 (UTC)
Well he's aggravated me, & I don't have a strong desre to see him go down. I just want him to act more civil & be more careful with his automated edits. (And if he did so, maybe Carcharoth would find the time to do less stressful things than constantly mediate this ongoing forest fire.) -- llywrch (talk) 21:56, 19 May 2008 (UTC)

The real problem - competence

As someone wrote above, "There is substantial support for limiting Betacommand's automated edits." Yes. Whether or not there is a community ban, this editor should not be running 'bots. As a programmer, he's just not good enough and nowhere near cautious enough. For his latest botched effort, see Wikipedia:Administrators' noticeboard/Betacommand blocked for sockpuppetry#Current block status. He was trying to undo some damage he did with a previous bot, and tried to use a self-modified version of AWB to do it. His modified version was buggy, but by his own count, he did 144 edits with it without noticing that he was creating bogus edit summaries. His edit history does not show him trying any edits with his new program on a sandbox article or something in his own user space; he just started editing live articles.

It's this lack of caution that's the real problem. This can be trained out of beginning programmers, but this editor has been making mistakes like this for several years now and doesn't seem to be improving. So he should probably be making them somewhere else. The cleanup costs are too high here. --John Nagle (talk) 06:25, 20 May 2008 (UTC)

I was not using bad software, so please stop the attacks and insults saying I was. I was looking that the edit summary function of AWB, because I find it annoying that it always appends that to the edit summary. it was not buggy software but rather a typo in the edit summary. I was examining every edit that I made and there where no problems with the edits, just a minor typo in the edit summary.
βcommand
13:00, 20 May 2008 (UTC)
That's the problem, really. It's "annoying", so you disable it. It couldn't possibly be there for a good reason. Rules are for other people. --Random832 (contribs) 14:32, 20 May 2008 (UTC)
no where does it say that edit summaries made by the tool requires that using
βcommand 2
14:42, 20 May 2008 (UTC)
Probably no rules beta, just common sense. Non-sensical edit summaries are not helpfull, especially not 144 of them before you even realise you made a mistake. MickMacNee (talk) 16:25, 20 May 2008 (UTC)
I could swear we've had this conversation before... I don't object to Betacommand's work but he has shown no will to let others help him fix his bot or even acknowledge that the bot has problems that one simply wouldn't accept in any mission-critical software. The closest we got to something that looked like co-operation was when he explained how it works but he never accepted our offer to help him fix the bot. That said, those who are making a career out of continuously baiting him and pushing his buttons shouldn't feel too safe either. The way I got him to finally explain what his bot does from a programming point of view was by changing my attitude and be nice to him. Unfortunatey it wasn't enough.
talk
) 17:24, 20 May 2008 (UTC)
yes all bots do make mistakes, but I fix all the bugs that are brought to my attention (the few that popped up). I may have not implimented every feature request, but I dont like giving extreamly powerful code to just anyone.
βcommand 2
18:07, 20 May 2008 (UTC)
I know you put a lot of work into this and try to help out where no one else would but when you make a mistake like this which really boils down to you not spending enough time hacking the code to figure out why it still left half of the edit summary you wanted to remove it really doesn't look good in the eyes of others. I've tried this out myself Betacommand, it isn't hard to do if you just spend the extra minutes it takes and look what it is doing before you make over 100 edits. You can do this on a test wiki without much hassle. Can you see why this was unwise?
talk
) 18:31, 20 May 2008 (UTC)
To the refusal to share, I would state that John Nagle is not just anyone. He's someone with significant programming experience which includes, among other things, major contributions to fundamental TCP/IP functionality which we all take for granted today. I suggest that his criticism of your programming methods is spot on. Furthermore, should he think it helpful, I would suggest that he be given full access to all of your source code in order to evaluate its suitability. If you won't take advice from the community, at least take advice from a genuine expert. --Dragon695 (talk) 15:27, 21 May 2008 (UTC)
And here we have the great myth: That your code (rather than, say, your ego) is extremely powerful. I could probably code a bot in a day that could make 100 edits per minute or more. Those edits would likely be page blankings, but still. Being able to edit quickly is not something that code has to be "powerful" to do. --Random832 (contribs) 14:56, 22 May 2008 (UTC)

Just fyi

A community ban exists when no administrator is willing to unblock. I am willing to undo any indefinite block on Betacommand. ^

[omg plz]
 12:05, 20 May 2008 (UTC)

Me also. ➨ ЯEDVEЯS looks at danger and laughs his head off 12:08, 20 May 2008 (UTC)
Which is fine, because then the editor is simply indef blocked until there is a consensus to unblock. In this instance, should any admin unblock against consensus I would re-impose the block, block the admin, and open a RfAR to have the admin desysopped. LessHeard vanU (talk) 12:29, 20 May 2008 (UTC)
You're missing the point. The point is not that I am threatening to wheel war over a block (and I know you're not either). The point is that a community ban on BC is not possible because there are admins who are willing to unblock - thus nullifying a community-imposed ban. If a ban is wanted, Arbcom will have to impose it. ➨ ЯEDVEЯS looks at danger and laughs his head off 12:34, 20 May 2008 (UTC)
No, I got the point - BC cannot be community banned because there are those who would be willing to undo the block (but will not because were there is not yet consensus to do so). I was making clear that, following previous misunderstandings, that non-consensus to ban is not consensus to unblock. In what appears to be developing into a potentially divisive matter I was attempting to draw a clear line over what actions admins might be able to take in pursuit of their position in the matter. LessHeard vanU (talk) 12:43, 20 May 2008 (UTC)
Worth noting, for the record, that Betacommand's main account is not currently blocked. [74]ЯEDVEЯS looks at danger and laughs his head off 12:49, 20 May 2008 (UTC)
Again, yes, but we are talking about how the community may act in trying to resolve the problem (after gaining consensus there is in fact a problem) regarding BC. As you say, and last time I checked the wording was such, that a community ban is broken as soon as there is one admin that is willing to unblock. Unlike some other correspondents below, I feel that the above is a timely comment that stops the community enacting such a ban because it is immediately invalidated. The community can therefore decide to enact a block for a length of time or for an indefinite period, which is then open for anyone to try to form a new consensus to get it lifted. This is appropriate. However, if anyone is sufficiently em
BOLDened by the non-consensus to enact a ban to attempt to lift any agreed block before a consensus (created over days rather than hours, and a range of opinions rather than the first few agreeing respondents) then there should - and will, if I consider it appropriate - be consequences. If, per the statements by Demon and Redvers, there cannot be a ban then we are left with discussing if and what type of block is considered appropriate, and the result of that discussion is not invalidated by the actions or opinions of just one (or a few) admin(s). LessHeard vanU (talk
) 19:51, 20 May 2008 (UTC)

Yes, these disruptive admins are indeed a problem. Thank you for identifying yourselves. Do you care to explain why you have a particular user you would unblock regardless of the circumstances? This is quite a surprising and bold statement to make. Friday (talk) 14:35, 20 May 2008 (UTC)

Come to think of it, I don't particularly care why. It's enough for me to know that a couple of admins would promise, before the fact, to actively interfere with admins in the performance of their duties. Would you guys mind resigning your tools in advance rather than wheel warring? Betacommand has been "untouchable" for a good while now, and we've gotten a good look at what this accomplishes. It's not pretty. So, it's time to try something else now. If you don't want to help, don't help, but don't get in the way, either. Friday (talk) 14:47, 20 May 2008 (UTC)
Where did I say I "would unblock regardless of the circumstances"? Please point to where I said that. Go on. No? Also "If you don't want to help, don't help, but don't get in the way, either": don't threaten me, Friday - you're not entitled to bulldoze those who do not agree with you out of the way like that. ➨ ЯEDVEЯS looks at danger and laughs his head off 19:29, 20 May 2008 (UTC)
Did I interpret "I am willing to undo any indefinite block" incorrectly? That's what you were "me too"ing, right? I'm not trying to threaten anyone (with what?!?) but you're not entitled to interfere with those trying to solve an ongoing problem, either. Those who keep unblocking BC are a big part of the problem here. You've had plenty of time to try your "let him off no matter what" approach, and we can all see how well it works. Don't continue to be part of the problem. Friday (talk) 19:42, 20 May 2008 (UTC)
Please consider that some people might think your assertions above mean that if you're not part of this lynch mob, you're not welcome to be involved. Telling people who do not agree with you that they are interfering with what you are attempting to do is a travesty of our consensus government and you should be ashamed. ➨ ЯEDVEЯS looks at danger and laughs his head off 19:48, 20 May 2008 (UTC)
I'll just say that Demon did not accurately paraphrase what we have writte on community ban. It sort of suggests that if just 1 admin out of 1,500+ would unblock a candidate, a community ban can never exist. This is not what the policy says. Rather, what I think Demon and Redvers are suggesting, is that there simply is not a consensus to impose a community ban, therefore if an admin imposed one, they would undo it. Correct me if I am wrong. Gwynand | TalkContribs 14:52, 20 May 2008 (UTC)
Is there some confusion here with a de facto community ban, which exists when no admin is willing to unblock, as opposed to a community ban which is effected by consensus of the community? Franamax (talk) 20:06, 20 May 2008 (UTC)

I don't think I agree with the application of the "I would unblock" rule in this situation. See my thoughts expressed in a lame graph here: http://img166.imageshack.us/img166/1953/banningza1.jpg Cheers, Daniel (talk) 15:08, 20 May 2008 (UTC)

A community block is block that imposed per consensus of a majority of the Wikipedia community (I say majority because obviously not every user would participate or possibly be even aware of such a situation). That consensus imposes the block and cannot be lifted without another consensus to lift the block. Yes it works both ways, in case you weren't aware. As said above, just because one or two admins, out of however many hundreds or thousands there are, does not agree to the ban and is willing to unblock a user, that does not mean they can override the block or that it cannot indeed exist. That is not how
:.
16:33, 20 May 2008 (UTC)

Let's just all be exactly clear about this. What you demon and presumably Redvers are saying, that no matter the arguments made in discussions like this[75], you would always unblock beta. Why? Just put some thoughts here that illustrate why you would go against the well put and endorsed thoughts of Durova, just so we can adequately assess just how deadlocked the 'community' is with regards Beta and any further violations, because as sure as eggs is eggs, and based on his own actions and statements, change in his attitude or behaviour is not coming, and never will, and good will banked by NFCC tagging is being extended indefinitely. Similarly, any actual actionable incidents are clearly going to continually be treated in isolation despite repeat final warnings, as seen by the above proposal, and even worse, any subsequent blocks thus recieved are actualy watered down, rather than be increased, as happens with other persistent repeat offenders. Even even worse, people have completely ignored beta's apparent solution to all this, to dissapear, and run unapproved bots on user accounts. With comments like this section, I can only see one outcome, an extension of the second arbcom case to force the standards and expectations already stated, to actually be linked to real and descriptive consequences, and to take the issue of how to deal with beta out of the community's hands altogether. MickMacNee (talk) 17:31, 20 May 2008 (UTC)

Although I am an admin and I personally oppose a community ban (and at this stage anyway I seriously doubt one would get off the ground), I would make the general comment that in my view threats or indications of future action are unhelpful. If a process goes to the conclusion and people war it just because it meets their personal definition of "wrong" rather than some objective standard, they're making a rather big statement of how they see their own role with respect to the community, and how they see the community's expressed views. Regrettably I think it's going down the ArbCom road again, although what good it will do I have no idea given that we're still arguing over enforcing the last one. Orderinchaos 18:02, 20 May 2008 (UTC)
The lack of action was apparently down to no the case not having anything to 'enforce'. I requested clarification here [76], as well as at ANI at the time of a beta civility alert 5 days after the case closed, but there was no response to either. So the next step imo would be to extend case 2 to include enforcement, in light of beta's behaviour since the close of case 2. MickMacNee (talk) 18:44, 20 May 2008 (UTC)
There being nothing to enforce provides something of a clue as to why the calls for enforcement aren't working. The "punishment first, verdict later" idea has little merit. ➨ ЯEDVEЯS looks at danger and laughs his head off 19:29, 20 May 2008 (UTC)
We all already know you think there is nothing to enforce, but this is simply not the case. In fact your repeated one line assertions and silly links in light of pages of contrary views only support the case being made that community action is no longer appropriate for dealing with anything beta does. MickMacNee (talk) 20:38, 20 May 2008 (UTC)
But the ArbCom set precedent [77] that a sufficiently large number of edits is more important than adhering to ArbCom restrictions. BetaCommand has a very large number of edits, thus restrictions do not apply to him. -- SEWilco (talk) 18:42, 20 May 2008 (UTC)

Request that betacommand updates his user pages

Right now, beta is prevented from doing anything but a few tasks with betacommandbot for 30 days, so I would request someone requests beta to change the large WP:BITEY boxes on top of his talk pages here

User talk:Betacommand
, to actually reflect the current status. Their persistence there, despite beta not having done any image tagging for ages, might explain why some people in the above discussions were not even aware he has stopped doing this.

However, I would also point out, bar the current 30 day restriction, this appears to be by his own choice, and not through any official unapproval, [78]. Therefore, with a number of people proposing to monitor the bot's actions for this 30 day restriction, I would request that beta is also asked to update on the bot's user page User:BetacommandBot with what it is approved for for the 30 day period, and what it will still be approved for after that, i.e. an accurate summary of these pages [79] in regards to which he considers active and likely to be resumed after the 30 days. MickMacNee (talk) 18:37, 20 May 2008 (UTC)

Seems reasonable; I've always thought that they were a bit rude - but then I entered into dialogue with Beta :-) No, seriously, if they're BITey and inaccurate (worse, misleading), then they ought to come down pronto. That said, the bot info isn't essential to update IMO, that just creates un-necessary confusion.
I'm sure enough people are watching to make sure than no lines are overstepped, but I do SuPpORt with a capital 's', 'p', 'o' and 'r' the removal of the nasty talkpage templates. TreasuryTagtc 18:52, 20 May 2008 (UTC)


how about you take a look from my point of view, Im still getting questions that happen from edits BCBot made over a year ago. those notices clearly address 98% of all the common questions. Id rather not have to go back to being a broken record when those messages answer the questions.

βcommand 2
20:00, 20 May 2008 (UTC)

As someone who promised to do image work in his RfA and then was foolish enough to do some, I can plainly and completely vouch for Beta here. The FAQ at the top of his talk page is required, is sensible and is useful. It will cut down vastly the number of complaints he gets - and he will still get them, even if he never touched an image for the rest of his life. Anyone who works with Wikipedia image problems knows that it gets you stupid complaints, ad hominem attacks, death threats, legal threats, email bombs and threats of banning from powerless twerps with nothing better to do. And you get them for the rest of time. And that's after you put up an FAQ. If you don't have one, you might as well pin a $50 bill on your ass and scream "victim here, victim here!". And there are plenty of people trying to do that to him already. ➨ ЯEDVEЯS looks at danger and laughs his head off 20:11, 20 May 2008 (UTC)
Fair point actually; ongoing issues are... erm, ongoing. However, I do have some specific points to make. 1: "Read this talk page and its archives before registering your complaint" - it is unreasonable to realistically expect newbies who don't understand why they've been templated to read through over 50 pages of (let's face it) uninteresting dullness. 2: "I do not want to see images deleted" - asking for trouble; while I appreciate the point, it's going to cause more trouble than it's worth to say it! Could perhaps those points be actioned? TreasuryTagtc 20:16, 20 May 2008 (UTC)
the reason that #7 exists is because I always got those "you want all NFCC images deleted" messages, I dont want to see images deleted what I want is for all of our images to be compliant with policy, that means some will be fixed and others will need to be deleted, not delete all. As for the read the archives, at one point it pointed to a specific archive, not sure when/how that changed. as for your over 50 pages of (let's face it) uninteresting dullness the same could be said about our policy pages, people are still required to follow policy, even though its dull and uninteresting.
βcommand
20:45, 20 May 2008 (UTC)
True, but policy can be easily explained to a user if necessary, by templates or the first paragraph of the relevant policy page. If they require more technical details, then they can read deeper. Expecting users to wade through 50 pages of drivel before posting a simple (and tbh, frequently justified) question to a more experienced user, is totally unreasonable. What's more, no-one ever does. I bet you. Not one single four-day old account will have read each and every one of your talkpage archives - so why continue to have the notice there? TreasuryTagtc 20:51, 20 May 2008 (UTC)
It would be too long on my talk page, otherwise I would use the same (or similar) box. Especially since I am working again on
Wikipedia:Possibly unfree images and Wikipedia:Copyright problems. When dealing with copyright, you actually need something like that. Garion96 (talk)
20:31, 20 May 2008 (UTC)

I noticed about two since 1 April, from editors logging after months long absences from wiki, amongst what must be over a 100 non NFCC related queries. I seriously doubt these types of editors are ever assisted by the boxes, but more to the point I think you revel in the continued defence it allows, per Redvers above unsurprisingly, of your right to be incivil because you once chose to image tag, and the confusion in others as to whether you still do it. They always were a violation of BITE and POINT, but now they have no practical use they should be gone. MickMacNee (talk) 20:30, 20 May 2008 (UTC)

Brief comment and question from a non-relevant user

Hi. I usually find little interest in cases from ANI, however this one got me quite interested, mainly due to the "size" of this debate/boxing match. I also looked up previous cases as well, such as this user's arbitration case for bot abuse. At this point, my question is: if this user was me and did not have all that power (or priviledge as many here like to call it), how long would it take to ban him? In other terms, would I, for example, be able to get away with this? Do you? yes...|or no · 01:24, 22 May 2008 (UTC)

  • Would you (or almost anyone else) be able to get away with incessant incivility, disruptive bot edits, sockpuppetry, biting newbies, running a bot on your main account without authorization, and repeating most of the above after an arbcom case told you not to? In a word: no. 166.128.57.118 (talk) 04:29, 23 May 2008 (UTC)
That, sadly, is actually one of the clearest summaries I've seen of the problem. Orderinchaos 20:22, 23 May 2008 (UTC)

Now that we've talked it to death...

...what, exactly, have we decided to DO???

Gladys J Cortez
14:56, 24 May 2008 (UTC)

Nothing. What can be blocked is blocked and there are admins willing to unblock the main account so this needs to go back to ArbCom if you want him banned.
talk
) 15:14, 24 May 2008 (UTC)
Well, I'm not sure where you got the idea that I, personally, want him banned; I just wanted to know what was the result of all that sound and fury.
Gladys J Cortez
17:55, 24 May 2008 (UTC)
Sorry I was being unclear. I mean those advocating a ban.
talk
) 17:59, 24 May 2008 (UTC)
An arbitration request has now been filed so nothing further is going to be achieved here.
talk
) 18:10, 24 May 2008 (UTC)

Requiem

By my highly unreliable count, in the above thread 66 editors made an indication of !voting. 48 commented on the ban, 40 on the Sam Korn solution, 20 on both. (I'll leave that discrepancy of two as an exercise for the reader). ;) Of the 48 commenting on the ban, 8 for, 36 against, 4 neutral - a pretty clear indication. Of the 40 commenting on Sam Korn's remedy, 34 for, 1 against, 5 neutral. I submit that the community has made its wishes clear. Sam has well expressed the community sentiment, combine that with Durova's earlier proposal, which also gained approval - there is a way forward which doesn't have to include ArbCom. Franamax (talk) 23:46, 24 May 2008 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Secret Pages

Hihi...wondering if we can start talking about these Secret Pages things. I was wandering around New Pages and saw a strange user subpage, so I followed...this user is building a HUGE (like 20 or 30 pages) sub section of his page as a 'maze' that you wander through to earn a Barnstar. I looked into the history and saw that he'd made a couple of edits and then found someone else's secret page and after that, nearly all of the WP contributions were to his own secret pages. I don't think any of us wants to be the jerk that tells people to stop having fun on WP, but at what point does this help the project? It seems like there are bunches of these things out there...are we getting so big now that we just have to let the kids be kids as long as they aren't disrupting the article side? It's not like the "you have new messages" prank that made people actually think they had WP business to deal with...Any thoughts/ideas? Its frustrating when you see someone putting that much thought into a game you wonder what they could do with an article! Anyway...feel free to tell me to go away if this isn't something that anyone else is worried about. LegoTech·(t)·(c) 16:50, 23 May 2008 (UTC)

Apparently you've missed the drama, which is a plus for you Legotech! There have been several discussions about this recently. Check MFD, check the ANI archives, the AN archives, then the other DRV.....if you want links I'll get 'em. Generally, it was determined that secret pages are the purest form of evil incarnate. And also ironically, harmless. Very deletable, also very non deletable. Complete wastes of time, and also helpful and fun. A big fat no consensus that ended in a resounding Meh. if I recall...Keeper | 76 | Disclaimer 17:03, 23 May 2008 (UTC)
Found the most pertinent link anyway, here. Happy reading! Warning:According to the Surgeon General, reading that MfD may cause premature death by drinking, random twitches and other seizure-like behavior, and a general sense of hopelessness. Also, may cause birth defects in unborn fetuses, even if you're not pregnant. Just random unborn fetuses. Keeper | 76 | Disclaimer 17:08, 23 May 2008 (UTC)
So was it just coincidence, or an act of the
cabal to have Secret close the discussion about Secret pages? In either case, the matching of actor with topic brought a smile to my face. -- llywrch (talk
) 18:13, 23 May 2008 (UTC)
Repeat after me Llywrch.... 19:15, 23 May 2008 (UTC)
Yeah, there are legitimate differences of opinion. The best that can be said for such stuff is that it might be a honeypot (computing) for the kiddies who would otherwise be running amok, touching important things like articles. The worse that can be said for such stuff is that as long as we're content to let children play here, we'll continue to attract children. It'd be best if Wikipedia were seen by these children as boring, rather than as a fun myspace-like place to play. If this userspace nonsense attracts children and keeps them out of the way, it's a bit like a bug zapper- sure, it zaps bugs, but it attracts them too. So, does it do more harm than good? I see no clear answer to that quesiton. Friday (talk) 17:10, 23 May 2008 (UTC)
[ec]Here is the relevant ANI thread on the subject. If my brain is working right, it seems that the general idea was to look at these things on a case-by-case basis as there is such a wide variation in their style and content. My opinion: generally pointless but harmless, the particularly egregious/complex/sprawling ones should be deleted.
Ɣ ɸ
*** 17:12, 23 May 2008 (UTC)

Wow, interesting reading! I went back to the one that sparked this interest and the last 100 contributions for this user are JUST the secret pages and his userpage. I don't want to call him out in public tho...and I'm not sure how to approach without him getting really upset about it...maybe someone could drop me an email and I'll point them to the user? LegoTech·(t)·(c) 18:07, 23 May 2008 (UTC)

While
WP:NOT#HOST. I say we delete the maze and block the user if he persists, this isn't his personal playground. TreasuryTagtc
18:17, 23 May 2008 (UTC)
Hmmm...perhaps a friendly note on the user's talk page first, asking why/what they intend to do with them would work. However, given that they are the user's first contributions and that they created 30+ of them... delete the lot and warn the user about MySpace-y behaviour. There are *** 18:54, 23 May 2008 (UTC)
And also perhaps a reminder about what barnstars are and how giving them out for this tarnishes their value. --
talk
) 22:46, 23 May 2008 (UTC)
Completely agreed, bainer. Barnstars are explicitly not earned, they are received, and unexpectedly at that. Once they are "earned", they've completely lost their value. I've seen the "Original Barnstar" severely misused. Keeper | 76 | Disclaimer 01:09, 24 May 2008 (UTC)
Legotech, any word on the secret pages? Have you managed to contact the user? If you want me to do it [you mentioned above that you weren't sure how to go about it] you can
Ɣ ɸ
*** 17:30, 24 May 2008 (UTC)