Wikipedia talk:Criteria for speedy deletion

Latest comment: 10 hours ago by Largoplazo in topic Time to get rid of A2?

RfC: Status of G5 edit

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


Which of these options is preferred for the status of CSD G5?

  • Option 1: Keep G5 as is.
  • Option 2: Add mention of general sanctions to G5.
  • Option 3: Add general sanctions violations to its own speedy criterion.
  • Option 4: Repeal G5 and incorporate its principles into the WP:BANPOL (specifically WP:BANREVERT) as "administrators are permitted, but are not required, to delete page creations made in violation of a ban, general sanction, or block".
  • Option 5: Repeal G5 and do nothing else.
  • Something else?

Awesome Aasim 15:32, 12 December 2023 (UTC)Reply

Background edit

WP:ARBECR is a sanction that is applied by both the Arbitration Committee and the community, with one of the permitted actions being deletion. There has been contention as to whether this is an extension of G5, but what is agreed is that these deletions will continue to happen per arbitration enforcement or community consensus, regardless on the wording of G5. This RfC aims to clarify the purpose of G5 and whether this case is included in G5, if G5 is adequate as is, or if its wording is controversial and better superseded by text in the ban policy.

See also the extensive discussion of Special:Permalink/1188336533#Suggestion:_Expansion_of_G5.

Survey (Status of G5) edit

  • As proposer: Option 4. Option 3 and Option 2 are second choice. Oppose Option 1, as the status quo might not adequately cover all cases. Neutral about Option 5. The whole point of topic and editor sanctions is to stop disruptive editing by limiting the type of editing within the topic area in general, or by keeping editors out of topic areas they were previously disruptive in. And since the CSD appears to be for unequivocal cases where almost no editor would disagree the page should be deleted, how to enforce ban evasion should be up to administrator discretion. Awesome Aasim 15:32, 12 December 2023 (UTC)Reply
  • G5 is up to administrator discretion already. It's not something separate from BANREVERT; it's the way BANREVERT is implemented regarding deletion. Repealing G5 would just make our deletion policy more confusing. Elli (talk | contribs) 16:44, 12 December 2023 (UTC)Reply
    That's what I thought, but the discussion linked leading up to this creation of the RfC lead to a bunch of confusion. Which is why I started it in the first place. Awesome Aasim 17:23, 12 December 2023 (UTC)Reply
  • The criteria for speedy deletion (CSD) specify the only cases in which administrators have broad consensus to bypass deletion discussion [...], and unless we want to break this, option 4 is invalid. ~ ToBeFree (talk) 17:28, 12 December 2023 (UTC)Reply
    If option 4 was chosen, it would probably be like any proposed deletion process. An editor would be able to propose a page be deleted because of general sanction or ban evasion, and if the PROD was expired without any (not banned) editor taking responsibility for the content, the page would be deleted until someone in WP:RFUD takes responsibility for the diff. Awesome Aasim 18:36, 12 December 2023 (UTC)Reply
  • Something else. Explicitly state (here and in other relevant policies) that speedy deletion is not a valid enforcement mechanism for DS/GS/CT sanctions unless the page meets a speedy deletion criterion for other reasons. This is because it is not, per the arguments cogently made by Ivanvector and others in the Gun Control ARCA linked below. If administrators continue to delete pages after this then this should be dealt with like any other breach of the deletion policy, up to and including desysopping in extreme cases. Thryduulf (talk) 17:52, 12 December 2023 (UTC)Reply
    Does that mean that WP:ARBECR is wrong that administrators are permitted but not required to delete pages as arbitration enforcement actions? Speedy deletion describes if I recall whether a page can immediately be deleted without waiting for further discussion. Awesome Aasim 18:19, 12 December 2023 (UTC)Reply
    As I argued in the case linked below, the Arbitration Committee does not have the power to create policy by fiat, and is not empowered to make content decisions. An Arbcom case saying, in isolation, that deletion is permitted by arbitration enforcement, did not make it so; the deletion policy remains the only policy under which deletion is allowed on Wikipedia. That said, this discussion could decide to modify policy to align with Arbcom's decision, but I don't like the implication of the community retroactively changing long-established policies to accommodate Arbcom making decisions outside its authority. Ivanvector (Talk/Edits) 18:34, 12 December 2023 (UTC)Reply
    In shorter words: yes, WP:ARBECR is wrong. Ivanvector (Talk/Edits) 18:35, 12 December 2023 (UTC)Reply
    How would you enforce ARBECR for new content? Don't punt and say "AFD", the point of the measure is to prevent sockpuppetry and has been since its creation a decade ago. Hence G5's extensive current use to enforce it. Izno (talk) 19:42, 12 December 2023 (UTC)Reply
    The point of the measure is two-fold, or at least it was when I proposed it. On one hand it's to deter sockpuppetry, but it's also intended to discourage new users from engaging in contentious topics which are frequent causes of disputes, in the interest of retention. Speedy deletion is inherently bitey - a new user creates an article in good faith on a topic they feel is missing coverage, and their work is immediately deleted and their talk page filled with bureaucratic advisories (to be charitable; it would be fair to call the notices "dire warnings") about contentious topics and speedy deletion, without any advice on how to proceed. Personally I feel that some leniency is warranted for pages which are not obviously unacceptable (like POV forks or clear propaganda or whatever). ARBECR already permits non-ECP users to make proper edit requests, and maybe creating a new page is an extension of that. I admit that I don't know what such a process would look like; something PROD-like maybe, I agree that AFD is too heavy a process for this. Ivanvector (Talk/Edits) 19:56, 12 December 2023 (UTC)Reply
    @Ivanvector so to clarify, I am understanding that you think only the page deletion aspect of ARBECR is wrong, but you are otherwise alright with the policy? Or have I misunderstood you? CaptainEek Edits Ho Cap'n! 20:32, 12 December 2023 (UTC)Reply
    I don't necessarily think that deleting these pages is wrong if the community desires it, only that Arbcom didn't have the authority to say so as it does not have authority over article content. I don't like the idea that we're building up a chain of pronouncement connections where one policy says that this one aspect of the decision is probably okay because this other policy doesn't explicitly disallow it and one decision from 10 years ago kind of allowed it and so on and so on and so on; there should be an explicit community endorsement. In the interest of moving on and not turning this into a policy wonkathon I can accept that the discussion above that Izno linked to below (wheee) is that explicit endorsement, although I think that that's the sort of retroactive endorsement of Arbcom changing policy by fiat that I think is a slippery slope. At the same time policy is meant to reflect consensus and not the other way around, and if admins are already citing the speedy deletion guideline to support these deletions then that's a good indicator that consensus has changed; the guideline should be updated to reflect that. I'm going to keep my comments here focused on that, but if you'd like to continue this discussion (which I admittedly started) on the theoretical implications of these various actions, my talk page is open. Ivanvector (Talk/Edits) 20:47, 12 December 2023 (UTC)Reply
  • Option2 clarifies that if a page is created against a ban or other restriction, speedy deletion is the most appropriate enforcement mechanism. Page creation restrictions under Arbcom sanctions should either have an effective enforcement mechanism, or should all be immediately repealed. —Kusma (talk) 18:36, 12 December 2023 (UTC)Reply
  • Option 1 - G5 is a criterion for user restrictions; a patrolling administrator needs to check that the page-creating user is in fact blocked or banned, which in most cases is evident from their block log. Checking that a page is created in violation of a general sanction is a different check entirely, and should be its own criterion. That is, if such deletions are in fact uncontestable: this has been established only by Arbcom making pronouncements in content matters in which it explicitly has no authority, and not through community consensus. I also think that such a criterion is an A-level criterion, but not strongly. Ivanvector (Talk/Edits) 18:49, 12 December 2023 (UTC)Reply
    Ivanvector, thank you for your thoughts on this, which are new to me. While we've so far just been talking about ArbCom-imposed ECR, there is also community-imposed ECR. See, for example, WP:GS/AA or WP:GS/KURD. Since the community does—as far as I'm aware—have the ability to affect deletion policy, do you believe that this community-endorsed deletion should have its own SD criterion? Firefangledfeathers (talk / contribs) 18:55, 12 December 2023 (UTC)Reply
    Thank you for that; those discussions are new to me. It seems to me that the wording of the general sanctions is adopted directly from ARBECR, which did not have the authority to modify the deletion policy. I'm not sure that the discussions that enabled those general sanctions were proper tests of community intent to create this as a path to deletion. I don't think that this discussion is really a proper test either, as the question is written with a presumption that there's consensus for it. I dislike bureaucracy for bureaucracy's sake almost as much as I despise bureaucratic overreach, but we seem to be creating deletion guidelines to accommodate a novel deletion method that wasn't actually discussed, and I think that discussion should have happened first before we start creating or modifying speedy criteria to support it. Ivanvector (Talk/Edits) 19:33, 12 December 2023 (UTC)Reply
  • Option 1 - Following User:Ivanvector and User:bradv. Expanding speedy deletion further shifts power from community to bureaucrats in an undesirable way. Sure, creating new articles is an annoying way to evade ECR, but my sense is that speedy deletion isn't the best imaginable remedy.— Preceding unsigned comment added by Groceryheist (talkcontribs) 19:36, 12 December 2023 (UTC)
  • Option 2 or Option 3 G5 has always been about consistently enforcing rules. Having one set of rules (Arbcom and Community General Sanctions) than we arbitrarily decide not to enforce in the obvious way while continuing to enforce another set of rules (User Topic/Site-Bans) that way is utterly illogical. * Pppery * it has begun... 19:40, 12 December 2023 (UTC)Reply
    Indeed, it is consistent with our handling of creation of material by banned users. Who are actually effectively topic banned by ECR. Izno (talk) 19:45, 12 December 2023 (UTC)Reply
    G5 is absolutely not about consistently encforcing rules, indeed "consistent" is one of the last words I'd use to describe the application of G5. G5 is about allowing administrators to enforce "banned means banned" when they choose to do so, for whatever reason they choose to do so. Neither GS nor DS topic restrictions are bans and enforcing the restrictions by speedy deletion is not conducive to a healthy editing environment in which good faith editors can participate. Thryduulf (talk) 20:05, 12 December 2023 (UTC)Reply
  • Within its scope, the committee may issue binding decisions that override consensus. Now, ignoring the procedural point, I think given how the restriction is being used, and G5's application here as being consistent with non EC users who are effectively topic banned from ECR topics, that what is being done today is Fine, with or without changing WP:CSD directly to acknowledge that such users cannot contribute to the pages they have created or otherwise extensively modified before they become EC. Izno (talk) 19:50, 12 December 2023 (UTC)Reply
    "Within its scope" has a rather clear bullet list definition written in the policy, and content decisions (including deletion) are clearly not within that scope. I'm not necessarily opposed to creating this path to deletion as there's clearly a desire to do so, but I'm very strongly opposed to doing anything under any presumption that Arbcom can do anything it wants for any reason. Ivanvector (Talk/Edits) 20:14, 12 December 2023 (UTC)Reply
    The bullet of interest is To act as a final binding decision-maker primarily for serious conduct disputes the community has been unable to resolve;. We have heard cases on the material, of which the first case introducing the measure includes the choice word draconian. Izno (talk) 20:17, 12 December 2023 (UTC)Reply
  • As for community general sanctions, I think it's a fair point of discussion within the context of each specific area as to whether the deletion part of ECR applies. Exceptions to policy can and have been made, and the community deciding they've had enough of socks in an area could override any declaration by this page anyway because that's how consensus works (hence why community-applied general sanctions aren't at AN(I) anymore). What ARBECR does(n't) do is not what "COMMECR" has to do. However, differing ways to implement ECR may cause general confusion among both experienced and inexperienced editors and administrators alike. Izno (talk) 20:15, 12 December 2023 (UTC)Reply
Option 1. Waylon (he was here) (Does my editing suck? Let's talk.) (Also, not to brag, but...) 17:51, 15 December 2023 (UTC)Reply
'Option 2 or Option 3 I do not believe that G5 should be strictly enforced, but it is clear that we do need to enforce general sanctions. –LaundryPizza03 (d) 03:25, 18 December 2023 (UTC)Reply
I thought about this last night and I think this is quite confusing. I'd like to clarify some things before I make my points, and if anyone disagrees with my summary they can feel free to comment. As far as I understand, the two main contentions here are "whether arbcom are allowed to authorize deletions outside of process", and "whether it is appropriate for CSD to include something that requires the discretion of admins and is not uncontroversial". For the former, I have no strong feelings, is not the original subject of this discussion, and IMO should be directed at arbcom. For the latter, my answer for that would be "No". Therefore I believe I mostly align with Option 1, but I think it is ridiculous to suggest people should be desysopped for following what arbcom says. 0xDeadbeef→∞ (talk to me) 09:03, 18 December 2023 (UTC)Reply
  • Option 2 or 3. What is the point of general sanctions in contentious topics if we had to go through the whole shebang of AfD, AN/I, AE etc to enforce it anyways? Arbcom cannot make content decisions, but it can very much make decisions on conduct, of which the creation of articles of a certain topic is an example. WP:BITE is not "don't tell the newbie they did something wrong", it is "tell the newbie they did something wrong in a kind and constructive manner". If need be, make db-gs more clear with wording such as "this does not indicate that the content is non-notable or otherwise wholly inappropiate for Wikipedia". Fermiboson (talk) 23:37, 19 December 2023 (UTC)Reply
  • Option 3. WP:NEWCSD, and follow the requirements of NEWCSD. Establish the evidence by putting several cases through MfD. Prouncements by ArbCom should be specific, not an endless chain of creation of new policy by autocrats. —SmokeyJoe (talk) 23:29, 22 December 2023 (UTC)Reply
  • Option 1 per Ivanvector. The new ARBECR is too resyrictive anyhow Mach61 (talk) 05:02, 23 December 2023 (UTC)Reply
  • Option 2 or 3, or reword ECR to frame it as a form of TBAN. The latter approach seems the most future-proof: It puts ECR violations under whatever rules apply to individual TBAN violations, without needing any special-casing. -- Tamzin[cetacean needed] (they|xe|she) 18:42, 24 December 2023 (UTC)Reply
  • Amend WP:BANPOL to list ECR as being treated as equivalent to a ban for the purpose of other policies. Add one line to WP:TBAN and one column to the WP:BLOCKBANDIFF table.—Alalch E. 20:14, 26 December 2023 (UTC)Reply
  • Option 3 first choice, Option 2 second choice. This is a really confusing RfC format, and I pity the editor who volunteers to close this; I'm not sure why Options 4 and 5 were proposed at all—they seem like very poorly-thought-out ideas. That being said, I think the cleanest, most organized solution would be to create a new G15 that applies to "pages created in violation of a general sanction, such as the extended-confirmed restriction, that have no substantial edits by other editors", but squeezing it into G5 would work too, and so would a consensus that ECR is, for the purpose of G5, essentially a topic ban applied to all non-extended-confirmed editors. Mz7 (talk) 07:49, 29 December 2023 (UTC)Reply
    While we're here, I will shamelessly drop a link to my essay Wikipedia:G5 is not a firm rule. Regardless of whether we create a new criterion or squeeze this into G5, I would like to emphasize that administrators should have discretion in all cases, and the rules will never obligate an administrator to delete a page that was created in violation of a general sanction like ECR—obviously helpful pages can be allowed to stand, but the presumption in ambiguous cases should be to delete. Mz7 (talk) 07:55, 29 December 2023 (UTC)Reply
    That's why G5 shouldn't be changed, because it's underpinned by this real and good practice and this can't simply be transplanted onto a brand new criterion, and we can't say "note to administrators: do it like you did it with G5" because it would look silly. That's why I believe that my idea is the best one: Just codify an interpretation of the arbitration rule from the vantage point of community created policy, and the relevant policy is BANPOL, not CSD. —Alalch E. 16:59, 29 December 2023 (UTC)Reply
  • Support option 2 as the easiest solution. Effectively G5 is about pages created where the creation of the page itself (rather than content) breaks a rule. I also support option 3 but I don't think it's necessary. Oppose options 4 & 5. Callanecc (talkcontribslogs) 08:49, 29 December 2023 (UTC)Reply
  • Option 2 or 3: I was confused when I read ARBECR and CSD and didn't find explicit mention of which criterion (if any) could be used by non-admins to request ARBECR deletion. I see some experienced volunteers believed G5 to implicitly cover ARBECR on first reading (which I think is reasonable—functionally, a non-EC editor is topic banned, at least once they've been made aware of GS). This should be spelled out explicitly. — Bilorv (talk) 12:17, 29 December 2023 (UTC)Reply
  • Option 3 first choice, Option 2 second choice. I think a criterion should cover violations of ECR to prevent disruption. I think having a new criterion is preferable to avoid confusion and to avoid practices from G5 (which mostly seems to amount to delete-on-sight, despite discretion given to admins). If option 3 passes, it should in substance be something like the following: GXX: Creations violating non-editor-specific restrictions. This applies to creations of pages where the creation violates a non-editor-specific restriction, whether imposed by the community or the Arbitration Committee, such as the extended-confirmed restriction. This criterion does not apply, however, to pages which have substantial edits that do not violate the restriction. Administrators must exercise discretion when deleting pages under this criterion, and must consider whether lesser action is more appropriate. Depending on factors such as the level of disruption present or likely, whether the creating editor is aware of the restriction, and (if an article) article notability and quality, this could include: leaving the page be without any action, improving the page, notifying the creating user of the restriction, nominating the page for a deletion discussion, protecting the page to enforce the restriction prospectively, any other action permitted by policy, and any combination of the above. I feel like this creates the right balance between allowing speedy deletion of disruptive articles and requiring admins to lean towards keeping good articles when a good-faith editor creates them. I believe any modification to G5 should include similar caveats. — Mdaniels5757 (talk • contribs) 21:38, 29 December 2023 (UTC)Reply
  • Option 2 as it makes it clear, without having to go though more complex rules, or processes. Option 3 would be my second preference. Graeme Bartlett (talk) 21:57, 29 December 2023 (UTC)Reply
    Rules, and processes, painful aren’t they. Benevolent dictatorship is so much more practical.
    G5 was always about completely, unambiguously blocked/banned people. These sanctions are not unambiguous. I expect they will fail WP:NEWCSD, and slipping new measures in like this is a real corruption of process. Let’s see a few cases put through XfD to see what’s really being talked about. SmokeyJoe (talk) 03:08, 30 December 2023 (UTC)Reply
  • Option 2 is my first choice and Option 3 is my second. Patient Zerotalk 00:12, 5 January 2024 (UTC)Reply

Discussion (Status of G5) edit

Wikipedia talk:Arbitration/Requests/Case/Gun control#Clarification request: Gun control (April 2019) is directly relevant. —Cryptic 16:14, 12 December 2023 (UTC)Reply

  • This might be a dumb question, but how does "Creations by banned or blocked users" (the heading of WP:G5) include any page created by any non-EC user? Violating a ban is not the same as violating a restriction. Primefac (talk) 17:42, 12 December 2023 (UTC)Reply
    Not a dumb question at all. This criterion is for creations by banned or blocked users, which explicitly includes an individual user's specific editing restrictions. It does not and has not ever extended to general page nor topic restrictions. I'm also having a hard time wrapping my head around the rationale for repealing the criterion - why would we do that? Ivanvector (Talk/Edits) 18:37, 12 December 2023 (UTC)Reply
    The argument (which I think is more or less valid) is that these users are effectively topic banned from topics which fall under ECR. They may not edit in the area, period end of story, and they should be dissuaded from doing so (the point of G5). Izno (talk) 19:55, 12 December 2023 (UTC)Reply
    Izno, one option on the table during the prior discussion was an ARCA to get clarity from ArbCom on whether that argument (non-ECR=topic banned) could be written into the procedures. Worth pursuing? Firefangledfeathers (talk / contribs) 20:00, 12 December 2023 (UTC)Reply
    I've raised that suggestion on the internal list, I think there is definite merit to it. I'm kind of surprised an RFC was started before exploring that option with any ArbCom members. :) Izno (talk) 20:08, 12 December 2023 (UTC)Reply
    I'd prefer if we didn't do that, for the biteyness I referenced earlier - declaring by policy that all new users are automatically procedurally banned from a rather long list of contentious topics, even if that is functionally true, is not very good optics to put it mildly. Policy-wise it would be much simpler to either modify G5 or create a new criterion (my preference) to permit deletion of pages created contrary to the general restriction. Ivanvector (Talk/Edits) 20:53, 12 December 2023 (UTC)Reply
    (ARB)ECR is already bitey, no ifs ands or buts about it. Changing the text to say that it's a topic ban makes it clear how it relates to this policy (among others), with little that I can see of unintended consequences. (I do not believe we would change ARBECR to remove its current exceptions.) Not sure where you get "long list of contentious topics", ECR by arbitration committee dictate is implemented only in a couple areas (Palestine-Israel and the not-entirely-unrelated "Polish history during World War II (1933-1945) and the history of Jews in Poland" areas).
    (ECR should be strongly distinguished from ECP, which is a technical mechanism which can be used to enforce ECR but which has no other non-historical relation to it. Not sure if that is also a point of confusion.)
    "COMMECR" for specific topic areas as I noted above can do whatever it wants (20:15, 12 December 2023 (UTC)) and I have no strong opinions besides that potential confusion may result from the community implementing ECR in a way which differs from ArbCom. (Which is already a problem incidentally since ArbCom has changed ECR at least once since many of the same community-thinking regimes have been implemented.... and even now the community is inconsistent on the rule in various regimes, so.... something for the community to review at VP generally now I guess.) Izno (talk) 21:39, 12 December 2023 (UTC)Reply
    You're right, I confused "topics subject to ECR" with "all contentious topics". I'll just say that, yeah, the whole regime is inherently and unavoidably bitey, but putting in writing that all new users are topic banned just seems more bitey, and maybe unreasonably so.
    And also I think this all makes a good point that Arbcom shouldn't be creating its own protection and enforcement regimes when parallel community regimes exist, as it invites confusion. I thought that deprecating discretionary sanctions for contentious topics was meant to harmonize those restrictions but it seems there's more work to do. Out of scope for this discussion but maybe something for next year's Committee to consider. Ivanvector (Talk/Edits) 22:59, 12 December 2023 (UTC)Reply
    ArbCom's came first? :) I think TBANs may have existed by the time that the committee thought up ECR, but the community is definitely following in the committee's footsteps on the use of ECR in areas it is tired of socks. Izno (talk) 23:10, 12 December 2023 (UTC)Reply
    Yeah, DS came before GS :) As far as I can tell, "partial bans" (admin bans from particular pages, different from blocks) were added to the banning policy near the end of 2005, and the policy already referred to Arbcom's authority to ban, so I don't know which came first. But I think that's a good example: topic bans are topic bans, whether they're community bans, unblock conditions, or arbitration enforcement. There are only differences in how they're logged and how they're appealed, which still isn't ideal, but it's better than having two completely separate processes that accomplish the same thing, or near enough that they may as well be the same except for the quirks of their implementation. Anyway, I said I wasn't going to sidetrack this discussion again, and I am failing. Ivanvector (Talk/Edits) 23:23, 12 December 2023 (UTC)Reply
    ... :) Izno (talk) 23:59, 12 December 2023 (UTC)Reply
  • For my edification and perhaps others, there was previous discussion. Izno (talk) 20:01, 12 December 2023 (UTC)Reply
  • Lets say, hypothetically speaking, that I was dumb and didn't understand option 4. If we repeal G5, but incorporate its principles into BANPOL...then what CSD would admins be using to achieve that. What am I missing here? CaptainEek Edits Ho Cap'n! 20:20, 12 December 2023 (UTC)Reply
    Presumably they'd delete the page without citing a CSD (and only citing BANPOL). Elli (talk | contribs) 21:45, 12 December 2023 (UTC)Reply
    I suggested one way option 4 might be implemented through a PROD process, where an editor who is not banned or blocked can go to WP:RFUD and accept responsibility for the content (including any problems). But shouldn't speedy deletion only be used for cases where there are very, very serious problems with the page (i.e. spam, vandalism, etc.) that has zero chance of being rectified? i.e. G3, G10, G11. For WP:BRV we have that a non-banned editor who restores content by a banned editor takes complete responsibility for such content. And "that have no substantial edits to others" can be quite subjective; maybe that needs to be clarified what that means. Awesome Aasim 16:24, 13 December 2023 (UTC)Reply
    Speedy deletion is explicitly only for cases that are uncontroversial and objective, the biggest problem with G5 as it stands is that it is neither. Speedily deleting pages due to ECR restrictions, through any process, would definitely not meet both criteria - anything objective would result in the deletion of things many people think should not be deleted, anything else would be subjective. It would, in theory, be possible to amend the deletion policy to allow for subjective speedy deletion of these or other pages, but you would need to get explicit consensus for that first. Thryduulf (talk) 18:21, 13 December 2023 (UTC)Reply
    (edit conflict) They wouldn't be using any part of the speedy deletion policy, or any other part of the deletion policy for that matter. Given that only the WMF can delete anything in a manner not provided for in the deletion policy, this would make the banning and deletion policies contradict each other (I hope everyone can agree this would be a bad thing). This Which is why ToBeFree correctly states that it is an invalid option. Thryduulf (talk) 21:47, 12 December 2023 (UTC)Reply
    WMF deletions are covered by deletion policy. That's what G9 is. * Pppery * it has begun... 21:49, 12 December 2023 (UTC)Reply
    (edit conflict) Yeah, that's what I think Option 4 is trying to say. I agree it makes no sense, though. It effectively amounts to a contradictory WP:POLICYFORK. * Pppery * it has begun... 21:49, 12 December 2023 (UTC)Reply
  • There are a couple comments above to the effect that, if we reject this change and admins delete these pages anyway, they face desysopping. As a practical matter, this is not the case: right now the only way for an administrator to get desysopped is at the direction of arbcom. If arbcom says admins can delete these pages, WT:CSD says they can't, and admins go ahead and delete them, arbcom doesn't seem likely to desysop them at WT:CSD's behest.
    If we want to change that, I see only two methods. One is to elect like-minded arbitrators. This also is impractical; we barely have enough candidates running this year to fill the open seats, and it's been that way for a few years in a row now; and just about any administrator with a pulse can meet the minimum 50% threshold. (By my count, about 90% of running admins in the past ten years of elections have done so; and I don't think we've ever failed to fill an arbcom seat at an election.)
    The other method is to formally amend arbitration policy to make it explicit that they don't have the authority to declare pages deleteable in this manner. —Cryptic 03:59, 18 December 2023 (UTC)Reply
    If the community explicitly rejects deletion as an option (as I continue to believe we should), then that is something that arbitrators will take into account should a case come their way. Their previous statement came at a time when the community had expressed no specific views on the matter. Such a case would only practically happen if an admin was aware of the explicit consensus and knowingly and intentionally deleting anyway, possibly on more than one occasion (anything less would almost certainly just result in censure at AN(I) for not keeping up with policy they are enforcing). On the issue of awareness, it will be a good idea to mention any change to the status quo resulting from this discussion in the admin newsletter. Thryduulf (talk) 04:15, 18 December 2023 (UTC)Reply
    (edit conflict) And thus begins the dissonance that lurks beneath every discussion on this page. My evil twin would be tempted to (in the event this closes as some option 1) add a section for deletions of this sort to Wikipedia:Database reports/Possibly out-of-process deletions and then go through and systematically appeal every single one to AN or AE (note that DRV is not a permitted venue for appealing arbitration enforcement actions). But that behavior would both likely fail to produce the required clear and substantial consensus to overturn the deletion (since this discussion is nowhere near that threshold) and get him sanctioned for disrupting Wikipedia to make a point.
    No, I don't actually have an evil twin, nor do I plan to do that, it's just a thought experiment.
    We did try to do what you proposed once at Wikipedia:Village pump (policy)/Archive 152#Petition to amend the arbitration policy: discretionary sanctions and deletions, but it petered out with only 22 out of the required 100 supports, and furthermore only barely had a majority in the first place. If that were reproposed, I would sign. Despite my position on the RfC above, there's no reason such deletions need to follow AE's especially-stringent provision against being overturned rather than following standard undeletion policy. * Pppery * it has begun... 04:15, 18 December 2023 (UTC)Reply
  • The thought that we would decide to speedy delete a page created by a newer user which is otherwise acceptable or revert edits to articles or talk pages other than edit requests that are clearly acceptable seems a blunt instrument and is going to put people of contributing. I'm fine however with allowing questionable pages to be deleted this way but would obviously need to pass NEWCSD. Crouch, Swale (talk) 17:46, 19 December 2023 (UTC)Reply
    • Well the page does not have to be deleted and an administrator or ECP user should be able to take responsibility for the page, and thus make it immune to a (G5) deletion. Any substantial edit by someone allowed to do so will avert a G5. Graeme Bartlett (talk) 22:00, 29 December 2023 (UTC)Reply
  • The problem is that I don't see how we could possibly have a situation where we don't have a CSD for articles created in violation of ECRs, and where those ECRs are still enforced. Where are we supposed to ask for ECR enforcement, then? We revert non-EC edits on sight, and we automatically ECP such articles even when no disruption has occurred. As far as I can tell, this is common and consensus practice. Why let the creation of new articles in the topic area be such a loophole? The editing restriction does not say "you are not allowed to edit unless one of us likes it", it says "you are not allowed to edit". (And if an EC user wanted to keep the article so badly, they could simply make substantial edits to it so that G5 no longer applies.) This RfC appears to be going down the direction of attempting to partially repeal an Arbcom remedy by consensus processes. Fermiboson (talk) 22:38, 21 December 2023 (UTC)Reply
    partially repeal an Arbcom remedy by consensus processes.  Like Mach61 (talk) 00:16, 24 December 2023 (UTC)Reply
    @Fermiboson why is partially repeal[ing] an Arbcom remedy by consensus processes an undesirable thing? Arbcom restrictions and other remedies are only ever enforced when the consensus of the community is that they make sense and are otherwise desirable. If community consensus is that (part of) a remedy is not desirable for some reason, then it absolutely should be repealed. Thryduulf (talk) 13:52, 30 December 2023 (UTC)Reply
    Isn’t Arbcom decisions listed as an entry in WP:CONEXCEPT? If there existed a (hypothetical) consensus at, say, WP Infoboxes that infoboxes weren’t a CT, that wouldn’t make CT sanctions inapplicable there. At the very least, is this not something that should go on Wikipedia:Arbitration/Requests/Clarification and Amendment? Fermiboson (talk) 14:49, 30 December 2023 (UTC)Reply
    If you read, rather than vaguely wave at, WP:CONEXCEPT you will see The English Wikipedia Arbitration Committee may issue binding decisions, within its scope and responsibilities, that override consensus. which says nothing about whether community consensus can override arbitration remedies after they are made (only that ArbCom may override community consensuses that pre-date their rulings). The community could effectively decide that e.g. infoboxes are no longer contentious by no longer treating them as contentious (i.e. all editing regarding them becomes harmonious) and/or declining to enforce any CT remedies regarding that topic area. Indeed, the former happens all the time - editors move on, disputes get resolved, and people forget that the topic area was ever contentious.
    Yes things need to go to ARCA to get the remedy formally repealed, but the best way to achieve that is for there to be a clear community consensus regarding the need. What I'm seeing in this RFC is a consensus that deletion is not always desirable, and no consensus that when deletion is desirable that such deletion should be done speedily. Thryduulf (talk) 18:28, 30 December 2023 (UTC)Reply
    You'll see that my reply was worded as a question, because it was that - an honest question.
    Regardless, I'm not sure I agree with you on the status of the consensus, but I take your point about consensus overriding outdated remedies. That said, if this RfC is closed as option 1, I would definitely be hoping for some sort of clarification from Arbcom on how we're supposed to enforce ECR. (I take it that there is still consensus to ECP the relevant articles, revert non-EC edits inserting CTs into unprotected articles, and such.) Fermiboson (talk) 02:42, 5 January 2024 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Post RfC discussion edit

There is consensus for option 2 or option 3. I think it might be a good idea to clarify whether GS/CT restrictions fall under G5 or if a new criteria G15 should be created. I think either is okay, as long as it gets mentioned somewhere on the page. Awesome Aasim 21:22, 30 January 2024 (UTC)Reply

If we must authorise speedy deletion as a GS/CT remedy (and I continue to believe it is a bad idea to do so) then the very first step is to set out a wording that meets all of the WP:NEWCSD requirements (which isn't going to be easy). Once we have that we can see how similar it is to G5 and thus whether it works best as part of that criterion or as its own standalone one. Thryduulf (talk) 02:29, 31 January 2024 (UTC)Reply
I agree it is a bad idea. Delegated speedy deletion being further delegated, makes a mockery of the leading line of CSD, and dangerously elevates ArbCom as a governing power, free to delegate their power. This is a bad pathway.
Better to block any editor who breaks their partial ban, and leave it to their unblock request to make the case that it was not a partial ban violation. SmokeyJoe (talk) 10:43, 31 January 2024 (UTC)Reply

Is anybody actually interested in this? As it stands we have a consensus that these deletions should be allowed, but the relevant policy still prohibits them. Thryduulf (talk) 23:21, 10 February 2024 (UTC)Reply

Do you have any objections (specific ones, and consistent with the RFC close) to the pre-RFC version? —Cryptic 23:33, 10 February 2024 (UTC)Reply
It fails NEWCSD point 2, because deletion speedy deletion is not required for the majority of such pages - especially ones created in good faith. G5 (which is already too vague) is intended to allow for the deletion of content created by editors who have been repeatedly disruptive and who are fully aware that they are being disruptive and why it is considered disruptive, not for allowing easier biting of newbies who happen to start on a contentious topic . Thryduulf (talk) 01:11, 11 February 2024 (UTC)Reply
So no objections consistent with the close? I mean, you don't get to stonewall this against the consensus above on NEWCSD2 grounds any more than I do the R5 proposal below on NEWCSD3 and 4 ones. Best either of us can do is to stand aside, document how very wrongly things turn out, and - if our fears are proven justified - attempt to convince people to repeal once we've got stronger evidence to point at. —Cryptic 03:11, 11 February 2024 (UTC)Reply
My objections are consistent with the close, and I'm not attempting to stonewall. Thryduulf (talk) 11:43, 11 February 2024 (UTC)Reply
That version looks fine to me. Firefangledfeathers (talk / contribs) 03:17, 11 February 2024 (UTC)Reply
I would replace "general sanctions" with "in violation of general sanctions" with "in violation of a topic-wide extended confirmed restriction", to be less ambiguous. Although on second thought that link points to ArbCom procedures and thereby misses the community RUSUKR restrictions, which should probably be fixed. Until that happens I guess I'm fine with the pre-RFC version. * Pppery * it has begun... 03:20, 11 February 2024 (UTC)Reply
I would be fine with "in violation of an extended-confirmed restriction" without a link to WP:ECR. I'm not aware of any non-ECR general sanctions that would apply here. It's possible that the community or ArbCom would authorize some other topic-wide creation restriction, so maybe "general sanctions" is more future-proof? Firefangledfeathers (talk / contribs) 03:27, 11 February 2024 (UTC)Reply
I would prefer the broader "general sanctions" so that it's more future-proof but I'd also be fine with an unlinked "extended-confirmed restriction". Callanecc (talkcontribslogs) 03:40, 11 February 2024 (UTC)Reply
By “future-proof”, do you mean “lax”? SmokeyJoe (talk) 12:39, 11 February 2024 (UTC)Reply
No, I mean future-proof in that we won't need to go through this process again if the community comes up with another page or topic-level sanction that prevents a group of edits from creating pages. Callanecc (talkcontribslogs) 08:32, 12 February 2024 (UTC)Reply
If that happens then it should be trivial at the time to get consensus about whether this should be enforceable by speedy deletion, and if so what the NEWCSD-compatible wording implementing that is. Unless and until that happens, it's just less precise language that increases the risk of problems down the line. Thryduulf (talk) 11:38, 12 February 2024 (UTC)Reply

Y'all seem a little stuck, so let me throw something out to get discussion started.

A12. Author violating arbitration committee extended confirmed restriction

Topics under a contentious topic extended confirmed restriction may not be created in mainspace by editors who do not possess the extended confirmed permission.

I purposely changed it from G to A to exempt user sandboxes, as that was mentioned as a concern somewhere, although I'd be fine with changing it back. Thoughts? –Novem Linguae (talk) 04:29, 11 February 2024 (UTC)Reply

My preference is that we try incorporate it into G5 but I don't have an issue with a new criteria. I think it does need to be G rather than A as it would also apply to drafts, talk pages, Wikipedia pages and so on. Callanecc (talkcontribslogs) 04:42, 11 February 2024 (UTC)Reply
Support. ECR does not logically fit under G5, and abandoning logic necessarily means abandoning “objective” and screws up the foundational basis of CSD.
Support “A” because it only needs to apply to mainspace. It should not apply to drafts or userspace. ECR accounts putting stuff in talk or project namespaces should be dealt with as with any WP:GAMING. SmokeyJoe (talk) 12:38, 11 February 2024 (UTC)Reply
That seems like something that should be brought up as an amendment request (for the ArbCom-imposed ones) and WP:VPR (for the community imposed one). Callanecc (talkcontribslogs) 08:32, 12 February 2024 (UTC)Reply
ArbCom should not be overriding policy. WP:CSD should be a standalone policy. If ArbCom want ECR violations to be speediable, as opposed to a deletion reason, and for this to be applicable to all namespaces, not just mainspace, then they should be clear about this, and it needs ratification here at CSD. WP:CSD should not be asked to contract out WP:CSD-writing to ArbCom.
It is not clear that ARbCom insists that ECR violations in userspace should be speediable. If userspace ECR violations are not speediable, then it is not clear that weird namespace creations, such as in project or project_talk namespaces, or worse, should not be treated as a mistake and speedy-userfied (without trailing redirect). The rationale here is merely that the newcomer should not be bitten. Arcane rules should not justify beating and confusing the newcomer. If you speedy delete their userpsubpage or draftpage, how are they meant to hope that they will understand exactly what they did wrong. These are my concerns. Newcomer biting, as well as subverting CSD by addition of large door and subjective new criteria.
I think User:Novem_Linguae's A12 is obviously agreeable, and the first question is: Does anyone disagree. The second question is: Can you please justify why it needs to be broader (eg why not allow MfD deletions in userspace, and speedy-userfication from other namespaces. Already, the one case at MfD did not result in deletion!).
-- SmokeyJoe (talk) 07:27, 13 February 2024 (UTC)Reply
This looks good to me. I would suggest removing "arbitration committee" and "contentious topic", and I think we shouldn't link WP:ECR. The community has also established extended confirmed restrictions that authorize deletion, and the restrictions do not follow the exact text at WP:ECR. See for example WP:GS/AA or WP:GS/RUSUKR. Firefangledfeathers (talk / contribs) 17:03, 13 February 2024 (UTC)Reply
How about this:

G15: Pages created in violation of a contentious topic restriction or other general sanction

Pages that are created by users in violation of an arbitration- or community-authorized contentious topic restriction or other topic-specific general sanction, with no significant edits from others. This does not apply if the user is explicitly banned from the topic area (see WP:CSD#G5), nor does it apply if a user not subject to the restriction takes responsibility for the content.

And then we can have WP:RFUD for an appropriate user to take responsibility for such content, and WP:DRV if the creator believes the deletion was done out of process. Awesome Aasim 21:18, 15 February 2024 (UTC)Reply
Too broad. Hopelessly subjective. SmokeyJoe (talk) 22:57, 15 February 2024 (UTC)Reply
I'm failing to see how this is subjective. Either the page was created and edited in violation of a general sanction, or it was not. Just like either the page was created as ban evasion, or it was not. Awesome Aasim 17:33, 16 February 2024 (UTC)Reply
The subjective part I think is that not everything that could be deleted under this criterion should be deleted. Awkward42 (talk) [the alternate account of Thryduulf (talk)] 21:43, 16 February 2024 (UTC)Reply
The same argument can be said about G5. An article can be of exceptional quality but written by a banned editor in that topic area. The point of bans and topic restrictions is that allowing specific users or groups of users in specific topic areas pose a serious risk of disruption for any number of reasons, that we shouldn't allow them to edit there at all. Not that there will sometimes be good content that is deleted for that reason. Awesome Aasim 22:18, 16 February 2024 (UTC)Reply
The same argument can be said about G5 indeed, which is why G5 would not be approved if proposed today, and why it is one of the most controversial criteria. Whenever we delete good content just because of who wrote it we are cutting off our nose to spite our face. Good content should be kept and bad content should be deleted, in all cases who the author is is irrelevant. Awkward42 (talk) [the alternate account of Thryduulf (talk)] 23:11, 16 February 2024 (UTC) Awkward42 (talk) [the alternate account of Thryduulf (talk)] 23:11, 16 February 2024 (UTC)Reply
G5 began objective. It used to read simply:
Banned user. Pages created by banned users while they were banned.
Scope creep is a problem. SmokeyJoe (talk) 06:03, 17 February 2024 (UTC)Reply
Indeed scope creep is a problem.
In my humble opinion, I would have G5 and the proposed G15 deletions undeletable at WP:RFUD by someone who is not subject to the ban/block or topic restriction. Instruction creep is really the enemy that we should fight here. Awesome Aasim 02:53, 18 February 2024 (UTC)Reply
Perhaps then what is needed is simply (sticky) PROD, which can only be removed by an extended confirmed editor taking responsibility for it. This guarantees at least two pairs of eyes and gives people a week to find the content. If it is too problematic to remain for a week then it should meet at least one existing speedy deletion criterion. Thryduulf (talk) 03:23, 18 February 2024 (UTC)Reply
Sticky PROD sounds like a much better response to the subjective violation of a subjective partial topic ban pronouncement by ArbCom, and especially where it has spilled over to classes of editors, not specifically named users.
Speedy deletion, with a log reference to a peculiar technical requirement, is confusing and chilling to newcomers attempting to contribute to an important topic.
Where good faith can’t be assumed and disruption is at play, it’s a behavioural problem, and behaviours should be responded to by warnings and blocks, not content deletion.
This especially applies to content creation in userspace and draftspace, where there is no urgency to product the product (WP:PPP). SmokeyJoe (talk) 07:15, 18 February 2024 (UTC)Reply
Additionally, if something is created in mainspace then existing processes such as draftifcation, userfication, and AfD exist to deal with content that is actually (rather than just procedurally) unfit to be public-facing without needing deletion. Thryduulf (talk) 13:08, 18 February 2024 (UTC)Reply
There are speedy templates that operate a bit like PROD: namely, a lot of the {{di}} templates, as well as WP:C1. I fail to see how this is any different. Awesome Aasim 17:13, 18 February 2024 (UTC)Reply
With a PROD anyone can remove for any reason at any time, because it's just one person's opinion that deletion is uncontroversial. With sticky-PROD anyone can remove at any time if they've taken specific actions (e.g. added references to a BLP), because it's one person's opinion that it's not possible to do that action. With speedy deletion, the bar to removal is higher as you have to assert that the page does not meet the criterion for some reason, because to be a valid speedy deletion criterion it must be community consensus that everything that meets the criterion should be deleted. WP:C1 is proper speedy deletion as community consensus is that categories that have been empty for 7 days should be deleted. Most of the {{di}} ones are a mix of proper speedy deletion (but with a delay because it can take time to verify that the files do meet the criterion) and PRODs in disguise.
Either a page was created by a non-ECR editor or it wasn't, we don't need time to verify that, and waiting any amount of time doesn't change that. However, we do need to give time for other editors to verify that the content should be deleted. Thryduulf (talk) 18:43, 18 February 2024 (UTC)Reply
Maybe we can enforce the ECR restriction in different ways, like edit filters.
We can have a speedy criteria in case anything slips past, but we can tag if the article appears to contain keywords hinting at an ECR topic, maybe also warn the user in the edit box. Awesome Aasim 17:06, 19 February 2024 (UTC)Reply
Folks, what exactly is the problem here? There's a consensus from the RfC that either G5 applies, or a new Gx should be created. Modifying G5 is simple, just add the text from Awesome Aasim's G15 suggestion as a bullet point and it's done. It's literally the easiest option, and doesn't even require changes to tools like Twinkle. Or create the G15 suggestion from Awesome Aasim and again, we're done.
As someone who's completely uninvolved in the RfC and post-discussion until now, I'm sorely tempted to just make one of these edits myself, probably the G5 modification, because it shouldn't be this hard to just implement. It's been 8 days since the last comment. Can we please see some action here, or am I just going to do this? Sideswipe9th (talk) 02:24, 28 February 2024 (UTC)Reply
What is it you are not understanding about the comments and objections noted above? (this is not a sarcastic question, I'm genuinely not understanding what is unclear to you). I'm disappointed the (sticky) PROD suggestion has not received more input, given that it seems achieve the outcome those supporting the expansion of the speedy deletion criteria want while avoiding (at least most of) the incompatibilities with the requirements for speedy deletion criteria noted. The reason it's proving harder to implement than a surface reading suggests it should is because when you look at the detail you find that converting a vague aspiration into something that meets the NEWCSD requirements is actually hard. If you want to ignore those requirements and just implement the subjective, overly broad criterion proposed then you might be able to get consensus to do that (although I personally hope you don't, as the requirements exist for good reason), but that consensus doesn't exist yet. Thryduulf (talk) 03:07, 28 February 2024 (UTC)Reply
It's simple, there's a consensus from the RfC that either G5 applies, or a new Gx should be created. Either option appears to fulfil NEWCSD. Pick one of those two, and do it. If there's no action on this by tomorrow, I'm just going to pick the easiest option to implement myself (G5) and do it. Sideswipe9th (talk) 03:14, 28 February 2024 (UTC)Reply
Either option appears to fulfil NEWCSD the outcome of the first RFD was "create or modify a criterion to allow this", which is neither compatible nor incompatible with NEWCSD (it's not a proposal). For the reasons explained above multiple times, the specifically proposed wordings do not: they're subjective and overly broad. I explicitly and actively oppose adding this to G5 as that just makes one of the most controversial criteria more complicated and even less objective. G15 is a little better as it doesn't muddy multiple only semi-related things in together, but it doesn't solve the overreach problem. The A12 proposal is the least problematic - there is no consensus whether drafts and talk pages should be deleted so they need to be excluded from any speedy deletion criterion compliant with speedy deletion policy, but (like the other suggestions too) it hasn't attracted enough comment to determine whether it has consensus or not.
What needs to happen is either more discussion until we arrive at a consensus for something that is compatible with policy, a consensus to ignore the policy, or no change through lack of interest in achieving consensus. What we really do not need is reckless changes to policy in the absence of consensus. Thryduulf (talk) 03:29, 28 February 2024 (UTC)Reply
Here's an explainer for how either criteria meets NEWCSD:
  1. Objective: A user either is or is not extended confirmed. Whether an article does or does not meet ARPBIA4, GS/AA, or GS/KURD is an objective assessment that any editor in good standing can make.
  2. Uncontestable: WP:ARBECR#A2 states that non-extended-confirmed editors may not create new articles in content areas covered by this sanction. ARBECR#A1 states that non-extendend-confirmed editors may only use the Talk namespace to make edit requests, and canno
  3. Frequent: We have non-extended-confirmed editors creating articles in content areas covered by ARBPIA4, GS/AA, and GS/KURD. Per ARBECR and the copied versions in GS/* non-extended-confirmed editors are not allowed to create these articles. This speeds up deletion of articles created in violation of that sanction.
  4. Nonredundant: There are no other CSD that currently apply for enforcement of ARBECR.
This is quite clearly an objective criteria, either a user is or is not extended confirmed, and an article either is or is not in one of the relevant sanction areas. I'm don't really want to be dragged into a state where I become INVOLVED in this, because this really should have been implemented already. Sideswipe9th (talk) 03:33, 28 February 2024 (UTC)Reply
Also worth noting, {{db-gs}} has existed as a valid template to use here since November 2023, telling the processing page deleter that a nomination can be deleted under CSD G5. Category:Candidates for speedy deletion as having been created in violation of general sanctions gives a report of all pages currently tagged with the db-gs template, and tells reviewing page deleter that a nomination can be deleted under CSD G5. We're already using G5 in practice to delete violating articles. Making the simple edit simply brings the text of the policy in line with how it's already being used in practice. Sideswipe9th (talk) 03:41, 28 February 2024 (UTC)Reply
  1. A user either is or is not extended confirmed. This is indeed objective, but Whether an article does or does not meet ARPBIA4, GS/AA, or GS/KURD is an objective assessment that any editor in good standing can make. varies - some things are clearly within the topic area, some things clearly aren't, but there is a very large grey area (at least for ARBPIA4 and GS/AA, I'm much less familiar with GS/KURD).
  2. There is no consensus that every page created in violation of these restrictions should be deleted (e.g. moving, redirecting, draftifying are better in some circumstances).
  3. Correct.
  4. Correct.
{{db-gs}} has existed as a valid template to use here since November 2023, telling the processing page deleter that a nomination can be deleted under CSD G5. Until not long ago this template would have been speedily deletable as a misrepresentation of policy and really should be deleted or amended as G5 says no such thing. Thryduulf (talk) 10:31, 28 February 2024 (UTC)Reply
2. Uncontestable. This is only really demonstrated by putting a series of cases through XfD and having them all result in SNOW deletion. The one MfD case did not result in deletion. SmokeyJoe (talk) 11:18, 28 February 2024 (UTC)Reply
If you really want to be specific about criteria 2, almost all pages that could be deleted using the rule, should be deleted (bolding added for emphasis); and I have a strong feeling that the community, especially community members who see WP:ARBECR'd articles at XfD, are going to feel it a waste of time to bureaucratically establish a criteria that has already been enforced, just not explicitly. These deletions were happening long before this discussion happened for as long as ARBECR existed, before anyone even attempted to add ARBECR to G5. There are no viable alternatives to speedy deletion for this kind of stuff anyway; blank pages provide a terrible experience for readers and draftification does not fix the fact that the creator was banned/blocked/violating a general sanction restriction. The whole reason community would impose WP:ARBECR in a topic area (or ask ArbCom to do so) is they don't want to waste time at XfD or PROD. Deletion is reversible and I think the best compromise would be to have REFUND available to anyone not subject to the general sanction. I would also clarify that ARBECR does not mean that pages must be deleted either. Awesome Aasim 14:36, 28 February 2024 (UTC)Reply
Those objections deal with articles, not other types of pages. That people have been speedily deleting things outside of the speedy deletion policy does not mean that we must mangle the speedy deletion policy to fit, it means people should stop speedy deleting those things. Thryduulf (talk) 14:41, 28 February 2024 (UTC)Reply
That or the policy is wrong. WP:IAR and WP:NOTBUREAUCRACY. We don't work by rules lawyering, we work by consensus. And I don't think we should send ARBECR violating articles to XfD to prove that this is uncontestable either, as it's just a waste of time. Community policies are just a reflection of community consensus. Deletion is also reversible; which is why we have WP:RFUD. Awesome Aasim 15:44, 28 February 2024 (UTC)Reply
WP:RFUD is currently silent on whether it is applicable to G5 deletions (some criteria are explicitly listed as in scope, others are explicitly listed as out of scope, G5 is not in either list) but a search of the archives suggests that such pages are only refunded when the G5 was in error. A new or modified criterion could be explicit about this, but it's a strong argument against lumping it in with G5 as some but not all G5s being refundable would be confusing, especially to new editors.
IAR is never a reason to speedily delete a page. IAR is only for actions that uncontroversially improve the encyclopaedia, the speedy deletion criteria list the only times it is uncontroversial to delete a page without consensus to do so (prods are a special case of silent consensus).
There is no way to demonstrate that deletion of ARBECR pages is uncontestable is to demonstrate that they are not contested. This is not POINTY, a waste of time or process for the sake of process, it is simply getting evidence to back up an assertion. So far 100% of the pages sent to MfD have not been deleted, which is as far from unontestable as you can get.
It's true that we work on consensus, which is why (most of us) are discussing things not making unilateral changes to policy that clearly do not have consensus. And before you point again to the RFC, that was a consensus to modify an existing criterion or add a new one and was completely silent on which should be done and importantly how either should be done. Thryduulf (talk) 16:14, 28 February 2024 (UTC)Reply
Do we really need to have an implementation RfC here? Put the G5 and G15 texts up against "none of the above"? Because to me that seems like kicking the can down the road for another 30 days, while ARBECR deletions under G5 continue in practice. It's true that our policies and guidelines are often decided by RfC, but they also are often decided or refined through how they're used in practice by "editors on the ground". Why can't we just implement this and move back to editing? Sideswipe9th (talk) 16:46, 28 February 2024 (UTC)Reply
We need consensus. That can be arrived at by an RFC or it can be arrived at by normal discussion but it can't be arrived at by ignoring discussion. We can't "just implement this and move back to editing" because there are strong objections to doing so and no consensus to overrule those objections.
We have several options at this point G5, G15, A12, (sticky) prod, XfD only, none of the above. G15, A12 and sticky prod need more discussion and workshopping before being put to any sort of vote or similar. Thryduulf (talk) 17:43, 28 February 2024 (UTC)Reply
We need consensus There are multiple ways consensus can form. RfC and discussion are two of those ways. Through editing is another. Policies and guidelines however can also change based on how editors are tackling an issue in practice. Currently in practice, articles that violate ARBECR or the GS equivalent are typically deleted under G5. There have been at least 16 such deletions since August 2023 (possibly more, there's no standardised log entry for these and the quarry might have missed some that log it differently). Yes that is technically out of step with how G5 is currently written, but that suggests to me that resolving this means adjusting the text of G5 so that the letter of the rule is in line with how it's actually being used.
Why can't we just have the text of the policy reflect how it's currently being used in practice?
We have several options at this point We could do an RfC on all of those options, but even if we did that as some form of ranked voting it'd likely just result in no consensus due to there being too many options. Better to just pick one or two, and run that against none of the above. Sideswipe9th (talk) 18:55, 28 February 2024 (UTC)Reply
Yeah I think we should just write something and drop the stick. It can always be refined later based on actual implementation but it should not be excluded. There already is consensus to implement ECR deletions so why can't we just leave it at that. Awesome Aasim 17:45, 28 February 2024 (UTC)Reply
I would be fine with such an implementation. I've been fine with many of the proposals made here. I'm eager to implement something in accordance with the accumulated consensus of ArbCom, the community at AN, and the community here in the RfC. I think it would be fine to refine whatever we implement. I think it would be great to be as compliant with NEWCSD as possible, but it's not some pinnacle of policy. It's a notice at the top of a policy talk page, and it shouldn't be a major obstacle to implementing consensus. The NEWCSD-based arguments were evaluated as part of the RfC, and the community decided to proceed with an adapted or new criterion for GS speedy deletions. Firefangledfeathers (talk / contribs) 03:41, 28 February 2024 (UTC)Reply
Yeah it was kind of pointless rambling on how to actually implement this. We should probably continue to further clarify the wording but hey it's better than nothing! I do think we should definitely rethink how we implement G5 deletions though. Not the wording, but what should happen.
I think G5 deletions should be REFUND-able so that users that are not subject to a ban or block, or the general sanction restrictions mentioned, can fairly request undeletion of the deleted material and take charge of fixing any problems with the text. For the user that is allegedly subject to the general sanction, we can have deletion review if they think the deletion was done out of process. Awesome Aasim 05:34, 28 February 2024 (UTC)Reply
We should probably continue to further clarify the wording but hey it's better than nothing! badly worded speedy deletion criteria are worse than nothing - this is the entire reason why the NEWCSD requirements exist in the first place. Speedy deletion is one of the bitiest things it's possible for an admin to do and so must be used with caution so as not to delete things there is no consensus should be speedily deleted. Thryduulf (talk) 10:34, 28 February 2024 (UTC)Reply
I think we need mediation. Why can't we agree on the wording of something that there already is consensus for above. Does anyone want to open something on WP:DRNB? Or maybe we can go to a different WP:3O forum like WP:VPIL or WP:VPPL to get wider input. Awesome Aasim 17:59, 28 February 2024 (UTC)Reply
Honestly I think the outcome from a DRNB or 3O would just be "have an RfC". Technically I came in here completely uninvolved in the past discussions so could kinda be considered a 3O if you don't look too closely at it I guess. Sideswipe9th (talk) 18:03, 28 February 2024 (UTC)Reply

Question the close edit

User:S Marshall. You wrote:

It's questioned whether Arbcom is empowered to authorise speedy deletions at all. Since both option 2 and option 3 agree that general sanctions can, in some circumstances, lead to speedy deletions, it necessarily follows that the community delegates that power to Arbcom.

Can you please explain why it necessarily follows? I don't think that it necessarily follows. I think that a possible, even better, interpretation, is that ArbCom has introduced a new WP:DEL-REASON. And from there, it is possible that WP:NEWCSD is met, or that in somecases an existing CSD is already met. However, it does not necessarily follow that the community delegates the power to overwrite this policy. That interpretation is quite extreme, to jump straight from something not even being a reason for deletion to arbcom wanting it to be speediable by their inference. --SmokeyJoe (talk) 03:47, 29 February 2024 (UTC)Reply

  • I found consensus somewhere between options 2 and option 3. So that gives me two ways:
  1. Option 2—add general sanctions to G5, which is to say, speedy deletion under general sanctions is permissible, and falls under G5; or
  2. Option 3—add general sanctions to its own CSD, which is to say, speedy deletion under general sanctions is permissible, and falls under some new speedy deletion criterion.
Therefore speedy deletion under general sanctions is permissible. QED.
Arbcom has the power to authorize general sanctions. Therefore Arbcom has the power to authorize speedy deletion. Indirectly so, but quite clearly.
Sanity check: some editors adopted the position most clearly argued by Thryduulf, although Ivanvector also explained it well, which was to question whether Arbcom has the power to authorize speedy deletion at all. Those editors opposed option 2 and option 3.—S Marshall T/C 14:12, 29 February 2024 (UTC)Reply
I don’t like the possible inference that editors at WT:CSD supporting new CSD text matching an ArbCom statement implies that they support ArbCom having the power to overwrite WP:CSD. I don’t think you’ve supported your words that the community delegates that power. SmokeyJoe (talk) 00:54, 1 March 2024 (UTC)Reply
Arbcom has the power to authorize speedy deletion
I think that needs to be put, cleanly, to an RfC. It is a serious expansion on Wikipedia:Arbitration/Policy, which has a formal amendment process. SmokeyJoe (talk) 01:07, 1 March 2024 (UTC)Reply
Arbcom don't have the power to "overwrite CSD". They have wide powers to deal with disruptive conduct, including the power to delete content without giving a reason in public (in their personal capacity as checkusers and oversighters) and to authorize the deletion of content by others (who must be sysops who've individually granted access to the delete tool by the community). Consensus is that Arbcom can do these things; what's disputed is which flavour of alphabet soup we use to describe that power. You can start a confirmatory RFC if you like, but to me, that doesn't seem like a good use of community time, because there's so little doubt that Arbcom has that power.—S Marshall T/C 01:42, 1 March 2024 (UTC)Reply

Discussion Continued At WP:VPPL edit

See WP:VPPL#How to word G5 expansion/G15 new criteria. Awesome Aasim 22:34, 28 February 2024 (UTC)Reply

Improper disambiguation redirects edit

First RfC edit

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
Procedural close. Per WP:PGCHANGE, this discussion was required to be widely advertised; it was not. Editors are encouraged to participate on the follow-up RfC below. voorts (talk/contributions) 01:35, 8 March 2024 (UTC)Reply


For a while now WP:RFD has been flooded with nominations for redirects that a missing a space between the term and the opening parenthesis of a disambiguator (e.g. Constantine(video game) and Scaramouche(1952 film)), see for example sections 17 to 35 at Wikipedia:Redirects for discussion/Log/2024 January 31, sections 17 to 57 at Wikipedia:Redirects for discussion/Log/2024 February 1, and similar in the days leading up to them. These discussions invariably end up being deleted uncontroversially, and the number of discussions is causing issues for RfD (see e.g. Wikipedia talk:Redirects for discussion#Can we reduce the number of RfDs transcluded on this page?). Accordingly I propose a new speedy deletion criterion R5:
Redirects with no space before a parenthetical term, e.g. "Foo(bar)", "Joe Smith(disambiguation)". This does not apply to terms that will correctly or plausibly be searched for without spaces, e.g. 501(c)(3)

  • Before nominating a redirect under this criterion:
    • Create the correctly spaced version as a redirect to the same target if it would make a good redirect but does not exist
    • Adjust any incoming internal links to point to the correctly spaced version.
  • This criterion does not apply if the redirect is the result of page move made less than 30 days ago, but criteria R3 and/or G6 may apply.

The rationale for the last bullet is to allow time for mirrors, etc. to catch up. If the page was moved and then immediately moved again, or created at this title then quickly moved then this title was obviously created in error and G6 applies. Thryduulf (talk) 13:34, 2 February 2024 (UTC)Reply

  • I'd support this. As you said, it's been an ongoing issue and the discussions end the same way every time. It's adding unnecessary bureaucracy when the outcome is clear from the beginning. Hey man im josh (talk) 13:39, 2 February 2024 (UTC)Reply
  • Support – these are among the most straightforward closes I regularly encounter at RfD, and they aren't adequately covered by R3 and G6. Complex/Rational 13:54, 2 February 2024 (UTC)Reply
  • Support. I would also support coverage of other obvious typographical errors, such as disambiguators missing a closing paren. BD2412 T 15:26, 2 February 2024 (UTC)Reply
    The most recent large discussion I found about missing closing parentheses was very controversial as they were working around an external link problem. I can't remember what the outcome was in the end but it was relisted a couple of times, so not at all suitable for speedy deletion. Thryduulf (talk) 15:30, 2 February 2024 (UTC)Reply
    I've started trying to track past nominations such as these and I have 3 bulk nomination links saved in my notes for these types of redirects. They're for February, 2019, April, 2019, and October, 2022, the most recent of which was contentious. I'm sure you already know Thryduulf, but I thought I'd share the links for reference. Hey man im josh (talk) 17:28, 2 February 2024 (UTC)Reply
  • Support * Pppery * it has begun... 16:11, 2 February 2024 (UTC)Reply
  • Support but I would title it "Redirects with no space before a parenthetical disambiguator" to define the scope. If not then things like 501(c)(3) absolutely will be carelessly tagged and deleted. Ivanvector (Talk/Edits) 16:36, 2 February 2024 (UTC)Reply
    Good suggestion. I think that's a good differentiation to make. Hey man im josh (talk) 17:32, 2 February 2024 (UTC)Reply
  • Why aren't these R3's? Is it just that we're only now working through a backlog of very old ones that nobody noticed before? What happens when those are gone? And would a database report to detect new ones help? —Cryptic 17:07, 2 February 2024 (UTC)Reply
    Some of the ones that have been nominated recently have been around for over a decade. I guess a database report wouldn't harm. Thryduulf (talk) 17:10, 2 February 2024 (UTC)Reply
    Very preliminary version at quarry:query/80153. Very many false positives still, chemical names in particular, and it's not immediately obvious how to filter them out without introducing false negatives. I'd hope that most wouldn't be interpreted as a disambiguator, but I'm sure someone would eventually carelessly speedy ones like Chromium(III), and I wouldn't be entirely surprised to find ones of the much-more-common sort like Dysprosium(III) nitride tagged db-r5 either.
    What I'm not seeing are recently-created ones. The current most recent is Deportivo Toluca F.C.(women) from January 13, and the next most recent is Fletcher Ladd(justice) from December 14. Unless RFD has been very diligent about deleting recently-created ones in particular recently - has it? - this suggests to me a backlog we can hope to eventually clear rather than an ongoing and permanent problem. —Cryptic 17:55, 2 February 2024 (UTC)Reply
    I tweaked your query to just filter out the articles, which got the total down to 12.2k. If it helps, Dcirovic seems to have created 900+ of the redirects that appear in the query. I expect that they're legit ones which could be removed. I also noticed that your list is including redirects that contain "-(", which could be something to look at to trim it a bit. Hey man im josh (talk) 19:22, 2 February 2024 (UTC)Reply
    Filtering out non-redirects is good if you're looking for more to bring to RFD, or potentially speedy. It's not so good in the context of this discussion (since it also filters out redirects currently at RFD, since they're not technically redirects while tagged) or in an ongoing database report (we'd want to see pages created at or moved to titles like these as soon as they happen, not just after someone else happens to notice them, moves them back, and doesn't deal with the redirect).
    You can reasonably go further than just eliminating -( by looking specifically for a letter- or digit-like character before the paren, as in quarry:query/80157. Again, if I were watching a date-ordered report, I'd rather see them show up than risk missing a false negative - it misses Deportivo Toluca F.C.(women) from above, for example. —Cryptic 20:59, 2 February 2024 (UTC)Reply
    Even just removing '-(' is going to filter out redirects we should deal with, like Hurdling-(horse race). —Cryptic 21:28, 4 February 2024 (UTC)Reply
    I don't know the flavor of SQL being used here and I don't have Quarry access but could it stand to have something along the lines of AND NOT EXISTS (SELECT 'X' FROM page otherpage WHERE otherpage.page_title = REPLACE(page.page_title, '(', ' (')? — Preceding unsigned comment added by Largoplazo (talkcontribs) 20:56, 3 February 2024 (UTC)Reply
    WMF-run wikis are backed by MariaDB, a MySQL fork. You (and anyone else with a registered account) do have Quarry access, if you care; click "Login" from the upper right and it'll bounce you through meta. And, again, that sort of refinement is going to result in many false negatives - this time, it'll find pages that haven't been partially dealt with (by someone creating the properly-disambiguated title), but miss cases where someone saw a page at Acme(widget manufacturer) and moved it to Acme (widget manufacturer) without dealing with the leftover redirect. —Cryptic 20:38, 4 February 2024 (UTC)Reply
    That right there is one of the largest groups of false positives I've found: Valid chemistry-related titles with parentheses without spacing before/after parentheses. Thus .. my reservations about making this a CSD. Steel1943 (talk) 19:59, 4 February 2024 (UTC)Reply
    (For what it's worth, here's the regex query I've developed over time that reduces the amount of chemistry-related false positives: [^ 0-9:\-\)]\([^0-9\-\)][^\)]. (Search using this regex [takes a bit to load]) However, it also doesn't allow any numbers directly after a "(" which will make "bad" disambiguators that start with years not appear in the list either.) Steel1943 (talk) 20:09, 4 February 2024 (UTC)Reply
    (Well, I just tried my own regex a few times, and even that list on 20 titles has like 2–3 false positives. Over the years, trying to write the perfect regex to reduce false positives has been rather difficult.) Steel1943 (talk) 20:15, 4 February 2024 (UTC)Reply
    @Steel1943 What we could do is tag chemistry redirects with a proper redirect category and then exclude the redirect template or category from the query. This way future editors will also know that these aren't fit for speedy deletions. Gonnym (talk) 20:46, 4 February 2024 (UTC)Reply
  • Support it seems to pass most of the NEWCSD requirements, objective, as noted all discussions seem to today result in deletion with most people agreeing, uncontestable, there is a clear consensus today to delete these, frequent, although it may become less frequent if newer ones are caught and deleted under R3 other namespaces and if future ones get missed (and some in other namespaces not yet checked as all from what I can remember have been namespace redirects but there will probably be such redirects in other namespaces) will be needed, nonredundant, as noted while many newer ones can be deleted under R3 older ones can't and although it could already be argued these can be deleted under G6 it would probably be more sensible for the same reason G14 was split to have a separate criteria. In terms of consensus etc in previous years such redirects were kept often per WP:CHEAP, see Wikipedia:Redirects for discussion/Log/2013 December 26#Burn (Scotland but in more recent years such as Wikipedia:Redirects for discussion/Log/2022 October 27#Redirects with disambiguators missing ")" the consensus has changed namely that such redirects are WP:COSTLY. I would put one condition here, that the redirect doesn't have any article content history currently at the title (as opposed to from a move) Wikipedia:Redirects for discussion/Log/2024 January 30#Montblanc(ffta) for example was an article so as a sub topic the history should probably be moved to Montblanc (ffta) (and the resulting redirect could then be deleted under R5) and Wikipedia:Redirects for discussion/Log/2024 January 29#Musa(name) which has significant history. When it comes to such redirects they should in some cases be moved to the correct title, in some cases should be restored and sent to AFD and in some cases are simply duplicates which means that if they only contain nonsense etc or don't contain any significant content not in the target they don't need to be kept and could have been deleted as A10 if they hadn't been redirected.
  • I also think we should cover "(Disambiguation)" redirects like London (Disambiguation) per Wikipedia:Redirects for discussion/Log/2022 August 24#"Title (Disambiguation)" redirects to disambiguation pages. I would also support incorrectly capitalized qualifiers like Morbius (Film), see Wikipedia:Redirects for discussion/Log/2022 September 13#Morbius (Film) but the consensus seems to be weaker. Crouch, Swale (talk) 22:17, 2 February 2024 (UTC)Reply
    Excluding redirects that have history as an article would seem best as there aren't so many of them that RfD would be overwhelmed and the best course of action is not always the same. As for "improperly" capitalised disambiguators, the consensus that these are bad is weak and (from my biased perspective) getting weaker so they definitely shouldn't be speedily deleted. Thryduulf (talk) 22:25, 2 February 2024 (UTC)Reply
    I'm surprised those capitalizations were deleted. I don't personally support that as alternative capitalizations are typically valid redirects. Hey man im josh (talk) 22:33, 2 February 2024 (UTC)Reply
    I don't think capitalization redirects with incorrect qualifiers are useful as users are very unlikely to use incorrect Wikipedia qualifiers, see WP:UNNATURAL and for internal searchers they would get to the correct place anyway. These redirects do inconvenience editors though.
    @Thryduulf: Would something like This criteria does not apply to any redirect that has non-redirect content (such as being a separate article or template etc) at the current title's history unless the page would qualify for speedy deletion (such as A10 or G1) if restored. If the page was redirected more than a month ago then the page can be moved to the correct title without redirect or the resulting redirect deleted immediately under this criteria. This would clarify that redirects like Montblanc(ffta) could not be deleted by this criteria but because it was redirected ages ago it could be moved to Montblanc (ffta) without redirect or the redirect speedily deleted. While I don't really agree with you that article content can't be deleted at RFD I don't think article content should be speedily deleted under R5. And cases like say Musa(name) that have history that can't easily be moved would still go to RFD but as you say there aren't many of these case so shouldn't be a problem. Crouch, Swale (talk) 20:06, 5 February 2024 (UTC)Reply
    I think I agree with the concept in your second paragraph, but the wording isn't the clearest (I had to read it multiple times to be clear about what you mean). I've not got time right now to improve it though. Your first paragraph is almost completely backwards - they do help and don't hinder - (UNNATURAL is a mix of correct, debatable and incorrect) but as this is something good faith editors disagree about it fails the uncontroversial requirement for speedy deletion. Thryduulf (talk) 22:22, 5 February 2024 (UTC)Reply
  • I am wondering if this would make more sense as X3. Recently created redirects which match the description of the proposed R5 fall under R3; once the "backlog" has been cleared this would seem redundant (NEWCSD#4). I think RfD can handle the occasional term(dab) that makes it past NPR without getting nominated for R3. HouseBlaster (talk · he/him) 08:14, 3 February 2024 (UTC)Reply
    I strongly support X3 and oppose weakly support R5. Once the backlog is cleared, it will be redundant (i.e. fail WP:NEWCSD4) to R3; RfD will be able to handle the occasional redirect that makes it through the R3 window. HouseBlaster (talk · he/him) 03:03, 23 February 2024 (UTC) EDITED 00:20, 6 March 2024 (UTC)Reply
  • Support per my previous discussion with Thryduulf. As I noted there, RfD has continued to be inundated with RDAB redirects, so I do think a CSD criterion is warranted. I would also support expanding the scope to cover the other types of errors mentioned at RDAB (I can live with capitalization differences being exempted, if others agree with Thryduulf that they are not uncontroversial), including (disambiguation, ((disambiguation), (disambiguation) (disambiguation), etc. InfiniteNexus (talk) 18:17, 3 February 2024 (UTC)Reply
    Missing closing parentheses were controversial last time they were discussed en mass so are not suitable for speedy deletion. I don't recall seeing any of the others at RfD recently. Ø (Disambiguation) (disambiguation) is the only page I can find "(disambiguation) (disambiguation)", and that's a {{R from merge}} so likely needs to be kept. As of the 21 November dump of page titles (the most recent I have downloaded) there were no instances of "((disambiguation" or "disambiguation))". Thryduulf (talk) 10:46, 4 February 2024 (UTC)Reply
    Wikipedia:Redirects for discussion/Log/2024 January 20#Andrew Sinclair (privy councellor and etc., Wikipedia:Redirects for discussion/Log/2024 January 20#Bonaparte's Retreat (Disambiguation), Wikipedia:Redirects for discussion/Log/2024 January 20#Islamic Resistance in Iraq (Disambiguation ), Wikipedia:Redirects for discussion/Log/2024 January 21#Terminal value (philosophy/, Wikipedia:Redirects for discussion/Log/2024 January 21#Chen Mingyi (Taiwan), etc. You can easily find more cases of RDAB via regex search, e.g. [1] [2] [3] [4] [5]. InfiniteNexus (talk) 17:53, 4 February 2024 (UTC)Reply
  • Oppose while I like the idea; I don't think this will reduce the load on RfD. Maybe what is needed is a proposed deletion process. I think we can expand WP:PROD to include redirects. Awesome Aasim 19:07, 3 February 2024 (UTC)Reply
    Please also see User_talk:176.33.241.125#Can you group all your misspaced parentheses RfDs into one nomination? where I give a kind request for all the similar redirects to be in one nomination to make discussion easier to follow. Awesome Aasim 19:08, 3 February 2024 (UTC)Reply
    From memory, a PROD for redirects has been rejected previously and I oppose it now. PROD only works for pages that are reasonably well watched, but very few redirects are watched other than by their creators (and not even always then) so PRODed redirects are unlikely to be seen. Thryduulf (talk) 10:38, 4 February 2024 (UTC)Reply
    Do you think extending the PROD duration and maybe having a bot update the list of PRODded redirects periodically would solve this problem? Awesome Aasim 17:53, 4 February 2024 (UTC)Reply
    Also I disagree that PROD won't work for pages not well watched; we have maintenance categories where people can review PRODs and reject them if they disagree. Awesome Aasim 18:00, 4 February 2024 (UTC)Reply
    PROD only works for pages that are reasonably well watched: it was my impression that PROD is used largely by new page patrol, so that wouldn't be the case. No? Largoplazo (talk) 20:45, 4 February 2024 (UTC)Reply
    I personally think PROD should be available to all types of pages but that's a different discussion. In any case these redirects shouldn't be left to clutter the search etc for 7 days. Crouch, Swale (talk) 20:06, 5 February 2024 (UTC)Reply
  • Support. These RfD end the same and are basically just a waste of editorial time and take time away from the other nominations. Gonnym (talk) 13:21, 4 February 2024 (UTC)Reply
  • @Utopes just sent another batch of redirects to RfD today, so pinging them here. Also pinging @Steel1943, who previously nominated several RDAB redirects, and notifying 176.33.241.125 on their talk page. InfiniteNexus (talk) 18:10, 4 February 2024 (UTC)Reply
    Thanks for the tip! I didn't even realize this was a discussion taking place when I sent those, will leave a comment now. 👍 Utopes (talk / cont) 20:31, 5 February 2024 (UTC)Reply
  • Neutral. I'm concerned drive-by admins will delete redirects that look like disambiguation issues when the title is actually valid (false positives). Examples: BSc(Hons) (currently nominated at RFD) and JANET(UK) (apparently, a valid alternative/former name for its target [see its edit history for my back-and-forth edits on this].) Yeah, given my level of participation in these redirects, one would think I would be supporting this ... but not so much since I'm concerned administrators may not get it right the first time when enforcing such a speedy deletion criterion, which has a potential to cause harm to the encyclopedia. Steel1943 (talk) 19:47, 4 February 2024 (UTC)Reply
    Create a temporary criterion "X3" until the numbers get low enough to where it can be reasonably appealed. Thinking about this, turns out I'm okay if this is the chosen path, given that I think "X" criteria tend to make admins do a double take and research the redirect's history prior to deleting the redirect. Seems like such a situation could appease all parties. Steel1943 (talk) 23:28, 9 February 2024 (UTC)Reply
  • I've stuffed the (full, unfiltered) results into subpages of User:Cryptic/Improper disambiguation redirects, and am going to spend a few hours classifying them - maybe all of them, but at least the first subpage which has the thousand most recent. Yes, even the relatively-easy-to-detect chemical ones. A problematic case with two examples has already jumped out at me (maybe the same sort as Steel1943's above, I haven't looked at them) - CPUSA(PW)/CPUSA(P) and PCd'I(ml). Would the advocates of this criterion speedy those? And if not, how are they excluded by this wording? —Cryptic 20:42, 4 February 2024 (UTC)Reply
    The first two should be excluded as they "will [be] correctly or plausibly be searched for without spaces" - determined by them being listed in bold in the target article without spaces. PCd'I(ml) does not appear to be correct - the article uses the acronym spaced and every unspaced google hit seems to relate to this redirect, so would be correctly speedily deleted. Thryduulf (talk) 22:08, 4 February 2024 (UTC)Reply
  • No confidence that some heathen who thinks there should be a space before the param list of function prototypes won't use this as an excuse to speedy int main(void). —Cryptic 21:38, 4 February 2024 (UTC)Reply
  • Support if I create the list, and improper disambiguation does not affect some titles like 501(c)(3) and chemical names like Cadmium(I). 176.33.241.125 (talk) 01:54, 5 February 2024 (UTC)Reply
  • Support: Such redirects are almost invariably getting deleted at RfD – I haven't found a single nomination in the last 30 days that closed as anything other than "delete", though BSc(Hons) seems headed to "keep". – This proposal will probably reduce the backlog and editor workload considerably. My only issues are the potential misuse/careless use of the criterion, hence why I would additionally support a listing of major exceptions (chemical names come to my mind but there are others). Dsuke1998AEOS (talk) 02:49, 5 February 2024 (UTC)Reply
  • Neutral, but would love to support a criteria that can be used to clean these. From what I've seen, while these titles might look the same, the backgrounds for all can be vastly different. As an example based on my personal experiences, I set out to find the total number of film redirects that were exactly: Foo(film). There were 172 of these, yet their histories were always varied. (I found it useful to display these titles in a Massviews chart). There are some pages that were recently created, and could qualify for R3 (although not usually). Sometimes, these were intentionally created with the lack-of-space, but most of the time these titles came about as left-behind from moves. Sometimes these were created at a bad title with extensive histories before being BLAR'd into the version that already exists, or may contain convoluted reversions between two titles that only differ in their spacing. In some of these cases though, G6 is likely to apply under the stipulation that they're "redirect(s) left over from moving a page that was obviously created at the wrong title." (which directly comes from Template:Db-error). The reason I'm neutral is because while I agree that these titles should be ridden of, I don't know if there is a clear-cut description would lead to deletion at this stage, more than what we already have described in G6 and R3. I agree something needs to be done, but investigating the histories seems to be an absolute requirement here, which cancels out a lot of these situations I'd think. Utopes (talk / cont) 20:47, 5 February 2024 (UTC)Reply
    As a question to this, would Shock(film) be eligible for CSD under this criteria, with its history? What about Rockers(film), which survived RfD? Brij Bhoomi(film) has 173 pageviews this month (due to its multiple incoming links), but would it also be CSD-able under this criteria despite it getting 17 views a day? At RfD I'd !vote to delete all of these for sure, but what I don't know is whether CSD makes the deletions too hasty, and whether there is value in investigating their histories and circumstances for existence. These are just the (film) redirects, and I don't know how complicated the other titles could be. Utopes (talk / cont) 20:56, 5 February 2024 (UTC)Reply
    @Utopes: "...there is value in investigating [the redirects'] histories and circumstances for existence..." There always is, which is one of the reasons I cannot sway my opinion one way or another to codify these redirects as eligible for CSD. Steel1943 (talk) 22:20, 5 February 2024 (UTC)Reply
    As more and more examples get brought up, I'm becoming less and less certain that speedy deletion beyond R3 and G6 is possible in a way that is not too narrow to be useful and not too broad so as to catch things that shouldn't be deleted. I need to think more. Thryduulf (talk) 22:25, 5 February 2024 (UTC)Reply
    (edit conflict)I agree with that, yes. This is my concern as well. When looking through these titles, the backgrounds can be vastly different. When putting the Foo(film) RfD together, I was skipping over pages in history, because those would need to be checked on a case-by-case basis, presumably. It was unclear to me whether this new CSD criteria puts weight into histories, and if so, by how much? If we take away the pages with history, we're left with a decently smaller number of applicable pages, and the question becomes whether a whole criterion is necessary for the [X] number of cases that are safe to outright delete. I don't know how much that number is. Utopes (talk / cont) 22:32, 5 February 2024 (UTC)Reply
    I guess my follow-up would be to find a comparison. How are histories dealt with other R CSD criteria? I feel like I've seen situations where a page (and its history) are replaced with a redirect (I think it was to Draftspace, but I can't recall), which was then tagged as R2'd by someone who followed up with the page. How "valuable" is the page history there? I'd presume it's checked every time, so doing it here might not be that unconventional. The question becomes what constitutes a "valuable history" that makes CSD a safe action for redirects that meet R5. Utopes (talk / cont) 22:44, 5 February 2024 (UTC)Reply
    It should be checked every time, as with all other speedy criteria. I have no confidence that it is. —Cryptic 02:59, 6 February 2024 (UTC)Reply
  • So, I've finished sorting the most recent 2000 and least-recent 1100ish page titles containing an open-paren not preceded by a space at User:Cryptic/Improper disambiguation redirects (I was never going to get through all of them, and had only been fooled into thinking I could because SDZeroBot initially only gave me about a third of the results). The conclusions I'm drawing from that are:
    • We should make it explicit that this only applies to disambiguators per se, not parenthesized text that's part of the redirect subject's proper name, even if it's misspaced or misspelled. (This sounds obvious to me when it's put like that, but nobody's brought it up as the general case, even though more specific subcases like chemicals and section names have been.) So It's On(Dr.Dre)187um Killa and INS Talwar(F40) and Cheeses...(of Nazereth) wouldn't be speedyable, but restatements of the proper name or redundant parenthesized names like in King Edward Medical university(KEMU) and SsangYong Rodius(Stavic) could be. "Plausibly be searched for without spaces" is too vague, fails NEWCSD#1, and will be abused.
    • Section names like 501(c)(3) aren't common. Chemical names and processes are very, very common, and I didn't notice any incorrectly-formed disambiguators in chemistry-related redirects. If we're mentioning broad classes of counterexamples, that should be the first. I further think we should specifically exclude the entire subject area even if the disambiguator of a chemistry-related redirect is ill-formed and it would otherwise qualify.
    • These aren't frequent. There are a lot of extant cases, but we only see a handful of new ones a month. This seems to be a recurring theme at RFD - someone finds some broad new class of malformed redirects that have been accumulating since 2001, starts nominating them at RFD - sometimes properly in batches, sometimes individually! - and then it finds its way here, even though new ones aren't being rapidly created, and those that are fall under existing criteria.
    I've commented multiple times above, so I'll bold a position here: I oppose this as a permanent criterion, for being infrequent, redundant to R3, and error-prone; I'm neutral on a temporary X- series criterion until the old ones are dealt with. —Cryptic 03:26, 6 February 2024 (UTC)Reply
    We can't delete anything under R3 unless it was created recently. It would make more sense to expand the scope of WP:G14, which already includes (disambiguation) redirects. InfiniteNexus (talk) 05:41, 7 February 2024 (UTC)Reply
    Well, yes, R3 is recent only. Quite obviously. As I mentioned above. But there's a finite, relatively small, number of non-recent ones: roughly 5000, based on the sample I analyzed, and that's assuming a vanishingly-small number of redirects with non-redirect history (which I didn't check for). As soon as they're gone - and that'll happen quickly, the admins vying for topspot at the awful WP:ADMINSTATS scoreboard query for speedy candidates like these and feed them into Twinkle - it'll be entirely redundant. —Cryptic 03:02, 8 February 2024 (UTC)Reply
    admins vying for topspot at the awful WP:ADMINSTATS scoreboard - surely not: the top admin there is behind the second-top admin by 400,000 deletions and so 5000 entries would be trivial. * Pppery * it has begun... 03:09, 8 February 2024 (UTC)Reply
    I hadn't realized about these all time lists. It's just as I've always suspected, there's just no keeping up with Explicit. Hey man im josh (talk) 04:05, 8 February 2024 (UTC)Reply
  • Support as a useful tool. Even if the current situation looks temporary, forcing repeated discussions isn't a good use of anyone's time. Also, there's no way of knowing it won't flare up again at some point, since redirects aren't necessarily closely watched and these sorts of mistakes can steadily build up unnoticed; hell, this discussion is going on now because it already happened once. I don't buy the arguments that admins should be assumed to be total rubes, it doesn't actually take a PhD to recognize scientific nomenclatures and other idiosyncratic spellings aren't the same as Wikipedia disambiguators. If there's that much concern, just create a Category:Redirects with unspaced parentheticals or something similar; don't force people to murder untold numbers of characters and minutes of their lives they're not getting back. The Blade of the Northern Lights (話して下さい) 17:23, 8 February 2024 (UTC)Reply
  • @Thryduulf:, what I think could be helpful would be if we can identify which / how many of these qualify for G6 or R3 already, and use those existing criteria where appropriate. Once all of the G6/R3 candidates are addressed, maybe we can take a look at what remains, and the commonalities between them? If I had to guess, maybe 50% of these were unambiguously created in error and currently actionable?{{cn}} which might allow us to compartmentalize this block bit by bit. Utopes (talk / cont) 20:27, 9 February 2024 (UTC)Reply
  • Strong Oppose these redirects are entirely harmless. We may as well have them since they likely bring a small net benefit to the encyclopedia. The do no damage. Readers don't know our guidelines on how to format the disambiguator, and readers are our priority, not top-down decisions based on overly-finicky guidelines.🌺 Cremastra (talk) 13:22, 14 February 2024 (UTC)Reply
  • Would they qualify under WP:G6? — Qwerfjkltalk 21:17, 14 February 2024 (UTC)Reply
    The very fact that this is controversial indicates it isn't a G6. * Pppery * it has begun... 21:25, 14 February 2024 (UTC)Reply
    The ones that were very obviously created by or when fixing a mistake (most commonly this is evidenced by being moved to and from this title by the same person in quick succession) do qualify as G6, but this only applies to some of the redirects that would fall under this criterion (either because they were created deliberately or because it isn't obvious whether creation was intentional or not). Thryduulf (talk) 21:55, 14 February 2024 (UTC)Reply
  • Support. Agree with editor Cremastra that these are harmless and possibly a bit helpful as {{R from typo}}s; however, the issue is that they are being deleted anyway and clogging RfD, which begs for a solution. And this solution does the trick as long as care is taken not to delete needed redirects that just look like the bad guys. P.I. Ellsworth , ed. put'er there 22:43, 14 February 2024 (UTC)Reply
  • Comment: I'm worried that, as worded, the proposed criterion doesn't take into account page history that (a) may be required to be kept for attribution in the case of redirects from merges (which might lead to accidental breaches of licensing requirements), or (b) is otherwise useful; both of which are listed in the redirect guideline's reasons for keeping redirects. I'm also worried that it doesn't take into account the age of these redirects - some may have existed for a significant length of time and/or may be redirects with old history, which are listed in the guideline as redirects that should not normally be deleted without good reason & that should be left alone. I also share Cremastra's view about these redirects being harmless - in RfD discussions I've seen where such redirects have been nominated, I sometimes see WP:RDAB being cited; however, that shortcut links to an essay that doesn't explain why such redirects are costly enough as to warrant deletion (as opposed to being cheap). With the greatest respect to Paine Ellsworth,/gen I'm very hesitant to think we should be creating a new CSD criterion for redirects that may be being deleted at RfD when (arguably) they should be being kept, especially when they are possibly...helpful (which is another reason in the guideline for keeping them). Only a comment for now while things are still mulling around in my head, but I think I'll add a bolded !vote at some point relatively soon. All the best, ‍—‍a smart kitten[meow] 01:59, 16 February 2024 (UTC)Reply
    Strong oppose per my comments above. I am heavily unconvinced that these redirects are costly enough to warrant deletion in the first place. To take a few recent RfD examples ([6] [7], [8] [9] [10] [11] [12] [13]), often in such discussions the only reason given for deleting them is per WP:RDAB - but, as I mentioned above, that essay section doesn't explain why these redirects are at all costly and/or problematic (and so, arguably, isn't a valid rationale for deletion - especially when considering that redirects are cheap is one of the guiding principles of RfD). I'm concerned that a local consensus may have formed at RfD to delete these redirects, and I wouldn't want to create a speedy deletion criterion that further embeds this. All the best, ‍—‍a smart kitten[meow] 18:09, 18 February 2024 (UTC)Reply
  • Comment Considering many RfD participants don't watch this page or subscribe to FRS, is it reasonable to advertise this RfC via an editnotice at RfD? InfiniteNexus (talk) 16:07, 16 February 2024 (UTC)Reply
  • Create a temporary criterion per Steel and Cryptic. These redirects are a countable list and will go away in some time. Hence I would not prefer a "R5" as this becomes redundant once the backlog is gone. Also, we need the updated wordings incorporating Crouch Swale's suggestions about page history, which was also A Smart Kitten's concern. Jay 💬 06:32, 17 February 2024 (UTC)Reply
    The problem with making it temporary is that this backlog already built up once, so removing it once this current issue is resolved allows it to build up again. The other two temporary criteria were to deal with issues that definitively weren't going to recur, which is not the case with this; people will still inevitably create these bad redirects. Why take away a useful tool? The Blade of the Northern Lights (話して下さい) 15:47, 20 February 2024 (UTC)Reply
    My understanding behind the suggestions for a temporary criterion is that once the backlog is cleared, the combination of a report, R3 and G6 would mean there aren't enough redirects to meet NEWCSD criterion 3 (frequent). Of course there is nothing stopping us enacting a temporary criterion and then making it permanent later if the issue remains ongoing. Thryduulf (talk) 20:04, 20 February 2024 (UTC)Reply
    If there's a choice, I'd definitely take a temporary criterion over nothing at all. The Blade of the Northern Lights (話して下さい) 03:48, 25 February 2024 (UTC)Reply
  • Support with caveat that it excludes redirects with a substantial non-redirect history. That situation is rare enough to be worth discussing; and there could easily be situations where eg. an article was turned into a redirect that fits this description, which nobody noticed, and is then listed under this CSD - it wouldn't even have to have been done maliciously (although ofc it could be.) And if there is a history, whether due to a merge or whatever, this CSD would usually be the wrong approach anyway - in that case you'd want to move the redirect to preserve history and attribution, rather than create a new one that lacks them. --Aquillion (talk) 19:16, 20 February 2024 (UTC)Reply
  • Oppose per WP:CHEAP. -- Tavix (talk) 03:06, 23 February 2024 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Discussion (Improper disambiguation redirects) edit

Skimming over some of the discussion at VPPOL regarding the recent G5 RFC, it appears there is a view that RFCs to establish a new speedy deletion criterion should be advertised on T:CENT; which I am personally amenable to. Looking in WP:CENT/A, I can't see that it's already been notified there. What are others' views on the idea of adding this to CENT? I would be in favour of it, but I wanted to hear from other editors first. All the best, ‍—‍a smart kitten[meow] 03:57, 5 March 2024 (UTC)Reply

While I have no objection to doing so, I don't think it's worth it as there isn't a clear consensus here and I don't think more input is going to significantly change that. More workshopping leading to a second proposal that was advertised on CENT would be a better use of time I think. Thryduulf (talk) 12:10, 5 March 2024 (UTC)Reply
That's a fair point. ‍—‍a smart kitten[meow] 23:55, 5 March 2024 (UTC)Reply
After skimming through the discussion prior to closing, I got here. At this point, I can close this per WP:PGCHANGE since it wasn't properly advertised, or this RfC can be relisted and then advertised at T:CENT, VPPOL, and other appropriate places. I personally prefer the latter, since I see a consensus forming around creating X3 that excludes redirects with a substantive page history or redirects from merges. voorts (talk/contributions) 03:54, 6 March 2024 (UTC)Reply
Personally, I'd prefer a new proposal with a specific proposed wording to be the one advertised to make it clear what people are supporting/opposing. Thryduulf (talk) 04:26, 6 March 2024 (UTC)Reply
Does this work for people?

X3: Redirects with no space before a parenthetical disambiguation, e.g. "Foo(bar)", "Joe Smith(disambiguation)". This does not apply to terms that will correctly or plausibly be searched for without spaces, nor does it apply if the redirect contains substantive page history (e.g. from a merge). Before nominating a redirect under this criterion:

  • Create the correctly spaced version as a redirect to the same target if it would make a good redirect but does not exist
  • Adjust any incoming internal links to point to the correctly spaced version.
HouseBlaster (talk · he/him) 17:49, 6 March 2024 (UTC)Reply
Yes I think that makes sense per my above comments. Crouch, Swale (talk) 18:05, 6 March 2024 (UTC)Reply
There is a typo ("not does it apply" should be "nor does it apply"), and I wouldn't object to giving an example of "correctly or plausibly" but other than those two minor points this looks good to me. Thryduulf (talk) 18:34, 6 March 2024 (UTC)Reply

I have silently corrected the typo. As for examples, I did not include any because I honestly could not think of any (which certainly does not mean they don't exist, but does very much mean I am open to suggestions). In e.g. 501(c)(3), "(3)" is not a parenthetical disambiguation. Likewise for things like Dysprosium(III) nitride: the "(III)" is not a disambiguator.

If there are no other points, I will look to launch an RfC with a CENT listing ~tomorrow. HouseBlaster (talk · he/him) 18:47, 6 March 2024 (UTC)Reply

RfC: enacting X3 edit

Should X3 (redirects with no space before a parenthetical disambiguation) be enacted as a temporary CSD? 17:34, 7 March 2024 (UTC)

Proposed text:

X3: Redirects with no space before a parenthetical disambiguation, e.g. "Foo(bar)", "Joe Smith(disambiguation)". This does not apply to terms that will correctly or plausibly be searched for without spaces, nor does it apply if the redirect contains substantive page history (e.g. from a merge). Before nominating a redirect under this criterion:

  • Create the correctly spaced version as a redirect to the same target if it would make a good redirect but does not exist
  • Adjust any incoming internal links to point to the correctly spaced version
  • Support as proposer. These are all redirects which are errors in the act of disambiguation, and thus has no natural affinity with the article in question. I will also add that in the above discussion people have explained why this is A Good Thing; I will let them explain their own reasoning rather than attempt to filter it through my voice. I will note that this is supposed to be a temporary criterion per WP:NEWCSD criterion 4, as once the "backlog" has been cleared it will be redundant to WP:R3. (For transparency, this comment includes a hidden ping to everyone who commented above. I have opted for a hidden ping to avoid the distraction of a bunch of usernames.) HouseBlaster (talk · he/him) 17:34, 7 March 2024 (UTC)Reply
  • Support per HouseBlaster and my comments in the preceding section (tldr; when nominated at RfD these redirects are inevitably deleted). Although it is very likely that once the backlog is cleared the combination of R3 and G6 will make the need for this redundant we can discuss making it permanent if that turns out not to be the case. Thryduulf (talk) 17:57, 7 March 2024 (UTC)Reply
  • Support it may be better to make it permanent because some redirects will likely later get missed and then becoming too old for R3 but its better than nothing. Crouch, Swale (talk) 18:16, 7 March 2024 (UTC)Reply
  • Strong oppose, per my comments in the previous RfC. Although this proposed criterion takes into account page history, it doesn't factor in redirects' ages - which may lead to redirects that have existed for some time (including potentially redirects with old history) being deleted; despite the Redirect guideline stating that these should be left alone. Furthermore, and most importantly, the essay cited as the deletion rationale (WP:RDAB, part of WP:COSTLY) doesn't explain why these redirects are harmful enough to warrant deletion at all - simply stating that, in the opinion of the essayist, there is no need to redirect from them. As far as I can see, these redirects are entirely harmless. As I said in the previous discussion:

    I am heavily unconvinced that these redirects are costly enough to warrant deletion in the first place. To take a few recent RfD examples ([14] [15], [16] [17] [18] [19] [20] [21]), often in such discussions the only reason given for deleting them is per WP:RDAB - but, as I mentioned above, that essay section doesn't explain why these redirects are at all costly and/or problematic (and so, arguably, isn't a valid rationale for deletion - especially when considering that redirects are cheap is one of the guiding principles of RfD). I'm concerned that a local consensus may have formed at RfD to delete these redirects, and I wouldn't want to create a speedy deletion criterion that further embeds this.

    All the best, ‍—‍a smart kitten[meow] 18:18, 7 March 2024 (UTC)Reply
    Redirects with significant history, including old history, are excluded from this criterion. That doesn't invalidate the rest of your comment though. Thryduulf (talk) 18:36, 7 March 2024 (UTC)Reply
    For clarity, when I used the phrase redirects with old history, I was referring to redirects with entries in the page history from previous versions of Wikipedia - i.e., those that {{R with old history}} would be applied to. I read the phrase substantive page history in the proposed criterion as referring to an article (instead of just a redirect) being present in the history - therefore, my understanding was that redirects with old history are not necessarily excluded from this criterion. All the best, ‍—‍a smart kitten[meow] 18:50, 7 March 2024 (UTC)Reply
    I meant substantive page history to mean something like page history with something more than adding/removing rcats/fixing double redirects/etc. HouseBlaster (talk · he/him) 19:25, 7 March 2024 (UTC)Reply
    Why not just add this to the "e.g." parenthetical above? I think that would avoid further confusion. voorts (talk/contributions) 01:36, 8 March 2024 (UTC)Reply
  • Notified Wikipedia talk:Redirect & Wikipedia talk:WikiProject Redirect of this discussion. ‍—‍a smart kitten[meow] 18:18, 7 March 2024 (UTC)Reply
  • Neutral If there seriously is a problem with these kinds of redirects then sure, go ahead. But I am failing to see how these can just all be nominated in one big RfD with consensus to delete. Are there too many of them? I know the IP that was doing the nomination of them failed to group the redirects appropriately together in a single nomination. Awesome Aasim 18:20, 7 March 2024 (UTC)Reply
    Grouping up nominations more often then not leads to a failed nomination as editors just can't handle a large amount. Gonnym (talk) 16:15, 8 March 2024 (UTC)Reply
  • Oppose per WP:CHEAP. I fail to see what harm these redirects are causing and would recommend instead to just leave them alone. -- Tavix (talk) 18:28, 7 March 2024 (UTC)Reply
  • Neutral What is the problem that needs to be solved? The Banner talk 18:35, 7 March 2024 (UTC)Reply
  • Support, this is a convention that affects a quite-literally-"random" selection of pages that happened to have issues. While it is good to create redirects for reasonable typos based on different way that search terms can be spelled, errors in the act of disambiguation are not useful or plausible typos to keep. Out of the millions of pages that have parenthesis in their titles, there is not a single time when I, nor you, nor anyone would expect that the Foo(bar) version exists for the same title. Basically, if you were to purposely leave off this space when searching for a title, there is a 0.1% chance that the redirect would exist (as it's a group of thousands among a pool of millions). It's totally unreliable, will never be intentionally typed, and all-in-all exist as clutter among incoming links with the potential to drown out and dilute the actually likely typos. To quote WP:COSTLY, redirects also need looking after. While they may not take up a lot of bandwidth on their own, these faulty titles have been a WP:PANDORA's box cracked wide open, which has led to a surplus of unexpected corners where edits can go undetected. Out of the thousands of affected redirects, I'll estimate that 10%(?) have substantial history, as duplicate pages left unincorporated for anywhere up to a decade and beyond in some cases. That's still hundreds of titles with histories! Of course these such cases wouldn't apply under this new CSD criterion, but by removing the titles that have no reason to exist, a higher focus can be placed on the titles that ARE distinguished by their complicated histories, most of which haven't seen the light of day from their peculiar, isolated locations.
All in all, an uncontrolled surplus of these titles makes it difficult to monitor new content, harder for editors to track changes and split histories, adds unnecessary and unlikely filler to redirect lists, maintains a faulty narrative that it's okay to move a title to "Foo(bar)" if "Foo (bar)" is salted for whatever reason, or that it's okay to have these unlikely parenthetical errors in titles (which always get ejected to new titles per the MOS anyway), and just all-in-all makes navigation less consistent to randomly account for an implausible typo redirect that exists 0.1% of the time. Utopes (talk / cont) 20:02, 7 March 2024 (UTC)Reply
Based on my comment below, I am moving to oppose the current version. I would hypothetically support a permanent R5 that does not include the bullet points, which puts the onus unnecessarily on new page patrollers to continuously be jumping through hoops to follow these. As it stands there is a very high reliance on the idea that "once these are deleted then we will start catching everything with R3/G6/RfD" which is exactly what is going on right now, with very little success. This is plucking the flower without detaching the root of the issue. Utopes (talk / cont) 02:40, 11 March 2024 (UTC)Reply
  • Support since I suggested it above. Steel1943 (talk) 20:21, 7 March 2024 (UTC)Reply
    Blarg, my own comment further down in the discussion concerns me. Steel1943 (talk) 22:45, 7 March 2024 (UTC)Reply
  • Strongly oppose per Tavix and my comments above. 🌺 Cremastra (talk) 20:44, 7 March 2024 (UTC)Reply
  • Support per Hey man im josh below. Preferably without the two bullet points, and preferably permanently. In regards to deleting the two bullet points, CSDs should be simple. We should not be putting the burden of checking other pages, editing other pages, etc in order to place a CSD on patrollers and administrators. I'd prefer to keep CSDs simple, without a bunch of little gotchas and caveats. The complexity of NPP workflows is a big problem, slowing down review times and leading to NPP burnout. –Novem Linguae (talk) 21:46, 7 March 2024 (UTC)Reply
    "...We should not be putting the burden of checking other pages, editing other pages, etc in order to place a CSD on patrollers and administrators." For what it's worth, such actions have to be taken in some cases, such as for WP:R4 and most of WP:G8, and for good reasons; thus, that quoted claim cannot be applied across the board. Steel1943 (talk) 22:17, 7 March 2024 (UTC)Reply
    G14, A2 and A10 all require checking the existence and/or content of other pages too. G12 requires checking for external sources. Thryduulf (talk) 23:33, 7 March 2024 (UTC)Reply
    It seems that this RFC's wording says that the CSD is temporary, but lists no expiration date. Is this really a temporary X criteria if this CSD has no expiration date? Perhaps it would make more sense to have this as a permanent R criteria, then use an RFC to repeal it later. –Novem Linguae (talk) 02:12, 11 March 2024 (UTC)Reply
    Changing to Oppose. This proposed criteria is too complicated because of the two bullets. I do not like the idea of a CSD where patrollers and admins are required to do a bunch of cleanup steps before placing or executing the CSD. The two bullet points put a lot of burden on the patroller and deleting admin. Are these bullets required when filing RFDs or closing RFDs? This is more cleanup burden than the status quo, if I'm understanding things correctly. –Novem Linguae (talk) 02:17, 11 March 2024 (UTC)Reply
    Replying to both your comments in order: neither X1 nor X2 had built-in expiration dates; they were just repealed when the cleanup was done. And this is complicated because it is temporary: there are people (e.g. me) who are volunteering to complete the steps required by the two bullet points to clean up the backlog of incorrectly spaced disambiguations. Put differently, this is not meant for e.g. NPPers (though they are welcome to use it), instead it is meant for people who volunteer to help with this backlog. If you (generic you) wish to use RFD, nobody will stop you; this is a shortcut for the people who feel like it is a shortcut. But a discussion takes volunteer time; I think it is easier to check Special:WhatLinksHere and potentially create a redirect (both of which could be linked from the CSD template for ease of use) than have a weeklong discussion. HouseBlaster (talk · he/him) 17:59, 13 March 2024 (UTC)Reply
  • Comment Support (summoned by bot). I’m supportive in principle, but the discussion above highlighted some instructive examples, such as the chemistry false positives, and the film examples where each case seemed to warrant individual investigation, so I’m a little hesitant on whether this change might reduce due diligence that would have caught false positives. Then again, if that happens, just recreate them? Barnards.tar.gz (talk) 22:31, 7 March 2024 (UTC)Reply
    The Chemistry examples would not be in scope because the text in the parentheses is not a disambiguator, similarly anything that is correctly rendered without a space cannot be deleted by this. The concern with the film redirects was almost entirely that some have substantial history, such redirects are explicitly excluded from this this criterion. Thryduulf (talk) 23:37, 7 March 2024 (UTC)Reply
    Fair enough, I have upgraded my comment to a Support. Barnards.tar.gz (talk) 20:04, 8 March 2024 (UTC)Reply
Comment/Question (probably primarily to those "support"-ing this proposal): Does anybody recall why the texts at WP:UNNATURAL and WP:RDAB were written? I've ... unfortunately slept since they were added to Wikipedia:Redirects are costly, and the comments above by The Banner and Barnards.tar.gz seem to validate that without quick-to-find context, this proposal may be a bit confusing to understand regarding what problem it is trying to solve, especially for those who do not visit WP:RFD regularly. If anyone recalls the reasons and/or precedents, it may need to be added to Wikipedia:Redirects are costly or even Wikipedia:Redirects for discussion/Common outcomes since I just realized that ... I don't see this as an example at Wikipedia:Redirects for discussion/Common outcomes, and I would have expected to have found it there. Steel1943 (talk) 22:39, 7 March 2024 (UTC)Reply
  • Support the exceptions have been well thought out, the risk of unintended consequences seems low. – Teratix 05:06, 8 March 2024 (UTC)Reply
  • Support per Utopes. While these redirects are cheap, the effort wasted on individually judging their deletion is not. Without this proposal, it is apparent that editors unfamiliar with this discussion will continue to flood RfD with uncontroversial deletion requests. BluePenguin18 🐧 ( 💬 ) 05:22, 8 March 2024 (UTC)Reply
  • Support per my comments in the previous discussion – individual nominations have invariably resulted in a clear consensus to delete. I trust that the reviewing admins would catch most false positives. Perhaps this could then be incorporated into R3 after the current round of cleanup is complete, if a standalone criterion would be redundant. Complex/Rational 15:27, 8 March 2024 (UTC)Reply
    The only reason these aren't included in R3 at the moment is the recency requirement of that criterion (which is there for good reason). Thryduulf (talk) 15:39, 8 March 2024 (UTC)Reply
  • Support: The outcome of these types of redirects being sent to RfD is extremely predictable and it would save everybody involved some time. Hey man im josh (talk) 15:42, 8 March 2024 (UTC)Reply
  • Weak support (Invited by the bot) "Weak" because I have less expertise on this than the other respondents above. Everything has a cost (including retained redirects) and IMO folks who calculate that based on what the hard drive cost are mistaken. Also, if these are already all getting uncontroversially deleted, then IMO that refutes the argument that some need to be kept. North8000 (talk) 19:17, 8 March 2024 (UTC)Reply
  • Support. As in the above closed discussion, my support for this action is resumed. P.I. Ellsworth , ed. put'er there 20:11, 8 March 2024 (UTC)Reply
  • Support well thought-through proposal and supported by an apparent consensus across multiple RfDs on the topic. I don't see a large benefit to delaying the cleanup by requiring all of these go through RfD; if it's obvious just let sysops delete it and avoid the busywork and bureaucracy, that's the whole point of CSDs. Wug·a·po·des 20:57, 8 March 2024 (UTC)Reply
  • Support per my previous comment. My support is primarily because of the RfD nominations, which almost always result in deletion and are an unnecessary waste of time, but secondarily because of the unnatural aspect of the typos (as Utopes said above). Personally, I would be even more restrictive: for example, I'm never going to speedy a redirect that has had hundreds (or, heck, even just tens) of pageviews in the last month, but I understand that pageviews are rarely a consideration for redirects nominated at RfD, and this proposal is obviously better than nothing. Dsuke1998AEOS (talk) 02:41, 9 March 2024 (UTC)Reply
  • I'd really be happier if this spelled out "non-redirect history" rather than the vague "substantial". (The only other thing it could mean - pages tagged {{R with old history}} - isn't a concern; no page with a matching title is tagged with the template, and the oldest, Road Warriors (Atlantic League)(version 2), postdates modern MediaWiki and has an article in the history besides.) —Cryptic 03:03, 9 March 2024 (UTC)Reply
  • Support from a maintenance perspective. Redirects need maintenance to ensure they're categorized appropriately, link to Wikidata items, etc. With the sheer amount of redirects on enwiki, it's not going to make a huge difference, but it's nice to do housekeeping. SWinxy (talk) 18:59, 9 March 2024 (UTC)Reply
  • Support per my previous comments. RfD has been constantly overwhelmed in recent days. InfiniteNexus (talk)
  • Support: uncontroversial maintenance work supported by previous consensus. — Bilorv (talk) 16:39, 10 March 2024 (UTC)Reply
  • Comment. Now that I've thought about what this would entail, I do want to add: while I support the addition of a CSD to cover these, there is nothing about the group of affected pages that signals it into the X category. Under the pretense that a CSD will be created for this, I oppose X3 and support R5. There are other supporters above who also prefer something permanent, which is my lean as well, and there has not been a spot to cover how this would be categorized. R5 was the original suggestion, but was changed to X3 by HouseBlaster when starting this RfC. As a refresher on the precedent for X criterion, which has only been enacted once ever (X1/X2 occurred simultaneously), both of these affected a limited number of titles which was impossible to grow in scope, due to the finite bounds, and will 100% never be a problem again when the target set of titles gets dealt with. This was due to the clearly defined and permanent bounds of the X1 and X2 sets.
X1 was created to deal with redirects meeting one criteria: "created by Neelix". After Neelix's ban, that group of 50,000 eventually would basically disappear, and cannot possibly grow in size due to the finite nature of a single banned user's page creations. X2 was a bit more nuanced, but was created to deal with faulty pages created by the content translator tool, specifically before the configuration error described at WP:CXT was fixed in 27 July 2016. This set too, would disappear in number, in part due to the full draftification of remaining pages.
The list of redirects applicable under X3: "Redirects with no space before a parenthetical disambiguation", is totally unlike X1 and X2, in the sense that Foo(bar) can be created by anyone, at any time, for all time. Based on the hundreds of recent RfDs, there is consensus that these titles can go. There's thousands of these pages at the moment, and this mistake was equally as common 12 years ago just as it was common 2 years ago. It's because of this that the temporary aspect I don't think holds up; there needs to be a long term solution that doesn't involve hawking NPP eternally for R3 candidates. In the opening, HouseBlaster states that: "this is supposed to be a temporary criterion per WP:NEWCSD criterion 4, as once the "backlog" has been cleared it will be redundant to WP:R3." This is only the case if every single Foo(bar) title is caught within a month of creation forever, i.e. within the window where R3 applies. While many of these titles are quite old, this quarry shows many (but not all) of the 100+ Foo(bar) redirects created within the last two years, the key takeaway being that "they exist" and haven't been RfD'd or R3'd yet. If we delete all the Foo(bar) titles and end up with another 100+ of these two years from now, now we're back where we started with the overflow. From my point of view, this should be a permanent CSD until the consensus is that this shouldn't be a permanent CSD any longer. These titles will always pop up and calling this X3 implies that there will never be a surplus of these ever again, which cannot be known. Utopes (talk / cont) 22:29, 10 March 2024 (UTC)Reply
If these get created at such a rate that those which are not caught by the combination of R3 and G6 gets to a point that RfD gets overwhelmed again or it looks like it wouldn't if X3 didn't exist we can easily convert it to R5 at that time because we will have evidence that it is needed permanently. We don't have that evidence now. Although I suspect it wasn't your intent, the wording of your comment implies that the change from R5 to X3 was a unilateral decision by HouseBlaster, but it was a decision taken based on comments in the first discussion and discussion of the way forward following it. Thryduulf (talk) 00:42, 11 March 2024 (UTC)Reply
Apologies, it looks like I didn't see the other parts of the discussion where the temporary aspect was being talked about. HouseBlaster was the person saying X3 in the first RfC, whereas the other mentions were of whether or not to make a "temporary criteria" without necessarily saying "X3". It was then proposed as X3 a day before the new RfC began, with the sign-off being mainly for the proposed text and in my eyes wasn't necessarily about the X3 vs R5 decision.
Something that has been brought up previously is that this is redundant to R3 and G6, when this is not the case. (Side note: The last R3 deletion was 4 days ago, on Solar eclipse of 2024-04-28, not super important though, just a fun thing). R3 is its own entity entirely and is completely time-sensitive for recent redirect creations. This is impossible to be a failsafe alone. Redirects will be missed, or mistakenly patrolled, and based on the sheer number of recently-created Foo(bar) pages from the last year or so that still exist untouched, they definitely escape eyes. The criteria that has more pertinence is G6, which is reserved for errors, and most of these are errors! The (unanswered) question I asked in the first RfC was whether we should go through and delete the errors right now, and see how many intentional creations remain. Who knows! Maybe we won't need to make a temporary CSD in the first place if the CSD is just going to go away once we temporarily clear the backlog. Contrarily to what you say, this is fundamentally an ongoing issue if we have Burek(song), Poison ivy(plant), and KP Oli Cup(cricket) all created days ago in Feb/March 2024, and all marked as new-page-patrolled too, preventing anyone from possibly spotting these in time to R3. These aren't even necessarily G6-able either, and if we start picking up several a month to RfD (despite overwhelming consensus being to always delete regardless of time spent at title), this backlog will never be fully cleared. Because of the continuous nature that these redirects get created, this should be R5, in my eyes. There's no evidence to suggest this is temporary, as we have pages that meet this criteria from 2002 through 2024. Starting at X3 and moving to R5 is unprecedented to occupy a temporary X CSD first, and there is a need to get it right the first time to avoid occupying more CSD names than we have to. If there are titles here that are G6-able as unambiguous errors, I say let them be G6ed if they can. If it's a permanent thing, let it be permanent! I'm in support of the speedy deletion of all of these pages, but I think the idea that the Foo(bar) group is a temporary and countable problem is just not the case. Utopes (talk / cont) 02:20, 11 March 2024 (UTC)Reply
Everything is unprecedented until it's needed for the first time, that's not a reason to support or oppose anything. Everybody supporting a temporary criterion was supporting the creation of a criterion numbered X3 even if they didn't use that explicitly (temporary criteria are numbered in the X series, the next one available is 3) in the same way that everyone supporting a new permanent criterion for redirects only is supporting a criterion numbered R5 and everyone supporting a new permanent criterion for articles is supporting a criterion numbered A12, regardless of whether they use those names or not.
Some of the titles are G6-able, some aren't, but the point is that once the backlog has been cleared the combination of R3 and G6 means that the few not eligible under either criterion will not overload RfD to the point a new criterion is needed, as best we can predict based on the data we have now. If that changes then there is no harm at all (number exhaustion is not a thing) in changing X3 to R5. Thryduulf (talk) 16:47, 11 March 2024 (UTC)Reply
That's a very useful query but let's not limit ourselves strictly to its output. Other redirects should also go, such as "Joe Smith(disambiguation)" mentioned in the proposal (excluded because of the space) and 10,000 Summers(No Devotion song), which also has a space in the qualifier. (The database Quarry uses represents spaces as underscores.) Certes (talk) 21:43, 13 March 2024 (UTC)Reply
  • Oppose X3, although I could support a CSD for one-character typo disambiguation redirects. Temporary criteria are there to help fix issues created by specific users or specific software tools; this one has no business being temporary. —Kusma (talk) 07:02, 11 March 2024 (UTC)Reply
    @Kusma: The point is such typos are already covered by R3 if recently created. Once a cleanup is done under X3, the ability to speedily delete longstanding typo redirects is no longer needed. -- King of ♥ 16:26, 11 March 2024 (UTC)Reply
    Why would plausible typos like omission of a single space be covered by R3? These are being generated quite frequently, which shows they are not freak occurrences, but plausible typos. I can't see R3 being applicable. —Kusma (talk) 16:38, 11 March 2024 (UTC)Reply
  • R5 as first choice, X3 as second per my reasoning earlier in this discussion and Utopes above. The Blade of the Northern Lights (話して下さい) 17:42, 11 March 2024 (UTC)Reply
  • Support X3 first choice, R5 second choice - This is most cleanly X3. However, we should dump the quarry query onto a page somewhere, and state that X3 applies only to these redirects. This is appropriate as X3 because the backlog is disproportionate to the creation rate. Tazerdadog (talk) 21:17, 12 March 2024 (UTC)Reply
  • Support. These redirects are not useful, given that we have the correct versions, and simply clutter search results and the database. {{Database report}} is good at dumping quarry queries onto a page. Certes (talk) 21:07, 13 March 2024 (UTC)Reply
  • Oppose as there are so many correct redirects without a space before (. It would lead to too many erroneous deletions. More care and consideration is required than a speedy delete. R3 can be used if creation is recent. Suppress redirect on move policy would also need to match. Graeme Bartlett (talk) 22:32, 13 March 2024 (UTC)Reply
    Not specific to you, but I see a lot of discussions on this page (to borrow my earlier wording) act as if in this area admins are also total rubes. Admins are by definition experienced enough to distinguish obvious errors in Wikipedia disambiguators, even unfamiliar ones, from idiosyncratic spelling conventions such as chemical nomenclature or artwork titles. As an example, even someone unacquainted with chemistry can click the redirect Fe(III) oxide and, within two paragraphs, see ample evidence that it's part of a nomenclature. By contrast, if someone were to somehow create Isaac Brock(longevity claimant), no one experienced enough to be an admin would think that the disambiguator (longevity claimant) is unique among disambiguators in lacking spaces; even without its existence, if you get as far as typing in "Isaac Brock(" you'll see the result you're looking for in the dropdown search results. And on top of that, if there's a mistake it's also entirely reversible. The Blade of the Northern Lights (話して下さい) 04:02, 14 March 2024 (UTC)Reply
    This is all well and good so long as the admin bothers to read the page title and comprehend what they are doing before pressing delete. Doesn't sound especially difficult of course, but CSD definitely attracts the type who are intent on speed over anything else. J947edits 07:05, 14 March 2024 (UTC)Reply
  • R5 as first choice, X3 as second. There are ways to handle some of the false positives, including using {{R from chemical formula}} on chemistry redirects. The fact is that there are just a very large amount of these and this ongoing clean up has been going on for years. Even using twinkle to send to RfD is time consuming as some editors want these grouped up (which is understandable), but the template at RfD is expanded (for whatever reason) so it isn't a smooth and easy copy/paste. Then we also come into a problem of batch nominations where time and time again it has proven that editors just don't like these and these fail for no other reason other than that. So we end up with clean up editors needing to decide each time what amount is the correct amount to batch up... which is just a waste of time. To the above concern about admins not doing their job correctly. If the that happens, the problem isn't with this but with the admin themselves and the proper channels should handle that. --Gonnym (talk) 08:13, 14 March 2024 (UTC)Reply
  • Comment - I originated (and have expanded as necessary over time as more examples arise) the content contained at WP:RDAB. I did so because it is easier to reference the sentiment expressed there with a quick shortcut rather than repeating myself over and over again at redirects for discussion. However, on similar grounds, I oppose this as a temporary remedy because such redirect archetypes arise and populate the venue so often. I am also unsure if I would support such a criterion if it were proposed as permanent. I would have to put a lot more thought into the matter than I have at the moment. — Godsy (TALKCONT) 09:36, 14 March 2024 (UTC)Reply
    @Steel1943: A partial answer to your question posed much above (i.e "does anybody recall why the texts at WP:UNNATURAL and WP:RDAB were written?") is contained in my comment right above this. Let me know if elaborating further on any particular point would be of help. — Godsy (TALKCONT) 09:55, 14 March 2024 (UTC)Reply
  • Support There seems to be agreement that these should be deleted at RfD, and that is what ultimately controls. * Pppery * it has begun... 23:14, 14 March 2024 (UTC)Reply
  • Support per NOTBURO; this solely enforces a longstanding consensus, even if I disagree with the longstanding consensus. First hand experience, this is also putting a huge burden on RfD. Queen of Hearts she/theytalk/stalk 20:39, 18 March 2024 (UTC)Reply

More G5 misuse edit

See Wikipedia talk:Arbitration Committee#WP:ECR as a side step to WP:CSD. SmokeyJoe (talk) 22:13, 10 February 2024 (UTC)Reply

See #RfC: Status of G5 (in which you already participated) above. * Pppery * it has begun... 22:17, 10 February 2024 (UTC)Reply
That's... a misuse of removing ExCon... Primefac (talk) 14:13, 13 February 2024 (UTC)Reply
Dead link; archived at Wikipedia talk:Arbitration Committee/Archive 25 § WP:ECR as a side step to WP:CSD. jlwoodwa (talk) 04:37, 18 March 2024 (UTC)Reply

Promote G/A/F/C criteria to top-level sections edit

It seems better to have these be top-level sections, rather than under a redundant "List of criteria" heading. Remsense 03:00, 23 February 2024 (UTC)Reply

The current structure of the ToC (with "criteria" being the same level as "non-criteria" and "obsolete criteria") makes perfect sense to me. —Kusma (talk) 06:46, 23 February 2024 (UTC)Reply
It is more strictly logical, but it is slightly less good in terms of convenience—or at least it is for me, using Vector 2022, where the ToC is permanently on the side, and top-level headings are collapsed by default. Remsense 06:50, 23 February 2024 (UTC)Reply
We should not make things worse because Vector 2022 is broken. —Kusma (talk) 07:13, 23 February 2024 (UTC)Reply
I would still prefer find this layout preferable barring any particular visual presentation, for what its worth. I don't think Vector 2022 is broken, I quite like it, but it happens to emphasize what I find to be this genre of minor issue.
When the main point of an article isn't stashed under one heading, it works exactly how I want it to. See also: articles about historical events with a monolithic "History" section for no practical reason beyond category theory. Remsense 07:19, 23 February 2024 (UTC)Reply
See also: biographical articles where some editor has decided the article needs sections and implemented that by adding a "Biography" or "Life" section containing all but the first paragraph. Anyway I like the new flatter hierarchy. —David Eppstein (talk) 08:09, 23 February 2024 (UTC)Reply
I see where Remsense is coming from on this. With the title of the page being Criteria for speedy deletion, at first glance, it does seem a little redundant to have a section on the page titled List of criteria. All the best, ‍—‍a smart kitten[meow] 06:56, 23 February 2024 (UTC)Reply
Yeah. That might be worth looking at. Done here. SmokeyJoe (talk) 06:55, 23 February 2024 (UTC)Reply

A Slightly Different G5 ? edit

This is a question about whether my interpretation is correct that a slightly different version of G5 is correct. There is a discussion in progress at MFD, so it is not important right now whether this is G5, but I would like other views. A draft was created by an account that was then globally locked by a steward. The reason for the global lock is that the account is a sockpuppet of another globally locked account, and the earlier account had been globally locked before the draft was created. So my question is whether this would be speedy-deletable as G5, and my opinion is yes, but I would like another opinion. A global lock is a technical mechanism for preventing a user from logging on, so it is really a form of block. A sockpuppet of a globally locked user is evading a block in a way similar to a sockpuppet of a user that has been blocked on the English Wikipedia. So my question is whether my understanding is correct, that this draft can be deleted as G5. Since it is already at MFD, we can let the MFD run this time, but I would like to know whether, in the future, such drafts (or articles) can be nominated for G5. It doesn't look exactly like a normal G5. Robert McClenon (talk) 16:08, 24 February 2024 (UTC)Reply

My interpretation is the same as yours: that the article can be nominated under G5. I don't see any difference between a global lock and a local block or ban. Of course in any particular case (and I don't know what this one is) no action or an XfD discussion may be better. Phil Bridger (talk) 16:19, 24 February 2024 (UTC)Reply
I was mistaken about it being a draft. It's a user talk page. The MFD is Wikipedia:Miscellany for deletion/User talk:Sakda Kulnaphang . Other editors have said that the originator was spamming. The portions of the posts that I can read look like spam. I !voted to Delete because Wikipedia doesn't have a use for advertising by blocked sockpuppets. The nominator probably tagged it for MFD rather than for G5 because it doesn't look like a typical G5. Robert McClenon (talk) 03:44, 25 February 2024 (UTC)Reply
The nominator did tag it for CSD -- twice -- before bringing it to MFD. Primefac (talk) 12:38, 25 February 2024 (UTC)Reply
I was under the impression that user talk pages are not generally deleted barring clear and obvious issues (G10, outing, death threats, etc). Primefac (talk) 12:37, 25 February 2024 (UTC)Reply
I agree, user_talk pages are not generally deleted at MfD. The rare main exception has been that the talk page has no history of being used as a talk page, eg a NOTWEBHOST dump was placed on an unused talk page.
Problematic talk pages can often be completely sufficiently dealt with by blanking. Where that is not good enough, the page should probably be quietly referred to WP:Oversight. If blanking is not good enough, it is a worse idea to advertise the problem at MfD.
I’ve never seen a good reason to tag a usertalk page with U5, or a good reason to expand u5 to user_talk.
On the use of G5, especially with global blocks, I’ve seen that it quickly becomes technical, with necessary attention to detail on the time of edit and time of block, and I really think these questions are best referred to WP:SPI clerks. SmokeyJoe (talk) 01:23, 26 February 2024 (UTC)Reply
I tend to think that user talk pages should only be speedily deleted if every single revision is either blank or eligible for speedy deletion. Sure, that's how every speedy deletion is supposed to work, but it's especially important for user talk pages because their purpose means that they often have edits from users other than the one the user talk page is about. I don't think that U5 would apply to User talk:Sakda Kulnaphang because of the namespace, and I dunno if G5 is applicable. Jo-Jo Eumerus (talk) 07:54, 26 February 2024 (UTC)Reply

Repeated Speedy Deletions (or: is AfD sovereign?) edit

A page is nominated for speedy, recreated and then deleted via an AfD. The page is then recreated yet again. A subsequent request for speedy G4 is declined because G4 says, This criterion also does not cover content undeleted via a deletion review, or that was only deleted via proposed deletion (including deletion discussions closed as "soft delete") or speedy deletion.

This is, BTW, the current AfD of the article in question. The application of the 'no more than one speedy, ever' interpretation has meant the article being deleted through AfD, recreated and then a (IMHO) perfectly proper G4 declined - resulting in yet another AfD.

However, I read that G4 text as intending to mean 'if an article has not gone to AfD you can't nominate it twice for speedy deletion', which makes sense. AfD is, surely, sovereign - and therefore would effectively 'cancel' or supersede any previous speedy deletion nomination, allowing a page that had been deleted via AfD and then recreated to be nominated for speedy G4 when it had been quite properly deleted via consensus (and no deletion review involved). Should the text of G4 be clearer, therefore, and specify something like "This criterion also does not cover content undeleted via a deletion review, or that was only deleted via proposed deletion (including deletion discussions closed as "soft delete") or speedy deletion - unless it has been subsequently deleted via the AfD process."

I do hope that all comes across as clearer than I fear it might... Alexandermcnabb (talk) 07:14, 28 February 2024 (UTC)Reply

Of course it's a G4. You can't immunize a title from ever being G4'd by writing 'LOL, JIMBO IS GAY' there once. The point of that clause is that you can't G4 something unless it's gone through AFD, even if it happens to have been speedied or prodded; that's why it says "only". I've deleted it. —Cryptic 07:40, 28 February 2024 (UTC)Reply
I agree. I closed the new AfD accordingly. —David Eppstein (talk) 07:48, 28 February 2024 (UTC)Reply
There is no interpretation involved here. The criterion clearly contains the word "only". Phil Bridger (talk) 07:52, 28 February 2024 (UTC)Reply
I thought it was clear (hence "a (IMHO) perfectly proper G4") but others appear not to have found it so... Best Alexandermcnabb (talk) 07:57, 28 February 2024 (UTC)Reply
If a page has been deleted at its most recent XfD and is recreated in a way that is substantially identical to the deleted version, then it may be speedily deleted under G4, unless it was draftified/userfied for improvement and/or undeleted at DRV. The only interpretation required is whether it is substantially identical to the deleted version.
Of course, it is not required to be speedy deleted, and editors may choose to take it to a new XfD if they wish (e.g if they aren't sure if the changes are significant enough, or they think consensus might be different this time.) Thryduulf (talk) 10:58, 28 February 2024 (UTC)Reply
Actually, it also excludes pages to which the reason for the deletion no longer applies which might apply in cases where e.g a biography is deleted for lack of notability and then restored with the exact same text when some event has conferred notability. That said, G4 isn't the only speedy deletion criterion - if a page speedily deleted for being spam is restored with the exact same text, G4 wouldn't apply but the previous speedy deletion reason (G11, in this case) would. Otherwise, yes, a previous speedy deletion does not affect G4 eligibility one way or another when there was an AfD in the meantime. Jo-Jo Eumerus (talk) 09:13, 9 March 2024 (UTC)Reply

Time to get rid of A2? edit

Pretty much the title. For one, it is not used frequently (the last 100 entries take us back to November 2021). But more importantly, I don't think deletion is actually beneficial. The criterion itself calls for tagging with {{Not English}} (if it does not exist on a different language Wikipedia), and I would add that draftification is a good option as well. Given those two alternatives to deletionWP:ATD-T and WP:ATD-I—exist, I am not sure we should have this CSD (c.f. WP:PRESERVE). Is there anything I am missing/other thoughts? HouseBlaster (talk · he/him) 03:46, 5 March 2024 (UTC)Reply

Nowadays most of these creations are in Draft space, so that is where they get knocked back. If there is a chance that the content is useful to another project or could be translated, then draftifying could be good. Graeme Bartlett (talk) 21:45, 5 March 2024 (UTC)Reply
Presumably, the justification for draftifying new non-English articles is Wikipedia:Drafts#During new page review #2a-iii, that the article meets some speedy deletion criterion, namely A2? So in order to continue justifying these draftifications it would be appropriate to add non-English to the list of reasons why a page might be obviously unready for mainspace, releasing A2 from its role there. —David Eppstein (talk) 22:18, 5 March 2024 (UTC)Reply

RfC: deprecating A2 edit

Should A2 (Foreign-language articles that exist on another Wikimedia project) be deprecated as a CSD? 01:18, 9 March 2024 (UTC)

  • Support as proposer. A2 is rarely used, and thus fails NEWCSD3. The last 100 entries on that query take us back to November 2021, and when you ignore false positives my rough count takes us back to February 2021. Assuming all of the articles which qualify for A2 need to be deleted, AfD can handle an additional ~0.14 articles a day. But more importantly, I don't think deletion is needed in this case. Incubation and tagging for translation is a viable WP:ATD, and per ATD If editing can address all relevant reasons for deletion, this should be done rather than deleting the page. HouseBlaster (talk · he/him) 01:18, 9 March 2024 (UTC)Reply
Notified: Template:Centralized discussion. HouseBlaster (talk · he/him) 01:22, 9 March 2024 (UTC)Reply
  • Oppose. Foreign language articles pasted into English Wikipedia without any translation are low effort on the part of the article creator and not a good use of editor time. The status quo of deleting these seems fine here. Also, the idea of sending more articles to AFD is not exactly a selling point, as it is often mentioned that AFD is backlogged and does not have enough regular !voters. –Novem Linguae (talk) 02:23, 9 March 2024 (UTC)Reply
  • NEWCSD is not the threshold to repeal a criterion, unless you'd like to make a play at A7 and G11 - when we've removed criteria before, it was because essentially all uses of them were incorrect. And oppose on the merits too: these aren't enwiki articles, they're requests for enwiki articles, without even the possibility of moving them to the proper project (where, in my experience, they're either ignored forever or deleted outright anyway). —Cryptic 02:43, 9 March 2024 (UTC)Reply
  • Oppose. It may not be used much directly, but my comment above that it is still needed to justify draftication appears to remain unaddressed by the nominator. —David Eppstein (talk) 02:50, 9 March 2024 (UTC)Reply
    I would be happy to note in the proposal that it would be deprecated in favor of draftifying. HouseBlaster (talk · he/him) 16:01, 9 March 2024 (UTC)Reply
    You miss the point. To draftify an article requires a rationale. The current rationale for draftifying non-English articles invokes A2. Removing A2 also removes this rationale from draftification, preventing in-process draftification of non-English articles. If you want to continue draftifying non-English articles, leave A2 in place and it will just work. —David Eppstein (talk) 19:03, 9 March 2024 (UTC)Reply
    “Wanted topic but not in English” sounds like a good draftification rationale. SmokeyJoe (talk) 23:02, 9 March 2024 (UTC)Reply
  • Strong support per every point by the proposer. Eligible cases are required to have a corresponding article on another language Wikipedia. This is an implicit claim that the topic is missing from the English Wikipedia. Draftification for translation is an obvious better route. Far less WP:BITEY is one big reason. SmokeyJoe (talk) 08:16, 9 March 2024 (UTC)Reply
  • Support per proposer and especially SmokeyJoe. This criteria long predates draftspace, and the wiki has also changed in other ways in the past 15 or so years. Additionally, every criterion should be compatible with NEWCSD. Yes there are some that have been grandfathered in, but that doesn't mean they would be good criteria if proposed today or that we shouldn't periodically review existing criteria to see if they are still fit for purpose (this is why R4 and G14 exist as separate criteria). Thryduulf (talk) 09:48, 9 March 2024 (UTC)Reply
    • Oppose at least for now. Largoplazo makes good points in the Discussion section below about needing to consider this in concert with pages needing translation, and others' comments about how this interacts with criteria for draftification are also valid. This isn't an endorsement of the status quo, rather I think we need to take a comprehensive look at how we want to handle non-English submissions in 2024 and then make necessary changes to all the affected policies and guidelines to match that. Thryduulf (talk) 11:44, 10 March 2024 (UTC)Reply
  • Oppose per Cryptic. Just copying some content doesn't mean one would necessarily work on translating it. Aaron Liu (talk) 13:36, 9 March 2024 (UTC)Reply
    Sounds like the purpose of draftspace! SmokeyJoe (talk) 23:03, 9 March 2024 (UTC)Reply
    That takes six more months of lying around, which irks me >:(. If someone wants to actually work on something, IMO they'd translate the text and put it there one by one instead of just copying something, or, even better, use the content translation tool. I don't see the value of keeping stuff that would be deleted under A2. Aaron Liu (talk) 23:27, 9 March 2024 (UTC)Reply
    You think six months is too long a deadline?
    There is no cost to putting the foreign language submission in draftspace. I think there is value in giving the author one week to follow up. And once it’s been one week, why not ignore it for six months. The cost of complicating G13 is more than the cost of leaving untouched in draftspace for six months.
    Many editors are not very good with their first edit. Here, it is necessarily an autoconfirmed editor, but still, fresh autoconfirmed editors are not always very good. Do you think Wikipedia needs a higher barrier for competence before they are allowed to create a mainspace page?
    The value of draftification is in pointing out to the newcomer where draftspace is, and allowing them to continue their intended contribution. SmokeyJoe (talk) 05:59, 10 March 2024 (UTC)Reply
    I don't see how deleting a copied page produces a higher barrier to contribution. My interpretation of A2 is that it only applies if the article's entirely foreign language but nothing else. If there is something else to salvage, A2 wouldn't apply, and the article can still be draftified. Aaron Liu (talk) 13:07, 10 March 2024 (UTC)Reply
  • Support. In 2024, there are sufficient tools available to assess whether a foreign-language page is worthy of translation (then it can be draftified) or not (then the other criteria apply). A2 seems to do more harm than good if we delete articles solely based on whether they are not in English and not on their merits. For example, Karl Friedrich Wunder which was deleted as A2 in January was a copy of de:Karl Friedrich Wunder (a notable 19th century photographer) was eligible for deletion under G12 since copying another language Wikipedia article is also a violation of copyright. Saturnino de la Torre was a wrong A2 since it didn't exist on es-wiki at that time but was probably eligible for G11 like the es-wiki counterpart. Point is, I don't think there is really much need anymore for A2 because in most cases the material either already fails another criterion or it's translation-worthy. Regards SoWhy 18:26, 9 March 2024 (UTC)Reply
  • Oppose when I first looked and read this discussion or at last the 1st points I was going to support. However having read the rest and thought a bit more about it I think this criteria is good. Objective, most people are likely to agree foreign language articles that exist on another Wikimedia project should be deleted as no content is actually lost as the content and history will still be on the foreign language project. Uncontestable, again this is a bit like A10 and arguably for the same reason as splitting G14 from G6 it might not be a good idea to merge or if this criteria is removed I'd expect people to use G6 anyway. Unlike T2 its quite simple so which as noted in the discussion to repeal T2 that the criteria is not easy to understand unlike this one. Frequent, yes it doesn't appear to be extremely frequent but with around 1 use per week that seems frequent enough given as noted in the U3 discussion neither A9 nor A11 appeared in around 32 hours of deletion. So I think this passes the 1st and 2nd NEWCSD and given the reasons for splitting G14 I'd argue along that logic it passes the 4th item and in terms of the 3rd though not very frequent seems frequent enough. I'd agree the articles can be drafted upon request but it seems a bit pointless given the article will still exist on the other project so if the author wants to start translating they can still use that page to get the content from. Crouch, Swale (talk) 18:42, 9 March 2024 (UTC)Reply
    “Uncontestable”, that the wanted topic but not written in English needs to be deleted? That sounds weak. SmokeyJoe (talk) 23:07, 9 March 2024 (UTC)Reply
    Its not the topic its the content, having a foreign language article with the same content as the native language on the English Wikipedia is completely pointless. Its quite likely that if the topic exists on a foreign language Wikipedia it will be notable here but as noted we don't need to duplicate foreign language content here just like we don't need 2 articles on the same topic on the English Wikipedia. Crouch, Swale (talk) 20:13, 15 March 2024 (UTC)Reply
  • Oppose still a completely valid deletion criteria. Not being used much doesn't mean it doesn't have its place in the toolbox, and each Wikipedia has different notability standards. SportingFlyer T·C 19:09, 9 March 2024 (UTC)Reply
  • Well. A2 exists to enforce WP:MACHINE so we shouldn't repeal A2 without modifying WP:MACHINE, but. I think the ideal process is, reviewing editor looks at article in %language on en.wiki and compares it to the same article on %language.wiki. Reviewing editor isn't necessarily expected to be able to read %language, but makes a quick eyeball assessment: does the version on en.wiki look reasonably developed and substantially different? If not, tag for A2. If so, reviewing editor tags the en.wiki version with {{Not English}} and then drops a note on %language.wikipedia.org/Talk:%Article to ask if they want it. (Reviewing editor is likely going to have to use google translate to make an intelligible note in %language, but that ought to be acceptable for talk pages). %language.wiki then has access to the old text which they can use to develop their article if appropriate, and en.wiki doesn't have foreign-language content in mainspace. Happy days. I do feel that this process is a useful way round a 7 day community timesink at AfD, but I also think it needs better documentation than currently exists.—S Marshall T/C 21:25, 9 March 2024 (UTC)Reply
    A2 predates MACHINE.
    If A2 requires human review, it should be PROD not CSD. I think immediate draftification is much better than PROD for a new non-English article. SmokeyJoe (talk) 23:11, 9 March 2024 (UTC)Reply
    Thank you for sending me on that nostalgic trip into Wikipedia history.  :) I don't think it's strictly accurate to say that A2 predates MACHINE. The text now at WP:MACHINE has moved around a lot, and was, originally, phrased as:

    Translation is hard. Amateur translators tend to produce prose that is unnatural, and perhaps incorrect when it comes to specialized terminology....Machine translation is much much worse. Never use machine translation to create an article!

    I've traced that text back to the first revision of Wikipedia:Translations, on 11 May 2003. According to the edit summary that text was moved from the Village Pump and considering the date, I expect that would have been a cut-and-paste move. The paste includes undated text by User:MyRedDice, who is now User:MartinHarper and was incidentally the inventor of the Three Revert Rule and the Barnstar, saying "We do indeed recommend against machine translation". In other words, the gist of WP:MACHINE has been custom and practice since at least May 2003.
    Well, at that point in time, what's now the Criteria for Speedy Deletion read like this and the criteria for speedy deletion were collectively called "exemptions from the five-day rule" (which I think at that time was the minimum possible time a page had to be listed on Votes for Deletion before anyone was allowed to delete it).
    I'm saying that both rules go back to Wikipedia's equivalent of time immemorial.
    All CSD "require human review" because it's a human that adds the tags. We expect those humans have read, understood what they were reading, reflected if necessary, and then taken a decision to use CSD. Something should be a PROD when it needs two humans to review it. Therefore A2 is appropriate for CSD, not PROD.
    Why would draftification be a helpful step? Content doesn't meet A2 unless it duplicates content on another WMF project, so I can't see any benefit to using draft space in that way.—S Marshall T/C 00:13, 10 March 2024 (UTC)Reply
    All CSD require human review? Great in theory. Tagging if often done in error. Any editor or IP can tag {{Db-a2}}. And then, there’s plenty of not so old evidence of some admins would delete tagged pages en-mass, at high speed. This is why there is supposed to be the rule, all eligible pages should be deleted.
    Would draftification be helpful? Yes, it would be helpful to the editor who saved the article there. They should have saved it in draftspace. Moving it to draftspace necessarily means that the article log will point to the draftpage. Then, when that editor comes back, they can find the draft, both from the deletion log of the article title, and in their contribution history. This is more helpful to them than coming back to find a log entry mentions A2, and no record that they ever did anyhthing. SmokeyJoe (talk) 05:53, 10 March 2024 (UTC)Reply
  • Oppose, solution looking for a problem. Stifle (talk) 11:46, 12 March 2024 (UTC)Reply
  • Change to speedy draftification: As stated by editors in this discussion and above, deletion might be a bit too harsh, and these are requests for articles to be created on English Wikipedia. Speedy draftification might be the best way to allow for these articles to be developed for enwiki. Failing that, repeal. Awesome Aasim 13:34, 12 March 2024 (UTC)Reply
  • Oppose per David Epstein, Cryptic, and S Marshall. Translation tools are not yet 'sufficient'. Moreover, one should not potentially use the mainspace in an attempt to tip the scales towards the translation or scrutiny of viability of one topic over any other. Just because a criterion exists does not mean the deletion of such a page is a certain; incubation is still an option if a page is deemed worthy of retention by those reviewing it. At the end of the day, non-English content is likely of little use to most of our readers; eliminating a longstanding tool to easily and quickly remedy that is not a good idea. — Godsy (TALKCONT) 08:51, 14 March 2024 (UTC)Reply
  • Oppose As long as it is being used to delete pages that are of no use to us, we should not be repealing criteria solely because they are not used very often. Having this criteria discourages users from other language Wikipedias from copying their articles onto here without properly translating, resulting in a page that needs a fundamental rewrite. funplussmart (talk) 20:46, 16 March 2024 (UTC)Reply
  • Oppose; not broken, the last thing AfD needs is more burden. Queen of Hearts she/theytalk/stalk 20:37, 18 March 2024 (UTC)Reply

Discussion of A2 RFC edit

  • Comment WP:Pages needing translation into English should be taken into account. Should this RFC be closed and redrafted to consider both together? Under the terms of WP:PNT, an article created in a language other than English that doesn't qualify for A2 (or any other reason for deletion) gets a grace period of two weeks. If translation isn't at least underway by then, the article gets put up for deletion under WP:PROD or WP:AFD. It doesn't make sense to give non-English articles treatment that's disparate in this manner, one month to live if they aren't on another language's Wikipedia and six months to live if they are.
Having said that, draftification really has changed the game, as most of the otherwise legitimate articles listed on WP:PNT, by the time I see them, are red links because someone's response was to draftify them. So if this RFC comes out in favor of draftification as a blanket treatment when a non-English article is on another Wikipedia, then it will make just as much sense to make draftification that standard treatment for all non-English articles, and eliminate WP:PNT's role in that situation. WP:PNT would still be of use for cases for which it's used today, where someone has added a chunk of potentially useful non-English material to an article already in English. And it would retain its role as the place to post requests for fixing articles that have been translated to English.
If this change in guidance were to be made, however, it would definitely be time to rename WP:PNT (which should long ago have been renamed WP:Articles needing translation to English, since non-articles, including drafts, aren't handled there) to something else, since coverage of "Pages needing translation" would no longer be its role at all.
Alternatively, we could simply allow the drafts to be listed at WP:PNT. And remove the two-week grace period. Let all entries remain posted until either translated or G13ed.
Due to all these considerations, I think A2 and WP:PNT should be considered holistically. Largoplazo (talk) 11:06, 10 March 2024 (UTC)Reply
I may be wrong (I haven't done a lot of work at WP:PNT for at least a decade now) but I don't think any articles have actually been given the two weeks grace for a few years now. Most articles either get deleted as copyvios or A2 or moved to draft space well before the two weeks have expired. Ping @Lectonar who might be able to correct me. —Kusma (talk) 12:00, 12 March 2024 (UTC)Reply
I can only speak for myself here, but I will respect the 2 weeks grace for prodded articles. As for the case of Saturnino de la Torre which I deleted as an A2 because it had once existed on Spanish Wikipedia: I actually interpret A2 a bit more widely here: for me it's enough that an article has once existed in another Wikipedia; requirements for an article here are more strict regarding sources and notability in compariosn to most other Wikipedias....so if something is deleted at, e.g., Spanish Wikipedia, rare would be the case that it would stand as an article here. And yes, probably it would have been eligible as a G11, but that would mean the article would have to be translated first, or the prospective deleting admin is able to read and understand enough Spanish to be able to process it without translation...this would rather cut down the number of admins who could delete. On another point, G speedy deletion criteria are "general" ones, while A deletions are restricted to article space. When I have a choice, I will use the specialized criterion over the general one. Lastly, allowing drafts at WP:PNT will inflate the workload over there even more. It's bloated enough as it is. But I would support a move to WP:Articles needing translation to English. Lectonar (talk) 12:19, 12 March 2024 (UTC)Reply
It is not PNTers who do not respect the two weeks (I realise I have not been clear in what I wrote); what happens most of the time is that pages get listed at PNT and then are dealt with by other people using other mechanisms (draftified/speedied) so PNTers just have to remove the redlinked entries. —Kusma (talk) 13:53, 12 March 2024 (UTC)Reply
That is correct. WP:PNT used to be fun, I actually got to do some translation, now it's just remove the red links and maybe the date header. On the other hand, if we were to start accepting drafts there, then I'd have my pointers to potential translation fodder back, in cases where the language is the only reason the article was draftified. Largoplazo (talk) 21:14, 18 March 2024 (UTC)Reply
  • To look at some real cases, would someone please temp undelete and list the last twenty A2 deletions? -SmokeyJoe (talk) 13:35, 10 March 2024 (UTC)Reply
    Undeleting into mainspace would be pretty bad. I'd say somebody just copy the contents and put them in userspace. Aaron Liu (talk) 14:13, 10 March 2024 (UTC)Reply

R3: redirects from foreign edit

Are there any objections to adding the underlined text to WP:R3? Currently, it seems to state an exception (certain redirects from foreign should be kept) without stating the rule which it qualifies (inappropriate redirects from foreign may be deleted).

This applies to recently created redirects from implausible typos or misnomers or from languages other than English that are not pertinent to the topic. However, redirects from common misspellings or misnomers are generally useful, as are some redirects in other languages... [continues as before]

This addition was prompted by Wikipedia:Redirects for discussion/Log/2024 March 9#シカゴ大学. Certes (talk) 23:10, 9 March 2024 (UTC)Reply

I feel like this actually changes the rule too much. R3 is about whether something is implausible - the additional text basically implies just being in a foreign language is not grounds for implausibility. This would instead turn R3 into RFOREIGN. SportingFlyer T·C 00:57, 10 March 2024 (UTC)Reply

Template:Db-r3 is also confusing: it marks an implausible typo or misnomer, which is not in another language pertinent to the topic. What does this mean? Taken literally, it says that typos and misnomers must be kept as long as they're in a pertinent language (so Brookselz → Brussels would be ineligible for deletion, even though it's an implausible typo for Bruxelles, because it's in a pertinent language). Obviously, that's not the intended meaning. Is it trying to say the same as I'm suggesting above? Certes (talk) 10:33, 10 March 2024 (UTC)Reply

  • Support as I suggested, these generally get deleted if this applies due RFOREIGN having widespread consensus. Crouch, Swale (talk) 19:15, 10 March 2024 (UTC)Reply
  • At minimum, this doesn't belong in R3. These are neither typos nor implausible misnomers, time since creation shouldn't be a factor, and R3 is not a dumping ground for everything that usually gets deleted at RFD. —Cryptic 20:58, 10 March 2024 (UTC)Reply
  • Oppose, "not pertinent to the topic" isn't always clear enough to be decided by a single admin. —Kusma (talk) 21:00, 10 March 2024 (UTC)Reply
  • Oppose per Kusma. Whether something is pertinent sometimes needs knowledge of the language and/or subject. Thryduulf (talk) 22:00, 10 March 2024 (UTC)Reply
  • Oppose per Kusma. Lectonar (talk) 09:27, 13 March 2024 (UTC)Reply

Thanks to all who replied. It's looking as if we need to continue pushing these through RfD, which is easy with Twinkle though !voting takes time. (They've been unanimous Deletes so far.) Certes (talk) 11:25, 13 March 2024 (UTC)Reply

Would it be helpful to clarify the wording of R3 and/or {{db-r3}}, both of which seem to refer to desirable redirects from non-English as if they were an exception to the deletion criterion I was trying to add? Certes (talk) 23:30, 13 March 2024 (UTC)Reply
From foreign languages is not cut and dry enough. Affinity in regard to a topic is best sorted at RfD. To foreign language wikipedias probably would be a criterion, if it were more common. See Wikipedia talk:Redirects for discussion/Common outcomes#Redirects (soft) to other language versions of Wikipedia if interested. — Godsy (TALKCONT) 09:01, 14 March 2024 (UTC)Reply
A proposal for a speedy deletion criterion covering redirects to non-English wikis failed to get consensus in 2013 (see Wikipedia talk:Criteria for speedy deletion/Archive 48#Soft redirects to foreign-language Wikipedias). I don't recall any discussions more recently than that. Thryduulf (talk) 10:40, 14 March 2024 (UTC)Reply

Question About Declined Draft Moved to Article Space edit

A question has arisen at my user talk page about what can be done when a draft that is declined in AFD is moved unilaterally to article space. An editor says that they have been told that it is then eligible for G4. I didn't think so, but I am aware that I might not know something. The article that started this discussion was Paloma Aguirre, which was written by a paid editor, and declined by an AFC reviewer as a draft, and then copied to article space. I WP:PROD'd the article, and was asked whether that was the right action, because that will result in a Soft Delete. I don't know whether the subject is notable. I didn't want to do a source analysis, and didn't want to write an AFD without a source analysis on notability. So then this question arose about whether declined drafts moved to article space can be tagged as G4. Robert McClenon (talk) 19:32, 11 March 2024 (UTC)Reply

Paloma Aguirre edit

Are you sure it is best to use WP:PROD for these? If successful, it will result in WP:SOFTDELETE. Do we want a stronger result?

Also pinging User:Scope creep who endorsed the PROD. ~Kvng (talk) 17:11, 11 March 2024 (UTC)Reply

User:Kvng - I will be satisfied with a Soft Delete as the right result. The alternative would of course be to send the article to AFD, and decide whether the subject is biographically notable. I have no opinion on her notability. She may be notable. A soft delete permits a neutral editor to request undeletion. If a neutral editor requests undeletion, they may leave the biography unchanged or improve it. In either case, it can then be taken to AFD on the merits. To be honest, I PROD'd it because I didn't feel like doing a source analysis (and I wasn't prepared to argue lack of notability unless I did a source analysis), and knew that I might be doing a source analysis at a later day. Robert McClenon (talk) 17:45, 11 March 2024 (UTC)Reply
@Kvng: @Robert McClenon: I'm pretty detached from it as well. If it comes up again, it will appear in the watchlist. I would have G4 since it was declined at AFC review, which is the legitimate way of deleting it, but ok with prod. If it comes back again, it go to Afd and it will be salted. scope_creepTalk 18:07, 11 March 2024 (UTC)Reply
User:scope_creep - It is not my understanding that a decline at AFD enables a G4. It is my understanding that G4 is only available when a page has been deleted after a deletion discussion in the address space that the nominated page is in. It is my understanding that a neutral editor may move a declined draft from draft space into article space to contest a decline, and then it will be subject to AFD as a consensus process, so that there is a consensus process for reviewing the unilateral action of the decline. If there has been a change to the G4 criteria so that a declined draft that is sent to article space can be tagged for G4, I would like to know (and might disagree). In this case, the reason why the author did not have the right to contest the decline by moving it to article space is that they are a paid editor. I think that in a while I will copy this discussion to the AFC talk page for clarification. Robert McClenon (talk) 18:20, 11 March 2024 (UTC)Reply
Not at Afd. If its declined in Afc and then moved to mainspace and its junk, it can be G4'd. I think that is the process as far as I know. I didn't know you could G4 until a few days ago, when I saw it in a conversation. I've not used it as yet. scope_creepTalk 18:33, 11 March 2024 (UTC)Reply
If its declined in Afc and then moved to mainspace and its junk, it can be G4'd. Really? I don't see anything in the criterion that suggests that this is true. If it's junk enough to meet one of the other criteria for speedy deletion then do it. But G4? Remember AfC is decided by only one usually non-admin editor. Phil Bridger (talk) 19:45, 11 March 2024 (UTC)Reply
User:Scope creep is wrong. An AfC decline in the history does not enable G4. G4 requires an AfD consensus to delete and for the new page to be substantially identical. SmokeyJoe (talk) 23:01, 11 March 2024 (UTC)Reply
I believe AFC is unrelated to AFD and G4. I think G4 is only for AFD results. –Novem Linguae (talk) 02:50, 12 March 2024 (UTC)Reply
XfD results. Eg a prior MfD on a draft also works. SmokeyJoe (talk) 05:43, 12 March 2024 (UTC)Reply
If in doubt, the answer is almost always XfD. Draftspace and AfC is optional. If someone doesn’t think it belongs in mainspace, use AfD. If there is any evidence of actual dispute, use AfD not PROD, PROD is intended for things that you think no one cares about. SmokeyJoe (talk) 22:55, 11 March 2024 (UTC)Reply
There was a conversation clear as day about it that stated G4 could be used, unless I misinterpreted it. It was only a couple of days ago. Up until that point i'd only used articles that had reappeared after an Afd deletion. I'll try and find it. scope_creepTalk 05:05, 12 March 2024 (UTC)Reply
Using g4 on declined drafts moved to mainspace also contradicts WP:DRAFTOBJECT and the idea that draftspace is optional. Perhaps there was a misunderstanding somewhere. –Novem Linguae (talk) 05:24, 12 March 2024 (UTC)Reply
Start with WP:G4. “This applies to sufficiently identical copies, having any title, of a page deleted via its most recent deletion discussion”.
G4 can never be used where there was not a deletion discussion. An AfC decline is certainly not a deletion discussion. SmokeyJoe (talk) 05:41, 12 March 2024 (UTC)Reply
Maybe someone in a conversation said that it could be done. One misguided person in a conversation saying it doesn't make it true. Phil Bridger (talk) 07:25, 12 March 2024 (UTC)Reply
@Scope creep where was this conversation, because the people in it need to know that they have been giving incorrect advice. AfC is completely irrelevant to G4, because it is not a discussion or related to deletion, let alone a deletion discussion. Pages may only be deleted when there is consensus to delete, the speedy deletion criteria list the only times when that consensus may be presumed to exist without a discussion about the specific page. G4 exists because when a page is substantially identical to how it existed at the time a consensus was reached to delete it, we can presume that consensus still exists. A page being declined at AfC is not a consensus for anything, just one editor's opinion that it is not currently suitable for mainspace. Thryduulf (talk) 11:56, 12 March 2024 (UTC)Reply
User:Thryduulf - Occasionally in Wikipedia misinformation about Wikipedia policies and guidelines becomes so widespread that it rises to the standing of myth. This is such a case. It is not the only time I have been advised that declined AFC drafts that are mainspaced should be tagged to G4. So I think it is at least as important simply to restate the correct information as to identify the source of the myth, because it has become myth. Thank you, User:Novem Linguae, User:Phil Bridger, for restating the guideline accurately. There are probably occasional cases where declined drafts moved to mainspace can be tagged for G4, but only if the history is that there was a previous deletion discussion and the draft is similar to the previous deleted document, in which case the AFC history is not important. Robert McClenon (talk) 18:24, 12 March 2024 (UTC)Reply
I'm just back in now. I'll try and find it. It has been a busy couple of weeks. scope_creepTalk 18:50, 12 March 2024 (UTC)Reply

Floating an idea about G5. Creations by banned or blocked users edit

After [22], which was an article/draft created that clearly would require Extended Confirmed to edit, I wonder if G5 should be changed to read:

Old: "Creations by banned or blocked users"

New: "Creations by banned or blocked users, or that violate the extended confirmed policy."

I do think that the spirit of policy says that new editors should not be creating drafts or articles on topics that clearly are restricted to EC editors, and this would just be putting into writing what we should be able to do as administrators: speedy delete articles that are by their nature, are violations of policy by their very creation. MfD is the only current solution, but it shouldn't be required for creations that violate policy. CSD is a strict, literal policy, so I think we need to spell this out to simplify things. Feedback? Dennis Brown - 09:55, 14 March 2024 (UTC)Reply

See #RfC: Status of G5 (currently the first section on this page) and the follow-up Wikipedia:Village pump (policy)#How to word G5 expansion/G15 new criteria. Thryduulf (talk) 11:12, 14 March 2024 (UTC)Reply
Is it objective that the new page would clearly require XC? Is it objective to the author? I’m not sure it is. SmokeyJoe (talk) 11:14, 14 March 2024 (UTC)Reply
Thank you. I probably should be watching those pages more than I do now (which is very little). That is probably the best place to take this discussion. Dennis Brown - 09:20, 15 March 2024 (UTC)Reply
In general I think the goal of this is correct and coming from the right place, but I worry that there may be edge cases in here worth considering. Let's say an article is under a contentious topic area, and that specific article but not the entire area, is subject to ECR. Would an IP who is attempting to spin something closely related off of that page into a new article, qualify for G5 under this policy? (I foresee the arguments going something like: "Yes, because we disallow Gaming the System" vs. "No, because the ECR only applied to the specific original article, not the whole topic.") SWATJester Shoot Blues, Tell VileRat! 18:34, 14 March 2024 (UTC)Reply
I see what you are saying, but it is CSD and should only be done in obvious cases, which would often. If it were an edge case, then XfD would be the answer. Same as we do now for articles that are non-notable... if there is a VALID claim, you AFD, if not, you CSD. Dennis Brown - 09:32, 15 March 2024 (UTC)Reply
Good point. I suppose that mitigates my concerns. SWATJester Shoot Blues, Tell VileRat! 19:12, 15 March 2024 (UTC)Reply
(See also Awesome Aasim's Wikipedia:Requests for comment/Enforcing ECR for article creators.) I won't repeat everything I said at the VPP discussion, but in sum, I disagree with G5ing ECRvio articles. They should be draftified (ECPing it seems unnecessary but would be fine if that's what an admin wanted to do), so the editor can come back to it when they have XC, and so other editors can work on it if they want to. They should only be CSD'd if they meet some other CSD criteria (attack page, copyvio, etc). Levivich (talk) 21:44, 14 March 2024 (UTC)Reply
An EC violation is still a violation in Draft. Dennis Brown - 09:20, 15 March 2024 (UTC)Reply
Does that benefit Wikipedia? Thryduulf (talk) 11:30, 15 March 2024 (UTC)Reply
Absolutely. It removed an obvious vector for gaming the system by allowing someone to bypass Arb restrictions on editing CTOP areas by creating Drafts, accumulating 500 edits, so they can move into main space. The whole point of the 500 restriction is to not attract this kind of behavior, and encourage general editing before someone enters areas that are problematic. Demonstrated by the MfD I spoke of (and the next draft they created), that resulted in the person getting indef blocked. Had we been able to delete it, it would have removed the incentive to game the system and get blocked. So yes, absolutely would have saved time for many people, including the blocked editor. Dennis Brown - 12:18, 15 March 2024 (UTC)Reply
It's not a violation at all. The edit creating the page is a violation. The page itself is not a violation.
It's like this: if a non-XC editor makes an ECR edit, we tell the editor about the restriction, in a repeated or egregious case we might sanction the editor. But we don't remove the edit just because it violated XC. Even if a good edit were removed, it's just be re-done by someone else. But the edit gets kept or removed based on the edit, not based on who made it. Same principle if the edit is a page creation.
Enforcing rules for the sake of enforcing rules is foolhardy. Building an encyclopedia and all that. Levivich (talk) 19:42, 15 March 2024 (UTC)Reply
You are enforcing the rules because the rules are solving a problem, one so great it required that a restriction be put in place, for a reason. You are focused on the single edit. I am focused on the bigger problem it causes. Having many editors creating drafts and articles that violate EC is a bigger problem than deleting one draft or article, that (under 96%+ of circumstances) probably wouldn't last under XfD anyway. Almost all of these articles are POV garbage, but XfD is the only solution, and a piss poor one. Dennis Brown - 00:43, 16 March 2024 (UTC)Reply
Whether the articles are deleted or draftified will have no effect on the volume of ECRvio drafts and 96% of all new articles are probably crap. Is there evidence that ECRvio new creations are significantly worse than other new creations? Levivich (talk) 06:30, 16 March 2024 (UTC)Reply
I don't know of any measuring system in place, so I can only go by anecdotal experience that the EC violating articles tend to be really over the top POV. It is better to delete and explain than to drag it out in XfD and end up with the editor blocked. That is the big difference, you will have fewer blocks, and fewer articles becoming magnets for debates at XfD that obviously don't belong. It just creates more drama to let non-EC editors create EC anything. They lack the basic experience, so the amount of problems is naturally going to be higher, which again, is why the restriction was put in place, to get new editors somewhat up to speed before they start creating POV essays and trying to pass them as articles. I would say that if someone started a draft that was actually valid, but violated EC, in good faith, that doesn't mean it MUST be deleted. We could tell them to stop editing, let them get some experience, then go back to it. Or userfy it but they can't edit it until they get the 500 edits. we would have some more tools, but right now, we have nothing. I haven't seen one like that, but I know it could happen, and changing G5 won't mean those very few articles would disappear, it would mean we would have options. There is no rule that says WHAT we should do with those articles as it stands. Dennis Brown - 06:50, 16 March 2024 (UTC)Reply
My anecdotal experience differs, and yes we do have a way of measuring it, and yes we do have tools for handling it, I'm happy to show you. We don't need a rule for it, because we don't need a rule for everything, and even if we did, the rule could be "draftify" (which nobody who wants a G5 has yet to explain why deletion of ECRvio is better for the encyclopedia than draftification).
Areej Sabbagh-Khoury and Draft:Palestinian cultural genocide are two recent examples of good-quality ECRvios I've come across. There are many more listed at edit filter 1,276 and I'd encourage you and anyone else who thinks most ECRvio is crap to peruse that list and test your assumptions. Notice the ratio of blue links to red links. Ask yourself if it would be better for the encyclopedia if everything listed there had been G5.
One of the reasons I oppose speedy deleting all ECRvio is that I do not trust admins to be able to distinguish a promising or good quality page from a poor quality page, absent very specific and clear or obvious instructions (such as are provided by CSD criteria). If G5 were allowable for ECRvio, some admins would just nuke all of it, out of hand, without even reading it, in the same way that some admins will block people without looking at sources or sometimes even say that they can't look at sources. So we'll have admins saying they must G5 everything created in violation of ECR, and they can't make a decision as to whether it's worth saving, because that would be getting involved in a content dispute.
And the end result would be that almost everything on that edit filter 1,276 list would be red. And if almost everything on that list were red, we would have lost a lot of good work.
We don't have a problem of being overrun with ECR drafts, and nuking them all out of hand would be a significant step back, not step forward, for writing an encyclopedia. Draftification is the way. Levivich (talk) 14:40, 16 March 2024 (UTC)Reply
  • It seems the best place to take this discussion is actually Wikipedia:Requests for comment/Enforcing ECR for article creators, where an actual RFC is being formulated. This makes more sense than continuing it here. Thanks for looking, and please participate. Whatever the community decides, it will be better than what we currently have. Dennis Brown - 09:30, 15 March 2024 (UTC)Reply
  • What is currently done when an ECR editor creates an article, anyway? What's our current practice? I feel like there's this weird thing where creating a new article, which is a more drastic action, is generally easier to do under policy and practice, and harder to undo, than making the exact same addition to an existing article. --Aquillion (talk) 18:55, 15 March 2024 (UTC)Reply
    Good question, and I think XfD is our only option. If it an article, we can warn the user, and if they continue to edit "their own" article, we can block them. This isn't the best use of the banhammer. Dennis Brown - 00:39, 16 March 2024 (UTC)Reply
    What is currently done when an ECR editor creates an article, anyway? In practice despite all of the words said in the prior discussion, the article is tagged with {{db-gs}} and the correct contentious topic code, which adds it to a specific admin backlog category and a patrolling admin either deletes the article or removes the tag depending on the circumstances. Although the deletion log entries for this are inconsistent, as there's no standardised format, as of this reply there have been at least 18 deletions done with a G5 ARBECR log entry. Sideswipe9th (talk) 01:13, 17 March 2024 (UTC)Reply
    Sideswipe9th, I see this was made back in October of 2023, but I'm not sure that has consensus. I like it, but if it didn't have a clear consensus to create, we need to build that consensus before we use. Just because the template exists, doesn't mean policy supports it. Dennis Brown - 10:57, 17 March 2024 (UTC)Reply

Should there be a new criterion for redirects that imply the target covers a topic it does not? edit

I recently approved Ghanaians in Sweden as a redirect to African immigrants to Sweden at WP:AFC/R. However, the latter page actually does not mention Ghana or Ghanaians, so I shouldn't have created that redirect.   Self-trout

Significa liberdade quickly brought this redirect up at WP:RFD.   Thank you

I went ahead and tagged the redirect as {{Db-g7}}; there's really no need for a discussion on that redirect, but G7 is the only criterion that would apply. To handle cases like this, I am proposing a new criterion:

R5. Redirects to pages without relevant content
This applies to redirects with target pages that do not have content relevant to the redirect's title. It does not apply to redirects that could be appropriately retargeted to another page; such redirects should be fixed, not deleted.

Would this, or something similar, be a useful criterion? Luke10.27 (talk) 02:18, 15 March 2024 (UTC)Reply

How do you feel it meets the four listed criteria at the top of this page? -- Whpq (talk) 02:20, 15 March 2024 (UTC)Reply
  1. Objective: There is little room for debate as to whether or not a page covers a particular topic.
  2. Uncontestable: I can't think of any case in which a redirect pointing to a page that does not cover the topic of the redirect's title would be useful.
  3. Frequent: I'm not sure about this one.
  4. Nonredundant: In this case, G7 applied. However, if I hadn't tagged it myself, none of the existing criteria would have applied.
Luke10.27 (talk) 03:50, 15 March 2024 (UTC)Reply
Both of the redirects with open discussions at Wikipedia:Redirects for discussion/Log/2024 March 15, 5:-) and Hoothi, would fall under this criterion. Luke10.27 (talk) 04:38, 15 March 2024 (UTC)Reply
Sometimes the target article used to cover the topic, and then the question is whether it should cover the topic or not, and whether a different article should cover the topic. Some page being BLARed does not automatically mean all of its previous redirects should be speedily deleted; it is better to examine them individually.
As for your introductory example, Ghanaians are Africans, so the redirect you mention seems a perfectly acceptable {{R with possibilities}}. —Kusma (talk) 09:03, 15 March 2024 (UTC)Reply
My understanding is that {{R with possibilities}} applies to redirects that are covered in the target article, but could be expanded to separate articles? Luke10.27 (talk) 01:23, 17 March 2024 (UTC)Reply
In this specific case there might not be any doubt about whether the topic is covered, but that is not always true. Additionally there is often coverage elsewhere (redirects not getting updated when content is moved), sometimes the lack of coverage is due to vandalism, sometimes the redirect was an article that should be restored and discussed as an article (and there is frequently disagreement about doing that). This is not suitable for speedy deletion. Thryduulf (talk) 11:36, 15 March 2024 (UTC)Reply
That's a good point. I hadn't thought about the possibility of this seeming to apply when it doesn't due to temporary removal of content. Luke10.27 (talk) 01:25, 17 March 2024 (UTC)Reply
  • Weak oppose largely for the same reason as Thryduulf. While I think this would be useful I think the problems with cases where content in the target was removed and if it should be restored or not mean this is not suitable for speedy deletion. Otherwise I would have supported. Crouch, Swale (talk) 19:45, 15 March 2024 (UTC)Reply
  • Comment There is room for debate as to whether or not a page covers a particular topic. For example, African immigrants to Sweden lists several Swedish people of Ghanaian descent (Samuel Adjei, Kodjo Akolor, Patrick Amoah, Jeffrey Aubynn, ...) who might be of interest to a reader following the deleted redirect given as an example above. Certes (talk) 10:42, 17 March 2024 (UTC)Reply
  • What about redirects from alternative spellings or common misspellings? The former may not be present in the target and the latter should not be. I think there are enough cases that breach point 2 above that this would not be a good speedy deletion criterion. Another one that I've just thought of while writing this is where an AfD discussion closes as "merge". Often a well-meaning but rather lazy editor comes along and redirects the title without merging the content, potentially leaving the situation described here. The solution is to merge the relevant content, not to delete the redirect. Phil Bridger (talk) 11:13, 17 March 2024 (UTC)Reply
  • That seems more of a RfD issue than a speedy. Speedy is more for obvious issues, and it is possible to have a redirect that at one time had the relevant information that explains the redirect, but it no longer does. So it is a matter of either reinserting the info to make the redirect valid again, or concluding it never should have been created, which isn't a speedy decision, it is a discussion, hence RfD. The "damage" of keeping an irrelevant redirect for a week while it is discussed is minimal. Dennis Brown - 11:21, 17 March 2024 (UTC)Reply