Revision as of 09:52, 28 October 2011 editJimbo Wales (talk | contribs)Extended confirmed users, Founder14,538 edits →An argument against redirects for at least some common misspellings: new section← Previous edit | Latest revision as of 21:28, 28 December 2024 edit undoSuperMarioMan (talk | contribs)Autopatrolled, Administrators60,928 editsm Reverted edits by 88.241.52.187 (talk) to last version by ObserveOwlTags: Rollback Mobile edit Mobile app edit Android app edit App rollback | ||
Line 1: | Line 1: | ||
{{See also|Misplaced Pages talk:Deletion policy/redirects|Misplaced Pages talk:WikiProject Redirect|Misplaced Pages:Article wizard/version1/Redirect}} | |||
{{Help Project}} | |||
{{Talk header|WT:R|WT:REDIR|noarchives=yes}} | |||
{{WikiProject banner shell| | |||
{{dablink|For deletion of redirects see below, and also in ]}} | |||
{{Misplaced Pages Help Project |class=Project |importance=High}} | |||
{{WikiProject Redirect}} | |||
}} | |||
{{User:MiszaBot/config | {{User:MiszaBot/config | ||
|archiveheader = {{aan}} | |archiveheader = {{aan}} | ||
|minthreadsleft = 5 | |minthreadsleft = 5 | ||
|algo = old( |
|algo = old(182d) | ||
|archive = Misplaced Pages talk:Redirect/Archive %(year)d | |archive = Misplaced Pages talk:Redirect/Archive %(year)d | ||
}} | }} | ||
{{Archive box |bot= |
{{Archive box |bot=Lowercase sigmabot III |age=6 |units=months |index=/Archive index |search=yes| | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | * ] | ||
* ] | |||
}} | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ] | |||
* ]}} | |||
{{User:HBC Archive Indexerbot/OptIn | {{User:HBC Archive Indexerbot/OptIn | ||
|target=/Archive index |mask=/Archive <#> |leading_zeros=0 |indexhere=yes | |target=/Archive index |mask=/Archive <#> |leading_zeros=0 |indexhere=yes | ||
}} | }} | ||
== Deprecation of redirecting the talk page of a mainspace redirect == | |||
== Edit request from 98.148.231.244, 18 August 2011 == | |||
<s>A talk page is just a regular page and can therefore also be a redirect. This is sometimes done when turning a page into a redirect and always done when ] since that also moves its talk page. Doing this during a move is fine in my opinion but in almost every other case, redirecting a talk page is a bad practice that should be discouraged. The reason is that if someone retargets one of the redirects but forgets to retarget the other, editors who wish to discuss the redirect will do so at the wrong place. Redirecting the talk page also provides no benefit in comparison with {{tl|talk page of redirect}} which already acts like a soft redirect that can update itself when its page is retargeted. | |||
So, my proposal is that we add this to WP:R or ]:</s> | |||
<blockquote> | |||
<s>The talk page of a mainspace redirect should not be redirected unless that was the result of a ] or as specified in ]. In all other cases, {{Tl|talk page of redirect}} should be used instead.</s> | |||
</blockquote> | |||
<s>Otherwise we end up with cases like ] where the page itself is a redirect to ] but its talk page redirected to ] before I {{diff2|1219044495|fixed it}}. Note that the utility of talk page redirects is much higher in other namespaces. Someone who looks up WT:R probably wants to end up here instead of discussing the redirect itself. So those should be allowed but people should still remember to {{diff2|1219045856|keep them synced up}} (not likely that WP:R will ever change but other shortcuts might). I'd also be open to the idea of having a bot sync up such redirects automatically. ] (]) 13:31, 15 April 2024 (UTC)</s> | |||
:Pinging participants of the previous discussion at ]: {{ping|Aristophanes68|Thryduulf|Johnuniq|Robertgreer|Flatscan|Redrose64|Lolifofo|p=.}} ] (]) 13:34, 15 April 2024 (UTC) | |||
::Also {{ping|Jameboy|Uanfala|p=}} from ] ] (]) 13:50, 15 April 2024 (UTC) | |||
:Well, I thought about it again and I'm going about this the wrong way. I'll just ask at ] first and if it gets declined then we should consider this. But, if someone else thinks that the change I proposed above is worth making anyway, they are free to pick this up and even open an RfC. ] (]) 23:08, 15 April 2024 (UTC) | |||
::Well, here goes nothing: {{slink|Misplaced Pages:Bot_requests#Bot_to_sync_talk_page_redirects with their corresponding page}}. ] (]) 23:44, 15 April 2024 (UTC) | |||
:::I vaguely recall some cases where a talk page was kept so that its history was retained. That is, the talk discussion had some possibly useful information regarding the now-redirected associated page? ] (]) 04:03, 16 April 2024 (UTC) | |||
::::I got pinged, and am here to vote keep for ]. Deleting, moving, shrinking articles makes some sense to me but I'm a huge proponent of keeping talk pages. I like Misplaced Pages queries to go somewhere useful, and if I end up on a page that doesn't exist, but that I expect to exist, I would like the talk page to already exist explaining why. ] (]) 20:52, 29 October 2024 (UTC) | |||
== Do not "fix" links to redirects that are not broken == | |||
The issue is the "fixing" of correct piped links by making them redirects. That seems at odds with the mentioned: ]. | |||
Before I start a new discussion, where was this discussed earlier? <span style="border:1px solid green; padding:0 2px">] ]</span> 13:33, 20 July 2024 (UTC) | |||
:The most recent discussion was ]. ] ≠ ] 13:43, 20 July 2024 (UTC) | |||
::Hmmm, I took part in that discussion. <span style="border:1px solid green; padding:0 2px">] ]</span> 16:07, 20 July 2024 (UTC) | |||
:::I support starting a new discussion, coming from an inclusionist perspective. ] (]) 01:20, 23 July 2024 (UTC) | |||
::I'm not quite sure what the OP is suggesting, but I very strongly agree with the consensus in the previous discussion that replacing <nowiki>] with ]</nowiki> is something that should not be done. ] (]) 11:39, 23 July 2024 (UTC) | |||
:::I also agree with that consensus. | |||
:::I think the OP was about people changing <nowiki>]</nowiki> to <nowiki>]</nowiki>. I think I've seen some consensus that such changes should generally not be done as the only reason for an edit but should instead be done alongside a more substantive edit. ] (]) 12:30, 23 July 2024 (UTC) | |||
:::: | |||
::::As well as I know it, an important reason to use the redirect is that it might be worth its own article someday. For the <nowiki>]</nowiki> case, one should consider the possibility of a new article, and which one should be used. I suspect most often it should be <nowiki>]</nowiki>, but maybe not always. ] (]) 17:42, 23 July 2024 (UTC) | |||
{{outdent}} | |||
:Over the past few weeks I've been removing piped links using ]. In all this work I've had one objection that doing so may create a situation where there are multiple links pointing to the same target, potentially some using one redirect and some using another and some direct. The inconvenience this poses for readers is that their browser can't accurately track which articles they've visited and change blue links to purple appropriately. I don't see this discussed in ] but it does seem to be a valid concern. I have been addressing this by eliminating unnecessary ] and editing the article to use consistent terminology and thus consistent linking. ~] (]) 14:59, 24 July 2024 (UTC) | |||
:: | |||
::OK, but as above, link names should consider the idea of a possible new page replacing the redirect. I can imagine, though maybe not think of an example, where one might use the redirect, and one not. The context of the links could be different in a way not so obvious to me right now. ] (]) 19:51, 25 July 2024 (UTC) | |||
:::Yes, I frequently run across examples of this. I'll try to remember to pop back here and update next time I run across one. An unpiped link is more robust in terms of ] and general maintenance this is probably a more important concern than the link tracking. ~] (]) 15:25, 28 July 2024 (UTC) | |||
::::That didn't take long. replaces a piped link with ] which has potential as a stand-alone article. ~] (]) 15:39, 28 July 2024 (UTC) | |||
== Template redirect categories == | |||
Are there any redirect categories for specifically intra-template-namespace redirects? ] (]) 09:16, 22 July 2024 (UTC) | |||
:(It seems what I was looking for was {]}, but I suppose the question still stands!) ] (]) 22:22, 23 July 2024 (UTC) | |||
== Redirects in hatnotes == | |||
You are invited to a discussion about the use of redirects in hatnotes at ]. ] (]) 16:41, 5 August 2024 (UTC) | |||
== An input request == | |||
In context to ], an input request has been made at ]. ] (]) 09:36, 8 August 2024 (UTC) | |||
== New rcat == | |||
:{{tlx|R from word reorder}} | |||
was split from {{tl|R from modification}}. It doesn't have a unique category and it isn't in the template index yet. ] (]) 22:01, 16 August 2024 (UTC) | |||
:I've redirected it to {{tl|R from modification}}. ] (]/]) 22:04, 16 August 2024 (UTC) | |||
:I've posted on ]. @], in the future, you should inform the editor who created the template that you're starting a discussion about it. ] (]/]) 22:18, 16 August 2024 (UTC) | |||
== on interpretations of the blar section == | |||
for a while now, ] has been interpreted at least in ] as "undiscussed blars must be restored and taken to ]", with few regards to its content or why it was blar'd. while that's obviously not what it means every time (as always, it's on a case-by-case basis), i've been feeling that the "such as" has to do a little too much legwork to imply that there's more than one option | |||
with that in mind, opinions on naming two or more examples, with something like {{font|text="...other methods of dispute resolution should be used, such as ''nominating the article for ] or'' restoring the article and nominating it for ]."|font=mingli u|color=green}}? '''] <sub>] ]</sub>''' 23:39, 8 October 2024 (UTC) | |||
{{edit semi-protected|answered=yes}} | |||
<!-- Begin request --> | |||
Please redirect | |||
http://en.wikipedia.org/Burlington_Public_Schools | |||
to | |||
http://en.wikipedia.org/Wikipedia:Articles_for_creation/Burlington_Public_School,_Burlington_Oklahoma | |||
<!-- End request --> | |||
] (]) 15:38, 18 August 2011 (UTC) | |||
:Let's wait until the page is created first. — ] (]) 16:53, 18 August 2011 (UTC) | |||
:Encouraging BLARs to be nominated at RfD is exactly the opposite of what we should be doing, they already come here far too often. The ''only'' circumstances in which RfD should be deleting article content that has not been removed with explicit consensus is when that content would be speedily deletable if restored. The "such as" means that AfD is not required in every situation (e.g. talk page or wikiproject discussion is sometimes fine), it does not mean RfD is a suitable venue. ] (]) 00:17, 9 October 2024 (UTC) | |||
:We don't normally redirect from mainspace --> projectspace. See ]. -- ]] 18:37, 21 August 2011 (UTC) | |||
::per... '''''that one discussion''''', i'll also disagree with this. for the most part, anyway, case-by-case and all. a blar either not being properly discussed, or being undiscussed entirely, is one part of it. the content it had being unsourced or not properly sourced cruft (as was the case there) is the big issue, that i feel most of your restore votes deliberately ignore. i, at least, trust the people in rfd to be able to look at the history of a blar and determine whether or not its sources (if any were presented) were usable. in the cases of the list of strogg in quake 2 (linked below) and ], for example, they... really weren't. <small>frankly, i'm pretty sure that list would have been bad enough to warrant a specific exception for ]'s "not for software" deal at this point</small> | |||
::this doesn't mean there's not a chance that the content ''was'' usable, or even downright good, or that there's coverage proceeding the blar or that the blarrer <small>(that's a word, right?)</small> and everyone else just missed ''until'' a discussion happened, but as i'm almost tired of seeing, some cases just aren't that. on the chance that they are, nice, but while this might be my pessimism talking, those tend to be the exception to the norm in rfd | |||
::also, i ''still'' have no idea why you keep bringing the "blars should only pop up in rfd if they meet csd" thing up. it was already argued against based on your reason for it being a misreading (coincidentally the exact misreading this discussion is about), the thing that was misread mentioning nothing about speedy deletion or the criteria for it, or being a criterion for anything, and your only argument against that being... bringing it up again later like tavix and i never questioned it '''] <sub>] ]</sub>''' 02:29, 9 October 2024 (UTC) | |||
:::Much of what you are saying doesn't make sense, and much of the rest of it is bizarrely and/or plain wrong - particularly you are misinterpreting my comments about CSD in the same way I had to correct you about more than once in the last discussion. Whether something is "cruft", whether sources are or are not reliable, are discussions of article content that belong in the venues for discussion of article content: AfD, talk pages, etc. not RfD. You may trust RfD participants to undertake research that is not relevant to RfD and that everyone who would comment on an AfD for the article will know it is beign discussed at RfD is endearing but naiive and/or wrong. ] (]) 02:40, 9 October 2024 (UTC) | |||
::::if i'm misinterpreting your comments about csd, it's because you took over a month to explain them in a coherent way (that is, one that didn't somehow equate rfd to reversion and speedy deletion), and ''still'' ended up being "plain wrong" per the policies you yourself cited. i also said nothing about people at afd knowing that something would be discussed at rfd, where did you get that? '''] <sub>] ]</sub>''' 11:22, 9 October 2024 (UTC) | |||
:::::When you actually think (rather than just reading the words of policy without doing so) its very simple: The purpose of requiring deletion of articles to be discussed at AfD is so that both those involved with the article, ''and'' those who are interested in and/or knowledgeable about the article and/or its subject know that it has been nominated for deletion. This is done because the community has decided that deletion without this notice is not reasonable. If articles are BLARed then discussed at RfD then only those involved with the article know that the subject has been nominated for deletion, those who watch AfD (and these days also article alerts and deletion sorting lists) because they have opinions about the deletion of articles do not know that an article has been nominated for deletion. | |||
:::::Content that meets a speedy deletion criterion is an exception to this because notification is not required. Content that has previously been discussed is an exception because the consensus discussion happened previously. ] (]) 11:38, 9 October 2024 (UTC) | |||
::::::this requires that rfd somehow have ''no one'' who knows anything about article content, how blars work, how rfd nominations and twinkle work, pop culture references old enough to drink, or that more than one thing can be in rfd at a time, that that 2021 consensus shown in wp:blar be absolute and not "yeah that's usually a good idea" (see the use of "most" in wp:blar), and that that consensus not currently be in the process of being challenged '''] <sub>] ]</sub>''' 11:54, 9 October 2024 (UTC) | |||
:::::::It actually requires none of those things. Whether people at RfD are competent in certain topic area is irrelevant, what matters is that the people who are interested in/knowledgeable about the topic area know that article content is being discussed. They know that when articles are discussed at AfD, they don't know that when a redirect is at RfD. ] (]) 12:26, 9 October 2024 (UTC) | |||
::::::::problem: nominating something for rfd leaves evidence on the edit history (and thus the watchlist of anyone watching it), twinkle has the option to notify the original creator and/or target talk page, you can just ping someone else involved and presumably knowledgeable, and probably sends a pigeon out to notify you personally (i can't verify this one, i live in a fictional location) '''] <sub>] ]</sub>''' 13:08, 9 October 2024 (UTC) | |||
:::::::::It notifies those people that a redirect is being discussed, it notifies nobody that article content is being discussed. It notifies nobody who watches AfDs, the AfD section of article alerts, deletion sorting lists (this one isn't absolute but very occasionally RfDs get added whereas almost all AfDs do), etc. ] (]) 14:25, 9 October 2024 (UTC) | |||
::::::::::...yes. that's the point. because it's at rfd. because blars are redirects. and redirects can have edit histories. which any voter worth their salt will check '''] <sub>] ]</sub>''' 14:28, 9 October 2024 (UTC) | |||
:::::::::::Except BLARs are not redirects, they are blanked articles. The edit history isn't the issue, it's the deletion of article content. ] (]) 15:10, 9 October 2024 (UTC) | |||
::::::::::::they're redirects with history, see good ol' wp:blar '''] <sub>] ]</sub>''' 15:20, 9 October 2024 (UTC) | |||
:::::::::::::That history is an article. That article was blanked without consensus. Therefore it should be restored and discussed as the article it is per ], ] etc. ] (]) 16:54, 9 October 2024 (UTC) | |||
::::::::::::::that's not what either of them say. ] explicitly states that brd isn't a ''reason'' to revert '''] <sub>] ]</sub>''' 17:45, 9 October 2024 (UTC) | |||
:Cogsan, I disagree with your premise. "Undiscussed blars must be restored and taken to afd" has never enjoyed consensus at RfD. I would think that ] would have disavowed you of that idea. That said, I don't think ] needs any changes. If an editor blanks and redirects an article and another editor sees it right away disagrees with the blank-and-redirection, the best option is to restore the article and have it taken to AfD. The ones we usually see at RfD don't really make sense in the context you're quoting because there is no ongoing disagreement between editors on whether or not the page should be an article or not. If a page was redirected in 2009 and it's just now coming to RfD, it's been a redirect for a long time and should be evaluated as such. If the underlying content looks like it may be notable, restore it. If not, delete it. --] <sup>(])</sup> 00:45, 9 October 2024 (UTC) | |||
::i didn't say i thought that, i said it tended to be interpreted that way. i wouldn't turn to the dark side ''this'' fast, even if the dark side has cookies '''] <sub>] ]</sub>''' 00:51, 9 October 2024 (UTC) | |||
:::I know ''you'' don't think that, but even "tends to be interpreted that way" gives way too much credence to a vocal minority. --] <sup>(])</sup> 00:56, 9 October 2024 (UTC) | |||
::::fair lol. still not a fan of how easy it is for said vocal minority to start discussions spanning 2 months that end up amounting to having missed two words in a paragraph, but eh '''] <sub>] ]</sub>''' 01:01, 9 October 2024 (UTC) | |||
:That change to BLAR would contradict ], which states that contested BLARs should be discussed on talk or at AfD. This reflects consensus from ] and ] RfCs. ] (]/]) 00:46, 9 October 2024 (UTC) | |||
::eh? that one ''also'' only provides restoring and sending to afd as an example (see the use of "include"). this is the exact kind of case this is about '''] <sub>] ]</sub>''' 00:53, 9 October 2024 (UTC) | |||
:::I interpret the Quake discussions as exceptions to the rule per ] , given the ages of the redirects and their complete lack of encyclopedic content. The general rule that things should go to AfD holds in most cases and we should not muddy the waters by affirmatively stating that RfD might be appropriate. ] (]/]) 00:58, 9 October 2024 (UTC) | |||
::::then shouldn't it say that afd is usually the way to go, as opposed to only naming it as an option? i'm starting to think that the way it's currently written doesn't look good for either side '''] <sub>] ]</sub>''' 01:05, 9 October 2024 (UTC) | |||
:::::I'll start a discussion to do so at ]. ] (]/]) 01:15, 9 October 2024 (UTC) | |||
::{{outdent|3}} ]. ] (]/]) 01:26, 9 October 2024 (UTC) | |||
:::nice-a. gonna dip my toes there when i've had my sleep '''] <sub>] ]</sub>''' 02:30, 9 October 2024 (UTC) | |||
== redirects to death of.... articles == | |||
== Problem with redirections to sections/anchors == | |||
I've been looking for any editorial policy or styleguide on Redirects from a person's name towards the article about incident which caused their death. I recall reading the debate that when we have an article which is specifically about the incident (accident, crime etc.) which caused someone's death, but they would ''not'' ''otherwise'' have been considered Notable for a WP Biography, we should name the article "death of..." or "murder of...", "killing of..." etc., and ''not'' merely their name. But, I cannot find anything about ''redirects'' for issue. Does anyone know of a consensus on this, one way or the other? | |||
If I create a page named redirection_page and add something like | |||
<pre> | |||
#REDIRECT ] | |||
</pre> | |||
or | |||
<pre> | |||
#REDIRECT ] | |||
</pre> | |||
this works fine for as long as I have JavaScript enabled. However, it will only take me to the start of the target_page article, not the section/anchor within, if JavaScript is disabled and I link to <code><nowiki>]</nowiki></code> in another article or type the name of the redirection_page in the search box. The resulting link displayed in the browser's link bar while viewing | |||
<pre> | |||
http://en.wikipedia.org/target_page | |||
</pre> | |||
is | |||
<pre> | |||
http://en.wikipedia.org/redirection_page | |||
</pre> | |||
If I then follow the "Redirected from redirection_page" link at the top of the article, I will be shown the redirection link like ] on the redirection_page. Clicked, this link will correctly bring me to the desired anchor/section within the article. | |||
We have ] - which is about the naming convention of the article itself. Do we have a policy for whether to, or whether to NOT create a redirect from their name to that article? If so, could it please be added to the list of valid reasons ] or ] a redirect? | |||
It looks as if the hashed argument would get stripped off at some stage if not using JavaScript. I tried to URL encode the hash-mark using | |||
<pre> | |||
#REDIRECT ] | |||
</pre> | |||
or HTML encode it as follows: | |||
<pre> | |||
#REDIRECT ] | |||
</pre> | |||
But this does not change anything. | |||
The primary argument that we ''should'' create such a redirect is because it aids findability/SEO from the most likely search term (e.g. ] redirects to ]). The primary argument that we should ''not'' create such a redirect is the same as for having the "death of..." naming convention in the first place – that a person's biography shouldn't be defined by the manner of their death (especially if the only reason they're known to the public is because they became someone else's victim). | |||
Since the help pages read as if this should not be any problem at all, is this a known behaviour or limitation, perhaps only under certain other conditions? I'm using Firefox 6.0, and JavaScript is typically disabled for security reasons. Before I test more configurations, I would like to know if I can expect this to work at all. Thanks. --] (]) 15:42, 22 August 2011 (UTC) | |||
I'm not expressing a judgement or vote! on either option, but it would be helpful if "NAME -> death of NAME" could be added to the list of ''valid'' or ''invalid'' reasons for a redirect. ]] 10:39, 13 November 2024 (UTC) | |||
== Suggested changes to {{tl|R from alternative language}} == | |||
*I would think that the advantages generally outweigh the disadvantages, and if the person is notable for any other reason the redirect may encourage someone to write the article. · · · ] ]: | |||
I have ] to make it possible to specify the alternative language, in a standardized and more convenient way than currently in place. Details are on the talk page. ] (]) 21:17, 19 September 2011 (UTC) | |||
*Anyone searching or such an article would know the name of the person, but not necessarily the article title, which could take on any one of several forms – Death of, Drowning, Fatality, Incident etc, so the name would be the most useful search string, and could plausibly be the most common way to try to find the article, so I think it should be a redirect unless ambiguous. · · · ] ]: 14:45, 13 November 2024 (UTC) | |||
* If I saw a "Death of ..." redirect while doing ] work, and it pointed to a section on the person's page regarding their death or to a relevant article about it, I'd mark it as patrolled. It's a useful search term and I don't see it as being likely to be deleted at RfD for that reason. ] (]) 15:44, 13 November 2024 (UTC) | |||
== Talk page scope == | |||
== Another reason for re-directs not mentioned in the article == | |||
What is the difference between here and ]? These two talk pages seem like they ] to be centralized. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">]</span> <sup>]</sup> 06:31, 20 November 2024 (UTC) | |||
I don't see the following on ]: | |||
==Deletion nomination of soft redirects== | |||
A redirect from a page about a company that was bought out by another company to the parent company. Example: http://en.wikipedia.org/search/?title=QNX_Software_Systems&action=history . | |||
] You are invited to join the discussion at ]. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">]</span> <sup>]</sup> 06:32, 20 November 2024 (UTC)<!-- ] --> | |||
=={{noredirect|WP:Redirect assimilation}}== | |||
Is there any way to locate information that was available on Misplaced Pages before the company disappeared? ] (]) 17:01, 7 October 2011 (UTC) | |||
FYI, {{lw|Redirect assimilation}} was created to redirect to ] | |||
-- ] (]) 21:28, 20 November 2024 (UTC) | |||
== Semi-protected edit request on 21 November 2024 == | |||
:In the case that you mentioned, ], there is no history there. I think the redirect is incorrect. It should go to ]. But your general point is true. I'd say it is covered by the bullet: ''Sub-topics or other topics which are described or listed within a wider article''. There are lots of reasons a sub-topic title might redirect to a section of another article. ] ≠ ] 17:42, 7 October 2011 (UTC) | |||
::Thanks for responding. I wonder how such a re-direct can be undone (so those who are interested can view the original content), if in fact it is "incorrect"? ] (]) | |||
{{edit semi-protected|Misplaced Pages:Redirect|answered=yes}} | |||
:::There are number of ways to display and edit the redirect page. Commonly by clicking on the link in the "(Redirected from ...)" notice at the top of the page. Once there, the redirect page can be edited just like any other page. See ] for more information. ] ≠ ] 18:30, 8 October 2011 (UTC) | |||
Add ] to the shortcut list of ]. No source needed since it's pretty obvious. ] (]) 19:16, 21 November 2024 (UTC) | |||
:{{complete2}}. ''''']''''' , ] ] <small>20:09, 21 November 2024 (UTC)</small> | |||
I have undone this change. It is by no means obvious to me what this has to do with "assimilation", and there are no nontrivial incoming links. I think this redirect should probably be deleted. --] (]) 23:26, 21 November 2024 (UTC) | |||
== Enforcement == | |||
{{br}} Listed for RfD at ]. --] (]) 03:16, 22 November 2024 (UTC) | |||
== See related recommended best practice proposal == | |||
Should this page be enforced on articles? An editor is insisting that he be allowed to in ] based on what is said in this page. I believe he is treating this page as a policy when it is only a guideline. A guideline means a strong recommendation and so is not binding. I believe redirects should not usually be created, unless there is a strong justification for doing so. In this case, the editor at issue believes that editors have difficulty editing with direct links in place as opposed to with the redirects. I think this is baseless. If this editor is right, then redirects should be created whenever they would be shorter than direct links. Rather than getting into an edit war, I would like to know what other editors have to say on this issue. ] (]) 00:12, 22 October 2011 (UTC) | |||
At ] concerning recommending the use of {{tl|Uw-blar}} <sub style="border:1px solid #228B22;padding:1px;">]|]</sub> 02:18, 17 December 2024 (UTC) | |||
:In a word, yes ] applies to articles. ] ≠ ] 00:21, 22 October 2011 (UTC) | |||
::So should editors go around to article and create redirects? ] (]) 00:29, 22 October 2011 (UTC) | |||
:::No. Have you read ]? What it says is that you should go around trying to fix redirects that aren't broken. Redirects exist for many reasons and are a convenience for readers and editors alike. There is very little benefit to editing an article for the sole purpose of fixing redirects. ] ≠ ] 00:35, 22 October 2011 (UTC) | |||
::::You seem to agree with me. Articles should not be edited simply to fix, create, eliminate redirects. However, that is what happened in this case. ] (]) 00:43, 22 October 2011 (UTC) | |||
:::::Ah, I had only looked at the one link you provided, which seemed to imply that TJRC was simply undoing an edit where you had changed the redirects to direct links. I can see now from the edit history that it is a little more complicated. While I would not have edited as TJRC has, I can sort of understand the point. Piped links, especially where the direct link is very long, can make it a little more difficult to read the raw wikitext while editing. Since the other editor has expressed a strong opinion on the matter and the redirects don't actually hurt anything for readers and might have some benefit for editors, I suggest that you just leave the redirects be. ] ≠ ] 01:03, 22 October 2011 (UTC) | |||
::::::Sorry for not being clearer with my linking and thank you for seeing my point. However, wouldn't your advice to me apply at least as much to TJRC? ] (]) 01:08, 22 October 2011 (UTC) | |||
:::::::Sure, like I said, I would not have edited the way he/she did. ] ≠ ] 01:14, 22 October 2011 (UTC) | |||
== Semi-protected edit request on 27 December 2024 == | |||
== An argument against redirects for at least some common misspellings == | |||
{{edit semi-protected|Misplaced Pages:Redirect|answered=yes}} | |||
I just went around and corrected a bunch of misspellings: "Tuscon, Arizona" is often written when "Tucson, Arizona" is meant. Because ] is a redirect, many authors do not notice their own error - but they would if the link turned up as a red link. There are reasons to redirect from misspellings to correct spellings, of course, but there is this downside.--] (]) 09:52, 28 October 2011 (UTC) | |||
] (]) 18:26, 27 December 2024 (UTC) | |||
:] '''Not done''': it's not clear what changes you want to be made. Please mention the specific changes in a ] and provide a ] if appropriate.<!-- Template:ESp --> ] (]) 18:34, 27 December 2024 (UTC) |
Latest revision as of 21:28, 28 December 2024
See also: Misplaced Pages talk:Deletion policy/redirects, Misplaced Pages talk:WikiProject Redirect, and Misplaced Pages:Article wizard/version1/RedirectThis is the talk page for discussing improvements to the Redirect page. |
|
This project page does not require a rating on Misplaced Pages's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||
|
Archives |
This page has archives. Sections older than 182 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present. |
Deprecation of redirecting the talk page of a mainspace redirect
A talk page is just a regular page and can therefore also be a redirect. This is sometimes done when turning a page into a redirect and always done when moving a page since that also moves its talk page. Doing this during a move is fine in my opinion but in almost every other case, redirecting a talk page is a bad practice that should be discouraged. The reason is that if someone retargets one of the redirects but forgets to retarget the other, editors who wish to discuss the redirect will do so at the wrong place. Redirecting the talk page also provides no benefit in comparison with {{talk page of redirect}} which already acts like a soft redirect that can update itself when its page is retargeted.
So, my proposal is that we add this to WP:R or WP:TALK:
The talk page of a mainspace redirect should not be redirected unless that was the result of a page move or as specified in WP:TALKCENT. In all other cases, {{talk page of redirect}} should be used instead.
Otherwise we end up with cases like Acts of God (book) where the page itself is a redirect to Acts of God (disambiguation) but its talk page redirected to Talk:Acts of God (novel) before I fixed it. Note that the utility of talk page redirects is much higher in other namespaces. Someone who looks up WT:R probably wants to end up here instead of discussing the redirect itself. So those should be allowed but people should still remember to keep them synced up (not likely that WP:R will ever change but other shortcuts might). I'd also be open to the idea of having a bot sync up such redirects automatically. Nickps (talk) 13:31, 15 April 2024 (UTC)
- Pinging participants of the previous discussion at Wikipedia_talk:Talk_page_guidelines/Archive_8#Are_redirect_talk_pages_also_redirected?: @Aristophanes68, Thryduulf, Johnuniq, Robertgreer, Flatscan, Redrose64, and Lolifofo. Nickps (talk) 13:34, 15 April 2024 (UTC)
- Well, I thought about it again and I'm going about this the wrong way. I'll just ask at WP:BOTR first and if it gets declined then we should consider this. But, if someone else thinks that the change I proposed above is worth making anyway, they are free to pick this up and even open an RfC. Nickps (talk) 23:08, 15 April 2024 (UTC)
- Well, here goes nothing: Misplaced Pages:Bot requests § Bot to sync talk page redirects with their corresponding page. Nickps (talk) 23:44, 15 April 2024 (UTC)
- I vaguely recall some cases where a talk page was kept so that its history was retained. That is, the talk discussion had some possibly useful information regarding the now-redirected associated page? Johnuniq (talk) 04:03, 16 April 2024 (UTC)
- I got pinged, and am here to vote keep for Inclusionism. Deleting, moving, shrinking articles makes some sense to me but I'm a huge proponent of keeping talk pages. I like Misplaced Pages queries to go somewhere useful, and if I end up on a page that doesn't exist, but that I expect to exist, I would like the talk page to already exist explaining why. Mathiastck (talk) 20:52, 29 October 2024 (UTC)
- I vaguely recall some cases where a talk page was kept so that its history was retained. That is, the talk discussion had some possibly useful information regarding the now-redirected associated page? Johnuniq (talk) 04:03, 16 April 2024 (UTC)
- Well, here goes nothing: Misplaced Pages:Bot requests § Bot to sync talk page redirects with their corresponding page. Nickps (talk) 23:44, 15 April 2024 (UTC)
Do not "fix" links to redirects that are not broken
The issue is the "fixing" of correct piped links by making them redirects. That seems at odds with the mentioned: Misplaced Pages:If it ain't broke, don't fix it.
Before I start a new discussion, where was this discussed earlier? The Banner talk 13:33, 20 July 2024 (UTC)
- The most recent discussion was Misplaced Pages talk:Redirect/Archive 2023#NOTBROKEN needs to be moderated. older ≠ wiser 13:43, 20 July 2024 (UTC)
- Hmmm, I took part in that discussion. The Banner talk 16:07, 20 July 2024 (UTC)
- I support starting a new discussion, coming from an inclusionist perspective. Mathiastck (talk) 01:20, 23 July 2024 (UTC)
- I'm not quite sure what the OP is suggesting, but I very strongly agree with the consensus in the previous discussion that replacing ] with ] is something that should not be done. Thryduulf (talk) 11:39, 23 July 2024 (UTC)
- I also agree with that consensus.
- I think the OP was about people changing ] to ]. I think I've seen some consensus that such changes should generally not be done as the only reason for an edit but should instead be done alongside a more substantive edit. Mgp28 (talk) 12:30, 23 July 2024 (UTC)
- As well as I know it, an important reason to use the redirect is that it might be worth its own article someday. For the ] case, one should consider the possibility of a new article, and which one should be used. I suspect most often it should be ], but maybe not always. Gah4 (talk) 17:42, 23 July 2024 (UTC)
- Hmmm, I took part in that discussion. The Banner talk 16:07, 20 July 2024 (UTC)
- Over the past few weeks I've been removing piped links using User:Nardog/Unpipe. In all this work I've had one objection that doing so may create a situation where there are multiple links pointing to the same target, potentially some using one redirect and some using another and some direct. The inconvenience this poses for readers is that their browser can't accurately track which articles they've visited and change blue links to purple appropriately. I don't see this discussed in WP:NOTBROKEN but it does seem to be a valid concern. I have been addressing this by eliminating unnecessary duplicate links and editing the article to use consistent terminology and thus consistent linking. ~Kvng (talk) 14:59, 24 July 2024 (UTC)
- OK, but as above, link names should consider the idea of a possible new page replacing the redirect. I can imagine, though maybe not think of an example, where one might use the redirect, and one not. The context of the links could be different in a way not so obvious to me right now. Gah4 (talk) 19:51, 25 July 2024 (UTC)
- Yes, I frequently run across examples of this. I'll try to remember to pop back here and update next time I run across one. An unpiped link is more robust in terms of WP:ASTONISH and general maintenance this is probably a more important concern than the link tracking. ~Kvng (talk) 15:25, 28 July 2024 (UTC)
- That didn't take long. This edit replaces a piped link with Computer Music Melodian which has potential as a stand-alone article. ~Kvng (talk) 15:39, 28 July 2024 (UTC)
- Yes, I frequently run across examples of this. I'll try to remember to pop back here and update next time I run across one. An unpiped link is more robust in terms of WP:ASTONISH and general maintenance this is probably a more important concern than the link tracking. ~Kvng (talk) 15:25, 28 July 2024 (UTC)
- OK, but as above, link names should consider the idea of a possible new page replacing the redirect. I can imagine, though maybe not think of an example, where one might use the redirect, and one not. The context of the links could be different in a way not so obvious to me right now. Gah4 (talk) 19:51, 25 July 2024 (UTC)
Template redirect categories
Are there any redirect categories for specifically intra-template-namespace redirects? Tule-hog (talk) 09:16, 22 July 2024 (UTC)
- (It seems what I was looking for was {R from template shortcut}, but I suppose the question still stands!) Tule-hog (talk) 22:22, 23 July 2024 (UTC)
Redirects in hatnotes
You are invited to a discussion about the use of redirects in hatnotes at Misplaced Pages talk:Hatnote#Redirects in hatnotes again. Thryduulf (talk) 16:41, 5 August 2024 (UTC)
An input request
In context to WP:BLANKANDREDIRECT, an input request has been made at Misplaced Pages talk:Merging#Any rules of thumb?. Bookku (talk) 09:36, 8 August 2024 (UTC)
New rcat
was split from {{R from modification}}. It doesn't have a unique category and it isn't in the template index yet. Hyphenation Expert (talk) 22:01, 16 August 2024 (UTC)
- I've redirected it to {{R from modification}}. voorts (talk/contributions) 22:04, 16 August 2024 (UTC)
- I've posted on template talk. @Hyphenation Expert, in the future, you should inform the editor who created the template that you're starting a discussion about it. voorts (talk/contributions) 22:18, 16 August 2024 (UTC)
on interpretations of the blar section
for a while now, wp:blar has been interpreted at least in rfd as "undiscussed blars must be restored and taken to afd", with few regards to its content or why it was blar'd. while that's obviously not what it means every time (as always, it's on a case-by-case basis), i've been feeling that the "such as" has to do a little too much legwork to imply that there's more than one option
with that in mind, opinions on naming two or more examples, with something like "...other methods of dispute resolution should be used, such as nominating the article for Misplaced Pages:Redirects for discussion or restoring the article and nominating it for Misplaced Pages:Articles for deletion."? cogsan (nag me) (stalk me) 23:39, 8 October 2024 (UTC)
- Encouraging BLARs to be nominated at RfD is exactly the opposite of what we should be doing, they already come here far too often. The only circumstances in which RfD should be deleting article content that has not been removed with explicit consensus is when that content would be speedily deletable if restored. The "such as" means that AfD is not required in every situation (e.g. talk page or wikiproject discussion is sometimes fine), it does not mean RfD is a suitable venue. Thryduulf (talk) 00:17, 9 October 2024 (UTC)
- per... that one discussion, i'll also disagree with this. for the most part, anyway, case-by-case and all. a blar either not being properly discussed, or being undiscussed entirely, is one part of it. the content it had being unsourced or not properly sourced cruft (as was the case there) is the big issue, that i feel most of your restore votes deliberately ignore. i, at least, trust the people in rfd to be able to look at the history of a blar and determine whether or not its sources (if any were presented) were usable. in the cases of the list of strogg in quake 2 (linked below) and dcvd, for example, they... really weren't. frankly, i'm pretty sure that list would have been bad enough to warrant a specific exception for a7's "not for software" deal at this point
- this doesn't mean there's not a chance that the content was usable, or even downright good, or that there's coverage proceeding the blar or that the blarrer (that's a word, right?) and everyone else just missed until a discussion happened, but as i'm almost tired of seeing, some cases just aren't that. on the chance that they are, nice, but while this might be my pessimism talking, those tend to be the exception to the norm in rfd
- also, i still have no idea why you keep bringing the "blars should only pop up in rfd if they meet csd" thing up. it was already argued against based on your reason for it being a misreading (coincidentally the exact misreading this discussion is about), the thing that was misread mentioning nothing about speedy deletion or the criteria for it, or being a criterion for anything, and your only argument against that being... bringing it up again later like tavix and i never questioned it cogsan (nag me) (stalk me) 02:29, 9 October 2024 (UTC)
- Much of what you are saying doesn't make sense, and much of the rest of it is bizarrely and/or plain wrong - particularly you are misinterpreting my comments about CSD in the same way I had to correct you about more than once in the last discussion. Whether something is "cruft", whether sources are or are not reliable, are discussions of article content that belong in the venues for discussion of article content: AfD, talk pages, etc. not RfD. You may trust RfD participants to undertake research that is not relevant to RfD and that everyone who would comment on an AfD for the article will know it is beign discussed at RfD is endearing but naiive and/or wrong. Thryduulf (talk) 02:40, 9 October 2024 (UTC)
- if i'm misinterpreting your comments about csd, it's because you took over a month to explain them in a coherent way (that is, one that didn't somehow equate rfd to reversion and speedy deletion), and still ended up being "plain wrong" per the policies you yourself cited. i also said nothing about people at afd knowing that something would be discussed at rfd, where did you get that? cogsan (nag me) (stalk me) 11:22, 9 October 2024 (UTC)
- When you actually think (rather than just reading the words of policy without doing so) its very simple: The purpose of requiring deletion of articles to be discussed at AfD is so that both those involved with the article, and those who are interested in and/or knowledgeable about the article and/or its subject know that it has been nominated for deletion. This is done because the community has decided that deletion without this notice is not reasonable. If articles are BLARed then discussed at RfD then only those involved with the article know that the subject has been nominated for deletion, those who watch AfD (and these days also article alerts and deletion sorting lists) because they have opinions about the deletion of articles do not know that an article has been nominated for deletion.
- Content that meets a speedy deletion criterion is an exception to this because notification is not required. Content that has previously been discussed is an exception because the consensus discussion happened previously. Thryduulf (talk) 11:38, 9 October 2024 (UTC)
- this requires that rfd somehow have no one who knows anything about article content, how blars work, how rfd nominations and twinkle work, pop culture references old enough to drink, or that more than one thing can be in rfd at a time, that that 2021 consensus shown in wp:blar be absolute and not "yeah that's usually a good idea" (see the use of "most" in wp:blar), and that that consensus not currently be in the process of being challenged cogsan (nag me) (stalk me) 11:54, 9 October 2024 (UTC)
- It actually requires none of those things. Whether people at RfD are competent in certain topic area is irrelevant, what matters is that the people who are interested in/knowledgeable about the topic area know that article content is being discussed. They know that when articles are discussed at AfD, they don't know that when a redirect is at RfD. Thryduulf (talk) 12:26, 9 October 2024 (UTC)
- problem: nominating something for rfd leaves evidence on the edit history (and thus the watchlist of anyone watching it), twinkle has the option to notify the original creator and/or target talk page, you can just ping someone else involved and presumably knowledgeable, and probably sends a pigeon out to notify you personally (i can't verify this one, i live in a fictional location) cogsan (nag me) (stalk me) 13:08, 9 October 2024 (UTC)
- It notifies those people that a redirect is being discussed, it notifies nobody that article content is being discussed. It notifies nobody who watches AfDs, the AfD section of article alerts, deletion sorting lists (this one isn't absolute but very occasionally RfDs get added whereas almost all AfDs do), etc. Thryduulf (talk) 14:25, 9 October 2024 (UTC)
- ...yes. that's the point. because it's at rfd. because blars are redirects. and redirects can have edit histories. which any voter worth their salt will check cogsan (nag me) (stalk me) 14:28, 9 October 2024 (UTC)
- Except BLARs are not redirects, they are blanked articles. The edit history isn't the issue, it's the deletion of article content. Thryduulf (talk) 15:10, 9 October 2024 (UTC)
- they're redirects with history, see good ol' wp:blar cogsan (nag me) (stalk me) 15:20, 9 October 2024 (UTC)
- That history is an article. That article was blanked without consensus. Therefore it should be restored and discussed as the article it is per WP:BLAR, WP:BRD etc. Thryduulf (talk) 16:54, 9 October 2024 (UTC)
- that's not what either of them say. wp:brd-not explicitly states that brd isn't a reason to revert cogsan (nag me) (stalk me) 17:45, 9 October 2024 (UTC)
- That history is an article. That article was blanked without consensus. Therefore it should be restored and discussed as the article it is per WP:BLAR, WP:BRD etc. Thryduulf (talk) 16:54, 9 October 2024 (UTC)
- they're redirects with history, see good ol' wp:blar cogsan (nag me) (stalk me) 15:20, 9 October 2024 (UTC)
- Except BLARs are not redirects, they are blanked articles. The edit history isn't the issue, it's the deletion of article content. Thryduulf (talk) 15:10, 9 October 2024 (UTC)
- ...yes. that's the point. because it's at rfd. because blars are redirects. and redirects can have edit histories. which any voter worth their salt will check cogsan (nag me) (stalk me) 14:28, 9 October 2024 (UTC)
- It notifies those people that a redirect is being discussed, it notifies nobody that article content is being discussed. It notifies nobody who watches AfDs, the AfD section of article alerts, deletion sorting lists (this one isn't absolute but very occasionally RfDs get added whereas almost all AfDs do), etc. Thryduulf (talk) 14:25, 9 October 2024 (UTC)
- problem: nominating something for rfd leaves evidence on the edit history (and thus the watchlist of anyone watching it), twinkle has the option to notify the original creator and/or target talk page, you can just ping someone else involved and presumably knowledgeable, and probably sends a pigeon out to notify you personally (i can't verify this one, i live in a fictional location) cogsan (nag me) (stalk me) 13:08, 9 October 2024 (UTC)
- It actually requires none of those things. Whether people at RfD are competent in certain topic area is irrelevant, what matters is that the people who are interested in/knowledgeable about the topic area know that article content is being discussed. They know that when articles are discussed at AfD, they don't know that when a redirect is at RfD. Thryduulf (talk) 12:26, 9 October 2024 (UTC)
- this requires that rfd somehow have no one who knows anything about article content, how blars work, how rfd nominations and twinkle work, pop culture references old enough to drink, or that more than one thing can be in rfd at a time, that that 2021 consensus shown in wp:blar be absolute and not "yeah that's usually a good idea" (see the use of "most" in wp:blar), and that that consensus not currently be in the process of being challenged cogsan (nag me) (stalk me) 11:54, 9 October 2024 (UTC)
- if i'm misinterpreting your comments about csd, it's because you took over a month to explain them in a coherent way (that is, one that didn't somehow equate rfd to reversion and speedy deletion), and still ended up being "plain wrong" per the policies you yourself cited. i also said nothing about people at afd knowing that something would be discussed at rfd, where did you get that? cogsan (nag me) (stalk me) 11:22, 9 October 2024 (UTC)
- Much of what you are saying doesn't make sense, and much of the rest of it is bizarrely and/or plain wrong - particularly you are misinterpreting my comments about CSD in the same way I had to correct you about more than once in the last discussion. Whether something is "cruft", whether sources are or are not reliable, are discussions of article content that belong in the venues for discussion of article content: AfD, talk pages, etc. not RfD. You may trust RfD participants to undertake research that is not relevant to RfD and that everyone who would comment on an AfD for the article will know it is beign discussed at RfD is endearing but naiive and/or wrong. Thryduulf (talk) 02:40, 9 October 2024 (UTC)
- Cogsan, I disagree with your premise. "Undiscussed blars must be restored and taken to afd" has never enjoyed consensus at RfD. I would think that Misplaced Pages:Redirects for discussion/Log/2024 September 17#List of Strogg in Quake II would have disavowed you of that idea. That said, I don't think WP:BLAR needs any changes. If an editor blanks and redirects an article and another editor sees it right away disagrees with the blank-and-redirection, the best option is to restore the article and have it taken to AfD. The ones we usually see at RfD don't really make sense in the context you're quoting because there is no ongoing disagreement between editors on whether or not the page should be an article or not. If a page was redirected in 2009 and it's just now coming to RfD, it's been a redirect for a long time and should be evaluated as such. If the underlying content looks like it may be notable, restore it. If not, delete it. -- Tavix 00:45, 9 October 2024 (UTC)
- i didn't say i thought that, i said it tended to be interpreted that way. i wouldn't turn to the dark side this fast, even if the dark side has cookies cogsan (nag me) (stalk me) 00:51, 9 October 2024 (UTC)
- I know you don't think that, but even "tends to be interpreted that way" gives way too much credence to a vocal minority. -- Tavix 00:56, 9 October 2024 (UTC)
- fair lol. still not a fan of how easy it is for said vocal minority to start discussions spanning 2 months that end up amounting to having missed two words in a paragraph, but eh cogsan (nag me) (stalk me) 01:01, 9 October 2024 (UTC)
- I know you don't think that, but even "tends to be interpreted that way" gives way too much credence to a vocal minority. -- Tavix 00:56, 9 October 2024 (UTC)
- i didn't say i thought that, i said it tended to be interpreted that way. i wouldn't turn to the dark side this fast, even if the dark side has cookies cogsan (nag me) (stalk me) 00:51, 9 October 2024 (UTC)
- That change to BLAR would contradict WP:ATD-R, which states that contested BLARs should be discussed on talk or at AfD. This reflects consensus from 2018 and 2021 RfCs. voorts (talk/contributions) 00:46, 9 October 2024 (UTC)
- eh? that one also only provides restoring and sending to afd as an example (see the use of "include"). this is the exact kind of case this is about cogsan (nag me) (stalk me) 00:53, 9 October 2024 (UTC)
- I interpret the Quake discussions as exceptions to the rule per WP:BURO , given the ages of the redirects and their complete lack of encyclopedic content. The general rule that things should go to AfD holds in most cases and we should not muddy the waters by affirmatively stating that RfD might be appropriate. voorts (talk/contributions) 00:58, 9 October 2024 (UTC)
- then shouldn't it say that afd is usually the way to go, as opposed to only naming it as an option? i'm starting to think that the way it's currently written doesn't look good for either side cogsan (nag me) (stalk me) 01:05, 9 October 2024 (UTC)
- I'll start a discussion to do so at WT:DELETE. voorts (talk/contributions) 01:15, 9 October 2024 (UTC)
- then shouldn't it say that afd is usually the way to go, as opposed to only naming it as an option? i'm starting to think that the way it's currently written doesn't look good for either side cogsan (nag me) (stalk me) 01:05, 9 October 2024 (UTC)
- I interpret the Quake discussions as exceptions to the rule per WP:BURO , given the ages of the redirects and their complete lack of encyclopedic content. The general rule that things should go to AfD holds in most cases and we should not muddy the waters by affirmatively stating that RfD might be appropriate. voorts (talk/contributions) 00:58, 9 October 2024 (UTC)
- Discussion started. voorts (talk/contributions) 01:26, 9 October 2024 (UTC)
- nice-a. gonna dip my toes there when i've had my sleep cogsan (nag me) (stalk me) 02:30, 9 October 2024 (UTC)
- eh? that one also only provides restoring and sending to afd as an example (see the use of "include"). this is the exact kind of case this is about cogsan (nag me) (stalk me) 00:53, 9 October 2024 (UTC)
redirects to death of.... articles
I've been looking for any editorial policy or styleguide on Redirects from a person's name towards the article about incident which caused their death. I recall reading the debate that when we have an article which is specifically about the incident (accident, crime etc.) which caused someone's death, but they would not otherwise have been considered Notable for a WP Biography, we should name the article "death of..." or "murder of...", "killing of..." etc., and not merely their name. But, I cannot find anything about redirects for issue. Does anyone know of a consensus on this, one way or the other?
We have Misplaced Pages:Naming conventions (violence and deaths) - which is about the naming convention of the article itself. Do we have a policy for whether to, or whether to NOT create a redirect from their name to that article? If so, could it please be added to the list of valid reasons Reasons FOR deleting or Reasons for NOT deleting a redirect?
The primary argument that we should create such a redirect is because it aids findability/SEO from the most likely search term (e.g. Tessa Majors redirects to murder of Tessa Majors). The primary argument that we should not create such a redirect is the same as for having the "death of..." naming convention in the first place – that a person's biography shouldn't be defined by the manner of their death (especially if the only reason they're known to the public is because they became someone else's victim).
I'm not expressing a judgement or vote! on either option, but it would be helpful if "NAME -> death of NAME" could be added to the list of valid or invalid reasons for a redirect. Wittylama 10:39, 13 November 2024 (UTC)
- I would think that the advantages generally outweigh the disadvantages, and if the person is notable for any other reason the redirect may encourage someone to write the article. · · · Peter Southwood :
- Anyone searching or such an article would know the name of the person, but not necessarily the article title, which could take on any one of several forms – Death of, Drowning, Fatality, Incident etc, so the name would be the most useful search string, and could plausibly be the most common way to try to find the article, so I think it should be a redirect unless ambiguous. · · · Peter Southwood : 14:45, 13 November 2024 (UTC)
- If I saw a "Death of ..." redirect while doing WP:NPP work, and it pointed to a section on the person's page regarding their death or to a relevant article about it, I'd mark it as patrolled. It's a useful search term and I don't see it as being likely to be deleted at RfD for that reason. Hey man im josh (talk) 15:44, 13 November 2024 (UTC)
Talk page scope
What is the difference between here and WT:WikiProject Redirects? These two talk pages seem like they ought to be centralized. Sdkb 06:31, 20 November 2024 (UTC)
Deletion nomination of soft redirects
You are invited to join the discussion at Misplaced Pages:Templates for discussion/Log/2024 November 19 § Template:Wikispecies redirect. Sdkb 06:32, 20 November 2024 (UTC)
Misplaced Pages:Redirect assimilation
FYI, Misplaced Pages:Redirect assimilation (edit | talk | history | links | watch | logs) was created to redirect to Misplaced Pages:Redirect#Do not "fix" links to redirects that are not broken -- 65.92.246.77 (talk) 21:28, 20 November 2024 (UTC)
Semi-protected edit request on 21 November 2024
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add WP:ASSIMILATION to the shortcut list of § Do not "fix" links to redirects that are not broken. No source needed since it's pretty obvious. 67.209.130.52 (talk) 19:16, 21 November 2024 (UTC)
- Completed. P.I. Ellsworth , ed. 20:09, 21 November 2024 (UTC)
I have undone this change. It is by no means obvious to me what this has to do with "assimilation", and there are no nontrivial incoming links. I think this redirect should probably be deleted. --Trovatore (talk) 23:26, 21 November 2024 (UTC)
Listed for RfD at Misplaced Pages:Redirects for discussion/Log/2024 November 22#Misplaced Pages:Redirect assimilation. --Trovatore (talk) 03:16, 22 November 2024 (UTC)
See related recommended best practice proposal
At Wikipedia_talk:Deletion_policy#Propose_addition_of_the_following_best_practice_to_redirection_section concerning recommending the use of {{Uw-blar}} Piotr Konieczny aka Prokonsul Piotrus| reply here 02:18, 17 December 2024 (UTC)
Semi-protected edit request on 27 December 2024
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
156.229.32.214 (talk) 18:26, 27 December 2024 (UTC)
- Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. ObserveOwl (talk) 18:34, 27 December 2024 (UTC)