Wikipedia talk:Criteria for speedy deletion/Archive 9

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Archive 5 Archive 7 Archive 8 Archive 9 Archive 10 Archive 11 Archive 15

IP talk pages

I just saw User:Tawkerbot add a Talk:IP that I watch to Category:IP talk pages for speedy deletion. It refers to WP:CSD#U2 on this page:

Recycling IP pages. User talk pages of non-logged in users where the message is no longer relevant. This is to avoid confusing new users who happen to edit with that same IP address.
  1. Adding the category sends them a "new messages" box, doesn't it? If this is to avoid confusion, then any list of to-be-deleted pages should be managed externally, not through category edits to the talk pages.
  2. Is deleting the pages going to be at all necessary in the first place? I think the history of an IP may present useful information. After all, the edits of those IPs are preserved in the edit history. The related warning messages should be too, even if years old.

Shouldn't irrelevant old messages simply be removed by blanking the page (thus essentially archiving it)?

Femto 12:58, 3 March 2006 (UTC)

In reference to your second point, I've always thought that CSD criteria U2 was odd for the same reason, i.e. old IP talk pages should simply be blanked. That fulfils the stated purpose of avoiding confusion for new users of that IP address, whilst also keeping the history of the page if needed. Petros471 13:44, 3 March 2006 (UTC)
Femto's propositions and resolution seem perfect. Any objections?? --Gurubrahma 13:50, 3 March 2006 (UTC)
I have no objections to blanking, it probally is easier on the admins too (those 2500 pages are less than 1% of the bots run) -- Tawker 19:30, 3 March 2006 (UTC)
After giving this some thought, page blanking would be much preferred over speedy deletion of a talk page. Some of our best vandal fighters are anonymous editors, and if we delete these pages outright, they and other non-administrators will have no way of to telling if there is any relevant history associated with a recurring vandal. Best regards, Hall Monitor 19:46, 3 March 2006 (UTC)
I agree; blanking makes a lot more sense. android79 19:49, 3 March 2006 (UTC)
Likewise here, blanking is better, and asked a few other admins as well, there's no need of deletign the talk page (and thus hiding its history). I'm removing U2 since consensus seems to be that blanking is better. -- ( drini's page ) 20:06, 3 March 2006 (UTC)
Yep. Mainly because I think it's impossible to determine when an IP talk page message has become "irrelevant"; I've often seen IPs repeat the exact same kind of vandalism after gaps of several months or more. Postdlf 20:44, 3 March 2006 (UTC)
Also, tawkerbot has been adding this to user pages with useful templates on them such as User talk:, which has an informational sharedip template. --DDG 22:41, 6 March 2006 (UTC)
Why were we deleting in the first place? Blanking makes so much more sense. In fact, we could probably add a header that says something like "This IP Talk page has been/is periodically recycled by blanking. To see older comments, please view the (link to history page)history(/link)." We'd need some good constraints on what constitutes a talk page that needs to be recycled though, to avoid unscrupulous vandals blanking their talk pages to hide previous warnings. Werdna648T/C\@ 08:26, 7 March 2006 (UTC)
Users blanking their own talk page (when it contains warnings) is generally considered vandalism anyway, I don't see why this should change. Talk pages should only be blanked by RC patrollers and include a good edit summary for reference. Petros471 11:02, 7 March 2006 (UTC)

I can only echo the sentiments expressed above. It makes no sense to delete (rather than blank) IP talk pages, and I just noticed that Tawkerbot tagged my college's talk page (which only contained a notice identifying the IP address as a shared entity and advising users to register accounts) on 3 March (the day on which this discussion began). —David Levy 14:51, 14 March 2006 (UTC)

Proposal for blantantly unencyclopedic articles

I want to propose CSD A9, which states

9. A page that is blatantly unencyclopedic, i.e.:

    • Clearly a blog
    • A discussion of what happened in school
    • An obvious hoax, including facts that are impossible to happen in reality
    • An attempt to start up a website on a Wikipedia page

-- King of Hearts | (talk) 19:53, 5 March 2006 (UTC)

The term "unencyclopedic" is too vague. Also, some blogs are clearly notable. —Guanaco 20:00, 5 March 2006 (UTC)
I suspect (correct me if I'm wrong) that King of Hearts means a page being treated as a blog, rather than an encyclopedia article about a blog. Right? Matthew Brown (Morven) (T:C) 08:23, 6 March 2006 (UTC)
I agree with this CSD 9. It seems to imply one thing that I like: topic's merits=/=article's merits. One problem is that a BS article on a worthy topic is kept as a "potentially good article" and then nobody does anything (fixes it). Either fix it now, get a taskforce, or delete it and put it on Request for Creation, but please lets not just leave blogs here. And when he said blog, I think that he meant the article IS a blog, not about a blog.Voice-of-AllT|@|ESP 20:02, 5 March 2006 (UTC)
Yeah, by "blog" I meant some guy writing a blog on Wikipedia; basically almost everything that has nothing to do with writing an encyclopedia. -- King of Hearts | (talk) 01:21, 7 March 2006 (UTC)
Absolutely not. Again, the more we speedy, the less chance encyclopedic topics can be reviewed by other authors and fixed, even if they're being used incorrectly to start. {{prod}} is perfect for this. --badlydrawnjeff (WP:MEME?) 03:08, 7 March 2006 (UTC)
I'm with King of Hearts on this one, except I'd reword it as "Articles that are blatantly and unredeemably not suitable for an encyclopaedia". Basically, a page in articlespace that is not an article. This could cover Resumes (most of these can be speedied under A7 anyway, but for the resume of a notable person we need something), source texts, instruction manuals, et cetera. Interestingly enough, perhaps many of these should be "speedy transwikied", as many of these types may not be useful on Wikipedia, but may be interesting on Wikibooks, WikiSource, et cetera. An interesting proposition, but one that needs to be objectively defined. Werdna648T/C\@ 08:18, 7 March 2006 (UTC)
Speedy-transwiki used to be the normal interpretation of transwiki. Any page that was moved from one WikiMedia project to another was not considered "deleted" because it could easily be recovered (by transwiki in reverse) with no loss of content or history and without the use of any special administrator powers. The leftover page in the source project was immediately deleted by default unless there was a compelling reason not to. In fact, that was the origin of speedy-deletion case A2. It standardized what had already been the existing practice. (The case is worded specifically to the foreign language projects but remember that at that time the only other WikiMedia projects were the alternate language encyclopedias. We hadn't yet created Wiktionary, WikiSource, etc.) Over time, that meaning got lost and people began to believe that we had to both transwiki and go through a formal deletion process to get rid of the leftover. I would like to return to the original interpretation of the transwiki process. Rossami (talk) 20:26, 7 March 2006 (UTC)

I just reverted this addition. I did not think this discussion ended in a consensus to use this, otherwise I'd've expressed my opposition while it was current. I just don't see having so many speedy criteria that I can't memorize them. Use prod. NickelShoe (Talk) 05:49, 18 April 2006 (UTC)

I was trying to revert this addition, but NickelShoe beat me to it. I think the criteria is to vague. Also, now that we got PROD, we have an effecient way of eleminating obvious cases, that don't fit a speedy criteria. -Rob 06:06, 18 April 2006 (UTC)
This is too subject to interpretation to be of any use. And indeed, as Rob says, {{subst:prod}} is perfect. Stifle (talk) 10:15, 28 April 2006 (UTC)

Propose to change template db-empty

Please see this proposal to add the A3 reasons to the db-empty template here. cmh 06:19, 9 March 2006 (UTC)

Speedy deletion of image uploaded for speedily-deleted article?

What we do for orphan images which were obviously uploaded solely for an article which has now been speedily deleted? In particular I mean this one which was only placed on a non-notable vanity page, now deleted. Do we speedy these images too? And should we consider adding this as an explicit speedy deletion criterion for images? --RobertGtalk 17:07, 9 March 2006 (UTC)

I generally use common sense and just speedy them. Unless they are definitely free images. Those *might* some day be of conceivable use, so it's probably best to leave them alone. Johnleemk | Talk 17:16, 9 March 2006 (UTC)
Huh. I'm surprised this isn't already a CSD. It seems relatively non-controversial an idea (though I've always been surprised at what turns out to be controversial). What's the proposed language? Something like "Pictures which were used or explicitly intended for use on pages that have been speedily deleted, and which have no reasonable use on undeleted pages"? (Obviously, tweak as you will...) Of course, Johnleemk is right: common sense typically does prevail here. JDoorjam Talk 17:20, 9 March 2006 (UTC)
Yes, I thought it was common sense, and I'm pleased to see others agree. If no-one objects, I propose tweaking JDoorjam's wording thus: "Images used on speedily deleted pages may themselves be speedily deleted if they are of little encyclopedic value" which removes the requirement to guess at the uploader's motives. Meanwhile, I'll speedily delete the image in question per Johnleemk! If this gets approval I'll add it as a criterion some time next week (unless someone else gets there first). Thanks. --RobertGtalk 17:52, 9 March 2006 (UTC)
That image looks like a probable copyvio anyway. While I'm not opposed to a more general criterion such as suggested by JDoorjam above, simply waiving the seven-day requirement of I4 and I5 for "images uploaded for use in a deleted article" would probably suffice in most cases like this. Generally, if an image is free and properly sourced, we might as well let it be and see if anyone finds a use for it. —Ilmari Karonen (talk) 17:59, 9 March 2006 (UTC)
If they're fair use, then there's already {{subst:orfud}} to deal with them. If they're free use, then they should probably go to IFD, but I don't see any real objections to people WP:IARing. Stifle (talk) 09:09, 12 May 2006 (UTC)

Porposal for expansion of Articles item #7

I've just been told that an article dealing with obscure elements of popular fiction which have no notability on their own are not speediable. I've re-read the criteria, and shockingly, I have to agree. To address this terrible loophole that allows for torrents of non-notable cruft, and yet allow for "valid fancruft" which is notable in its own way, I propose the following ammendment:

Unremarkable real people or groups. An article about a real person, group of people, band, or club that does not assert the importance or significance of its subject. If the assertion is disputed or controversial, it should be taken to AFD instead.
Unremarkable fictional subjects. The determining factor between remarkable and unremarkable fictional subjects is the question of notability relative to the genre or work from which they arise. Non-notable subjects would include characters or places in a story which have no impact on its plot or the establishment of the setting or tone of the story. However, if the article title refers to a discrete character, event or setting, it may be of value as a redirect. If this is the case, the article should be merged and redirected to the appropriate work of fiction rather than deleted.

Without this additional criteria, the door is left wide open to waste the time and effort of those debating truly controversial notability of other articles in the AFDs. It also wastes the time of those who, like myself, attempt to patrol new articles. -Harmil 19:36, 9 March 2006 (UTC)

Or, you could see if it has no chance of becoming more than a worthless stub and merge with the article for the work of fiction, or you could use {{prod}} to see if anyone's capable of expanding. Why rush to speedy? --badlydrawnjeff (WP:MEME?) 19:48, 9 March 2006 (UTC)
Actually, you bring up a valid point, and I'll modify the above inline to reflect it. However, as an example of an article which explains my point, see Typical Earth Alliance Permanent Space Colony. I'm almost tempted to request a new criteria: so many separate violations of Wikipedia policy that cleanup would present a serious mental health risk. ;) But aside from my distaste for the article, it is clearly about a topic which, even as a redirect, would have no value for Wikipedia. -Harmil 20:12, 9 March 2006 (UTC)
What makes you think it holds no value? Genuinely curious. I dunno, I just feel like we're looking for excuses to speedy stuff, as opposed to fixing these things. Fictional information only exists via a fictional universe, and most works of fiction that would have individual articles for characters, major and minor, would at the very least have a page for its source material to redirect to. The smaller ones can be redirected to that article or to a list of characters, the larger ones kept. Speedies just tend to create ill will and warring, when a redirect with merging worthwhile info keeps the info and discourages recreation. --badlydrawnjeff (WP:MEME?) 20:29, 9 March 2006 (UTC)
I'm with BDJ on this one. I find that crufty stubs (which sounds like a skin condition) are better as redirs if the articles don't warrant standing on their own. JDoorjam Talk 20:23, 9 March 2006 (UTC)
I have to agree that it's sily to speedy them. Just redirect. I don't see what the deal is with people wanting to speedy delete everything, like it's the end of the world if it exists as a redirect or takes five days to get rid of. NickelShoe 21:34, 9 March 2006 (UTC)
I agree with Jeff as well; redlinks encourage recreation of crufty stubs (how's that for a medical condition?), whereas redirects encourage people to find the main article. -- nae'blis (talk) 23:22, 9 March 2006 (UTC)
Tooootally already made that joke three postings ago. ;-) JDoorjam Talk 23:34, 9 March 2006 (UTC)
First off, I think someone very much missed the point. I know that there's a lot of the same coversations over and over here, so I imagine it's easy to assume that you can categorize any request and give a standard answer. However, you've missed the mark here. We're not talking about deletions that would cause redlinks here. Let's throw out some examples. I might create a page called, Earth Alliance Space Colony. Ok, now that clearly meets the above criteria for redirecting. It's just not terribly notable within the genre nor impacting on the plot of the show (though there are specific colonies that are notable and have pages, as they should), but it's something that people might link to or otherwise reference. On the other hand, Typical Earth Alliance Permanent Space Colony is not referenced external to Wikipedia. It borders on (but isn't quite) original research. We could create hundreds of thousands of this sort of article per genre, I'm sure, but they have no encyclopedic value, even as redirects (since no one is going to be looking for that name). Next: to the point of hyperbole. I do not "want to speedy delete everything, like it's the end of the world if it exists as a redirect or takes five days to get rid of." Please lay off the hyperbole and evaluate suggestions on their own merits and the contributions of their suggestors. Thanks. As for the question of why speedy vs. AFD/prod? I like to think that we involve the community for articles where their value is in dispute (or could be), not just to serve as a distraction. How many users respond to the average {{prod}} these days? How many {{prod}} are added on a typical day? Could a user reasonably visit and read them all? half? -Harmil 21:26, 11 March 2006 (UTC)
If it borders on OR, then start hunting people down who can give sources? The more we use prod, the more people will respond and the more useful it becomes. No need to speedy most stuff whe it can be prodded. --badlydrawnjeff (WP:MEME?) 23:21, 11 March 2006 (UTC)
I have to say that the page given as an example, Typical Earth Alliance Permanent Space Colony, is a perfectly valuable and valid Wikipedia and I personally have no problem with it remaining on the site. John Coxon 13:56, 28 April 2006 (UTC)

neologisms / protologisms

I see that this has been discussed before, but without apparent result / consensus.

I'd like to add a CSD criteria to make articles about unambiguous protologisms / neologisms speedyable. This would not include new words with very limited usage. I'd like it to focus only on the various "this is a word we made up last Friday" or "we're trying to get this word into common parlance" type articles.

I don't know if this needs a brand-new section, it could easily be a subsection of CSD/A7, a la CSD/A7(1).

Basically, without causing instruction creep, I'd like to avoid having prolonged debates on WP:AFD about clearly unremarkable and unused new words, of the type that are caused by words made up on Internet forums, and defended solely (but extensively) by forum denizens. Policy shouldn't require a week of that :)

The language I'd like to add is something like:

  • Neologisms: Articles clearly created for the sole purpose of injecting a new word into circulation, that do not assert the importance or common usage of the word.

What say you? — User:Adrian/zap2.js 23:22, 10 March 2006 (UTC)

I still think this would be better handled by prod. There's enough quibbling on some words that might be notable where I think speedying is a poor idea. --badlydrawnjeff (WP:MEME?) 00:44, 11 March 2006 (UTC)
I have to disagree. The description calls only for the speedy deletion of words that are unambiguously non-notable or contrived. {{prod}} and WP:AFD would remain the venues of choice for controversial deletions, as is right and proper. This wouldn't make speedy deletion of questionably notable / legit words a discretionary function.
User:Adrian/zap2.js 01:19, 11 March 2006 (UTC)
And I'm saying that speedying tends to bite newcomers that may not be aware of our notability standards, as well as doesn't allow for the possible expansion of articles that don't initially look notable. prod is for uncontroversial deletions, not controversial ones, and if a word is truly non-notable and worthless, it'll get deleted as such. --badlydrawnjeff (WP:MEME?) 01:45, 11 March 2006 (UTC)
Thank you for your feedback. There's a balance between not biting newcomers and maintaining an orderly community. If the priority was *always* to avoid displeasing newcomers, we wouldn't speedily delete anything at all. Your arguments work against every speedy deletion criterion, but the existence of WP:CSD in the first place is a nod to the needlessly laborious nature of some elements of deletion process. Since you've evidently put some thought into this, I'd be interested in your take on why plainly nn people or organizations have speedy deletion criterion, but words don't. Cheers! :)
User:Adrian/zap2.js 02:40, 11 March 2006 (UTC)
Ah. I note now your generalized opposition to multiple parts of WP:CSD, per your userpage. If you have thoughts on this that aren't raised there, I'd still like to hear them, but I'd be more interested in your feelings on the question: If words *had* to be included in WP:CSD, what would be the least harmful way to do it?
Thanks! — User:Adrian/zap2.js 02:50, 11 March 2006 (UTC)
The problem is that I disagree with the premise outright. Certainly, CSD is useful in SOME cases, but it should never be used for things that may be notable or may not have proper sourcing and could be better served by a larger community review. Save CSD for nonsense, for libel/slander issues. --badlydrawnjeff (WP:MEME?) 14:22, 14 March 2006 (UTC)
Good idea. I don't see why we can speedy NN people and not equally-obviously NN words. --Fang Aili 20:17, 11 March 2006 (UTC)

Personally I'm in favor of a general increase in ease of deletion; obvious neo/protologisms should easily fit the bill. In the mean time though, {{prod}} should be more than sufficient. --Cyde Weys 21:22, 11 March 2006 (UTC)

Handling it by PROD should be good enough. Also, it is difficult to say a priori as to what a notable neologism is. For example, I have seen the word "" used many times on en-wiki mailing list. Had I not been on the mailing list, I would not have come across that word and would have probably speedied the article, if the rules ncluded that. Thanks to the exposure I got to the word on the mailing list and to my subsequent secondary research, I have started it instead. --Gurubrahma 10:52, 14 March 2006 (UTC)
Having read it, I believe that you should not have started that article in Wikipedia. It is an entry about a word, not a real company or a broad social concept. What you have is a definition that belongs in our sister project, Wiktionary. I mention it not to criticize your motives but because that has been true in essentially every neologism case that I've reviewed. They are articles about words (or sometimes phrases). They cause controversy in Wikipedia but would have been perfectly acceptable in Wiktionary. I believe the right answer should be to transwiki any neologism article to Wiktionary and immediately delete (or redirect) the Wikipedia version.
Note: Wiktionary does not keep protologisms but they are better equipped to make the determination when a word is reaching wider acceptance. Rossami (talk) 14:53, 14 March 2006 (UTC)

I'm be a little hesistant about adding this because, based on various AFDs, even experienced editors don't fully grasp Wikipedia's policy on neologisms. I'm not against a CSD for it, but it should be very, very explicit. I'd say at the minimum it should have no Google hits outside of Wikipedia and its mirrors before being speedied. Turnstep 04:35, 19 March 2006 (UTC)

New image criteria proposal

Hi all. While working on the untagged images project, I've come across a number of images that were uploaded to the Commons, and then had their description page here modified. In some cases, this is warranted, such as adding the image to a category on Wikipedia. However, occasionally there are images (for example, Image:Platform Sandal wood Buffalo brown.jpg) whose description page replicates the Commons description, or does not include any new information.

I think that we should add a criteria for speedy image deletion that would allow administrators to delete such images (presuming that they would look through the history and ensure that there hadn't been any vandalism, removing categories and such) since I can't really think of any reason not to delete them. Thoughts? ~MDD4696 22:40, 27 March 2006 (UTC)

That particular image is a special case: it has never been uploaded to enwiki. The image is only present on Commons and the page here is redundant entirely. I have deleted it since having, effectively, a fork locally means that any updates to licensing/soucing/wording will not appear here. That is bad for obvious reasons. Perhaps this very particular case needs a CSD to make it clear, or perhaps it's just occasional enough that (what I hope is) common-sense is enough. Note that what I just did is very different from deleting the image: I am not able to do that, since it is not present on this project. -Splashtalk 22:53, 27 March 2006 (UTC)
Exactly. I would think that admins would know enough that it qualifies for speedy deletion, but it might help non-admins to have a specific item addressing this issue when determining whether or not to add the {{db}} tag. ~MDD4696 23:34, 27 March 2006 (UTC)

Proposed CSD

How about articles that are patently original research, and by that I mean they explicitly state that that is the case in their text? I have seen a few of these lately and they seem like common sense speedys to me. Has this been discussed before? Ramanpotential (talk | contribs) 00:02, 28 March 2006 (UTC)

Why not use {{prod}}, with a note as to why? I've seen some of these, and the authors often don't know about WP:NOR, and apologize when they find out. The trolls who post OR should probably see the consensus of AfD anyway, so they don't come back. Septentrionalis 15:58, 29 March 2006 (UTC)

Handling G7 and A3

I think admins have to be alerted that while deleting under G7 one has to make sure no other editor has edited the page, and while deleting under A3 one has to make sure that earlier versions of the article also satisfy some CSD criteria. As explained in User talk:Wavelength, List of environment topics:F-G was deleted after the page was blanked but other people (including me) had edited the page and hence it didn't fall under G7, and its earlier versions didn't satisfy A3 and are actually important to preserve the history of List of environment topics:F and List of environment topics:G. -- Paddu 09:01, 1 April 2006 (UTC)

This is in the order of "stop or I'll say stop again." Admins are already meanto to do everything contained in the new notes. If they aren't then telling them to do so again when it's written everywhere else (templates, admin how-to, etc) isn't going to help.
brenneman{L} 01:25, 4 April 2006 (UTC)

Non-notable articles

I've seen a couple of pages that I've tagged as 'db|non-notable subject' (or something more specific under subject, ie website or comic) that were rather plainly non-notable moved over to prod recently on the grounds that there is no CSD criteria. Besides the fact that I think that the basic db template exists. Moreover, the CSD criteria currently doesn't include anything on notability, despite the fact that the various A7 templates (db-bio, db-group, db-band and db-club) all argue for speedy deletion on notability grounds. This seems like a minor oversight more than anything else, but it also seems that there's room for an additional consensus to speedy delete articles that are clearly non-notable but non-human subjects under A7 as well. --DMG413 15:39, 1 April 2006 (UTC)

Notability is contnetious, and will never command general consensus as a deletion criterion nevermind a speedy one. What is notable? Is a school, a company, a church, or a verse of the Bible? Actually A7 does not allow the speeding of non-notable bios, it only allows a speedy where there is no assertion of anything which anyone might regard as notable, and other decision must be reached via prod and AfD. The following are often given as reasons for speedy, but do not qualify: 'advert' 'spam' 'not-notable' 'essay' 'rant' 'neologism' 'not on google'. Having said that, there are some obvious cases where deletion is not in doubt and admins will use common sense. --Doc ask? 15:47, 1 April 2006 (UTC)
I echo Doc, but add that WP:PROD is a good alternative to a technically invalid speedy. Most times people try to speedy delete for something not in CSD, you see where they're coming from... but those aren't speedy delete criteria for a reason. PROD gives everyone 5 days to improve the article, so there's less chance of deleting a potentially good article. It's a good choice when there's a chance the article can be improved.
Articles that genuinely assert notability generally shouldn't be speedied. The exception is obviously false claims, like "Joe Blogs was just elected King of England", etc. But something like "Joe Blogs is a famous professor" should probably not be speedied, PROD, then AfD, is a better choice ultimately. --W.marsh 16:03, 1 April 2006 (UTC)
The points above are valid, but it still remains confusing why a human subject on which there is no assertion of anything regarded as notable can be speedied but a non-human subject on which there is no assertion of anything regarded as non-notable cannot. For pages that clearly violate WP:WEB, for instance, and have no assertion to anything resembling notability, it seems reasonable to speedy them to me. I realize the uses of WP:PROD, but my concern about it is that it allows someone to come back and remove the tag a couple of days later before deletion, and unless someone is watching things very closely, it may slip through. --DMG413 22:25, 1 April 2006 (UTC)
Well that's what watchlists are for, yes? If you prod an article, put it on your watchlist if you're concerned about the idea of it not getting deleted. NickelShoe (Talk) 22:28, 1 April 2006 (UTC)
Don't forget the list of previous nominations. It's easy enough to use to keep track of previously prodded pages. howcheng {chat} 06:15, 4 April 2006 (UTC)
And Special:my contributions is useful too: If you're still the top edit 5 days after the PROD, it hasn't been fixed or removed; if you're not, go see what happened. Septentrionalis 15:15, 14 April 2006 (UTC)

G5 clarification

G5 is for banned users. But what about proven sockpuppets of permblocked users? Shouldn't they be speedied as well? (example: User:Doe, John) `'mikka (t) 20:32, 4 April 2006 (UTC)

Yes. It's the user that's banned, not the account. --Carnildo 02:40, 5 April 2006 (UTC)


Any objection to a G9 criteria for legal threats (where the only page history is legal threats). In the case where the history contains other page history that is not riddled with legal threats, it may be possible to do a full deletion/partial restore without the legal threats. —Locke Coletc 09:22, 5 April 2006 (UTC)

Sounds good in principle. We already have an "I-know-it-when-I-see-it" criterion in A7, so perhaps this wouldn't be too bad. I think there are many edits which are borderline on this rule though. (ESkog)(Talk) 11:16, 5 April 2006 (UTC)
k, I'll wait a bit more for comments before adding it. For those curious, this was suggested as a result of Wikipedia:Miscellany for deletion/User:Daniel Brandt (which was closed as delete). —Locke Coletc 20:43, 5 April 2006 (UTC)

Here's a rough stab the language I'd use:

9. Legal threats. In cases where legal threats are intermixed with good content, the page can be deleted, and then only the non-offensive revisions undeleted.

Though I suppose, if we want to cut down on instruction creep, we could just use:

9. Legal threats.

And leave it up to the acting sysop to decide how to handle it/deal with it. —Locke Coletc 21:07, 5 April 2006 (UTC)

It would be well if the language made it explicit that the intention is that articles containing legal threats can be speedied, not that an article can be speedief if somebody makes a legal threat about it. (Yes, this should be obvious, but never underestimate the stupidity of human beings). On a more general note, is this really a sufficiently widespread problem that prod/*fd cannot handle it? Henning Makholm 14:56, 6 April 2006 (UTC)
Oh I'm certain that this is uncommon enough that *FD/PROD could handle it, the idea is that people shouldn't have to wait a week (or have it put to a "poll") whether or not the page should be deleted. CSD not only makes it possible to speedy these things, it also determines that there is no need for discussion or debate. (As we wouldn't, for example, debate whether or not a page created with only the word "penis" on it should be deleted or not). —Locke Coletc 00:03, 7 April 2006 (UTC)
Needing to poll/discuss the deletion is a cost, yes. But adding a new CSD criterion is a cost too, in form of instruction creep (as then every admin patrolling the SD category would have an item more to remember). All I'm saying is that these two costs ought to be weighted against each other. Henning Makholm 00:17, 7 April 2006 (UTC)

Proposed CSD criteria for Portals

The CSD currently has no criteria for Portals, although the policy page for these states that "Portals are not appropriate for every topic. Only create portals for broad subject areas, which are likely to attract large numbers of interested readers and portal maintainers." However, we currently have on MfD Wikipedia:Miscellany for deletion/Portal:Malaysian expressway system and Wikipedia:Miscellany for deletion/Portal:Famous Slaves (both leaning heavily towards deletion as inappropriate for a Portal), and we have recently deleted Wikipedia:Miscellany for deletion/Portal:Arlington, MA and Wikipedia:Miscellany for deletion/Portal:Family Guy as too narrow (compare Wikipedia:Miscellany for deletion/Portal:Oz, kept). In Wikipedia:Miscellany for deletion/Portal:Kenya, the Portal was deleted for being a stub which had not been touched in months (compare Wikipedia:Miscellany for deletion/Portal:Uganda, kept). In light of the much higher standard imposed on Portals as opposed to articles, I propose the following criteria for speedy deletion of Portals:


For any Portals that are not speedy deletion candidates, use Wikipedia:Miscellany for deletion.

  1. Any topic that would be subject to speedy deletion as an Article.
  2. Any Portal based on a topic for which there are not a non-stub header article, and at least three non-stub articles detailing subject matter that would be appropriate to discuss under the title of that Portal.
  3. Any Portal created as a skeleton, a stub, or a simple collection of links for which no other work has been done in over 60 days

This is more or less a seed, and I seek the consensus of the community in this proposal. Cheers! BD2412 T 15:50, 6 April 2006 (UTC)

One and two look good, but I don't quite like number three; simply because something hasn't been worked on shouldn't automatically qualify it as something that should be deleted. Perhaps take off number three as a speedy criterion and instead ask that such portals be taken to MfD? Thanks! Flcelloguy (A note?) 20:11, 6 April 2006 (UTC)
For articles I would agree with you completely, but portals are supposed to appeal to a community of interest. If no one cares enough to work on them, they should disappear... however, I see your point. How about putting portals under #3 in prod (presuming they have no sub-pages)? BD2412 T 23:51, 6 April 2006 (UTC)
I support the first two proposed criteria. I would hesitate on the third one. Most portals in such a state should probably be deleted, but probably isn't good enough for speedy deletion. --TantalumTelluride 21:33, 7 April 2006 (UTC)
I too support the first two, but would not include the third in its present form as a CSD. Sure, most portals it describes ought to be deleted, but most =/= all; let WP:MFD handle them. --CComMack 11:49, 8 April 2006 (UTC)
I'll support all three. We had a crude Portal:South Park hidden away for ages that was a no-brainer that couldn't be no-brained.Hiding talk 17:51, 8 April 2006 (UTC)
I'm inclined at this point to say definitely post the first two, and seek greater community input on handling apparently abandoned portal skeletons/stubs. BD2412 T 18:43, 9 April 2006 (UTC)
I have posted the first two criteria. The third I've raised for discussion at WP:PROD. Cheers! BD2412 T 20:21, 12 April 2006 (UTC)

Random underlines?

Maybe I'm missing something, but in the guideline

"Very short articles providing little or no context (e.g., "He is a funny man that has created Factory and the Hacienda. And, by the way, his wife is great."). Limited content is not in itself a reason to delete if there is enough context to allow expansion."

is there a reason for the underlining? An explanation would be appreciated... >> \\/\//esleyPinkha//\/\\ | 00:46, 8 April 2006 (UTC)

Basically, it's ok for an article to be short, i.e., to have little content. It'd be nice if it could be expanded, of course, but shouldn't be deleted just because it's small. However, and article that doesn't explain what it's about isn't very useful. If you read the article and have no idea what you just read about, then there's not enough context, not enough grounding the article in such a way that it can be understood by people who aren't already familiar with the topic. The underlining is to express the important difference in changing that one little letter, from content to context. I hope that helps, JDoorjam Talk 00:57, 8 April 2006 (UTC)
See the various discussion starting about here for the need to emphasize the difference between a lack of content and a lack of context. Until we added the underlines, it was a source of considerable confusion. Rossami (talk) 12:46, 8 April 2006 (UTC)

A modest proposal

The following statements on userboxes are all, I believe, consensus:

  • There is no consensus on userbox policy
  • All the other speedy criteria are intended for cases where all reasonable admins are likely to agree that something should be deleted; that's why they're so narrowly phrased.
  • Speedying userbozes can, and has, caused division and ill-will.
  • TfD'd userboxes tend not to be taken to WP:UBD; and if they are, deletion tends to be quietly and quickly endorsed.

(There's just been another example of this ill-will on WP:UBD and its talk page.) If these are in fact consensus, they should be added, with a suggestion to consider alternatives. Septentrionalis 21:56, 12 April 2006 (UTC)

I propose, therefore, the following:

There is no consensus on userbox policy. Other speedy criteria are intended to cover cases in which all reasonable editors would agree there should be a deletion; that's why they are narrowly phrased. Speedying userboxes has caused division and ill-will.
If a userbox is creating an emergency, other administrative action should be considered, as well as speedying. If it is not, the situation may be resolvable more quickly and calmly by
  • Discussing one's concerns with the makers and users of the box; or
  • Nominating the box for deletion on WP:TfD. TfD consensuses are rarely brought up, and very rarely overturned, on WP:UBD.

I have not done a exhaustive study on the last point, but I am watching the page. The rest of this I believe to be consensus. Septentrionalis 15:32, 14 April 2006 (UTC)

Right. I only just found this section. No, I do not think that the stuff above belongs on the policy page. They aren't part of the policy, which is a 'straightforward' sentence or so. Adding "there is no consensus..." is strange because that then becomes part of the policy, requiring consensus to establish that there is no consensus and consensus to establish a new consensus. It's the sort of material that belongs on a userboxes page somewhere, being essentially an editorial opinion on the policy rather than part of the policy itself. It is tempting to add these things to policy pages; the usual result is an ever-expanding wrapping of cotton wool on the actual policy for little executional benefit. -Splashtalk 22:11, 18 April 2006 (UTC)
Agreed. These statements belong here on the Talk page (or perhaps a guideline page), not on the policy page. Kaldari 02:20, 19 April 2006 (UTC)

Let's try this again

In an effort to reduce the number of copyvio images on Wikipedia, I'd like to suggest the following new criterion for speedy deletion:

  • CSD I6: Missing fair-use claim. Any image uploaded after April 13, 2006, tagged only with {{fairuse}} or {{Non-free fair use in}}, with no fair use rationale, may be deleted seven days after it was uploaded.

--Carnildo 01:31, 13 April 2006 (UTC)

This really needs to happen. Our current system means that any user who knows that those tags exist can upload any copyright-infringing media that they want, tag it with one of those tags, and thereby avoid all of our otherwise automated copyright problem systems. Images with any kind of reasonable fair use rationale would still go to WP:IFD, but all of this media belonging to to someone else that no one here has taken responsibility for need to be treated exactly the same as incompatibly-licensed images. Jkelly 01:40, 13 April 2006 (UTC)
I agree. No need to make this retrospective for now, but we need to stem the tide of new images that have the potential to get us in hot soup. Right now it is damn freaking easy to game the copyvio system by claiming any copyvio to be fair use. Johnleemk | Talk 08:05, 15 April 2006 (UTC)

I've suggested an alternate way to bring these images back into our cleanup process at Template_talk:No_license#Extending_template. Jkelly 16:26, 20 April 2006 (UTC)

Proposal for new CSD template

I often come across newly created pages which I'm sure are infringing a policy, but due to not being an admin and having not read the policies thoroughly I can't pick the right CSD template. Furthermore, there are often pages which, due to your unfamiliarity with the subject matter, you cannot tell whether they should be deleted or not. For instance, sometimes you come across a brand new stub, and it may not be obvious whether this is a stub on a notable, encyclopedia-worthy subject, or whether its just plain vanity or something else.

The proposed template is: {{db-attention}}/{{db-suspected}} or similar. It places the page either the CSD category or a subcategory called "Suspected CSD's" or similar. The idea is that you are bringing the page to the larger attention of the admins at CSD, because you suspect that it's a CSD, but you dont have the expertise to say exactly why or you require a CSD peer review. In short the proposal is a template that "brings a page to CSD's attention". -- Alfakim --  talk  16:12, 13 April 2006 (UTC)

If prod weren't having technical difficulties, that would be a good time to use prod. Also, you could simply use db-reason. No one should be deleting it if it doesn't qualify for speedy even if it's improperly tagged. NickelShoe (Talk) 16:19, 13 April 2006 (UTC)
Clarifying, this is more of an "I'm not an expert on this subject, but someone more knowledgable would certainly know whether this was CSD, so I'm bringing it to their attention"-template.-- Alfakim --  talk  17:37, 13 April 2006 (UTC)
If you can't be bothered to check the speedy criteria, don't use speedy. If you're not sure of the names of the templates or want to be more clear about your concern, use db-reason. If the article looks bad but you lack the knowledge in the relevant subject area to tell, notify the article creator, add maintenance tags, and/or submit to AfD or prod. NickelShoe (Talk) 17:46, 13 April 2006 (UTC)
Is there anywhere I can get a list of maintenance tags? Please reply on my talk page if so. -- Alfakim --  talk  15:52, 14 April 2006 (UTC)
Wikipedia:Template messages/Cleanup. Putting on your talk page too, at your request. NickelShoe (Talk) 16:03, 14 April 2006 (UTC)

With WP:PROD as policy...

...does anyone think it might be worth moving some of the less offensive speedy candidates to a PROD system. What I have in mind is A7, which could be better served (and, in fact, often has been in spite of its speedy candidacy) having multiple eyes look at it via prod? I've had a couple articles, most notably Mark Eitzel, prodded as a nn-bio for a musician, when in fact the article simply needed expansion and sourcing. Instead of speedying these, and given we have a policy in place now that would keep the majority of them from going to AfD (which was the point of the A7 expansion in the beginning), does anyone else think it might be a good idea to at least attempt in practice? A3 could also qualify here, as we could have more eyes looking at articles that may not have immediate context, but could use more eyes looking at it. --badlydrawnjeff (WP:MEME?) 16:29, 13 April 2006 (UTC)

I would agree strongly, but you might want to wait a few days and see what happens with prod now that we're not able to use the toolserver...see WP:PROD, and help us solve this problem satisfactorily. NickelShoe (Talk) 16:35, 13 April 2006 (UTC)
Well, I'm assuming a good prod outcome here, I did notice that note, but we're not 36 hours officially down yet, either. --badlydrawnjeff (WP:MEME?) 16:45, 13 April 2006 (UTC)
Well, actually, A3 (no content) is probably the CSD I most frequently use...did you mean A1 (no context)? Probably worth prodding it if it's no context, although usually I'd just give it a {{context}} tag if it looked like it might have potential...I usually go for maintenance tags first and put the article on my watchlist to watch out for removal, but go for deletion (speedy or otherwise) in cases where it's more obvious that there's no hope. NickelShoe (Talk) 16:43, 13 April 2006 (UTC)
Actually, I kinda meant both, although A1 is harder for even someone like me to justify moving to prod initially, but thanks for pointing that out. I just feel as if the more eyes looking at articles that aren't blatant nonsense or attack pages there are, the better the result could be. --badlydrawnjeff (WP:MEME?) 16:45, 13 April 2006 (UTC)
Sometimes context is easily fixed. Frequently articles lacking context have incoming links which give context and such can be added to the article. If there aren't any incoming links, usually the author could easily provide context. I've speedied articles under A1, but with prod there's five days for the author to explain what in the world they meant. I've noticed, however, that what I consider context (as far as CSD is concerned) is less stringent than some. I just want the field of study or profession of the person or whatever. A useful predicate for the introductory sentence.
Lacking content, on the other hand, annoys me enough that I'm probably biased. (Who writes an encyclopedia article that doesn't tell anything about the subject?) If it's not even a dicdef, we're not helping anybody by keeping the article. NickelShoe (Talk) 17:53, 13 April 2006 (UTC)

Wikipedia:Ammendment to deletion policy

This is a proposal that seeks to change our approach to the deletion process by removing content of a page as a criterion for deletion, only the topic can be judged in deletion debates. Please discuss the proposal at the talk page. Thanks a lot. Loom91 19:15, 13 April 2006 (UTC)


Please discuss the TFD nomination of {{db-web}} (a newly made speedy deletion tag) at Wikipedia:Templates for deletion#Template:Db-web. --Rob 05:19, 16 April 2006 (UTC)

Proposal: I1a

Note: It could be I2 if the other are bumped down, but that would probably annoy people who have to rememorize the numbers, so in my opinion I1a is best, since it's very similar.

  1. a. Any image tagged with {{NowCommonsThis}} that is public domain, or any image that is GFDL with the description and file history of the page copied to Commons.

This should allay any fears of messing up the license. PD images don't need anything at all, and GFDL just need to show who created what when. By copying the file history, it does meet the requirements. This only applies to {{NowCommonsThis}}, though, because {{NowCommons}} would require that all uses be replaced (though we could add something where "if all uses are replaced then it can be speedied" or something). --Rory096(block) 21:03, 16 April 2006 (UTC)

I agree with the proposal, many admins already speedy images that are already in commons --Jaranda wat's sup 21:11, 16 April 2006 (UTC)

I strongly object to the proposal. Until such day as we have a tool to automatically migrate history and information to Commons, I don't trust people to reliably migrate information or the admins to check that it was migrated correctly, which in my experience with my own work, it almost never is (e.g. links to en.wikipedia material are broken, file histories and dates are deleted, attribution is messed up, etc., etc.). Also, I am opposed to the idea that having an image on Commons inherently makes an image on EN redundant, since EN can have an English description and be watched for vandalism here while Commons ought to have multiple language descriptions and can't be watched for vandalism. Dragons flight 21:34, 16 April 2006 (UTC)
As for the first part, I can't make you trust anyone to do things, but right now, it rarely even gets checked at all; it's moved to Commons, well or sloppily, then listed on IfD and almost invariably deleted in a few days. Making it a CSD would help bring an admin's attention to it and hopefully check, rather than just seeing that it was on IfD for 5 days and just deleting it. For the second part, we can still have our own image description if we want, and why can't we monitor it for vandalism? If we see that the image isn't what it's supposed to be, we can just go to the commons page and revert it. If anything, it would make it less likely to be vandalized for long because there are less vandals on Commons AND there would be any countervandals on both Commons and other projects that may be using the pic watching. --Rory096(block) 23:25, 16 April 2006 (UTC)
Going through IFD gives the image uploader time to see the tag and make corrections/protest/etc. Secondly, the way the software currently works, if an image is on Commons but not here, it will display the Commons' image, the local image description page (if any) and then the Commons' image description page which creates ugly redundancy if both places are using image descriptions. Having a full local copy ensures that only the local image description is used. I'm not worrying about the image appearance being vandalized, but rather the image description being vandalized, which is much more common in my area of work (global warming/climate change). Moving an image to Commons makes it much more difficult for me to monitor changes to the image descriptions. I also disagree that it is substantially less likely to be vandalized, since it is just one extra click to get to the Commons page after finding the image used on an article in EN. Dragons flight 23:45, 16 April 2006 (UTC)
Object, for one thing CSD is already backed up most times without having to go through a time-consuming check on whether the history has properly been migrated, for another it isn't really necessary since most images under this category can go through IFD normally. Stifle (talk) 14:31, 6 May 2006 (UTC)
While true that images can go through IfD (though I'm not so sure about CAT:CSD being backed up much), it's a real PITA. One has to notify the uploader, format a template so it has both the uploader and the reason in it, then enter it onto the page, for EVERY image. There's a reason CAT:NCT is backlogged. --Rory096 05:22, 10 May 2006 (UTC)

author requests deletion

The current policy allows speedy deletion for

Any page for which deletion is requested by the original author, provided the page was edited only by its author and was mistakenly created. If the author blanks the page, this can be taken as a deletion request. Note: Please check the page history to make sure there is only a single author.

I suggest to add, after "edited only by its author", the following phrase:

not counting edits which call for (1) deletion or (2) speedy deletion of the page, or which question the (3) importance or (4) veracity of the page

I think that at least (1) and (2) are uncontroversial -- an edit that adds {{afd}} or {{db}} obviously should not prevent a speedy deletion that is requested by the author. Also editors who add {{hoax}} or {{importance}} would probably be happy to see the page go, if the original author him/herself suggests that. --Austrian 22:19, 19 April 2006 (UTC)

  • This is common sense... do we really need to explicitly add that clause? ~MDD4696 22:35, 19 April 2006 (UTC)
  • If we must guard against overly literal readings, I think a better choice would be to change "provided the page was..." to "provided the text of the page was ...", with the understanding that cleanup tags, stub markers, categories and so forth, are not part of the text. But I'd really prefer that such common sense could be left to the deleting admin. Henning Makholm 22:57, 19 April 2006 (UTC)
  • That clause has always been interpreted as only applying to significant edits. So, for example, (5) correcting spelling or grammar and (6) minor wikification of headers or links also do not count as "edits" for the purposes of this clause. The list of possible exceptions is large. We trusted the user enough to make him/her an admin. Unless there is evidence to the contrary, we should continue to trust them to exercise common sense and discretion. I'll reconsider if you can show evidence that the current wording is creating real problems but in general, cluttering up the page with more instruction creep is a bad thing. Rossami (talk) 22:58, 19 April 2006 (UTC)
    • I agree that listing situations is not necessary, but perhaps rewording to something like the only "contributor of content" instead of only editor, which is just wrong. NickelShoe (Talk) 04:43, 20 April 2006 (UTC)
  • Common sense should prevail, but often doesn't. I've edited to "provided the page's only substantial content was added by its author". Stifle (talk) 14:29, 6 May 2006 (UTC)

Adding more examples to A7

I would like to add some more examples to A7's description because I do not feel that the current wording encompasses the full scope of the policy change that was approved in December 2005: "In short, my proposal is to expand CSD A7 to include non-notable groups of people as well as individuals. This would apply to bands, clubs, organizations, couples, families, and any other collections of individuals that do not assert their importance or significance." [1] (my highlighting) Specifically, I would like to add the following words (in bold) to the current description:

7. Unremarkable people or groups / vanity pages. An article about a real person or group of people—for example, a band, club, family, online community, company or other organization—that does not assert the importance or significance of its subject. If the assertion is disputed or controversial, it should be taken to AFD instead.

I want to emphasise that this is not intended to change the agreed-upon policy in any way. But I would like us to use our existing policy to its full extent. Why? Because it's doing an incredible job, but it could do more. About 90% of deleted articles are deleted via speedy deletion. But AFD is still overflowing with 120-150 articles per day, and many of those are obvious deletions with no opposing "keep" votes.

Two of the new examples—families and organizations—are copied directly from the proposal. The other two—companies and online communities—are also included in this policy, but it is useful to mention them specifically:

  • A company is "an organization of individuals conducting a commercial or industrial enterprise"[2], but it is also an entity that stands to gain financially from using and abusing Wikipedia. As Wikipedia grows in prominence, it is increasingly becoming a target for blatant (and not so blatant) self-promotion. Currently the most egregious examples are being dealt with by the (mis)use of the {{db-copyvio}} template, but strictly speaking it is not "blatant copyright infringement from the website of a commercial content provider"—it's advertising material being copied with the full permission of the copyright owner. In A7 we have the appropriate tool to deal with this. Let's use it.
  • An online community is also a "group of people"[3], but it is one that can (and often has) mustered its members in an attempt to overwhelm Wikipedia's defences. While these attempts rarely (if ever) succeed, they can waste a tremendous amount of our time and effort. We could save ourselves an awful lot of hassle if we could deal with these cases swiftly and decisively, where appropriate.

Please comment, and share your thoughts and opinions below. Thank you. GeorgeStepanek\talk 09:16, 20 April 2006 (UTC)

  • Oppose there's no need for further expansion. PROD has now avoided past reasons for repeated CSD-expansion. PROD gives an easy way avoiding AFDs, for straight-forward matters, unikely to be contested. If a deletion is contested, it should go to AFD. Basically, the only reason for expanding a7 yet again, is if you want to speedy more things that some wish kept. That wouldn't make much sense to me. If we get expanding a7, we might as well hand over the keys to admins, and quit pretending the community approves content by discussion and consensus. --Rob 10:12, 20 April 2006 (UTC)
    • Rob this is not a policy proposal, and there is no need to vote. Voting for this finished in December. This is not an expansion of A7: this is policy that has already been voted on and approved. The discussion now is about how it could best be expressed, and explained. GeorgeStepanek\talk 10:26, 20 April 2006 (UTC)
      • The policy page has had current wording for a while. So, it will take a consensus to change it. So, what you're asking for now, is in fact, an expansion, and change in policy. It would be different, if you tried for that wording earler. But, any new wording now, requires a clear new consensus for support. And yah, it is an expansion. If it wasn't, you wouldn't have any reason to propose it. --Rob 10:30, 20 April 2006 (UTC)
        • I am not proposing any changes. I just want to improve the current wording so that it fully express the policy proposal that was approved in December. You said yourself that "if anybody wishes to change policy, please seek changes to the WP:CSD page, and try to gain consensus first." I know that you don't like this policy because you originally voted against it, but if you want to overturn it then you'll first have to obtain unequivical consensus for doing so. GeorgeStepanek\talk 11:04, 20 April 2006 (UTC)
  • I see no reason to expand A7 further. Again, I'll reiterate that I'd much rather see A7 thrown into a PROD situation to allow more eyes to look at such articles rather than deleting them quickly. --badlydrawnjeff (WP:MEMES?) 12:56, 20 April 2006 (UTC)
  • This is very sensible rewording of the A7 policy. I couldn't agree more. Especially companies abusing Wikipedia for self-promotion are becoming a nuisance. And it is not always so easy to find out if they fall under the guidelines of WP:CORP, especially if they are situated in countries such as India, Pakistan etc... JoJan 12:59, 20 April 2006 (UTC)
  • No. The idea of including website and companies in speedies has been often suggested and uniformly rejected. It was rejected again in December, as evidenced by the fact that it did not manage to remain in the policy as it came to be rewritten. I see no case for not taking such things to AfD at present, or through PROD or copyvio as appropriate. I do not agree with the assertion that the expansion proposed has support already, or it would already be present in the policy. -Splashtalk 13:56, 20 April 2006 (UTC)
    • It's interesting. When I looked through the page's history for the days after the "groups of people" policy was implemented, I see only one person removing criteria from A7. That person removed "This includes bands, clubs, organizations, couples and families." here and "This includes bands, clubs, couples and families" here. These were all criteria that had been specifically mentioned in the proposal. It is simply disingenious to claim that their current absence is due to some kind of consensus.
      This edit was the only clarification to survive, perhaps because it may even help to narrow the criteria further. With it in place the wording actually implies that that only clubs and bands are considered to be "groups of people"—which is a far cry from the broad "any other collections of individuals" that had received 80% approval. That's probably why the only templates to be created were for bands and clubs[4], and that in turn is probably why bands and clubs are the only groups of people that tend to be speedy deleted nowadays. I am not proposing any kind of expansion. I would just like the wording to accurately and clearly reflect our existing policy: policy that has already been properly proposed, voted on and unequivically approved. GeorgeStepanek\talk 09:37, 21 April 2006 (UTC)
  • Oppose This is an expansion, because A7 is not currently used this way even if it could be interpreted this way. I would support getting rid of A7 entirely; I certainly do not support expanding it. As Rob said, with the existence of prod, this serves no purpose except to delete articles people want kept, and there are better ways to handle that than zapping without discussion. NickelShoe (Talk) 14:21, 20 April 2006 (UTC)
    • This is not a vote. Nor is it an expansion of A7, nor indeed is it any kind of policy proposal. You don't have to like A7, but you are always free to put forward a proposal to revoke it. Until then our policy is the policy that was voted on and approved in December 2005: "This would apply to bands, clubs, organizations, couples, families, and any other collections of individuals that do not assert their importance or significance." The question for us should rather be: what is the most thorough and effective way to describe and explain this policy? GeorgeStepanek\talk 09:37, 21 April 2006 (UTC)
      • You're unilateral edit to a7 was undone by me. I see no consensus here for a new wording. So, please wait till that happens before editing it again please. Incidently, there were two other edits after yours, I didn't undo them. So, everybody should look over the recent changes. --Rob 05:34, 23 April 2006 (UTC)
  • Expanding CSD seems pretty silly at the moment as PROD, which has virtually the same overhead, seems to be working pretty well. Christopher Parham (talk) 05:36, 23 April 2006 (UTC)

As the originator of the original expansion, I believe that consensus has dictated that companies and web sites are specifically exempted from this. I really tried to find a wording that would indicate that this is to be applied only to informal groups, because really, you could broadly interpret "collections of individuals" to mean cities, for example, which would certainly be beyond the scope of A7. Perhaps it would help if we listed examples of what does and does not qualify for speedy deletion under this criterion in the instructions. howcheng {chat} 23:49, 24 April 2006 (UTC)


Hi, I rewrote the opening paragraphs, because I found them a bit disorganized and unclear. I was careful not to make content changes; I hope it's an improvement, and my apologies if it is not. Kaisershatner 14:05, 20 April 2006 (UTC)

A7 and companies

A7 is sometimes (wrongly) attributed to companies (see above). This is a Bad Thing (it is far more ambiguous in these cases) however the reason is clear and has a serious point: many articles are created which are blatant spam for companies which are not even in the same time zone as WP:CORP. At present we can {prod} them or take them to AfD, and we can revert the spamminess, but we can't just remove them. And unfortunately many editors forget to undo the spam links and remove the flummery. Sometimes they are a straight copy and paste from the company website, but that is not a CSD copyvio since these are not sites which sell the content.

Is there any support for proposing a CSD "blatant spam" criterion? I am in two minds about it myself. Just zis Guy you know? 15:55, 20 April 2006 (UTC)

Try a couple sections up from here. -Splashtalk 15:56, 20 April 2006 (UTC)
Yes, I saw. But I am not being very clear today. I need to think about it more I guess. There is a difference ebtween spam and non-notable companies, and that's best handled by a separate critrion (in my view), which is very tightly worded to exclude being used for neutrally worded articles on companies of no or doubtful notability. Maybe I'm misunderstanding the arguments above. Just zis Guy you know? 16:00, 20 April 2006 (UTC)

I don't really support this idea, though I understand it. It's just too subjective what is spam, and differentiating between cleanupable spam and unredeemable spam. I'd hatchet it down (Joe Corp is a bubble gum company based in Florida, USA) and stick a notability tag on it and go from there. I don't think speedying is necessary, personally. NickelShoe (Talk) 16:53, 20 April 2006 (UTC)

  • I've seen some laughably blatent spam - just off the top of my head, a "Free iPods click here THIS REALLY WORKS" kind of article, and people with links to cheap vi@gra. In the spirit of WP:IAR I deleted these, technically it doesn't meet a criteria, but come on. Perhaps there's some way to codify the difference between outright spam and someone posting a flowery article praising their company (which should probably be prod'd/afd'd). Perhaps "Article exists only to attempt to sell a product, service, or get people to click a referral link"? But this might be so uncommon that we can just go on with the status quo... "rouge deletes" and whatnot. --W.marsh 17:01, 20 April 2006 (UTC)
    • If it's working, why fix it? It seems to me that trying to fix the problem would only worsen things. You can never make a hard and fast rule without striking out the fast part of the equation; right now admins seem to be doing the right thing, IMO. Johnleemk | Talk 17:06, 20 April 2006 (UTC)
      • Well, I'm aware of that... but I also think the optimal system is one where you don't have to break rules to deal with daily occurances. Also... I think people do want to speedy anything deemed spam, even if it's about a notable company, and really the issue is about WP:NPOV... cleanup is often more in order than deletion. I think a rule clarifying what should be speedied and what shouldn't would help there. But I'm mostly thinking aloud... I want to avoid instruction creep as much as anyone. --W.marsh 17:31, 20 April 2006 (UTC)
  • Yes, you put your finger on it: it's handling a pretty routine ocurrence (pretty much every time I do a session at CAT:CSD I find some articles tagged as "spam") without writing a special set of rules. Most of the time removing the spam links and {prod} ing is the right thing, but there are a significant number which simply shouldn't be allowed to sit around for a week. Just zis Guy you know? 17:36, 20 April 2006 (UTC)

I think you can safely have a speedy for spam if you limit it to newly created articles (say under 48 hours) with major edits by only one user. We need to try to toast the stuff before it gets to Google (and mirrors), as that's the "gold prize" for the spammer. Once a company's page has been around for a while, its best to give it a PROD or AFD (if anybody wishes it deleted), as there's little harm in taking the time for one. As for the definition of spam, I'm not sure of what wording to use. --Rob 17:40, 20 April 2006 (UTC)

Is there a basic timing thing for how long it takes for Google to grab an article from here? --badlydrawnjeff (WP:MEMES?) 17:42, 20 April 2006 (UTC)
Perhaps: Articles created within the last 48 hours which serve to promote a commercial subject and which make no assertion of notability per WP:CORP. Actually on reflection I think we should apply the 48 hour limit to all criteria - speedy is designed as a counter-vandalism measure, an article which has been around for a couple of days can probably survive another week, unless it's a blatant attack, in which case it should be stubbed. Just zis Guy you know? 21:40, 20 April 2006 (UTC)
I don't think there's need of putting a 48-hour limit on speedying. It's annoying to make everything so technical. It's a good idea not to speedy old articles, but let's not make it a rule unless we have to. NickelShoe (Talk) 00:18, 21 April 2006 (UTC)
I think 48-hours makes a good anti-spam rule. In general, I would prefer not to speedy unless we have to, or the deletion is a no-brainer. Septentrionalis 02:17, 21 April 2006 (UTC)
So a possible addition to A7: including articles which are blatant advertising for a commercial organisation, created in the last 48 hours.
Or possibly, add the 48 hours to the header along the lines of in general speedy deletion is only appropriate for articles which are the work of a single editor, or which have been created very recently - within the last 48 hours or so. For articles which have been around for longer or which have input from several editors, consider using the proposed deletion process instead.
Thoughts? Just zis Guy you know? 13:33, 25 April 2006 (UTC)
It's too subjective. {{subst:prod}} is fine. Stifle (talk) 14:27, 6 May 2006 (UTC)

Suggested addition to intro

Before the last para of the intro I suggest something along the lines of:

If the problem is with the content rather than the subject - for example an excessively florid description of a company, or a highly critical biography of a public figure - consider fixing the problem, perhaps by reducing the article to a verifiable stub, rather than nominating it for deletion.

Jimbo says: "Mostly, if we (any of us! for any reason!) stub a controversial article and demand careful sourcing for rebuilding it, that's fine, EVEN IF THE ARTICLE SUCKS FOR A FEW DAYS." - it didn't apply to this instance, but I think it has relevance here. Just zis Guy you know? 21:37, 20 April 2006 (UTC)

I like it. It might not be bad to mention prod there, too, as an alternative in some cases. --badlydrawnjeff (WP:MEMES?) 21:41, 20 April 2006 (UTC)
Interestingly, an early title of what became AfD was "Article names for deletion". I think there should be more awareness that you can do more with a "bad" article than just delete it. If there's anything salvagable, by all means, people should salvage it. My suggest for wording:

If the problem is just that the current version of the article isn't acceptable, but a good article could be written on the topic, considering fixing the problem, even if it means reducing the article to a verifiable stub, rather than nominating it for deletion.

I dunno, probably not much better but it's a thought. --W.marsh 02:57, 21 April 2006 (UTC)

A3 used in a way that hampers my ability to create something useful for the reader

I am an active participant in WP:HOT - the wikiproject to make sure we have articles on topics that other encyclopedias have. As part of this I create a butt-load of redirects from A.N.OTHER naming conventions to our naming conventions. This is all good and helps the reader find the information they are looking for when they come to Wikipedia. However sometimes an article title comes up that in a sense needs to be "redirected to two places". Consider for example the topic "Flemings and Walloons" that describes the similarities and differences between the two major groups of Belgians. Now our articles are at Flemish people and Walloons, so at Flemings and Walloons I write a short stub that is more-or-less a pointer to those two articles with the bulk of our content. Now occasionally some well-meaning editor doing about 50 edits a minute slaps an A3 on it - saying "no content". Now I agree that it doesn't have much content, but the page is undeniably useful, because it helps direct the reader to the information they are searching for. It certainly wasn't the intention to delete such articles when we invented A3. Does anyone have any objection if I re-word A3 to make it clear that we don't have this sort of thing in mind? Pcb21 Pete 17:21, 22 April 2006 (UTC)

Wouldn't putting a {{dab}} tag on it alleviate that problem? It sounds like that's what it is, and no one expects a dab page to be full of enriching information. Blackcap (talk) 17:29, 22 April 2006 (UTC)
If it stops others making mistakes then I will use that if necessary.
However it isn't, conceptually, the right tag to add. The dab template says "This is a disambiguation page: a list of articles associated with the same title". The two-or-more things I want to point to people don't have the "same title". There is no ambiguity between "Flems" and "Walloons". Given how big the disambig category is already, it seems wrong to overload it even further. Hence my alternative characterization of "signpost article". Better names very welcome and thanks Blackcap for your input. Pcb21 Pete 17:46, 22 April 2006 (UTC)
Maybe we should have a "signpost article" cat and template, as a subcat of the dab cat, thus avoiding that problem. Blackcap (talk) 18:01, 22 April 2006 (UTC)
I am in favour of that. And maybe if necessary, we can add "This does not include disambiguation pages or signpost articles" to A3, but that could come later. Pcb21 Pete 18:05, 22 April 2006 (UTC)
Added into A3 here. I'm about to go and make the cat. Blackcap (talk) 18:35, 22 April 2006 (UTC)
Hey, whaddya know? It already exists. I'll go and make the template now. Blackcap (talk) 18:38, 22 April 2006 (UTC)
All right, here's a start. Whaddya think? (Oh, and further converse should go here.) Blackcap (talk) 21:32, 22 April 2006 (UTC)
Pcb21 unilaterally recreated Category:Signpost articles, which was deleted per a debate that he deemed "bogus." (I've re-deleted it.) The corresponding "guideline" page (which Pcb21 introduced without discussion) also was unanimously rejected by participants in its deletion debate.
Disambiguation pages are used to list topics that might share the disambiguation page's title, not merely each other's title. —David Levy 00:12, 23 April 2006 (UTC)
It was a great shame that I was away when that debate occured because it was bogus. To repeat, the dab template says "This is a disambiguation page: a list of articles associated with the same title" (my emphasis). You may also care to look up "ambiguous" in the dictionary. It makes no sense to add further meaning to the category that would take it outside its natural meaning in English, as the category is already extremely large. To have a sister category that actually says what its makes a lot of sense.
I am very sorry that the purpose of the category was not made clear during that deletion debate. But now that it has been (I hope!) please do not hinder the improvement of the encyclopedia by process-fiddling.
In addition I notice you have been creating inappropriate redirects to try hide the fact that we need these signpost pages! Pcb21 Pete 01:31, 23 April 2006 (UTC)

The following reply to Pcb21 was written by David Levy:
It was a great shame that I was away when that debate occured because it was bogus.
Then take your grievance to Wikipedia:Deletion review. That's what it's for.
To repeat, the dab template says "This is a disambiguation page: a list of articles associated with the same title" (my emphasis).
Yes, and that's referring to the disambiguation page's title, not to the individual articles' titles.
You may also care to look up "ambiguous" in the dictionary.
Perhaps we should change the name. Why don't you propose that?
It makes no sense to add further meaning to the category that would take it outside its natural meaning in English, as the category is already extremely large.
It's merely a project category. It isn't used for article navigation, so size isn't a major concern.
To have a sister category that actually says what its makes a lot of sense.
You're welcome to formally propose your setup (a step that you've repeatedly bypassed), but please stop ignoring consensus.
I am very sorry that the purpose of the category was not made clear during that deletion debate.
It was clear. The participants rejected your reasoning.
But now that it has been (I hope!) please do not hinder the improvement of the encyclopedia by process-fiddling.
You believe that this would be an improvement, but others disagree. As a veteran sysop, you know better than to force your viewpoint upon the community.
In addition I notice you have been creating inappropriate redirects to try hide the fact that we need these signpost pages!
No. I replaced some of your inappropriate "signpost articles" with appropriate redirects as I emptied the category. —David Levy 02:09, 23 April 2006 (UTC)

The following reply to David Levy was written by Pcb21:
Then take your grievance to Wikipedia:Deletion review. That's what it's for.
DR is for reviewing any mistakes the
Yes, and that's referring to the disambiguation page's title, not to the individual articles' titles.
This is simply untrue Pcb21 Pete 12:43, 23 April 2006 (UTC)

The following reply to Pcb21 was written by David Levy:
DR is for reviewing any mistakes the
Your thought appears to have been cut off.
This is simply untrue
I'm sorry, but you're mistaken. The purpose of a disambiguation page is to direct readers to various articles that they might seek by typing (or clicking on, but such links should be repaired) the title of the disambiguation page. The titles of the individual articles may be similar, but this is not a requirement.
You believe that your "signpost articles" serve a unique purpose, but this is because you misunderstand the scope of disambiguation pages. —David Levy 16:47, 23 April 2006 (UTC)

Moving back over to the left... I think that the intention of a signpost article, as differenciated from a dab, is that a signpost article is a page pointing a person to articles that, though they wouldn't be confused, are commonly grouped together enough that someone might enter them as a search term, whereas a dab is a collection of links disambiguating between (semi)unrelated topics with similar names. Additionally, I'm under the impression that a signpost article is intended to be an article, albeit perhaps a short one. Seems like somewhat of a difference. Also, next time you have a problem with a page, could you talk it over before you go and delete it? That's not very polite, especially when you then go and say "you know better than to force your viewpoint upon the community" to another fellow. Pcb21 made a poor choice in unilaterally undeleting it, but then you didn't do the wisest thing either by deleting it when there was obviously discussion about the issue, which is exactly what would've happened had he taken it to WP:DRV anyways. Blackcap (talk) 07:04, 23 April 2006 (UTC)

The following reply to Blackcap was written by David Levy:
I think that the intention of a signpost article, as differenciated from a dab, is that a signpost article is a page pointing a person to articles that, though they wouldn't be confused, are commonly grouped together enough that someone might enter them as a search term, whereas a dab is a collection of links disambiguating between (semi)unrelated topics with similar names.
A disambiguation page may be used for all of the above. The titles of the individual articles need not be similar or remotely interconnected. They need only relate to the title of the disambiguation page.
Additionally, I'm under the impression that a signpost article is intended to be an article, albeit perhaps a short one.
One might be led to believe that (because Pcb21 didn't select the term "signpost pages"), but the ten "signpost articles" that I eliminated (all of which were created by Pcb21) were nothing more than pointers to the existing articles.
If one wishes to create an actual article (assuming that a reasonable amount of original content can be written), there's no need to apply a special designation. Simply include links to the individual subjects' articles. (Sonny and Cher is a random example.) If the subjects are notable only as elements of a broader subject (and not individually), their respective pages should serve as redirects. (Zac Hanson is a random example.)
Also, next time you have a problem with a page, could you talk it over before you go and delete it?
I did participate in such a discussion. Pcb21 unilaterally deemed it "bogus" and restored the category without discussion of any kind.
That's not very polite, especially when you then go and say "you know better than to force your viewpoint upon the community" to another fellow.
I'm not forcing my viewpoint. I'm following policy by honoring community consensus.
Pcb21 made a poor choice in unilaterally undeleting it, but then you didn't do the wisest thing either by deleting it when there was obviously discussion about the issue, which is exactly what would've happened had he taken it to WP:DRV anyways.
The category wasn't deleted until after a discussion (which Pcb21 decided to ignore) had concluded. It should not be recreated until after a discussion leads to such a consensus. Keep in mind that this isn't merely a category; it's a significant alteration to the encyclopedia's structure. At no point has Pcb21 formally proposed such a setup. Instead, he introduced it (without any discussion) as part of our Manual of Style. This addition was unanimously removed, but he still believes that it's appropriate to reintroduce his "signpost articles" without any discussion. (He began doing so long before this thread existed.) —David Levy 16:47, 23 April 2006 (UTC)
You're right, you're right, no two ways about it. I should've thought this over more, thanks for pointing out my errors. Blackcap (talk) 17:01, 23 April 2006 (UTC)

Perhaps it was a mistake to undelete the category. To-reiterate why I did that:
The deletion debate took place on the assumption that it was a duplicate of the disambiguation category, which as you point out it is clearly not. So the deletion debate had no particular value. Deletion pages are not somehow a "greater authority" whose mistakes cannot be corrected.
That the deletion debate took that direction is partly my fault. I did not document the new category well enough and so it began to be misused.
I should've have spent more effort on it.
You are both experienced Wikipedians and know that to suggest Deletion Review as an appropriate place to make a structural alteration to Wikipedia (however minor) really is not a flyer. The debate is always about counting the number of votes and nothing else!
But of course no-one is paying me to improve Wikipedia so I see little point in butting heads with David who must have his own reasons to maintain the status quo (though he has kept them to himself so far). I will find another way to contribute which involves draining less time on obscure project talk pages. Pcb21 Pete 12:43, 23 April 2006 (UTC)

The following reply to Pcb21 was written by David Levy:
The deletion debate took place on the assumption that it was a duplicate of the disambiguation category, which as you point out it is clearly not. So the deletion debate had no particular value.
That's your opinion. I disagree, and I don't appreciate having my input (and that of others) dismissed by someone who believes that he's entitled to overrule community consensus.
Deletion pages are not somehow a "greater authority" whose mistakes cannot be corrected.
Of course not, nor are you somehow a "greater authority" whose wisdom allows him to unilaterally decide when mistakes have been made. Again, feel free to raise the issue at Wikipedia:Deletion review.
You are both experienced Wikipedians and know that to suggest Deletion Review as an appropriate place to make a structural alteration to Wikipedia (however minor) really is not a flyer. The debate is always about counting the number of votes and nothing else!
WP:DRV "considers appeals to restore pages that have been deleted. It also considers disputed decisions made in deletion-related fora." Why do you insist upon bypassing the appropriate process?
You are, however, correct in stating that you never took the necessary steps to "make a structural alteration to Wikipedia." You should have {{proposed}} your setup (and you still could).
But of course no-one is paying me to improve Wikipedia so I see little point in butting heads with David who must have his own reasons to maintain the status quo (though he has kept them to himself so far).
What do you mean?! I've repeatedly explained my reasoning (which is shared by others). You, conversely, decided to simply ignore consensus and once again create your setup without any discussion. —David Levy 16:47, 23 April 2006 (UTC)


Why isn't blatant absurdity a ground for speedy deletion? I find it really annoying that a user can create an article about himself, claiming (say) that he invented time travel and is the king of the universe, and there is no official justification for tagging this for speedy deletion (after all, these claims, if true, would certainly make the person notable). Thus we have to go through the prod (and probably) AFD process, wasting everyone's time. It makes no sense to me. dbtfztalk 19:14, 22 April 2006 (UTC)

There's {{db-nonsense}} and {{db-bio}} for situations like that. --ZsinjTalk 19:24, 22 April 2006 (UTC)
{{nonsense}} covers patent nonsense, which that is not. Blackcap (talk) 19:32, 22 April 2006 (UTC)
Extraordinary claims require extraordinary evidence. I don't think anyone's going to argue with deleting articles where the claims to notability are obviously false. If nothing else they can be deleted as vandalism (G3). Of course, this requires being a bit of discretion... absurd claims like you mention can be safely declared obviously false... but seeking out verification, or using Prod/AfD is more appropriate for claims that are merely dubious. --W.marsh 19:31, 22 April 2006 (UTC)
Thanks for the input. I think db-vandalism works for the situation I've described, so I'll use that from now on. dbtfztalk 19:34, 22 April 2006 (UTC)
By the way, I am talking only about claims that any sane person could immediately recognize as obviously false. I agree that prod/AfD is the right course of action for other cases. dbtfztalk 19:36, 22 April 2006 (UTC)
You seem to understand what to do quite well. Don't be afraid to tag common sense speedies, whether they exactly fit a category or not. We don't have an official policy for this stuff but the deletions of obvious junk are fairly uncontroversial. Friday (talk) 19:39, 22 April 2006 (UTC)
Agreed. --ZsinjTalk 19:44, 22 April 2006 (UTC)
Thanks for the good advice.  :-) dbtfztalk 19:46, 22 April 2006 (UTC)

New template deletion criteria

CSD T2: Any copyright tag that asserts "All rights reserved", that does not assert "fair use", and does not provide a valid fair-use rationale.

Now that OrphanBot's assisting with tagging of recently-uploaded images, I'm seeing a bunch of image copyright tags that simply assert "all rights reserved" go by. It would be nice if I could simply tag the template for speedy deletion, rather than having to run it through TFD. --Carnildo 22:10, 23 April 2006 (UTC)

How about redirecting the templates to Template:Nld? Jkelly 22:15, 23 April 2006 (UTC)
That template says that there was no license. The problem Carnildo describes is one where the user has created a template for an invalid license. My only reservation is whether this problem is really big enough to justify yet another CSD criterion. Couldn't we just do a one-time clean-up and be done with it? How many different templates are there with these invalid licenses? How often are new ones created? Rossami (talk) 02:24, 26 April 2006 (UTC)
I've seen two of them go by in the nine days that OrphanBot's been doing new-upload tagging: {{SKT}}, created on the 22nd, and {{Indiancopyright}}, created on December 10, 2004. I've also seen a number of invocations of the nonexistant {{RightsReserved}}; sooner or later, someone's going to get the idea of actually creating it. I expect to see more as time goes by.--Carnildo
No. They shouldn't be speedied as much as giving the uploader a chance, if possible, to find the correct copyright or replace it with a proper-license image. Few things chap my behind more than seeing images go bye-bye without an opportunity to rectify the problem. --13:36, 25 April 2006 (UTC)
I'm talking about templates here, not images. The templates will be deleted, it's only a question of if it will be as soon as they are discovered, or seven days later. --Carnildo 01:33, 26 April 2006 (UTC)
Of course, this travesty is the real reason to speedy-delete these. Two people voted that the template should be kept because some images really are all-rights-reserved, and so the vote was closed as no consensus. --Carnildo 01:09, 30 April 2006 (UTC)

The CSD:T2 speedy rule would be good. Admins should toast these on site. Otherwise, innocent, well meaning users, will see the tag, and assume it is ok. They would think that the only reason the tag exists, is because it is ok to use. Better to delete the template early, then the image later. --Rob 01:29, 30 April 2006 (UTC)

Just redirect the templates to {{db-noncom}} or the like. No need to speedy these. Stifle (talk) 14:26, 6 May 2006 (UTC)

New criterion proposal for redirects

CSD R4: Redirects in any talk namespace caused by a move, where the associated article (project page, template, whatever) was changed from a redirect into a distinct page.

A case in point is Talk:Nickel (coin), which is a redirect to Talk:Nickel (U.S. coin), but the article it's attached to is a disambig page also including the Canadian coin. Clearly the redirect is inappropriate, and deleting such a redirect should not be controversial in the slightest, especially since there is no edit history to worry about, because that was moved at the same time.

There is already precedent for this: Talk:Lingua Franca was boldly deleted by Commander Keane - it used to be a redirect to Talk:Lingua franca. Lingua Franca was moved to Lingua franca because its capitalisation was wrong, but someone later created a distinct page on the old name. At that point the page you got when clicking on "discussion" on Lingua Franca no longer bore any relation to that article.

See also Wikipedia_talk:WikiProject_Disambiguation#Multiple_pages_with_differently_capitalised_names.

Hairy Dude 15:16, 25 April 2006 (UTC)

Or you could just blank the redirect. That seems like a complicated rule when it's not like you need to get rid of the history. NickelShoe (Talk) 18:00, 25 April 2006 (UTC)

Patent hoaxes

Why, o why aren't "patent hoaxes" a speedy criterium (or at least included under patent nonsense)? I have come across quite a few articles where the claims made about a person were clearly nonsense (e.g. Joe Bloggs invented penicillin, was made king of the world, etc), but the article couldn't be "legally" speedied under either CSD G1 - patent nonsense (specifically excludes hoaxes) or CSD A7 - non-notable biography / vanity about a person or persons that does not assert the notability of the subject (it does assert notability, although false). Do we have a loophole here, or am I missing something?

Please note that I do not neccessarily include all hoaxes under this category - some may indeed be complex enought that they have to go on proposed deletions or AfD, but some hoaxes are so glaringly obvious that one should be able to "legally" speedy them.

Elf-friend 12:17, 26 April 2006 (UTC)

After writing this I did notice the "db-absurd" section above, but that just suggests workarounds ... I would rather prefer to have a seperate category (for example G9:Patent hoax) or have the definition of G1 broadened. Elf-friend 12:34, 26 April 2006 (UTC)

Well, you note the above discussion, I don't think it's exactly a work around. Posting obviously false claims is vandalism... be it in an existing article or to a new one. The problem is with a hoax that isn't obviously false, which most aren't. I personally don't feel comfortable speedy deleting an article just because I, the ignorant American, have never heard of it. CSD, if interpreted strictly, tends to avoid those kind of judgement calls... and I think that's a good thing. Deal with hoaxes via PROD and AfD.
You also run into the problem of people speedy deleting established and verifiable pseudoscience articles as hoaxes, and also probably other repercussions. Ultimately being a hoax isn't truly why we delete something, being unverifiable is. And I like to reduce the margin for error when deciding that. --W.marsh 14:02, 26 April 2006 (UTC)

Privacy vio

Privacy vio should be on the list, e.g. personal details, private correspondence etc. Phr 01:19, 27 April 2006 (UTC)

Private correspondence needs a very limited scope to prevent abuse. --Avillia (RfC vs CVU) 05:09, 27 April 2006 (UTC)

Categories relating to AfD deletions

The CfD debate at Wikipedia:Categories for deletion/Log/2006 April 27#Category:Online Soccer Project Alpha made me wonder whether we should add to C1 a permission to speedy delete categories which have become empty as a result of an AfD debate — or, more generally, the deletion (rather than recategorisation) of all articles under the deletion policy. Perhaps with a grace period of four days of emptiness? —Whouk (talk) 15:08, 27 April 2006 (UTC)

Shouldn't categories be deleted on their own merits, not whether they're being used? Who's to say they wouldn't be used again? And if they're redundant for whatever reason, why does it hurt to send it to CfD and make sure the consensus is there? --badlydrawnjeff (WP:MEMES?) 15:21, 27 April 2006 (UTC)
I think that's a case for not having any CSD category criteria, isn't it? My point is that if a category that's empty and never been populated can be deleted under C1, a category which has only had as content articles/templates which were deleted could potentially be considered as analogous. —Whouk (talk) 17:56, 27 April 2006 (UTC)
I'm not sure there is any sort of reason to speedy delete categories outside of attack categories (i.e., "Category: People who think badlydrawnjeff is a moron") or nonsense cats. But maybe I'm missing something here. --badlydrawnjeff (WP:MEMES?) 18:14, 27 April 2006 (UTC)
How can we tell if the category has ever been populated? (This is not a rhetorical question. I'm not a Wikipedia expert, but I don't know where to look in the logs for that information.) I think there should be a CSD for categories; but G1 should take care of most of the cases I've run across. — Arthur Rubin | (talk) 16:02, 6 May 2006 (UTC)

Addition to G4

I would like to add a clause to G4 to say that articles deleted under WP:PROD and then re-created should not be speedied under G4, but rather taken to AFD, as the re-creation of a PRODded article amounts to the same thing as contesting the PROD. I think this is common sense, but it doesn't seem to be explicitly stated anywhere. Any objections? Angr (talkcontribs) 09:34, 3 May 2006 (UTC)

Seems logical; incidentally, G4 already covers the case for articles that were speedy deleted (saying that the administrator have to check whether the article actually meets WP:CSD), so this is a natural extension. - Liberatore(T) 10:18, 3 May 2006 (UTC)
It sounds like a good idea. No objections here. --Siva1979Talk to me 14:58, 3 May 2006 (UTC)
Support.Ruud 15:00, 3 May 2006 (UTC)
Generally support, although I believe it should be up to someone else (perhaps even the prodder) to take it to AfD. Removal of PROD doesn't automatically mean AfD, and articles shouldn't just be AfD'd just because they were prodded once upon a time. --badlydrawnjeff (WP:MEMES?) 15:08, 3 May 2006 (UTC)
You're right of course. By "taken to AFD" I meant "taken to AFD if you want it deleted". Leaving it alone is of course also an option. Angr (talkcontribs) 16:44, 3 May 2006 (UTC)
Support. Snoutwood (tóg) 15:32, 3 May 2006 (UTC)

There having been some support and no opposition, I'm making the addition now. Angr (talkcontribs) 19:13, 4 May 2006 (UTC)

Wikipedia:Abuse reports

Although I've posted this on AN, I'm posting it here again so that all of you notorious vandalfighting lads are sure to hear about it.

If you have a IP address that has been warned, blocked, blocked again, and still keeps coming back, list him at the page mentioned in this header: WP:ABUSE. This is a process, similar to WP:AIV and WP:RFCU, that contacts the ISP of an IP address that is a repeated abuser. The page went live about ten minutes ago, and we're itching to try it out. Please read the guide and the main page before posting, that's all we ask. Thanks, lads. Snoutwood (tóg) 23:24, 3 May 2006 (UTC)

A7 too subjective for CSD

It is my impression that CSD criteria should be sufficiently clear and follow consensus opinions enough to have one person able to objectively decide on an issue. Since Notability has not been decided on how can someone justify using criteria pre-emptively developed using the essay to delete without discussion in an objective way. I propose that the guideline be scrapped as it does not fit the consensus model currently. Ansell 07:14, 7 May 2006 (UTC)

A7 is for articles with no assertion of notability. If there is any reason to suspect someone might disagree, it can't be used. -- SCZenz 08:39, 7 May 2006 (UTC)
How low an assertion is "no notability", considering that the tag can be used after the first edit to a page while it is still in a stub stage? Why are their tags called nn-bio if they are not really referencing the notability criteria, only the lack of any part of it? If the criteria are not used at all then how is notability able to be determined by an isolated individual, as in the CSD process? Ansell 10:11, 7 May 2006 (UTC)
Somewhere, perhaps on WP:YFA, there ought to be an advice to article creators that if they create an article in multiple edits, they should start by writing the part that explains why the topic is notable. But in any case, an article does not even reach stub state until the notability is explained. Without information about why to care, the arctile fails to fulfill even a stub's function. You are wrong in assuming that the criterion calls for anyone to determine notability itself; it just says to look whether there is any claim in the article that if assumed true, even though unreferenced and unlikely, would constitute notability. Henning Makholm 11:26, 7 May 2006 (UTC)
And the bar for potential notability should be quite low. If someone thinks an article has an assertion of notability that they think wouldn't save it from AfD, that does not mean it can be speedied. -- SCZenz 17:44, 7 May 2006 (UTC)
An article on a person (or group, band, club, etc.) can only be speedied under A7 if it does not contain an assertion of notability. "Katie won the spelling bee in 1993" is such an assertion, and an article with that line could not be speedied under A7. (It might be possible under A1, but that's another discussion.) Once an assertion of notability exists, it must go to prod or AFD. Stifle (talk) 17:22, 9 May 2006 (UTC)
"Katie won the spelling bee" could (and should) most certainly be speedied. We also speedy things that contain assertions of notability like "Bob is the Ruler of the Entire World", and this is hardly controversial. We just need to use a bit of common sense here. Friday (talk) 17:28, 9 May 2006 (UTC)
Friday and Stifle are entirely correct. We do, I think, set the bar for assertions fairly low, and I suppose that's altogether appropriate. Katie won the spelling bee surely qualifies for {{db-empty}} or {{db-bio}} , while Katie won the 2006 Kansas state spelling bee and represented her region at the Scripps National Spelling Bee seems to assert notability, even as I'd surely support "delete" at AfD (per WP:BIO). I do think common sense can properly dispose of 99 per cent of entries to which a speedy tag is appended; it's not difficult, IMHO, to differentiate between an article without an assertion of notability and an article with such assertion, even where the achievement/characteristic adduced to demonstrate notability does not fit within one's own defintion of WP:NOT; in the other 1 per cent of situations, inasmuch as one isn't certain whether an assertion is really made, speedy is likely inappropriate (in those cases, I think the admin removing the speedy tag might do well to refer the article straightaway to AfD—with no recommednation if one wants—although surely the initial tagger ought also to watch the article). Joe 06:00, 12 May 2006 (UTC)

Notifying contributors should be enforceable policy

Notifying the original contributors to an article before tagging it should be an enforceable policy, not simply an optional nicety. This would ensure that people thought clearly about what they were doing when placing such a powerful tag on a page. Ansell 07:19, 7 May 2006 (UTC)

I politely disagree. We are not required or expected to notify anyone about any other kind of edit (including a complete rewrite). As it says very clearly and in bold at the bottom of every edit page, "If you don't want your writing to be edited mercilessly or redistributed by others, do not submit it." The original contributors have no more rights to the article than every other reader/editor in the project. See WP:OWN for more. Rossami (talk) 14:33, 7 May 2006 (UTC)
Is it policy or simply practice that a contested CSD tag should become an XfD nomination instead? If the former, it would certainly be polite to give major contributors notification. (And either way, this page should say something about it.) Septentrionalis 16:29, 7 May 2006 (UTC)
Articles go to AfD if someone nominates them. I don't know of any policy other than that. -- SCZenz 17:49, 7 May 2006 (UTC)
To contest a CSD tag you need to make a comment on the talk page of the relevant article, optionally placing {{hangon}} on the article while you type the comment. However, if the article meets the criteria, it can still be speedied by an admin. If the article does not meet the criteria, or is improved after being tagged, the tag can be removed by anyone except authors of the page. In any case, if the tag is removed, the page can optionally be taken to ?FD. Stifle (talk) 17:20, 9 May 2006 (UTC)
I disagree with Ansell. This would be exceptionally time-consuming procedure. When I go on new pages patrol, I can speedy up to five pages a minute. Requiring me to come up with a notification for each and every one of the authors of those pages would cut this by 80% or more. The articles shouldn't be there, my deletion summary gives a clear and concise reason why I deleted the article, and people can put a message on my talk page at any stage if they need another explanation. This proposal has come up a few times; I regret that it appears to be instruction creep. Stifle (talk) 17:20, 9 May 2006 (UTC)
I agree with Stifle. However, you COULD encourage it by adding a template for the user's talks to the bottom of the CSD notice (similar to how {{db-copyvio}} has {{nothanks-sd}} at the bottom). It shouldn't be mandatory, but it would make it easier. --Rory096 06:26, 10 May 2006 (UTC)
A very simple method, {{subst:DRVU note|section heading}} ~~~~ is already available for userbox deletion review, how much harder would it be to integrate a method of this type into the current process for speedy deletion. I cannot really accept the fact that it will slow the process down as a factor, as I consider this to be the most vulnerable of all processes to be possibly abused and should be totally transparent. It is the transparency that would be increased by mandatory notification, as this could possibly be the only non-log record for the deletion in any part of wikipedia. Ansell 07:39, 14 May 2006 (UTC)

Protection of this policy page

  • 22:03, 7 May 2006 Geni protected Wikipedia:Criteria for speedy deletion (Edit rate is far to high for a policy page. [edit=sysop:move=sysop])

There had been 13 edits on this page in the previous seven days. I don't think this qualifies as "far too high" even by the strongest stretch of the imagination.

Moreover Geni has inserted a bespoke notice which says "This page is protected since it is a key policy page so changes should not be made without considerable discussion."

I don't consider that an adequate reason to protect this important policy page from editing.

I am notifying Geni and I am asking him to remove protection. --Tony Sidaway 17:44, 9 May 2006 (UTC)

~2 edits a day is far to high when they continue at that rate for day after day week after week. People should not be comeing along and casualy changeing this page. If you want to change it disscuss and debate. Get a reasonable level of support and page protection isn't going to matter.Geni 18:01, 9 May 2006 (UTC)
Perhaps this page is controversial? Kim Bruning 21:49, 9 May 2006 (UTC)

I second Tony's request that Geni unprotect this page. Yeah, it's tweaked a couple times a day, but I don't remember this leading to any crises recently. I'd rather have this page stay nice and Wiki. If ridiculous changes are being made to it, they'd get reverted. Let's not set a precedent of hardening policy pages. I agree with the sentiment, Geni, but don't think locking the page is the answer. JDoorjam Talk 22:01, 9 May 2006 (UTC)

Fine. However I stand by my position that we need to reduce the edit rate on policies to give the admins half a chance of keeping up.Geni 23:44, 9 May 2006 (UTC)
This talk page is edited half-a-dozen times a day; I don't have trouble keeping up with it. Septentrionalis 05:28, 10 May 2006 (UTC)
we have rather a lot of policy pages.Geni 06:42, 10 May 2006 (UTC)

I do find it interesting that the first edit after unprotection was vandalism. Looking at the history of the page, this is one of the more aggressively and continuously vandalized pages in the project. The vandalism was immediately reverted but perhaps some level of protection would be appropriate just to keep that under control. Rossami (talk) 13:33, 10 May 2006 (UTC)

Agreed; I don't think semi-protection would be out-of-order for a page that so often gets attention from vandals. Cuiviénen (talkcontribs), Thursday, 11 May 2006 @ 02:54 UTC
We don't protect pre-emptively. This page isn't that seriously vandalised. If vandalism steps up, then we'll protect. Otherwise, it should stay as it is. Snoutwood (talk) 05:04, 11 May 2006 (UTC)
I tend to agree. Pre-emptive protection is reserved for the likes of WP:HRTs; semi-protection might not be out of order but it would have to be permanent, and protected pages are considered harmful. Stifle (talk) 11:53, 11 May 2006 (UTC)
Protected articles are harmful, but I see nothing wrong with long-term semiprotection of a Wikipedia policy page. The only legitimate reason I can think of for an anon or brand-new user to edit a policy page would be to correct a typo; for that, a note on the talk page asking someone else to correct it is sufficient. Angr (tc) 14:33, 11 May 2006 (UTC)

If vandalism of this policy page were to become a serious problem, I wouldn't object to semiprotection. However it's a very closely watched page and most of the edits are serious attempts to improve Wikipedia, so it shouldn't be semi'd as a matter of course. --Tony Sidaway 15:53, 11 May 2006 (UTC)