[go: nahoru, domu]
Jump to content

Wikipedia:Redirects for discussion/Log/2018 June 4

Add links
From Wikipedia, the free encyclopedia

June 4

[edit]

This is a list of redirects that have been proposed for deletion or other action on June 4, 2018.

O2-

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was retarget to O2. (non-admin closure) feminist (talk) 03:10, 12 June 2018 (UTC)[reply]

Ambiguous, could also refer to Oxide. {{3x|p}}ery (talk) 23:19, 4 June 2018 (UTC)[reply]

The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Windows media player classic

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was retarget to Media Player Classic. (non-admin closure) feminist (talk) 03:10, 12 June 2018 (UTC)[reply]

WP:XY - CHAMPION (talk) (contributions) (logs) 23:12, 27 May 2018 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, Galobtter (pingó mió) 20:25, 4 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Draft:Kanwarjit Singh, popularly known by the name, Kanwarjit Singh Rozi Barkandi, is an Indian politician. He is an MLA from Sri Muktsar Sahib, Punjab. He won the 2017 Punjab Vidhan Sabha elections as a Shiromani Akali Dal candidate.

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was speedy delete. This redirect is not the result of a move from the draft namespace to the article space (that redirect is at Draft:Kanwarjit Singh). So, this page is not the result of an R from move to the current title and, according to a strict interpretation, RDRAFT only applies to redirects created as the result of a move from the draft namespace to article space. — Preceding unsigned comment added by DrKay (talk • contribs) 20:43, 4 June 2018 (UTC)[reply]

Effectively the entire article in the title as a (cross-namespace) redirect. Not at all useful. ƒirefly ( t · c · who? ) 20:16, 4 June 2018 (UTC)[reply]

The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
  • @DrKay: Thanks for explaining what happened in your closing statement. I see it now; I was looking at this diff, and was unable to make out what happened thanks to the long title taking up the entirety of the viewable edit summary. After you closed the discussion, I saw this diff, and can confirm what you stated happen did indeed happen. Steel1943 (talk) 20:48, 4 June 2018 (UTC)[reply]
    That is what I just figured out. It was a Draft to Draft redirect that a bot modified. Legacypac (talk) 20:51, 4 June 2018 (UTC)[reply]
    @Legacypac: Yep, and at this time, WP:RDRAFT doesn't say anything about keeping redirects in the "Draft:" namespace that were {{R from move}}s into another title in the "Draft:" namespace. As far as I see, I would have supported deletion if I had known the correct story from the get-go. Steel1943 (talk) 20:57, 4 June 2018 (UTC)[reply]

Sushi grass

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was retarget to Sushi#Condiments. ~ Amory (u • t • c) 01:12, 12 June 2018 (UTC)[reply]

Not mentioned at target page. Readers looking fir information pertaining to the subject of the redirect will not find information pertaining to what they are looking to find. Steel1943 (talk) 18:50, 4 June 2018 (UTC)[reply]

The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Gomyeong

[edit]

Relisted, see Wikipedia:Redirects for discussion/Log/2018 June 13#Gomyeong

Wikipedia:NODRAFT

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was keep per WP:SNOW. -- Tavix (talk) 13:21, 5 June 2018 (UTC)[reply]

This redirects to an essay that lacks support and has no links to it. The redirect has been used once in a now archived page. The only other use is at the top of the target page. Legacypac (talk) 18:11, 4 June 2018 (UTC)[reply]

  • What? This is a shortcut to a personal essay, which I was under the impression essay creators were free to choose as they wished. I understand the essay "lacks support", that's why it's in my userspace. The shortcut is sparsely-referenced because the essay is new and I haven't posted it around very much. Is there another place this redirect should be pointing? I don't understand. A2soup (talk) 18:16, 4 June 2018 (UTC)[reply]
P.S.: WP:SHORTCUT is a guideline. Paradoctor (talk) 23:21, 4 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Trevor Engelson

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was delete. --BDD (talk) 17:41, 13 June 2018 (UTC)[reply]

Engelson is best known and most notable as the producer of Remember Me (2010 film), All About Steve, Heathers (TV series), Incarnate (film), Outpost 37, Zoom (2006 film) and Snowfall (TV series) not as an ex-husband. DrKay (talk) 16:50, 4 June 2018 (UTC)[reply]

  • Comment: I'm not sure what the purpose of this nomination is. Do you think it's better to have no redirect at all for this name, even though Meghan Markle appears to be the only place on WP where Engelson is mentioned in the text of an article (rather than just in the infobox)? Do you think the redirect should have a different target—and, if so, which article? The closer of the last AfD about the Engleson article, less than a year ago, expressly left a door open for recreation of the article if adequate sources could be found, so if you think that he is "most notable" for film and TV production, why not overwrite the redirect with an acceptable article focusing on that aspect of his life? Deor (talk) 17:50, 4 June 2018 (UTC)[reply]
  • Comment overwrite the redirect with a sentence thst says he is a film producer who was married to Markle. He is clearly 100% notable and no reason suchba stub would be deleted. Is there a page under the redirect to revert too? Legacypac (talk) 19:22, 4 June 2018 (UTC)[reply]
    • No, article content this title has been deleted at AfD twice. It was created directly as a redirect in its present incarnation. The last AfD was closed by SoWhy with the summary "The result was delete. At this point, consensus is in favor of deletion, however, DESiegel, once you have access to more sources, I see no reasons here for you not to restore the article to work on it (let's call it a "somewhat soft delete")." Redirection was not mentioned by anyone in either discussion. Based on that, the content could be undeleted to draft or userspace by request of someone who wants to work on it (personally I'd restore that over the redirect, move it to the desired location and then retarget the resulting redirect back to the current target). I would not recommend recreating the article without getting feedback about the expanded draft and its sourcing first. Thryduulf (talk) 23:59, 4 June 2018 (UTC)[reply]
  • Delete for likely article creation. While he narrowly got deleted last time, he looks notable now.  — SMcCandlish ☏ ¢ 😼  11:50, 5 June 2018 (UTC)[reply]
  • Either retarget to Family of Meghan Markle (and make a section for him there as her ex-husband, or delete for article creation per above. He's definitely notable enough. Paintspot Infez (talk) 18:58, 6 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Silver ore

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was retarget to Silver#Occurrence and production. Seems well-covered there ~ Amory (u • t • c) 01:14, 12 June 2018 (UTC)[reply]

The target article does not seem to identify or define the subtopic as described by the redirect. To compare, Copper ore redirects to List of copper ores, so there may be reason to delete this redirect per WP:REDLINK. Steel1943 (talk) 13:54, 4 June 2018 (UTC)[reply]

The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Life Is Strage 2

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was Speedy delete per WP:CSD#G7 (and possibly WP:CSD#G6 too). Thryduulf (talk) 15:25, 4 June 2018 (UTC)[reply]

Delete. Was a typo. Probably not a misspelling many people will make. Interqwark talk contribs 11:16, 4 June 2018 (UTC)[reply]

The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Archbishop of London

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was disambiguate. (non-admin closure) feminist (talk) 03:11, 12 June 2018 (UTC)[reply]

Should this target Bishop of London (who isn't an archbishop), or Coptic Orthodox Church in Britain and Ireland#Coptic Orthodox Diocese of London (the target of the redirect Coptic Orthodox Archbishop of London, who is an archbishop, but maybe not the one that readers are searching for)? Shhhnotsoloud (talk) 08:16, 4 June 2018 (UTC)[reply]

  • Disambig. I'm seeing approximately equal uses referring to the coptic archbishop and mistaken references to the Bishop of London. Archbishop of Southwark and Archbishop of Westminster would make good see alsos, being archbishop's of places in the heart of London. There is also a David Bell who is a self-proclaimed Archbishop of London as leader of a Catholic splinter group [1], we don't have any coverage of him or his group that I have found, and I'm not immediately convinced he/they are notable but I've not looked deeply and this is not a topic area I'm familiar with - if we do have or gain content though then it should be mentioned on dab page. Thryduulf (talk) 10:23, 4 June 2018 (UTC)[reply]
  • I've drafted a disambiguation page. This is a bit thorny, since there's really only one reasonably accurate use of the term (the Coptic archbishop), but it seems unlikely to be what readers would be looking for. Since the page would be almost all misnomers anyway, I threw Archbishop of Canterbury on there. I figured someone unfamiliar with the Church of England might assume its leader would have such a title. Too much of a stretch? --BDD (talk) 19:52, 4 June 2018 (UTC)[reply]
    • Not too much of a stretch for me. I've expanded the descriptions slightly to give a bit more context, noting the archbishops of Southwark and Westminster are Roman Catholic and that the Bishop of London is sometimes mistakenly referred to as an archbishop (something one source I found earlier implied was not just a recent phenomenon). Thryduulf (talk) 00:05, 5 June 2018 (UTC)[reply]
    Good, thanks. I like those changes. --BDD (talk) 01:33, 7 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Cherokee citizen

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was keep with Paradoctor's refining. (non-admin closure) Ben · Salvidrim! ✉ 16:31, 11 June 2018 (UTC)[reply]

This is a relatively specific redirect pointing to a very broad target. Do we have any material that specifically addresses Cherokee citizenship? Oiyarbepsy (talk) 02:59, 4 June 2018 (UTC)[reply]

My bad for not remembering or realizing that! Still, I think the contemporary Cherokee Nation might have something of a primary topic claim to this. I've also just come across Cherokee cultural citizenship, which could use work, but might ultimately be the best place to point this, especially if its scope can be expanded beyond the Cherokee Nation. I'm always a bit wary of instances of "Foo bar" redirecting to "Foo", since presumably readers searching on the longer term would already know to check the shorter. --BDD (talk) 17:33, 4 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Mos:

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was keep. I'll admit to being surprised by this result. Compared to the others yesterday (Wikipedia:MOS and MoS:), these have somehow garnered the most attention and numerically the most support. I could mostly echo my close yesterday for MoS:, especially that the helpfulness argument is persuasive; I encourage you to read it. That being said, I do find the arguments for keep less strong here, as there's some nuance beyond painting these all with the same brush: there are upper-, lower-, and mixed-case letters after the mos: prefix, and while many are quite old, some have been created just a few months ago. As such, by my read this is has a hint of traincwreckiness to it, and as with the previously-linked discussions, this close should not preclude the nomination of individual redirects created after and in contrast to the 2014 RfC, provided there is a good rationale for doing so. Still, this discussion was about pseudo-namespace redirects (PNRs, or PXNRs) with a given prefix, and on that basis, consensus here is to keep these. ~ Amory (u • t • c) 15:44, 12 June 2018 (UTC)[reply]
Extended content

Formally nominating these because SMcCandlish opined on them and because that opinion differed from the other set. Pinging others: (SnowFire—Thryduulf—rogerd). — Godsy (TALKCONT) 01:06, 4 June 2018 (UTC)[reply]

Moved from Wikipedia:Redirects for discussion/Log/2018 June 3 § MoS:
Judging from the number and the age range of these redirects, I am not the only one who finds them useful. Paradoctor (talk) 01:35, 4 June 2018 (UTC)[reply]
  • Keep Per Paradoctor --rogerd (talk) 01:52, 4 June 2018 (UTC)[reply]
  • Keep Lowercase titles of other redirects (MOS:XXXX).  Nixinova  T  C  02:32, 4 June 2018 (UTC)[reply]
  • Keep per WP:CHEAP and per WP:R#KEEP point 5 - as further evidence of their utility I spot checked the usage figures for about half a dozen of these redirects and all of them were used - 150 times last year in one case. Even if they weren't this well used, there would be no benefit to deletion. Thryduulf (talk) 03:04, 4 June 2018 (UTC)[reply]
  • Delete as pseudo-pseudo-namespace pollution of mainspace. While we have a long-standing consensus to have a few defined pseudo-namespaces, including "MOS:", it must be remembered that these actually live in mainspace. Every single time we create a non-article in mainspace we increase the risk of colliding with a real-world topic, and also make mainspace maintenance more difficult. Thus, we absolutely should not create duplicates of pseudo-namespace shortcuts at misspellings of the pseudo-namespace (i.e. we are not duplicating shortcuts like WP:CONSENSUS at "QP:CONSENSUS" or "EP:CONSENSUS" in case people's fingers are misaligned on their keyboards). Those particular redirects are not, in fact WP:CHEAP at all. We need plausible-typo redirects in mainspace for things like Arnold Schwarzeneger, to help millions and millions of readers find the actual content this site is all about. We have no such rationale for trying to account for every possible typo in entering a cross-namespace shortcut for editorial hyper-convenience. That's the tail wagging the dog. While I'm in a "weak keep" stance on the "MoS:" versions of these (separate RfD), because in running prose it's common to refer to WP:Manual of Style as "MoS", no one calls it "Mos", and we have no namespace or pseudo-namespace in sentence-case ("Xyyy...") form. There is thus no excuse for "Mos:" in a bunch of redirs in mainspace. @Paradoctor, Rogerd, Nixinova, and Thryduulf: Pinging previous commenters because I'm skeptical they've considered all these factors. This is not a typical "redirects are cheap" case.  — SMcCandlish ☏ ¢ 😼  04:10, 4 June 2018 (UTC)[reply]
  • It seems to me that there are actual (minor) benefits, while the potential harm is insignificant. While SMcCandlish's argument is essentially good, does it really apply? People do type "mos" which is why these were created. Capitalization is quite different to spelling errors, because of the way that people usually expect URLs and searches to be case insensitive, so I don't think comparisons between "WP" and "QP" or "EP" are valid. Also is namespace collision really an issue here? I can't see there ever being a large number of articles created beginning with "Mos:", but even there were, it takes no more effort to replace the redirect with the article than if the redirect didn't exist. The only potential issue is if the article creator doesn't create any other redirects, e.g. they make the article "Mos:DP" (wut rly) but not "Mos:dp", so a redirect unexpectedly points out of article-space, however again is this really significantly worse than having no redirect at all? ··gracefool 💬 07:32, 4 June 2018 (UTC)[reply]
  • Let's not commingle "accidentally type" and "intentionally use". By mis-defining "use" or "type" in constructions like "I have used this" or "people do type it", we might as well never, for any reason, ever delete a misspelled redirect in any namespace, and actually go create numerous more of them that have nothing to do with getting readers to articles. There are 1,078 "MOS:" shortcuts you need to go make "Mos:" copies of, and by your reasoning every single "CAT:" shortcut badly needs a "Cat:" duplicate. The idea just doesn't hold up to scrutiny. While we quite grudgingly have a shaky consensus to permit a handful of pseudo-namespaces at all (and many editors oppose them, including in ongoing threads right now), permitting pointless duplication of them at redundant "case typos" – which are going to be accidentally used by a tiny number of people but intentionally by nearly zero, this could easily encourage those already skeptical or angry about pseudo-namespaces to go on the warpath. You're taking a "give me convenience of give me death" suicide-pact approach, probably without realizing it.

    An missing-the-big-picture "keep non-misleading redirects if ever possible, at all costs" WP:LOCALCONSENSUS effect is going on here. If I go RfC this at WP:Village pump ("Should we permit expansion of pseudo-namespaces like 'MOS:' to cover typo versions like 'Mos:' for editor convenience?"), the result with be a WP:SNOWBALL "No". I would bet real money on it. We're here to work on an encyclopedia, not make the encyclopedia and its article namespace do cute tricks that piss off lots of other editors just to save us 0.5 seconds of hitting backspace over 2 characters. The amount of time you and I have already spent talking about this has probably exceeded the total amount of time saved by all editors on the system by this handful of bogus redirects for the entire time that they've existed.

    PS: Something notable named or abbreviated "Mos:something" could appear at any second. Please take a stroll through our redirects and see how many odd text strings like this exist in them and point to real articles. CP/M, ST:TWoK, E=mc², F102, etc., etc., etc., They come up all the time in computing, science, entertainment, product names, and more. Lack of a "Mos:" one right this moment is pure (and probably temporary) coincidence. [Some of them are already broken by our Mediawiki being coded to treat language code prefixes case-insensitively. E.g., you cannot do [[ST:TWoK]] directly; I had to pipe to STTWoK. Let's not introduce more namespace problems than we have to.] Anyway, I can't make the case any clearer, so I'll stop and go back to my game of TES4:OB.
     — SMcCandlish ☏ ¢ 😼  08:30, 4 June 2018 (UTC)[reply]

  • "risk of colliding with a real-world topic" As gracefool pointed out above, this is a non-issue. There are no actual collisions, not even with Mos Def or MOS Technology or Mos Eisley. And if one were to happen, we redirect or create the article content, then place a hatnote, if deemed appropriate.
"trying to account for every possible typo" Who does? We certainly should not indiscriminately create typo redirects, but nobody is proposing that. The one I created, I created to address an actual issue I have. Presumably, the other editors did the same.
"The amount of time you and I have already spent talking about this has probably exceeded the total amount of time saved" Achieving consensus with my fellow editors is worth it. Also, there is the issue of motivation / retention. Different contributors have different styles. Accomodating them when there is no harm in doing so is a good thing.
Are the redirects useful to some of us? I assert it, and I see nobody disagree. Also, as Thryduulf pointed out, they are in active use.
Are the redirects harmful? SMcCandlish pointed out a risk, but there does not seem be an actual instance, at least not among the 39 delinquents brought before us.
Would deleting them improve Wikipedia? Not on the evidence so far. Paradoctor (talk) 10:29, 4 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.

Kaijing

[edit]

Relisted, see Wikipedia:Redirects for discussion/Log/2018 June 13#Kaijing

Lutte a la corde

[edit]

The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
The result of the discussion was delete. --BDD (talk) 13:57, 13 June 2018 (UTC)[reply]

Delete per being based on a lie. I am seeking deletion for this article, as it is an untruth that I believe to have been added mischiveously, without citations, in 2006, to both the main article and the redirect, by the same editor. I have been unable to find any proof that this term was ever used to describe Parliamentary Ping-Pong, and the only references to this term are dated AFTER this untruth was added to the encyclopedia - a regrettable instance of Circular reporting. I firmly understand this to be an untruth that was added in jest - I am unsure how to 'prove' this exactly, given that this has now been repeated in media outlets over the past 12 years since the redirect's creation, and the inclusion of the lie in the target article. I understand I cannot cite my expertise on wikipedia, but for what it is worth I am a Parliament and Constitution expert working for Parliament.

See the target article history for the un-cited line that introduced this untruth - I have now excised it. ShieldMaidens (talk) 16:40, 4 June 2018 (UTC)[reply]

In addition, a quick search will show the phrase has never been used in Hansard as far back to 1803. ShieldMaidens (talk) 16:50, 4 June 2018 (UTC)[reply]

Delete — I can't find anything to disagree with the above case on Google Books or Google News. Ralbegen (talk) 17:01, 7 June 2018 (UTC)[reply]
The above discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Redirects_for_discussion/Log/2018_June_4&oldid=1036305288"