Wikipedia:Administrators' noticeboard: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 656: Line 656:
::*:This same issue recurs on this noticeboard, indicating a significant problem. It is counterproductive to our goals of attracting good new editors to enhance content, rather than alienating them, and we should address it.
::*:This same issue recurs on this noticeboard, indicating a significant problem. It is counterproductive to our goals of attracting good new editors to enhance content, rather than alienating them, and we should address it.
::*:If the consensus has shifted, we should indeed update the terms "trivial" and "unconstructive" to better align with the current understanding, perhaps using a term like "unsubstantial." [[User:Marokwitz|Marokwitz]] ([[User talk:Marokwitz|talk]]) 22:35, 2 January 2024 (UTC)
::*:If the consensus has shifted, we should indeed update the terms "trivial" and "unconstructive" to better align with the current understanding, perhaps using a term like "unsubstantial." [[User:Marokwitz|Marokwitz]] ([[User talk:Marokwitz|talk]]) 22:35, 2 January 2024 (UTC)
::*::This war is maybe the most significant event in the conflict since ECR was instituted at [[WP:ARBPIA3#500/30]] almost 10 years ago. I don't have the stats but I wouldn't be surprised if these past few months have seen an all-time high for new editors in this topic area. I think that's why there is so much activity around ARBPIA ECR lately? <p>PGAME was written with [[WP:EC]] in mind, not [[WP:ECR]], and "gaming EC" isn't quite the same thing as (what we call) "gaming ECR". To take FoodforLLMs edits as an example, had FFLLM continued to add short descriptions after reaching EC, I don't think anyone would ever suggest they were "gaming EC." <p>PGAME is written with an intent requirement ("to raise your user access level"), and that kind of makes sense in relation to EC, but it doesn't necessarily make as much as sense for ARBPIA ECR. The difference is that PGAME is about preventing ''bad faith'' acquisition of EC--"gaming EC"--whereas ARBPIA ECR is intended to prevent bad faith and ''good faith but inexperienced'' editing in ARBPIA. So, in my view, for ECR, it doesn't matter if the editor's intent is to raise their user access level to edit ARBPIA. As I said in another EC revocation appeal thread, we ''want'' editors to make edits to raise their user access level, but even good faith editors may not make the "right" kind of edits for ARBPIA ECR (even if they are the right kind of edits for EC). That is what I think the documentation is lacking. <p>I am not in favor of a system, as SFR mentioned above, where admins gatekeep new editors in a topic area. I'm also not in favor of writing rules for admins to follow when it comes to EC revocation in ECR'd CTOPs--I think that's too restrictive and we're not going to do a good job of it. But I do think we should have an explanation about EC revocation in ECR'd CTOPs that does ''not'' suggest that EC is only revoked when there is "unproductive" or "trivial" or bad faith "to raise your user access level." I'm not sure exactly what the answer is, but it should be the answer to the question: if I registered an account today and I want to edit an ECR'd CTOP, what kind of edits should I make for the first month? And then an explanation that admins may revoke EC if the editors' edits aren't those kinds of edits. (I'm not sure if "those kinds" means "substantial" or "non-trivial" or what.) [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 02:11, 3 January 2024 (UTC)


== Closure request for "Inside Voices / Outside Voices" ==
== Closure request for "Inside Voices / Outside Voices" ==

Revision as of 02:11, 3 January 2024

    Welcome – post issues of interest to administrators.

    When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough.

    You may use {{subst:AN-notice}} ~~~~ to do so.

    Sections inactive for over three days are archived by Lowercase sigmabot III.(archivessearch)

    Open tasks

    XFD backlog
    V Feb Mar Apr May Total
    CfD 0 0 19 12 31
    TfD 0 0 0 0 0
    MfD 0 0 1 3 4
    FfD 0 0 0 3 3
    RfD 0 0 18 46 64
    AfD 0 0 0 0 0


    Pages recently put under extended-confirmed protection

    Report
    Pages recently put under extended confirmed protection (28 out of 7756 total) (Purge)
    Page Protected Expiry Type Summary Admin
    Comedy Shorts Gamer 2024-05-16 18:08 indefinite edit,move This subject is still on WP:DEEPER and the title blacklist and should not have a standalone article without approval through DRV Pppery
    ComedyShortsGamer 2024-05-16 18:06 indefinite edit,move Restore salt Pppery
    Template:Fl. 2024-05-16 18:00 indefinite edit,move High-risk template or module: 2585 transclusions (more info) MusikBot II
    Reform Zionism 2024-05-16 17:50 indefinite edit,move Arbitration enforcement WP:PIA Rosguill
    Progressive Zionism 2024-05-16 17:46 indefinite edit,move Arbitration enforcement WP:PIA Rosguill
    Nagyal 2024-05-16 17:42 indefinite create Repeatedly recreated Justlettersandnumbers
    British support for Israel in the Israel–Hamas war 2024-05-16 12:54 indefinite edit,move Arbitration enforcement: WP:AIPIA Malinaccier
    Neil Hartigan 2024-05-15 17:16 2025-05-15 17:16 edit WP:Sockpuppet investigations/Buzzards-Watch Me Work RoySmith
    Tad Jude 2024-05-15 17:16 2025-05-15 17:16 edit WP:Sockpuppet investigations/Buzzards-Watch Me Work RoySmith
    Minneapolis 2024-05-15 17:15 2025-05-15 17:15 edit WP:Sockpuppet investigations/Buzzards-Watch Me Work RoySmith
    Draft:CaseOh 2024-05-15 02:40 indefinite create Repeatedly recreated Dennis Brown
    Poot 2024-05-15 00:14 2025-05-15 00:14 edit,move Persistent sock puppetry; requested at WP:RfPP Daniel Quinlan
    Spore (2008 video game) 2024-05-14 23:39 2024-11-14 23:39 edit,move Persistent vandalism from (auto)confirmed accounts; requested at WP:RfPP Daniel Quinlan
    Jewish Institute for National Security of America 2024-05-14 06:51 indefinite edit,move Arbitration enforcement Doug Weller
    Nava Mau 2024-05-14 03:45 indefinite edit,move Persistent disruptive editing: per RFPP; will also log as CTOPS action Daniel Case
    Andrey Belousov 2024-05-14 03:31 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
    Category:Hamas 2024-05-13 23:01 indefinite edit,move Arbitration enforcement Izno
    Sde Teiman detention camp 2024-05-13 20:49 indefinite edit,move Contentious topic restriction: WP:ARBPIA Ymblanter
    Çankaya Mansion 2024-05-13 14:18 indefinite edit,move Arbitration enforcement, WP:GS/AA Rosguill
    Second Battle of Latakia 2024-05-13 13:39 indefinite edit,move Arbitration enforcement ScottishFinnishRadish
    Alien 2024-05-13 13:23 indefinite move lower to semi, time heals; requested at WP:RfPP The Night Watch
    Shays' Rebellion 2024-05-13 08:08 2025-05-13 08:08 move dang it. Not used to move protection, I guess.... Dennis Brown
    Chuck Buchanan Jr. 2024-05-13 02:01 indefinite create Repeatedly recreated; requested at WP:RfPP Daniel Quinlan
    Animal stereotypes of Jews in Palestinian discourse 2024-05-13 01:24 indefinite edit,move Contentious topic restriction: per ARBPIA Daniel Case
    Michael Ealy 2024-05-13 01:22 2025-05-13 01:22 edit,move Persistent vandalism: racist swinery Drmies
    Template:Nelson, New Zealand 2024-05-13 00:51 indefinite move Highly visible template that is vulnerable to macron vandalism Schwede66
    Hebrew University of Jerusalem 2024-05-12 21:47 indefinite edit,move Contentious topic restriction: per ARBPIA Daniel Case
    Interracial marriage 2024-05-12 19:14 2024-11-12 19:14 edit,move Persistent sockpuppetry RoySmith

    Topic ban appeal

    The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.



    I'm here to appeal my topic ban from caste related articles that i recieved on 21 June 2021 :[1] BLP, POV issues along with civility issues were cited as the reason for topic ban. :[2]

    In the future, I will only rely on broad perspective scholarly sources for the changes i wish to make and utilise venues such as WP:RSN and WP:DRN incase the dispute arises.

    I will avoid making any edits that might be deemed promoting a POV. If I get reverted, I will seek consensus on the talk page and refrain from edit warring . I will not accuse or cast aspersions against any fellow editor. I will maintain civility and take additional time to seek the consensus.

    It has been roughly two and a half years since I was topic banned from caste related articles, during this time my contribution has been constructive to Wikipedia, having brought Brajesh Singh to DYK section on Wikipedia's front page aswell as participating in recent NPP and AfC backlog drives. I have also been granted permissions such as new page patroller, rollback and pending changes reviewer. I have stayed out of trouble and I have not been blocked or received any other sanction other than this topic ban. I hope my topic ban will be lifted. Ratnahastin (talk) 11:21, 10 December 2023 (UTC)[reply]

    • Support Convincing appeal. ArvindPalaskar (talk) 12:52, 10 December 2023 (UTC)[reply]
    • Support - Ratnahastin deserves a chance to prove themselves. GoodDay (talk) 14:28, 10 December 2023 (UTC)[reply]
    • Support - I have been watching Ratnahastin edit since he was on a verge on getting topic banned. He has reformed big time as his appeal clearly shows and has been significantly productive for this site. Abhishek0831996 (talk) 16:57, 12 December 2023 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Dozens upon dozens of questionable redirects created by now-blocked user

    Today I've discovered that Special:Contributions/JailBrokenIPODGoneWild, a user now blocked for harassment, had created dozens upon dozens of questionable redirects related to public transportation. The redirects are all from color terms to a specific transportation line or service in systems where lines are depicted with colors on maps but not referred to by color in conversation or in official operations. The problem is that these redirects have qualifiers in front of the color terms like "Dark" and "Light", when nobody speaks like that, at least not in America. Nobody will say "Take the Dark Red Line"; people just say "Take the Red Line". If a given system has multiple lines or services that share a core color with different shades, the core color title should be a disambiguation page. Example of redirects that I just turned into disambiguation pages today are Green Line (Metra) and Orange Line (Metra). Again, very few if anyone would actually use the color qualifiers in conversation and thus I'm led to conclude that these redirects are implausible. The issue is the sheer quantity of them - way too many to list at RFD. How do we proceed from here? Taking Out The Trash (talk) 21:52, 22 December 2023 (UTC)[reply]

    • Holy crap. This user has created a whopping 12,000 redirects, and that's not including the 500ish additional redirects that have already been deleted. There's no way that all of those are valid. This may be a bigger issue than it seems on the surface. Taking Out The Trash (talk) 22:00, 22 December 2023 (UTC)[reply]
      • Some redirects appear valid (e.g. List of countries by calling code) but the majority appear to be nonsense. I think we need community consensus to allow admins to review and delete at their discretion. GiantSnowman 22:03, 22 December 2023 (UTC)[reply]
    • Looks like a 13k editor that was not blocked for socking, so WP:G5 and WP:NUKE is not an option here. Their activity and the block were both over a year ago. Looks like they were on the redirect autopatrol list at the time of their blocking, so all their stuff got autopatrolled. RAL at the time of their blocking, with them on it.Novem Linguae (talk) 22:07, 22 December 2023 (UTC)[reply]
    • Notified: Wikipedia talk:Redirects for discussion. –Novem Linguae (talk) 22:09, 22 December 2023 (UTC)[reply]
    • (from RFD): This is, uh, not good...

      The worst part is that many of the redirects look plausible, at least the most recently created ones.

      I think the best way to proceed is to have a formal, community-wide discussion on Are Such Redirects Helpful or Valid, preferably at the Village Pump, and if community consensus is that they are not, and that they would be deleted at RfD, then mass-delete them as a community action. (Non-administrator comment) Cremastra (talk) 22:31, 22 December 2023 (UTC)[reply]

    • This user has had plenty of redirects come to RfD before and I think they should probably continue to be handled that way; I fear that the mere fact of being blocked for an unrelated reason could place unwarranted scrutiny upon these redirects. While some of these redirects may be undesirable, their problems seem at a glance to generally be in the class of "implausible search term", not very harmful, rather than "targets wrong place", actively harmful. At the least, the most recent redirects are very helpful creations. J947edits 01:51, 23 December 2023 (UTC)[reply]

      • I skimmed through a few hundred of these redirects and most seem at first glance to lie somewhere in the space between "probably fine" and "implausible search term"; nothing Neelixual. Is there a way to find the ones that have inbound links? Folly Mox (talk) 03:06, 23 December 2023 (UTC)[reply]

    Was it unrelated? Was it for harassment at all?

    It is unclear from Special:Diff/1106477198 what prompted the 2022 block by Daniel Case, or the determination that this was a trolling/harassment-only account. I haven't found any noticeboard or talk page discussion since the 2009 discussion of the creation of redirects at Wikipedia:Administrators' noticeboard/IncidentArchive579#Redirects for every street in Manhattan. I haven't found a single talk page contribution from this account in 13 years, so it is perplexing what the trolling/harassment was. And the block log entry is no help.

    Uncle G (talk) 02:33, 23 December 2023 (UTC)[reply]

    • Looks like it was in response to this AIV report, which just expressed concerns about the redirects. I'd be curious to hear how people reached the conclusion that this was a vandalism-only account/troll: at a glance most of the redirects appear to be pretty clearly in good faith, whatever one might think of their usefulness. Extraordinary Writ (talk) 02:51, 23 December 2023 (UTC)[reply]

    I RfD'd a few of JBIGW's creations, and wasn't surprised to see them blocked eventually. (I'm not dismissing Uncle G's concerns about the procedure of the block, but in either case that level of WP:COMMUNICATE was going to lead to a block sooner or later.) My perception of JBIGW's redirects in general, though, is similar to Folly Mox': Most probably weren't worth creating, but at the same time don't need to be deleted. Before we go too far talking about a CSD X3 or whatever, could someone put together a list of, I dunno, 20 redirects they think would almost certainly fail RfD, and say how many redirs they had to go through to compile that list? Right now it's hard to get a feel for the shape of the problem, and if it is such a massive issue, this shouldn't be too hard to put together. -- Tamzin[cetacean needed] (they|xe|she) 04:50, 23 December 2023 (UTC)[reply]

    • It is more that Taking Out The Trash said above that JailBrokenIPODGoneWild was blocked for harassment and J947 commenting that this was unrelated and could result in unwarranted scrutiny. But from what Extraordinary Writ has turned up the block log entry is misleading, the block was actually directly about the redirects, and they were characterized by Sir Joseph as vandalism.

      That report was made on 2022-08-24; the most recently deleted redirects, created on 2022-08-20, were the ones from Wikipedia:Redirects for discussion/Log/2023 May 18#MBTA Silver Line line redirects; and the most recently not-deleted redirects were the likes of Postal code (United States) and List of Internet top-level domains (country) which may be useless, but which as Extraordinary Writ says do not really say vandalism-only account let alone trolling/harrassment.

      They also contain KOP, Pennsylvania and 84, PA created that day which seem unlikely but conceivable search terms that are fairly obviously in line with the target articles's contents. And from the previous month Geography of State College, Pennsylvania and its ilk seem uncontroversial and Government of Veracruz actually got used by someone else in an article.

      So I think that you are right, and both a case for vandalism and a case for "Holy crap. 12,000 redirects" need to be made with examples.

      Uncle G (talk) 10:47, 23 December 2023 (UTC)[reply]

      • For the record, I think Postal code (United States) is a great redirect. How am I supposed to remember what they call their postal codes? Zippers? Something like that. Cremastra (talk) 15:15, 23 December 2023 (UTC)[reply]
        • In this case, the best solution is to have Postal codes have a list of links to individual countries' pages where they exist (possibly as a navigation box); I believe that parantheticals generally make unneeded redirects, except where either there is the potential for a future article, or where an ENGVAR-alternate article with the parenthetical already exists (e.g Orange (color)). Animal lover |666| 08:58, 24 December 2023 (UTC)[reply]
          • I'm generally lenient on redirects – my criterion is, is this potentially useful to a reader?, as they are after all WP:CHEAP and generally harmless (they are usually a small net-positive, even if they seem unusual), but we should probably leave theses specifics to later. (And I'm aware I'm probably not wholly within policy with my views). 🎄Cremastra 🎄 (talk) 13:05, 24 December 2023 (UTC)[reply]

    (Undid automatic archival) So what exactly should be done here? I haven't had the chance to comb through all 12,000+ redirects, but I can tell you that the ones like "Dark Red Line", "Dark Green Line", "Light Green Line" etc when referring to transit lines are implausible, since nobody talks like that. The problem is that there are simply too many of these alone to send them all to RFD. Taking Out The Trash (talk) 19:13, 28 December 2023 (UTC)[reply]

    • @Taking Out The Trash: I don't see a problem with them. Take, for example, Light Green Line (Shanghai). The target notes that the line is displayed as "light green" on the system maps (Green Line (Shanghai Metro) correctly redirects to Line 12), and there's no ambiguity. It is 100% plausible to call it the "light green line" because that's what it is. 🎄Cremastra 🎄 (talk) 19:57, 28 December 2023 (UTC)[reply]
    • We're not quite in Miniscule boobies territory, but the similar situation with Neelix in 2015 is what WP:X1 was created for. With consensus we could just reactivate it, add this user's name to the criterion, and let it be handled naturally until no longer needed. The WordsmithTalk to me 22:17, 28 December 2023 (UTC)[reply]
    • What should be done is make a case with examples, as two of us stated above. Because the rest of us looking through this edit history haven't seen one leaping out at us. Actually make your case. You're leaping to the next step of asking something to be done assuming that a case has been made. It has not been. Uncle G (talk) 14:26, 1 January 2024 (UTC)[reply]

    Appeal of the removal of EC membership for User:DMH43

    The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.



    I (@User:DMH43) recently obtained EC membership. Since then, I have made several edits to ARBPIA pages (see https://en.wikipedia.org/wiki/Special:Contributions/DMH43). Today, I had my EC membership revoked by User:ScottishFinnishRadish, see https://en.wikipedia.org/wiki/User_talk:DMH43#Extended-confirmed_revoked. Quoting this user's message:

    you rushed to 500 total edits and then immediately switched entirely to editing ARBPIA topics exclusively. That is a clear case of WP:GAMING just to regain access to ARBPIA.
    

    I argue that my edits were not a case of gaming based on the rules described. The Gaming page describes restrictions as being preventative rather than punitive. I would consider the removal of my permission as punitive since no one has brought an issue with the contents of my edits (which I don't think have been controversial in any sense). The Gaming page does describe a case of gaming to gain EC access:

    An editor makes many unconstructive edits in a sandbox to become extended confirmed, and then makes controversial changes to extended confirmed protected articles.
    

    This is very different from my case. The example described is a clear manipulation whereas my edits have been valuable phrasing, formatting, citation and content improvements.

    User:ScottishFinnishRadish also suggests I edit strictly non-ARBPIA pages for a few months. But this is not mentioned anywhere in the rules. This suggests that the action taken against me is punitive.

    User:ScottishFinnishRadish also linked two recent cases (https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/IncidentArchive1144#User:President_Loki and https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/IncidentArchive1144#500/30_gaming_for_ARBPIA_editing) of users Gaming to gain EC access. Both cases are very different from mine. Specifically, the user mentioned in the first link has ~296 edits wikilinking "genus". The user mentioned in the second link has a HUGE number of very tiny, arguably useless edits. In contrast my edits are arguably much more substantial, very few are under 20 characters changed.

    Based on the above, I think the action taken against me is unjustified (and strictly punitive, not preventative) by the rules and I should have EC membership restored. DMH43 (talk) 17:11, 24 December 2023 (UTC)[reply]

    1) This account was open on 15 November.
    2) The first actual edit was on 1 December - just over 3 weeks ago.
    3) The first 100+ edits were in ARBPIA, in violation of 30/500. The user continued to edit in ARBPIA after being warned by me and other users, and stopped doing so only after I opened a complaint in AE.
    4) After the complaint, the user started editing in other topics, many of the edits not very substantial.
    5) As soon as the user got to 500 total edits, including many violation edits because they had edited in ARBPIA, they again started editing exclusively in ARBPIA, adding much POV material.
    Seems like a clear case of WP:GAMING. Dovidroth (talk) 17:36, 24 December 2023 (UTC)[reply]
    Everyone can feel free to check that discussion which has now been archived without action. And they can check that I messaged you to notify that I would undo your reverts. None of my edits were controversial or malicious. None of my edits have been challenged as POV. DMH43 (talk) 17:43, 24 December 2023 (UTC)[reply]
    How can the first 100+ edits be in ARBPIA where EC is the standard? Buffs (talk) 21:38, 27 December 2023 (UTC)[reply]
    @Buffs, There are many, many BLPs which have WP:ARBPIA4 related content. Most are semi-protected but not all and not many are fully protected. I've seen quite a few instances of Non-EC editors editing these articles and have had to warn them a number of times. I've seen instances new accounts making their first 10 edits by adding and removing spaces to article to get past semi-protection and then moving to editing BLPs which are semi-protected in sections which are WP:ARBPIA4 related. I've brought it to WP:AN/I when I've detected it. It's a very live issue and I don't think enough attention is paid to it. I've seen quite a few RfCs which are WP:ARBPIA4 related and where there are a lot of editors who have just over 500 edits who all vote in exactly the same manner. I'm not going to accuse each of those specific editors involved in those RfCs of gaming but it's hard not to draw conclusions when the same phenomena is seen a number of times. TarnishedPathtalk 07:46, 31 December 2023 (UTC)[reply]
    (edit conflict)I've also notified Dovidroth of this thread since they seem to have been quite invested in reverting you.
    As for my opinion on the merits of the request, I'm not convinced that this was really gaming the system. Did the user rush to 500? Sure, but the edits, in my opinion, seem to be at least fairly reasonable on the surface. I'm also not really convinced the standard generally established in other cases like this was met here. I don't think ScottishFinnishRadish was wrong here, but I also don't think the revocation of extended confirmed was particularly necessary, and I don't see a reason that it shouldn't be returned to them. The links ScottishFinnishRadish gave to the editor on their talk page as examples of gaming don't seem very egregious, and it seems like the editor, while maybe a bit inexperienced, does still know what they're doing, and the page they made in ARBPIA is still up. Based on this, I would support returning extended confirmed to the editor. If they're really becoming that problematic in ARBPIA even with extended confirmed, blocks still exist, and so does a friendly talk page discussion. EggRoll97 (talk) 17:42, 24 December 2023 (UTC)[reply]
    I would say that immediately reverting one editor a half-dozen times as one of their first actions after gaining autoconfirmed demonstrate problematic ARBPIA editing already, and also demonstrate the problem with gaming extended-confirmed with minor copyedits with the goal of returning to ARBPIA. ScottishFinnishRadish (talk) 18:08, 24 December 2023 (UTC)[reply]
    Those reverts were undos of reverts performed because I didn't have EC. No issue with the content was raised at the time. And I notified said user. DMH43 (talk) 18:10, 24 December 2023 (UTC)[reply]
    I would argue my reverts are the most benign edits I could have made, since no issue was raised regarding the content when i originally made these edits. DMH43 (talk) 18:14, 24 December 2023 (UTC)[reply]
    To be clear, I didnt go on a reverting spree of a specific user. DMH43 (talk) 18:14, 24 December 2023 (UTC)[reply]
    The fact that this user is calling POV-filled edits “benign” shows a lack of sensitivity to ARBPIA and that they are not ready to edit in this area. Dovidroth (talk) 02:56, 25 December 2023 (UTC)[reply]
    Those arent POV-filled edits, and if you had a case for removing them except for them being made by a non-ECP editor you could offer that. You dont though. nableezy - 14:23, 25 December 2023 (UTC)[reply]
    I have to agree with nableezy above. You could have explained that instead of just spamming "reverting editor not 30/500". You could have put a detailed edit summary in there, for what you actually thought was wrong with the edits. The editor was trying to contribute in good faith, which frankly it's a shame we don't just IAR these early ARBPIA edits and actually put a descriptive edit summary instead of spamming the same non-descript "user not allowed in here" garbage. Getting new editors acquainted is a problem, and this is part of it. EggRoll97 (talk) 14:34, 25 December 2023 (UTC)[reply]
    I disagreed with the edits, but there was no need to state that as you were non-EC and not allowed to edit in those articles in the first place. And I did not receive any notification that you were reverting me. Where do you think you have notified me? Dovidroth (talk) 18:59, 24 December 2023 (UTC)[reply]
    I had tagged you on the talk pages. For example https://en.wikipedia.org/wiki/Talk:Scars%20of%20War,%20Wounds%20of%20Peace?title=Scars_of_War,_Wounds_of_Peace&diff=prev&oldid=1191425028 DMH43 (talk) 19:01, 24 December 2023 (UTC)[reply]
    As a matter of procedure, @Dovidroth: I'm pretty sure your reversions on Scars of War, Wounds of Peace above are actually a violation of ARBPIA4, remedy 6, stating in part, All primary articles will be subject to the ARBPIA General Sanctions. {{ArbCom Arab-Israeli enforcement}} should be added to the talk page of affected pages, and {{ArbCom Arab-Israeli editnotice}} should be added as an editnotice to affected pages. The presence of the templates is required before the General Sanctions can be enforced on primary articles. As that particular article is part of the entire set of articles whose topic relates to the Arab-Israeli conflict, broadly interpreted ("primary articles"), ARBPIA restrictions shouldn't apply unless the editnotice and talk page template have been applied. Regardless, it seems the editor wasn't actually prohibited by 500/30 from making those edits. POV is a different issue, but that can be hashed out separately. EggRoll97 (talk) 19:30, 24 December 2023 (UTC)[reply]
    EggRoll97, while there are separate additional requirements for sanctioning editors for restriction violations, there is no such requirement for the extended-confirmed restriction to exist and apply in the entire topic area. Special:Diff/1188566854 is a fine revert and Special:Diff/1187991384 (2023-12-02), from an account created 2023-11-15, is a clear violation of the extended-confirmed restriction independently of the edit count. This doesn't mean that DMH43 has to be blamed for not knowing about it; it just means that your procedural concern is invalid. ~ ToBeFree (talk) 22:05, 24 December 2023 (UTC)[reply]
    You used the automatic edit summary that says that you are reverting me. That is not exactly informing me. Either way, your cannot assume if I reverted you saying that you are a non-EC editor that I otherwise agree with your edits. Dovidroth (talk) 02:59, 25 December 2023 (UTC)[reply]
    "Rushing to 500" is GAMING, and the policy at WP:PGAME should be updated to reflect modern understanding. This isn't the clearest cut obvious case of gaming ever, but yes if the first 100 edits, three weeks ago, are in violation of ECP, then someone putters around for awhile making edits like this and this and this (all trivial) and these (non-trivial, editor's most-edited article outside ARBIPA space, may be a genuine improvement, lots of references removed), and then immediately abandons the prior topic area to leap back into EC with seven reverts of the same editor and then publishes this (removing balance from Wikivoice, refbombing POV statement including a citation "by" |last=Nast |first=Condé with the balance unformatted, adding contentious material with a built-in {{cn}} tag at time of edit, then reinforcing the POV with an added paragraph at the end of the subsection): this demonstrates both intent to game, and unreadiness for constructive editing in ECP topics. Folly Mox (talk) 04:01, 25 December 2023 (UTC)[reply]
    The first and third edit are also nontrivial from a conceptual standpoint, which i am happy to explain.
    I also don't consider what I've done as abandoning. I am excited to edit pages which I havent had a chance to edit yet, which is why I am engaging more with ARBIPA content recently. DMH43 (talk) 04:09, 25 December 2023 (UTC)[reply]
    "Trivial" was not the most appropriate description of your edits in the statistics and mathematics space. Your contributions were definitely better than the type that (for example) changes a single punctuation mark or adds a single wikilink. For what it's worth, I do sympathise with your position, and having looked more fully into your post-EC edits in ARBIPA, I definitely picked the most problematic one to link to (it was chosen arbitrarily).
    What I was trying to convey was that your editing while waiting for EC wasn't the kind that engaged with any policies that will be necessary to understand for editing non-disruptively in contentious topic areas. I do see you've engaged appropriately at Talk:Oslo Accords, and your ARBIPA edits like this and this seem unproblematic. But both this edit and the one already linked above show that you haven't learned yet how to correct problems with your citations, which is going to be important in a contentious area; this edit and this edit display a propensity for placing quotes that align with your POV in eye-catching blockquote templates in prominent locations, the bit about removing balance to put your POV in Wikivoice I mentioned above, and the removal of all the references that didn't align with your vision for Statistical hypothesis testing concerns me.
    Reverting the same editor on seven articles as soon as you were technically able to does give the impression of an antagonistic perspective. It's fine to disagree completely with someone else, but hopping straight to reversion instead of attempting to reach a compromise is how articles get disrupted. Reversion should feel icky, not triumphal. The goal is always productive collaboration, not our own preferred prose.
    One major problem with ECP is that it's a purely numeric threshold standing in for what would ideally be a qualitative test of applicable competencies. The assumption behind the idea is that if someone has been editing for a month and made five hundred edits, they'll be sufficiently familiar with the rules for constructive collaborative editing, and sufficiently invested in encyclopaedic improvement, that they should be able to edit whatever articles call their interest. But if someone spends that month (not even, in this case) and those 500 edits making small edits in a space where they're not even interacting with other editors and then leaps directly into the most contentious topic on the project, the process hasn't worked.
    I'd like to see an understanding of WP:NPOV, an approach of attempted compromise before resorting to reversion, and closer attention paid to citations. I'm not an admin and I don't usually edit content in contentious topics, so my opinion here shouldn't be taken too seriously, but I wouldn't oppose restoring EC after a brief period demonstrating collaborative editing in a non-ECP CTOP, or even just a personal reflection accurately describing the problems with the edits made before the permission was revoked. Also, WP:PGAME should be updated. When policy lags behind practice, it confuses people. Folly Mox (talk) 14:05, 25 December 2023 (UTC)[reply]
    Oh, I characteristically forgot: please don't add unsourced prose with a {{cn}} attached at time of edit. Even if done for the best of reasons it can lead to undesirable results.
    Noting also for the crew that (per Zero0000 and nableezy) my understanding of PGAME as practiced may be in the minority, on the "overly strict" side. Folly Mox (talk) 14:50, 25 December 2023 (UTC)[reply]
    Ive brought up several GAMING violations in the past, they were all for doing mindless edits repeatedly with a clear intention to get to the restricted topic. But doing mindful edits with that same intention has never been treated as GAMING before, even when the intent to return to a CTOPIC is plainly evident. This editor, from everything Ive seen of their edits, will be a positive to our goals as an encyclopedia. There were editors previously who very plainly edit from the polar opposite of the POV spectrum that I encouraged to stick around because I also saw their edits would be a positive as an encyclopedia. Eg here. I think it would be healthy if we saw more of that instead of editors attempting to use procedural roadblocks to stop what is plainly a good faith and productive editor who is trying to follow the rules. I dont mean you to be clear, but it seems pretty plain to see that is motivating some of the comments here. nableezy - 22:08, 25 December 2023 (UTC)[reply]
    The points you brought up are:
    • I didn't edit pages which allowed me to engage with other users
    • I started editing ARBIPA pages when I was given access
    • I have shown some issues formatting citations and possibly other content
    • I haven't made edits outside ARBIPA that clearly show an understanding of WP:NPOV.
    • I reverted a user's edits who had reverted me for no reason other than I was new and did not have EC permission.
    But none of this is close to breaking any rules, as far as I know. I followed the rules in good faith which is clear from my edit history. If the rules aren't sufficient and the "process hasn't worked" isn't that a call to update the guidelines rather than to punish me as a new user?
    In response to your other comment, thank you for pointing out that I shouldnt use cn expecting someone else with find a citation. DMH43 (talk) 14:55, 25 December 2023 (UTC)[reply]
    I think this thread provides adequate guidance, and I'm feeling convinced by nableezy above that the string of reverts were reverts of technical reverts of DMH43's own edits (which I didn't realise at first). Levivich makes good points below, as does Zero0000 in their response to my question.
    Emotionally I feel bad for taking a stance which I wrongly assumed to be consensus, but turns out to be stricter. That's not the person I want to be. I note also DMH43 engaging productively again in non-ECP space. Switching to Support restoring EC at 30 days since first edit (i.e. 01 January) per Black Kite somewhere in this thread; wouldn't oppose restoring earlier. Folly Mox (talk) 21:44, 26 December 2023 (UTC)[reply]
    • Endorse SFR's action, close AN thread appeal, user should receive a warning. The user does not understand what they did wrong. They should read Gaming the system and Righting great wrongs, and receive a warning. Andre🚐 05:04, 25 December 2023 (UTC)[reply]
      Can you be more specific? DMH43 (talk) 06:18, 25 December 2023 (UTC)[reply]
      If this is a case of gaming, someone should be able to show me a case of another user who made similar edits and also had their EC membership revoked. So far, I have only been shown users with a history of very clear bad faith edits. DMH43 (talk) 14:57, 25 December 2023 (UTC)[reply]
      That is not a reasonable request as there is no way to either contact every Admin who has removed ECP or search every instance. And it shows to me at least you aren’t listening or not understanding what you are being told. Doug Weller talk 21:53, 25 December 2023 (UTC)[reply]
      Yeah, this is bordering on WP:NOTHERE Andre🚐 22:17, 25 December 2023 (UTC)[reply]
      That is highly uncivil, the editor is clearly here to build an encyclopedia and even the briefest perusal of their edits would demonstrate that. nableezy - 22:18, 25 December 2023 (UTC)[reply]
      Read NOTHERE, it talks about gaming and attitude conflicts similar to what we see here. Andre🚐 22:21, 25 December 2023 (UTC)[reply]
      There isnt any gaming. Constructive editing is not gaming. nableezy - 22:22, 25 December 2023 (UTC)[reply]
      There's a clear consensus here of users and admins saying that racing to 500 to revert the same user 7 times along ideological lines is obvious gaming. Let's not go back and forth. You disagree, but there's a consensus here against you. Andre🚐 22:24, 25 December 2023 (UTC)[reply]
      Dont think any of that is true at all. And I expect if people look at it a bit more deeply they will see it is not true. But no, I dont think your description of this is accurate either. nableezy - 22:28, 25 December 2023 (UTC)[reply]
      I don't believe that they're NOTHERE, I just believe that they rushed edits as quickly as they could to meet EC by the letter of the rules and immediately dive in to conflict, gaming the system so they could revert to their preferred version. That shows a critical lack of understanding of how Wikipedia, and CTOPs in particular, work. If I had seen any editor in the topic area go around to half a dozen articles reverting the same editor I would have taken some action. With the circumstances in this particular situation I figured removing ec was a reasonably light touch. ScottishFinnishRadish (talk) 22:51, 25 December 2023 (UTC)[reply]
      I don’t think that’s really what happened, they were restoring their own edits. Not simply reverting another editor. If they had been following Dovidroth around then sure that’s its own issue, but they returned to articles they had previously edited and had their edits removed for reasons that no longer applied. I don’t think that’s even remotely gaming or evidence of any bad faith at all, those edits were all fine and were only removed for EC reasons. When he was EC then it made sense to return them. nableezy - 23:06, 25 December 2023 (UTC)[reply]
    • Proposal: issue warning, endorse permission removal, restore permission at 30 days after first edit and 500 main space edits, notwithstanding any findings of misconduct, which should be treated separately. DMH43's account will be 30 days old on 30 December, and has made 490 main space edits. I agree that gaming against the spirit of 30/500 has clearly occurred, but the edits seem to be themselves in good faith, even if they are trivial or minor. Their request to restore permission has also provided greater scrutiny on their editing. Onetwothreeip (talk) 06:40, 25 December 2023 (UTC)[reply]
      I also note that this is not the designated process for requesting restoring permissions, but we might as well determine this here; the relevant editor brought this here and we are not a bureaucracy. Onetwothreeip (talk) 08:13, 25 December 2023 (UTC)[reply]
      Since this was a logged AE action, I told them they could appeal here. ScottishFinnishRadish (talk) 12:02, 25 December 2023 (UTC)[reply]
    • Deny appeal and use the standard process for restoring in the future. No need for other sanctions. It is a bit of gaming, but they are also a new user (we assume). I would imagine that ScottishFinnishRadish would be willing to restore after a short period of worthwhile contributions. SFR was within their authority to issue the sanction and I see it as a reasonable admin action, but the actions that led to the sanction weren't the most egregious case of gaming, so I have faith a balanced approach will be taken when reinstating EC. Dennis Brown - 07:22, 25 December 2023 (UTC)[reply]
    • Deny appeal per Folly Mox and Dennis Brown. — Preceding unsigned comment added by Doug Weller (talkcontribs) 08:00, 25 December 2023 (UTC)[reply]
    • I don't get it. It is true DMH43 did many early edits contrary to ARBECR. No argument there. But I wonder when editing exclusively in ARBPIA after becoming EC became a crime. Many editors edit exclusively or almost exclusively in ARBPIA. I also don't see the "gaming" claim. I've seen lots of gaming of the 500/30 rule and they didn't look like this. Most the edits are substantial, including some of those described above as trivial (such as this and this which correct actual errors; as a mathematician I am qualified to say that). Specifically, I contend that on looking at DMH43's first 500 edits (your prefs might determine how many display at once) they don't look out of the ordinary. They do not consist mainly or even largely of trivial edits. And it took 20 days to reach 500, which is not a particularly fast rate of editing. Zerotalk 13:16, 25 December 2023 (UTC)[reply]
      "Trivial" was an inapt descriptor. Pretty much everything in that paragraph was inapt to a degree, particularly the structure, and also on reread using "balance" in two different meanings a few words apart. I've attempted to explain myself a bit better above in the cold light of day. Zero0000, are you able to comment on the filer's rewrite here, and whether there's anything concerning about it? Folly Mox (talk) 14:26, 25 December 2023 (UTC)[reply]
      @Folly Mox: your question is one that belongs on the article talk page, as there are no obvious behavioral problems. As far as this case is concerned, note that making a lot of changes to an article in a single edit is exactly the opposite of what people do who are making rapid trivial edits to get EC. Zerotalk 01:03, 26 December 2023 (UTC)[reply]
    • Restore after 100 more edits - I dont see any GAMING at all, there were ECP violations, not gaming ones, earlier. Those edits shouldnt count towards the 500 to become extended confirmed, but this is not gaming, those are constructive edits that took time, not mindless adding whitespace or changing and reverting their own change, or making slight modifications to categories or templates. But the claim of gaming appears to have little to no substantiation, I see no "rushing" to 500, and I think it pretty normal for an editor to revert edits that were made for a reason that no longer applies. Hell, when Dovidroth was unblocked as a sockpuppet he restored his edits that had been reverted for BANREVERT. And why wouldnt he? The cause for the removal wasnt valid, so he was entitled to restore them. nableezy - 14:27, 25 December 2023 (UTC)[reply]
    • In the middle of this appeal, this user complained about me on another user's talk page. This continues into a possible WP:Battleground behavior. Dovidroth (talk) 16:49, 25 December 2023 (UTC)[reply]
      The battleground page describes behavior which disrupts Wikipedia. Nowhere in my post do I suggest any disruptive behavior, rather I point out a few cases that seem to me to be bad faith edits. This post of yours suggests you are taking my edits personally, whereas none of my posts have been personal in nature; they are all content based. DMH43 (talk) 17:26, 25 December 2023 (UTC)[reply]
      Posting a complaint about a user on another user (not an admin)’s talk page is inappropriate and borderline WP:battleground. And on what basis do you claim my edits are bad faith? Seems like an ordinary edit dispute. Dovidroth (talk) 17:32, 25 December 2023 (UTC)[reply]
      You haven't engaged with the content of any of my edits, just reverting them despite some of them were correcting obvious factual errors (such as misattributed quotes). DMH43 (talk) 17:43, 25 December 2023 (UTC)[reply]
      I am glad to engage with EC users. I am allowed to revert anything in ARBPIA from a non-EC user that I disagree with without providing further explanation. “Anyone is free to revertany edits made in violation of a ban or block, without giving any further reason and without regard to the three-revert rule.” WP:Banrevert. A non-EC user in ARBPIA is effectively the same thing as a ban. Dovidroth (talk) 17:56, 25 December 2023 (UTC)[reply]
      Any reasonable third party would consider your reverts as irresponsible and borderline harassment of a new editor. DMH43 (talk) 19:10, 25 December 2023 (UTC)[reply]
      I showed you in the policy that what I did is legitimate. Falsely accusing me of acting irresponsible and abusive because you don’t like it will not get you anywhere. I hope the admins reviewing this case will see that this user is interested in pushing his POV without following the rules and that they should not be allowed to edit in ARBPIA. Dovidroth (talk) 19:14, 25 December 2023 (UTC)[reply]
      That accusation of harassment is incivil. Propose that DMH43 should be warned for incivility Andre🚐 22:12, 25 December 2023 (UTC)[reply]
      I'd say it's spot on, actually. I'd instead propose that Dovidroth be warned for violating WP:BITE. EggRoll97 (talk) 23:19, 25 December 2023 (UTC)[reply]
      "I am allowed to revert anything in ARBPIA from a non-EC user that I disagree with without providing further explanation." Are you saying that you wouldn't revert a contribution from a non-ECP editor that you did agree with? Black Kite (talk) 22:15, 25 December 2023 (UTC)[reply]
      WP:Banrevert states that “This does not mean that edits must be reverted just because they were made by a banned editor (changes that are obviously helpful, such as fixing typos or undoing vandalism, can be allowed to stand), but the presumption in ambiguous cases should be to revert.” There have been cases that I have decided to leave something, but obviously if another EC editor reverts them, I will respect that. Dovidroth (talk) 05:15, 26 December 2023 (UTC)[reply]
    • Frankly, the most troubling behavior in this thread is being displayed by Andrevan (for misstating the degree of consensus in an apparent attempt to shut down the discussion, as well as the hyperbolic, bolded demand for a warning above in response to a comment that is well within the norms of discussion on AN if not necessarily wise), and to a lesser extent Dovidroth (a new editor asking on a 3rd party's talk page for advice on how to respond to what they perceive to be harassment is completely reasonable behavior, and in general if Dovidroth had followed correct protocol and started with {{alert/first}} like we're supposed to there's a decent chance that this discussion wouldn't be happening at all right now). signed, Rosguill talk 22:51, 25 December 2023 (UTC)[reply]
      I didn't say the consensus is that the thread should be shut down, but that gaming is gaming. You can disagree. I stand by the statement that the accusation of harassment is inappropriate and I still feel the user should be warned; nothing hyperbolic about a warning, nor does bolding indicate anything, it is standard to bold opinions in discussions. I was not aware the user was not alerted, however, which is unrelated. Andre🚐 22:55, 25 December 2023 (UTC)[reply]
    • Endorse removal, but I would look favourably on restoring the permission when the user has made 500 non-ARBPIA edits (and has reached 30 days, of course). Obviously, if they then behave disruptively in a CTOP area after that, then that's a separate issue. Black Kite (talk) 23:06, 25 December 2023 (UTC)[reply]
    • Keep removed, but restore after 500 mainspace non ARBPIA edits, and take further issues (if any) to arb enforcement.VR talk 23:28, 25 December 2023 (UTC)[reply]
    • Support appeal/restore EC now - I don't understand how anyone looks at this editor's mainspace edits and sees them as trivial or gaming or anything other than normal editing: adding sourced content, removing unsourced content, fixing/adjusting content. The edits aren't perfect but they're normal edits.
      More broadly, as someone who strongly supports ECR (and its expansion), I don't understand why some editors refer to a pattern of editing in non-ARBPIA edits until EC, and then editing ARBPIA once EC, as "leaping" or "jumping" into ARBPIA or "abandoning" the other topic area. I don't get how other editors don't get that editing in non-ARBPIA areas before EC and then editing ARBPIA after EC is exactly what we want editors to do, and the whole point of ECR. We want new editors in ARBPIA, and we want editors to get experience elsewhere before editing ARBPIA. This is exactly what this editor has done (thank you for your volunteer work, sorry for this unpleasant experience). (This is also exactly what I did when I first got here in 2018. Nobody took away my EC. I don't see any meaningful difference between this editors first 500 edits and my own first 500 edits. And if someone had yanked my EC, Wikipedia would probably have lost my next 25,000 edits over the next five years. Let's not shoot ourselves in the foot by driving away new volunteers.)
      Folks, whenever there is a major world event, new editors will show up wanting to edit topics about that event. When the event is in ARBPIA, as here, you can expect to see editors editing non-ARBPIA topics and then editing ARBPIA topics after EC. There is nothing wrong with this. This editor's mainspace edits show me they have enough experience and understanding of policies to edit in the ARBPIA topic area. Their edits aren't all perfect, but neither are mine or any other EC editor's.
      "Gaming" is when someone makes 250 edits adding a period and then 250 edits removing a period and then edits ARBPIA. This is plainly not what this editor did.
      If someone reverts an editor's edits because they're not EC that's allowed per ECR, but we shouldn't be surprised when the editor reinstates their edits after hitting EC. Again, this is what we want: new editors volunteering to edit this topic area. Levivich (talk) 18:34, 26 December 2023 (UTC)[reply]
      Many of the 500 edits are very minor and trivial, and were made very rapidly. The first edits also began two weeks after the account was created. This is why I see this as gaming, but it's not particularly egregious. Giving this editor EC permission does not jeopardise Wikipedia. Onetwothreeip (talk) 21:33, 26 December 2023 (UTC)[reply]
      Here are DMH's first 50 edits -- none of them are very minor or trivial AFAICS. You can tell just by looking at the size of the edits that they're not trivial. The most trivial edit in the bunch is one edit that adds a wikilink, and that's not trivial. Here are their next 50 edits -- I see one edit that adds a period, the rest are plainly not trivial (I can't see the revdel'd ones). So that's 99 non-trivial edits out of their first 100. I haven't looked at all 500, but here are their first 500 and again, just by looking at the sizes of the edits, we can see that the vast majority, like almost all of them, are non-trivial. It makes me wonder what other editors consider "trivial"? Levivich (talk) 21:46, 26 December 2023 (UTC)[reply]
      I saw various edits which were adding or removing a word that had little to no effect on the meaning of the sentence, when I was looking at the later edits. However, this is too trivial to necessitate any sanctions or permission removals. Onetwothreeip (talk) 23:47, 26 December 2023 (UTC)[reply]
    • I returned here to write more but I see that Levivich has written more or less exactly what I wanted to write, so I'll just say that I agree completely. Zerotalk 03:53, 27 December 2023 (UTC)[reply]
    • Restore now per Levivich. Curiously, some participants in this thread are now topic banned from ARBPIA by SFR. 0xDeadbeef→∞ (talk to me) 12:04, 27 December 2023 (UTC)[reply]
    • After reflecting on the discussion here I think Black Kite's proposal is a good way to split this particular nickel. If I weren't a meathead I would have made that the restoration criteria when I removed the permission. ScottishFinnishRadish (talk) 13:10, 27 December 2023 (UTC)[reply]
    • Procedurally restore permissions. Levivich makes excellent points above. Likewise, the idea that fulfilling bright line requirements (50/300) is somehow indicative that they are attempting to game the system is absurd. Blocking someone from "the club" based on the fact that they met the rules "too quickly" is ridiculous. We have the 30 day requirement and 500 edits for a reason. It's not like he added a space 250 times and deleted a space 250 times to achieve that. He was making substantive contributions. Now, the quality of those edits and other issues notwithstanding, EC should be restored forthwith. Any additional issues should be addressed in a different thread (the user seems remarkably versed in WP terminology for a noob). Buffs (talk) 21:50, 27 December 2023 (UTC)[reply]
    Thanks everyone for the thoughtful comments and followups. I believe SFR has come to a decision about my EC status (see my talk page). My question for the group is: is there any kind of behavior not described in the rules that I should avoid? For example some have mentioned that I should spend a few months editing non ARBIPA topics for a while; should I head this advice? Should I make sure to have a daily mix of EC and non-EC edits? It seems my focus on EC specific pages raised a flag for users and I would like to avoid that. I'm open to suggestions and advice. Thank you DMH43 (talk) 22:12, 27 December 2023 (UTC)[reply]
    And as for the reverts that Dovidroth has done from most of my edits, when can I undo them? Should I open discussions on the associated talk pages for these changes? DMH43 (talk) 00:29, 28 December 2023 (UTC)[reply]
    For the reverts, I suggest a talk page message and give it a couple days to see if there are any objections. You don't need to have a mix of edits, but it's good to get experience in not one of the worst areas to edit, and the same goes for editing in other topics before diving in. That's my take, other views will likely vary. ScottishFinnishRadish (talk) 00:38, 28 December 2023 (UTC)[reply]
    • Endorse SFR's action, with consideration of restoring after user has shown a pattern of productive editing and an understand of what brought this about, using the normal appeal process. I generally agree with Dennis Brown's comment. SFR has shown abundant evidence to support their action.  // Timothy :: talk  22:06, 28 December 2023 (UTC)[reply]
    • Endorse SFR's action, close AN thread appeal, user should receive a warning. The fact that there first 100+ edits were in WP:ARBPIA and that they only ceased when warned and that they immediately resumed editing WP:ARBPIA the second they reach 500 speaks for itself. Additionally DMH43's description of their edits "my edits have been valuable phrasing, formatting, citation and content improvements", sounds mostly like minor editing designed to reach EC as fast as possible. In recent similar cases in AN/I, I've seen editors lose their EC rights. TarnishedPathtalk 07:58, 31 December 2023 (UTC)[reply]
      So you're saying that he was warned, complied with the warning, and so now should be warned again? "Speaks for itself"? What does it say: that the editor follows instructions? "Content improvement" sounds like minor editing to you? Seriously? This is an even worse rationale than the one above it. Levivich (talk) 14:43, 31 December 2023 (UTC)[reply]
    • Procedural note. I roughly count DMH43's non-IPA mainspace contributions at ≥520, and in about four hours it will have been 31 days since the account's first edit. Folly Mox (talk) 01:31, 1 January 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Create N-word redirect pls

    From bibliography of the slave trade in the United States, link from Nigger Trader White (original language used in primary source article) redirect to John R. White#Negro-Trader White. Please and thank you and also I'm sorry. jengod (talk) 03:51, 26 December 2023 (UTC)[reply]

    •  Done Dennis Brown - 07:57, 26 December 2023 (UTC)[reply]
      Appreciate it. I hope you have a wonderful week. Best, jengod (talk) jengod (talk) 08:01, 26 December 2023 (UTC)[reply]
      Wouldn't it be better if whatever filter this is allowed creations by ECP users? Mach61 (talk) 01:19, 27 December 2023 (UTC)[reply]
      This is from Mediawiki:Titleblacklist, not a WP:EF. There's an option to allow autoconfirmed editors, but I'm not sure if allowing EC editors is possible. Suffusion of Yellow (talk) 02:16, 27 December 2023 (UTC)[reply]
      Given that any template editor, page mover, or sysop can bypass the title blacklist when needed, I don't see much reason to move down the prohibition on the title blacklist. Probably best to keep this as a fully-blacklisted part of the TB. EggRoll97 (talk) 02:32, 27 December 2023 (UTC)[reply]
      I agree. The harm of blacklisting these titles (a small number of legitimate requests to create pages or redirects, although no automatic restrictions on editing them once created) is probably minimal; the risk of removing it from the blacklist (anyone, including sockpuppeteers, as long as their IP address isn't blocked, can create an account and create such pages 10 edits and 4 days later) is much greater. Animal lover |666| 17:31, 28 December 2023 (UTC)[reply]
      Or anyone in draftspace or talkspace; some other namespaces can be created by non-autoconfirmed registered users. –LaundryPizza03 (d) 01:29, 3 January 2024 (UTC)[reply]
      I also agree. It took me less than one minute to verify that this was a valid request. The request was filled about 4 hours after it was made, on the day after Christmas, which I think is very timely. The current system seems to work fine. Dennis Brown - 01:59, 31 December 2023 (UTC)[reply]

    RFC closure review request - Enrique Tarrio

    Discussion focused on whether the infobox image should be of the subject posed in a suit or a candid at a rally. By vote count, opinions were split close to equally, but the main rationale against the "suit" image was not founded in policy and this was not addressed in the closure statement. The closer also closed the RFC as "No Consensus" but has since clarified that they interpret that to mean "Consensus against both options" and used that result to justify negating the previous consensus for the suit image, which has been the lead image in the article since mid 2021. I believe both the closure and the follow-up interpretation merit review. VQuakr (talk) 04:09, 29 December 2023 (UTC)[reply]

    Endorse the no consensus closure, and interpret as reverting to the consensus of the previous RFC, meaning the suit image should still be used. EggRoll97 (talk) 05:59, 29 December 2023 (UTC)[reply]
    I do want to clarify that while there was a discussion that resulted in unanimity amongst the five participants, there was not a previous RFC to my knowledge. VQuakr (talk) 06:09, 29 December 2023 (UTC)[reply]
    The RFC clearly established that there's no consensus to include the very controversial promotional image uploaded by an SPA photographer -- its restoration would likely constitute a behavior issue at the point. Meanwhile the alternative also proved controversial, with multiple editors suggesting no image would be better than either of the candidates. We should keep looking -- lots of people have spoken of the possibility of using a cropped mugshot, that's probably the solution. Feoffer (talk) 06:32, 29 December 2023 (UTC)[reply]
    • [uninvolved] Partial endorse - Looking at the discussion, I find the arguments against the suit image to be the strongest. Fundamentally, images on Wikipedia are supposed to be an aid to understanding, and I think those supporting the alternative effectively argued that the suit photo, while, yes, a professional studio shot, does not aid the reader's understanding of the subject (and in fact presents an impression of the subject incongruous with the way we write about him). That said, those supporting A have a good point that B isn't ideal either, but I don't see those arguments as disqualifying as the arguments against the suit photo. We settle for subpar images all the time -- the important thing is that they aid understanding. We're not identifying a bird species such that the best image is always going to be the sharpest, clearest photo depicting a typical specimen; we're determining how best to illustrate an article on an American far-right activist and convicted seditionist, and I think that kind of distinction -- and its relation to our guidelines about what an image is supposed to do -- comes through in the arguments. TL;DR - It does look like there's consensus against the suit image, but I'd just call it "no consensus about a replacement". — Rhododendrites talk \\ 06:53, 29 December 2023 (UTC)[reply]
      I'm not sure how much weight should be put into arguments that a professional studio photo doesn't aid the reader's understanding of the subject. As a practical matter, we seem quite happy to use such photos of politicians, judges, CEOs and heck plenty of other people even when alternatives exist. While I've sometimes seen arguments against this saying they're too promotional, this rarely seems to be accepted so I'm unconvinced there's any community consensus on this, probably the opposite in fact. The only minor difference here is that professional studio photos of others will often photograph them in something akin to their more everyday clothes, which may very well be a suit for a politician. Although even that can be complicated and it's hardly uncommon they dress different generally in a way that comes across as more professional than they do most of the time. I mean for someone in the military they'll often be in their dress uniform even if they're in a role which means they spend most of the time in their regular uniform. (There's also the question of how we should interpret people encountering the subject. For example, for a politician especially a member of a legislature, there might be dress codes requiring them to dress in a certain way. And people might see them on TV or in the legislature dressed in this way. But practically, people might be more likely to actually see them in person at a rally or walkabout or constituency office or whatever where they might dress different.) Nil Einne (talk) 12:45, 29 December 2023 (UTC)[reply]
      we seem quite happy to use such photos of politicians, judges, CEOs [...] The only minor difference here is that professional studio photos of others will often photograph them in something akin to their more everyday clothes - That's not a minor difference. A studio shot of a politician looking like a politician makes sense for a lead image. If we had 10 so-so photos of a politician looking like a politician and one of a politician in a baseball uniform even though nothing in the article talks about a baseball, we wouldn't use the latter even if it were a perfect 30 megapixel studio shot because it doesn't aid understanding. Likewise the studio shot here does not aid understanding. It can always be added to the article further down if folks feel like it's important, but the arguments that it shouldn't be the lead photo are IMO persuasive. — Rhododendrites talk \\ 14:40, 29 December 2023 (UTC)[reply]
      @Rhododendrites: this seems like verging into rehashing the RFC rather than the close, but I do want to clarify that the reason we wouldn't use the image of the politician in the baseball uniform is because it would be confusing, not because it didn't look like the politician. It is an imperfect analogy because anyone can wear a suit, and wearing a suit doesn't cause confusion in the same way that a baseball uniform would. The primary purpose of a lead image in a biography should be to see what the person looks like. Wearing a suit doesn't detract from the purpose of being an identifiable image; face turned to the side and wearing hat and sunglasses does. VQuakr (talk) 18:07, 29 December 2023 (UTC)[reply]
      I understand that's your perspective. I'm saying I found the arguments against that perspective to be stronger in the discussion. We're not identifying a species of animal, we're illustrating a subject about a specific person to aid understanding of that person. The color of the subject's eyes, the shape of his pores, etc. do not aid understanding as much as seeing him engaged in the activity he is best known for. — Rhododendrites talk \\ 18:19, 29 December 2023 (UTC)[reply]
      Ok but getting back to the closure review, "my perspective" is based on PAG. MOS:IMAGEQUALITY specifically calls for a portrait photo in the lead. "the color of the subject's eyes" is a weird way to say "what the subject looks like" but yeah, that is absolutely the main purpose of a lead image. VQuakr (talk) 18:49, 29 December 2023 (UTC)[reply]
      "portrait photograph" doesn't mean "with fancy clothes in a studio" -- it means it's a photo taken with intent to depict the subject. Going back to my example, we could have a portrait photograph of a politician in some random non-politiciany outfit and we would still use the photo that makes them look like a politician. That guideline also says For example, a painting of a cupcake may be an acceptable image for Cupcake, but a real cupcake that has been decorated to look like something else entirely is less appropriate. The policy, WP:IUP says The purpose of an image is to increase readers' understanding of the article's subject matter. WP:NPOV includes images as a possible WP:WEIGHT issue. There's plenty. It's not the same calculation the subject uses to decide on a profile picture; it's what best aids understanding and accurately depicts the full subject. I feel like I'm repeating myself, though, so I'll leave this be as it waits for additional input. — Rhododendrites talk \\ 19:08, 29 December 2023 (UTC)[reply]
    • The closer was right to find no consensus, but wrong to understand that as consensus against both. The correct finding would have been "no consensus, restore the status quo ante".—S Marshall T/C 08:01, 29 December 2023 (UTC)[reply]
    • I agree that no consensus seems a fair close of that discussion. However as others have said, the correct outcome of a no consensus here is to keep the previous image until consensus is found for a new alternative. In other words, it's fine to encourage continued discussion, but not to say the previous images can't be used. Nil Einne (talk) 12:03, 29 December 2023 (UTC)[reply]
      I would add that there's no chance in hell that an NFCC image could be used for simple identification of the subject who not only is a living person (albeit currently in prison) but for whom free images do exist. And so any discussion that involves the premise it could is a non-starter. In case there's some confusion, while Wikipedia:Non-free content is technically only a guideline, the living person issue actually comes from the foundation's wmf:Wikimedia Licensing Policy so is not even something we can just change by ourselves. I mean if someone really wants to petition the WMF to change the policy, they can try I guess, but until that happens we should just ignore the possibility it could. Nil Einne (talk) 12:25, 29 December 2023 (UTC)[reply]
    I'm involved, but I endorse close as written, including the consensus against the previous image. Loki (talk) 20:18, 29 December 2023 (UTC)[reply]
    • I'm also involved, but for what it's worth, I endorse as written, including the consensus against the previous image. Notably there had been no previous RfC, this was the first. Additionally prior discussion on the issue, by my reading did not result in that much of a clear consensus, despite the claims of others. The only grounds for reversion to the previous image is that it was there for a while and I think that frankly we can do better than that. TarnishedPathtalk 02:34, 30 December 2023 (UTC)[reply]
    @TarnishedPath: the previous discussion was unanimous, and therefore pretty clear. The only grounds for reversion to the previous image is that it was there for a while is simply not true. VQuakr (talk) 03:28, 31 December 2023 (UTC)[reply]
    Incorrect by my reading. TarnishedPathtalk 04:16, 31 December 2023 (UTC)[reply]
    the previous discussion was unanimous My reading is that the image has been controversial since its first inclusion even before the attack -- after only days it was removed by Graywalls as unrepresentative. In June 2021, before Tarrio is indicted and arrested, User:Jason Quinn started a thread titled Propaganda image must go, Loki concurred. Now that the subject has been convicted, an always-controversial unrepresentative image has been demonstrated at RFC to have no consensus for inclusion. In the unlikely event the RFC was ruled to be "poorly worded" or "incorrectly closed", we'd just write a new RFC and re-ping everyone to demonstrate the image is too controversial for inclusion. No pre-conviction status quo is gonna hold as binding on future editors. Feoffer (talk) 06:05, 31 December 2023 (UTC)[reply]
    The 2020 diff you linked was for a different, related image than the one discussed in 2021 and 2023. It has the Betsy Ross background. No, the subject's conviction has precisely zero bearing on the selection of lead image. VQuakr (talk) 06:20, 31 December 2023 (UTC)[reply]
    Removing the Betsy Ross Flag does not do much to remove the fact that Tarrio is portrayed as something he is not. Jason Quinn made a lot of same arguments in that discussion as he did in the RfC. TarnishedPathtalk 06:26, 31 December 2023 (UTC)[reply]
    the subject's conviction has precisely zero bearing Well, not to put too fine a point on it -- before the conviction, some of us were willing to overlook a NPOV violation out of abundance of BLP caution; Post conviction, there's no possible BLP issues with using a mug-shot or a protest photo. Feoffer (talk) 07:08, 31 December 2023 (UTC)[reply]
    For what it's worth, even while supporting the gray background image over the flag background image, I supported what became option B over either. Option A at no point ever had "unanimous" agreement. Loki (talk) 07:12, 31 December 2023 (UTC)[reply]
    If it was reverted mere days after being added and has had multiple discussions challenging it, then it didn't have implicit consensus per WP:EDITCONSENSUS and shouldn't be left in following a non-consensus RFC. Part of the point of EDITCONSENSUS is that editors who object in that manner shouldn't be forced to immediately go through the entire dispute-resolution process or to aggressively assert a lack of consensus via editing (which would result in unnecessary busywork and could encourage edit-wars to "deny" something implicit consensus); my interpretation has always been that once someone has lodged an objection to a relatively-new edit, it can no longer gain implicit consensus no matter how much time passes, ie. any future RFCs that fail to reach a consensus on it will result in removal unless it's had explicit consensus confirmed for it since then. If the people who defended the image in 2020 or 2021 or were certain it had consensus, they should have started an RFC to settle the matter permanently; by quietly restoring it in 2020 and letting the discussion die in 2021, they merely deferred the issue, they didn't settle it. EDITCONSENSUS and QUO are for edits that many editors have seen and implicitly accepted which remained without controversy the entire time, demonstrating implicit consensus; they're not for things that remained in the article because people who liked them there were aggressive about putting them back in the face of objections or because nobody had the time and energy to start a proper RFC at the time. --Aquillion (talk) 23:08, 31 December 2023 (UTC)[reply]
    @Aquillion: that's not what actually happened, though. The image was contested because it had an obnoxious flag background, an alternative with a gray background was proposed, those present agreed it was acceptable, then it was added to the lead where it remained for the following two years. VQuakr (talk) 23:23, 31 December 2023 (UTC)[reply]
    That's not entirely my reading as evidenced by Jason Quinn making the similar arguments back then as he did in the RfC. Notably when the photo the non-flag background was proposed in 2021 Jason didn't form part of that sub-thread discussion, perhaps he was otherwise disposed or over it by that stage? Who knows, however the important factor to my reading is that an individual editor who had shown very significant opposition to the image never voiced an opinion on the non-flag photo. Per @Aquillion above, I don't see that consensus was ever formed, just that the issue was left to unresolved until the recent RfC. TarnishedPathtalk 01:42, 1 January 2024 (UTC)[reply]
    I mean, I don't actually think there's any denying that there was a rough consensus at the time. Not necessarily for the portrait image over the hat image though, but for the gray version of the portrait image over the flag version. My reading of the situation back there is that people assumed that that consensus carried over to the overall situation without actually discussing it. Maybe everyone was just tired of arguing. Loki (talk) 02:46, 1 January 2024 (UTC)[reply]
    For me what stands out is that the editor (Jason Quinn) who started the main thread Talk:Enrique Tarrio/Archive 2#Propaganda image must go talked about a lot more than just the Betsy Ross Flag and then when it got to the subthread Talk:Enrique Tarrio/Archive 2#Alternative image the only thing that was addressed was the Betsy Ross Flag and Jason Quinn wasn't part of that subthread discussion. Personally if I was the person proposing the alternative image I would have pinged the person who started the main thread, along with everyone else that was involved at the very least to ensure consensus. Better yet as @Aquillion suggested run a RfC. TarnishedPathtalk 05:56, 1 January 2024 (UTC)[reply]
    • Involved and I would partially endorse the close. As others pointed out, if there's no consensus this should roll back to the status quo. The closer should have said to further discuss alternatives instead. Nemov (talk) 17:53, 30 December 2023 (UTC)[reply]
    • This is getting confusing now. When I wrote "partial endorse", I was basing it on what the closer actually said (consensus against both pictures). Now those supporting the suit picture are using "partial endorse" to mean something completely different -- an interpretation of the closing statement that isn't, per the closer, what they meant at all. It would be helpful to treat the closing statement as the closer intended it rather than focus on two words out of context which happen to support your preference. — Rhododendrites talk \\ 14:48, 31 December 2023 (UTC)[reply]
      That's why I wrote "endorse as written", so there could be no misunderstanding about my meaning. TarnishedPathtalk 15:11, 31 December 2023 (UTC)[reply]
      Same. I agree this is confusing. Loki (talk) 00:01, 1 January 2024 (UTC)[reply]

    Stealth Canvassing for RFC

    Can anything be done about a controversial ongoing RFC on the names of deceased trans people, and this RFC being shared on a Discord server called "LGBT Wikimedians"? Comment revealed the post here, though since the person commenting is not being accused of impropriety, I didn't ping their talk page.

    Discord server posting is specifically called out on WP:CANVASSING as "inappropriate notification (and may be seen as disruptive)". Cuñado ☼ - Talk 18:06, 29 December 2023 (UTC)[reply]

    Do you have any reason to believe that the discussion refered to by LilianaUwU (btw this is obviously you starting a discussion about an editor, it's ridiculous that you didn't inform the person you mentioned) is designed to persuade [people] to join in discussions? I see you haven't bothered to ask LilianaUwU or anyone else about it before coming to WP:AN. Maybe we need a guideline about not jumping to negative conclusions about other users' motives or something. --JBL (talk) 20:56, 29 December 2023 (UTC)[reply]
    In addition to this, Cuñado was warned about casting these exact sorts of WP:ASPERSIONS only a few months ago. And then nearly got topic-banned from GENSEX for immediately running out and doing it again, literally days later. Loki (talk) 02:51, 30 December 2023 (UTC)[reply]
    Hi. Server mod here (speaking just for myself). One user gave a neutral pointer to the RfC on the 10th. While the server generally disallows discussion of ongoing disputes (a higher standard than held by the main Wikimedia community Discord), the mods left this mention (to which no one replied) because this was a discussion at WP:VPP, linked from WT:LGBT, so a very large audience was already aware of the RfC. On the 27th, during a discussion about inclusion of Near's legal name, a different user mentioned their intention to comment in the RfC, without endorsing any specific stance or encouraging anyone else to participate; there was then brief discussion of how the RfC's proposed rule would apply to Near. Under WP:INAPPNOTE, both posts were limited, with neutrally-worded messages, in a semi-transparent setting (server is publicly listed at WP:DISCORD and meta:Discord and open to anyone with a Wikimedia account). As to the remaining prong, partisanship, it may be tempting to assume that LGBT Wikimedians will be on the "pro" side in the RfC, but that's not necessarily the case. Personally I'm moderately opposed, although I've abstained from !voting so far. With all this in mind, I (again, speaking just for myself) stand by our decision to not remove these two policy-compliant mentions of the RfC's existence. And I commend Liliana for her transparency (above and beyond what's required by policy) in acknowledging that she had seen the RfC discussed on-server. -- Tamzin[cetacean needed] (they|xe|she) 21:58, 29 December 2023 (UTC)[reply]
    Come on, Cuñado, you've been extended confirmed for longer than I've been a Wikipedian, you could've sent me a notification despite the blue lock on my talk page. With that said, I know I've been blocked for canvassing before, so it's understandable to be worried... also, I did say I had intended to weigh in prior; this was true, and the link in that Discord server simply reminded me, as I had forgotten about it. LilianaUwU (talk / contributions) 23:56, 29 December 2023 (UTC)[reply]
    LilianaUwU my post here was not about you, it was about whoever posted in the Discord chat. I have seen people get in trouble for posting an RFC on a wiki project page, or pinging people on-wiki to join a conversation. Trying to drum up more participants on a Discord server seems even more obviously inappropriate. Cuñado ☼ - Talk 01:39, 31 December 2023 (UTC)[reply]
    Posting a neutrally worded statement and link on wikiproject talk pages or article talk pages is almost always OK, in my opinion. Pings, user talk pages, and offwiki, not so much. –Novem Linguae (talk) 09:50, 31 December 2023 (UTC)[reply]
    I wish I could remember the example, but WP:CANVASS came crashing down on someone who posted an RFC to a wikiproject that would likely vote the same as the poster. For example, if there were an RFC about whether the images of Muhammad should be displayed, someone could seek comments from WikiProject Islam or similar, and not seek comments from WikiProject Democracy or similar. Clearly that would be a form of WP:VOTESTACKING (part of WP:CANVASS). Posting this particular RFC to WikiProject Conservatism, for example, would clearly have generated a discussion about the poster canvassing, regardless of how neutrally worded.
    Votestacking aside, it seems that Discord is specifically called out as "inappropriate notification (and may be seen as disruptive)", and that's why I brought it up here. Cuñado ☼ - Talk 20:14, 31 December 2023 (UTC)[reply]
    I've heard of people told off for only posting to certain wikiprojects and warned not to do it again, but from my experience provided there was some reasonable justification for informing that wikiproject, in terms of outcome it's not considered a big deal unless it's something only noticed after the RfC is finished. This makes sense since unlike with a non-neutral notice or pinging random people without a clear rationale (or a poor rationale), it's something that can be easily corrected. On the "after outcome" think, this is why editors should always mention on the RfC that they've informed whatever wikiprojects. That way people can see what happened and decide if there's some wikiproject that was missed etc. Nil Einne (talk) 22:39, 31 December 2023 (UTC)[reply]
    Thanks nil Einne. I didn't notice previously but the wikiproject share was mentioned on the RFC, below in the comments section. Cuñado ☼ - Talk 17:40, 1 January 2024 (UTC)[reply]
    In my view, if an editor is concerned about a biased wiki project being informed, they can always inform wiki projects of their choice as well to balance it out. I don't see anything controversial about informing wiki projects, personally. –Novem Linguae (talk) 02:26, 1 January 2024 (UTC)[reply]
    • Comment. Though I am not very active, I am technically a moderator of the server as well. I can confirm what Tamzin said above. I am very paranoid about Discord stealth canvassing (and coverups thereof), so I checked the audit logs as well to see if messages were deleted from the server in the last 45 days. Only 1 WikiAuthBot message was deleted during that time-frame.
      The server does not hide previous messages from new users, so anyone here with a Discord account can verify that the only mentions of the RFC are the ones Tamzin described. –MJLTalk 17:43, 30 December 2023 (UTC)[reply]

    Can an uninvolved admin please step in over toxicity and BATTLEGROUND at darts-related pages?

    Affected pages span at least 2024 PDC World Darts Championship, 2023 Grand Slam of Darts, Wikipedia:WikiProject Darts, and their associated talk pages, as well as user talk pages.

    Edit summaries should be checked too: (Redacted) (diff) and (Redacted) (diff) and (Redacted) (diff) JoelleJay (talk) 19:23, 30 December 2023 (UTC)[reply]

    I'm still checking the issue, but I've blocked Penepi for a week for now for their personal attacks. Any uninvolved admin may lengthen the block if they see fit. Isabelle Belato 🏳‍🌈 19:30, 30 December 2023 (UTC)[reply]
    I've extended Penepi's block to indefinite due to the sheer extent and cruelty in all the shown diffs. Isabelle Belato 🏳‍🌈 19:37, 30 December 2023 (UTC)[reply]
    Thank you for the very quick response! I think that editor was the main antagonizer in these articles. The atmosphere there is still pretty BATTLEGROUNDy and OWNy, but that can hopefully be remedied with more editors looking into it and isn't so urgent. JoelleJay (talk) 19:43, 30 December 2023 (UTC)[reply]
    I'll note that ItsKesha appears to have been edit warring on some of those articles. Since it's stale now, I don't think a block is needed, but they should consider themselves formally warned not to do so again.
    In the future, they should consider seeking administrative assistance when they see another user personally attacking them, instead of allowing it to go on. Isabelle Belato 🏳‍🌈 19:52, 30 December 2023 (UTC)[reply]
    IMO there's been some "goading" from ItsKesha, as a minimum. Does "Nobody cares about the opinion of you logged out losers" [3] get over the civility bar? or "Sad act"? (I've been editing there but trying not to be "involved") Nigej (talk) 20:08, 30 December 2023 (UTC)[reply]
    I'll remove those comments and I profusely apologise to all involved for such embarrassing, insulting and time-wasting behaviour. All my warmest wishes, ItsKesha (talk) 20:14, 30 December 2023 (UTC)[reply]
    @Nigej: I'm still reading all the linked pages, but yes, I agree with you that ItsKesha didn't facilitate things. I'll also note that their behavior at Talk:2024 PDC World Darts Championship has been poor. Isabelle Belato 🏳‍🌈 20:14, 30 December 2023 (UTC)[reply]
    In my experience, ItsKesha is disruptive and repeatedly engages in personal attacks. In addition to the edits at the darts talk page mentioned above which they have now removed (calling other editors 'sad act', 'losers' etc.), there are also edits elsewhere such as this ("lol @ u") and this (calling another editor an "oddball") which are indicative of a wider attitude problem. Indeed, a quick look at their contribs in general show a clear pattern - multiple reverts to the same article(s) over & over again. They seem to obsess over an article and try and bully other editors into keeping their preferred version through reverts and insults, and once achieved they move onto another article... GiantSnowman 20:29, 30 December 2023 (UTC)[reply]
    Other edits by ItsKesha at the talk page which remain up - "You don't half talk some shite" and "you talked a load of shite". I cannot see Penepi's edits that have been revdeled, but how do they compare to ItsKesha's comments/conduct? GiantSnowman 20:41, 30 December 2023 (UTC)[reply]
    Penepi's were about 2000x worse... JoelleJay (talk) 20:50, 30 December 2023 (UTC)[reply]
    OK, then what's 1/2000th of an indef block... GiantSnowman 21:35, 30 December 2023 (UTC)[reply]
    @GiantSnowman Here's a much milder example of the PAs (this one was at least removed by Penepi). Can you please revdel that span of history? The rest of the comments in that chain are pretty typical for interactions here. JoelleJay (talk) 21:58, 30 December 2023 (UTC)[reply]
    E.g. their response prior to deleting that comment. JoelleJay (talk) 22:08, 30 December 2023 (UTC)[reply]
    Can you please confirm exactly what edits to revdel? GiantSnowman 10:23, 31 December 2023 (UTC)[reply]
    @GiantSnowman Have you looked at those diffs? It should be clear from the content which span of the history should be revdeled. JoelleJay (talk) 20:54, 31 December 2023 (UTC)[reply]
    You've asked to revdel a span, but provided one diff.... GiantSnowman 11:29, 1 January 2024 (UTC)[reply]
    @Isabelle Belato JoelleJay (talk) 20:55, 31 December 2023 (UTC)[reply]
    @JoelleJay: I've revdel'ed the more egregious one from the ones you posted here. Isabelle Belato 🏳‍🌈 17:35, 1 January 2024 (UTC)[reply]
    Should this diff also have its edit summary revdeleted? ChaotıċEnby(t · c) 19:43, 30 December 2023 (UTC)[reply]
    Thanks. That should be all. Isabelle Belato 🏳‍🌈 19:55, 30 December 2023 (UTC)[reply]

    I don't know why there is so much animosity over darts, but there is. While Penepi has shown the worst behavior, ItsKesha's behavior has been subpar, usually adding more heat than light to the discussions they participate in. I wonder if a formal warning to be more WP:CIVIL and avoid commenting on other editors would suffice for now. Isabelle Belato 🏳‍🌈 20:39, 30 December 2023 (UTC)[reply]

    You mean like the previous warnings for disruption/conduct/civility that litter their talk page going back 3 years? See also Wikipedia:Administrators' noticeboard/IncidentArchive1054#User:ItsKesha and Wikipedia:Administrators' noticeboard/Archive344#ItsKesha's removal of major WP:RS contents claiming then not notable based on personal views and accusing me of lack of sourcing tag when very line of the aricle was complient with WP:PW/RS and this edit warring warning from October 2021. They were also blocked in July 2022 for personal attacks. Clearly all of this has had zero effect on ItsKesha given they continue the behaviour. GiantSnowman 20:49, 30 December 2023 (UTC)[reply]
    Yes it had zero effect on me when I was accused of violating copyright and plagiarism and nothing was done about it by administrators when I reported it. Remind me why should I have any faith in the process of reporting somebody to the administrators? All my warmest wishes, ItsKesha (talk) 12:31, 31 December 2023 (UTC)[reply]
    TBF, ItsKesha has been trying to bring darts articles in line with policy for a while and has been met with quite hostile resistance from what seems like a LOCALCON walled-garden, including from another now-blocked-and-TBANNED editor. Their approach has often been antagonistic, passive-aggressive, and POINTY, but IMO the responses to them by some of the darts editors have been way out of proportion and non-policy-based to boot, so I can at least understand a bit of their frustration. JoelleJay (talk) 21:50, 30 December 2023 (UTC)[reply]
    Thing is, being frustrated isn't a reason to not be civil. I'm equally as frustrated by some of the responses on that page, but you can't make such aggressive comments here. I wouldn't consider myself uninvolved at this stage, so maybe one who is could have a word with all parties. Lee Vilenski (talkcontribs) 22:38, 30 December 2023 (UTC)[reply]
    I've had run-ins with ItsKesha in the past, so will leave it to others, but suggest a final warning for civility/personal attacks/edit warring for ItsKesha, with an indef block if it happens again. GiantSnowman 10:24, 31 December 2023 (UTC)[reply]
    I will note that since this discussion started, they continue to repeatedly revert/edit war with other editors, see 1, 2, 3. GiantSnowman 12:36, 31 December 2023 (UTC)[reply]
    And those reverts show yet another example of them not understanding a policy they’re trying to enforce. In this case the difference between the concepts of primary&secondary sources on one hand, and first-, second- and third-party sources on the other hand. Tvx1 12:56, 31 December 2023 (UTC)[reply]
    How are the Professional Darts Corporation are not a primary source for the Professional Darts Corporation World Darts Championship? ~~~~ All my warmest wishes, ItsKesha (talk) 13:15, 31 December 2023 (UTC)[reply]
    Because primary≠first party. How can you not understand that??Tvx1 13:42, 31 December 2023 (UTC)[reply]
    I suppose this is the exact tone we should be taking when trying to have a discussion. Right admins? All my warmest wishes, ItsKesha (talk) 13:57, 31 December 2023 (UTC)[reply]
    Sorry, but that’s on oversimplification of the issue. The reality is that they try to force these articles to match their view of what the policies should be. The multiple talk page discussions going on right now on the 2024 PDC World championship article’s talk page show that they have little actual understanding of the policies they quote. And when multiple editors point out the incorrectness of their arguments, they show no intent to accept that.
    Therefore, seeing as they already received a topic ban elswhere but changed nothing of their behavior but rather moved to another topic to do just the same, I strongly suggest an indefinite block until such time they can prove they are here to build an encyclopedia. At the very least they should be subjected to a topic ban from darts. Tvx1 12:37, 31 December 2023 (UTC)[reply]
    Yes, given the ongoing reverts this morning (after this discussion started) which I have just noted and linked to above, it is becoming increasingly clear that only an indef or topic ban will stop ongoing issues. I'd obviously prefer a topic ban to an indef, but I'm not convinced that with a topic ban they won't just direct their attention elsewhere. GiantSnowman 12:39, 31 December 2023 (UTC)[reply]
    However we can't put all the blame with ItsKesha. Comments like your's just now "I still don’t understand why something that was used for years without anyone having a problem with it, has now become all but unacceptable." (and other similar comments by other editors) show a reluctance to listen to comments from "outsiders". Nigej (talk) 12:56, 31 December 2023 (UTC)[reply]
    Nigej I have posted my thoughts at the bottom of the thread, but in line with my view posted there, this has been an ongoing issue for about 12 months, and part of the consequence has been a massive drop in darts articles this year. I think frankly, that people are fed up with ItsKesha and their presence is enough for people to feel backed into a corner and come out fighting. That is not okay of course, and I am guilty of that myself to a degree, but this is something thats been building for twelve months, comes to a head during the worlds when more editors are active, and will no doubt happen again next year if left as is. Dimspace (talk) 23:37, 31 December 2023 (UTC)[reply]
    How much of the dropoff in darts editing this past year could be attributed to JRRobinson being TBANned from darts and then indeffed? JoelleJay (talk) 00:04, 1 January 2024 (UTC)[reply]
    That has probably had some impact. But there have also been ongoing arguments over notabilty. The Darts project sadly has not established a structured notability scale for events, so in the absence of one there have been disputes over what is notable, and predictably, from what I saw earlier in the year, ItsKesha was at the centre of that with their "interpretion" of notability criteria. But you are correct, JRRobinsons absence would have had an impact. Equally, people who have watched from the sidelines like myself who could contribute more don't have the inclination to throw their hat in that particular warzone :D Dimspace (talk) 00:16, 1 January 2024 (UTC)[reply]
    Should add, a lot of have fallen foul of issues of sourcing, and the primary sources issue, https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Darts#Better_sources_for_darts_articles which I know is something Itskesha has been hot about (I'm not getting into a right or wrong on that one, but thats been part of the reduction as well). But again as noted elsewhere, the approach from people like ItsKesha has very much been "not sourced properly DELETE IT" "doesnt fill a certain criteria DELETE IT" as opposed to how can we work together to remedy those things Dimspace (talk) 00:25, 1 January 2024 (UTC)[reply]
    There is a notability guideline for darts: WP:NSPORT, which requires the subject to meet GNG and on top of that requires all athlete articles actively cite at least one IRS SIGCOV source. ItsKesha's interpretation of notability criteria is correct. JoelleJay (talk) 00:20, 1 January 2024 (UTC)[reply]
    Working with others to establish a notability list for Darts and listing the guidelines, being specific, explaining reasoning, however, would be far more productive, than just stamping feet and fighting. People can see a wall in their path and just knock it down, or they can work together to cross it. Dimspace (talk) 00:29, 1 January 2024 (UTC)[reply]
    What I would add, is WP:NSPORT is largely aimed at notablity of individual sports men, women and teams. When it comes to events, it is very vague, generalised, and extremely open to interpretation, but, any discussions on darts events notability have just been "its not notable" "yes it is" "no it isnt" as opposed to objective. WP:EVENT is possibly more relevant. but. getting sidetracked a bit here. But I think formalising event notability over the course of 2024 could solve some issues. Dimspace (talk) 00:35, 1 January 2024 (UTC)[reply]
    Well, any notability criteria created for darts events will have to be a very strong predictor of GNG and SUSTAINED independent secondary significant coverage (per NEVENT). Project-level notability criteria are treated as essays and hold zero weight at AfD, so it really wouldn't be productive to pursue this if the hope is to protect certain classes of articles from deletion. Pinging @Nigej who also has experience at NSPORT discussions and might have more background on non-biography stuff. JoelleJay (talk) 00:44, 1 January 2024 (UTC)[reply]
    Personally I would not view it as protecting certain classes from deletion, but, having an established, discussed, agreed, list of notable events, is a lot better than having editors fighting with each other over their perception of notability. (as long as those establishing, discussing and agreeing are objective and able to look at more than one point of view lol) 01:16, 1 January 2024 (UTC)
    What is "ItsKesha was at the centre of that with their "interpretion" of notability criteria" even in reference to? All my warmest wishes, ItsKesha (talk) 01:54, 1 January 2024 (UTC)[reply]
    Sorry, but what is that supposed to mean? I listen very much, I just say that I don’t understand why there is such a big drama about this. I have even offered you a simple solution to your biggest concern with the content. I find this a really low blow from you. Meanwhile the user that this discussion centers on, who doesn’t show any less reluctance to listen to outsiders, has even broken WP:3RR. Tvx1 13:18, 31 December 2023 (UTC)[reply]
    It seems from comments below that ItsKesha finds some of your comments "low blows" too. Nigej (talk) 14:44, 31 December 2023 (UTC)[reply]
    I don’t see any comment that references me below at all. Your snide remarks are totally uneccesary here. They do nothing but detract from the issue at hand here. Tvx1 15:34, 31 December 2023 (UTC)[reply]
    I mean you've just made a comment here advising @Lee Vilenski to "learn to read". I'd say that's definitely a low blow. All my warmest wishes, ItsKesha (talk) 18:20, 31 December 2023 (UTC)[reply]
    No, that’s a comment on the point in reaction to someone who clearly misread a comment I made in that discussion. But that doesn’t even matter. It’s my behavior that was reported, it was yours and that is what you should discuss.Tvx1 19:13, 31 December 2023 (UTC)[reply]
    It is a bizarre comment over six months after the last comment in that thread. Lee Vilenski (talkcontribs) 20:46, 31 December 2023 (UTC)[reply]
    • I see that the arguments from the talk page are starting to leak into here. Have any of the involved parties asked for assistance from uninvolved editors at WP:RSN about whether those PDC reports should be considered a primary source? Moving on from that, can someone point me to which topic ItsKesha has been banned from? I see nothing on their talk page or at WP:AEDR. I think a final civility warning to ItsKesha should help reduce the heat in these discussions, and I wouldn't oppose a WP:1RR sanction to prevent slow edit wars. Concerning the overall darts topic, I think a reminder to all participants to remain civil, respect WP:BRD, and seek assistance from third parties when a discussion appears to be going nowhere wouldn't go amiss. Isabelle Belato 🏳‍🌈 13:46, 31 December 2023 (UTC)[reply]
      In future I won't even try and collaborate to improve these articles, I'll just work independently because this is so unbelievably boring. All my warmest wishes, ItsKesha (talk) 14:08, 31 December 2023 (UTC)[reply]
      I do not think this is the answer you want to give. Saying you will not collaborate is a big no-no and the alarm bells are ringing louder for me. GiantSnowman 14:10, 31 December 2023 (UTC)[reply]
      See, this is another indication that this user is WP:NOTHERE to build an encyclopedia. Tvx1 15:33, 31 December 2023 (UTC)[reply]
      I'll edit to improve articles, I just won't bother asking questions to the community. Why should I even try when I am made out to be the villain and targeted simply for asking a question? Look here and read the first four responses I received. Three of them are absolutely pathetic and I won't subject myself to this going forward, and you can't sway my opinion. All my warmest wishes, ItsKesha (talk) 15:48, 31 December 2023 (UTC)[reply]
    ItsKesha"read the first four responses I received." the first few responses, my response included are not ok. However, bear in mind two things. a) Nobody had a foggiest idea what stats you were claiming were against WP:SYTH, and even after discussion, and head scratching b) it was established very quickly that they were not against WP:SYNTH. And here's the thing, throughout that thread you refuse to actually explain why you felt they were against WP:SYNTH (Or even which stats you thought were against WP:SYNTH. All you did was repeatedly quote "do not combine different parts of one source to reach or imply a conclusion not explicitly stated by the source". You wouldn't actually elaborate on what your issue actually was. So a month long argument (Where nobody actually understood what your issue was in relation to WP:SYNTH ends with "ItsKesha was quoting wiki policies that didnt even apply" again. And so the cycle starts again. Dimspace (talk) 23:47, 31 December 2023 (UTC)[reply]
    • Again, saying you are going to continue editing (without dealing with the attitude and behaviour concerns that have been raised here and elsewhere) AND that you are not going to collaborate indicates you will continue disruption. Comments like "you can't sway my opinion" means there is little point in the community working with you as nothing we do will have a positive effect. In short, the more you post, the more supportive I become of an indef block as the only way to prevent ongoing issues. GiantSnowman 15:54, 31 December 2023 (UTC)[reply]
      So not raising issues is disruption, but raising issues is disruption. Brilliant. All my warmest wishes, ItsKesha (talk) 18:17, 31 December 2023 (UTC)[reply]
      There is a whole lot of background to why these were the first four reactions you got from these people. These are the many interactions you had with them during the last year or so, including on the article on the previous edition of the sports’ world championship. "you can't sway my opinion" is the core attitude issue you have been displaying throughout that period and is the reason why were here, yet you show no understanding at all. Tvx1 16:39, 31 December 2023 (UTC)[reply]
      I think ItsKesha needs an indefinite block for their behavior discussed above. The battlegrounding is just too much. Thanks -- Deepfriedokra (talk) 18:04, 31 December 2023 (UTC)[reply]
      Can you explain the "whole lot of background" then, so I can learn from it? All my warmest wishes, ItsKesha (talk) 18:17, 31 December 2023 (UTC)[reply]
      The battleground behavior is detailed above, and I believe you have responded earlier. Thanks -- Deepfriedokra (talk) 18:27, 31 December 2023 (UTC)[reply]
      I would say some of the darts "regulars" have displayed quite a bit more battlegrounding on the darts pages than ItsKesha. Those pages need a serious overhaul by uninvolved editors. JoelleJay (talk) 20:53, 31 December 2023 (UTC)[reply]
      See that’s the core issue here. People like the reported user and you unfairly treat the regular editors of these articles like a nuisance. Like an annoying band of rebels that need to be squashed. I’m not even part of that community and I’m still appaled by the treatment they have been given. Maybe what it needs is not for outsiders to barge in with a lecturing attituted trying to enforce their personal views. Tvx1 14:19, 1 January 2024 (UTC)[reply]
      P&Gs are not really "personal views"... JoelleJay (talk) 17:55, 1 January 2024 (UTC)[reply]
      Interpretations of them are. Multiple editors on those talk pages have carefully read those guidelines and properly adressed many of the incorrect claims regarding these guidelines and policies in the talk page discussions. Yet instead of reading and accepting these replies and collaborating, you and the reported user keep treating these people, who actually have invested a considerable amount of time in reading and adressing your concerns, as a pest that needs to be eradicated.Tvx1 19:04, 1 January 2024 (UTC)[reply]
      @Tvx1: please tone down your rhetoric. No one here is treating the regular darts editors as "a pest that needs to be eradicated." An uninvolved user saw an issue occurring on a certain topic of the Wikipedia and we are discussing to reach a consensus on whether this is a chronic issue and how to best deal with it. Isabelle Belato 🏳‍🌈 20:42, 1 January 2024 (UTC)[reply]
      @Isabelle Belato, this comment shows clearly what I meant. A call for outside editors to come in an and overhaul the project. Treating the current regulars as if they have no good intentions or at the very least wouldn’t be willing to colleborate constructively. If find that very respectless and I can sympathise in a way with how this people have reacted to such treatment. Tvx1 00:13, 2 January 2024 (UTC)[reply]
      I said some of the darts regulars, which includes two editors indeffed for NPAs and battleground behavior... And content can need to be overhauled without it impugning the motivations or collegiality of other editors. There are still synth issues1 and misunderstandings of notability, PRIMARY, and independence that need to be addressed. JoelleJay (talk) 02:13, 2 January 2024 (UTC)[reply]
      I tried to offer my opinion -- that the tournament draws and schedules formulated and released by the tournament itself are primary (and non-independent) as they are original materials ... close to an event ... written by people who are directly involved -- but was told by Tvx1 that my comment didn't make sense and that I was incorrectly conflating secondary sources and independence... JoelleJay (talk) 21:12, 31 December 2023 (UTC)[reply]
      JoelleJay What I would say, is when the battle is already raging, any opinions are probably going to be shot down because peoples backs are already up. Now probably isn't the time to be saying whats wrong with this years article, emotions are running too high. I think there needs to be a period of calm, and a built towards next year to be honest. Dimspace (talk) 23:51, 31 December 2023 (UTC)[reply]
      Can we please leave the content discussion out of this? This is not the venue for this.Tvx1 04:14, 1 January 2024 (UTC)[reply]
    I feel like I summarised it in the 2023 Worlds talk page. Basically Kesha seemed to come in from out of the blue, and unilaterally decided that about half the article failed some policy and just slapped a ton of "fix this" templates all over the place; as opposed to... well, fixing it. That same attitude seems to have continued over the year, and is coming to a point again now during the 2024 Worlds. There was little collaboration until I had to call out the 3RR that was ongoing, and even then I don't think any of the discussions really amounted to much. Hence why there's still such an impasse over the whole thing.
    The sticking point over notability is going to remain though. Darts is still a relatively niche sport, it doesn't have the same amount of eyeballs on it as other events that Sky and ITV broadcast; and because of that the resulting neutral coverage is also lacking. Snooker — another of matchroom's portfolio — gets a lot from the BBC because they actually broadcast it; but unfortunately they don't offer that same level of effort to darts or pool. 🇮🇪 TheChrisD {💬|✏️} 02:22, 1 January 2024 (UTC)[reply]
    You accused me of being "biased against most darts articles on the Wiki" for nominating an article for deletion. All my warmest wishes, ItsKesha (talk) 03:28, 1 January 2024 (UTC)[reply]

    I can’t believe we’re letting us be mocked like this. It’s New Year’s Eve for crying out loud, we should be celebrating with our families and friends, not be dealing with this. Granted, maybe for some of you it’s maybe already the morning of New Year’s Day, but still. — Preceding unsigned comment added by Tvx1 (talkcontribs)

    Ok, throwing my two-pennorth in as I have been watching the talk of all darts pages since late last year after things blew up on the 2023 World Championship talk. Darts articles are not perfect, and there are areas as have been brought up by people like NigelJ etc where things can be improved, but there is a way to work with existing editors, discussion, compromise, and explaining decisions. Itskesha since late in 2022 (as far as I am aware, it could even be earlier) has behaved as a bull in a china shop on darts articles. Filling articles with various banners, sourcing need, 1st party sources, etc etc, kicking up a storm over notability, and in many instances citing Wikipedia policies that when actually looked at have zero relevance to what he is flagging. His general passive-aggressive approach (for example, his constant even when baiting people, well wishes) has got a lot of peoples backs up. The net effect has been in 2023 the number of darts articles has dropped massively, many events no longer have articles for them, and a lot of editors have simply backed off the darts community completely. For much of the year I have just been watching, and yes, over December I have decided to butt heads with him, which I probably shouldn't, but honestly, my impression is very much that while he maybe intends well, his forcible opinions (which very often are based on poor interpretations of policy), and his general passive aggressive, non-compromising approach, is a disruption to the Darts community as a whole. As I say that as someone who does not edit on Darts, but read the articles, and have been paying very close attention to talk. (But yes, I will admit I've been like a dog with a bone over the last month). As I say, Darts pages are not perfect, but there are ways of working with the existing editors to improve and develop the pages, and going in, sticking banners everywhere, misinterpreting wiki policies, and being at the centre of every single argument, are not the way to improve things. His aspproach alsi is very much "This doesn't fit the (poorly interpreted) rules so delete it", as opposed to "how can we rework it to make it fit the policy guidelines better"Dimspace (talk) 23:30, 31 December 2023 (UTC)[reply]

    Just to add, this all started last year. https://en.wikipedia.org/wiki/Talk:2023_PDC_World_Darts_Championship and has gradually built over the course of 2023. So whats going on on the talk page for this years World Championship is not the full reflection, this has been a 12 month brewing battle. Dimspace (talk) 23:32, 31 December 2023 (UTC)[reply]
    Also, it appears at least two regular editors of darts articles have already ended up indefblocked because of this ongoing situation.Tvx1 19:18, 1 January 2024 (UTC)[reply]
    Not sure who posted this last comment ^^ but yes, this is a side effect, that Darts is losing its most "passionate" editors because of this ongoing conflict. — Preceding unsigned comment added by Dimspace (talkcontribs)
    • Related, would an admin please look at Draft:Alex Spellman and this change an IP tried to make to sports notability? I blocked the first IP as they were being generally disruptive but there's not enough with the new one desipite my spidey sense that it's blocked editors logging out. I know that JRR is far from the only problematic one in this area, but it's who it reads to me. Wikipedia:Sockpuppet investigations/JRRobinson/Archive exists, but nothing we can do with IPs so I've not bothered filing Star Mississippi 16:16, 1 January 2024 (UTC)[reply]
    Without sidetracking completely, " Have won an event hosted by either the Professional Darts Corporation or British Darts Organisation." yes, support. " Have participated in the PDC World Darts Championship." as someone who loves the sport of darts, no, not even close. Participating in the worlds is not notable. For me notablity would not start until they reached the last 16, or had multiple appearances in the world championships. A single appearance is not even close to notable. I would say 90% of big darts fans would have to google who Alex Spellman even is :D Dimspace (talk) 16:24, 1 January 2024 (UTC)[reply]
    This is again a discussion we should not hold here. This is not the venue. So, please focus on the ANI report at hand. This section is already lengthy enough as it is. Tvx1 19:28, 1 January 2024 (UTC)[reply]

    Section break

    Okay, I hope this is appreciated but I decided to please a section break here because the above discussion was suffering from a lot of sidetracking and became difficult to follow. So I hope we can refocus on the issue at hand. The reported user has shown no insight into their behavior, has no demonstrated to have headed lessons from a previous topic ban and has not shown any willingness to change their attitude in the right way. Therefore I think it would be best to try to find a consensus on some action. Personally I still feel WP:NOTHERE applies.Tvx1 00:20, 2 January 2024 (UTC)[reply]

    Probably wise, but remember that the raised topic wasn't about a specific user. There has been one block already. I agree there needs to be something done to stop the atmosphere around these types of articles. Lee Vilenski (talkcontribs) 09:48, 2 January 2024 (UTC)[reply]
    Well, one other specific user WAS discussed following the block and I think an action considering them should be taken now. Especially considering their contributions here.Tvx1 10:12, 2 January 2024 (UTC)[reply]
    We should move to discussion about what (if any) action should be taken against ItsKesha given the conduct highlighted above. I think the options are (1) final warning (2) topic ban from darts, widely construed or (3) indef block. GiantSnowman 18:59, 2 January 2024 (UTC)[reply]

    NARMADA PUSHKARAMS 2024

    The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.


    Sir,

                 Good Afternoon.
    

    it is seen that you had mentioned the dates of upcoming NARMADA PUSHKARAMS as April 22–May 5, 2024. As per Telugu Panchangam, the dates of Narmada Pushkarams are shown as " from 01-05-2024 to 12-05-2024. This creates confusion. Kindly appraise me the exact 12 day period of Narmada Pushkar for the year 2024.

                                                                                      THANKING YOU SIR
                                                                                       I.S.N MURTHY @ HYDEARABAD 49.204.29.125 (talk) 07:05, 31 December 2023 (UTC)[reply]
    
    This question is best asked at Talk:Narmada Pushkaram. I will do so. Phil Bridger (talk) 10:11, 31 December 2023 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    S201050066 again

    User:S201050066 has resurfaced and posted messages on my talk page and User:Tenryuu. These are his accounts:

    It seems he is now able to create accounts again. Andykatib (talk) 11:43, 31 December 2023 (UTC)[reply]

    Thanks @Panamitsu: for your help in reverting S201050066's attacks. I have filed a report on WP:ANI. Andykatib (talk) 11:44, 31 December 2023 (UTC)[reply]
    There is a 22.3 now. —Panamitsu (talk) 11:49, 31 December 2023 (UTC)[reply]
    Thanks for doing some of the reversions, Andykatib. Could we get yet another IP range block with account creation disabled? —Tenryuu 🐲 ( 💬 • 📝 ) 16:13, 31 December 2023 (UTC)[reply]

    CommanderWaterford unban request

    The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.


    CommanderWaterford (talk · contribs · logs) has requested an unban through the standard offer. (community ban discussion)

    Hello Wikipedia Community, I hope this message finds you all well in this festive season. I'm reaching out today, on December 30, 2023, to appeal after two and a half years my ban from English Wikipedia, which has been in place since May 2021. Looking back, I truly wish I could turn back time and undo the mistakes that led to this. I made several stupid mistakes (like copyright violations) but more importantly, I was often kind of rude to other editors, not presuming good faith in their edits or contributions, when I definitely should have. The fact that I made thousands of edits every single day gave me the misconception that I was always in the right, that I was someone more important than others. It made me kind of blatantly arrogant and know-it-all. I didn't realize then how my actions were out of line with what Wikipedia stands for—being obsessed with the edit count. I'm genuinely sorry for any trouble I caused and for not being a positive influence in the community. Since my ban, I've been engaged with ESWiki and WikiData almost daily; but far, far away from the hours I spent years ago - especially in the pandemic - every day on ENWIKI. I've stayed out of trouble and really thrown myself into contributing in a meaningful way. In the aftermath, I can honestly say that I've learned a lot about respecting guidelines and working together with others. I miss being part of the ENWIKI community and want to make amends. My heart's still with ESWiki, but I'd love to bring my perspective back to English Wikipedia. I know about the WP:StandardOffer, and I'm ready to stick to it. I promise to be respectful, helpful, and totally in line with Wikipedia's rules. I totally get that this appeal means asking for your trust again and for many of you it will definitely not be easy, but I'm ready to prove that I can be a responsible and positive member of ENWIKI. Thank you for considering giving me another chance. Happy Holidays to you all, and I'm looking forward to hopefully making a constructive comeback. Regards, CommanderWaterford
    — Ingenuity (talk • contribs) 15:15, 31 December 2023 (UTC)[reply]
    • While this is certainly a better request than some that come here, to me, there are still too many questions and unresolved issues to unhesitatingly say that i would support the SO for CommanderWaterford. I don't want to come across harshly, i mostly fall in the Almost Everyone Should Be Able To Edit camp, so if i phrase them as questions to him perhaps my meaning is clear and it's also clear i hope for good answers:
    What “mistakes that led to this” are you referring to?
    Do you mean your continued assumption of bad faith, that many actors in the discussion which led to the current indef block were either incompetent or out to get you?
    In the category of “kind of rude” would you include this arbitrary, unbelievable process of a single sysop with not even having 1/3 of my edits being unsatisfied with my behaviour because I did not answer properly in their eyes and the only comment I will make on this witch hunt and I already demonstrated it a thousand times so no need to repeat it. If you still think so, I have to accept this but that also would mean that you are free to disable my account immediately or would you say that these (and many other examples) are undeniably fully rude and disrespectful?
    How is it that you didn't realize then how my actions were out of line with what Wikipedia stands for then but do now, i.e., what has changed in you and for you?
    Would you ~ and what reasoning would you use ~ accept a request from a user whose block log already contains the phrase User has accepted there were issues in the past, and committed to do better regarding their last unblock? How are we to accept essentially the same words from you this time? Happy days, ~ LindsayHello 17:28, 31 December 2023 (UTC)[reply]
    CW's responses, copied from their talk, are as follows:
    Do you mean your continued assumption of bad faith, that many actors in the discussion which led to the current indef block were either incompetent or out to get you?
    • I was pretty upset 2 and a half year ago, so at this time I would have answered yes to this question. In retrospect, it was total nonsense. As I said in the appeal - I was in the stupid idea of just being the most active editor at this time my opinion would valued more than others
    In the category of “kind of rude” would you include this arbitrary, unbelievable process of a single sysop with not even having 1/3 of my edits being unsatisfied with my behaviour because I did not answer properly in their eyes and the only comment I will make on this witch hunt and I already demonstrated it a thousand times so no need to repeat it. If you still think so, I have to accept this but that also would mean that you are free to disable my account immediately or would you say that these (and many other examples) are undeniably fully rude and disrespectful?
    • Without a doubt, fully rude and disrespectful.
    How is it that you didn't realize then how my actions were out of line with what Wikipedia stands for then but do now, i.e., what has changed in you and for you?
    • In me? 2 Heart Attacks in 2023. I honestly did not care much in 2021 about Wikipedia's collaborative aspects, my Ego and Edit Count were unfortunately much more important to me at that time.
    Would you ~ and what reasoning would you use ~ accept a request from a user whose block log already contains the phrase "User has accepted there were issues in the past, and committed to do better" regarding their last unblock? How are we to accept essentially the same words from you this time?
    • I would probably not if the request would come soon after the block and if I would not recognize any insight.
    — Ingenuity (talk • contribs) 20:19, 31 December 2023 (UTC)[reply]
    • Oppose this is not their first indefinite block/ban. They were already indef'd once before they were banned, successfully appealed it, and then went back to doing the exact same things. My standard for unbans has always been To support an unban the editor needs to convince me that the potential benefits to the Encyclopedia outweigh the known risk of disruption. That's true for a first unblock/unban, but even more true for a second.
      In short, this user was given a second chance and said essentially the same thing as they did above and then they went on behaving poorly. I do not support giving a third chance. TonyBallioni (talk) 22:58, 31 December 2023 (UTC)[reply]
    • I recall this editor well and he's simply too prolific to manage. Monitoring and checking that quantity of edits isn't feasible, and I'm unwilling to support his return without monitoring and checking. So for me this is a non-starter.—S Marshall T/C 00:45, 1 January 2024 (UTC)[reply]
    • Ick. I had hopes that my asking certain questions would trigger some reflection in CW, and maybe the first couple did. The response to the final, however, makes it impossible to accept this request: He, himself, says he would likely not accept if it came soon after the block (OK, we're two and a half years into it) and "if I would not recognize any insight." I'm afraid there isn't sufficient recognisable insight, so oppose. Happy days, ~ LindsayHello 09:51, 1 January 2024 (UTC)[reply]
    • Meh. I find this unconvincing. For one, This would be their second unblock. Second, I am concerned about how they would deal with disputes with other editors. They mention that they edited eswiki and Wikidata; hovewer their edits thereat Wikidata appear to be virtually 100% interwiki or description tweaking, and as such don't tell me anything about it. I am less certain about their track record on eswiki given that I don't speak spanish, hovewer, what I found likewise doesn't convince me they would work well with other editors, given that their talkpage edits appear to be mostly translation attributions; and the user talkpage edits are mostly templated (speedy deletion) notices. I am also still trying to wrap my head around what to make of es:Special:Redirect/revision/150296768#Usuario expulsado de la Wikipedia inglesa viene a cometer los mismos errores acá, but it doesn't look great. Victor Schmidt (talk) 11:56, 1 January 2024 (UTC)[reply]
    • Oppose My viewpoint only, but I don't think that we need an editor whose username is that of a fictional serial rapist and domestic abuser. (previously discussed about half way down this section). I'm unconvinced that even a name change would be useful; after all, it doesn't address why it was chosen in the first place. Black Kite (talk) 12:08, 1 January 2024 (UTC)[reply]
    • Oppose. I was involved in the second indef discussion, and I remember what a damned mess that was. Like Tony, I feel we should be cautious when judging a second request to lift an indef block, and I just don't find the unblock request convincing, given CW's documented history of making commitments that he immediately disregards. ♠PMC(talk) 16:03, 1 January 2024 (UTC)[reply]
    • Oppose request and answers to LindsayH don't convince me we won't be right back to the old problems. CW lacks the temperament for a collaborative editing environment and per Victor, their edits elsewhere don't show behavior has changed. Time served is not enough to indicate this is no longer a necessary block. Star Mississippi 17:55, 1 January 2024 (UTC)[reply]
      Can someone find the link to the 2022 request referenced here here and at User_talk:CommanderWaterford/Archive_1#Sorry_to_hear_about_your_troubles. Thanks! Star Mississippi 18:17, 1 January 2024 (UTC)[reply]
      @Star Mississippi: it's Special:Redirect/revision/1066660412#Request for lifting of community block of Commander Waterford. Victor Schmidt (talk) 18:43, 1 January 2024 (UTC)[reply]
      Thanks @Victor Schmidt!
      For the sake of history, User_talk:CommanderWaterford/Archive_1#Follow-up doesn't appear to have ever adequately been addressed. If unblocked, should be absolutely limited to one account. Star Mississippi 21:19, 1 January 2024 (UTC)[reply]
    • (edit conflict) Per WP:ROPE, I'd probably support an unblock. Two & a half years is a long time to (perhaps) recalibrate one's approach to collaboration. It's also a period of maturation (hopefully). And the pandemic was not the best time for anyone; while NOTTHERAPY clearly applies, judging someone's actions in that period as symptomatic of fundamental irreversibility would be looking at them through a glass (darkly). While coming back from a site ban is, all things being equal, more unusual than otherwise, I'm sure CW is under no illusion that there would be a second chance should recidivism raise its ugly head. No. Their feet, as they say, would not touch. At even one single hint of trouble. It would not be the case that there would be an outpouring of anger against the blocking admin; there would be no massive report at AN; and there certainly would not be such a lack of consensus for the block that it was deemed unsafe. On the contrary. The process would be: Hint of trouble → indef block → AN thread → block supported → site ban reinstated. Les jeux sont faits.
      By the way, in case anyone thinks we were friends  :) ——Serial 19:06, 1 January 2024 (UTC)[reply]
    • Oppose. I saw this request yesterday but decided to think about it before commenting. I'm usually in favour of giving some rope after this length of time, but I see two reasons not to. One is the username, as pointed out above by Black Kite. This did not get much discussion at the time of the block because the user was going to be blocked anyway, but it betrays some boneheadedness to appeal the block without changing it or even mentioning it. The other is that this editor presumed to pass judgement on other people's efforts by taking part in new page patrol. I don't believe that anyone who does that without looking first at whether they have it in themself to be a good editor can change significantly, unless they are a child, of which I see no indication. Phil Bridger (talk) 19:48, 1 January 2024 (UTC)[reply]
    • Oppose. Given the history, there are too many reasons to conclude that an unban would not be worth the likely downsides. --Tryptofish (talk) 22:50, 1 January 2024 (UTC)[reply]
    • Oppose: in their UTRS appeal they mention editing the Spanish Wikipedia and staying out of trouble, and here they mention one of their past issues was assuming bad faith. As it was pointed out above by Victor Schmidt, CW was ibanned at eswiki for assuming bad faith and accusing another user of sockpuppetry with no evidence. Isabelle Belato 🏳‍🌈 14:17, 2 January 2024 (UTC)[reply]
    • Comment - Why was your talkpage re-blocked, a few days ago? GoodDay (talk) 14:23, 2 January 2024 (UTC)[reply]
      Unless I'm missing something, TPA was restored on the 30th to allow CW to reply to concerns listed here. I don't see anything else at the moment. RickinBaltimore (talk) 14:27, 2 January 2024 (UTC)[reply]
      My boo boo. I misread enabled as disabled. GoodDay (talk) 14:39, 2 January 2024 (UTC)[reply]
    • Oppose The fact that they have continued their behavior at another Wiki while banned here, leading to sanctions being placed on them, tells me all I need to know. Lifting the ban will result in being right back where we are now soon after. RickinBaltimore (talk) 14:25, 2 January 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Proposed motion to create Reliable source consensus-required restriction procedures and add the restriction to the Lithuania topic area

    The Arbitration Committee is considering a motion to amend the procedures and to extend reliable source requirements to Lithuania as a topic area. Comments are welcome at the relevant request for clarification.

    For the Arbitration Committee, Barkeep49 (talk) 18:33, 31 December 2023 (UTC)[reply]

    Wikipedia Hack - Vandalism

    DuckDuckGo search for "Seven laws of Noah" brings up a preview page with homophobic hate speech, "https://en.wikipedia.org › wiki › Seven_Laws_of_Noah Seven Laws of Noah - Wikipedia The Seven Laws of Noah include prohibitions against worshipping idols, cursing God, murder, adultery and Abominable Detestable Hideous h*m*s*xuality, Abominable Detestable Hideous tr*nss*xuality, Abominable Detestable Hideous imitation of the opposite sex Abominably Detestably Hideously in ..." 71.211.134.163 (talk) 23:23, 31 December 2023 (UTC)[reply]

    That would be due to some recent vandalism at Seven Laws of Noah which has been reverted with the IP being blocked. Johnuniq (talk) 23:31, 31 December 2023 (UTC)[reply]
    Should it be revdel or no? ChaotıċEnby(t · c) 23:56, 31 December 2023 (UTC)[reply]
    Alexf has now done so. DMacks (talk) 00:51, 1 January 2024 (UTC)[reply]

    Wrong Telephone Country Code for Bangladesh !

    Hi, I don't know why and who made this mistake, but the Telephone Country Code (+690) for Bangladesh is WRONG. Actually the Phone code for Bangladesh is +880 So, could you please correct the phone code for Bangladesh in your Wikipedia. Thanks in advance. 120.18.89.131 (talk) 03:07, 1 January 2024 (UTC)[reply]

    Fixed. Thanks for alerting us! DMacks (talk) 03:11, 1 January 2024 (UTC)[reply]

    Unblock request of Sbb1413

    The following is the unblock request of Sbb1413. I am transferring it here as a courtesy, and make no endorsement in doing so, I will also provide the link to the discussion leading to the block, Special:Permalink/999244891#Soumya-8974,_again. 331dot (talk) 09:58, 1 January 2024 (UTC)[reply]

    • I have already understood why I was banned in February 2021. I used to create zillions of useless redirects and behaved negatively towards other users (intentionally or unintentionally) under the username Soumya-8974. Now I understand the consequence of disruptive editing and behaving negatively towards other users. I have worked in English Wikivoyage, Wikimedia Commons and Bengali Wikipedia for more than two years, and I have largely avoided anything that could prevent working there. I know that banning is undertaken as a preventative measure and not as a punitiative measure. I hope the English Wikipedia community will unban me with certain terms and conditions, including topic bans on certain topics. I promise that I will avoid any disruptive editing in English Wikipedia and I won't behave negatively towards any users. I want topic bans on China, Pakistan and all redirects, and focus on topics related to India and transport systems instead. So many years have passed and everything has changed. I have already translated many English articles into Bengali. Now I want to translate Bengali articles into English. Thank you for your support and happy new year 2024. I want to copy this post to an appropriate venue by an uninvolved experienced editor.
     – previous appeal (October 2021). Victor Schmidt (talk) 10:26, 1 January 2024 (UTC)[reply]

    Edit request to (hopefully) unbreak the Main Page video for mobile users

    I was just wondering if an administrator could take a look at my edit request for Wikipedia:Main Page/styles.css. Apologies for the post to AN as well as the edit request, I'm just conscious that the video on the Main Page is currently broken for mobile users. Any questions let me know.

    Best, ‍—‍a smart kitten[meow] 12:11, 1 January 2024 (UTC)[reply]

     Done by Maxim :) ‍—‍a smart kitten[meow] 13:18, 1 January 2024 (UTC)[reply]

    No reply on an ANI section

    Hello, I made a report at ANI, which has been closed without any reply. Was there an error on my side, or did it just go unnoticed? Should/could I reopen the report? And finally, why is it possible for a section to be archived without any feedback to its opener? Janhrach (talk) 15:30, 1 January 2024 (UTC)[reply]

    If a section has no activity, it gets archived. The archiving bot doesn't know that there's no activity due to a lack of replies. 331dot (talk) 15:34, 1 January 2024 (UTC)[reply]
    I find it surprising that the bot doesn't have a feature to archive sections with replies only. This means that there are many sections that got archived without any response from admins. Janhrach (talk) 07:55, 2 January 2024 (UTC)[reply]
    That's on purpose. If no one at all finds the section worth even commenting on, there's unlikely to be any action taken. — The Hand That Feeds You:Bite 18:07, 2 January 2024 (UTC)[reply]

    Closure Review Request on Neopronouns guidelines in MOS

    The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.


    (I'm new to editing wikipedia so apologizes if I make any mistakes doing this)

    In November 2022 a RFC discussing use of neopronouns across wikipedia was closed (https://en.wikipedia.org/w/index.php?oldid=1124226138#Neopronouns_RfC_(moved)) claiming that the vast majority of respondents were in favor of mentioning the neopronouns once in the article lead and defaulting to singular "they" otherwise. (The closing post didn't include any numbers but I counted around 70% first choice votes for option E or C)

    I'm requesting review on this by an impartial, uninvolved admin because

    1. This is a politically-charged and controversial decision that affects every article on wikipedia that mentions someone who goes by neopronouns.
    2. I believe that the discussion was closed prematurely
      1. There was still ongoing discussion and new votes and arguments were being made when the RFC was closed.
      2. This issue is still discussed.
    3. Many of the votes did not provide an argument, were based solely on personal political opinion, or made strong claims that they did not back up. The closing post did not provide any explanation for how it handled these votes, and it appears that they just chose the option which got the most votes (E+C since they were pretty similar). This is not how wikipedia works, to my understanding. Additionally, there being multiple similar options, options being added partway through the discussion, and users voting for more than one option complicates making this decision solely based on the number of votes.
    4. Many of the arguments given for option E (and other options) were that modern sources weren't using neopronouns. Option H was added partway in the discussion, which was to defer to the pronoun usage in recent reliable and independent sources. Many of the arguments were more in-line with option H but were presumably counted as being for other options as option H was not there from the start. The options that were initially presented to editors did not represent the range of opinions that emerged in the discussion.
    5. An argument voiced by some participants was that the ESL audience may be confused by the use of neopronouns so they should not be used. The closing post claimed that "there is broad agreement among the vast majority of editors" for this argument and presented it as the argument that decided the issue. However, in actuality only 13 out of 46 respondents voiced support for this argument. The closing post gives the impression that the discussion reached a much stronger consensus than it actually did.

    We went though and summarized every respondent's argument and vote(s). We'll include that here since it could be useful. We bolded votes that did not include an argument/reason. I don't know enough about wikipedia policy to judge whether arguments are relevant to it though.

    Extended content
    • A "Allow all neopronouns"
      • Sideswipe9th (disrepectful to ignore people's preference)
      • Thatbox (agrees with Sideswipe9th, using neopronouns represents people's identities)
      • GreenComputer (second choice, thinks misgendering people is in violation of WP:BLP)
      • Tewdar (thinks its in the intended spirit of the gender identity section of the manual of style)
    • B "Don't use noun-self pronouns, use other neopronouns (e, xe, xir, zir etc)"
      • Sideswipe9th (disrepectful to ignore people's preference)
      • Thatbox (agrees with Sideswipe9th, using neopronouns represents people's identities)
      • MSG17 (neopronouns are used by acceptable sources and present in dictionaries, doesn't think neopronouns will be notably confusing for readers)
      • MarjinFlorence (neopronouns are not new and it is fair to respect people's preferences, nounself pronouns are more like nicknames so they don't count)
    • C "Retain status quo (use singular they)" (note - some respondents pointed that this was not the status quo but was just the result of an isolated non-binding discussion & that the actual status quo was MOS:GENDERID)
      • Rosguill (selects C as a fallback, prefers taking cues from RS coverage when a consensus exists)
      • Crossroads (claims neopronouns aren't words and using them would not be grammatical)
      • SMcCandlish (second choice, no reason for support given, implies people supporting neopronoun usage are "irrational")
      • Masem (neopronouns are non-standard and don't belong in an encyclopedia)
      • Slywriter (thinks wikipedia should only adopt styles that are widely used in scholarly sources)
      • Rhododendrites (second choice, agrees with bluerasperry/funcrunch)
      • WhoIs 127.0.0.1 ping/loopback (thinks that we should prioritize comprehension and stick to words that every reader knows)
      • Elli (Will make articles confusing to people who aren't familiar with neopronouns. little benefit to using neopronouns and they/them or the person's name works fine)
      • Girth Summit (second choice, no reason given)
      • David Eppstein (second choice, thinks we shouldn't use neologisms people aren't familiar with)
      • Ficaia (no reason given)
      • SWinxy (agrees with masem)
      • JoelleJay (harms readability, doesn't want to have to determine whether pronoun usage is sincere or satirical)
      • Levivich (readers aren't familiar with neopronouns)
      • Satellizer el Bridget (no reason given)
      • Some1 (agrees with masem)
      • John Cline (feels the issue was adequately resolved earlier)
      • Darwin (second choice, no reason given)
    • D "Refer to subjects only by name"
      • SMcCandlish (fourth choice, no reason for support given, implies people supporting neopronoun usage are "irrational")
      • MikutoH (its how ptwiki does it)
      • Elli (Will make articles confusing to people who aren't familiar with neopronouns. little benefit to using neopronouns and they/them or the person's name works fine)
      • Girth Summit (second choice, no reason given)
    • E "Mention the neopronouns once in the article lead, default to singular they otherwise"
      • Bluerasberry (thinks it will make reading harder for ESL audience)
      • Crossroads (second choice, thinks neopronouns aren't words and using them would not be grammatical)
      • SMcCandlish (no reason for support given, implies people supporting neopronoun usage are "irrational")
      • Funcrunch (agrees with bluerasperry, thinks its a reasonable compromise for non-binary people)
      • Rhododendrites (agrees with bluerasperry/funcrunch)
      • Dsuke1998AEOS (thinks neopronouns make reading difficult because they look unnatural, feels they're controversial in the LGBT community, would support their use on wikipedia once/if they become popular in reliable sources)
      • GiantSnowman (no reason given)
      • Guerillero (believes neopronoun usage will cause accessibility issues for esl, older speakers, and uneducted readers, believes we should be following trends rather than spearheading them)
      • Dickylon (feels we shouldn't be endorsing/spreading changes to the language that are still unfamiliar to most readers)
      • Elli (Will make articles confusing to people who aren't familiar with neopronouns. little benefit to using neopronouns and they/them or the person's name works fine)
      • Girth Summit (no reason given)
      • David Eppstein (thinks we shouldn't use neologisms people aren't familiar with)
      • TreyMaturin (thinks neopronouns are too startling. Feels like singular they is inoffensive except to people it offends and that they are irrational and shouldn't be pandered to. Also says that neo-pronoun users offended by being misgendered are irrational.)
      • dudhhr (believes neopronouns would be confusing to ESL speakers)
      • 109.255.211.6 (thinks we should follow the tone of mainstream publications)
      • SWinxy (agrees with masem)
      • Valereee (confusing to readers, E>H>B>C>A>D)
      • Hentheden (harms readability, particularly for ESL)
      • JoelleJay (harms readability, doesn't want to have to determine whether pronoun usage is sincere or satirical)
      • Levivich (readers aren't familiar with neopronouns)
      • Satellizer el Bridget (no reason given)
      • Necrothesp (if we use neopronouns, soon we'll be removing factual information because the subjects want us to)
      • Darwin (no reason given)
      • Carter (Tcr25) ("seems the most workable")
      • small jars (least confusing for readers)
    • E.1 "Refer to any person whose gender might be questioned with gendered words (e.g. pronouns, "man/woman", "waiter/waitress" "brother/sister") that reflect the person's most recent expressed gender self-identification as reported in the most recent reliable sources, even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise." (added mid-discussion)
      • Tamzin (thinks pronoun usage should be avoided altogether for people who object to being referred to with they/them)
      • JoelleJay (harms readability, doesn't want to have to determine whether pronoun usage is sincere or satirical)
      • Carter (Tcr25) ("seems the most workable")
    • F "Only use neopronouns if the subject does not also use one of the common sets of pronouns. To avoid potential reader confusion, the usage of neopronouns should be noted with an appropriate hatnote/footnote/in-text note before or at the first usage" (added mid-discussion)
      • GreenComputer (thinks misgendering people is in violation of WP:BLP)
      • Madeline (agrees with greencomputer, roxysaunderes, and endwish, thinks its ironic using the AP stylebook as an argument to support singular they over neopronoun usage given the AP stylebook recommends against using either)
    • H "Use the pronouns most common in recent reliable and independent sources" (added mid-discussion)
      • SMcCandlish (third choice, no reason for support given, implies people supporting neopronoun usage are "irrational")
      • BilledMammal (believes wikipedia is obligated to agree with primary sources)
      • MSG17 (neopronouns are used by acceptable sources and present in dictionaries, doesn't think neopronouns will be notably confusing for readers)
      • XOR'easter (believes its in line with wikipedia's policies. Thinks its wrong to sacrifice providing accurate information for the sake of readability)
      • Sariel Xilo (thinks neopronouns are comprehendable and that they're used in acceptable sources)
      • Aquillion (thinks overriding sources is inappropriate)
      • Bilorv (thinks a blanket rule is inappropriate when there is no consensus among professional sources, and that deferring to sources is how wikipedia works)
      • Levivich (readers aren't familiar with neopronouns)
      • MarjinFlorence (neopronouns are not new and it is fair to respect people's preferences)
    Mousecat111 (talk) 16:27, 1 January 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Appeal of the removal of EC permissions for User:FoodForLLMs

    I (User:FoodforLLMs) had my EC permissions revoked by User:Ingenuity. (Incident Page)

    Quoting the reason:

     Yeah, that's pretty clear WP:PGAMEing. I've revoked their extended- confirmed permission, which they may re-request at WP:PERM/EC after making 500 non-trivial edits
    

    Presumably my permissions were revoked because of a string of short description edits that I have done, mainly on articles relating to railway stations around the world.

    First of all, I do not agree that these edits are trivial. They took me relatively little time because in order to be efficient, I created custom search queries (which took me time to figure out) that allow me to find articles with missing templates from specific categories. This helped me quickly process a lot of these, as I handled one category at a time. However, this is still not easy work, you need to read the lead of the article to make sure the description aligns and you need to add 5-6 new words to each article.

    If they are regarded as trivial because they are considered unimportant, I'll disagree again, as these show up at the search box, one of the most used UX surfaces. And a lot of wikipedia articles currently miss a short description.

    Thirdly, according to WP:NNH, "Focusing on niche topic areas" and "Focusing on particular processes" are encouraged.

    Furthermore, I made different contributions that greatly improved the state of low quality articles across many different subjects. I did so before receiving EC and afterwards, I still continued adding short descriptions to missing articles as recent as today.

    WP:PGAME does not mention any behavior that is close to any of my edits (it mentions sandbox editing and dummy edits).

    When I look at a recent appeal (https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard#Appeal_of_the_removal_of_EC_membership_for_User:DMH43), the account was open for a much shorter time, it showed battleground behavior around ARBPIA which I did not, and a fifth of its contributions were around ARBPIA before even receiving EC status.

    If you intend to reject my appeal, may I at least ask you to update WP:PGAME and create a clear policy around this? Currently it is very murky and open to interpretations, while the only thing that is clear is the 500/30 rule, which I abided by.

    After I made a lot of hard work to improve wikipedia, being the target of a seemingly arbitrary decision is plainly extremely demotivating.

    Because of the above, I think my EC permissions should be reinstated FoodforLLMs (talk) 21:43, 1 January 2024 (UTC)[reply]

    That was a fine removal of EC permission. All this gaming and appeals makes me think we'd be better off if EC was not automated, and instead worked similar to autopatrolled, where you'd need to request it at WP:PERM or be bequeathed upon by an uninvolved admin. Isabelle Belato 🏳‍🌈 21:48, 1 January 2024 (UTC)[reply]
    Except for the fact that even in the current state a lot of PIA articles are in an abysmal state because of lack of maintenance, this is a lot of the time because contributors have less access to edit these. You can see that on talk pages with ignored requests for edits.
    For example articles I worked on:
    They are usually filled with bad formatting, old and inaccurate information and unreadable amount of text FoodforLLMs (talk) 22:02, 1 January 2024 (UTC)[reply]
    I agree with the removal, but I'd be concerned about essentially requiring admin approval for all editors who want to edit in a few topics. ScottishFinnishRadish (talk) 22:11, 1 January 2024 (UTC)[reply]
    • Obvious gaming, and entirely justified removal of EC. -- Euryalus (talk) 23:06, 1 January 2024 (UTC)[reply]
    • One of the purposes of EC protection/restrictions in contentious editing areas, is that editors need to learn about Wikipedia policies and processes before diving into said areas. The idea of 500 edits is that it provides time to learn said policies, processes and also editing norms before getting involved in contentious topics. There is no way that 500-odd short description changes allows a new editor to achieve this goal, and for that reason I support the removal of EC in this situation with the requirement that they complete 500 non-trivial edits. Daniel (talk) 00:54, 2 January 2024 (UTC)[reply]
      1. I think that whether I learned about said policies should be judged on the basis of my contributions to WP:ARBPIA and you can see by my diffs that I engaged in constructive behavior and never degrading into WP:BATTLEGROUND. This is not the case among the longtime EC editors in this subject.
      2. In order to do said short description editing, I read about Wikipedia:WikiProject Short descriptions, I made sure not to touch articles that do not have a description but have an autogenerated description from the template and I created search queries to speed up my contributions (which is my biggest crime apparently). I also added clear edit descrptions and read style guides for the rest of my edits.
      All in all I added missing descriptions to hundreds of articles that were missing these, finishing entire categories for a few different geographies, which in my opinion was impactful.
      3. I did want to reach 500/30 to edit WP:ARBPIA because these are subjects that interest me, and I think I have knowledge in. I read the related policies and made sure that my contributions would not be regarded as WP:PGAME, even currently, I cannot tell you what constitutes as a trivial edit as it seems like it's some latent tribal knowledge that changes on case by case basis FoodforLLMs (talk) 06:45, 2 January 2024 (UTC)[reply]
      Adding short descriptions doesn't give an editor the kind of experience that prepares an editor for ARBPIA editing because, among other things, it doesn't involve having to work with sources at all. This is especially true when it's 100s of the same short description, "railway station in [location]," added to articles about railway stations. These aren't useless contributions, but they don't require thought or research, it's just plugging in a location in a stock phrase, which is why you were able to do so many so quickly. Such edits don't develop content experience in an editor, they don't involve discussing content, they don't involve or demonstrate knowledge of editing policies or guidelines. Endorse removal. Levivich (talk) 14:25, 2 January 2024 (UTC)[reply]
      I agree. Endorse removal. It won't hurt the editor to make more substantial contributions before getting it restored. Doug Weller talk 17:09, 2 January 2024 (UTC)[reply]
    I agree with @FoodforLLMs that the current policy is murky and does not define engaging in "wikignoming" as an example of gaming. It is clear that a specific interpretation has evolved, but this is not clear to new users who believe they are abiding by the rules, only to discover later that there is an "oral law" not written in the policies. I call for administrators to bring order to the rules.
    Regarding the appellant, I would like to recommend that administrators define a specific, clear condition where the editor can regain their EC (for example: an additional X mainspace edits to prove they are a constructive editor), as it seems like a frustrating place to be, and we are likely to lose him/her as a valuable editor, that would be unfortunate. Marokwitz (talk) 19:02, 2 January 2024 (UTC)[reply]
    I think this is a very fair criticism. WP:PGAME does not describe these kinds of edits -- they are not "unconstructive edits" or "dummy edits" or edits to a sandbox. Also, WP:ARBECR doesn't link to PGAME, so a new editor being pointed to ARBECR may not even be aware of PGAME. We are, in fact, holding editors to a standard that is not documented. I join the call for arbs/admins to update the documentation. Levivich (talk) 19:54, 2 January 2024 (UTC)[reply]
    Ok, I'll join that call too. Not sure how it can be worded to be unambious, I think there may always be some judgement involved. Doug Weller talk 20:57, 2 January 2024 (UTC)[reply]
    • WP:ARBECR does link to WP:EXTENDEDCONFIRMED, though, which links to PGAME and which states that Extended confirmed is revoked if a user is in another group with which it is redundant, and in rare cases may be revoked for other reasons, such as if a user games the system by making many trivial edits. That is the core policy defining the extended confirmed permission and is quite clear. It could be made more clear elsewhere, and PGAME should reflect EXTENDEDCONFIRMED and say "trivial" rather than "unconstructive" (since making many unconstructive edits is already against policy), but I don't accept the argument that any editor who has gamed the system was unaware of what they were doing; maybe they thought it wouldn't be noticed or that nobody would care, but rushing to get to 500 through minor edits is extremely obvious when it happens. I'm also concerned that setting too clear of a definition could just encourage editors to game the system - the problem with gaming the system isn't that the edits fall below some hypothetical standard; the problem is with the editor's intent. If an editor is reading EXTENDEDCONFIRMED and PGAME with an eye towards figuring out how they can become extended-confirmed as quickly as possible, they should stop doing that, and the guidelines should be written in a way that makes that clear rather than encouraging it by effectively providing a map to the fastest way to get the desired permission. --Aquillion (talk) 21:52, 2 January 2024 (UTC)[reply]
      These aren't "trivial" edits, though, either. Gnoming isn't "trivial." "Trivial" means "of little value or importance." Adding a short description, fixing typos, adding wikilinks, fixing citation formatting... these gnoming edits are not trivial because they are not "of little value or importance." Levivich (talk) 22:05, 2 January 2024 (UTC)[reply]
      The fact that "trivial edits" are linked to WP:PGAME suggests that the content in WP:PGAME is the intended interpretation of "trivial." Based on the way WP:EXTENDEDCONFIRMED looks, I doubt that the policy's author regarded technical edits such as adding 5-6 word descriptions as trivial.
      This same issue recurs on this noticeboard, indicating a significant problem. It is counterproductive to our goals of attracting good new editors to enhance content, rather than alienating them, and we should address it.
      If the consensus has shifted, we should indeed update the terms "trivial" and "unconstructive" to better align with the current understanding, perhaps using a term like "unsubstantial." Marokwitz (talk) 22:35, 2 January 2024 (UTC)[reply]
      This war is maybe the most significant event in the conflict since ECR was instituted at WP:ARBPIA3#500/30 almost 10 years ago. I don't have the stats but I wouldn't be surprised if these past few months have seen an all-time high for new editors in this topic area. I think that's why there is so much activity around ARBPIA ECR lately?

      PGAME was written with WP:EC in mind, not WP:ECR, and "gaming EC" isn't quite the same thing as (what we call) "gaming ECR". To take FoodforLLMs edits as an example, had FFLLM continued to add short descriptions after reaching EC, I don't think anyone would ever suggest they were "gaming EC."

      PGAME is written with an intent requirement ("to raise your user access level"), and that kind of makes sense in relation to EC, but it doesn't necessarily make as much as sense for ARBPIA ECR. The difference is that PGAME is about preventing bad faith acquisition of EC--"gaming EC"--whereas ARBPIA ECR is intended to prevent bad faith and good faith but inexperienced editing in ARBPIA. So, in my view, for ECR, it doesn't matter if the editor's intent is to raise their user access level to edit ARBPIA. As I said in another EC revocation appeal thread, we want editors to make edits to raise their user access level, but even good faith editors may not make the "right" kind of edits for ARBPIA ECR (even if they are the right kind of edits for EC). That is what I think the documentation is lacking.

      I am not in favor of a system, as SFR mentioned above, where admins gatekeep new editors in a topic area. I'm also not in favor of writing rules for admins to follow when it comes to EC revocation in ECR'd CTOPs--I think that's too restrictive and we're not going to do a good job of it. But I do think we should have an explanation about EC revocation in ECR'd CTOPs that does not suggest that EC is only revoked when there is "unproductive" or "trivial" or bad faith "to raise your user access level." I'm not sure exactly what the answer is, but it should be the answer to the question: if I registered an account today and I want to edit an ECR'd CTOP, what kind of edits should I make for the first month? And then an explanation that admins may revoke EC if the editors' edits aren't those kinds of edits. (I'm not sure if "those kinds" means "substantial" or "non-trivial" or what.) Levivich (talk) 02:11, 3 January 2024 (UTC)[reply]

    Closure request for "Inside Voices / Outside Voices"

    I posted this before, but it got archived. Per my inquiry at WP:HD, I am requesting a procedural close or snowball close for Wikipedia:Articles for deletion/Inside Voices / Outside Voices (2nd nomination). --Jax 0677 (talk) 22:56, 1 January 2024 (UTC)[reply]

    @Jax 0677 I have SNOW closed it, if anybody has problems with my close feel free to revert and we can discuss. Thanks, Seawolf35 T--C 07:37, 2 January 2024 (UTC)[reply]

    Extended-confirmed gained largely through ECR violations

    Chavmen (talk · contribs) recently gained extended-confirmed permissions, but looking through their history it appears that a large portion of their earlier edits were ECR violations. I don't have the time right now to handle this, so I'm leaving a note here. ScottishFinnishRadish (talk) 14:06, 2 January 2024 (UTC)[reply]

    Hi @ScottishFinnishRadish, what's an ECR violation? And which earlier edits? I'm not really sure what this is about so if anyone can explain that would be great. Chavmen (talk) 14:44, 2 January 2024 (UTC)[reply]
    (Non-administrator comment) I'm surprised you're asking what an WP:ECR violation is because you seem to have understood it on Nov 30 and also on Dec 26? Also a question for admins: why didn't this creation trigger edit filter 1276? Levivich (talk) 15:47, 2 January 2024 (UTC)[reply]
    It looks like the filter was using the "page_id" variable to check if the article was just created, which according to the documentation is unreliable. I've switched it so it uses the "page_age" variable instead, which should hopefully fix it. — Ingenuity (talk • contribs) 15:54, 2 January 2024 (UTC)[reply]
    More likely that the page was created in userspace and then moved to mainspace, while the filter only checks for new creations in the mainspace. DatGuyTalkContribs 17:05, 2 January 2024 (UTC)[reply]
    Oh yeah, that would make sense. I've edited the filter so it should match pages moved into mainspace as well. — Ingenuity (talk • contribs) 17:30, 2 January 2024 (UTC)[reply]
    Unfortunately there's no way to access the wikitext during a page move. I've modified the filter to check the new title, which is the best we can do. (Also, there's nothing wrong with page_id anymore; WP:EFD is just really out of date.) Suffusion of Yellow (talk) 22:11, 2 January 2024 (UTC)[reply]
    I'm not familiar with all the Wiki lingo, so you mean EC protected?
    When I knew the page was EC protected I always put in edit requests? Isn't that how things are done? I didn't think this was unreasonable or against any rules.
    The edits mentioned above, I was involved in prior to any EC protection on the page and when I noticed the protection was placed on the page I left the page and didn't edit it further. You can see that looking back at when the tag was placed.
    I also created a page about an organisation to do with Israel which I didn't think controversial. I've edited several other organisations in the same area that weren't EC protected - NGOs etc.
    I also requested EC protection on several pages (Bassem Eid, UN Women for example) that were previously vandalised and then I did not edit them.
    This feels like a technicality that isn't very clear and I can't see how my edits were negative in anyway or controversial. Chavmen (talk) 23:03, 2 January 2024 (UTC)[reply]
    Sorting this, stand by. -- Tamzin[cetacean needed] (they|xe|she) 22:51, 2 January 2024 (UTC)[reply]
    Hi Tamzin,
    Just to clarify, if a page doesn't have the EC protection tag but still falls under an Israel/Arab/Palestinian topic I shouldn't have edited it?
    For instance, pages like LGBT rights in Israel, notable people pages Israeli Arab etc, NGOs, history pages.
    Because majority of my edits were in non-EC protected pages.
    The claim is that the majority of my edits were in EC pages which I don't see how that's possible since I had stayed away from them or put in edit requests.
    Shall I count them manually to demonstrate? Chavmen (talk) 23:27, 2 January 2024 (UTC)[reply]
    Yes, not all pages that fall under the ARBECR are extended-confirmed protected on a technical level. Non-extendedconfirmed editors are expected to abide by the ARBECR on all pages. As I've written in your user rights log, when you hit 1,000 edits you may re-apply for extendedconfirmed to me or at WP:PERM/EC. It seems you're interested in LGBTQ topics, so if you're looking for things to edit not about the Arab-Israeli conflict, there's no shortage of LGBTQ articles to work on. I started a vague outline of Draft:Judaism and LGBT topics a while ago, if you're interested.
    Also, since Indigenous Coalition for Israel has been PRODded and de-PRODded, but hasn't been substantively edited by EC editors, I won't ECR-delete it, but I'll split the difference by draftifying and EC-move-protecting it. Any EC editor willing to take responsibility for its contents can move it back. -- Tamzin[cetacean needed] (they|xe|she) 23:48, 2 January 2024 (UTC)[reply]

    Rangeblock request

    Hello! Could someone please rangeblock 2604:3D08:2F84:2000::/64? Two IPs from this range, along with accounts Israelisascourge and Blooperman12345 (since blocked), have been repeatedly adding the same unconstructive and possibly defamatory content to Perpetrators, victims, and bystanders. IP disruption seems limited to this /64 (and I think it's likely that the accounts are on the same range), so I believe a rangeblock would be helpful. (Also, is this the right venue? I don't know if AN/I would be more appropriate — the stated scope in its header seems to have been limited to only "chronic and unmanageable behavioral problems" sometime since I last looked.) Thanks. Tol (talk | contribs) @ 01:49, 3 January 2024 (UTC)[reply]