Wikipedia:Administrators' noticeboard/IncidentArchive1175

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 363 364 365 366 367
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 1159 1160
1161 1162 1163 1164 1165 1166 1167 1168 1169 1170
1171 1172 1173 1174 1175
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 485 486 487 488 489 490
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 335 336 337 338 339 340
341 342 343 344 345 346
Other links


Concern About a New Contributor

The following discussion 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.


Kriji Sehamati (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Dear Wikipedians,

I hope you’re doing well. I wanted to inform you about a new contributor @Kriji Sehamati, despite lacking experience, has repeatedly attempted to vandalize multiple articles. These articles were properly aligned with Wikipedia’s guidelines and reviewed by experienced contributors, but he/she seemed unwilling to understand or respect their adherence to the policies.

I believe your experience could help address this situation effectively.

Looking forward to your advice on how to proceed.

Thankyou! 𝒮-𝒜𝓊𝓇𝒶 15:21, 23 December 2024 (UTC)

"Vandalize" is a very loaded word here with a specific meaning. As far as I can tell, what they've done is nominate 4 articles for deletion, and your response has been to accuse them of vandalism, ignoring dispute resolution procedures and making personal attacks – none of which I can see at a glance through their contributions.
Perhaps if you supplied evidence of this behaviour, someone would be able to help? If your issue is that they've nominated 4 articles of which you are a major contributor and are doing so by going through your contributions in order to find articles to nominate for deletion with specious reasons, then this board would be the place to come. If not, then making your arguments for keeping the articles on the AfDs in question would be your best bet.
By the way [1] [2] [3] [4] is forum shopping. Stop that. 81.2.123.64 (talk) 16:06, 23 December 2024 (UTC)
(ec) This is an odd one. As S-Aura failed to provide diffs, I looked at Kriji Sehamati's contribution history. New account (9 Dec) began editing today, created two drafts and made a bunch of edits to those. Then began adding COI tags to articles S-Aura wrote, nominated those articles for deletion, and then left a possible UPE template on S-Aura's talk page. Really seems to be something weird going on here between those two. (In addition to opening this ANI thread, S-Aura asked for help with basically the same message on the talk pages of Ipigott, Ryan shell, CFA, and BusterD, and S-Aura opened same complaint at AN.) Schazjmd (talk) 16:06, 23 December 2024 (UTC)
I am concerned that User:Kriji_Sehamati’s actions, including unjustified deletion nominations and spamming, are disruptive and violate Wikipedia’s guidelines.
She seems to lack understanding of basic Wikipedia guidelines, particularly those related WP:GNG and WP:NPOL. 𝒮-𝒜𝓊𝓇𝒶 16:40, 23 December 2024 (UTC)
You were asked to provide diffs. You did, almost, here but then reverted yourself. Those diffs (well, the ones before those diffs) are just the other user nominating articles for deletion (which is allowed) or tagging them for what they believe to be conflict of interest edits (which is also allowed).
Please provide some actual evidence that the other user is engaging in chronic, intractable behaviour, rather than just not editing how you would like them to. 81.2.123.64 (talk) 17:21, 23 December 2024 (UTC)
Here are some diffs highlighting her problematic edits. However, I believe that many of her contributions may be in violation of Wikipedia’s guidelines. It appears she has specifically targeted me and added the COI tag multiple times to the same page. I would appreciate it if you could review her actions more thoroughly:
[5]
[6]
[7]
[8]
and many more
Thankyou! 𝒮-𝒜𝓊𝓇𝒶 17:33, 23 December 2024 (UTC)
We wouldn't generally treat an AfD as vandalism. Simonm223 (talk) 17:39, 23 December 2024 (UTC)
I understand your point about AfDs not generally being treated as vandalism. However, I noticed that the major contribution history of the user seems suspicious. 𝒮-𝒜𝓊𝓇𝒶 17:42, 23 December 2024 (UTC)
Not from where anybody else is standing so far. I get that you're upset to have four articles of yours nominated for deletion, and if you have any evidence at all that you are being deliberately targeted by the other editor, then people will very much act on that. Please provide it. 81.2.123.64 (talk) 17:58, 23 December 2024 (UTC)
I am here to contribute and edit articles in accordance with Wikipedia’s guidelines. However, today a new user targeted me and falsely blamed me for actions that are not accurate. I believe this is unfair and not in line with the collaborative nature of the platform. 𝒮-𝒜𝓊𝓇𝒶 18:04, 23 December 2024 (UTC)
Please provide evidence of this. 81.2.123.64 (talk) 18:06, 23 December 2024 (UTC)
Please check! [9] 𝒮-𝒜𝓊𝓇𝒶 18:07, 23 December 2024 (UTC)
The articles that have been nominated for deletion discussion have been reviewed by experienced contributors. These discussions involve articles about judges and lawyers, under WP:NPOL, a valid criterion according to Wikipedia’s guidelines. Therefore, the deletion decision was made after carefully reviewing these articles. 𝒮-𝒜𝓊𝓇𝒶 18:11, 23 December 2024 (UTC)
Honestly it looks like this user, rightly or wrongly, believes you have a conflict of interest and are acting on the basis of that assumption. I would suggest, if you don't have a CoI, talking to them about this and maybe asking why they've come to this conclusion. Simonm223 (talk) 18:10, 23 December 2024 (UTC)
They have just started targeting my contributions, and I tried to inform her about the situation. However, she is acting as if she knows everything about Wikipedia and is dismissing my concerns. 𝒮-𝒜𝓊𝓇𝒶 18:15, 23 December 2024 (UTC)
@Kriji Sehamati: hasn't edited since their AfD spree earlier today, let's wait and see what their response here is when they return to editing. Schazjmd (talk) 18:16, 23 December 2024 (UTC)
  • We need to stop focusing on the OP's calling this vandalism; it is not. I've changed the header to reflect that. That said, the new user's edits are problematic and merit scrutiny. As for the UPE stuff, I've removed that post from the OP's Talk page; it's nonsensical coming from a new user and does not merit a response.--Bbb23 (talk) 18:42, 23 December 2024 (UTC)
  • It is, of course, not vandalism to nominate articles for AFD discussions as long as a legitimate deletion rationale is provided and the article hasn't just been discussed at a recent AFD. However, I don't think it's a good sign when a brand new editor claims to understand all of Wikipedia policies and whose first actions are to nominate articles at AFDs. They are almost never an actual new editor, especially when they know how to even set up an AFD or are familiar with using Twinkle on their first day of editing. Liz Read! Talk! 19:34, 23 December 2024 (UTC)
    It seems that she is not new to Wikipedia and might be operating multiple accounts. It appears she has an issue with one of my contributions, as she created her account just 15 days ago, yet she already has a good understanding of tools like Twinkle and AfD procedures. This level of familiarity suggests prior experience on the platform. I am now requesting her account to be blocked as I am completely disturbed by her repeated allegations and disruptive behavior. 𝒮-𝒜𝓊𝓇𝒶 11:32, 24 December 2024 (UTC)
    I am now genuinely confused—if all my contributions are not good, then why am I even here? Were the experienced editors who reviewed and approved these pages also mistaken? A newcomer, who joined just recently, is now disrupting and questioning the validity of all the work that has been carefully reviewed and maintained by experienced contributors. This situation is deeply discouraging. 𝒮-𝒜𝓊𝓇𝒶 11:58, 24 December 2024 (UTC)
    Please resolve this situation—either block her for her disruptive behavior. How can i continue working under such constant targeting and stress ? 𝒮-𝒜𝓊𝓇𝒶 12:00, 24 December 2024 (UTC)
    User:S-Aura, you seem to be making unsupported personal attacks against User:Kriji Sehamati. You should provide specific evidence of wrongdoing, including diffs, or your arguments here will fall on deaf ears (and bring consequences for you). Meanwhile, as a filer on ANI, you have brought all your own edits to close scrutiny by the community. You may have to face that smart people disagree, and this is how we sort disagreements out on English Wikipedia. You are not required to edit, but we encourage you to do so. Nobody is going to block Kriji Sehamati at this point, because you've given us no reason to do so. BusterD (talk) 12:01, 24 December 2024 (UTC)
    Meanwhile, in the last few minutes S-Aura has disruptively created a second thread about this exact issue on this same board, which was reverted by another editor. This is intentional disruption. BusterD (talk) 12:07, 24 December 2024 (UTC)
    As to the question "Why am I here?", poets and artists have been trying to answer this question for eons. Epistemology is outside the scope of this board, but there are articles about it. Show up to edit if you want to, but expect disagreement from time to time. (That's actually a sound answer to any epistemology question as well.) BusterD (talk) 12:16, 24 December 2024 (UTC)
    Dear @BusterD,
    It means I have been proven wrong, and that user’s contributions have been more focused on me, which is quite insufficient to catch someone’s lie that she is pretending to be new, when in fact she is old.
    Also, I am not against AfD; I am simply expressing my opinion. 𝒮-𝒜𝓊𝓇𝒶 13:12, 24 December 2024 (UTC)
    Could you please rephrase your point here? I don't understand. While it's okay to be suspicious that this editor is somehow socking or doing something else deceptive due to the familiarity, it seems unacceptable to deliberately accuse them of such repeatedly without firmer evidence. Remsense ‥  13:19, 24 December 2024 (UTC)
    Dear @Remsense,
    I am not engaged in paid activities on Wikipedia, and she claimed that I am connected with the subject, who is a judge, lawyer, etc. You all should understand that this is not a trivial matter; justice is a very respected position. Making such allegations can escalate court cases. I would like to remind you of the Wikipedia vs. ANI case. 𝒮-𝒜𝓊𝓇𝒶 13:24, 24 December 2024 (UTC)
    One thing you need to understand immediately is you should never make another post that sounds vaguely like a legal threat, as you've just done above. Seriously. That intonation is seriously not helping us decide who's right or wrong here. Remsense ‥  13:27, 24 December 2024 (UTC)
    Okay! 𝒮-𝒜𝓊𝓇𝒶 13:35, 24 December 2024 (UTC)
    I will caution you that this is tiptoeing right up to the edge of WP:NLT and you'd be advised to avoid making legal threats. Simonm223 (talk) 13:28, 24 December 2024 (UTC)
    Dear @Simonm223,
    I am merely showing that she can potentially do something inappropriate. I am following the guidelines and not making any legal threats. 𝒮-𝒜𝓊𝓇𝒶 13:31, 24 December 2024 (UTC)
    Accusing another editor of potentially making legal threats is not much better, when there is no concrete evidence that they would do so. Being interested in articles about judges does not suffice. Remsense ‥  13:32, 24 December 2024 (UTC)
    The page of Justice Subramonium Prasad, who had conducted over the Wikipedia vs. ANI court hearing, was also created by me. 𝒮-𝒜𝓊𝓇𝒶 13:28, 24 December 2024 (UTC)
    State plainly what the implication you are making here is, because what I'm hearing is "I'm familiar with people who have hit Wikipedia with a mallet in court before, and I can make sure it happens again". Remsense ‥  13:30, 24 December 2024 (UTC)
    This is becoming a rabbit hole. I urge you not to pursue the rabbit further. BusterD (talk) 13:33, 24 December 2024 (UTC)
    Good call, I'll retract the above. Remsense ‥  13:34, 24 December 2024 (UTC)
    No, that is not what I am implying. 𝒮-𝒜𝓊𝓇𝒶 13:33, 24 December 2024 (UTC)
    No one has said your contributions are not good. However, it should be noted that a draft being accepted at AfC or a new page having been patrolled does not guarantee greater scrutiny would not result in a valid AfD nomination. That said, echoing others here it's clear something problematic is up with this user's behavior. Remsense ‥  12:02, 24 December 2024 (UTC)
    You can't both criticize someone for lack[ing] understanding of basic Wikipedia guidelines, particularly those related WP:GNG and WP:NPOL, and then argue that she is too familiar with the platform to be a newcomer for knowing how to file an AfD. I wouldn't be surprised if most people here knew how to file an AfD before knowing all 14 notability guidelines by heart. Chaotic Enby (talk · contribs) 12:59, 24 December 2024 (UTC)
    There are detailed instructions on filing an AfD that can be found by googling "how can I get a Wikipedia page deleted" - if somebody had some personal reason for wanting to have pages removed it doesn't strain credibility to think that's why they created a WP account and that they just followed the very clear instructions on the appropriate pages.
    In fact that might explain why some of the AfD filings were reasonable and some were, on their face, incorrectly filed. If you looked up the AfD process but not criteria that is the likely outcome. That's why I find the "new user files AfDs must be a sock" idea here somewhat uncompelling. Simonm223 (talk) 13:04, 24 December 2024 (UTC)
  • I believe we're entering boomerang territory at this point. Opinions? BusterD (talk) 13:35, 24 December 2024 (UTC)
    I think OP is upset that a cluster of their articles were put up at AfD. This in itself is understandable, but while there's reason to think there might be mischief by Kriji Sehamati, we don't have any real evidence of it. We either need the OP to make it clearer what misconduct, if any, has occurred, or they need to drop the stick. Remsense ‥  13:37, 24 December 2024 (UTC)
    The OP has been intentionally disruptive (by creating a new ANI thread which was reverted), and this thread is going nowhere. IMHO, there's nothing ANI can do here. Everything I'm reading about should be resolved at the page talk and user talk level, in my opinion. The AfDs are underway. If dispute resolution is needed, fine. Nobody is harming S-Aura. S-Aura can't come crying to ANI (or four random user talk pages like mine) anytime someone merely disagrees with them. BusterD (talk) 14:08, 24 December 2024 (UTC)
    I'd have said close with trout for all if not for creating the second thread at AN/I. Based on that I'd say the OP should be formally cautioned against such antics in the future. Simonm223 (talk) 14:10, 24 December 2024 (UTC)
    I should have added that I largely hold with Remsense in their position. BusterD (talk) 14:15, 24 December 2024 (UTC)
    User:Kriji Sehamati‬ is definitely a sock puppet on Wikipedia, but we don’t have any evidence because understanding Wikipedia’s AfD process so quickly can be a bit challenging. I have no problem with AfD regarding my contributions, and it’s a good thing that experienced contributors are giving their feedback. If you believe that the kriji is 100% correct and her activity is not suspicious, then this discussion should be closed. 𝒮-𝒜𝓊𝓇𝒶 14:27, 24 December 2024 (UTC)
    You need to stop insisting this is definitely the case if you don't have any evidence for it, period. Remsense ‥  14:28, 24 December 2024 (UTC)
    S-Aura, how did you make the determination User:Kriji Sehamati‬ is definitely a sock puppet on Wikipedia? Please share your process. That's a personal attack, and requires proof to prevent you from being in violation of WP:NOPERSONALATTACKS. I've looked at the AfDs and they seem reasonable to me. When you've provided strong sources the article is being kept. So far the jury is out on the others. Both of you seem to be writing articles about obscure living persons who wouldn't normally (by my cursory reading) have a Wikipedia article about them because reliable sourcing is not readily found. When I see that, I must suspect COI or undeclared unpaid editing here, but nobody's admitting to it. BusterD (talk) 15:05, 24 December 2024 (UTC)
    S-Aura's continuing to issue personal attacks makes it more difficult for us to just close this (without some form of consequence for the editor making unproven personal attacks after they've been warned repeatedly). BusterD (talk) 15:08, 24 December 2024 (UTC)
    I have made a level-four user talk page warning for the personal attack. FYI. We've been very nice about this up 'til now, but we need to stop being so kind. Doing foolish things has real world consequences. BusterD (talk) 15:17, 24 December 2024 (UTC)
  • Both editors' apparent use of AI is certainly disruptive. If it continues, it should lead to blocks. C F A 15:10, 24 December 2024 (UTC)
    No personal hate intended, but I just found this and thought it would be worth checking.[10] 𝒮-𝒜𝓊𝓇𝒶 16:49, 24 December 2024 (UTC)
    It would be nice if you could explain the significance for those who do not speak Hausa. Remsense ‥  16:51, 24 December 2024 (UTC)
    She had made contributions to pages in other languages a few months ago. I am attaching her contributions link.[11] 𝒮-𝒜𝓊𝓇𝒶 16:59, 24 December 2024 (UTC)
    How does this constitute evidence of sockpuppetry if we aren't to know what exactly happened? There's a reason we don't just automatically block anybody who is blocked on another language wiki, and I looked through the edits some and didn't find anything outrageous that made it past the language barrier. Remsense ‥  17:01, 24 December 2024 (UTC)
    I agree that it’s important to ensure we have solid evidence before making conclusions. I appreciate your perspective on not automatically blocking users based on blocks from other language wikis. 𝒮-𝒜𝓊𝓇𝒶 17:17, 24 December 2024 (UTC)
    Please don't reply to me or others using ChatGPT. It is flat-out rude. Remsense ‥  17:18, 24 December 2024 (UTC)
  • Support BOOMERANG - I've been uninvoled and have mainly just been watching the back-and-forths, but the personal attacks and VESTED mindset, such as "questioning the validity of all the work that has been carefully reviewed and maintained by experienced contributors", concerns me. Not sure for how long, but I don't think anything longer than a months is appropriate given the circumstances. EF5 15:47, 24 December 2024 (UTC)
  • This whole thread, but especially the 16:49, 24 December 2024 (UTC) comment, feels like the OP is just throwing literally everything at the wall to see what sticks. But, worse, what is being thrown at the wall lacks any significant body of evidence to support. I note that a personal attack warning has been given for the continued unfounded accusations being presented, which I think is a good move. I don't support a block at this point, although if I was the OP I would withdraw this complaint and/or drop the stick and walk away from this topic as a matter of urgency to avoid continuing to make the situation worse. Daniel (talk) 17:41, 24 December 2024 (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.

Lil Dicky Semi-Protection

The following discussion 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.


Lil Dicky was semi-protected back in 2019. Now that five years have passed, could the semi-protection be lifted? 174.93.89.27 (talk) 16:25, 24 December 2024 (UTC)

Ask at WP:RFPP EvergreenFir (talk) 16:28, 24 December 2024 (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.

Potential vandal trying to start edit war on the page for Frisch's.

The following discussion 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.


This user keeps using IP addresses in order to revert creditable information about who makes their tartar sauce. Please look into this user. IP Addresses used were 67.80.16.30, 66.117.211.82, and 216.24.107.180. — Preceding unsigned comment added by JrStudios The Wikipedian (talkcontribs) 15:17, 24 December 2024 (UTC)

Courtesy link Frisch's. Knitsey (talk) 17:02, 24 December 2024 (UTC)
This sounds a lot like the same edit warrer I dealt with on Redbox, down to the false accusations of vandalism, removal of sourced information, and apparent use of proxies (all the IPs geolocate to different places). I wouldn't be surprised if this is the same person. I've asked RFPP to intervene. wizzito | say hello! 21:05, 24 December 2024 (UTC)
NVM, checked MaxMind for geolocation and they all are in the same general area. wizzito | say hello! 21:08, 24 December 2024 (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.

Disruptive editing by User talk:185.146.112.192

The following discussion 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.


The User talk:185.146.112.192 is engaging in disrupte editing. Neither does this IP provide sources and is POV pushing. And this IP has been warned multiple times for this on his/her talk page.

Moroike (talk) 20:52, 18 December 2024 (UTC)

@Moroike: It looks like you both are edit warring on Kichik Bazar Mosque.[12][13][14][15] That's not particularly helpful, so you should try to have a discussion on the article talk page as to whether you should include the Talysh language name for the article in the lead/infobox. –MJLTalk 20:33, 19 December 2024 (UTC)
MJL why and how did you pick out that one article over the many this IP has made recent changes to? The IP has been making disputed edits for months and has been reverted by a number of editors, not just Moroike. CMD (talk) 01:10, 22 December 2024 (UTC)
@CMD: I am not suggesting that the IP editor isn't being disruptive, but my point is that Moroike isn't making the situation better (using the example of that one article). You can see this by looking at their last 50 contributions where they have mostly just reverted this editor without using a summary. –MJLTalk 18:02, 23 December 2024 (UTC)
The IP's edits were removed a total of 13 times on the page regarding the capital city of Azerbaijan, Baku. You can't let him continue engaging in further edit wars with other users besides Moroike, can you? Nuritae331 (talk) 17:24, 23 December 2024 (UTC)

Since this IP user won't stop and is stonewalling, either he/should be temporarily blocked, or all the pages he is POV pushing without sources, should be semi-protected, so that only registered users can edit them. Moroike (talk) 21:37, 23 December 2024 (UTC)

After he/she was blocked for 24 hours, this IP created an account as User talk:Ibish Agayev in order to evade the block and has resumed his/her POV pushing. Moroike (talk) 16:51, 24 December 2024 (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.

Request to warn a user otherwise block request

Socking editor. Nothing to see here. - The Bushranger One ping only 04:52, 28 December 2024 (UTC)
The following discussion has been closed. Please do not modify it.

The following discussion 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.


This @Gheus Is making disruptive edits on different pages such as he made at Daily Dunya.He is placing deletion tags and is notability tags. The article is already has confirmed notability.This user did not stoped at this point he remove my warning from his talk page also and is removing content from other pages.I think please do some action Blirth (talk) 03:28, 28 December 2024 (UTC)

A quick cursory check seems to indicate that he is not being disruptive, but if anything editing contentiously but that is not prohibited. Looking at his AfD nominations, most of them are correct and consensus agrees with deleting or redirecting, instead of keeping most of the time -- although he does not get it correct every time. Rather it looks like you disagree, and when you brought it to his talk page once [16] he disregarded and deleted it asserting that you were the vandal [17]. It appears that he has a list of websites [18] that he considers promotional and likely is going about cleaning those up. Looking at Daily Dunya specifically, there is nothing intrinsically wrong with placing a AfD or Notability tags for this. Without looking into it much I would also question if this article meets GNG. Going beyond that article a quick look at his other edits also seem to be perhaps contentious but nothing that looks like vandalism, edit warring, or POV pushing. As such, this doesn't look like something for urgent admin intervention unless you have something more specific to reference. TiggerJay(talk) 04:09, 28 December 2024 (UTC)

This can be closed as the reporting user has been blocked for sockpuppetry. TiggerJay(talk) 04:47, 28 December 2024 (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.

Complaint by IPv6

Continued disruption by editor who refuses to drop the stick. - The Bushranger One ping only 00:28, 28 December 2024 (UTC)
The following discussion has been closed. Please do not modify it.

The following discussion 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.


A Wikipedia editor lied about me, https://en.wikipedia.org/wiki/User_talk:2A00:23C4:B3AE:3101:6463:27AE:4C80:E87B

I had complained about a editor, in the Alba Party article talk section, who claimed totally wrongly that I had compared someone to Holocaust deniers, I complained about that personal attack, and of course there was a pile on by the other editors on me, making horrible statements about me, I wont say which, but it is there to see Now on the talk page, I stated, a thank you to someone who came on defended me, and then The Bushranger a wikipedia editor came on to claim I was the one who had defended me. I did not. I find this allegation insulting, and am sure there will now be wikipedia editors on, who have another pile on. Shame on the lies about me, I did not do that, and shame on the horrible things they say about people who try to edit. I dont mind if you ban me from editing, the behaviour from the wikipedia editors is just atrocious — Preceding unsigned comment added by 2A00:23C4:B3AE:3D01:1470:CD88:4E1A:40F0 (talkcontribs)

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.

User:PlumberLeyland

The following discussion 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.



Could someone else please deal with PlumberLeyland, I feel a bit involved myself, not least because of the personal attacks ([19], User talk:PlumberLeyland/sandbox, [20]). If they say that sort of stuff to me, they'll one day say it to someone who actually minds. Thanks, --DoubleGrazing (talk) 12:41, 27 December 2024 (UTC)

Blocked indefinitely as a regular admin action. --Yamla (talk) 12:47, 27 December 2024 (UTC)
And TPA pulled. ScottishFinnishRadish (talk) 12:57, 27 December 2024 (UTC)
Thanks, both. -- DoubleGrazing (talk) 13:02, 27 December 2024 (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.

Persistent unsourced changes by IP

The following discussion 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.


2001:999:500:8D52:753A:9BD7:9D61:823B (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)

[21], [22], [23], [24], [25], etc.

Note that another IP in the same /64 range (2001:999:500:8D52:8065:5651:5389:18E (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)) was blocked for the same reasons less than a week ago. BilletsMauves€500 19:16, 26 December 2024 (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.

Suspected sockpuppet

The following discussion 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.


I've come across a user who I believe is a sockpuppet of a user who has been indefinitely block on Wikipedia. This is the user I suspect: https://en.wikipedia.org/wiki/Special:Contributions/Coop4883368638

I'm not sure if what I suspect is true, however I've found other accounts with the same editing habits as the user above. These are the users: https://en.wikipedia.org/wiki/Special:Contributions/Coop443535454, https://en.wikipedia.org/wiki/Special:Contributions/Coop40493, https://en.wikipedia.org/wiki/Special:Contributions/Coop2017

That's all the information I have to hopefully support my suspicions. Dipper Dalmatian (talk) 05:16, 27 December 2024 (UTC)

I'll ping User:Drmies since they blocked the other accounts. They probably have a better sense of whether or not this is the same editor. Right now, it seems like a username similarity at least. Liz Read! Talk! 05:29, 27 December 2024 (UTC)
WP:SPI 2001:8003:B16F:FE00:BCD0:5E51:7D5E:445D (talk) 10:05, 27 December 2024 (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.

Undoing my blocks due to collateral damage

The following discussion 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.


Hello, could an admin undo these blocks that I made? Blocks like these seem to have caused way more collateral damage than they're worth, per this message on an IP talk page (about a block I undid in October when I still had adminship) and this message on my talk page. Thanks! Graham87 (talk) 10:31, 26 December 2024 (UTC)

Ah, I've just done some checking, and it seems like, as ever, there's a template with unblock links. So here goes::

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.

Creating the need to make 400,000 unnecessary edits

Can we please dp something about editors who make unnecessary changes to widely-used modules, and then need to change 400,000 talk pages to get the same result we had before the change? Thanks to this change from last week, which removed the parameter "living" from the bannershell, we now have more than 400,000 pages in Category:Pages using WikiProject banner shell with unknown parameters. After the "cleanup" by User:Tom.Reding (and perhaps others), we will have the exact same result as we had last week, no new functionality, no new categories, no improvement at all, but a lot of flooded watchlists.

I tried to get him to stop at User talk:Tom.Reding#Cosmetic edits, to no avail. This isn't the first time, as you can see from that discussion. Fram (talk) 14:57, 20 December 2024 (UTC)

If you want to discuss {{WikiProject banner shell}}, you should do so at Template talk:WikiProject banner shell.
As for the size of the category, I have no plans to empty it, and was only going to update a few hundred more categories and templates.   ~ Tom.Reding (talkdgaf)  15:02, 20 December 2024 (UTC)
You made nearly 2000 of such edits in the last few hours, and when asked to stop pointed me to a category with 400,000 entries. I have no way to know how many more you planned now or in future runs. Starting a discussion at the module would hardly stop you. Fram (talk) 15:10, 20 December 2024 (UTC)
"when asked to stop pointed me to a category with 400,000 entries": incorrect. Since you wrongly thought I was making cosmetic edits, i.e. "no change in output or categories", the category was to inform you that they are not cosmetic.
Regarding a BRFA for the bulk of the category, that's looking more likely since the category appears to be neglected.   ~ Tom.Reding (talkdgaf)  15:29, 20 December 2024 (UTC)
Unnecessary removing a synonym and then making thousands of edits to remove the hidden cat created by that unnecessary change is not really any better than making cosmetic edits, the end result is that nothing has changed for the affected pages at all. Fram (talk) 15:33, 20 December 2024 (UTC)
Not unnecessary. The Lua code is very complex and removing the need the support various settings makes the code both easier to read and maintain. As always, editors that don't want to see these edits can hide these by hiding the tag "talk banner shell conversion". Gonnym (talk) 12:32, 22 December 2024 (UTC)
It doesn´t look as if the specific code to have these synonyms was very complicated though, the argument that in some cases two synonyms were used on one page with conflicting values was more convincing. And the edits I complained about did not have that tag, so no, even if people knew about hiding that tag, it wouldn't have helped here at all. Fram (talk) 16:04, 22 December 2024 (UTC)
This was discussed in detail on Template talk:WikiProject banner shell. Ideally these edits would be done by an approved bot so they do not appear on people's watchlists. The main benefit is to merge the |blp= and |living= parameters. When both are in use, we find they often get conflicting values because one gets updated and the other does not. — Martin (MSGJ · talk) 17:25, 20 December 2024 (UTC)
Isn't it more logical to first have a bot cleanup the unwanted parameter, then remove it from the template, and only then start populating the cat with the somehow remaining or since added instances? In any case, this is a typical bot task and shouldn't be done with massive AWB runs. Fram (talk) 17:39, 20 December 2024 (UTC)
Yes, probably. But we have this mechanism already set up and I assumed Cewbot would deal with these as part of its normal activities. Happy to look at other options - maybe discuss on template talk? — Martin (MSGJ · talk) 18:23, 20 December 2024 (UTC)
I don't know what this is about, but if the OP is correct, it is totally absurd to edit 400,000 talk pages for a tweak. Discussing at a template talk page monitored by those focused on the template would simply hide the issue. Johnuniq (talk) 03:53, 21 December 2024 (UTC)
Edits like these should always be bots, so they can be filtered from watchlists. There are numerous other editors who have recently engaged in the mass additional of categories to articles which I had to ask them to stop as my watchlist was flooded. GiantSnowman 13:02, 22 December 2024 (UTC)
Hiding bot edits from watchlists is not a viable option for many editors, since it also hides any non-bot edits that predate the bot edit (phab:T11790, 2007, unassigned). Users AnomieBOT, Cluebot III, Lowercase sigmabot III, Citation bot, et al edit with such high frequency that hiding their edits leads to an unacceptable proportion of watchlist items not appearing. (Also, Citation bot's edits should usually be reviewed, since it has a non-negligible error rate and its activators typically don't review its output, exceptions noted.)
The code for maintaining two aliases for one parameter cannot possibly be so complex as to warrant a half million edits. If one of the two "must" undergo deprecation, bundle it into Cewbot's task. If the values don't match, have the banner shell template populate a mismatch category.
In general, if a decision is made to start treating as an error some phenomenon that has previously not been a problem, and that decision generates a maintenance category with tens or hundreds of thousands of members, it is a bad decision and the characterisation of the phenomenon as "erroneous" should be reversed.
At minimum, any newly instanced maintenance task scoped to over a hundred thousand pages should come before the community for approval at a central venue. Folly Mox (talk) 15:19, 25 December 2024 (UTC)
Also, like, if only one of |blp= and |living= gets updated, shouldn't the net result be pretty obvious? Valid updates should really only go one direction. Folly Mox (talk) 15:24, 25 December 2024 (UTC)
Meanwhile, the category has grown to over 800,000 pages. Perhaps next time an RfC to determine whether creating such a large cleanup task is warranted, would be better? Fram (talk) 16:34, 24 December 2024 (UTC)
@Fram: this is logical. We should also make it a policy (or at least a guideline), something along the lines "if change would lead to edits/updating more than XYZ pages, a consensus should be achieved on a venue with a lot of visibility". Like Silver seren mentioned above, sometimes a formal consensus/discussion takes place, but it happens on obscure talk pages. —usernamekiran (talk) 14:01, 25 December 2024 (UTC)

North Korean involvement in Russian-Ukraine war discussion

The inclusion of North Korea as a belligerent in the infobox for the "Russian invasion of Ukraine" article has been a point of extensive and protracted discussion since September. A formal Request for Comment (RfC) on this matter ran for several weeks and was closed with a clear consensus to include North Korea as a combatant based on reliable sources and expert analysis. However, despite the closure, the discussion has continued unabated across multiple threads, with certain editors repeatedly rehashing resolved points and questioning the validity of reliable sources, leading to significant disruption.

Key Points:

  1. Prolonged Discussions and RfC Closure:
    • The RfC on North Korea's inclusion was conducted thoroughly, with a wide range of arguments presented by both sides.
    • The closing administrator, S Marshall, determined there was a clear consensus to include North Korea as a belligerent based on reliable sources and the strength of arguments.
    • The close explicitly allowed for reevaluation if new battlefield events or sources emerged, but no substantial new evidence has invalidated the prior consensus.
  2. Ongoing Disruption:
    • Despite the RfC's resolution, the same arguments are being repeated across multiple threads, often by the same editors.
    • This behavior includes undermining reliable sources, misrepresenting their content, and insisting on a higher standard of verification (e.g., requiring firsthand evidence of North Korean combat, which is unreasonable given the context).
  3. Reliable Sources Confirming North Korean Involvement:
    • Multiple reputable outlets, including the BBC, Reuters, and Pentagon statements, confirm North Korean military involvement and casualties in the conflict.
    • Experts from institutions like Chatham House and RUSI have explicitly stated North Korea's role in combat, aligning with the community's decision.
  4. Impact on the Community:
    • The continued disruption consumes editor time and resources, detracting from the article's improvement.
    • These actions disregard Wikipedia's consensus-building principles and guidelines for resolving disputes. This dispute has been ongoing for months, with multiple threads being opened and closed on the same topic.

Request for Administrative Action:

I respectfully request that administrators address the following issues:

  1. Enforce the consensus reached in the closed RfC, as no new evidence significantly alters the previous conclusions.
  2. Discourage editors from rehashing resolved discussions, particularly when arguments have been repeatedly addressed and dismissed.
  3. Consider imposing a topic ban or other appropriate measures on editors who persist in disrupting the article with repetitive or bad-faith arguments.

This matter has been discussed exhaustively, and it is essential to prioritize Wikipedia's goals of maintaining a high-quality, well-sourced, and consensus-driven encyclopedia. Thank you for your attention to this matter. UPDATE: I just noticed that North Korea was removed as a belligerent and added to the 'supported by' section, completely violating the consensus. Rc2barrington (talk) 08:48, 23 December 2024 (UTC)

Since this report isn't really about an incident and your request is directed towards admins, I think this complaint would be better placed at WP:AN rather than ANI. It will also need more specifics, which articles, which edits, which editors. You'll need to provide that. I also question whether or not these are content standards that the community can't handle on their own. Liz Read! Talk! 09:50, 23 December 2024 (UTC)
I was going to post it at WP:AN but it said: "This noticeboard is for issues affecting administrators generally – announcements, notifications, information, and other matters of general administrator interest.
If your post is about a specific problem you have (a dispute, user, help request, or other narrow issue needing an administrator), you should post it at the Administrators' noticeboard for incidents (ANI) instead. Thank you."
I posted it on ANI beecause my specific problem was this dispute Rc2barrington (talk) 12:07, 23 December 2024 (UTC)
The original post in this thread appears to resemble LLM output. GPTzero confirms this impression, rating text as "99% probability AI generated". Using AI to generate ANI submissions is highly inappropriate. Axad12 (talk) 18:01, 23 December 2024 (UTC)
Even when a message appears to be AI-generated, I think it is worth considering whether or not it is pointing out an actual problem. I think editors might be ignoring the results of an RFC, I just don't think asking for administrators to monitor a subject area, without identifying specific articles, is a feasible solution. It does seem like, possibly, a point that could come up in a complaint at AE regarding the Ukraine CTOP area. Liz Read! Talk! 19:55, 23 December 2024 (UTC)
I had a peek and it's a messy RfC and, as is generally the case with a messy RfC had a very involved closure message which seems to reflect that the closer felt constrained by the framing of the RfC. I didn't see any immediate indication in the edit history that anyone had tried to implement the RfC result and been rebuffed (although I might have missed it). So there's some smoke here but, I think, not a ton of fire. Simonm223 (talk) 20:21, 23 December 2024 (UTC)
Liz, I don't disagree but I'm not at all convinced that use of AI is a positive contribution to CTOP areas. Axad12 (talk) 20:27, 23 December 2024 (UTC)
It was written with AI assistance. Not all AI. ai detectors aren’t considered reliable, because you can put the U.S. constitution through one and it says 100% AI generated. Regardless, whether it’s AI or not has nothing to do with the topic. It’s just that there’a been so many discussions and when I checked the info box it said ‘supported by”, violating the consensus of the RFC Rc2barrington (talk) 12:45, 24 December 2024 (UTC)
you can put the U.S. constitution through one and it says 100% AI generated – Well, I just put it through GPTzero and got 97% human. Might be best if you don't just make up random "evidence". EEng 17:25, 25 December 2024 (UTC)
I think the underlying issue here is that if you use AI to generate text which looks like obvious AI output then readers will wonder "does the end user even have sufficient English to understand what the AI has generated for them?" and "did the end user understand the material prior to deciding to employ AI?". Thus if a user is fluent in English, as you obviously are, it will always be better to communicate in your own voice.
At the end of the day, a user making a valid point in their own voice is generally speaking going to be taken more seriously than a user employing LLM output.
There are plenty of other reasons for users not to employ AI (see the recent thread here [26] for extensive coverage) but the argument above seems like a good practical reason for fluent English speakers to always prefer using their own voice.
You will see from the recent thread that many users here are vehemently against AI use. Axad12 (talk) 15:46, 24 December 2024 (UTC)
I understood the material very well, its not like I just used 100% AI out of nowhere. I know the context. I have been involved in this discussion since September. Rc2barrington (talk) 16:43, 24 December 2024 (UTC)
It's a respect thing. It's disrespectful of other editors to make them read chatbot output rather than your words. Simonm223 (talk) 16:49, 24 December 2024 (UTC)
External videos
  Rc2barrington's appearance on Jeopardy
Rc2barrington's user page says This user believes in the bright future AI and robotics will bring, so there's probably no point in arguing here. However, I simply observe that in any kind of discussion where you're trying to convince other people, don't use a method that aggravates a significant number of readers (probably a significant majority of readers). It really is that simple. Axad12 (talk) 19:11, 24 December 2024 (UTC)

Putting the use of LLM aside, however you compose your message you should comply with the basics of ANI. This includes not making allegations without supplying evidence. This would normally be in the form of diffs but in this case just links might be fine. But User:Rc2barrington has provided none.

Probably because this is because their initial complaint appears to be unsupported by what's actually happening. They claimed "Despite the RfC's resolution, the same arguments are being repeated across multiple threads, often by the same editor". But where is this? I visited the talk page, and what I see is here Talk:Russian invasion of Ukraine#Post RFC discussion there was a request for clarification from the closer, something which is perfectly reasonably and which the closer followed up on. The OP then offered an interjection which frankly seemed unnecessary. There was then a very brief forumish discussion. To be clear, AFAICT no one in the follow up discussion was suggesting any changes to the article. So while it wasn't he most helpful thing as with any forumish discussion; it's hardly causing that much disruption especially since it seems to have quickly ended and also cannot be called "the same arguments" since there was no argument. No one in that discussion was actually suggesting changing the article.

Then there is Talk:Russian invasion of Ukraine#North Korea RFC aftermath discussion. There was again some forumish discussion in this thread which again isn't helpful but wasn't that long. But there was also discussion about other things like the name of the article and whether to restructure it. To be clear, this isn't something which was resolve in the RfC. In fact, the closer specifically mention possible future issues in a non close comment.

Next we see Talk:Russian invasion of Ukraine#Follow up to the previous discussion (Request for comment, can we add North Korea as a belligerent?). Again the main focus of the discussion is in how to handle stuff which wasn't dealt with in the RfC. There is a total of 2 short comments in that thread which were disputing the RfC which is unfortunate but hardly something to worry ANI about.

Next there is Talk:Russian invasion of Ukraine#Can we add a Supported by section for Ukraine in the infobox?. DPRK was briefly mentioned there but only in relation to a suggestion to change the infobox for other countries. No part of that discussion can IMO be said to be disputing the DPRK RfC. Next we have Talk:Russian invasion of Ukraine#Remove Belarus from the infobox. Again DPRK was briefly mention but only in relation to other countries. No part of that discussion can be said to be disputing the RfC. AFAICT, the only threads or comments removed from the talk page since the closure of the RfC was by automated archival. The only threads which seem to be post close are on Talk:Russian invasion of Ukraine/Archive 20 and none of them seem to deal with North Korea.

So at least on the article talk page I don't see what the OP has said is happening. The tiny amount of challenging of the RfC is definitely not something ANI needs to worry about. Even the other forumish or otherwise unproductive comments aren't at a level that IMO warrants any action IMO. If this is happening somewhere else, this is even more reason why the OP needed to provide us some evidence rather than a long comment without anything concrete, however they composed it.

Nil Einne (talk) 10:15, 25 December 2024 (UTC)

Disruptive behavior from IP

For the past month, 24.206.65.142 (talk · contribs · WHOIS) has been attempting to add misleading information to Boeing 777, specifically trying to use the unofficial "777-200LRF" designation beyond first mention in the relevant section and passing it off as official ([27], [28], [29], [30], [31], [32], [33], [34], [35], [36], [37]). Their behavior died down for a few weeks, but restarted several days ago ([38], [39]), including baseless claims that Fnlayson is "okay with it". They have been asked numerous times on their talk page to either stop or provide evidence of official use of the designation, but they have failed to do so and have continued their disruption. - ZLEA T\C 19:51, 24 December 2024 (UTC)

I forgot to mention that this user has used at least two other IPs; 24.206.75.140 (talk · contribs · WHOIS) and 24.206.65.150 (talk · contribs · WHOIS). 24.206.65.142 is the most recent to cause disruption. - ZLEA T\C 20:10, 24 December 2024 (UTC)

"777-200LRF" is not misleading, some cargo airlines do use that designation. Today I reverted to a previous version that User:Fnlayson was okay with [40][41]. I feel that User:ZLEA is going overboard with charges of misinformation and disruptive editing. 24.206.65.142 (talk) 19:59, 24 December 2024 (UTC)
It is misleading to remove any mentions of it being unofficial. Boeing has never made a "777-200LRF", no aftermarket conversion has ever been offered under that name, nor has the FAA or any other regulatory agency ever certified such an aircraft. To pass such a designation off as official is by definition misleading and misinformation. Likewise, to continuously do so after you have been told to stop by multiple people and falsely claiming that others support your arguments is by definition disruptive. - ZLEA T\C 20:06, 24 December 2024 (UTC)
Of note is the fact that this is not the first time the IP has claimed to have Fnlayson's support. They have been told before by Fnlayson not to assume support without a specific statement, yet it seems they've also ignored that. - ZLEA T\C 20:23, 24 December 2024 (UTC)
Its not misinformation as here are the sources which use "777-200LRF"[42][43], including GE Capital Aviation [44](the engine supplier for most Boeing 777) and Leeham News [45] (to avoid confusion with the upcoming 777-8F). 24.206.65.142 (talk) 21:06, 24 December 2024 (UTC)
I have asked you for sources from either Boeing or the FAA, yet you still either refuse to do so or (more likely) cannot because they don't exist. Only Boeing and the FAA can designate factory-built Boeing aircraft. Airlines and misinformed news websites have no authority to do so, and any alternative names they use are purely unofficial and should not have anything more than a single brief mention in the appropriate article section. Your failure or refusal to get that after numerous people have told you is disruptive. - ZLEA T\C 22:14, 24 December 2024 (UTC)
None of those are reliable sources suitable for sustaining the edit you want to make. #1 would only support that airline claiming to have that kind of plane. #2 is a model manufacturer, and #3 is a blog. — The Hand That Feeds You:Bite 18:37, 25 December 2024 (UTC)
Relevant range is 24.206.64.0/20 (block range · block log (global) · WHOIS (partial)), in case somebody needs it. wizzito | say hello! 21:02, 24 December 2024 (UTC)

User:24.187.28.171

The following discussion 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.


IP has been blocked before for previous infractions. Now, they continue to perform persistent disruptive edits contradicting the Manual of Style, either by deliberately introducing contradictions or undoing edits that resolve the issue. The user has also violated WP:DOB at Huntley (singer), though that remains unresolved for some reason. The IP has done all of this despite a backlog of warnings dating back to 2023. — Preceding unsigned comment added by EdrianJustine (talkcontribs) 22:48, 25 December 2024 (UTC)

@EdrianJustine: could you please provide specific diffs? voorts (talk/contributions) 23:23, 25 December 2024 (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.