Knowledge (XXG) talk:Deletion policy/redirects

1437:

other cases the question of their value or its lack is delicate and may require input from experts in the field. An obvious case being a redirect from a misnomer to a correct name. By that of course I do not mean to suggest that misnomers are NEVER appropriate article titles; the question of whether a misnomer is the right title is precisely the kind that may require expert input. The page I protected was nothing but an incitement to wholesale vandalism until I added a conspicuous warning against the "policy" of vandalising pre-emptive redirect pages. I realize some practitioners of that policy were judicious in their application of it, but the statement of the policy did not reflect that at all; it just incited unthinking vandalism. It actually encouraged the use of the word "broken" to refer to any redirect whose target does not exist! That is destructive of Knowledge (XXG)'s purposes, to say the least.

535:", and then to make the first page into a redirect to the second. That way, if someone wants to know the history of the content, they can follow it back through the history of the main article to the point at which it was added, see from the edit comment where it came from, and then go to that page (now a redirect) and explore the history of that page. To me, that seems an adequate way of doing things. I think it enables readers to ascertain the authorship of any piece of writing in the Knowledge (XXG) easily enough, at least as far as is possible in a system where anonymous contributions are allowed. (Attributing contributions is required by the terms of the GFDL, you see.) 1685:

caught that one). I applaud 165.76's efforts but I hardly believe the QC is lacking here. Many of the broken redirects were caused by articles being deleted by VfD, and some were simply pointing to pages that had never been created. By the time Fbriere tags them, we have almost certainly reached, if not passed, the point of diminishing returns in the QC department. We can have perfection (with a deadline of eternity), or we can have productivity. It would really help if people would create at least a substub at the end of pre-emptive redirects they create. Broken redirects are listed as

872:

differing points of view should be discussed in an unbiased manner. I think that the same philosophy applied to redirects would say that it is all right to include redirects that express points of view as long as it is done fairly. If an article is NPOV, and redirects are made according to the points made in the article, then "good" redirects and "bad" ones will usually end up existing in much the same ratio as "good" points and "bad" points in the article, which seems appropriate to me. What do you say? --

510:. There is no reason for this redirect to exist, Unia Wolno would serve only to confuse in search results because there is quite clearly no such thing. It is not simply a misspelling so there is no value in keeping it. It had not been archived by Google or linked to by anyone as it had only very recently been created and had never contained any content. The page creator had specifically asked for speedy page deletion. So, weighing up these options, I feel that to have kept this page 31: 776:

example, if someone writes a stupidly titled article that nevertheless contains some useful content about Joe Bloggs's acting career, then it could be moved to before being merged with and redirected to . Then people will know to look in its history for material on Joe Bloggs's acting career. If the content can't be categorised that easily, it could be given a vaguer title, like , or something like that. -

1001:) discourages the creation of new pages devoted to the minor topics by pushing readers towards the more general pages, which most people agree are preferable. (But if the material about a subtopic ends up with a wildly disproportionate amount of coverage in the article on the general topic then I still advocate splitting off a separate page for the subtopic, of course.) -- 772:

like titles of the form at all. In fact, I'd go further... I don't like subpages at all! I thought they'd already gone out of fashion by the time I arrived, but for some reason they've crept back in. But I suppose this is a matter to bring up somewhere else.) Either way, it looks like a talk page, which is misleading.

605:

out as separate entites stay that way, and their histories are less confusing. As long as the redirect isn't deleted, anyone can check the "What links here" list to find it, and then click on "Page history" to get the history of that redirect. But how many readers would know to do that is another matter... --

1029:. People will use this as an excuse to create offensive redirects on purpose. At present, the policy states that such titles may be listed on VfD, which doesn't mean they will be deleted - just that they will be discussed. If you remove it from the policy, there will be nothing to discourage their creation. 1421:"Pre-emptive redirects" are of no value and have been candidates for speedy deletion for a long time. If Mr. Hardy wants policy changed, he can get a consensus to do so. His protection of the page was a blatant violation of the policy that one does not protect a page one is involved in a dispute over. -- 1750:

My point is that the essential reason for doing all this is a kind of fastidiousness, and if so then by God you should actually BE fastidious instead of relying on the tool. It was trivially easy for me to spot the screw-ups, and if that's the case then there's something wrong with the process or the

917:

And, I should add lest I cause further offense, that the childish glee of one person will be defended by a number of other people on grounds of that person having a valid POV which should be reflected in the article titles which point at the subject. They don't, because it isn't Knowledge (XXG)'s job

901:

However, that doesn't address all cases, since often there is a single redirect to a single article. In those cases, I think that if the subject of the article is not being treated in a manner consistent with Knowledge (XXG) being a respectable and responsible encyclopedia, then we should rectify the

681:

True, but this is also the case when you merge page histories - the versions get interspersed, making it practically impossible to tell who the principle authors are. A copy of the history, with edit comments and major/minor marks, is certainly better than merging history, and probably good enough. A

1824:

If redirects that point nowhere are added deliberately, then surely the people who add these can also add a minimal one sentence substub at the target? That must take as much effort as adding the redirect, but without introducing any of the problems of redirects that point nowhere. To add a redirect

1436:

I have edited tens of thousands of Knowledge (XXG) articles. On many occasions I have created pre-emptive redirects. In some cases their value is very obvious (e.g., I see the someone created a redirect from "complex societies" to "complex society"; I've done the same thing hundreds of times). In

972:

Oh, I didn't mean that there should be a redirect for every fact or opinion expressed in the article. I just meant that if the actual sentence (not just the sentiment) "Joe Bloggs is great" is talked about in the article (if it is, for example, a slogan he used in his election campaign, or the title

818:

For duplicate articles, I find a far superior solution is to move the second article to some suitable archive location (I usually move it to a sub-page of the Talk: page of the kept article), and leave a pointer to that location at the top of the kept page's Talk: page. I would suggest we adopt this

672:

The problem is you can't copy the actual history, only a list of the contributors, so you don't have any idea of how much work each of those people have put in. The GFDL says you need to list "at least five of the principal authors of the Document". With just a list, you won't know who the principal

1820:

Yes, the people who try to clean up these redirects are not perfect, and do sometimes make mistakes. But these redirects were created either by a mistake, or deliberately. If they were created by a mistake, then attacking the person who tries to fix it and in turn makes a mistake, seems to miss the

863:

is a phrase which is well-known enough to be mentioned in the article on Joe Bloggs. To allow one but not the other is contrary to the spirit of NPOV, since we are pointing people to content that flatters the subject, without doing the same for content that paints a less favourable picture of them.

604:

Okay, my disaproval of your merging the histories was a bit harsh, sorry about that... I wasn't aware of it as a standard procedure. I think most people just redirect the "lesser" articles to the articles that they were merged into. I prefer that method, because then histories of pages that started

530:

It often happens that the complete contents of an article on a "minor" topic are merged into an article on a broader topic. There seems to be some uncertainty about the best thing to do with the page that covered the minor topic. As far as I was aware, the most usual practice was to add the content

1684:

Of the 34 broken redirects that I deleted, I see that 165.76 has found homes for five of them (thank you). Of those five, three would not have been obvious to me at all, one was a misspelling of a district I've never heard of and one was caused by a double word ("theorem theorem" -- I should have

1016:

This is not something we ought to be encouraging. Such redirects do not help people to find a page. If they search for "Joe Bloggs is an idiot", they will be presented with all the pages which contain this statement. The redirect will not help. It will also look misleading and make people think we

771:

I think that moving articles with silly titles in order to preserve their history without keeping the silly title is a very good idea. But I'm not sure about moving to . That looks like it's either the talk page of , or a subpage of . (The ambiguity there leads me to conclude that actually I don't

562:

The content of was used, and the page was deleted anyway. This is a violation of the terms of the copyrights of the original contributors, because the content is now being used without acknowledging their authorship. I thought we had a policy that any article whose content was merged into another

514:

have been more problematic than deleting it. There are no advantages to it being kept, and many disadvantages - upsetting the person who wanted it deleted, confusing people who could not understand why Wolno would redirect to Wolnosci and being annoying in search results. The redirect here is both

1206:

Well, I really do, but I'm not quite sure why. :) It annoys me when there are 10 redirects to a page as I just see them as superfluous, but, yes, if they could be accounted for in some way in the search that would improve things. I am generally for redirects, just not huge numbers of them for one

775:

I think that a page in the article space whose content is used in another article should be kept in the article space, if possible, to make it clear that at least some of what is in the history is article-type material. I'd suggest moving the page to whatever title best describes its content. For

744:

I just thought everyone did it but I don't know where I got that idea. I probably misinterpreted something somewhere but now I think about it I can't remember who else I've seen doing it. I think we need a page that announces changes to policies affecting sysops. Otherwise, are others going to be

596:

I thought it was standard practice to merge histories in order to acknowledge authorship. I don't think keeping a redirect is sufficient for this as you can't assume that those who would accessing this page for details of authorship would necessarily have access to the history of the article that

583:

difficult to follow the history of the content, not less. I think it makes sense to merge the histories of two pages if they have much the same content, especially when one has been created as a cut-and-paste of the contents of the other, because in those cases the "diff" feature would be useful.

450:

Keep Asassinated(858), Delete Asassineted(0), Keep(not on VfD) Assasinated(19k), Keep Assassinated (630k), Delete Assassineted(5) (needs a VfD entry). I think that 5 typos on Google is too few to be worth having as a typo redirect. Does anyone think that 5 is enough? If no, I'll VfD it; if yes, I

1828:

As a matter of practicality, the number of redirects without targets is kept very low (typically below 400) in large part because of efforts like WP:RFD and Wiki Syntax to apply the current policy that redirects should point somewhere. If redirects that point nowhere are allowed, then you should

1825:

that points nowhere and to not add a corresponding substub, seems like claiming that you know enough about something to say that two concepts are related, yet do not know enough to actually say in the briefest of terms what either of those concepts are. That seems a somewhat odd position to take.

1816:

For me, redirects are like the "See instead" items in the index of a paper encyclopedia. They exist to point you to the correct article. For this reason double redirects are bad (these would be like a "see instead" pointing to another "see instead", which then pointed to the real article - which

1668:

I only picked on the fairly obvious and plainly visible -- you know, where the words in the redirect link were spelled differently from target or were clearly mistaken ("theorem theorem"? Come ON). (Okay, the football stadium thing wasn't as obvious, but it didn't seem possible that there was no

907:

Obviously this is subjective, but that's why we have "votes for deletion" rather than "unassailable arguments for deletion", and obviously it's self-consorship, but I think that's justified if the effect is a genuinely more considered and reasonable treatment of the subject. Basically, what I'm

858:

I disagree with this condition. If the phrase "Joe Bloggs is a loser" is one which is well-known enough to be mentioned in the article on Joe Bloggs, then the existence of the redirect firstly helps people to find Knowledge (XXG)'s content on that phrase, secondly makes it easier to link to the

827:

location for the 'discarded' page; whatever people want to standardize on is fine with me. Leaving it in the main namespace as a top level name (as opposed to a sub-page), as anything other than a redirect, I'm not sure is a good idea, because someone may come across it and.... start editing it

542:

satisfy those who, for whatever reasons, want the redirects deleted, it is possible to merge not only the contents but also the histories of the pages. This is done by deleting the main article, moving the sub-article into its place, and then undeleting the main article again. This combines the

1860:

If it makes sense to do so. Be sure to check what links to the redirects, and edit any articles you find so that, if they are talking about the same person, they bypass the redirects, and if they're talking about someone else, turn the redirect (or the original article, if appropriate) into a

871:

what was meant was that redirects that express any POV about someone should be deleted. Then "Joe Bloggs is great" would be deleted along with "Joe Bloggs is a loser". But I would disagree with that, too. The principle of NPOV doesn't mean that points of view are not to be included, but that

578:

Merging the histories is a very ugly solution. The history of an article is supposed to show the development of a single article, not of all the articles that went into it. Merging the histories of two pages with very different content obscures what has actually taken place, and removes the

612:

I guess it depends partly on your views regarding redirects. Considering that many people prefer them to be deleted, I'm not sure what other solution there is, but I do concede your point that it makes the history look confusing. This probably isn't the right page to discuss it though.

1641:

Hi, me again from a different computer. You're flat out wrong: all of the redirects and what they link to were clearly visible, as you should know. I know because I got into an edit conflict on that page as you blew through them and I wanted to see why the page had changed so quickly.

993:. By having the redirect in place, people don't need to worry about remembering where the content happens to be at that moment when linking to it, as long as people are keeping the redirects up to date. And having redirects at the titles of minor topics (poems, slogans, album tracks, 505:

As I said in the reason for deletion - see the village pump. This had been discussed as the page had only been created due only to technical errors as the author in question had tried to use an unallowed character in the title. The only content the page ever had was a redirect to

571:

I have merged the histories to prevent this problem, but the information should not be included in the article anyway. The rough consensus was to delete it; people should not attempt to get round that by sneaking the information into another article. Contents from VfD below.

588:

as a redirect? As for the inclusion of the content, that's a separate question from the one about whether it should get its own page, and as you can see from the discussion below, at least two people who advocated deletion of the page accepted the move of the contents. --

973:

of a song/poem/football chant that was written about him, or a recognised catchphrase of his) then it makes sense to redirect it to the article where it is discussed. Then if someone looking for content on the slogan "Joe Bloggs is great" tries going to the page for

1829:

expect that the number of redirects that point nowhere to increase. In other words, if you think redirects without targets are rare, and so not very annoying, and therefore it's OK to allow them, then you're missing the cause-and-effect of current policy → result.

933:

associated with a topic. Hopefully over time the main article will evolve to cover the most noted ones. (Separate, more specialised articles can cover less well-known ones in the proper context.) I'm only advocating creating redirects for those synonyms, slogans,

859:

content, and thirdly prevents people who have failed to find the content from re-adding it at the obvious title, not realising that it is already covered at a different title. Exactly the same argument applies to the phrase "Joe Bloggs is great", of course, if

918:

to record every opinion on the planet, only to reflect every interpretation of information which might generally be regarded as notable. Opinions as to what is notable can be dismissed, and indeed commonly are when a page is deleted with a non-unanimous vote.

203:

I think we should fix the misspellings, but I suppose we could keep the misspelled redirects. They won't have anything linking to them once the articles with the misspellings are fixed, but they will at least be there for the next time someone misspells them.

815:) this makes the history almost totally unusable. The only circumstance under which I do a history merge is when someone did a cut-and-paste move, where the two histories don't overlap. Then you're just essentially pasting it back into one big long history. 626:

When merging/redirecting I typically say something like "from ***" in the edit summary, so that people can follow that chain to find the history. It is difficult though - another problem with using the GFDL. Ahh well - we all have our burdens to bear.

1044:

Oliver, I think your concerns are already dealt with, at least in part: if the phrase "Joe Bloggs is a loser" is one which is well-known enough to be mentioned in the article on Joe Bloggs, then it is may be spared by the following text:

949:

The fact that Joe Bloggs is great can be expressed in the article. We do not need a redirect to express this point. There is no point having a redirect for every fact expressed in an article and people should not be encouraged to link to

1229:

Careful, he said "if the topic of the redirect is covered in depth in the article", and you said "if the topic of the redirect is a major part of the article". Those don't even express the same goal, let alone mean the same thing...

245:(spelt correctly or not) as an article title? Also, though it is true we keep mispellings after they are fixed, in this case someone created all these variants intentionally at the same time. Is that what we want people to do? -- 1459:

I do hope that more knowledgeable people will chime in and expand upon the usual arguments (broken redirects appearing in blue, double redirects not working). Speaking only for myself, what annoys me with broken redirects is the

543:

histories, and thus also enables readers to ascertain the authorship of each contribution. However, my personal opinion is that this is not as nice a method, because it makes the history more confusing. Below is a discussion from

682:

redistributor will always need to make a judgement call on who the "principal authors" are anyway. If the merged text is but a small part of the overall product, maybe nobody nobody who edited it will be a principle author.

642:

Attempting to preserve attribution by merging page histories coulld be wrong: by essentially corrupting the history, it really removes attribution. An alternative and preferable option would be to move with a comment like:

285:

I think they should be deleted, but the Wiki has some sort of love affair with the redirect. Having all those redirects will probably encourage misspellings, but at least they'll be easy to find in the future.

1718:(sorry, I don't have the time to dig through the history to find the reference), I didn't simply delete the whole bunch, willy-nilly. Instead, I went to a lot of effort (as you can see see by the existence of 1653:

If you have questions regarding other redirects, I'll be glad to answer them. (I'm not watching them, so you'll have to flag me somehow.) If you think I'm flat-out wrong, feel free to refuse them—I won't be

1778:

doesn't mention this alternate name, one might question the usefulness of such a redirect. Nevertheless, I'm glad you caught that mistake (and any other I may have made), which is, after all, the point of

114:

Why delete? Imagine that a person with spelling problems in english (like me, for instance) is looking for assassinated persons? Unless the redirects use an enormous space in the wiki, i say keep. Cheers,

1103:

would, I think be reasonable. There would still be the possibility to discourage offensive redirects that Angela and others dissapprove of, but we're explicitly taking into account Oliver's desires too.

724:

That's a really good idea, yes. Best of both worlds. Btw, are you the only admin who does this history merge thing, or are there others that you know of? If there are others, could you point them here?

1627:

and asking redirect authors to add a stub to their redirect, I think I've done more than my share of due diligence on this. (Frankly, I do find this more fun than fixing gazillions of brackets...)

1405: 1378: 1328: 1733:

about this batch, again I'm going through this list carefully, and not simply bulk-deleting them. I can't speak for others, of course, but I am trying to exercise some care here. (I even found

705:

and keep the history there instead. It means it's in the talk namespace, so people won't object to it like they object to redirects in the main namespace, and preserves the actual history. The

1207:

article and not ones which could cause confusion or are meaningless. Anyway, I have no objection to adding the "keep redirects that are a major part of the target article" to the policy.

1191:

Anyway, if you have no objection to adding something about tending to keep redirects that are a major part of the target article, then we may be able to all agree on this part, at least.

563:

article was to be kept as a redirect to that article. I think that would be a good policy to have, as it enables people to study the history of the content and who added what to it. --

218:

Keep. It's long been a wikipedia policy to keep spelling mistakes. We might even get a lot of google hits by being one of the only sites that link to these alternate spellings. -

1619:

As you can probably imagine, there's no official QC on this; us volunteers merely flag the redirects, and rely on you to give the final word. However, given the hours I've spent

908:

against is the idea that contributors might be getting a kind of childish glee out of turning their favourite slander, abuse or slogan into a "real entry in a real encyclopedia".

1276:

I'm happy with either case - if the topic of the redirect is a major part of the article and/or it is covered in depth in the article would seem a good reason for a redirect.

67: 1704:

I've never heard of the district either; on the other hand, its name was spelled differently in the redirect and target links, so that should have been a clue right there.--

785: 746: 694: 1714:

This is a bit of a tempest in a tea-pot. It's worth noting (as some will no doubt recall :-) that the last time we did a bunch of these "non-existent target" redirects on

211:

Agree w/Adam. It is the place of a Dictionary to catch mispellings and direct user to correct spelling; not a legit function of Knowledge (XXG), except in special cases -

1821:

point: Wouldn't it be better to direct that concern to whoever made the mistake in the first place? (i.e. without the first mistake, there would be no second mistake).

1767: 1634:, I'm willing to bet there wasn't any link pointing to the redirect—that would explain why I didn't spend too much time peering over each syllable. Sorry 'bout that. 1331:. (I reverted him once on the basis that that wasn't the place to discuss policy, but I'd rather not engage in an edit war.) He's also considering filing this for 1729:) to try and exercise a fair amount of judgement, and not simply delete them all, including any that looked like the might be useful. As you can see from my note 1817:

would be annoying). Equally redirects that point nowhere are bad (these would be like a "see instead" pointing to something which did not exist - also annoying).

1527: 538:

However, a lot of people seem to have developed a phobia of redirects, and keep wanting them deleted. To preserve the history of contributions to an article

880:

First, there's the "slippery slope" argument. If offensive redirects shouldn't be deleted, then some bright spark is going to create dozens of redirects to

1563:

you should check whether there is an alternative place it could be appropriately redirected, and whether any of the exceptions noted below are applicable.

1556: 958:. It also causes problems if the article is changed and later no longer mentions that Joe Bloggs is great, making the redirect confusing and misleading. 1076:;-)), which I think is basically correct - and VfD is currently the way we try to find that balance. However, we could add another point to the policy: 977:

then they would be redirected to that content. Someone mentioning the slogan in another article ("John Smith habitually wore a T-shirt with the slogan '

579:

usefulness of the "diff" feature, because much of the time it would be comparing completely different pages. It just confuses the reader, and makes it

305:

Delete. I'm in favour of typo-correcting redirects for proper names, where someone can't reasonably be expected to know how to spell something (e.g.

1116:

I think we need to discourage such linking, not encourage it by promoting redirects for the reason that such links be used. They should not be used.

811:

The problem I have with doing history marges, when content from a duplicate article is used in the 'kept' article, is that (as pointed out above by

1537:

What confused us was that the emphasis in the statement of the policy was misleading. Read the paragraph starting with "However" after item #6 at

1506:

I would think that if someone strongly believes in the need for a redirect, that person should also be willing to spend a minute or two to write a

1360: 1545:

in a way that is really just a changed in emphasis and I hope will avoid some rash deletions-without-due-deliberation. It now reads as follows:

1510:. And if he/she cannot gather enough information to do that, then I question whether there's enough information to justify the redirect itself. 1178:

by the useless redirect. I believe that if you never noticed the existence of a useless redirect, perhaps due to a change in the interaction of

929:

An individual article is of limited size (personally I prefer to keep them fairly short), so it can only mention some of the synonyms, slogans,

981:' emblazoned across it") can link the slogan and be confident that it will take readers to wherever the content on that slogan is. The content 1143:

I've no objection if it is a major part of the article. I just want to avoid people creating idiosyncratic redirects for the wrong reasons.

1072:

The deletion policy expresses this issue as a balancing act (because it was the only way to avoid me and Daniel Quinlan settling it by a

585: 233:

really silly, the whole set of words violate the rules for article names. They are past tense verbs. If anything, the names should be

1812:

being treated with care. And here's my 2 cents worth on why I do not agree with changing policy to allow redirects that point nowhere:

1542: 1538: 1611:

I just browsed, and I found 8 obvious cases of mistakenly deleted redirects, most plainly obvious. How tight is QC on this project? --

1852:). Am I supposed to go and create redirects like ] and ] and maybe a few others if there might be a "jr." or something thrown in? 1026: 1670: 1062:

They would make the creation of duplicate articles less likely (this may well be relevant if the phrase is sufficiently well known)

556: 544: 47: 17: 1174:

have a problem with useless redirects: I believe that your real concern is the cluttering of search results and other awkwardness

892:

and any other category whose detractors have been creative with language over the years. I think that if several redirects form a

195:

I think that was some sort of passive-agressive performance art by someone who disagrees with our policy of keeping redirects. --

1719: 754: 1552: 1726: 1631: 1589: 1480:, but not in field B. How can we judge if the redirect is appropriate, since we have no information on whether it points to 162:

Is this serious? Do we have entries for every possible misspelling of every article, to accommodate people who can't spell?

1723: 702: 104: 1751:

way it's being implemented; either way, the quality of Knowledge (XXG) is being reduced, even if only incrementally. --

1253:

Don't they? It's a slight difference, perhaps, but the details will be done on RfD anyway, we just make a framework...

1887:, they'll think there isn't an article on him and write their own. I ran into just such a problem with my article on 107:. I suggest that all but the correct spelling be deleted immediately. Btw, I'm not sure I found all the variants. -- 293:

misspellings. Two of these return virtually nothing in Google and don't register in Google's built-in spellcheck:

38: 750: 122:

Unless a redirect is problematic, it is highly unlikely to be deleted. Is there any reason these are problematic?

58: 1604:

bother checking, or was he in a hurry to just slash away? How many obvious fixes did he overlook in his haste? --

706: 698: 658: 649: 1551:

6. If the redirect points to an article that does not exist and does not help avoid the accidental creation of

1892: 990: 1535:

I've just noticed that my critics and I were both mistaken about what the long-standing policy actually says.

1148:

There would still be the possibility to discourage offensive redirects that Angela and others disapprove of…

1581: 1374: 1321: 1313: 1156:

just as much as I would oppose something offensive being said about him if I saw no need for that redirect.

1179: 1152:

It isn't the offensiveness of redirects I disapprove of as such, it's more the uselessness. I would oppose

1541:. In view of the list of exceptions in the paragraph beginning with "However...", I've revised item 6 at 978: 974: 951: 116: 1775: 1752: 1705: 1674: 1643: 1612: 1605: 1593: 1022: 72: 938:

that are actually covered in the article, so there wouldn't be an uncontrollable explosion of them. --

146: 1891:-- I created it and all the redirects I though neccessary, but I missed that some articles linked to 1305:, to either fix or delete redirects pointing to missing articles—such redirects being candidates for 1088: 532: 332: 318: 661:

onto the top of the article's talk page, with a note asking people not to delete this history as it

451:

won't. I did Knowledge (XXG) searches for all of these. None make it hard to find the real entries.

1597: 1382: 1002: 939: 873: 777: 606: 590: 564: 548: 452: 1771: 1153: 828:

again, or link to it, or something. So the "better name" option is one I don't think works, alas.

1569: 1453: 1438: 1298: 1404:, as I couldn't find any discussion of the changes. You should probably list the protection of 491: 252:

I don't think people are going to type them as article titles, but someone might make a link to

178: 1880: 1694: 1317: 196: 1624: 1507: 1409: 1386: 1792: 1500: 1492: 1426: 1280: 1211: 1160: 1033: 962: 792: 339: 299: 257: 205: 1809: 1730: 1715: 1686: 1401: 1353: 1332: 1837: 1734: 1092: 459: 314: 1464:

they provide. A broken redirect is saying "foo is bar", without any information on what

1306: 1302: 483:

Redirects are kept unless they are problematic. Is there a reason these are problematic?

134:

Where? The only "reason" I can see is that they are apparently "silly", which is cyclic.

278:

Delete. I feel like someone's trying to make a point, but this is just over the top. --

1254: 1192: 1105: 812: 801: 726: 683: 666: 628: 325: 182: 154: 135: 847:

You might want to delete a redirect if one or more of the following conditions is met:

1896: 1862: 1741: 1413: 1339: 1231: 919: 909: 832: 507: 246: 212: 189: 108: 1868:

Does it make sense to do that proactively, even if ALL of the existing links are to

1087:

The topic of the redirect is mentioned in depth in the article in question (such as

531:

to the broader article with an explanatory edit comment such as "content moved from

1796: 1784: 1690: 1658: 1601: 1585: 1514: 1393: 1367: 1346: 434: 418: 346: 310: 306: 253: 100: 1780: 902:

situation by toning down the abuse (or the sycophancy, if it's positive comment).

709:

can then be deleted as it won't have any history. Would that seem a better idea?

1888: 1873: 1853: 1422: 1277: 1208: 1157: 1030: 959: 789: 758: 710: 674: 614: 598: 573: 516: 484: 402: 386: 370: 219: 169: 123: 96: 92: 88: 84: 46:

If you wish to start a new discussion or revive an old one, please do so on the

1808:

I can definitely confirm what Noel said about non-existent redirects listed on

296: 1834: 1788: 1018: 986: 955: 294: 279: 175: 172: 166: 163: 1884: 1869: 1849: 1496: 824: 1335:, so it should be obvious that there's a bit of a disagreement in the air. 1139:

The topic of the redirect is mentioned in depth in the article in question

853:

The redirect is offensive, such as "Joe Bloggs is a Loser" to "Joe Bloggs".

1738: 1513:

Here's looking forward to an informative discussion of this question. --

829: 495: 466: 268: 1065:

They aid searches on certain terms. (possibly the case, though unlikely)

1495:

is a city" is unacceptable as an article (even a stub), why shouldn't "

997:) to larger topics (collections of poems, political campaigns, albums, 1017:

have more than one article on Joe Bloggs if they see page titles with

256:, which would then go to the right place instead of being a red link. 1620: 889: 745:

aware that things like this are suggested? Or can I assume they have

697:

but I was wondering whether an alternative solution might be to move

1472:

are, or what context these words are taken from. Maybe in field A,

1381:. (No template, no inclusion in the list, I only found it in the 885: 526:

What to do with page history if a redirect is listed for deletion?

1121:

They would make the creation of duplicate articles less likely

1073: 1056:

They have a potentially useful page history (not relevant here)

881: 287: 264: 25: 1363:

showed what appears to be a clear concensus on that policy.)

1879:

It's quite possible that, in the future, someone'll link to

1309:. (Obviously, it's the delete part that is being debated.) 345:

Delete. Excessive redirects just clog up search results. --

1327:

I feel he's gone overboard by plastering warnings all over

1134:

I think they hinder searching, not aid it, as I said above.

753:

page wouldn't seem appropriate although I have used that

1099:

I'm not sure that's perfectly expressed, but something

823:

history merges. I'm open to standarding on a different

68:

Knowledge (XXG) talk:Deletion policy/redirects/Archive1

1059:

They would aid accidental linking (possibly, unlikely)

786:

Knowledge (XXG):Deletion guidelines for administrators

747:

Knowledge (XXG):Deletion guidelines for administrators

695:

Knowledge (XXG):Deletion guidelines for administrators

1895:, and guess what? someone wrote an article there. -- 586:

Invalid insect taxa described by Horace Donisthorpe

584:What exactly was wrong with my proposal of keeping 298:These two at the very least should be deleted. -- 317:) but not improper, dictionary english words. -- 267:, but it's debatable if it shouldn't redirect to 1768:Hardy-Littlewood-Selberg-Levinson-Conrey theorem 1342:deliver unto us a bit of wisdom on that matter? 1027:Joe Bloggs doesn't know what he's talking about 896:of abusive titles, they should all go together. 1182:, then you would not have a problem with them. 151:Knowledge (XXG) talk:Deletion policy/redirects 1412:, since this appears to be against policy. -- 480:In relation to some redirects listed on VfD: 8: 1592:, which you had on your list, redirected to 1068:Someone finds them useful. (again, possible) 1844:question regarding biographical articles... 1770:was sloppiness on my part—though given its 1673:. I don't think I counted that, though.)-- 229:that not only are the spellings ending in 338:Keep. No reason to delete redirects. -- 494:I guess. Must have been problematic. -- 1543:Knowledge (XXG):Redirects for deletion 1539:Knowledge (XXG):Redirects for deletion 1389:?) This is getting a bit annoying... 1356:to reflect his views on that subject. 289:The policy should be only to redirect 44:Do not edit the contents of this page. 1452:Glad to see you join the discussion, 784:That's an excellent idea. I reworded 7: 1848:I create a new article (for example 1462:utter lack of information or context 1130:They aid searches on certain terms. 557:Knowledge (XXG):Votes for undeletion 545:Knowledge (XXG):Votes for undeletion 18:Knowledge (XXG) talk:Deletion policy 1737:that had been mistakenly deleted!) 1623:, cross-checking articles, writing 1293:Fighting over pre-emptive redirects 703:Talk:Sensible title/partial history 1112:They would aid accidental linking 271:(as other variations) -- User:Docu 24: 1671:List of English football stadiums 1588:being a bit fast on the trigger: 1530:has been started on this subject. 1081:avoid deleting such redirects if: 1050:avoid deleting such redirects if: 1883:, and if it isn't a redirect to 1503:" be held to that same standard? 989:, but then again it might be at 652:- see talk page for attribution) 29: 819:as the preferred strategy, and 693:I've added your suggestions to 1632:Endocrine Disrupting Chemicals 1590:Endocrine Disrupting Chemicals 1359:(I should also point out that 657:Then copy the page history of 1: 1125:I agree this one is important 751:Knowledge (XXG):Announcements 59:Knowledge (XXG) talk:redirect 1596:, an obvious misspelling of 1400:I've reverted the change to 1301:over my efforts, as part of 1180:meta:redirects and searching 954:. They should be linking to 490:That's why you just deleted 105:List of assassinated persons 515:meaningless and worthless. 1918: 1876:13:46, Mar 29, 2005 (UTC) 1856:04:15, Mar 29, 2005 (UTC) 1385:. Isn't this contrary to 707:really silly article title 699:really silly article title 665:be required for the GFDL. 659:really silly article title 650:really silly article title 126:11:30, Oct 19, 2003 (UTC) 1865:04:51, 29 Mar 2005 (UTC) 1840:00:02, 27 Mar 2005 (UTC) 1774:status and the fact that 1766:You're absolutely right, 1744:12:50, 26 Mar 2005 (UTC) 1615:11:11, 26 Mar 2005 (UTC) 1608:10:24, 26 Mar 2005 (UTC) 1396:04:08, 26 Mar 2005 (UTC) 1370:01:15, 26 Mar 2005 (UTC) 1352:Note: He's also modified 1349:23:49, 25 Mar 2005 (UTC) 1297:I've drawn some ire from 749:on their watchlists? The 677:18:28, 16 Nov 2003 (UTC) 669:14:36, 16 Nov 2003 (UTC) 609:02:12, 16 Nov 2003 (UTC) 601:01:28, 16 Nov 2003 (UTC) 593:01:17, 16 Nov 2003 (UTC) 567:00:30, 16 Nov 2003 (UTC) 551:03:05, 16 Nov 2003 (UTC) 335:14:20, Oct 24, 2003 (UTC) 302:01:32, Oct 21, 2003 (UTC) 260:13:17, 20 Oct 2003 (UTC) 249:13:12, 20 Oct 2003 (UTC) 222:18:34, Oct 19, 2003 (UTC) 185:15:35, 19 Oct 2003 (UTC) 111:11:11, 19 Oct 2003 (UTC) 1899:18:55, 29 Mar 2005 (UTC) 1799:19:40, 26 Mar 2005 (UTC) 1783:. (And my hat's off to 1755:14:36, 26 Mar 2005 (UTC) 1708:14:36, 26 Mar 2005 (UTC) 1697:11:53, 26 Mar 2005 (UTC) 1677:14:36, 26 Mar 2005 (UTC) 1661:11:32, 26 Mar 2005 (UTC) 1646:14:36, 26 Mar 2005 (UTC) 1572:03:52, 3 Apr 2005 (UTC) 1517:21:53, 26 Mar 2005 (UTC) 1499:means the same thing as 1441:21:24, 26 Mar 2005 (UTC) 1429:15:05, 26 Mar 2005 (UTC) 1416:05:02, 26 Mar 2005 (UTC) 1108:19:40, 8 Dec 2003 (UTC) 991:self-aggrandizing slogan 876:01:57, 8 Dec 2003 (UTC) 835:16:33, 12 Dec 2004 (UTC) 780:01:57, 8 Dec 2003 (UTC) 761:19:40, 16 Nov 2003 (UTC) 729:19:19, 16 Nov 2003 (UTC) 713:19:07, 16 Nov 2003 (UTC) 686:18:46, 16 Nov 2003 (UTC) 631:02:37, 16 Nov 2003 (UTC) 617:02:18, 16 Nov 2003 (UTC) 519:13:49, Nov 6, 2003 (UTC) 498:05:22, Nov 6, 2003 (UTC) 462:18:10, 25 Oct 2003 (UTC) 455:13:21, 25 Oct 2003 (UTC) 349:00:12, 25 Oct 2003 (UTC) 342:14:26, 24 Oct 2003 (UTC) 328:21:36, 22 Oct 2003 (UTC) 321:13:14, 22 Oct 2003 (UTC) 282:00:52, 21 Oct 2003 (UTC) 215:18:03, 19 Oct 2003 (UTC) 208:17:54, 19 Oct 2003 (UTC) 192:07:34, 20 Oct 2003 (UTC) 157:23:10, 19 Oct 2003 (UTC) 138:21:06, 24 Oct 2003 (UTC) 119:11:26, 19 Oct 2003 (UTC) 1861:disambiguation page. -- 1584:may have a point about 1406:redirect-target-000.txt 1379:redirect-target-000.txt 1377:has actually protected 1329:redirect-target-000.txt 1257:19:27, 9 Dec 2003 (UTC) 1234:02:12, 9 Dec 2003 (UTC) 1214:22:25, 8 Dec 2003 (UTC) 1195:20:07, 8 Dec 2003 (UTC) 1163:19:59, 8 Dec 2003 (UTC) 1036:18:03, 8 Dec 2003 (UTC) 1005:13:51, 8 Dec 2003 (UTC) 965:04:08, 8 Dec 2003 (UTC) 942:13:51, 8 Dec 2003 (UTC) 922:04:00, 8 Dec 2003 (UTC) 912:03:47, 8 Dec 2003 (UTC) 804:20:09, 8 Dec 2003 (UTC) 795:04:12, 8 Dec 2003 (UTC) 555:Begin text moved from 465:I agree with JamesDay 352:In alphabetical order 1776:Critical line theorem 476:Problematic redirects 42:of past discussions. 1338:Could somebody from 1170:I don't believe you 1089:AIDS Kills Fags Dead 648:(moved content from 225:(I'm the proposer.) 1598:Endocrine disruptor 1557:deleted immediately 1373:I now realize that 979:Joe Bloggs is great 975:Joe Bloggs is great 952:Joe Bloggs is great 842:Offensive redirects 547:on the subject. -- 145:Second Angela. See 103:- all redirects to 1722:, as well as some 1594:Endocine disruptor 1553:duplicate articles 1322:each other's reply 1023:Joe Bloggs is cool 597:redirected to it. 188:Keep, of course!-- 147:wikipedia:redirect 73:Talk:AKFD/redirect 1893:Daniel "Dan" Daly 1881:John Michael Doar 1833:-- All the best, 1526:Please note that 1101:along those lines 788:to reflect this. 449: 448: 442:no 426:yes 410:no 394:yes 378:yes 362:VfD note added 263:There used to be 241:going to type in 54: 53: 48:current talk page 1909: 1793:Military science 1501:Saint Petersburg 1493:Saint Petersburg 867:But then again, 467:Lirath Q. Pynnor 354: 353: 131:Yes, see below. 33: 32: 26: 1917: 1916: 1912: 1911: 1910: 1908: 1907: 1906: 1846: 1781:Knowledge (XXG) 1689:for a reason. 1578: 1491:Basically, if " 1314:my initial post 1307:speedy deletion 1295: 1093:anti-gay slogan 844: 533:name of article 528: 478: 333:David Stapleton 319:Finlay McWalter 280:BCorr ¤ Брайен 81: 30: 22: 21: 20: 12: 11: 5: 1915: 1913: 1905: 1904: 1903: 1902: 1901: 1900: 1845: 1842: 1831: 1830: 1826: 1822: 1818: 1807: 1805: 1804: 1803: 1802: 1801: 1800: 1759: 1758: 1757: 1756: 1712: 1711: 1710: 1709: 1699: 1698: 1681: 1680: 1679: 1678: 1663: 1662: 1655: 1650: 1649: 1648: 1647: 1636: 1635: 1628: 1577: 1574: 1567: 1566: 1565: 1564: 1532: 1531: 1528:another thread 1523: 1522: 1521: 1520: 1519: 1518: 1511: 1504: 1489: 1457: 1445: 1444: 1443: 1442: 1431: 1430: 1418: 1417: 1294: 1291: 1290: 1289: 1288: 1287: 1286: 1285: 1284: 1283: 1267: 1266: 1265: 1264: 1263: 1262: 1261: 1260: 1259: 1258: 1242: 1241: 1240: 1239: 1238: 1237: 1236: 1235: 1220: 1219: 1218: 1217: 1216: 1215: 1199: 1198: 1197: 1196: 1186: 1185: 1184: 1183: 1165: 1164: 1145: 1144: 1136: 1135: 1127: 1126: 1118: 1117: 1097: 1096: 1084: 1083: 1070: 1069: 1066: 1063: 1060: 1057: 1053: 1052: 1042: 1041: 1040: 1039: 1038: 1037: 1009: 1008: 1007: 1006: 967: 966: 946: 945: 944: 943: 924: 923: 914: 913: 904: 903: 898: 897: 856: 855: 843: 840: 839: 838: 837: 836: 816: 806: 805: 797: 796: 769: 768: 767: 766: 765: 764: 763: 762: 735: 734: 733: 732: 731: 730: 717: 716: 715: 714: 688: 687: 655: 654: 638:End moved text 635: 634: 633: 632: 624: 623: 622: 621: 620: 619: 618: 527: 524: 523: 522: 521: 520: 500: 499: 477: 474: 473: 472: 471: 470: 469: 463: 456: 447: 446: 443: 440: 437: 431: 430: 427: 424: 421: 415: 414: 411: 408: 405: 399: 398: 395: 392: 389: 383: 382: 379: 376: 373: 367: 366: 363: 360: 357: 350: 343: 336: 329: 322: 315:Lime's Disease 303: 283: 276: 275: 274: 273: 272: 223: 216: 209: 201: 200: 199: 193: 160: 159: 158: 143: 142: 141: 140: 139: 120: 117:Muriel Gottrop 80: 77: 76: 75: 70: 56: 52: 51: 34: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 1914: 1898: 1894: 1890: 1886: 1882: 1878: 1877: 1875: 1871: 1867: 1866: 1864: 1859: 1858: 1857: 1855: 1851: 1843: 1841: 1839: 1836: 1827: 1823: 1819: 1815: 1814: 1813: 1811: 1798: 1794: 1790: 1786: 1782: 1777: 1773: 1769: 1765: 1764: 1763: 1762: 1761: 1760: 1754: 1753:219.164.1.190 1749: 1748: 1747: 1746: 1745: 1743: 1740: 1736: 1732: 1728: 1725: 1721: 1720:this template 1717: 1707: 1706:219.164.1.190 1703: 1702: 1701: 1700: 1696: 1692: 1688: 1683: 1682: 1676: 1675:219.164.1.190 1672: 1667: 1666: 1665: 1664: 1660: 1656: 1652: 1651: 1645: 1644:219.164.1.190 1640: 1639: 1638: 1637: 1633: 1629: 1626: 1622: 1618: 1617: 1616: 1614: 1613:165.76.216.35 1609: 1607: 1606:165.76.216.35 1603: 1599: 1595: 1591: 1587: 1583: 1575: 1573: 1571: 1570:Michael Hardy 1562: 1558: 1554: 1550: 1549: 1548: 1547: 1546: 1544: 1540: 1536: 1529: 1525: 1524: 1516: 1512: 1509: 1505: 1502: 1498: 1494: 1490: 1487: 1483: 1479: 1475: 1471: 1467: 1463: 1458: 1455: 1451: 1450: 1449: 1448: 1447: 1446: 1440: 1439:Michael Hardy 1435: 1434: 1433: 1432: 1428: 1424: 1420: 1419: 1415: 1411: 1407: 1403: 1399: 1398: 1397: 1395: 1390: 1388: 1384: 1380: 1376: 1371: 1369: 1364: 1362: 1357: 1355: 1350: 1348: 1343: 1341: 1340:Mount Olympus 1336: 1334: 1330: 1325: 1323: 1319: 1315: 1310: 1308: 1304: 1300: 1299:Michael Hardy 1292: 1282: 1279: 1275: 1274: 1273: 1272: 1271: 1270: 1269: 1268: 1256: 1252: 1251: 1250: 1249: 1248: 1247: 1246: 1245: 1244: 1243: 1233: 1228: 1227: 1226: 1225: 1224: 1223: 1222: 1221: 1213: 1210: 1205: 1204: 1203: 1202: 1201: 1200: 1194: 1190: 1189: 1188: 1187: 1181: 1177: 1173: 1169: 1168: 1167: 1166: 1162: 1159: 1155: 1151: 1150: 1149: 1142: 1141: 1140: 1133: 1132: 1131: 1124: 1123: 1122: 1115: 1114: 1113: 1109: 1107: 1102: 1094: 1090: 1086: 1085: 1082: 1079: 1078: 1077: 1075: 1067: 1064: 1061: 1058: 1055: 1054: 1051: 1048: 1047: 1046: 1035: 1032: 1028: 1024: 1020: 1015: 1014: 1013: 1012: 1011: 1010: 1004: 1000: 996: 992: 988: 984: 980: 976: 971: 970: 969: 968: 964: 961: 957: 953: 948: 947: 941: 937: 932: 928: 927: 926: 925: 921: 916: 915: 911: 906: 905: 900: 899: 895: 891: 887: 883: 879: 878: 877: 875: 870: 865: 862: 854: 851: 850: 849: 848: 841: 834: 831: 826: 822: 817: 814: 810: 809: 808: 807: 803: 799: 798: 794: 791: 787: 783: 782: 781: 779: 773: 760: 756: 752: 748: 743: 742: 741: 740: 739: 738: 737: 736: 728: 723: 722: 721: 720: 719: 718: 712: 708: 704: 700: 696: 692: 691: 690: 689: 685: 680: 679: 678: 676: 670: 668: 664: 660: 653: 651: 646: 645: 644: 640: 639: 630: 625: 616: 611: 610: 608: 603: 602: 600: 595: 594: 592: 587: 582: 577: 576: 575: 570: 569: 568: 566: 560: 559: 558: 552: 550: 546: 541: 536: 534: 525: 518: 513: 509: 508:Unia Wolnosci 504: 503: 502: 501: 497: 493: 489: 488: 487: 486: 481: 475: 468: 464: 461: 457: 454: 444: 441: 439:no 438: 436: 433: 432: 428: 425: 423:once 422: 420: 417: 416: 412: 409: 407:no 406: 404: 401: 400: 396: 393: 391:twice 390: 388: 385: 384: 380: 377: 375:twice 374: 372: 369: 368: 364: 361: 359:listed here 358: 356: 355: 351: 348: 344: 341: 337: 334: 330: 327: 323: 320: 316: 312: 308: 304: 301: 297: 295: 292: 288: 284: 281: 277: 270: 266: 262: 261: 259: 255: 251: 250: 248: 244: 240: 237:etc. Who is 236: 235:assassination 232: 228: 224: 221: 217: 214: 210: 207: 202: 198: 194: 191: 187: 186: 184: 180: 177: 174: 171: 168: 165: 161: 156: 152: 148: 144: 137: 133: 132: 130: 129: 128: 127: 125: 121: 118: 113: 112: 110: 106: 102: 98: 94: 90: 86: 83: 82: 78: 74: 71: 69: 66: 65: 64: 61: 60: 49: 45: 41: 40: 35: 28: 27: 19: 1847: 1832: 1806: 1713: 1610: 1580:Looks like 1579: 1568: 1560: 1555:, it can be 1534: 1533: 1485: 1481: 1477: 1473: 1469: 1465: 1461: 1391: 1372: 1365: 1358: 1351: 1344: 1337: 1326: 1311: 1296: 1175: 1171: 1154:Joe is great 1146: 1137: 1128: 1119: 1110: 1100: 1098: 1080: 1071: 1049: 1043: 998: 994: 982: 935: 930: 893: 868: 866: 860: 857: 852: 846: 845: 820: 774: 770: 671: 662: 656: 647: 641: 637: 636: 580: 561: 554: 553: 539: 537: 529: 511: 482: 479: 435:Assassineted 419:Assassinated 311:Lime Disease 307:Lyme Disease 290: 254:assassinated 243:assassinated 242: 238: 234: 230: 226: 150: 101:Assassinated 62: 55: 43: 37: 1889:Daniel Daly 1576:A bit hasty 1303:Wiki Syntax 673:ones were. 403:Assasinated 387:Asassineted 371:Asassinated 365:Google hits 300:Minesweeper 258:Adam Bishop 206:Adam Bishop 170:Tony Blaire 97:Asassinated 93:Asassinated 89:Asassineted 85:Asassineted 79:Asassineted 36:This is an 1789:Modern war 1735:an article 1019:Joe Bloggs 987:Joe Bloggs 956:Joe Bloggs 800:Seconded. 492:Unia Wolno 460:Nydigoveth 265:one or two 176:Tony Blaer 173:Tony Blear 167:Tony Bliar 164:Tony Blare 63:See also: 1885:John Doar 1870:John Doar 1850:John Doar 1654:offended. 1561:but first 1497:Leningrad 1361:this talk 1318:his reply 1003:Oliver P. 940:Oliver P. 874:Oliver P. 825:canonical 778:Oliver P. 607:Oliver P. 591:Oliver P. 565:Oliver P. 549:Oliver P. 326:Wartortle 179:Tony Blér 1897:Carnildo 1863:Carnildo 1621:Googling 1414:Carnildo 1232:Onebyone 920:Onebyone 910:Onebyone 453:JamesDay 331:Delete. 313:, maybe 269:Assassin 227:I'll add 213:Marshman 190:Ruhrjung 1797:Fbriere 1785:SWAdair 1691:SWAdair 1659:Fbriere 1630:As for 1602:Fbriere 1586:Fbriere 1582:Michael 1515:Fbriere 1486:foo (B) 1482:foo (A) 1454:Michael 1410:WP:AN/I 1394:Fbriere 1375:Michael 1368:Fbriere 1347:Fbriere 894:pattern 869:perhaps 458:Keep. - 429:630,000 347:Viajero 39:archive 1874:Morris 1854:Morris 1810:WP:RFD 1795:.) -- 1772:orphan 1742:(talk) 1716:WP:RfD 1600:. Did 1423:Cyrius 1402:WP:RFD 1387:policy 1354:WP:RFD 1320:, and 1278:Angela 1255:Martin 1209:Angela 1193:Martin 1176:caused 1172:really 1158:Angela 1106:Martin 1031:Angela 985:be at 960:Angela 890:Police 833:(talk) 813:Martin 802:Martin 790:Angela 759:Angela 755:before 727:Martin 711:Angela 684:Martin 675:Angela 667:Martin 629:Martin 615:Angela 599:Angela 574:Angela 517:Angela 485:Angela 413:19,000 324:Keep. 291:common 220:SimonP 155:Martin 136:Martin 124:Angela 1835:Nickj 1724:other 1695:Talk 1625:stubs 1312:(See 1147:: --> 1138:: --> 1129:: --> 1120:: --> 1111:: --> 983:might 886:Negro 512:would 197:Ifrog 57:< 16:< 1739:Noel 1731:here 1727:ones 1687:CSDs 1508:stub 1074:duel 1025:and 999:etc. 995:etc. 936:etc. 931:etc. 861:that 830:Noel 581:more 340:Jake 247:Zero 239:ever 231:eted 183:Adam 109:Zero 1838:(t) 1787:'s 1484:or 1478:bar 1474:foo 1470:bar 1468:or 1466:foo 1408:at 1383:log 1333:VfD 1324:.) 1091:to 882:Jew 821:not 701:to 663:may 540:and 496:Wik 381:858 1872:? 1693:| 1657:-- 1642:-- 1559:; 1392:-- 1366:-- 1345:-- 1316:, 1095:). 1021:, 888:, 884:, 757:. 309:, 181:? 153:. 149:, 99:, 95:, 91:, 87:, 1791:→ 1488:? 1476:= 1456:! 1427:✎ 1425:| 1281:. 1212:. 1161:. 1034:. 963:. 793:. 445:5 397:0 50:.

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge (XXG)

talk:Deletion policy/redirects - Knowledge (XXG)

Index