Wikipedia talk:Criteria for speedy deletion

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.

This is an old revision of this page, as edited by Thryduulf (talk | contribs) at 18:46, 18 June 2019 (→‎Tightening G8 with respect to redirects: implemented). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.


Provide for CSD criterion X3: Mass-created portals

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.


WP:CD, and it has been requested that it stay open for at least 30 days. ~Swarm~ {talk} 05:14, 17 March 2019 (UTC)[reply
]


I am entering and numbering this proposal in order to get it into the record, but am requesting that action on it be deferred until the current round of MFDs are decided.

As per

Criteria for Speedy Deletion criterion X3, for portals created by User:The Transhumanist between April 2018 and March 2019. Tagging the portals for speedy deletion will provide the notice to users of the portals, if there are any users of the portals. I recommend that instructions to administrators include a request to wait 24 hours before deleting a portal. This is a compromise between the usual 1 to 4 hours for speedy deletion and 7 days for XFD. The availability of Twinkle for one-click tagging will make it easy to tag the pages, while notifying the users (if there are any). Robert McClenon (talk) 04:21, 3 March 2019 (UTC)[reply
]

This proposal should be posted in a wider venue, such as
WP:MFD. Many of those portals have been in place for months, making WP:AN too narrow a venue for them. CSD notices wouldn't be placed until after the discussion is over, and therefore would not serve to notify the users of those portals of the discussion. A notice to the discussion of this proposal, since it is a deletion discussion, should be placed on each of the portals, to allow their readers to participate in the discussion. The current round of MfDs are not a random sampling of the portals that were created, and therefore are not necessarily representative of the set. The portals themselves vary in many ways, including scope, the amount of time they've been accessed by readers, quality, number of features, picture support, volume of content, amount of work that went into them, number of editors who worked on them, length, readership, etc.    — The Transhumanist   07:09, 3 March 2019 (UTC)[reply
]
How would you suggest to get a representative sample? Legacypac (talk) 07:20, 3 March 2019 (UTC)[reply]
Thank you for asking. That would be difficult now, since there are already a bunch of portals nominated for MfD. If those were included, then the sample would already be skewed. I expect a truly random sample would reveal that some portals are worth keeping and others are not. A more important question would be "How would we find the portals worth keeping? Which is very similar to the question "what should the creation criteria for portals be?", the very thing they are discussing at the portal guidelines page right now. Many of these portals may qualify under the guideline that is finally arrived upon there. For example, they are discussing scope. There are portals of subjects that fall within Vital articles Level 2, 3, 4, and 5, and there are many portals of subjects of similar scope to the subjects at those levels. And many of the portals had extra work put into them, and who knows how many had contributions by other editors besides me. Another factor is, that the quality of the navigation templates the portals are powered by differs, and some of the portals are powered by other source types, such as lists. Some have hand-crafted lists, as there are multiple slideshow templates available, one of which accepts specific article names as parameters. Another way to do that is provide a manual list in the subtopics section and power the slideshow from that. Some of the portals are of a different design than the standard base template. Some are very well focused, contextually, while others are not. For example, some of the portals have multiple excerpt slideshows to provide additional context.    — The Transhumanist   07:46, 3 March 2019 (UTC)[reply]
  • Support in principle. Looking at the existing MFD discussions, TTH seems determined to drag and wikilawyer as much as possible to try to derail the discussions, even for blatantly and indefensibly inappropriate microportals like those discussed at
    Iridescent 08:26, 3 March 2019 (UTC)[reply
    ]
    Dreamy Jazz seems unlikely do that, having already decided during this debate to stop donating their time to Wikipedia. Certes (talk) 18:06, 3 March 2019 (UTC)[reply]
  • Comment – Another option would be to move these to draft space. The templates and lua modules could be modified so that the portals render right in that namespace (I wish I would have thought of this before). Being in draft space would give time to fix their various problems (keeping in mind that micro-scope is not fixable), and identify the ones worth keeping. I would agree not to move any of them personally, and would propose/request such moves after the new creation criteria guidelines for portals are settled upon. I would also be willing to tag those that did not meet those guidelines with CSD (as creator), saving Legacypac the trouble of nominating them at MfD (he mentioned somewhere that he thought I should help clean up this "mess"). Another benefit of this strategy is that if any of them sit in draft space too long without further development, they automatically become subject to deletion per the draft space guidelines, and those that reach that age without any edits can be deleted en masse without time-consuming effort-wasting MfD discussions. This course of action would of course need the participation of some lua programmers to add the necessary functionality to the modules, which would be a good upgrade for those, to allow for portal drafts to be created in the future.    — The Transhumanist   09:15, 3 March 2019 (UTC)[reply]
P.S. @
Iridescent and Legacypac: (pinging)    — The Transhumanist   09:28, 3 March 2019 (UTC)[reply
]
  • How is this the "only way" to be "sure"? What about actually viewing the portals themselves, as opposed to mass deleting them all sight unseen? North America1000 03:08, 26 March 2019 (UTC)[reply]
  • Could you provide any evidence that all of the portals are "broken"? Many of them that I have viewed and used are fully functional, and not broken at all. North America1000 03:09, 26 March 2019 (UTC)[reply]
Many editors at the Village Pump discussion, the Tban discussion above, and at MfDs also supported this. We do not need to fragment this discussion further. Legacypac (talk) 05:12, 4 March 2019 (UTC)[reply]
Proposal 1 will make this Proposal 4 moot. This Proposal 4 is not a proper CSD implementation. --SmokeyJoe (talk) 05:41, 4 March 2019 (UTC)[reply]
@SmokeyJoe: Proposal 1 is about stopping TTH from creating new portals. Proposal 4 is about deleting those he created in the last couple of months. How is P1 going to make P4 moot? —Kusma (t·c) 10:19, 4 March 2019 (UTC)[reply]
List them all in an MfD, if they must all be deleted. A CSD that enables self appointed decision makes for which should go and which might be ok, is inferior to MfD. MfD can handle a list of pages. —SmokeyJoe (talk) 11:24, 4 March 2019 (UTC)[reply]
If you want them all at MfD stop objecting to the listing of specific Portals at MfD. Legacypac (talk) 01:34, 11 March 2019 (UTC)[reply]
No. Some of the Portals I would support for deletion, and others definitely no. This makes the proposal for a CSD invalid. It fails the CSD new criterion criteria. The proposal is neither Objective or Uncontestable. It would pick up a lot of portals that should not be deleted. --SmokeyJoe (talk) 01:44, 11 March 2019 (UTC)[reply]
There is no new content in the automated portals, it's all poorly repackaged bits of existing content. Legacypac (talk) 04:40, 5 March 2019 (UTC)[reply]
All portals, old or new, good or bad, manual or automated, repackage existing content. That's their job. New content belongs in articles. Certes (talk) 11:20, 5 March 2019 (UTC)[reply]
  • Strong oppose per wumbolo below:
    necessary evil, and I don't think we should be hasty to add another criterion that skips our usual consensus process. I'm fine with nuking these portals and not opposed to deleting them, any diamonds in the rough will prove their worth by being created again, but I would prefer one big MfD with the rationale "created by The Transhumanist" which allows proper determination of consensus and gives those who want to spend their time triaging a chance to do so. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 08:03, 5 March 2019 (UTC)[reply
    ]
Building multipage MfDs like Wikipedia:Miscellany for deletion/Portals for Portland, Oregon neighborhoods is time consuming and tedious. A temporary CSD is rhe way to go. Consensus against this mess of new portals has already been established at VP, AN and in the test MfDs. Legacypac (talk) 17:20, 5 March 2019 (UTC)[reply]
  • Support due to the massive amount of time it would take to put the ~4500 portals through MfD. MfD has been swamped with portal deletion requests from some time ago, and I can't see all this stuff removed via MfD in the foreseeable future (as someone said earlier, there is still a lot of Outlines left over from one of TTH's previous projects, so who knows how long it would take for MfD to delete all of this). This CSD X3 would streamline the process, and it would probably only take a few days to a week. It would help, as also mentioned earlier, to extend the criterion to the other users involved in the mass creation of these portals. Rlin8 (··📧) 03:31, 6 March 2019 (UTC)[reply]
    • MfD has never had an issue to nominations of list of pages. 4500 separate MfD nominations would be absurd, but a list would be OK. If each is new, and has a single author, notifications of the author will be trivial. A CSD proposal shortcuts a discussion of the merits of the new portals, and pre-supposes deletion to be necessary, contrary to
      deletion policy. --SmokeyJoe (talk) 04:01, 6 March 2019 (UTC)[reply
      ]
TTH demands we place notification on every portal. We can skip notifying him, but building even 20 page MfD's is very time consuming. How do you propose to discuss 4500 or even 100 assorted portals at a time? These took 3 min to make - but far more than 3 min to list, tag, discuss and vote, then delete - when you add up all the time required from various editors and Admins. The test MfDs are sufficent and the very strong opposition to this automated portal project justifies this temporary CSD. Legacypac (talk) 04:16, 6 March 2019 (UTC)[reply]
"TTH demands we place notification on every portal"? Legacypac, I have missed that post by him. If he did that, it needs to be repudiated. If these are new pages, and he is the only author, it is sufficient to notify him once. If all 4500 are essentially variations on the same thing, as long as the full set is defined, and browsable, we can discuss them all together at MfD. --SmokeyJoe (talk) 05:34, 6 March 2019 (UTC)[reply]
User:SmokeyJoe during the Portland Oregon neighborhood MFD I specifically said I was not tagging all the related portals but he insisted I tag here [2] I could not get support in the section above to relax the MfD tagging because others wanted this CSD. During the Delete Portals RFC TTH went all out insisting every portal including the community portal be tagged for deletion - then he did it himself. That brought in all kinds of casual infrequent editors who were mostly against deleting the community portal. (Even though that was Pretty much pulled out of consideration for deletion before the tagging project). That massive tagging derailed the deletion RFC. By making cleanup as hard as possible TTH is making a lot of people want to nuke everything. Legacypac (talk) 06:11, 6 March 2019 (UTC)[reply]
Legacypac's analysis is erroneous and misleading. The
WP:ENDPORTALS RFC was a deletion discussion, and posting a notice on each page up for deletion is required by deletion policy. Note that the Community Portal was only mentioned twice. A portal that was the basis for about 50 oppose votes was the Current Events portal. Neither the Community Portal nor the Current Events portal were exempted in the proposal at any time. If you didn't count those, that left the count at about 150 in support of eliminating portals to about 250 against.    — The Transhumanist   07:25, 6 March 2019 (UTC)[reply
]
@SmokeyJoe: (edit conflict) See the top of this section for the referred to statement, which is not exactly as he quoted. A notice posted at the top of the portals slated by this proposal would be appropriate. Legacypac has been posting notice for his multi-page nominations using the {{mfd}} template, which auto-generates a link to an mfd page of the same title as the page the template is posted on. Rather than following the template's instructions for multiple pages, he's been creating an MfD page for each, and redirecting them to the combined mfd. Then a bot automatically notifies the creator of each page (me), swamping my user talk page with redundant notifications. Thus, Legacypac believes he'll have to create thousands of mfd redirect pages, and that I somehow want 3500+ notifications on my talk page.    — The Transhumanist   07:10, 6 March 2019 (UTC)[reply]
You want us to manually tag pages for deletion that you used an automated script to create? You flooded Wikipedia with useless pages in violation of
WP:MEATBOT but you are worried about having to clean up your talkpage notices? Just create an archiving system for your talkpage like we did for User:Neelix's talkpage. If you don't want notices you could start tagging pages that fail your own guidelines with "delete by author request" instead of commenting on how we will do the cleanup. Legacypac (talk) 08:37, 6 March 2019 (UTC)[reply
]
TTH, if you don't want so many deletion notices on your talk page, then remember in future not to create thousands of spam pages. Please help with the cleanup, rather than complaining about it.
@Legacypac: good work MFDing the spam, but it does seem that you are using a somewhat inefficient approach to tagging. Have you tried asking at WP:BOTREQ for help? In the right hands, tools such as AWB make fast work of XfD tagging. --BrownHairedGirl (talk) • (contribs) 12:21, 15 March 2019 (UTC)[reply]
  • Support whatever course of action that will result in every portal created in this manner being deleted with the minimal of time and effort required. TTH has set up his automated tool, created a massive mess, and left it unattended for others to sort out. It should take less time to clean up this mess than it did to make it, not more. Nuke the lot and if there is anything of value lost then TTH can manually request pages to be restored one at a time at DRV. Fish+Karate 11:19, 6 March 2019 (UTC)[reply]
  • Support per Fish and karate. RGloucester 14:20, 6 March 2019 (UTC)[reply]
  • Strong oppose as written. I could support something that explicitly excluded portals which are in use and/or are being developed, but the current proposal to indiscriminately delete everything, including active portals, unless the admin chooses to notify any editors and the ones notified happen to be online in a narrow time frame is significantly overly broad. Thryduulf (talk) 01:54, 7 March 2019 (UTC)[reply]
  • Support Not that portals are that bad, but I don't think we need portals on smaller subjects. (Portal:Spaghetti when we already have Portal:Pasta? Portal:Nick Jr., anyone?) Some might be worth keeping, but a lot are unneeded and unmaintainable. At least it's not a Neelix case. SemiHypercube 16:57, 8 March 2019 (UTC)[reply]
    • @SemiHypercube: "Some might be worth keeping" is actually an argument against this proposal. Thryduulf (talk) 12:08, 11 March 2019 (UTC)[reply]
      • @Thryduulf: Kind of, but that might be a reason not to just mass delete all at once. In the Neelix case there were some redirects that were actually useful, so a separate CSD criterion was used to keep some redirects at the admins' discretion, so this might be a similar case (before you say that contradicts my "it's not a Neelix case" statement, I meant that in terms of what the redirects were about) SemiHypercube 12:23, 11 March 2019 (UTC)[reply]
      • It violates points 1 and 2 of the requirements for CSD criteria: objectivity and unconestability. Unless all the portals covered should be speedily deleted then none of them should be. If you only want to delete some of them then you should be opposing this criterion (just like you should have opposed the subjective Neelix criterion). Thryduulf (talk) 12:34, 11 March 2019 (UTC)[reply]

*Support Only realistic way to deal with these. Johnbod (talk) 01:57, 11 March 2019 (UTC) Duplicate !vote struck. GoldenRing (talk) 10:16, 4 April 2019 (UTC)[reply]

  • Request the posting of a notice at the top of each of the pages being nominated here for mass deletion, as required by the Deletion Policy. This proposal is currently a gross violation of the deletion policy because it is a discussion to delete 3500+ pages, that have been created over the span of a year, that are presently being viewed hundreds of thousands of times per month (projected to millions of times over the coming year) by readers of Wikipedia. The proposal for mass deletion has been made without the required notice being posted at the top of the pages to be deleted. This is being decided by a handful of editors unbeknownst to the wider community, namely, the readership of the portals to be deleted. It may be that those reading such notices would decide that the portals should be deleted, but the point here is that you are denying them the opportunity to participate in the deletion discussion as required by the deletion policy.    — The Transhumanist   21:12, 11 March 2019 (UTC)[reply]
Request you stop wasting people's fucking time. Only in death does duty end (talk) 21:41, 11 March 2019 (UTC)[reply]
  • He switched back to Outlines Special:Contributions/The_Transhumanist which are another unpopular plague for Wikipedia. The assertion that hundreds of thousands of readers a month are looking at his 3500 portals is fanciful at best and not supported by readership stats. Legacypac (talk) 21:58, 11 March 2019 (UTC)[reply]
Support opposing anything TTH says from now on. Per OiD. ——SerialNumber54129 13:30, 12 March 2019 (UTC)[reply]
Strong oppose taking ad hominem arguments into consideration. Thryduulf (talk) 13:49, 12 March 2019 (UTC)[reply]
Oppose
WP:BLUDGEONING. ——SerialNumber54129 15:48, 18 March 2019 (UTC)[reply
]
Absolutely not. Look at the rate these were created [3] sometimes several dozen an hour, and sometimes an average of 12 seconds each. If so little thought went into creation, why make deletion so difficult? The Neelix cleanup took far too long (I was a big part of it) and we deleted the vast majority of those redirects anyway the extra hard way. As far as I could see the editors who insisted we review everything did none of the reviewing. Also, these were created in violation of
WP:MEATBOT which is a blockable or at least sanctionable offense Legacypac (talk) 11:04, 12 March 2019 (UTC)[reply
]
Two wrongs do not make a right - it is much more important that we get the cleanup right than it happens quickly. Whether or not TTH is blocked or otherwise sanctioned is completely irrelevant. While many (maybe even most) of the created portals should be deleted not all of them should be, and this needs human review: see requirement 2 for new CSD criteria at the top of
WT:CSD. Thryduulf (talk) 12:07, 12 March 2019 (UTC)[reply
]
@
WP:MEATBOT was not violated.    — The Transhumanist   18:55, 12 March 2019 (UTC)[reply
]
He claims [4] he created 500 portals in 500 to 1000 minutes. and is using a script Wikipedia:Miscellany_for_deletion#User:The_Transhumanist/QuickPortal.js If this is not MEATBOT we should refind MEATBOT as meaningless. Legacypac (talk) 19:07, 12 March 2019 (UTC)[reply]
A minute or two per portal of the new design sounds about right. Note that the script doesn't save pages. It puts them into preview mode, so that the editor can review them and work on them further before clicking on save.    — The Transhumanist   19:39, 12 March 2019 (UTC)[reply]
@
WP:MEATBOT don't affect this at all. What matters is only that these pages exist but some of them should not, this proposal needs to be rejected or modified such that it deletes only those that need deleting without also deleting those that do not. Thryduulf (talk) 20:42, 12 March 2019 (UTC)[reply
]
  • Procedural note I have advertised this discussion at
    WP:VPP and would encourage others to add links where they think interested editors might see. I think this should remain open for 30 days, as it is quite a significant policy change. GoldenRing (talk) 09:24, 13 March 2019 (UTC)[reply
    ]
  • Support now that the MfDs (here, here, here, here, here, here, here, here, here, here and here) are closing with strong consensus around delete, it is clear this is the fastest path to improving the encyclopedia (which is what we are here for, remember?) Any argument that 3,500 more portals have to go through MfD is strictly throwing sand in the gears. It is going to be enough manual labor pulling the links to the deleted portals from all the templates and pages they have been added to. UnitedStatesian (talk) 15:15, 13 March 2019 (UTC)[reply]
    • That shows that a speedy deletion criterion is possibly warranted for some, but several comments on those discussions - including your own at Wikipedia:Miscellany for deletion/Portal:Spaghetti - indicate that this proposed criterion is too broad. Thryduulf (talk) 15:33, 13 March 2019 (UTC)[reply]
      • You misunderstand my comment at that MfD: I strongly support that portal's deletion and all the others that would be covered by this proposed criterion. UnitedStatesian (talk) 15:37, 13 March 2019 (UTC)[reply]
        • You supported the deletion of Portal:Spaghetti because the topic was covered by Portal:Pasta, even though Portal:Pasta would be deleted under this criterion? That's rather disingenuous at best and very significantly and unnecessary disruptive at worst. Portal:Pasta is an example of a portal that should not be deleted without discussion. Thryduulf (talk) 16:00, 13 March 2019 (UTC)[reply]
          • Again, you misunderstand my reasoning: I was specifically pointing out to another editor that the existence of Portal:Pasta could NOT be a reason to delete Portal:Spaghetti, since in my opinion Portal:Pasta would likely also be deleted. Instead, I think the current Wikipedia:Portal/Guidelines provide ample OTHER reasons for deleting both portals (and many, many others, of course). Hope that clarifies. UnitedStatesian (talk) 17:55, 13 March 2019 (UTC)[reply]
  • Strong oppose and keep all.
    WP:IDLI to delete a large proportion of all of them, which were all kept after a RfC in 2018. The next time content policies are created at AN by the cabal of admins, I am retiring from Wikipedia. wumbolo ^^^ 16:40, 13 March 2019 (UTC)[reply
    ]
    @
    WP:CENT). I'm skeptical any alleged consensus is going to come out of this discussion, anyway.  — SMcCandlish ¢ 😼  17:33, 14 March 2019 (UTC)[reply
    ]
  • Support This is a repeat of the Neelix situation. ―Susmuffin Talk 00:01, 14 March 2019 (UTC)[reply]
    • @Susmuffin: The situation has similarities, but the proposed criterion is not comparable. Criterion X1 applied only to redirects created by Neelix that the reviewing administrator reasonably believed would be snow deleted if discussed at RfD (i.e. they had to evaluate each redirect), this criterion would apply to every portal created by TTH in the timeframe without any other conditions and without the need for anyone to even look at anything other than the date of creation. Thryduulf (talk) 00:13, 14 March 2019 (UTC)[reply]
      • Honestly, there are far too many portals to be deleted through the usual channels. However, an quick evaluation would be reasonable, provided we keep the portal system itself. ―Susmuffin Talk 00:24, 14 March 2019 (UTC)[reply]
Unlike Neelix who created some reasonable redirects along the way, these autogenerated portals are of uniformly low quality. The community has looked at representive samples across a variety of subject areas at MFD and the community has already deleted 143 of the 143 portals nominated at closed MfDs. The yet to be closed MfDs are headed to increasing that number. No one has suggested any alternative deletion criteria for X3. Legacypac (talk) 00:45, 14 March 2019 (UTC)[reply]
That nobody has suggested an alternative is irrelevant - it's not up to those who oppose this proposal to fix it, and those who support it are by-and-large ignoring the objections. The MfDs have been selected as a representative sample of those that, after review, are not worth keeping and have been reviewed by MfD participants. This does not demonstrate that deletion without review is appropriate - indeed quite the opposite. Remember there is no deadline, it is significantly more important that we get it right than we do things quickly. Thryduulf (talk) 09:59, 14 March 2019 (UTC)[reply]
Not particularly similar to the redirect situation that occurred; portals are vastly different in nature and composition from simple redirects. North America1000 03:16, 26 March 2019 (UTC)[reply]
  • Oppose as unwarranted and dangerous (and circular reasoning). First, we do not modify CSD without a strong community (not admins' star chamber) consensus that an entire class of material is not just categorically unwanted but so unwanted that it should be deleted on sight without any further consideration. It's our most dangerous policy, and a change like this to it should be an RfC matter at
    WT:CSD, except there is not yet any establishment of a consensus against these portals, and VPPOL is where that would get hashed out, since it's a project-wide question of content presentation and navigation (and maintenance, and whether tools can permissibly substitute for some manual maintenance, and ...). The cart is ahead of the horse here; we can't have a speedy deletion criterion without already having a deletion criterion to begin with. I strongly agree with SmokeyJoe: "Oppose any and all notions of creating new CSD criteria at any drama board. Discussions here are too rushed, too emotive, too reactionary."  — SMcCandlish ¢ 😼  17:05, 14 March 2019 (UTC)[reply
    ]
  • Oppose
    WP:P2 covers problematic portals just fine. A concerning issue here is that some users herein appear to simply not like portals in general, and so there are several arguments above for mass deletion as per this "I don't like it" rationale. Mass deletion should be a last step, not a first step, and portals should be considered on a case-by-case basis. North America1000 22:22, 14 March 2019 (UTC)[reply
    ]
You created some with the same tools. One or two of your creations are now at MfD which is why you are now engaging against this solution. We will consider each of your creations at MfD. Legacypac (talk) 02:34, 15 March 2019 (UTC)[reply]
My !vote here is based upon my view of the matter at hand, and as such, it stands. Period. Regarding my portal creations, so what? You come across as having a penchant for scolding content creators on Wikipedia if you don't like the medium that is used. Please consider refraining from doing so, as it is unnecessary, and patronizing. North America1000 01:12, 16 March 2019 (UTC)[reply]
This CSD exactly meets each criteria for CSD's at the
WP:CSD page. It is clear. It is easy to decide if the page meets the CSD. We ran 145 of these portals through MfD already and none survived. Numerous editors suggested this CSD in the Village Pump discussion. These mass created portals universally have the same flaws. Therefore this oppose rational is flawed. Legacypac (talk) 02:34, 15 March 2019 (UTC)[reply
]
If the Portals Project had exercised discretion so far, then we would be in a very different place. But it's utterly outraegous to ask the community to devote more time to assessing this spam than the Portal Project put into creating them. --BrownHairedGirl (talk) • (contribs) 12:10, 15 March 2019 (UTC)[reply]
Could these portals be marked to be spared?Guilherme Burn (talk) 13:03, 15 March 2019 (UTC)[reply]
@Guilherme Burn: not according to the proposal as written. The only chance of saving is if an admin chooses to notify and wait 24 hours and somebody objects within those 24 hours and someone spots that CSD has been declined previously if it gets renominated. Thryduulf (talk) 14:01, 15 March 2019 (UTC)[reply]
@
Iridescent 14:08, 15 March 2019 (UTC)[reply
]
@
Iridescent and BrownHairedGirl:One portal that does not meet Mfd criteria is enough for me to keep my opinion. Portal:Cities Although poor visualized is an important and good quality portal and the Portal:Sculpture (erroneously I quoted another portal) as well.Guilherme Burn (talk) 13:20, 20 March 2019 (UTC)[reply
]
@Guilherme Burn: please can you clarify that statement that One portal that does not meet Mfd criteria is enough for me to keep.
Are you saying that you are willing to personally scrutinise a few thousand drive-by Portals at MfD in order to find the one which should be kept? Or do you want others to do that work?
TTH as made it very clear that these portals took on average between one and two minutes each to create ([5] Have you tried creating 500 portals? It is rather repetitious/tedious/time-consuming (from 500 to 1000 minutes)). So many multiples of that-one-to-two minutes per portal do you think it is fair to ask the community to spend scrutinisng them? And how much of that time are you prepared to give? --BrownHairedGirl (talk) • (contribs) 14:12, 20 March 2019 (UTC)[reply]
So many multiples of that-one-to-two minutes per portal do you think it is fair to ask the community to spend scrutinisng them?Yes. The community also failed to set criteria for creating portals. What is the difference of Portal: Lady Gaga to Portal: ABBA? For me both should be excluded. If the community not had problems to create a portal for a unique singer, why now have problems with someone who has decided to create portals for lot of singers? And to be honest I do not think so much work like that, Mfd can be executed in blocks excluding several portals at the same time.Guilherme Burn (talk) 17:11, 20 March 2019 (UTC)[reply]
  • Oppose per SmokeyJoe et al. Completely unnecessary to override already existing procedure. Paine Ellsworth, ed.  put'r there  17:12, 15 March 2019 (UTC)[reply]
    • @Paine Ellsworth: the administrative work of trawling through several thousand drive-by-created micro-portals is huge. Cleaning up this flood of portalspam through MFD requires a huge amount of editorial time, vastly more than was involved in creating the spam.
If you think that existing procedure is fine, why aren't you devoting large hunks of your time to doing the cleanup by the laborious procedure you defend? --BrownHairedGirl (talk) • (contribs) 02:33, 16 March 2019 (UTC)[reply]
  • Because...? I don't know, I guess I think this whole thing is rather more of a knee-jerk reaction than a brainy, measured response. Sure I've done my share of big, teejus jobs for the project and plan to continue (on my terms). I have a lot of respect for editors like yourself and TTH who've been lifting this project out of the primal soup of its beginnings even longer than I have (I went over ten in January, or was it Feb? whatever) and I'm tired of seeing good, solid editors get reamed for their work and retire, just leave or get banned. Don't think it can't happen to you, because as good as you are, neither you nor the rest of us are immune to the gang-up-on-em mentality that turns justice into vengeance 'round here. Think you should also know if you don't already that I'm about 95 farts Wikignome and 5 parts other, and it takes a lot less for us to think we're being badgered and handled. I voted correctly for me and my perceptions, and I don't expect either of us will change this unwise world one iota if you vote you and yours! WTF ever happened to forgiveness? REspectfully, Paine Ellsworth, ed.  put'r there  13:28, 16 March 2019 (UTC)[reply]
  • @Paine Ellsworth: Thank you for adding the words that I dared not write in case I was next against the wall. Certes (talk) 16:31, 16 March 2019 (UTC)[reply]
But it seems to me that the unintended effect of what you are both saying is something like "I am not making any effort to assist the cleanup of this mass portalspam, but I will take the effort to oppose measures which reduce the huge burden on those who are actually doing that necessary cleanup work".
As I say, I do not believe that is what either of you intend. But all I see from either of you is opposition to any restraint on the portalspammer, and opposition to anything which would assist the cleanup. I respect the fine principles from which you two start, but I urge you to consider the effects on the community both of not easing the cleanup burden and of continuing to describe the likes of TTH in positive terms. Look for example at my post in a thread above about the #Lack_of_good_faith_from_User:The_Transhumanist, and at Iridiscent's observation above that of TTH's previous history of spamming useless pages.
As to lifting this project out of the primal soup of its beginnings ... that's an extraordinary way to describe TTH's spamming of hundreds, if not thousands, of useless, unfinished micro-portals. --BrownHairedGirl (talk) • (contribs) 22:53, 16 March 2019 (UTC)[reply]
I am not making any effort to assist with mass deletions, beyond !voting to delete the clearer cases. We already have enough enthusiasts working in that department. Until recently, I had been adjusting individual portals and enhancing the modules behind them to improve quality, but I slowed down when it became obvious that my contributions in that area will be deleted. Certes (talk) 00:19, 17 March 2019 (UTC)[reply]
So that's as I feared, @Certes: members of that WikiProject are leaving it to others to clean up the mess created by the WikiProject and its members.
That only reinforces my impression of a collectively irresponsible project, which doesn't restrain or even actively discourage portalspam, doesn't try to identify it, and doesn't assist in its cleanup.
That's a marked contrast with well-run projects. --BrownHairedGirl (talk) • (contribs) 02:06, 17 March 2019 (UTC)[reply]
To editor BHG: not a surprising perspective, possibly a hasty generalization, however that's not your worst move. Your worst move is to consider "mass deletions" of what you deem "portalspam" as better than the "mass creations" of portals. Who's really to say? As an editor mentions below, "...these portals are doing no harm so great that they can be deleted without due process." So maybe you're wrong about those mass deletions that portray some portals as WMDs instead of the harmless windows into Wikipedia that they were meant to be? No matter, at present you are part of the strong throng. If you're right, you're right. But what if you and the strong throng are wrong? May things continue to go well with you! Paine Ellsworth, ed.  put'r there  07:01, 17 March 2019 (UTC)[reply]
  • Support and also apply it to those created by Northamerica1000, who has made such useless portals as Portal:Strawberries and Portal:Waffles. Reywas92Talk 08:26, 16 March 2019 (UTC)[reply]
    • @Reywas92: Northamerica1000 has created only 70 pages in the portal namespace (excluding redirects) in the relevant timeperiod. In no conceivable scenario does that justify a speedy deletion criterion. Thryduulf (talk) 11:58, 16 March 2019 (UTC)[reply]
  • Support per F&K (whatever course of action that will result in every portal created in this manner being deleted with the minimal of time and effort required) and SN (nuke from orbit). I'll be honest I don't know enough to know whether it should be a X3 or a P2 or a single MfD list with 4,500 entries... but it should not need to involve manually tagging pages that were created by a bot or otherwise spending any real time figuring out which should be kept and which should not be kept. Delete them all. If editors feel like this portal or that portal should be kept, let them make the case for undeletion afterwards which can be examined on a case-by-case basis. (If that process is followed, it goes without saying that the portal creator should be banned from making any such undeletion requests.) Levivich 17:25, 16 March 2019 (UTC)[reply]
    How are we supposed to work out what is worth undeleting, short of downloading all portals in advance lest they be deleted? Certes (talk)
    If an editor is not aware of a portal existing, then that editor shouldn't be asking for it to be kept. If there are particular portals that editors know they want saved, then they should have an opportunity to request that it be saved. But there should be no one-by-one examination of thousands and thousands of portals created by one user using semi-automatic methods. Levivich 19:39, 16 March 2019 (UTC)[reply]
    Kill them all and let God sort them out is very much not the way Wikipedia works and is very much not the way it should work. Why should the review be restricted to administrators (as your proposal would require)? Why is it preferable to significantly harm the encyclopaedia by deleting good portals than to do the job properly and delete only those that actually need deleting (which are doing significantly less harm by existing than deleting good ones would cause)? Thryduulf (talk) 18:06, 16 March 2019 (UTC)[reply]
    So let me create several thousand pages semi-automatically, and then I'll put it to you to go through them one by one and tell me which should be deleted and why? I don't think that's how it should work. It should work in reverse. The default should be delete them all, with some process for allowing people to request that particular portals not be deleted. BTW, when I say "all portals" I mean all portals covered by this proposal, not all portals that exist on Wikipedia. Levivich 19:39, 16 March 2019 (UTC)[reply]
    If an editor created several thousand pages semi-automatically, the correct sequence of events is to analyse a representative sample to determine whether consensus is that they are (a) all good, (b) mostly good, (c) all bad, (d) mostly bad, or (e) a mixture. If (a) then no action is necessary, if (b) then individual deletion nominations are the correct response. If (c) then a CSD criterion to remove all of them is appropriate, if (d) or (e) then a CSD affectingly only the bad ones should be explored. In this the situation is somewhere between (d) and (e) depending on your point of view, but this proposal is treating them as (c). As I've said several times, I'm not opposed to a criterion proposed (in the right place) that caught only the bad ones and allowed for objections - that is not this proposal. This situation is frequently compared to Neelix, but the proposal is very different - this one: All pages created between Time A and Time B, unless anyone objects to the optional tagging within 24 hours. Neelix: All pages created between Time A and Time B that would be snow deleted if nominated at RfD, retargetting would not lead to a useful redirect and no other editor has materially edited the redirect. Do you now understand the fundamental difference? Also remember that pages can be tagged by bot. Thryduulf (talk) 20:56, 16 March 2019 (UTC)[reply]
    Yes. We also need to clarify one important detail of the proposal: would an editor be required to look at the portal before applying CSD, or is there an assumption that everything created by this editor in that time period is automatically rubbish and does not deserve assessment? Certes (talk) 22:29, 16 March 2019 (UTC)[reply]
    If a human being didn't spend a lot of time making a page, then human beings should not spend much time deciding whether to keep it. I put it to you again: suppose tomorrow I create 5,000 new pages and ask you to go through them and decide which to keep and which to delete. That would be insane; this is a website of volunteers; my doing such a thing would be disruptive. It would make work for others. Nobody reading this thinks it would be a good idea for me to do such a thing. Yet this is what is essentially being asked of us. Insofar as I have a !vote, I !vote no. Delete them all. They are all bad. Any that are good can be recreated as easily as they were created in the first place. Letting people flag keepers in one way or another is a perfectly reasonable way to prevent the baby from being thrown out with the bathwater. But yes, my starting point is that all of them should be deleted because none of them should have been made in the first place, and they do not have content value. Some portals are the product of careful creation and extensive work, but not 5,000 or however-many automatically created by one editor. The quantum portal idea is a much better idea, anyway. Levivich 02:38, 17 March 2019 (UTC)[reply]
    I've alreadyanswered this immediately above, but as you apparently don't like the answer I'll respond again. If you create 5000 new pages in good faith (which TTH did), then the correct response is for others to go through and look at a representative sample, then gain a consensus about whether they are all bad, mostly bad, a mixture, mostly good or all good. This has been done with TTH's portals and while you may think they are all bad that is not the consensus view, especially as others have taken over some and either have improved them or are working on improving them. This means that it is important that only the bad ones are deleted meaning any proposal (such as this one) to delete all of them is overbroad and needs to be opposed. Thryduulf (talk) 10:03, 17 March 2019 (UTC)[reply]
    This statement by Thryduulf is incorrect on many levels. Who has taken over and improved any of his creations? Where is the concensus view that they are not all bad when so far zero of his creations have been kept at MfDs. Where is the proof any of this was in good faith when he admits several sections down that no one (including him) has followed
    WP:POG Legacypac (talk) 10:38, 17 March 2019 (UTC)[reply
    ]
    Are you even reading the comments made by those who disagree with you because I'm not seeing evidence of it, especially when it comes to the MfDs (to reiterate, a reviewed selection of the worst pages being deleted by consensus but not unanimously in all cases does not provide evidence of the need for deletion of all of them without possibility of review). Thryduulf (talk) 16:36, 17 March 2019 (UTC)[reply]
    Thryduulf, so I spend less than 1 minute per page creating 5,000 pages; you and others spend–what, an hour, cumulatively, at least?–per page to analyze it, discuss it, vote it, close it, and delete it. I spend 5,000 minutes; the community spends 5,000 hours. With all due respect I am flabbergasted to hear such a high-ranked Wikipedian express the view that this is OK or preferred. Even with your representative sample approach, say it's 100 portals that are looked at, that's still 100 hours of labor forced upon volunteers. In my opinion, no one should be allowed to make 5,000 pages without going through something like a BAG process to seek community approval. There was once a time, years ago, when it made sense to, for example, automatically create a stub for every known city and town in the world. I believe that time has long since passed; there are not 5,000 pages that can be created automatically that we need to have that we do not already have (IMO). And as for consensus, if they're not being kept at MfD, the consensus is clear. Those portals that people maintain manually are the same ones that can be flagged as exceptions to a mass-deletion. So I feel like we're on the same page about consensus, but I'm saying the consensus to keep a particular portal can be effectuated by allowing people to flag them as exceptions to mass deletion, whereas you seem to be suggesting: let's get together and spend an hour per portal to decide if it should be kept, even though nobody spent anywhere near that time creating it in the first place. If that's where we are, we'll have to agree to disagree, because I fundamentally don't believe these portals are worth a one-by-one analysis, and I believe the representative sample approach you advocate has been done and has led to the conclusion that these are worth mass deleting with exceptions. I guess that's for a closer to make the ultimate decision about, but for my part, from uninvolved editors, I'm seeing a lot more support than oppose for mass deletion. Levivich 14:42, 17 March 2019 (UTC)[reply]
    @
    WP:VOLUNTEER, nobody is being forced to do anything they don't want to do - including you - and it's really disappointing that someone as experienced as you feels the need to prevent that work being done by others just because you don't want to. Perhaps between now and the time this is closed those in support of this overbroad proposal will actually choose to address the points in opposition but unless they do the only possible outcomes are no consensus or consensus against. Thryduulf (talk) 16:36, 17 March 2019 (UTC)[reply
    ]
    Thryduulf, I heard you say: pick a representative sample and decide if they're all bad, some bad, etc. As I understand it, a representative sample has been sent to MfD with consensus to delete almost all of them, if not all of them (I'm not sure if lists I've seen are complete). Then you say that just because the sample is all-delete doesn't mean the whole category is all-delete. I infer you think the sample is not well-chosen? By TTH's admission there are like 4,500–5,000 portals, and a tiny tiny percentage of those are being manually maintained–like less than 5%. Are we on the same page about the facts so far? If so, where do you see consensus other than "delete 95% of these things"? Why can't we tag the 100 that are manually maintained and delete the remaining 4,500? I am reading what you're writing, but I am not understanding it. Levivich 16:44, 17 March 2019 (UTC)[reply]
  • Support: these portals are easy to create semi-automatedly and contain no information not found in articles so we're not losing any information from Wikipedia, which sets this apart from most other CSD criteria. An alternative proposal I would support is to expand the remit of P2 to apply to any portals with fewer than one-hundred pages under their scope (or alternatively, fewer than one-hundred notable topics if there is evidence that the portal creators and users are planning to create such topics as articles). If a topic doesn't have 100 pages on it at the bare minimum, there's absolutely no reason to focus a portal around it. Even for portals covering tens of thousands of articles, reader interest is very, very low and the current semi-automated busywork is not serving the readers. Bilorv (he/him) (talk) 19:05, 16 March 2019 (UTC)[reply]
    • @Biorv: a proposal for expansion of speedy deletion criterion P2 is being discussed currently at [[Wikipedia talk:Criteria for speedy deletion}} (which is where proposals related to speedy deletion criteria should be held, not AN), so I will refrain from explaining here why I oppose your suggestion to avoid splitting the discussion. Thryduulf (talk)
  • Support with exceptions. I support the speedy deletion of all portals auto-created in recent months as it seems excessive and unnecessary. However, those few portals which are manually maintained in good faith should be kept. Down the line we need to take another look at a notability threshold to keep a lid on portalmania. Bermicourt (talk) 22:37, 16 March 2019 (UTC)[reply]
    • If you believe there should be exceptions for portals maintained in good faith (and I agree there should be), then you should be opposing this proposal in favour of an alternative one that allows for that. Thryduulf (talk) 22:59, 16 March 2019 (UTC)[reply]
    X3 only covers the mass created automated portals started by TTH so already excludes the type of portal User:Bermicourt wants to exclude. Thryduulf is muddying the facts. Legacypac (talk) 23:08, 16 March 2019 (UTC)[reply]
  • Oppose because a) on procedural grounds this shouldn't be discussed at the AN "closed shop" and b) because these portals are doing no harm so great that they can be deleted without due process. It is not TTH's fault that the guidelines for portal creation are permissive. Triptothecottage (talk) 02:56, 17 March 2019 (UTC)[reply]
  • Comment: I have already voted here but I just wanted to provide an example of how much thought was going into the creation of these portals. Portal:Aquatic ecosystem was created by TTH on Aug 15 2018 and in classified as "Complete" despite having 4 selected images. An identical portal was created at Portal:Aquatic ecosystems by TTH on Nov 24 and is classified as "Substantial" (the portalspace equivalent of B-class). One wonders, which portal is of better quality, how was this determined, and how was this oversight not caught? — pythoncoder  (talk | contribs) 13:33, 17 March 2019 (UTC)[reply]
  • Oppose: Criteria are supposed to be uncontestable - almost all pages could be deleted under this criterion, according to consensus. Looking at the most recent 50 portals created by TTH, I see a lot of frivolous ones, but I also see
    WP:G4. But the pages considered here were created before the ban, so they should stand or fall on their own merits. RockMagnetist(talk) 06:05, 18 March 2019 (UTC)[reply
    ]
  • Oppose I have gone over many of the portals. It seems that there are a mix of topics which are mainstream and some which should not have been created. This isn't a white or a black issue, the wheat must be carefully separated from the chaff. << FR (mobileUndo) 12:04, 18 March 2019 (UTC) !vote from sockpuppet struck. GoldenRing (talk) 10:17, 4 April 2019 (UTC)[reply]
  • FR, is there some issue with deleting them without prejudice to re-creating existing ones? These were basically made by a bot in what amounts to a single spasm, so deleting them all could be seen as a BRD reversion. The next step would be to let uninvolved editors recreate any worth keeping. Yes, that might take a while. There is no deadline and if some potentially useful portals have gone uncreated up til now, it's fine if they stay absent a little longer. 173.228.123.166 (talk) 04:07, 19 March 2019 (UTC)[reply]

Arbitrary break (CSD criterion X3)

have you looked at all the shit that sits in the mainspace (some of it for years)? There are like 182,000 unreferenced articles live right now, but this is the hill we're choosing to die on? Crazynas t 21:57, 21 March 2019 (UTC)[reply]
Large in-line image
Typical example of the kind of portals spammed across enwiki. Not just the five errors, but also the actual "text" of the lead article...
Typical example of the kind of portals spammed across enwiki. Not just the five errors, but also the actual "text" of the lead article...
Thank you for identifying a problem with a small number of Philippines portals where the lead contains {{PH wikidata}}, a technique designed for use in infoboxes. I'll pass your helpful comments on to the relevant WikiProject. Certes (talk) 11:02, 21 March 2019 (UTC)[reply]
No, please pass my comment on to all people supporting these portals, but not bothering to actually look at what they propose or defend. Creating and supporting pages with such blatant problems is basically the same as vandalism. There are e.g. also quite a few portals which confront their readers with the below "selected article" (as the default selected article, not even when scrolling deeper). Or with the same image two or three times. Or... The list of problems with these portals is near endless (selected categories only consisting of one redlink? Sure...). The fact that adding a category can cause a page to look completely different and generate different errors (like in the example above) should be a major indicator that this system, used on thousands of pages, is not as foolproof and low in maintenance as is being claimed.
Fram (talk) 11:36, 21 March 2019 (UTC)[reply
]
Large in-line image
Read more... and weep
Read more... and weep
Thank you for your continued help in identifying portal issues. I have found and fixed three pages which had repeated "Read more" links. If you could be kind enough to reveal which portal you have depicted as "PortalShit2.png", we may also be able to fix that case and any similar ones. Certes (talk) 12:20, 21 March 2019 (UTC)[reply]
There are two very simple solutions: either support X3, and all these portals are instantly fixed. Or actually take a look at all these low maintenance, automatic portals of the future, find the many issues, and fix them. Which still won't solve the problem that many of them are utterly pointless, mindless creations of course. I've noted more than enough problems with these portals to wholeheartedly support speedy deletion, since spending any time "corecting" a portal like the Calamba one is a waste of time (as it should be deleted anyway, speedy or not).
Fram (talk) 12:42, 21 March 2019 (UTC)[reply
]
@
Fram: You are clearly not understanding the opposition to this proposal. It is not about supporting the inclusion of poor content, it is about opposing a speedy deletion criterion that fails the criteria for new and expanded criteria and would delete content that should not be deleted in addition to content that should. Thryduulf (talk) 13:41, 21 March 2019 (UTC)[reply
]
No, I often have trouyble understanding burocratic opposition which creates tons of extra work for very little actual benefit. Furthermore, I'm not convinced that this actually fails the four criteria: it is objective and nonredundant (I guess we all agree on these two?), it is frequent (in the sense that having 3K portals at MfD is quite a heavy load, it's not just one or two pages), so we are left with "Uncontestable", which doesn't mean that as soon ass someone opposes it, it becomes contested, but that "almost all pages that could be deleted using the rule, should be deleted, according to consensus.". Looking at this discussion and the MfDs, I believe this to be true. Opposing this new CSD rule "because it is contested" is circular reasoning, as you are then basically saying "it is contested because it is contested", which is obviously not a valid argument. Having a significant number of portals which fall under the X3 but should not be deleted (which doesn't equal "should never exist", only "should not exist in the current form or any older form in the page history") would be a good argument, but I haven't seen any indication of such.
Fram (talk) 13:57, 21 March 2019 (UTC)[reply
]
(
WT:CSD) is objective as written (created by a single user within a defined time period). Uncontestable however very much is, the requirement is "It must be the case that almost all pages that could be deleted using the rule, should be deleted, according to consensus. CSD criteria should cover only situations where there is a strong precedent for deletion. Remember that a rule may be used in a way you don't expect, unless you word it carefully." It is very clear from this discussion and others around these portals that not all of them should be deleted - several have received strong objections to deletion at MfD, some are argued to be kept and others merged. "it is contested because it is contested" is exactly the point of this requirement - nobody argues in good faith against deleting copyright violations, patent nonsense, recreations, or specific types of articles that don't assert importance. There is consensus that were these to be discussed they would be unanimously deleted every time. There is no such consensus about these portals. Some, perhaps most, should be deleted but not all of them. Thryduulf (talk) 15:47, 21 March 2019 (UTC)[reply
]
I am pleased to report that a recent module change should eliminate the problem where articles too short to be worth featuring occasionally appear as "Read more... Read more...". This should fix the mystery portal depicted above next time it is purged. Certes (talk) 11:26, 22 March 2019 (UTC)[reply]
WP:POG. Seriously makes me doubt your competence and judgement. Admins should show better judgement then this. Legacypac (talk) 17:12, 21 March 2019 (UTC)[reply
]
@Legacypac: Assuming you mean X3, then I have explained every single one of my reasons several times and you have either not listened or not understood on every single one of those occasions so I Will not waste even more of my time explaining them again. Thryduulf (talk) 17:16, 21 March 2019 (UTC)[reply]
Second Legacypac. Additionally, part of what I meant by "some might be worth keeping" is that they can be deleted, but if any were actually worthy they could be recreated, perhaps with more care and effort than this. SemiHypercube 17:19, 21 March 2019 (UTC)[reply]
  • It seems like a lot of what is objected to can be covered by a judicious use of P2, G1, and A3 (via P1) but there's probably something I'm missing. @
    Fram:, I'm not here to support bad content, but bad policy (and precedent) can be far more harmful to the project than 'repackaged nonsense' existing for a bit longer than some people want it to. This would have the side effect of saving the portals worth saving. Crazynas t 22:07, 21 March 2019 (UTC)[reply
    ]
Please identify 35 out of the 3500 (1%) that are "very good portals" so we can run them through MFD to test your statement. Also there is no baby - there is no original content at all. No work done by humans is lost with X3 deletions because they were created using an automated script that was used without BAG approval to repackage existing content. Therefore
WP:PRESERVE is not an issue. If someone started creating thousands of articles called "Foo lite" that just copied Foo mindlessly we would CSD them without debate. These are just in another mainspace but they are really Foo lite. Legacypac (talk) 17:12, 21 March 2019 (UTC)[reply
]
Except that's not comparable at all. The point of portals (which the community has repeatedly endorsed) is to duplicate article content and provide links to related content - which is exactly what these portals are doing. They might be doing it poorly in many cases, but that's qualitatively different to one article duplicating another. Thryduulf (talk) 18:10, 21 March 2019 (UTC)[reply]
Wouldn't it be faster to delete them all and then recreate the ones that need recreating, rather than go through them one by one to see which to keep? Because the number of "keeps" is like 5% or 10% and not 50%? (It would have to be 50% to be equal time between the two approaches.) If you're not convinced that it's 5-10% keep and not 50% keep, what sort of representative sampling process can we engage in to test the theory? Levivich 19:13, 21 March 2019 (UTC)[reply]
Yes it would be faster, but
there is no deadline so it is very significantly more important to get it right than it is to do it quickly. Deleting something that doesn't need deleting is one of the most harmful things that an administrator can do - and speedily deleting it is an order of magnitude more so. As only administrators can see pages once they have been deleted, and doing so is much harder, deleting it first makes the job of finding the good portals very significantly harder. Thryduulf (talk) 21:30, 21 March 2019 (UTC)[reply
]
Timing matters because this issue is being discussed in several forums at once. If the first debate to close decides to delete, the portals may be gone by the time another discussion reaches a consensus to keep them. Certes (talk) 21:48, 21 March 2019 (UTC)[reply]
  • CommentI listed The Transhumanist's portal creations, latest first, and examined the top entry on each page, i.e. every 100th portal.
Assessment of a sample of TTH's recent creations
  1. Portal:Polar exploration – decent appearance; no obvious errors. 50 excerpts with more links at the bottom. Four other images, plus plenty more in the 50 leads. Manual input: refining the search criteria for Did You Know and In the News (DYK+ITN).
  2. Portal:Nick Jr. – Lua error: No images found. (To be fair, there may have been images before a recently requested module change to suppress images without captions.) 13 excerpts. No manual input: the wikitext matches that generated by {{bpsp6}}.
  3. Portal:Alternative metal – decent appearance; no obvious errors but a narrow scope. 11 excerpts; one other image. Manual input: refining DYK+ITN.
  4. Portal:Modulation – decent but minimal portal with no obvious errors. 30 excerpts; four other images. Several manual improvements.
  5. Portal:Spanish Civil War – potentially good portal but with a couple of display errors which look fixable. 30 excerpts; 20 other images. Manual input: routine maintenance, probably of a routine technical nature rather than creative.
  6. Portal:Carl Jung – decent appearance; no obvious errors. 40+ excerpts; six other images. Routine maintenance.
  7. Portal:Reba McEntire – decent appearance; no obvious errors but a narrow scope. 40+ other excerpts; six images. Routine maintenance.
  8. Portal:Romantic music – decent appearance; no obvious errors. 40+ excerpts; two other images. Routine maintenance.
  9. Portal:Anton Chekhov – decent appearance; no obvious errors. 36 excerpts; 17 other images. Routine maintenance.
  10. Portal:Media manipulation – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; no image section. Routine maintenance.
  11. Portal:Desalination – decent appearance; no obvious errors but a narrow scope. 15 excerpts; six other images. Manual input: refining DYK+ITN.
  12. Portal:Abuse – This portal has display errors which make it hard to evaluate properly. It's had plenty of manual input, possibly in attempts to fix it.
  13. Portal:Emmy Awards – decent appearance; one minor display error which looks fixable.(fixed) 50 excerpts; two other images. Routine maintenance.
  14. Portal:Shanghai cuisine – decent appearance; no obvious errors but a narrow scope. 19 excerpts; four other images. Routine maintenance.
  15. Portal:Saab Automobile – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 14 other images. Routine maintenance.
  16. Portal:High-speed rail – decent appearance; one minor display error which looks fixable.(fixed) 40+ excerpts; 30+ other images. Routine maintenance.
  17. Portal:Tetris – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; two other images. Routine maintenance.
  18. Portal:Azores – decent appearance; no obvious errors but a narrow scope. 20 excerpts; 18 other images. Some manual improvements.
  19. Portal:Musical instruments – decent appearance; no obvious errors. 40+ excerpts; 13 other images. Routine maintenance.
  20. Portal:Hidalgo (state) – decent appearance; no obvious errors but a narrow scope. 11 excerpts; 16 other images. Routine maintenance.
  21. Portal:Sporting Kansas City – decent appearance; one minor display error which looks fixable;(fixed) narrow scope. 11 excerpts; 7 other images. Routine maintenance.
  22. Portal:Piciformes – decent appearance; no obvious errors but a narrow scope. 9 excerpts; one other image. Routine maintenance.
  23. Portal:Birds-of-paradise – decent appearance; no obvious errors. 50 excerpts; five other images. Some manual improvements. Currently at MfD with the rationale that woodpeckers are not a family.
  24. Portal:Coffee production – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 11 other images. Routine maintenance.
  25. Portal:Albanian diaspora – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; three other images. Routine maintenance.
  26. Portal:University of Nebraska–Lincoln – decent appearance; no obvious errors but a narrow scope. 18 excerpts; eight other images. Routine maintenance. Currently at MfD with the rationale that Portal:University of Arkansas at Pine Bluff contains only two articles.
  27. Portal:University of Gothenburg – decent appearance; no obvious errors but a narrow scope. 10 excerpts; two other images. Routine maintenance.
  28. Portal:Transformers – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; two other images (everything else is non-free). Some manual improvements.
  29. Portal:Boston Celtics – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 16 other images. Routine maintenance.
  30. Portal:Newbury Park, California – decent appearance; no obvious errors but a narrow scope. 16 excerpts; 34 other images. Routine maintenance.
  31. Portal:Vanessa Williams – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; two other images. Routine maintenance.
  32. Portal:Bette Midler – decent appearance; no obvious errors but a narrow scope. 40 excerpts; seven other images. Routine maintenance.
  33. Portal:Ozzy Osbourne – generally decent appearance but several minor display errors;(fixed) narrow scope. 50 excerpts; 17 other images. Routine maintenance.
  34. Portal:Carnegie Mellon University – decent appearance; no obvious errors but a narrow scope. 15 excerpts; 28 other images. Routine maintenance.
  35. Portal:Milwaukee – decent appearance; no obvious errors. 15 excerpts; 47 other images. Some manual improvements. Too few excerpts but potentially good.
  36. Portal:Billings, Montana – decent appearance; no obvious errors but a narrow scope. Four excerpts; 27 other images. Some manual improvements.
  37. Portal:Empire of Japan – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 20 other images but with a couple of repeats. Routine maintenance.
  38. Portal:Cheese – decent appearance; no obvious errors. Nine excerpts; 50+ other images. Extensive manual improvements. Too few excerpts but potentially good.
It appears that most of the portals have a narrow scope and should go but a significant minority are either already of a good enough standard to keep or show sufficient potential to merit further attention. This impression is based not on cherry-picking but on a random sample. Certes (talk) 21:42, 21 March 2019 (UTC)[reply]
Thank you for this, this is a very good illustration of why this proposal is too broad - it will delete portals that clearly should not be deleted, and others that may or may not need to be deleted (e.g. I've !voted to merge several of the portals about universities). Thryduulf (talk) 21:58, 21 March 2019 (UTC)[reply]
  • Query Why don't we have a CSD for pages created by unauthorized scripts or bots?
    WP:BAG exists for a reason right? (And this seems to be a good example of it). Crazynas t 21:50, 21 March 2019 (UTC)[reply
    ]
    • @Crazynas: because not all of them should be deleted, as [[user:|Certes]] analysis immediately above demonstrates perfectly. Thryduulf (talk) 21:58, 21 March 2019 (UTC)[reply]
@Thryduulf: You're missing my point. Just like we have a policy that banned users are to be reverted in all cases not because they might not make good edits (to game the system or not) but because they are a disruption to the community; so we should have a policy that pages created (or edited I suppose) by unauthorized bots are inherently not welcome, because of the potential for disruption regardless of their merit (by disruption I'm talking about this AN thread as much as the pages themselves). This is the whole reason we have a group dedicated to overseeing and helping with bots right? Crazynas t 22:12, 21 March 2019 (UTC)[reply]
No bots were involved. The pages were created using a template. One of your last page creations was a user talk page, where you welcomed a new editor using Twinkle. You did a very professional job, by applying a template which introduces the new editor with the sort of carefully considered and neatly arranged prose that we don't have time to write every time a new contributor appears. Using a template is not a valid rationale for mass deletions. Certes (talk) 22:22, 21 March 2019 (UTC)[reply]
Curious, what template did you use? I guess the difference I see is the twinkle is highly curated and subject to extensive review (as are the templates it calls). If all these pages were manually created, then what happened in the example of (what to me looks pretty much like G1) that Fram posted above? Why didn't the human that pressed the button take responsibility for that (so to speak) pile of rubbish? To clarify, Bot here covers scripts, AWB (which is 'manual'), java implementations etc. In short: "Bot policy covers the operation of all bots and automated scripts used to provide automation of Wikipedia edits, whether completely automated, higher speed, or simply assisting human editors in their own work." The policy explicitly references mass page creation as being under the purview of BAG here. Crazynas t 22:39, 21 March 2019 (UTC)[reply]
I haven't used any of these templates myself but recent portals have been created by variants on {{Basic portal start page}}. The numbered versions such as {{bpsp6}} cater for portal-specific conditions such as there being no DYKs to feature. Certes (talk) 23:07, 21 March 2019 (UTC)[reply]
@Crazynas: I was simply answering your question about why we do not speedy delete every page created by an unauthorised bot, etc - simply because not every page created by such means should be deleted. You are also mistaken about banned users - they may be reverted but they are not required to be. Certes analysis shows that some of the portals created by the script have been improved since, sometimes significantly. Thryduulf (talk) 22:46, 21 March 2019 (UTC)[reply]
@Thryduulf: Sure, and this is tangential to the proposal here (which I'm still opposing, if you noticed). In any case the thought I'm having wouldn't be applied ex post facto but it would make it explicitly clear that mass creation of pages by automated or semi-automated means without prior approval is disruptive. Crazynas t 23:02, 21 March 2019 (UTC)[reply]
  • Comment. The problem with many of these recently created template-based portals is that it is difficult or impossible to improve them. I've edited portals for over a decade but cannot work out how to change the portal code to include or exclude a particular article or image. (For articles I believe one has to change the template or mark the article as stub to exclude it; for images I believe it just harvests those from the main topic article.) Thus they are not drafts that could be further improved, they are static uneditable entities for which the only solution is to start from scratch. There is no thought to be preserved that is not equally present in the list of articles in the template/images in the root article. Espresso Addict (talk) 02:12, 22 March 2019 (UTC)[reply]
  • The key issue is that traditionally, portals are viewed as entry points to broad topic areas. However a page generated by the helper templates that draw content from an underlying navigation box is more akin to a second screen experience: it provides an X-ray view into the navigation box. It's not clear this is the experience the community wants to provide for readers visiting something labelled a portal. isaacl (talk) 20:47, 24 March 2019 (UTC)[reply]
  • the automated scripts are so easy to fool. Even if everything looks perfect when the portal is set up, as soon as someone adds an new link to a nav box (that may make sense in the nav box but not for the portal), adds an image to a page, or creates a DYK completely unrelated to the topic which includes the five letters "horse" within someone's name behind a pipe, you get random inappropriate stuff in an automated portal. The editor adjusting the nav box, adding a picture without a caption per
    WP:CAPTIONOBVIOUS or creating the DYK has no idea the portal is being busted. There is no edit to the portal to review so watch listing the portal does not help. You have to manually review the portal display regularly. That is before looking at lua errors. Autogenerated content is a bad idea. Forcing other editors to review your auto generated crap is wrong. Ignoring the guidelines because they are "outdated" and leaving 4500 pages that need to be checked and discussed against the guidelines by other editors is wrong. The only reasonable solution is to nuke these from orbit. Then if someone willing to follow the guidelines and use intellgently designed and applied tools want to recreate some titles, that is fine. Legacypac (talk) 21:23, 24 March 2019 (UTC)[reply
    ]
    • Everything you say before "The only reasonable solution..." may be true but is irrelevant to this proposal as written. "Nuking them from orbit" is not the only reasonable solution, as fixing the issues so that the portals don't break is also reasonable. As is not deleting the ones that have been fixed so that the errors you talk about don't occur. Thryduulf (talk) 00:46, 25 March 2019 (UTC)[reply]

      Portal creation ... is down to about a minute per portal. The creation part, which is automated, takes about 10 seconds. The other 50 seconds is taken up by manual activities, such as finding candidate subjects, inspecting generated portals, and selecting the portal creation template to be used according to the resources available. Tools are under development to automate these activities as much as possible, to pare portal creation time down even more. Ten seconds each is the goal.
      — Portal Update #29, 13 Feb 2019

      Someone spent less than 50 seconds creating the page; requiring editors to spend more time than that to delete it has an extortionate effect, even though there's a good faith intent. If we don't nuke from orbit, then those who want these automatically-created portals deleted will be forced to spend far, far more than 50 seconds per portal discussing them one by one (or ten by ten, or one hundred by one hundred, it'll still be a lot of time). 50 seconds "taken up by manual activities" is how we end up with a Portal:Sexual fetishism that includes Pedophilia as one of the selected articles–probably not the best selection–but that's been there for five months now. Levivich 03:04, 25 March 2019 (UTC)[reply]
      • Two wrongs do not make a right and there is no deadline. The only reason for deleting them all you seem to have is that you don't like that these portals were created so quickly, and that some of them are bad. That's fine, you are entitled to your opinion and some of them are bad. However that does not equate to a reason to delete all of them without checking whether they are good or bad. If you have problems with specific portals then they should be fixed and/or nominated for deletion, as I see you have done in this case, but just because X is bad doesn't mean that the entire set of pages of which is a part should be speedily deleted. Thryduulf (talk) 09:35, 25 March 2019 (UTC)[reply]
  • Oppose 1) Let's not create precedents where we hand single admins editorial control, admins may well be great editors (some better than others), but let's keep editorial control as much as possible only with all editors. 2) The formulation of this supposed CSD criteria seems to be a
    WP:PUNISH against a single user. (As an aside, different perspective: there are perhaps millions of pages in article space that are "poor", so portal space is bound to have them, too - just work through it -- and if we come-up with new forward looking policies and guidelines for all portals (or mass creations) consistent as possible with the 5 P, all the better). Alanscottwalker (talk) 17:42, 25 March 2019 (UTC)[reply
    ]
  • Support - per Fish & Karate. Ealdgyth - Talk 16:08, 27 March 2019 (UTC)[reply]
  • Oppose. I feel there are much better ways of handling the situation, including but not limited to: expanding P2, Portal PROD, and even MFD. This is too broad of a sword that doesn't even cut in the right places since it's only limited to one user in a given time frame. -- Tavix (talk) 16:15, 27 March 2019 (UTC)[reply]
  • Thought I had voted here but I guess I hadn’t. Regardless, my thinking on this has changed because of Certes’ in-depth analysis of TTH’s portal creations. Anyway: Oppose. The mass creation of portals is something that should be dealt with preferably quickly, but this proposal as written is not the right way to do it. Sure, there are a lot of crappy portals that could be deleted fairly uncontroversially, but there are also a lot of good portals as well as edge cases that deserve more community discussion on whether they should be deleted, or at least a longer waiting period so users may object. — pythoncoder  (talk | contribs) 12:40, 29 March 2019 (UTC)[reply]
  • Oppose for now. I still hope that the proposal might become limited to portals looked at and determined to be poor by some objective criteria, which I could support, but that hasn't yet happened. Speedy ad hominem deletion regardless of subsequent tuning, current quality or even potential for future improvement is likely to throw too many babies out with the bathwater. Certes (talk) 12:46, 29 March 2019 (UTC) Duplicate !vote stricken. GoldenRing (talk) 10:14, 4 April 2019 (UTC)[reply]
  • Regretfully support: as an editor I dislike the idea of creations made by certain users being deleted en masse but, quite frankly, MfD cannot cope with the influx at the moment. Hell, I've got a decent laptop and MfD is getting so big scrolling down causes a bit of lag. SITH (talk) 20:57, 30 March 2019 (UTC)[reply]
  • Strong support of something to this effect, per
    few members, and while I do argue that portals are not content, they are a navigational tool, so community control of them can be a bit "stricter" than mainspace articles, perhaps something like PROD would be better. Regardless of how this pans out, for future portals going forward I proposed Portals for Creation at RfC, and created a mockup here if anyone wants a look. — Preceding unsigned comment added by John M Wolfson (talkcontribs
    )
    Why is requiring administrators to comb through deleted portals to find those that should not have been deleted in order to restore them, having inconvenienced those people who use the portals in the mean time, in any way better for the project than deleting only those that need to be deleted? Thryduulf (talk) 07:34, 4 April 2019 (UTC)[reply]
  • Support. Worthless pages which take 12 seconds to create shouldn't take more than 50000 times that for multiple users to delete. If a subject WikiProject or person interested in the portal's subject is willing to "adopt" that portal, or even assert that the portal is not useless, a more nuanced consideration may apply. And, I should point out, some of the individual deletions are incomplete, as user-facing pages (mostly categories and navigation templates, but some actual article pages) still point to the deleted portals. — Arthur Rubin (talk) 10:25, 4 April 2019 (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.

Clarification on G8

There are a whole host of unused documentation templates (1,111 to be exact). The vast majority are the result of the base page being redirected. For example, you have

WP:G8. Anyone have any strong feelings? --Zackmann (Talk to me/What I been doing) 20:13, 13 March 2019 (UTC)[reply
]

This is not a G8, as the parent page does exist. What is wrong with redirecting the doc of the old template to the doc of the new template? {{3x|p}}ery (talk) 20:21, 13 March 2019 (UTC)[reply]
To clarify, does G8 then apply to documentation pages for deleted or otherwise nonexistent templates? I would assume so, as documentation pages are technically subpages, though it is not entirely clear. ComplexRational (talk) 02:35, 14 March 2019 (UTC)[reply]
Yes, I would say so. If Template;X doesn't exist and wasn't speedy deleted out of process, then Template:X/doc is a proper G8 deletion. {{3x|p}}ery (talk) 02:49, 14 March 2019 (UTC)[reply]
If you really want to pursue the claim that doc pages of redirects should be deleted, then take it to the proper venue (
RfD) rather than misusing speedy deletion criteria that do not apply. {{3x|p}}ery (talk) 20:23, 13 March 2019 (UTC)[reply
]
For goodness sake Pppery AGF. I'm discussing it at templates for deletion because they are TEMPLATES. You are of the opinion that G8 is not valid, but so far that is just your opinion. --Zackmann (Talk to me/What I been doing) 20:29, 13 March 2019 (UTC)[reply]

Transcluded to Wikipedia talk:Criteria for speedy deletion. {{3x|p}}ery (talk) 20:32, 13 March 2019 (UTC)[reply]

Proposal: Apply a 7-day hold to G13

There are currently 1508 drafts eligible for

, and the number continues to rise. With the current workflow, clearing this backlog requires going through each of the drafts, checking them for notability/potential usefulness, and tagging them for speedy deletion. Then a closing admin will need to go through each of them again, verify it meets the G13 criteria, and delete.

This may happen quickly enough that the author of the draft, any reviewers who thought the draft might have potential, or other interested editors who may have the draft watchlisted, may not receive any warning or notification until the draft is already deleted. Admins can view and restore the deleted version, the original creator should hopefully remember what the draft was about and request a

REFUND
, but others have no ability to save the draft or even remember if it was useful.

I believe there is simpler and better way. Tag each stale draft as G13, with an appropriate notification for the creator of the draft. After 7 days, if no one has contested the deletion, an admin will delete it. If someone has contested it but does not improve the draft, the process repeats in six months. By applying a 7-day hold, the entire community could review the existing stale drafts and act to save them. Compare that to the current system, where no action results in the draft being saved, and editors need to act to delete them.

If we make this change we should be able to do a better job of clearing out old drafts, while working together to save the good ones. – bradv🍁 03:54, 7 May 2019 (UTC)[reply]

  • Oppose. Unless you have people who keep constant eyes on G13's category that aren't bots and who actually give a damn enough to find sources (as that's generally the main issue with drafts that languish that long) then this is just kicking the can down the road indefinitely, since to stall the process out an editor could either challenge the G13 or make a null edit to the draft (thus negating the G13 entirely). Another thing worth bearing in mind is that for many of these drafts, sources just might not exist at present (a problem for
    biographies in particular). —A little blue Bori v^_^v Bori! 04:06, 7 May 2019 (UTC)[reply
    ]
    Jéské Couriano, but the current system is that the draft languishes indefinitely until someone chooses to nominate it. And then no one chips in to fix it, it just gets deleted without a second look. This proposal provides a more collaborative approach. – bradv🍁 04:10, 7 May 2019 (UTC)[reply]
    A more collaborative approach doesn't mean much if the only sources available are ones that we don't consider useful, and this is, again, doubly so for biopgrapbies. A big reason many of these drafts languish is because the sourcing is not up to scratch. Indeed, a decent amount of the drafts we see in -en-help have serious issues with both the sources that are used and the sources that are even available in the first place, with the editor in question defaulting to
    mercenaries but that is largely irrelevant here except to explain their behaviour.) —A little blue Bori v^_^v Bori! 09:52, 7 May 2019 (UTC)[reply
    ]
I don't see a scenario where someone is astute enough to make a null editor but not request a refund. By putting a hold someone could verify that deletion is in the interests of promoting encyclopedic knowledge. Best, Barkeep49 (talk) 04:12, 7 May 2019 (UTC)[reply]
  • Don't have much of an opinion here, but It's amusing to me to note that the first sentence seems to imply that we need a faster G13 process, not a slower one. ansh666 05:20, 7 May 2019 (UTC)[reply]
    Ansh666, the idea is to tag stale drafts somewhat indiscriminately and then review them, rather than check each item on the list for notability before they are tagged. Then if anyone thinks they might be notable, the tag can be removed. So yes, this should actually speed up the process, while hopefully getting more eyes on the drafts before deleting them. – bradv🍁 05:31, 7 May 2019 (UTC)[reply]
  • To clarify, the idea here if this is implemented is to then indiscriminately nominate all G13 eligible pages at some sensible rate? Tazerdadog (talk) 06:05, 7 May 2019 (UTC)[reply]
  • I'm not sure what to think. On the one hand, a week-long hold akin to some C- and F-criteria to allow others time to rescue it from deletion seems like a good idea. On the other hand, changing the process so that taggers no longer have to think about the consequences of tagging something useful for deletion is imho a no-go because G13 is just a possibility, not a necessary step to take. Just a thought but can't the draft template be modified to list drafts that have not been edited for say 5 months in a category like Category:Drafts that are eligible for G13 in a month or something? A bot could also notify editors that their draft becomes eligible for G13 in a month if abandoned. That way, there is no need to add a hold to G13 while simultaneously speeding up the process by removing drafts that are still worked on before they become eligible for G13. NB, I oppose G13 altogether but if the community wants it, it should at least be done right. Regards SoWhy 07:22, 7 May 2019 (UTC)[reply]
    As it is, a bot notifies a user if a draft they worked on is at or approaching the six-month threshold. —A little blue Bori v^_^v Bori! 09:41, 7 May 2019 (UTC)[reply]
    Jéské Couriano, HasteurBot used to notify them and then automatically tag them for deletion, but it's been decommissioned. Stale drafts are now deleted manually without notification. – bradv🍁 14:01, 7 May 2019 (UTC)[reply]
    • AFC tagged drafts have this already (meaning the rest of draft-space does not): Category:AfC_G13_eligible_soon_submissions. --Izno (talk) 12:11, 7 May 2019 (UTC)[reply]
      Thanks for the info, I didn't know that. Then I'm definitely opposed to making such a change, seeing as that information about G13able drafts is already available and editors get notified that their draft is at risk. Further holding seems unnecessary then. Regards SoWhy 12:28, 7 May 2019 (UTC)[reply]
WP:OWN.) I think the issue with G13 is a bit deeper than we're going to get into in this proposal but I disagree entirely with the deletion of something just because it's old and I find this to be a problem also with administrators not actually evaluating the merit of the draft when reviewing for deletion (and I wonder if some G13 mass deleters actually look at the suitability of the content before doing so.) Praxidicae (talk) 14:21, 7 May 2019 (UTC)[reply
]
@Praxidicae: As I said, further holding seems unnecessary if editors are notified anyway. Bradv has afterwards clarified that the bot in question no longer works. Reinstating a bot to notify you and any other editors that a draft will soon be eligible for G13 seems like a better idea because it allows notice before deletion is requested. Regards SoWhy 15:20, 7 May 2019 (UTC)[reply]
SoWhy, the bot didn't notify any other editors though, it only notified the creator of the draft. In order to also notify other interested editors we would need to also put a tag on the draft so it shows up on watchlists. This would be a much more complicated solution than the one I am proposing, as the stale draft database report would have to somehow ignore the application of the tag in the edit history. – bradv🍁 15:25, 7 May 2019 (UTC)[reply]
  • Oppose per perennial opposition to G13. Also oppose in this case because speedy criteria are meant to be objective and uncontestable; adding a 7-day hold acknowledges that the criterion fails those two conditions. If we want to create a DRAFT
    PROD then let's just do that, and toss the six months requirement. Ivanvector (Talk/Edits) 12:33, 7 May 2019 (UTC)[reply
    ]
    Ivanvector, I agree that stale drafts need more review before deleting, not less, which is why I proposed this. – bradv🍁 14:07, 7 May 2019 (UTC)[reply]
Yes I know, it's a more reasonable approach than what I've seen proposed on stale drafts in recent memory. I'm mostly only opposed to this being defined as a speedy criterion, and in general (my ongoing protest) I dislike that we have a class of pages that can be deleted just because they're old. If they're old, and they're unsuitable for mainspace and nobody wants to improve them, well then fine, clean them out, but I think that's a PROD more than a CSD. Speedy criteria should be for pages that can be deleted at the moment they are tagged, for unresolvable issues. Ivanvector (Talk/Edits) 14:13, 7 May 2019 (UTC)[reply]
Ivanvector, in principle I agree with you entirely, and I think this is a step in the right direction. I'm fine with calling this a PROD rather than a CSD. – bradv🍁 14:16, 7 May 2019 (UTC)[reply]
I like the idea of a draft-prod without a 6-month requirement, but under current prod rules, something can't be re-prodded if it's been prodded in the past. That would mean that rather than getting a 6-month extension when someone removes a G13, these drafts would languish around forever once someone removes one. Natureium (talk) 17:11, 7 May 2019 (UTC)[reply]
MfD would be the place to handle drafts where a prod has been removed so they would only languish until improved enough for mainspace or nominated at MfD. Another solution would be a draft-only rule that drafts may be re-prodded after a given time (eg: after six months of inactivity if G13 procedures are to be imported). -- Tavix (talk) 17:28, 7 May 2019 (UTC)[reply]
As I understand the proposal, it is PROD-like but is not actually using PROD. If deletion of an abandoned draft is contested, it would be eligible again for deletion through this process after 6 more months of inactivity. ~Kvng (talk) 21:02, 7 May 2019 (UTC)[reply]
Whether we end up calling this G13 or a PROD is up for discussion, but I agree that drafts should be eligible again after 6 months of inactivity, regardless of whether they've been tagged in the past. – bradv🍁 21:06, 7 May 2019 (UTC)[reply]
Correct, it would be PROD-like, in the way that
WP:BLPPROD is "PROD-like" but is a separate process. I would think that the one-time PROD convention would not be a problem here: if something has been de-PRODded and is still not improved, run it to MfD. The idea is for there to have been a genuine opportunity for the creator to re-stake their claim or for someone else to take it over, not the current nominal "your stale draft is about to be dele ... oh never mind, an admin already got it" that we basically have now with this being a speedy criterion. Ivanvector (Talk/Edits) 16:09, 8 May 2019 (UTC)[reply
]
  • Strong support In the absence of any other reasonable changes to removing stale drafts. I find mass g13 deletions to be one of the more disruptive aspects of Wikipedia. I'll clarify a bit more in detail later but I don't see any harm in keeping stale drafts provided they don't meet some other deletion criteria. Praxidicae (talk) 14:14, 7 May 2019 (UTC)[reply]
  • Support. Adding a seven-day review would effectively make G13 a draft PROD process with a couple extra rules, so let's call it what it is and move the process to PROD if/when something like this passes. -- Tavix (talk) 14:21, 7 May 2019 (UTC)[reply]
  • Support I am in agreement with those who note it's no longer a speedy deletion but becomes a new kind of PROD. To that I say GREAT (and have indeed left a message on that talk page). Most G13 are incredibly uncontroversial. These will be unaffected by this change - G13 could already be removed by anyone including article creator (unlike some other CSDs). But this adds time for any interested editor to ensure that, given our
    WP:WEBHOST and thus not applicable. Indeed this tag would allow any who are interested to look through possible deletions and find an article they wish to improve and get ready for mainspace. We're here to build an encyclopedia and drafts are one way we do this. Best, Barkeep49 (talk) 17:49, 7 May 2019 (UTC)[reply
    ]
  • Support - Authors are currently receiving little or no notice before their drafts are deleted. I have watched
    WP:PROD closely and I think this process works well and would work when applied, in the modified form proposed, to our G13 candidates. ~Kvng (talk) 20:58, 7 May 2019 (UTC)[reply
    ]
  • Support plenty of people go to
    WP:REFUND to request restoration of drafts which were deleted only days ago, which is rather pointless. If there is an active editor who cares about the draft enough to contest deletion then it isn't abandoned. I don't see any inconsistency with a speedy deletion criterion having a waiting period, lots of the file criteria have waiting periods (e.g. F4, F5, F6, F7). Hut 8.5 21:18, 7 May 2019 (UTC)[reply
    ]
  • Isn't the more straightforward solution to pressgang someone into reviving the bot, so that users are notified at month 5 and then pages are auto-tagged at month 6? Seems like a good task for a bot, and a particularly pointless task for humans. ~ Amory (utc) 00:43, 8 May 2019 (UTC)[reply]
    I support this option. Natureium (talk) 00:46, 8 May 2019 (UTC)[reply]
    I'd be willing. — JJMC89(T·C) 03:49, 8 May 2019 (UTC)[reply]
    Without a doubt. —A little blue Bori v^_^v Bori! 05:25, 8 May 2019 (UTC)[reply]
    Amorymeltzer This is fine for the article creator but what about any watchers? Best, Barkeep49 (talk) 03:51, 8 May 2019 (UTC)[reply]
    The bot could do a dummy edit to the draft with a suitable edit summary to alert watchers. Johnuniq (talk) 03:57, 8 May 2019 (UTC)[reply]
    That would reset the clock on the G13. – bradv🍁 03:59, 8 May 2019 (UTC)[reply]
    Nah, bot edits don't count for G13. I think it's likely probably overkill, given how few watchers there are for most things, but you make a good point below about not being able to review. At any rate, such a "dummy edit" would be well suited to the talkpage; it'd be trivial for (insertBotName) to place a similarly-worded notification on the talkpage at the same time as notifying the creator, if desired, thus alerting anyone watching. That'd also make it trivial to categorize every draft into a G13 soon category, which should make review (or at least finding them) easier. ~ Amory (utc) 09:41, 8 May 2019 (UTC)[reply]
    I think the idea of the hypothetical bot posting on the talk page and alerting the creator is a great idea in lieu of this - where we can automate repetitive tasks like this, that's ideal. It sounds like JJMC89 might be willing to take this from hypothetical to actual bot? Best, Barkeep49 (talk) 14:13, 8 May 2019 (UTC)[reply]
    Sure, adding draft talk notices to go out with the user talk notices would be easy. — JJMC89(T·C) 05:25, 9 May 2019 (UTC)[reply]
    Amorymeltzer, HasteurBot indiscriminately tagged drafts for deletion once they had reached six months with no edits, and admins routinely mass-deleted entire categories of drafts. No one was actively reviewing these drafts, as the only ones who were notified were the original creators. It never was the best solution, as it led to thousands of potentially useful articles deleted without review. Every day there are several deleted drafts on my watchlist – I can't see them any more to see if any of them have potential, and I usually don't remember why I was watching them in the first place. Admins have the ability to view deleted drafts, but for most AfC reviewers and editors this is a big issue. How would bringing back HasteurBot help with this?
    Secondly, the current situation is that there are 1500 stale drafts that need to be either rescued or deleted. I propose we nominate them a handful at a time until the backlog is cleared, and allow 7 days for editors to review each of them. If you object to this proposal, what do you recommend we do with these drafts? – bradv🍁 05:42, 8 May 2019 (UTC)[reply]
    That sort of is the point though, no? You make a fair point about watchers and reviewers, not to mention there not being a complete category (that is, only AfC drafts have the "soon" category, not all drafts) for the community to peruse a la
    WP:ARS, but the difference between what you're proposing and a bot is 6 months + 7 day review versus 5 months + 1 month review. I'd feel much better with either process, truth be told — I'd be much happier deleting something knowing that folks have been explicitly given the chance to return to the content — but I don't see an appreciable difference in result aside from complexity, and I don't foresee an appreciable difference in behavior aside from easier cleanup. ~ Amory (utc) 09:48, 8 May 2019 (UTC)[reply
    ]
    Amorymeltzer, the change we're proposing would only require a change to the {{db-g13}} template so it behaves like other timed deletion templates, like {{Di-no source}}. That's a fair bit simpler than bringing back HasteurBot with the changes we discussed here, isn't it? – bradv🍁 14:34, 8 May 2019 (UTC)[reply]
  • Support, however the real issue is that pages are being drafitied (usually without any attempt at improving the article beforehand) for reasons that would never get a page deleted at AFD, then they're abandoned as the creator gives up or leaves Wikipedia, and then the page is G13'd after 6 months without anyone checking to see if the page could have been saved. Hopefully this change limits those kind of deletions, but I'd prefer a change so that any pages that have been draftified should be mainspaced or AFD'd instead of being subject to G13. IffyChat -- 10:09, 8 May 2019 (UTC)[reply]
    Generally, I move a page into draftspace in responce to a helpee in -en-help asking how to submit their already-in-mainspace article, and the page itself is not ready for mainspace yet. When I explain why I am moving it back (in IRC, of course), I get castigated by them.
    It's as if they only care that it shows up on Google.—A little blue Bori v^_^v Bori! 20:24, 8 May 2019 (UTC)[reply
    ]
  • Oppose - This defeats the purpose of CSD. It's called speedy deletion for a reason. If you would like to allow the draft author to have some time before the draft is deleted, you can just use
    talk) 11:38, 8 May 2019 (UTC)[reply
    ]
No, you can't because PROD cannot be used in draftspace. Praxidicae (talk) 15:33, 8 May 2019 (UTC)[reply]

NOTWEBHOST should apply to all namespaces

pages that violate NOTWEBHOST do not only exist in userspace, there are many in draftspace too. I see no reason to limit this speedy deletion criterion to only userpace. Roger (Dodger67) (talk) 07:46, 10 May 2019 (UTC)[reply]

Suggestion: Don't delete draft pages after 6 months due to historical reasons.

Hello.

I suggest to keep

draft pages
beyond 6 Months because of historical reasons and also because someone in future might find it and work on it.

Keeping those articles does not harm or disrupt Wikipedia at all, therefore I suggest draft articles to be kept indefinitely, or be put into a draft archive after 6 months instead of full deletion. Someone might find the article in the draft archive and work on it.

--Chanc20190325 (talk) 09:21, 18 May 2019 (UTC)[reply]

@
WP:REFUND. Also see the G13-related proposal above before making a new one. CoolSkittle (talk) 18:23, 20 May 2019 (UTC)[reply
]
@CoolSkittle: Good point. And thanks for the response. --Chanc20190325 (talk) 22:29, 21 May 2019 (UTC)[reply]

Clarification of R3 seems needed

Given some of the comments at Wikipedia:Deletion review/Log/2019 May 16#Badnam Song it seems there is misunderstanding of what R3 is for. I think the best way to solve this is to add a short note that simply being incorrect is not the same thing as being implausible (in a similar manner to how the difference between significance and notability is stressed at A7). I'm not sure how best to word this though. Thryduulf (talk) 10:49, 18 May 2019 (UTC)[reply]

I saw that discussion and I don't think any clarification is needed. Everyone knows just what the criterion says and means but they just don't like things like that. In my experience for other widely misused criteria such as
WP:G4 (not substantially identical) people just deny what the words say even when the exact wording is pointed out and explained. Thincat (talk) 13:28, 18 May 2019 (UTC)[reply
]
@Thincat: so what can be done to stop this abuse of CSD? Thryduulf (talk) 15:55, 20 May 2019 (UTC)[reply]
Consequent reporting of admins who do so to ANI? Regards SoWhy 17:08, 20 May 2019 (UTC)[reply]
  • I also think R3 needs clarifying, but not in the way I believe Thryduulf means. I would add something saying that it applies to any redirect which is strictly a mechanical alteration of the title based on punctuation, word order, or upper/lower case, since all of those are already handled by any reasonable search engine (including our own). The "recently created" clause should still apply in these cases, to avoid breaking external links. -- RoySmith (talk) 20:02, 20 May 2019 (UTC)[reply]
    • I'm sorry but you could not be more wrong.
      Barrington River, Nova Scotia speedily deleted for example as it's just a "mechanical alteration" of the conventional disambiguation and recently created, despite being a very useful redirect. Thryduulf (talk) 22:02, 20 May 2019 (UTC)[reply
      ]
  • I agree with Roy. I'd be happy to have someone justify why such newly created redirects are helpful, but I don't see a need right now. I can see an argument that getting the wording correct may not be as clear-cut as we generally like for CSD. But I'm not seeing a use for these at this point of search-engine prowess Hobit (talk) 20:41, 20 May 2019 (UTC)[reply]
    • Because going via the search engine is always going to be a significantly inferior experience for the reader to a direct link. Unless the search term is ambiguous or unintelligible to the point we don't know what the searcher is looking for or we don't have any relevant content to take them to, we should always take people directly to the content they are looking for as quickly as possible. Thryduulf (talk) 22:08, 20 May 2019 (UTC)[reply]
      • The people who write the big search engines put a mind-boggling amount of effort/money/brainpower into figuring out what page a person is looking for when they enter a search term. The idea that you or I can do a better job of that by guessing which redirects to create is just absurd.

        Let's for the moment assume that this redirect makes sense. Then, the logical extension of that would be to create the similar redirect for every other "...(song)" title. Which, by my count is just shy of 30,000. Are you suggesting we do that? Because, if we don't, then we'll have inconsistent results for different titles. badnam song will get you directly to that page, but gorilla song will get you to a search results page. Inconsistent behavior is confusing for the user. -- RoySmith (talk) 22:57, 20 May 2019 (UTC)[reply]

        • That's a fair argument for RfD but because not every redirect of the type "foo thing" → "foo (thing)" and vice versa should be deleted it is not a reason for speedy deletion - see
          WP:NEWCSD point 2. Thryduulf (talk) 23:24, 20 May 2019 (UTC)[reply
          ]
  • R3 has two criteria: "recently created" and "implausible". Both must be satisfied: it is not enough that it be recently created, it also needs to be implausible. If I were to create two redirects:
    Annalise Dodds suggested, and that will take you to the properly-spelled page. --Redrose64 🌹 (talk) 16:55, 21 May 2019 (UTC)[reply
    ]
    • That's a good example from Redrose64, although I suspect my suggestion of "the one in Oxford who's not Layla Moran" is probably a step too far. In general, the only time I would consider R3 if it contained formatting errors (eg: "Lore Ipsum (singer") completely nonsensical typos (eg: "Thereeeeeeesa May"), or blatantly offensive (use your imagination). As with all CSD criteria, it must be so obvious to any reasonable editor that you should be confident there will be no objections. Ritchie333 (talk) (cont) 17:05, 21 May 2019 (UTC)[reply]
    • I apologize for introducing a tangent, but R3 and A10 specify "recently created", and I was wondering if there's any clear agreement on what that means. A day? A week? A month? Three months? WhatamIdoing (talk) 21:48, 21 May 2019 (UTC)[reply]
      • In the case of R3, less than two weeks is uncontroversially recent, more than a month will almost never get consensus that it's recent. In between the two it varies - if it's extremely implausible (e.g. "Cahrles Dickens" → "Boeing") then people are more forgiving on the recency than if it's not (e.g. "Cahrles Dickens" → "Charles Dickens"). Thryduulf (talk) 23:29, 21 May 2019 (UTC)[reply]
        • The point of the "recent" restriction is to make it unlikely that external sites have already linked to the URL. It would be more useful to turn this into a search for such links (which the various search engines support with their own syntaxes). Our own web servers can also tell if a page has been linked to by looking at the HTTP Referrer headers, but I don't know if that information is available to users. If a redirect has existed for 5 minutes and external sites have already picked it up, then we should keep it. If it's existed for a year and nobody's linked to it, then there's no need. -- RoySmith (talk) 13:26, 22 May 2019 (UTC)[reply]
          • That information is not available to anyone (except possibly developers, and if they do I have no idea if they have the tools to easily analyse it). It also cannot tell whether a page has been linked, only whether links from sites that choose pass on correct refer information have been followed. It also cannot tell whether search engines have indexed it, nor whether it has been bookmarked or added to a hard copy document or other offline resource. The recency of creation is a crude method of determining the likelihood of such links, but it's the only one we have. I know getting access to the http refer information has been discussed before, I only have a vague memory of that but I think it was deemed that making such information public would violate the Foundation's privacy policy. I also vaguely recall some concerns about manipulation, spamming, or something like that. One final point is that even some redirects that seem implausible to a random editor can turn out to actually be very useful when someone with relevant subject knowledge fills in context. The longer ago a redirect was created, the less likely such a person will be around to spot the nomination and the more likely that the context will be discoverable by non-experts. Not the best example of this, but Wikipedia:Redirects for discussion/Log/2019 May 16#Gut bath is one of the most recent cases. Thryduulf (talk) 23:22, 22 May 2019 (UTC)[reply]
          • It has just occurred to me that if there is a privacy concern then aggregated and anonymised statistics might not (e.g. 20 hits today, 8 were from the English Wikipedia, 8 were from other websites, 4 were from other or unknown sources) but (a) I don't know if it would be allowed, and (b) I don't know who/where to ask to get the answer, but MusikAnimal maintains the pageviews analys tool and so might be able to help. Thryduulf (talk) 23:29, 22 May 2019 (UTC)[reply]
  • The extended lengthy discussion at DRV over a particularly unimportant redirect and the exact definition of scope of R3 is a monumental waste of time for the importance of the question. There is no information being deleted, it is just a cheap redirect. I think a better option than a tighter wording for R3, is explicit wording that in the case of an good-faith objection to a speedy deletion by any editor in good standing, and the lack of a good reason not to (generically G10 and G12 cases), the deletion should be listed at XfD. Discussion of the merits of a particular case belongs at XfD, not DRV. In this case, RHaworth has again being quick to accept a CSD request for an unimportant page(redirect). Just send it to RfD. --SmokeyJoe (talk) 01:01, 23 May 2019 (UTC)[reply]
    • Whether a page (redirect or otherwise) is "important" is something that can only be determined at XfD. I agree that any reasonable objection to a speedy deletion should result in the deleting admin speedily listing it at XfD (with evidence that it might not be a copyvio in the case of G12, for G10 I'd probably want a couple more opinions if it was borderline). That does not mean though that getting CSDs right first time is somehow unimportant or that it doesn't really matter if someone makes a lot of mistakes if they're happy to correct them afterwards when challenged. Incorrect speedy deletions are one of the most harmful things an administrator can do. Thryduulf (talk) 01:15, 23 May 2019 (UTC)[reply]
      • I think that admins should be allowed a reasonable error rate in accepting others' CSD taggings. In this case, did User:RHaworth unilaterally delete, or did someone else tag it? I think that is an important distinction, if someone wants to criticize the admin. This case is pretty trivial. Taking it to DRV without talking to deleting admin is poor protocol. DRV seems to need WP:CSD to say something to encouraging speedy listing at XfD disputed trivial deletions. --SmokeyJoe (talk) 01:43, 23 May 2019 (UTC)[reply]
        • Badnam Song was tagged by user:CptViraj. A deleting admin should be personally verifying that every CSD tag they encounter is correct, and it is the admin that carries the responsibility for the deletion. An error rate is inevitable as we're dealing with humans, but that does not mean that the errors themselves are anything other than significant, and the absolute number of errors is equally important to the error rate (10 incorrect speedy deletions out of 100 are equally important as 10 incorrect deletions out of 1000; and both rates are unacceptably high). No speedy deletions are trivial. Some G6 deletions (specifically: obvious errors that were quickly corrected, empty maintenance categories, redirects with trivial history in the way of page moves) and some G7 and U1 deletions (specifically: those with a trivial history and no significant current content) have a low potential for harm but even they are not trivial. Thryduulf (talk) 10:13, 23 May 2019 (UTC)[reply]
  • I found it totally incredible that the deletion review should grow to such length. A redirect such as Badnam Song would only come to my attention because it had a speedy tag on it (or was closely connected to another speedy candidate). In this case the relevant edits for Badnam Song are:
  • 2019-05-16T07:04:49 . . CptViraj 80 bytes ({{Db|Wrong Redirect! Not Useful!}})
  • 2019-05-16T01:44:05 . . Meatsgains 44 bytes (Meatsgains moved page Badnam Song to Badnam (song))
The ones for Badnaam Song are effectively identical: same mover and same speedy tagger.
But in this case, I totally deny doing anything "wrong": it was simply a normal editorial dispute. Instead of starting the discussion, the person who objected to my deletion could have simply re-instated either or both redirects with an edit summary of "RHaworth, I think this should be kept". I would have taken no further action. — RHaworth (talk · contribs) 10:21, 23 May 2019 (UTC)[reply]
Yes, well, like it or not people are gunning for you now so it might be wise to be super pedantic about crossing every t and dotting every i for a while. Reyk YO! 10:55, 23 May 2019 (UTC)[reply]

A10 in user space

Is A10 valid in the user space? I've seen this happen a lot, e.g.

WP:FAKEARTICLE? --Drm310 🍁 (talk) 19:12, 23 May 2019 (UTC)[reply
]

@Drm310: A10 only applies to articles. U5 does not apply to stuff that would look like an article. I asked the user on their talk page. Feel free to blank or MfD it. CoolSkittle (talk) 19:20, 23 May 2019 (UTC)[reply]
A10 is meant for cases when someone accidentally creates an article on a topic that already exists, not if someone copies an article and gives it a different name. Such cases are often either 1) people using a previous article as a template for their draft, 2) test edits or 3) cases of U5. The best approach is probably simply asking the user why they did so and explaining to them how drafts are supposed to work. Regards SoWhy 19:20, 23 May 2019 (UTC)[reply]
(edit conflict) Absolutely not. User space may only be tagged with G and U criteria; the A criteria apply only to article (main) space. --Redrose64 🌹 (talk) 19:22, 23 May 2019 (UTC)[reply]

Edits welcome to new post-CSD notices

As mentioned last month at AN, I'm (slowly) working on adding to Twinkle the ability for sysops to automatically notify users upon CSD deletion. I've created the corresponding templates, and wanted to make folks aware of them so it's not just me writing them. They were all created based on their corresponding "db-criterion-notice"(with minimal tweaks) and are named similarly, as "db-criterion-deleted." You can find them all at Template:Speedy deletion deleted, but I've included a table below for convenience, which includes each new template alongside its corresponding original notice (and any related templates). Also included are diff links to compare the two, so you can see what I changed.

Template table
Criterion New "Deleted" template Notice and related templates
G1
{{db-nonsense-deleted}} - diff )
G2
{{db-test-deleted}} - diff
Template:Test-warn-deletion(edit talk links history
)
G3
{{db-vandalism-deleted}} - diff
talk links history
)
G4
{{db-repost-deleted}} - diff
talk links history
)
G6
{{
db-copypaste-deleted}} - diff
talk links history
)
G10
{{db-attack-deleted}} - diff
talk links history
)
{{db-negublp-deleted}} - diff
talk links history
)
G11
{{db-spam-deleted}} - diff
Template:Spam-warn-deletion(edit talk links history
)
{{db-spamuser-deleted}} - diff
talk links history
)
G12
{{db-copyvio-deleted}} - diff )
G13
{{db-draft-deleted}} - diff
talk links history
)
G14
{{db-disambig-deleted}} - diff
talk links history
)
A1
{{db-nocontext-deleted}} - diff
Template:Empty-warn-deletion(edit talk links history
)
A2
{{db-foreign-deleted}} - diff
talk links history
)
A3
{{db-nocontent-deleted}} - diff
talk links history
)
A5
{{db-transwiki-deleted}} - diff Template:Db-transwiki-notice(edit talk links history)
A7
{{
db-notability-deleted}} - diff
)
{{db-bio-deleted}} - diff
talk links history
)
{{db-band-deleted}} - diff
talk links history
)
{{db-club-deleted}} - diff
talk links history
)
{{db-inc-deleted}} - diff
talk links history
)
{{db-web-deleted}} - diff
talk links history
)
{{db-animal-deleted}} - diff
talk links history
)
{{db-event-deleted}} - diff
talk links history
)
A9
{{db-a9-deleted}} - diff
talk links history
)
A10
{{db-a10-deleted}} - diff
talk links history
)
A11
{{db-invented-deleted}} - diff
talk links history
)
R2
{{db-rediruser-deleted}} - diff
talk links history
)
R3
{{db-redirtypo-deleted}} - diff Template:Db-redirtypo-notice(edit talk links history)
R4
{{db-redircom-deleted}} - diff Template:Db-redircom-notice(edit talk links history)
F1
{{db-redundantimage-deleted}} - diff
talk links history
)
F2
{{db-noimage-deleted}} - diff
talk links history
)
F3
{{db-noncom-deleted}} - diff
talk links history
)
F7
{{db-badfairuse-deleted}} - diff
talk links history
)
F9
{{db-imgcopyvio-deleted}} - diff
talk links history
)
F10
{{db-badfiletype-deleted}} - diff Template:Db-badfiletype-notice(edit talk links history)
C1
{{db-catempty-deleted}} - diff
talk links history
)
U3
{{db-gallery-deleted}} - diff Template:Db-gallery-notice(edit talk links history)
U5
{{db-notwebhost-deleted}} - diff
talk links history
)
T2
{{db-policy-deleted}} - diff Template:Db-policy-notice(edit talk links history)
T3
{{db-t3-deleted}} - diff Template:Db-t3-notice(edit talk links history)
P1
{{db-p1-deleted}} - diff Template:Db-p1-notice(edit talk links history)
P2
{{db-emptyportal-deleted}} - diff Template:Db-emptyportal-notice(edit talk links history)
Other {{db-reason-deleted}} - diff Template:Db-reason-notice(edit talk links history)
{{db-deleted-multiple}} - diff
talk links history
)
{{Db-csd-deleted-custom}} - diff
talk links history
)
{{CSD-deleted}} - diff Template:CSD-warn(edit talk links history)

A good portion of the language is handled by {{db-deleted}} and {{db-deleted-multiple}}, a la {{db-notice}} and {{db-notice-multiple}}, respectively, so those should certainly be edited to your heart's content. One particular area I was unsure of was the language around contacting the deleting administrator. I've written it to be neutral, to match the language in the notice templates, as well as since in the future these needn't necessarily be placed by the individual deleting the page in question, but would welcome feedback on that front. The notice for G6 copypaste merely redirects to Template:Db-copypaste-notice, which is itself mostly a wrapper for {{uw-c&pmove}}.

Additionally, Twinkle tagging and notification for F4, F5, F6, and F11 is handled by the di module, not the csd. As such, my intent is not to provide deletion notices for those criteria. F4, F6, and F11 specifically state that deletion may be seven days after notification, so there seems no need for duplicate notifications. F5 does have an "immediate" option, but {{

Di-orphaned fair use-notice}}). I did create versions of these templates, though, in case reviewing language would help decide (F4, F5, F6, F11). ~ Amory (utc) 19:49, 25 May 2019 (UTC)[reply
]

Draft tests

Can junk drafts be speedied? These were created by 75.97.183.77 (talk · contribs).

What about {{

db-test}}, or should they just be left for six months? Johnuniq (talk) 08:05, 26 May 2019 (UTC)[reply
]

WP:CSD#G2 (test pages) doesn't exclude draft space, but before applying it there you need to determine why deleting it sooner than G13 allows will benefit the encyclopaedia. In this case, the pages seem harmless so I don't see any reason why they shouldn't be left for G13. Thryduulf (talk) 11:48, 26 May 2019 (UTC)[reply
]
OK although my feeling about junk is that it accumulates and it would better to remove it on sight. However, I agree that arguments about whether a particular draft is or is not junk would probably be unproductive. No doubt some other reason to delete a draft could be found if someone kept adding meaningless stuff to the above. Johnuniq (talk) 05:16, 27 May 2019 (UTC)[reply]
If you think there is a reason and benefit to deleting any page in draft space sooner than G13 allows then nominate it at MfD. Thryduulf (talk) 07:40, 29 May 2019 (UTC)[reply]

Deletion of redundant (disambiguation) redirects

I have been tagging as G8 a number of "Foo (disambiguation)" redirects where they target a page that is not a disambiguation page. They exist, for instance, where the second entry at a two-entry disambiguation page at the base name has been deleted, and the other use is moved to the base name, but without the (disambiguation) redirect having been deleted. It's really a housekeeping exercise: these pages are orphans, useless, and not controversial (I would not nominate a "controversial" redirect from, for instance "Foo (disambiguation)" to "Foo (name)").

Some admins are happy to delete these redirects (@Anthony Bradbury:, @Nabla:, @RHaworth:, @Michael Greiner: thank you, by the way), although sometimes they're actually deleted as G6 or G14. One @Smjg: has suggested G6 is a better classification. One (@Jo-Jo Eumerus:) has removed the speedy tag and suggested RfD. Whether they're deleted as G6, G8, or G14 is a diversion: what's important is that they're deleted. The redirects are, using the language of G8, "redirects to invalid targets".

Can I please suggest an additional explanatory bullet at G8 "Examples include":

  • Orphan "Foo (disambiguation)" redirects that target pages that are not disambiguation pages or pages that perform a disambiguation-like function (such as name SIAs or lists).

Shhhnotsoloud (talk) 09:31, 9 June 2019 (UTC)[reply]

After looking after some of these deletions, perhaps it should be deleted under
WP:CSD#G6; that's the normal route for maintenance deletions. Jo-Jo Eumerus (talk, contributions) 09:40, 9 June 2019 (UTC)[reply
]
  • Agree Holsworthy (disambiguation) was declined with R3 (which I though included such redirects that point to non-DAB pages). Crouch, Swale (talk) 19:13, 9 June 2019 (UTC)[reply]
  • I agree (has my 2 deletions say :-). It should be clear that if and only if the target is not a disambiguation in any (broad) away then it is a good speedy delete candidate. I think the proposed tet makes it clear. I think G8 is more logic, but G6 is not bad either. - Nabla (talk) 21:21, 9 June 2019 (UTC)[reply]
  • If a redirect targets a page that exists then it is not a G8 candidate under any circumstances. The only speedy deletion criterion that applies to unnecessary disambiguation pages is G14 - if it isn't covered by that criterion then it should not be speedy deleted. Thryduulf (talk) 18:05, 10 June 2019 (UTC)[reply]
  • I would support that bullet point added under G6 because it's a housekeeping deletion and I think it would nicely fit with the other bullet points currently there. I'd also support G14 if we want to keep all disambiguation-related deletions together. R5 would even work. G8 is more of a stretch because the target page does exist (G8's redirects to invalid targets might need tightening if that's the argument). -- Tavix (talk) 20:01, 10 June 2019 (UTC)[reply]
    I think it falls under G6 (and indeed per Thryduulf not G8) but I suppose it could indeed be bundled with G14 (or R3). Crouch, Swale (talk) 20:09, 10 June 2019 (UTC)[reply]
    It definitely would not fall under R3 because (disambiugation) redirects are almost always not recently created, so that would be either too much of a restriction or too different from the criterion definition to fit. -- Tavix (talk) 20:17, 10 June 2019 (UTC)[reply]
    R3 could specifically have (disambiugation) redirects that target non dab pages regardless of age but I'd agree that G6 would be better. Crouch, Swale (talk) 20:20, 10 June 2019 (UTC)[reply]
    G6 is already overloaded so we really shouldn't be adding more stuff to it (it's part of why G14 and R4 were split off recently). Adding it to R3 wouldn't make sense as "recently created" is the fundamental part of that. If we need to speedy delete any of these redirects that don't already fall under G14 then we should be either expanding G14 slightly or adding a new criterion for them, but either way we need to exclude cases where there is a (different) target that is a dab page or something similar (e.g. set index). As for tightening the invalid targets section of G8, yes I'm all for that. Thryduulf (talk) 20:39, 10 June 2019 (UTC)[reply]

Modified proposal

Given the comments above that G6 is overloaded and G8 may not be appropriate, but no objections so far to the principle, may I suggest an addition to G14: "G14 also applies to orphan "Foo (disambiguation)" redirects that target pages that are not disambiguation pages or pages that perform a disambiguation-like function (such as name SIAs or lists)." Shhhnotsoloud (talk) 13:38, 14 June 2019 (UTC)[reply]

  • Support per the above. -- Tavix (talk) 14:11, 14 June 2019 (UTC)[reply]
  • Support. Note that I have deleted hundreds if not thousands of these historically using G6, though I stopped when I noticed some objection to deleting them via an RfD, I forget which. As I said then, the vast majority of these redirects are created by bots, and will never be used by a human. —Xezbeth (talk) 14:38, 14 June 2019 (UTC)[reply]
  • Support, although I'd prefer "set index articles" or "set indexes" to "SIAs" and I don't get why it's restricted to just name set indexes? Thryduulf (talk) 15:02, 14 June 2019 (UTC)[reply]
  • Question: Is this a proposal to allow speedy deletion of pages that end with the word "disambiguation" and are not acting as disambiguation pages? If that's the case, then I would support the proposal, but the verbiage needs to be cleaned up, because I personally do not understand the meaning of the proposed verbiage (hence I began this comment with the word "question", as opposed to either the word "support" or "oppose"). Banana Republic (talk) 15:48, 15 June 2019 (UTC)[reply]
Sounds to me like this proposal should be listed as an R5, rather than a G14, as it is specific to redirects. Banana Republic (talk) 19:13, 15 June 2019 (UTC)[reply]
It could fit as R5 but as it's entirely complimentary to G14 (disambiguation pages that don't disambiguate) it also fits as part of G14. I have no preference between the two. Thryduulf (talk) 20:53, 15 June 2019 (UTC)[reply]

Tightening G8 with respect to redirects

The bullet point for G8 regarding redirects currently reads: "redirects to invalid targets, such as non-existent targets, redirect loops, and bad titles". I propose changing that to just "redirects to non-existent targets" as the others are not needed. The section above also shows that these are currently causing confusion.

Redirect loops can mean either:

  • A page redirecting to itself - these will almost always be pages created in error (G6), test pages (G2) or vandalism (revert or G3). In the few remaining cases it is probably someone trying to create a valid redirect and RfD is the place to determine where it should point if the correct target is not obvious.
  • A page redirecting to a page that redirects back to it (A → B → A) - these are usually going to be the result of a page move and the correct solution is almost always not deletion but retargetting to where the content now is (i.e. retargetting A and B to point to C). If this is not obvious then again RfD is the place to discuss them. It's also possible that some could be the result of errors (if they can't be fixed then they can be deleted under G6 already).

"Bad title" is very ambiguous:

  • Many, perhaps most, titles that are "bad" (i.e. are incorrect or do not conform to naming conventions) are actually good redirects and so should not be deleted.
  • Redirects to titles that don't or can't exist are already covered by "redirects to non-existent targets".
  • Some redirects do not work (e.g. to special pages, see
    User:Thryduulf/R to special
    ) and function as soft redirects, the consensus regarding these is that they should be either left as is or changed to be explicit soft redirects not deleted.
  • A proposed as a CSD criterion for redirects to foreign language projects was rejected so these should not be speedily deleted. T
  • Anything else should be discussed at RfD (e.g. there was a redirect discussed not too long ago with a title that worked only in some circumstances - I can't immediately remember the details but I believe it was kept).

"Invalid targets" is also ambiguous so if there are any instances not covered by "non-existent targets", G2, G3 or G6 where deletion is always required they should be explicitly added to an existing criteria or a new criteria created that meets the

WP:NEWCSD requirements. Thryduulf (talk) 21:21, 10 June 2019 (UTC)[reply
]

  • Seems to jive well with
    ed. put'r there  15:30, 11 June 2019 (UTC)[reply
    ]
  • Support proposed reduction in scope. As well reasoned by Thryduulf, redirect loops are most likely fixable.
    To be honest, I don't think I even understand what does it mean to redirect to a "bad title". A page can be redirected to either an appropriate existing page, an inappropriate exiting page, or to a non-existing page. If a page is redirected to an existing page, and other speedy deletion criteria specific to redirects are not met, then it should be discussed whether the redirect is appropriate. I do want to note that this discussion is mostly academic. Since redirects are easy to create, if a redirect is erroneously speedily deleted, it's not very difficult to re-create the redirect. Creating a redirect takes less than a minute. Banana Republic (talk) 15:31, 15 June 2019 (UTC)[reply]
  •  Done after a week with two supports and no objections I've made this change.[6] Thryduulf (talk) 18:46, 18 June 2019 (UTC)[reply]

Ambiguity in G11

Current version of the page has this sentence in criteria G11 If a subject is notable and the content could plausibly be replaced with text written from a neutral point of view, this is preferable to deletion.

Seems to me that the word "this" is ambiguous, and it would be better to replace the fragment this is preferable to deletion with rewriting would be preferable to deletion. Banana Republic (talk) 15:36, 14 June 2019 (UTC)[reply]

I'm neutral about "this" vs "rewriting" but "is" is significantly better than "would be". Thryduulf (talk) 15:38, 14 June 2019 (UTC)[reply]
It's just grammar. Because this phrase is inside a conditional statement (the sentence begins with "if"), "would be" is more appropriate than "is". Additionally, the word "preferable" already implies that the action is not mandatory, so it is not compatible with the word "is", which does make it sound mandatory. Banana Republic (talk) 15:45, 14 June 2019 (UTC)[reply]
It's not about mandatory/not mandatory (although it is very strongly preferable) it's about tense. It is preferable in the present tense, not would be preferable in the future tense. Thryduulf (talk) 17:37, 14 June 2019 (UTC)[reply]
The verb "be" is present tense. Therefore "would be" is present tense. See this reference, for additional details. Banana Republic (talk) 23:33, 14 June 2019 (UTC)[reply]
Agree "this" is ambiguous, and conditionals are usually "If..., then..." types. "This" should be changed to "that", as in "If a subject is
ed. put'r there  08:42, 15 June 2019 (UTC)[reply
]