This page uses content from Wikipedia and is licensed under CC BY-SA.

Wikipedia:Village pump (all)

This is the Village pump (all) page which lists all topics for easy viewing. Go to the village pump to view a list of the Village Pump divisions, or click the edit link above the section you'd like to comment in. To view a list of all recent revisions to this page, click the history link above and follow the on-screen directions.

Click here to purge the server cache of this page (to see recent changes on Village pump subpages)


Village pump sections

Edit-find-replace.svg
Policy
watch
To discuss existing and proposed policies

Preferences-system.svg
Technical
watch
To discuss technical issues. For wiki software bug reports, use Phabricator

Dialog-information on.svg
Proposals
watch
To discuss new proposals that are not policy-related. See also: perennial proposals.

Tools-hammer.svg
Idea lab
watch
To discuss ideas before proposing them to the community and attempt to find solutions to issues

Help-browser.svg
Miscellaneous
watch
To post messages that do not fit into any other category

View all village pump sections at once

Other help and discussion locations
I want... Where to go
...help using or editing Wikipedia Help desk
...to find my way around Wikipedia Department directory
...specific facts (e.g. Who was the first pope?) Reference desk
...constructive criticism from others for a specific article Peer review
...help resolving a specific article edit dispute Requests for comment
...to comment on a specific article Article's talk page
...to view other Wikimedia projects Wikimedia Meta-Wiki
...to learn about citing Wikipedia in a bibliography Citing Wikipedia
...to report sites that copy Wikipedia content Mirrors and forks
...to ask questions or make comments Questions


Contents

Discussions older than 7 days (date of last made comment) are moved to a sub page of each section (called (section name)/Archive).

Policy

Do "sister cities" belong in top-level articles about cities?

It seems like a huge number of articles about cities end with a list of sister cities, and I'm feeling skeptical about the practice. For some (Chandler, Arizona) we have more or less incidental links, and there is very little to say. For others (Chicago) we have extensive sections with dozens of little flag icons, but is this material as important to include there as, say, Maxwell Street (mentioned only in the name of a food), or Boystown, which gets one line? (indeed, following that latter link it appears even Boystown, Chicago redirects in a way that tends to minimize the demographic implications and cultural attractions associated with the term)

Now I want to be clear - such material is often cited, almost certainly true, and therefore should have a place in Wikipedia. However, that place should be somewhere that it is relevant, and the question I want to raise is whether it is relevant to a city as a whole. This is much the same question as comes up with "international reactions" to mass shootings and other popular culture events. My initial feeling is that the connection here is weaker, because with a mass shooting you have one massacre and one set of international reactions; but with a city you have a vast number of ongoing events, and only a handful of nominal events about sisterhood. We do have articles like List of sister cities in Europe, which to me seem like the place where these things belong.

Opinions? Wnt (talk) 21:42, 22 June 2018 (UTC)

I assume you're suggesting that we (1) create and build List of sister cities in Africa, List of sister cities in Asia, List of sister cities in Australia, List of sister cities in North America, and List of sister cities in South America (are there any sister cities in Antarctica?), (2) replace the content at Chicago#Sister cities with {{Main|List of sister cities in North America#Chicago}}, and (3) repeat 2 for every other sistered city on the planet. Is that correct?
Have you considered the magnitude of such a project? Would it be worth the massive amount of editor time required? Or would it be just reorganizing information with insufficient cost-benefit justification? I think the WP:WIP pile is already far too large, and I'm leaning toward the latter. My opinion might change if (1) there were a consensus that it would significantly improve the encyclopedia, AND (2) one or more editors would commit to getting the job done within, say, two months. ―Mandruss  22:50, 22 June 2018 (UTC)
We have List of twin towns and sister cities in North America, List of sister cities in the United States, and Category:Lists of sister cities in the United States with many state lists, but nothing for Chicago or Illinois (except the odd List of sister cities of Springfield, Illinois which is shorter than Springfield, Illinois#Sister cities). PrimeHunter (talk) 23:34, 22 June 2018 (UTC)
Then at a minimum we would have to agree on conversion from the existing uncoordinated hodgepodge to some coherent and consistent structure, so as to at least give the appearance that this project's left hand knows what its right hand is doing. And still within a reasonable time frame. ―Mandruss  23:41, 22 June 2018 (UTC)
Wnt's question implies a false dilemma. You can have Chicago's sister cities in the article, and also have more information about Maxwell Street and Boystown. The most relevant article to list sister cities of Chicago is in the article about Chicago. Jack N. Stock (talk) 00:04, 23 June 2018 (UTC)
  • Comment I'll refrain from excessive editorializing on "sister cities", but suffice it to say that I think the concept is stupid and a waste of space to discuss here in the exhaustive detail that is present. However, as there is no shortage of space here, I can't make a good argument to remove them. power~enwiki (π, ν) 00:04, 23 June 2018 (UTC)
  • I tend to agree it's non-encyclopedic information; this stuff actually changes all the time, and is primarily for the entertainment and [something, I'm not sure what the word is] of residents, and for tourism promotion. It doesn't actually tell us anything informative about the cities. Festooning these lists with flag icons, even if we keep the lists, is against MOS:ICONS.  — SMcCandlish ¢ 😼  19:47, 28 June 2018 (UTC)
I believe that sister-cities is WP:TRIVIA (though I assume some are interesting enough to warrant proper inclusion). That they are trivia is easily established by seeing that such lists are almost always just that: a list of cities with nothing else to say about it. (In that regard, Chicago's piece is better than most). Wnt's point may technically be a "false dilemma" because size is no restriction, but burdening the article with trivial crap is hardly a plus for the encyclopedia. Maintaining a list of deep-dish pizzerias in Chicago would be just as verifiable and more useful than the list of sister cities (and, frankly, do more to tell you about the place). Matt Deres (talk) 21:12, 30 June 2018 (UTC)
Just on Chicago alone in the last month, you have international political meetings, medical initiatives and agreements, connecting with sister cities. So yes, they can tell about a city in the world, and no, it's not trivial. Alanscottwalker (talk) 21:38, 30 June 2018 (UTC)
And yet for some reason you haven't added that stuff to the article - why not? My guess is that it's because many, many, many significant things happen in Chicago all the time and the stuff you listed was, in the long run, not that big a deal. So the mayor of Birmingham visited - so what? So did the mayor of San Juan and London - are those visits less worthy of inclusion because San Juan and London aren't sister cities? Matt Deres (talk) 22:23, 30 June 2018 (UTC)
Your question is bizarre. You don't add everything to an article section, the article already covers it. Alanscottwalker (talk) 22:28, 30 June 2018 (UTC)
My purpose was to point out that the actions ascribed to sister-city status are no less trivial than the notion of sister-cities themselves. You don't want to add those links to the article (rightly) because even though they may technically be notable in the WP sense, they have no business in an article about the city as a whole. So it is with the list itself. It's just meaningless political glad-handing. Matt Deres (talk) 04:07, 1 July 2018 (UTC)
So, your purpose is to restate your evidence free feelings by making bizarre questions with bizarre assumptions, thus when faced with evidence all you can do is re-state your evidence free feelings. We will have to disagree. Cities are body politics. But when you write about crime in a city, you do not put everything in that section, and when you write about city architecture, you don't put everything in that section, and when you write about city food you don't put everything in that section. And when you write about cross-cultural, cross-international, international organizations and agreements of cities, it does not mean you do not cover it. Just because you don't like the city's choice of politics, or their chioce cross-cultural relationships, or their international economics is no reason. -- Alanscottwalker (talk) 10:16, 1 July 2018 (UTC)
Even if you take a city article with type of section, which sure can be improved, of which you have expressed your stronger dislike, Mineral Point, Wisconsin. In reading the rest of the article, you know exactly why it was important for that city to have a sister city agreement with a city in Cornwall, why you see multiple Cornish flags and signs about their Cornish sister city in that small town in the middle of America, and it's not because it's not important to them. -- Alanscottwalker (talk) 11:13, 1 July 2018 (UTC)
  • I'll add my name to those who feel that sister cities are cringe-worthy and should be removed altogether except in cases where the relationship is significant to history. Zerotalk 11:52, 1 July 2018 (UTC)
  • Comment: Frequently it is relevant to the city as a whole. There's usually some reason why two cities are paired. For example:

Those are the kind of things that get cities paired. Interestingly, that means you can learn something about one city by looking at its sisters. — Mr. Guye (talk) (contribs)  03:24, 6 July 2018 (UTC)

@Mr. Guye: This is a fair point. However, the article for Minneapolis just presents a list of 12 sister cities, of which one in Somalia is actually pretty recent. It says elsewhere in the text that Minneapolis has a large Somali community. Such a place might be a fair spot to mention in passing that Minneapolis has a sister city on this basis, linking perhaps to a sister cities sub-article that lists all the sister cities of cities in the U.S. or something. I don't think the section as it is is really so useful. Wnt (talk) 23:38, 13 July 2018 (UTC)

Not a democracy?

As a direct result of 17 years under the current model, content policy and guideline have become so complex, watered down, and self-contradictory as to be all but useless in governing content. For most disputed content, equally convincing policy arguments can be made for and against, and routinely are. Supporters make policy arguments A and X, opposers make policy arguments B and Y, and the closer (if any) is not allowed to decide which side has the weightier arguments because that would be a supervote. The only requirement, even when it's enforced, is that we make some kind of cogent connection to some policy, which is fairly easy for any editor well-versed in policy. Even if all participants are acting in good faith, which is rare, this leaves content arguments heavily dependent on editorial discretion and judgment, which are extremely susceptible to natural human bias. Looked at with stark clarity and objectivity, consensus comes down to the POVs of the editors present, and Wikipedia editing has become the democracy that it claims not to be.

For this reason, I sit out a majority of the content discussions that I see in the AP2 area. I have strong feelings in that area, and I'm not comfortable being (much) a part of what I see as a fundamentally broken system. I participate when I feel that policy clearly points us in one direction, and that's rare.

I'm posting this because I think it's a worthwhile discussion and not inappropriate for this page—even if there is no viable solution—and in the hope that I can be persuaded that my thinking is flawed. This is very different from the recurring "Wikipedia has a [liberal or conservative] bias" discussion, one of which was recently closed after 56 hours as a waste of time. Perhaps it can be received as something other than pointless heresy worthy of a speedy close. That said, I know these things usually degenerate into pointless bickering, and it would need to be closed at that time.

Comments? ―Mandruss  18:24, 24 June 2018 (UTC)

I would say that a lot of issues would be eliminated related to AP2 and many other ongoing controversial areas if we kept WP:NOT#NEWS and recentism in mind, in addition to how much information there is in a 24/7 news cycle and how much this has to be included in our encyclopedic articles. Facts can be updated when they come down the road, but opinions and analysis should be held off or very carefully discussed before addition. Too much of what I see at ANI/AE is because editors want to rush to add in non-facts (even if they are detailed analysis from well-established experts) that are critical of the topic, because it is human nature to focus on the negative, and editors challenging that. We don't need to be that up-to-date if it causes these behavioral conflicts. --Masem (t) 21:45, 25 June 2018 (UTC)
AP2? Headbomb {t · c · p · b} 22:11, 25 June 2018 (UTC)
Post-1932 American politics, most commonly present-day American politics. Refers to ArbCom remedies in that area. ―Mandruss  22:14, 25 June 2018 (UTC)
WP:ARBAP2 PackMecEng (talk) 22:17, 25 June 2018 (UTC)
I very much agree with Masem’s comment on this. We have a serious problem with not enforcing recentism and NOTNEWS. And it does tend to manifest in the form of giving UNDUE coverage to negative analysis and opinion regarding current events. Blueboar (talk) 22:44, 25 June 2018 (UTC)
I didn't intend for this to be a discussion about AP2 specifically, and I see similar problems in other areas. If it's more useful to narrow scope, so be it, but I suspect narrowing to AP2 will quickly devolve into a Wikipedia-bias discussion like the recently-closed one. ―Mandruss  23:12, 25 June 2018 (UTC)
Can you give us some examples from non-politics articles? Blueboar (talk) 00:58, 26 June 2018 (UTC)
I could, and I understand the benefit of illustration, but then we would tunnel-vision on those examples and miss the larger picture. The point is that we have one set of PAGs for everything; if the problem I have described exists at all, it exists for all topic areas. ―Mandruss  01:27, 26 June 2018 (UTC)
OK... Unfortunately, I can not comment on (or address) your concerns without a clearer understanding of what those concerns actually are... and to gain that clearer understanding, I would need some examples. So I guess I am done. Blueboar (talk) 01:50, 26 June 2018 (UTC)
That's fine. Ultimately, what I've said rings true with other editors based on their experience, or it doesn't. ―Mandruss  01:58, 26 June 2018 (UTC)
Keeping in mind my comment about 24/7 news cycles and their impact on lack of NOT#NEWS/recentism considerations, the next biggest area that this behavior manifests itself is any persons or groups involved in the current culture war over identity politics (which, unless they are a politician or directly connected to one, are not covered by AP2), which this often comes down to those called out as alt-right or far-right. This is not to say that we should whitewash away any valid criticism of these people, but their articles tend to be extremely slanted to paint them in as negative a light as possible, adding in any sourced opinion that make them seem worse, and attempts that I've seen to at least achieve a reasonable mid-point are refuted because "we have to follow UNDUE". I've argued elsewhere that UNDUE really needs aspects of recentism thrown in; UNDUE is great when looking at coverage of a topic 5 to 20 years after its left the spotlight to judge what the sources are, but fails in the immediate present in light of 24/7 news cycles. --Masem (t) 13:29, 26 June 2018 (UTC)
I think this highlights a problem with UNDUE. A plethora of low quality, though still reliable, sources can, and do force us to have highly biased and partisan articles. This could be mitigated if source quality could be weighted, but the way UNDUE is written now it's just a numbers game. --Kyohyi (talk) 13:49, 26 June 2018 (UTC)
Perhaps the next step then would be to propose modifications to WP:UNDUE with an RfC? I imagine we could get broad support for this if done properly. — AfroThundr (u · t · c) 15:06, 26 June 2018 (UTC)
It's not usually "low-quality" sources, though. It's mid-to-upper tier sources where these opinions/analysis are coming from (mid tier being things like the Daily Beast or Vox, at a mid-tier, up to things like the Washington Post and New York Times). And while writers for some of the upper tier works should be respected as experts or key people in certain fields, doesn't meant we need to include their immediate opinion if we've already layered on a lot of negative information already.
I've argued both on the lack of recentism concerns in UNDUE, as well as the fact that editors review UNDUE weighting of sources limiting themselves only those sources we have deemed RS, while we really should be looking at the broader pictures, and then decide what material from RSes may make sense to include. It is very short-sighted of editors to only look at a subset of sources and in the here-and-now to say that this is how a subject should be covered, when we really should been considering a much higher level, broader view (in both sourcing and time) to make sounder judgments of what to cover. That immediate action that some editors want to use is what fuels the endless debates and combative nature in AP2 and other topic areas. --Masem (t) 15:33, 26 June 2018 (UTC)
I'm not sure I agree with you on tiering. To me, upper tier is reserved for academic sources with good peer review. Mid-tier are academic style journals that pose new ideas, but not necessarily extensively peer reviewed. Also mid-tier are high quality publications that fall in NEWSORG. Finally, Editorial commentary, analysis, and opinion pieces in NEWSORG type publications are low tier or even should not be considered reliable at all. --Kyohyi (talk) 15:54, 26 June 2018 (UTC)
That's fair, but when I see debates on this articles, there's usually very little consideration of academic sources, and newspapers like NYTimes and others are held as high-tier sources for these. Given that good academic sourcing takes time to develop, we do have to consider how newspapers and other similar sources are used in the "short term" to develop these articles. --Masem (t) 16:05, 26 June 2018 (UTC)
I agree entirely with what you've posted here, Masem. The implications result in articles that are far too focused on history of the subjects post-2000s (where online news articles are more frequently found) and provide what is essentially trivia rather than a comprehensive overview of the topic. Killiondude (talk) 01:00, 28 June 2018 (UTC)
  • Our main problem is a new generation of editors that thinks everything is bias and use clickbait news spam as sources.....even seen people fight to keep one paragraph headline spam from Buzz feed. We need to update our policies about clickbait and news spam. No longer an academic environment and we need to make things more clear for the Next Generation.... like the difference between news reporting vs journalism....just look at the play by play daily news coverage at Scott Pruitt#Controversies .--Moxy (talk) 01:13, 28 June 2018 (UTC)
On the matter of Wikipedia becoming more democratic, or otherwise functioning as a de facto democracy, is that even a bad thing? More fundamentally, Mandruss, was there ever a worthwhile alternative? Regarding the concern that "consensus comes down to the POVs of the editors present", was that ever not the case? Sure, Wikipedia policy proclaims otherwise, but that is just another mute referral to scripture whose antiquites have become rather quaint. Given you consider this to be a "fundamentally broken system", what can replace it? Alternatively, why replace it? What objections do you have to the conditions you described?
I am genuinely interested in your thoughts on these matters and since nobody has asked those broader questions yet, I might as well. Hopefully, they are not too far beyond your intended scope. —Nøkkenbuer (talkcontribs) 22:51, 15 July 2018 (UTC)
@Nøkkenbuer: is that even a bad thing? Yes it is, unless Wikipedia content is to reflect the POV of the side who can mobilize the most editors. I think that's a bad idea.
I've been around for only 5 years, so I don't know whether things were ever any different. I do know the following two things. 1. If policy were less complex, watered down, and self-contradictory, it would tend to point everybody toward the same answer. It would be harder to misinterpret policy, and it would be harder to deliberately misuse it. The inherently biased editorial judgment would play a far smaller role. 2. Policy wasn't born that way, it took 17 years under the current model to get here. I postulate that that is an inevitable result of the way we have developed PAGs. Too many cooks in the kitchen, with no requirement for any particular cooking talent or experience. A different model would be needed, one in which policy is decided and written by a smaller group of individuals who have very extensive experience and policy knowledge, and who have an instinctive understanding of the problem and are prepared to say no, the policy doesn't really need that new wrinkle. The wide-open egalitarian self-governance model is a novel and interesting idea, but it's novel because civilization long ago figured out that it doesn't work. All societies need "wise men" (and wise women) in some form.
I reiterate what I said in the OP, "even if there is no viable solution". While there may be a theoretical solution, it is unlikely to be viable because the change would be too dramatic. It would require WMF to take action without asking for our permission, and that is unlikely in the extreme. I simply feel it's important to recognize and understand the problem for what it is—a problem with the system, not the people using it. ―Mandruss  04:53, 16 July 2018 (UTC)
Its worth noting that we do have a (very) weak form of the kind of central authority here that you are talking about, in ArbCom. Mostly ArbCom restrains itself to parsing disputes and establishing sanctions, but once in a blue moon it codifies a previously only presumed policy interpretation or even unilaterally extends the meaning of a policy. I'm not sure I wholly accept your basic premise that these ills are best described in terms of their being a consequence from the openness of our democratic model. That's a very wide-ranging suggestion and I'd have to choose the words of a response to that carefully, since I believe this project is unique in human endeavour and that the decentralization/plurality elements you are concerned about may not just be virtues, but indeed necessities--and yet, at the same time, I can hardl deny awareness of the difficulty in establishing primacy of different editorial considerations. I think that in 97% of content disputes, the consensus model works just fine in enabling groups of local editors hammer out a pragmatic solution. But that remaining 3% (mostly at BLPs) consume inordinate amounts of community effort and lead to reliability issues with some of our highest traffic articles.
Honestly, I think maybe community consensus is still the solution, but would involve a concerted and extended effort to form a kind of hierarchy of policy. To take just one of many possible examples, I'd love some "connective tissue" policy that makes it clear that BLP cannot trump WP:NPOV, which is, afterall, a pillar policy. Some editors wield it like a pure WP:BLUDGEON to keep anything remotely controversial out of articles about manifestly controversial figures, up to and including convicted perpetrators of mass atrocity crimes. BLP is meant to supplement/nuance NPOV, not override it, and it's damaging to our accuracy than some wave the those three letters around as if the term works like a magic talisman, making all unwanted claims disappear, no matter what the WP:WEIGHT of what the sources says. Recently we have developed the "explanatory supplement" tier of policy pages, but its clear that these are meant to be the weakest and least binding (with the exception of MoS guidelines) of all pages which nevertheless conform to WP:PROPOSAL and are thus "policy". Perhaps what we need instead are a super-ordinate level of policies just below the 5P which would allows us to somewhat more precisely and consistently coordinate the exact protocol/priority of policies when they clash. I'm not sure that this makes the policy scheme any less complicated, but if I am to be honest, that suggested priority of your recommendations may be at odds with the others; its probably impossible to make policy more concrete and less watered down while at the same time substantially reducing the actual volume of policy.
A massive effort to reorganize policy in such a way--and let's be honest, this would be one of the most onerous, complicated, difficult and drawn out community discussions ever--could theoretically proceed through our historically (mostly) successful community discussion processes. Or it could proceed with a nod to your "wise women" strategy. But that would be a sea change in itself. But I can't say the idea is entirely without merit. If we were to have a tier of editors who, like arbcom, had a position respected as capable of creating at least some binding analysis on policy, but were more numerous and did not need to be admins, because they would not be involved in conduct disputes (or even directly engaged in individual content disputes) and thus have no need for the tools, I wouldn't discount the possibility that, if approached carefully, it could improve consistency and reduce the territory for disputes. Speaking by analogy, if the larger editor community (or at least those who are interested in getting involved in policy areas) are Wikipedia's legislators, creating our "statutory" policies, your prospective group of wise men would function as a judiciary of sorts, ironing out the wrinkles through "common" policy. Of course, the metaphor is not perfect, since a policy is amenable to change (whether by the same or different parties that originated it) on the fly, which is arguably closer to common law than statutory law, but I'm sure you get the general thrust of the comparison. Again, I don't know I can commit to the idea that such a tiering-up of our user base is necessary or advisable, but that is roughly how I think it would have to work if the community ever moved in that direction. Snow let's rap 12:18, 20 July 2018 (UTC)

Bullet list of key misinterpretations of current sourcing policy

Some related points badly need to be reinforced, perhaps in multiple places (though in much more compact wording – I'm trying to explain the issues, not wordsmith them into rule rewrites):

Original draft:
  • What a writer/organization is an expert in actually matters. A lawyer is not a linguist, and punditry from one about English-language dialects is not reliably sourced just because it got published (especially if perpetuation of incorrect beliefs about dialectal matters is what drives his book sales). The central principles behind WP:MEDRS really apply to all topics. It doesn't matter if an author is a world-class expert on quantum mechanics, if what they're writing about is a professional digression into human psychology or the history of Cyprus. We're suicidally over-focused on publisher reputability [based mostly on pre-Internet reputation] instead of author reputability, in an era when publishers are buying each other, selling off divisions (without changing the names) to whoever has the most money, getting entirely bought out by international infotainment conglomerates, and also going more and more toward where the money is into nonsense populist works full out outlandish claims. Being from a major publisher is not proof that a source is reliable, it's just an indicating that it is more likely to be reliable than self-published blogging or e-books because at least one professional editor acted as a filter.
    • Journalism news reporting about or touching on technical topics cannot be used as a reliable source for technical claims. Journalism (in either sense) simplifies both concepts and wording in such topics. Nor is it reliable for statistics; journalists get statistics from somewhere else (the reliable sources for them) and then often misinterpret and misrepresent the data.
  • Blogs and advice/review/op-ed columns are primary sources and most of them are not high-quality primary sources. When they have not been written by notable individuals or those acting as official spokespersons of notable organizations, either with their own sources cited or at least a very clear indication where the information is ultimately coming from, they're just noise.
    • Even when editorial materials have been written by such ostensibly reputable parties, they are viewpoint not fact. Many columnists are wrong about many things, and the entire point of an op-ed (opinion editorial) is to press an opinion or view, just like a press release.
    • Even MEDRS has an error in it in this regard which I've been trying to fix for several years in the face of WP:STONEWALL behavior: "Ideal sources for biomedical information include ... position statements from national or international expert bodies". Position statements are press releases (though often citing their own sources for background facts, as do high-end op-eds), and the guideline even used to say "press releases" there. That term was removed to sweep under the rug the fact that MEDRS is saying, e.g., the British Medical Association or FDA organizational stance on e-cigarettes is "ideal" secondary sourcing when it is actually highly politicized primary material.
    • When usable at all (per WP:UNDUE), opinion material must be attributed inline and often should be directly quoted. We don't repeat what they say in Wikipedia's own voice. Reviews (in the book, film, etc. sense; I don't mean academic literature reviews) are by nature subjective; a work cannot be said by WP to be derivative, thrilling, etc. based on them; we can just quote/paraphrase reviewers in a due and balanced manner. (However, in-depth reviews can sometimes be secondary RS for particular facts, when they are based on research and are stating a simple objective claim, e.g. that so-and-so scene was filmed in Botswana. An FDA statement can likewise be a secondary source for factual not stance material when its own sources for the claim are clear.)
  • News reporting and journalism proper are not the same (though the profession of journalism covers both). But neither are guaranteed reliable secondary sources. Plenty of investigative journalism is primary, especially where it hides sources and comes to a conclusion reached by the writer as if that individual had the fact-finding and deductive powers of a huge agency. Some careful news reporting is secondary (based on interviewing multiple experts, agencies, etc., not on repeating what eyewitnesses said), when it's not regurgitation and conclusion-leaping; even then it has to be treated more and more like primary sourcing the closer it is to the events it's reporting on, and the further those events recede in time.
    • Learn this, know it, live it: Publication in a major newspaper, news site, academic journal, non-fiction TV show, etc. doesn't magically make it secondary. Secondary is a quality of the writing and the editorial process that led to publication, not of the publishing company or publication itself. Various publications that focus on secondary material also include lots of primary material. "It was in a newspaper so it must be secondary" is nonsense, a misunderstanding of the concept. (Do you think the advertisements in the newspaper are secondary sources? What about the "situation wanted" classifieds?)
    • Headlines and similar news blurbs ("kickers" and "deks" – see News style) are not sources; they're metadata and advertising: summaries and attention-getting teasers that not only are not the actual substance of the piece but often misrepresent it, either as to material facts or as to balance.
  • Not all tertiary sources are created equal. Reputable encyclopedias and dictionaries, both general and field-specific, are reasonable sources (at least temporarily) for basic and uncontroversial information, as long as we understand that more in-depth and current secondary sourcing trumps them. Coffee table books are not in the same class and verge on categorically unreliable. Being a compilation of previously-published claims doesn't automagically make a work reliable.
    • Dictionaries are generally not reliable except for what a term means in everyday casual speech and writing (which is usually not what we're writing about except in an article about a slang expression). They cannot be used to trump more in-depth sources. If we have an article about a term, the most notable and encyclopedic information is how the term is used in one or more professional fields; we should note the broadened everyday-banter definition in passing only, and focus otherwise entirely on what RS in the field(s) say about the term and the concept(s) it describes. A dictionary's definition that doesn't including that meaning cannot be used to suppress it. Similarly, if a dictionary (a highly tertiary source) gives a concise definition of how the term is used in a specific field, this cannot be used to constrain the scope or content relating to that field either; we should use the same sorts of secondary sources to provide encyclopedic coverage that the dictionary writers used [we hope] to arrive at their over-simplified topical dicdef (which may also be decades out of date); we should do a better job of it.
  • And that's just touching on some basic sourcing issues. Community understanding of WP:NOR seems to be an an all-time low. That policy needs to be rewritten with greatly enhanced clarity, both as to what various classes of sources are for what kind of info in what contexts, and as to what does and doesn't constitute original research at all. At this point, I now regret having opposed the merger plan of WP:NOR, WP:V, and WP:RS into a single attribution policy, back in the 2000s. While it would have produced a very long policy, at least it would've been in one place, and interpretational issues could actually be managed and resolved.
    • Every day I see farcical antics at both extremes of NOR misinterpretation. On one day, it's someone taking multiple sources about event X that suggest correlations with entity Y and perhaps outcome Z, none of them in agreement about exactly what happened, and turning this into a WP statement that Z is a result of Y doing X. The next day, it's someone denying that we're able (instructed, in fact) to use multiple sources that are in agreement to summarize the RS consensus in our own words, just because they didn't all use exactly the same phrasing.
    • This stuff is intensely disruptive, in a far worse way than chest-beating contests on talk pages, since it results in skewed edits in the articles, and thus direct misinformation or misleadingly cagey and incomplete information being sent to our readers.
  • WP:DE and related provisions (WP:NPA, WP:NOT#FORUM / WP:NOT#BATTLEGROUND, etc.) need to be enforced more swiftly and with less drama, especially when discretionary sanctions already apply to a topic.
    • The way to do this is to issue short-term topic bans and blocks with less hesitation, either on the part of DS-using admins or by the community at WP:ANI. If someone's being an asshat, remove them from the topic area and let the rest of us get back to work. If the sanctions are short-term, they will either a) have the desired effect and shift the editor's behavior, or b) demonstrate the editor has some kind of WP:CIR / WP:NOTHERE problem if they keep doing it again and again despite escalating sanctions each time.
    • Our current process typically involves a too-lengthy litigation and too-high standards of proof because the typical sanction imposed is too long and dramatic. Stop making it about a one-year sanction, and instead about a two-day sanction with the next one being a week, then a month, then three. Analogy: Our criminal justice system would be unworkable if every traffic ticket could lead to a life sentence. It would be hard to secure a conviction and no one would be willing to do their time but exhaust every avenue of appeal.

If a lot of this was resolved through better-written policies, then it wouldn't matter so much if screaming obsessives on either side showed up to rant about Trump. If they tried to use sources incorrectly we'd just revert them, and if they unreverted, someone else would revert them again because we'd all be on the same page about sourcing.  — SMcCandlish ¢ 😼  12:33, 29 June 2018 (UTC); collapsed in favor of new version, 04:47, 30 June 2018 (UTC)


User:SMcCandlish......make this into an essay !!! I would link the essay.--Moxy (talk) 00:42, 30 June 2018 (UTC)
Really comprehensive and well thought out wall of text. I agree with pretty much all of this. Now if only we could get some of those changes pushed into actual policy... — AfroThundr (u · t · c) 02:11, 30 June 2018 (UTC)
Working on essay-izing.  — SMcCandlish ¢ 😼  02:15, 30 June 2018 (UTC)
 Done, at WP:FMSP, with some revision and substantial reformatting, plus some additional points. Pings: Moxy, AfroThundr3007730.  — SMcCandlish ¢ 😼  04:47, 30 June 2018 (UTC)

Unblock people using VPNs from editing

I have a serious concern about blocking people from editing who are using VPNs – as, for example, this has totally silenced anyone in Turkey.

I know this is a complex issue and I'm not suggesting this decision was taken lightly – however surely one resolution would be to simply ‘grade’ edits and if they are done via a VPN they are flagged for more urgent attention.

For what it’s worth, I live in Australia and use a VPN constantly, as all ISPs are now legally allowed to track every site I visit, so I use one as a matter of privacy – and I’m sure I’m not alone.

I’m writing to ask advice about the best next step as I feel this is a very serious issue affecting freedom of speech and I’m not sure how to proceed.

At the very least I'm convinced a blanket ban on VPNs and TORs in principal sets a dangerous precedent and there must be some technical compromise that doesn't effectively silence those in places where Wikipedia is blocked.

I’m on the Editorial Board for the WikiJournal Science and keen to discuss this further - forgive me if this was not the correct place/tone to post here - it's my first time getting involved in this forum.

Jack Nunn 05:23, 26 June 2018 (UTC) — Preceding unsigned comment added by Jacknunn (talkcontribs)

Per Wikipedia:Blocking policy#Common blocks imposed, it says this:

A hard IP address block (account creation blocked, prevent logged-in users from editing from this IP address) disables all editing and account creation from behind the blocked the IP address, whether or not from logged in users (except accounts that are IP-block exempt - these users can edit while behind the blocked IP, but cannot create accounts). This is typically used when the level of vandalism or disruption via creation of "throwaway" accounts is such that all editing from the IP address is to be prevented except after individual checking of requests. Open proxies are hard-blocked on detection, and Tor IP addresses are automatically blocked by the Tor block extension.

VPNs are considered to be like open proxies. — MRD2014 Talk 12:52, 26 June 2018 (UTC)
Hi Jacknunn. How do you propose we stop people from using VPNs/proxies to easily evade blocks? --NeilN talk to me 12:53, 26 June 2018 (UTC)

@Jacknunn: There's no blanket ban on VPN that would be impossible to know all the IPs there are 100s if not 1000s of VPN services who are constantly changing IPs. Try others that are less well known, smaller, more expensive etc.. get away from the crowd greater chance the IPs will be clean. -- GreenC 13:39, 26 June 2018 (UTC)

I have to second GreenC's point: I edited via VPN all the time when I was in China while logged in to this IP block exempt account. Really the only thing that needs to be done is provide a process for folks in Turkey (or countries with similar problems with editing) to apply for an IP block exempt account from the get-go. We have other mechanisms to block such accounts. This doesn't help IP editors, but registering puts one more step between an unsafe editor and a malicious government anyway. Ian.thomson (talk) 15:29, 26 June 2018 (UTC)
In my experience, applying for an IP block exemption is not easy, nor are you very likely to meet with success, despite legitimate uses for one. I don't think a majority of IP users, or newly registered users will have much of a chance with that process, unless we change policy to cover those cases. I still think a soft block would be a better option, since that increases accountability and makes for easier management of the incoming edits from newly registered users. — AfroThundr (u · t · c) 15:35, 26 June 2018 (UTC)
(edit conflict) Many users will not look for lesser-used services, or even have the technical competence to know how to, past the basic guides one finds with a simple search. This is a legitimate issue that affects potential editors in countries with more restricted policies than what a majority of users here currently enjoy. Wikipedia strives to be the "encyclopedia that anyone can edit" but imposing restrictions that can cut off an entire region or demographic due to their (legitimate) use of a VPN or proxy is akin to throwing the baby out with the bath water. I know we need to cut down the vandalism, but a lot of our automated (and semi-automated) anti-vandalism tools have come a long way since this blocking policy was created. As mentioned above, the edits could even be flagged automatically for review, like we currently do for other potentially damaging edits. Are we sure that the continued blocking of all of these anonymizing solutions is really necessary? I would very much like to see statistics on number of vandalism edits previously encountered from anonymized users (and any other related data that may be relevant), so that we can properly assess the potential impact of this issue.
I know we need to cut down the vandalism, but a lot of our automated (and semi-automated) anti-vandalism tools have come a long way since this blocking policy was created. As mentioned above, the edits could even be flagged automatically for review, like we currently do for other potentially damaging edits. Are we sure that the continued blocking of all of these anonymizing solutions is really necessary? I would very much like to see statistics on number of vandalism edits previously encountered from anonymized users (and any other related data that may be relevant), so that we can properly assess the potential impact of this issue. — AfroThundr (u · t · c) 15:33, 26 June 2018 (UTC)
Of course it is necessary to slow down long-term abusers and general trolls. The automated anti-vandal tools are great but they don't work for long-term abusers, trolls and socks. Allowing anyone to edit is one side of the balance. The other side is providing support for those who do build the encyclopedia by not allowing waves of disruption. Johnuniq (talk) 23:08, 26 June 2018 (UTC)
I agree. The primary reasons for VPN blocks is long term abuse, not casual vandalism. — BillHPike (talk, contribs) 03:39, 1 July 2018 (UTC)

Evidence-based policy?

I just saw this tweet from WikiResearch which I think is relevant and challenges some of the assumptions underlying the VPN policy. Thoughts?

'"most vandalisms [on Wikipedia] were reverted within five minutes" on average' [web.archive.org]

Jack Nunn 06:36, 10 July 2018 (UTC)

Experienced editors are not concerned about poop vandals or others who make nonsense edits because they are easily handled. The corrosive force that drives away good editors is the wave of POV pushers who arrive with brand new accounts to repeat the same arguments that were settled last week and the week before. Open proxies provide haven for such troublemakers. Please ask at WP:HELPDESK about fixing your signature so it complies with WP:SIG. Johnuniq (talk) 11:02, 10 July 2018 (UTC)

VPN blocking discussion summary

Thank you everyone for your input on this so far - it's an important issue and I appreciate the enlightened discussion. For me I would summarise the issue as a matter of one of balance. If the balance at any point tips and means any one person is silenced from sharing, say, a human rights abuse or environmental catastrophe - then the balance has failed. At the moment, I feel the balance is failing. As mentioned, I don't have the expertise to suggest anything more than vague sketches of ideas. As others have suggested, some kind of flagging/rating/grading system could exist. Maybe a subject for a hackathon - which could redress the balance in a week. It will always be a game of cat and mouse but at the moment it feels like we've let the cat give up. Or are we the mouse? ha ha. Anyway - I had this helpful response from a Wikipedia email address (edited to remove identifying information as I didn't ask if I could share it):

'"We appreciate your email, and I have to say we are very sympathetic to your concerns XXXX we strongly advocate for anonymity and security measures for users wherever possible.

'Our policy against open proxies exists out of sheer necessity. It's unfortunate and we regret it, but the sheer quantity of abuse we receive through these sources is too large to handle. It's not that 'grading' Italic textwouldn't work theoretically, it's that we can barely keep vandalism and long-term abuse off our platform as it is, and we would not be able to do so without the blocks that are currently in-place.

'We do not have a blanket policy against closed proxies, and we evaluate these on a case-by-case basis.

'Experienced editors caught behind a block are encouraged to apply for an IP block exemption, and newer editors are encouraged to spend a few weeks polishing a proposed article to include as part of their application. Italic 'My understanding is we are reasonable with granting these, provided we can establish a level of trust."''

This was a helpful response but I have to agree with other comments above (AfroThundr3007730) - 99% of casual editors (like me) would have no idea how to get around a block, and frankly, shouldn't need to. The whole point of Wikipedia is it's 'quick' and easy to edit - say, in an emergency. I live in Australia and have to turn my VPN off for every edit - that's annoying enough - but it raises enormous alarm bells and I think something needs to change.

Sidetopic - but even this method of having a discussion about something this important feels like something built in the 1980s! Look to Loomio for discussion/decision platforms.

Thank you again for this discussion. Jack Nunn 12:37, 27 June 2018 (UTC) — Preceding unsigned comment added by Jacknunn (talkcontribs)

  • Sorry, you don’t qualify for local IPBE on the English Wikipedia. Any discussions about loosening IPBE all have assumed the loosening would apply to users with significantly more experience on-wiki than you have. Editors who have less than 500 edits are extremely unlikely to be granted it without significant experience on other Wikimedia projects. TonyBallioni (talk) 03:50, 1 July 2018 (UTC)
  • If the balance at any point tips and means any one person is silenced from sharing, say, a human rights abuse or environmental catastrophe - then the balance has failed. Wikipedia is WP:NOTNEWS and should not contain original reporting. If the abuses or catastrophes are not published in reliable sources, they shouldn't be on Wikipedia. If they are in reliable sources, anyone anywhere in the world can add it to the appropriate article. --Ahecht (TALK
    PAGE
    ) 05:23, 1 July 2018 (UTC)

Should WP:TWL be allowed to acknowledge the services they have partnership with in our articles?

This is a follow up to User_talk:CitationCleanerBot#Via. According to Nikkimaria (talk · contribs) and Vanamonde93 (talk · contribs), they put citations like

by the reasoning "It wasn't used to advertise the service; it was used to acknowledge the access provided by Project Muse to certain Wikipedia users." This is apparently to comply with partnership requirements where they have gained personal access to pay-for-access databases (in this case Project MUSE) through The Wikipedia Library, where in return they need to mention in our articles that they had made use of Project MUSE.

Should the practice be allowed to continue? Or under which condition should |via= be used? Headbomb {t · c · p · b} 15:32, 28 June 2018 (UTC)

TWL discussion

Disallow: This is something that is a textbook WP:SPAM/WP:PROMO situation. Citations exist to verify our material, not advertise pay-for-access academic services. While we have links that often point to paywalled ressources, such as DOIs in our article, those are vendor-neutral identifiers are there to help identify the citation. WP:SAYWHERE is clear about this:

The advice to "say where you read it" does not mean that you have to give credit to any search engines, websites, libraries, library catalogs, archives, subscription services, bibliographies, or other sources that led you to Smith's book. If you have read a book or article yourself, that's all you have to cite. You do not have to specify how you obtained and read it. [emphasis mine]

The following

  • Esmonde, Margaret P. (1981). "The Good Witch of the West". Children's Literature. 9 (1): 185–190. doi:10.1353/chl.0.0112. 

fully complies with WP:SAYWHERE, and links to Project MUSE resources in a way that does not unduly promote a commercial service. Further, using the URL to further link to the paywalled Project MUSE is fully redundant with the DOI, and discourages editors from finding non-paywalled versions of the paper.

Things like

are ridiculous.

This is a horrendous practice, and one that needs to end now. If Project MUSE wants attribution in some way, that can be done in edit summaries, or via the talk page. Not in the main bodies of our articles. Headbomb {t · c · p · b} 15:32, 28 June 2018 (UTC)

  • Comment to be clear, I have been formatting citations in that manner because I understand that that is what TWL requires. I see the concern about being promotional, but as we routinely link to sites that are inherently promotional (official websites, twitter accounts, paywall protected newspapers, newspapers that don't have paywalls because the use ad revenue which eventually comes from consumers, etc) I'm not overly worked up about this. All I would like is to continue to be able to use these resources to provide more reliable and detailed information, which is what this should be about. If the community compels TWL to remove this requirement, I'm not remotely bothered. Vanamonde (talk) 15:45, 28 June 2018 (UTC)
  • TWL Comment Just to clarify, using the |via= parameter is not a requirement of citing resources obtained through The Wikipedia Library, and the citations found on the old signup pages (e.g. Wikipedia:Project MUSE) are only a suggestion for a fully formatted citation. I can absolutely see how the text there makes it seem like more of a requirement, however, and I’ll rewrite that section to make it clearer, in addition to the note that is already present.
As far as I’m aware, the parameter was initially added to these citation examples simply because it was present in the citation templates and has uses in cases where the URL doesn’t point to the location the source was found. It’s also useful because it saves you mousing over or clicking a URL to know where the citation is from. Ultimately though, the discussion about whether the parameter is useful is unrelated to TWL.
We’re not concerned whether this parameter is kept in the suggested citation style or not, and are happy to change it based on the outcome of this discussion. Given that the parameter isn’t a requirement of using TWL, however, I’d suggest reframing the discussion around whether use of the ‘via’ parameter is desired in any context. Let me know if you have any questions or suggestions. Samwalton9 (WMF) (talk) 16:56, 28 June 2018 (UTC)
Well, I'm very glad to hear this is not a requirement. However, Wikipedia:The_Wikipedia_Library/Publishers specifically mentions, in the "Exposure and promotion", "Publisher credit using the |via= parameter of our citation templates". Maybe this is the source of confusion? Or possibly pages like Wikipedia:Credo/Citations and other similar pages? If this isn't a requirement, those pages should be updated to de-promotionalize those services. Nikkimaria (talk · contribs) and Vanamonde93 (talk · contribs), what led you to believe that using |via= to 'credit' Project MUSE was required/encouraged? Headbomb {t · c · p · b} 19:15, 28 June 2018 (UTC)
@Headbomb and Xover: The instructions in question are the ones found at Wikipedia:Project MUSE, which say, among other things, that editors should "provide original citation information in addition to linking to Project MUSE resources" and "Cite resources in line with the citation examples provided below or with the examples provided by Project MUSE" (the example in question uses the |via= parameter. The version of the instructions that existed when I received access was even more definitive about this. Vanamonde (talk) 03:44, 29 June 2018 (UTC)
  • Comment @Headbomb: If you're going to be opening a policy RFC, please at least try to frame it neutrally. The above is closer to a diatribe and I would really rather strongly implore you to retract it and try again once your apparent indignation has had time to recede a bit.
    Second, The TWL partnerships do not "require" much of anything. The TWL effort suggests that per WP:SAYWHEREYOUGOTIT you use |via= etc. in a specific way for sources from that particular archive or service when appropriate. So when you access a journal article through a third party service—rather than on paper in your local library or directly from the publisher—you specify that you're citing the copy provided there rather than an original. The TWL example citations have been formed based on SAYWHEREYOUGOTIT and are intended to be used in accordance with SAYWHEREYOUGOTIT, including their mostly being optional and when it is not appropriate to include such |via= parameters.
    By all means lets discuss the finer points of how we should apply SAYWHEREYOUGOTIT to the TWL resources, but please don't let your knee-jerk reaction based on limited (and obviously skewed) information turn that discussion into a pointless drama fest that will achieve nothing but tarnish the coordinators and other volunteers working very hard to improve the encyclopedia. Please. --Xover (talk) 17:01, 28 June 2018 (UTC)
The RFC is framed neutrality. My !vote expresses my opinion. Nothing wrong with that. You're welcomed to make a support case if you have one. Headbomb {t · c · p · b} 18:10, 28 June 2018 (UTC)
Yeah, see, the problem is you've set up a strawman (just about zero of the assertions and underlying assumptions in the current RFC framing are true) and now you're asking me to argue against it.
I have no objection what so ever to discussing how TWL should recommend that citations to sources that happened to be accessed through a TWL partner's donated access be done. Nor to discussing how SAYWHEREYOUGOTIT applies to cases like these (of which some, but not all, sources made available through donated partner services are examples, but in no way unique in that regard). Nor to discussing the purpose in general, or finer points of application of, the |via= parameter. I might even have some opinions on some of these issues (then again, probably not enough to argue about them). You want to do any of those things, have at it. Heck, if for some reason you need my help with any of those, I'd be happy to step up.
But we can't have any of those discussions, at least not productively, in an RFC framed in an inflamatory way (That is, "in a way that is likely to have the effect of inflaming", not "in a way intended to inflame") and based on incorrect information. So, again, please—please!—reconsider: either by reframing the current RFC, or by withdrawing and trying again when you're less outraged by what is incorrect information! --Xover (talk) 19:22, 28 June 2018 (UTC)
  • Allow when it adds something. E.g., we routinely use |via=Google Books for books that Google is providing snippet views of and other "digitally digested" content, because we are not looking at the literal book itself and cannot, e.g., be 100% that the book's original text, pagination, etc. were preserved correctly by Google's OCR and other munging. We don't need to use it for old-book scans that Google hosts, because they are exact photographic facsimilies (often including the library cards :-). It's useful to say that you got a journal article via a particular journals database, because you are not literally reading the actual journal, but a PDF prepared from submitted content not a scan, or an HTML text-and-images relayout, or something like that (sometimes it's even a pre-print copy which may be pre-peer-review, too – same goes for arXiv), not a photographic facsimile.  — SMcCandlish ¢ 😼  19:40, 28 June 2018 (UTC)
Yeah that's fine, I'm not arguing for a blanket ban on |via=. I'm only talking about cases where there's no URL given, when things are redundant with links that are already provided by identifiers, or that the reproduction hosted by Database X is a faithful reproduction. Headbomb {t · c · p · b} 19:49, 28 June 2018 (UTC)
  • Edit the template. The "via" parameter is plainly dangerous, because it advertises random third parties. I don't get the argument that it isn't as bad if you're talking about Google Books, either. But, we also have a duty to the readers to help them access the material. So we should change the template as follows:
  • All "via" links should display the same text -- "access notes". This avoids any appearance of spam, and can be a neat, regular format. The "access notes" would be a link, of course, and could be set off with a cute/recognizable box using inline CSS: access notes or some such. And the links, naturally, go to different places depending on the via=parameter.
  • All "via" links link to pages in Wikipedia space, e.g. WP:Access help/Project MUSE. The template can even be designed for reverse compatibility to process the links it receives to add the WP:Access help/ part so the existing via link texts go new places, but new links should name a WP: space page directly (and thus not be altered). The reason for this is that Wikipedia articles are "WP:NOT#HOWTO", whereas what access help should be is absolutely, completely, one hundred percent HOWTO. That's an unacceptable philosophical incompatibility. We want to tell readers any and all options to get access when via= gives a particular mechanism, but are interested there in nothing else about it.
  • Our WP pages should then each explain their particular "via" mechanisms for the readers, including whether they can become editors and apply for access, or pay for it, or try to get lucky with an inconsistent server (I'm thinking Google Books) using any legally acceptable trick like using a VPN or TOR. (Actually I don't know if this works ... obviously the composition of these pages will be the topic of some specialized expertise and debate)
Wnt (talk) 21:12, 28 June 2018 (UTC)
That forgets one thing: WP:TWL is an editor resource, not a reader resource. The way to help readers access things it to find free-to-read resources. Headbomb {t · c · p · b} 22:17, 28 June 2018 (UTC)
@Headbomb: No, I didn't forget that. If we have a Wikipedia-space page on MUSE we can tell readers they don't easily get access via this route. But we can also point out that they can ask editors about it. And of course, any Wikipedia reader can become an editor -- it's never to be ruled out -- so TWL is at least nominally an access mechanism. I am actually not sure how TWL plays with WP:WRE -- are there TWL editors listed under the latter, or can you request copies of specific resources via that means? The distinction between "interlibrary loan" and "piracy" is utterly mythical and of paramount legal importance. Wnt (talk) 23:07, 29 June 2018 (UTC)
  • TWL Followup Just a note that I've reworded the old signup page template to make it clearer that there's no required citation style or parameter usage, and also reworded or removed explicit mentions of the via parameter elsewhere. Samwalton9 (WMF) (talk) 09:44, 29 June 2018 (UTC)
  • Allow - I liken it to a CC-BY-SA 4.0 license—it serves to benefit the project. Atsme📞📧 16:29, 2 July 2018 (UTC)
  • I think that the "via" information is most useful when you consider it as a 'warning' about the URL, similar to a PDF icon after an external link. To that end, I think it would be better if the citation looked more like this: "The Good Witch of the West (via Project MUSE)" (etc.). WhatamIdoing (talk) 19:00, 6 July 2018 (UTC)
  • Ditto WhatamIdoing. It's just more context for the citation. I have a weak disinclination to support reformatting the link to say "access notes" since requiring a separate click defeats the point of having that handy context (they can just click the link itself and see where it takes them, after all). If it were a requirement that it be formatted a particular way, that would be one thing, but it sounds like it's not, so it's just using the template as it's intended. I'll add that I also don't have a problem with TWL encouraging people to use it. This seems along the lines of "remember to include the title of the publication when you cite it". If reminding people to use the procedures/templates they should/could be using anyway indirectly helps more people get access, that seems like a win. It's when it becomes mandatory that it's a little more uncomfortable. — Rhododendrites talk \\ 05:36, 15 July 2018 (UTC)
  • Disallow all paywalled links and |via= notices, except when they add something for the reader (e.g. Google Books preview) AND when that wouldn't be already linked through DOI/PMID etc. We're not an affiliate site. There's already an annoying amount of paywalled links (e.g. Highbeam) to newspaper articles that are readily available for free from the newspaper website or archive.org. BTW I was less than impressed the Project MUSE's crappy primary-sourced, unreadable Wikipedia page. What do they offer that we should bend the rules for? I'd rather do this for arXiv, the awareness of which the readers at large could actually benefit from. DaßWölf 00:35, 16 July 2018 (UTC)

Gender-neutral language

Although I support GNL, it looks (to a greater extent than ever before) that many Wikipedians prefer generic male language should be kept. Look at the GNL section of the WP:MOS. It appears that there are now more Wikipedians than ever (according to a current discussion in the middle of the talk page) who appear to support a rule that's closer to the following:

Either gender-neutral language or gender-specific language is acceptable, the preferred term depends on what is most commonly used in practice; please do not change from the version used in the first nonstub version of an article without consensus.

Any thoughts on the best words are?? The "Use gender-neutral language when..." rule appears to be something most Wikipedians disagree with now. Georgia guy (talk) 14:57, 1 July 2018 (UTC)

Georgia guy: Where is that quote from? It's not from MOS:GNL, the relevant guideline. — MShabazz Talk/Stalk 21:06, 1 July 2018 (UTC)
It's from the WP:MOS. Please scroll that page to the GNL section. Georgia guy (talk) 21:10, 1 July 2018 (UTC)
No it isn't. — MShabazz Talk/Stalk 21:18, 1 July 2018 (UTC)

For the record, the MOS says:

Use gender-neutral language where this can be done with clarity and precision. For example, avoid the generic he. This does not apply to direct quotations or the titles of works (The Ascent of Man), which should not be altered, or to wording about one-gender contexts, such as an all-female school (When any student breaks that rule, she loses privileges).
It would be most useful to clarify what we mean by "gender-neutral". In today's dispute, an editor mass-changed the word "mankind" in about 170 articles because one of its two definitions is not gender-neutral. (Actually there was no indication they even consulted a dictionary; apparently they simply saw the word "man" and felt that automatically made the word non-GNL.) In such cases, the existence of one non-GNL sense should not preclude Wikipedia's use of the other(s). If a word is ambiguous in the context, it should be changed, but that's an issue of clear language that has nothing to do with GNL. ―Mandruss  16:22, 1 July 2018 (UTC)
Reminds me of the person running around a few months ago with things like Talk:Misuse of statistics#Requested move 20 April 2018 and Wikipedia:Village pump (proposals)/Archive 114#Rename "View history". Anomie 21:42, 1 July 2018 (UTC)
  • As an editor, I actually see no reason whatsoever to use "mankind" (except if it is in a quote), see, [1] [2] but it may be different for different words. -- Alanscottwalker (talk) 16:35, 1 July 2018 (UTC)
  • While I do think we should encourage editors to use gender neutral language (where appropriate)... I don’t want a situation where editors are going around disrupting the project to “enforce” it. Encourage, don’t mandate. Blueboar (talk) 17:28, 1 July 2018 (UTC)
  • I strongly agree with Blueboar. I try to use gender-neutral language, and I think our policies and guidelines should encourage it, but I don't think it's a good idea to seek instances of non-neutral language to fix. To me, it reeks a little too much of WP:RGW. — MShabazz Talk/Stalk 18:15, 1 July 2018 (UTC)
  • The problem is the phrase "what is most commonly used in practice" - how is that to be determined? Google hits can be a start but they, all too often, are affected by variables that skew the "in practice" idea. I have seen plenty of discussions where each side was convinced that their version was the commonly used one. It should also be noted that many of the "gender specific v gender neutral" terms are as in flux at this time as they ever have been. Thus we have the question of when is the tipping point reached where the 'pedia should shift from one to the other. As I read the proposed phrasing I don't see it solving anything in the current situation. MarnetteD|Talk 18:26, 1 July 2018 (UTC)
    To see what's going on, please go to the Wikipedia talk:Manual of style, specifically the section that's currently #8 (its number may change as earlier sections are archived.) Georgia guy (talk) 18:33, 1 July 2018 (UTC)
    I've seen that discussion. It is about one specific term. This proposal is about gender neutral language in general and addresses none of the concerns I've raised. MarnetteD|Talk 18:38, 1 July 2018 (UTC)
    And I want to know people's opinions on when GNL should not apply besides trivial situations like direct quotations. Georgia guy (talk) 18:40, 1 July 2018 (UTC)
    I suggest: history articles when all the people under consideration were known to be men. Rjensen (talk) 19:24, 1 July 2018 (UTC)
    Although GNL is a goal, as has been said we are not here WP:RGW and should still follow common usage rather than use wikipedia as a vehicle for change. This doesnt mean we should not have guidance to educate, but the world moves slowly and it is not our job to force the use of GNL. MilborneOne (talk) 19:25, 1 July 2018 (UTC)
    Force? For goodness sake? No one forced Oxford to refer to 'mankind' not neutral in the cite I included above[3]. Alanscottwalker (talk) 21:43, 1 July 2018 (UTC)
  • We should use inclusive language in our articles, except for quotes and official titles, as appropriate. --Enos733 (talk) 19:47, 1 July 2018 (UTC)
  • Of course we should use gender-neutral language. I don't see anyone arguing against that. The problem is that some people think that "mankind" isn't gender neutral, when it's been clearly defined as such. Natureium (talk) 19:56, 1 July 2018 (UTC)
    Some people? No, unless what you mean is RS are people. Here's Oxford: [4]. -- Alanscottwalker (talk) 21:43, 1 July 2018 (UTC)
    What is your point? You have cited one source yes, but it doesn't weigh any more than another dictionary or related WP:RS would. - Knowledgekid87 (talk) 21:48, 1 July 2018 (UTC)
    The source from Merriam-Webster that makes no mention of a neutral alternative. [5]. - Knowledgekid87 (talk) 21:53, 1 July 2018 (UTC)
    What is your point? It's already been established that Webster notes the gender issue in its 'mankind', entry. Webster noted gender in it's 'mankind' entry because it exists, unlike in other words it notes. Alanscottwalker (talk) 22:17, 1 July 2018 (UTC)
    In the case of "mankind", all of the reputable style guides recommend against its use for reasons of gender, and have moved to this position over a 30 year period. I don't know any native speakers who use "mankind" without making a POINT by doing so; certainly none under the age of 50. This is a case where the language has already moved on. Newimpartial (talk) 13:49, 2 July 2018 (UTC)
  • As the whole "mankind" argument demonstrates, gender neutral language is already more common, at least in the style of contemporary written English that Wikipedia is composed in. Editors might benefit from using a more nuanced approach rather than changing article en-masse, but contra MilborneOne preserving gendered language seems Wikipedia is attempting to "stand athwart of history yelling 'stop'", which isn't the mission. Nblund talk 20:50, 1 July 2018 (UTC)
    • Just to point out that I dont have a problem with NGL when appropriate but rather see education rather then forcing the issue like the mass change of mankind against common and seemingly correct usage. MilborneOne (talk) 21:12, 1 July 2018 (UTC)
  • I am in favor of just keeping this to LGBT related articles. If the article is about a guy who self identifies as a guy then we use him/his/he, this should be done per WP:RGW. - Knowledgekid87 (talk) 21:44, 1 July 2018 (UTC)
  • A question: outside of use in direct quotes, how often is a WPian going to use "mankind/humankind" , and in a context where it can't be replaced with "humanity" or the like? I easily see issues whether we chose mankind or humankind, but switching off to a synonymous word that has no such gender implications at all seems better... --Masem (t) 15:11, 2 July 2018 (UTC)
  • Well, that's weird. So Neil Armstrong has now been retroactively given credit for claiming the Moon for men only? Who the hell interprets 'mankind' as excluding women? sigh. It's this kind of crap that got Trump elected... Wnt (talk) 15:24, 3 July 2018 (UTC)
  • What is missing from our MOS guidance is a nod to WP:RGW... it is fine (and even beneficial) to change individual instances of gender specific language (to gender neutral language)... but making indescriminant mass changes is considered disruptive. Go slowly, and take it one article at a time. Don’t make a crusade of it. Blueboar (talk) 16:31, 3 July 2018 (UTC)
    If we add something about that, it should also cite Wikipedia:Arbitration/Requests/Case/Magioladitis 2#High-speed_editing, which is a generally enforceable ArbCom sanction, as someone pointed out recently at ANI, about the "U.S." → "US" AWB spree: "Where editors have made a number of similar edits in a short time space and other editors have raised concerns about those edits, the editor is to stop making the edits and engage in discussion.". I would support doing so, but it should be in a footnote for the most part, off the MoS lead's bits about editwarring over style.  — SMcCandlish ¢ 😼  21:22, 3 July 2018 (UTC)
  • We already have support for gender-neutral languag at MOS:GNL. The current dispute is about the linguistically ignorant idea that "mankind" means "dudes only", a view not supported by any dictionary or by linguistic history, or by actual usage in reliable sources or in our own pages. In rare instances it has been used that way when paired with "womankind" in the same construction, but this is a poetic artifice and isn't going to be found in encyclopedic prose. A handful of usage dictionaries concede that some people think of "mankind" as gender non-neutral (unaware that the word dates with its generic meaning to before "man" by itself picked up a meaning [sometimes] of "male adult human", though loss of a prefix we now see only in "werewolf" and "weregild").

    The idea that "mankind" is sexist is a legitimate reader-perception issue, but it's a minor, niche one.[citation needed] (Most of our readers seem educated and experienced enough with the language to not go on a misguided language-policing spree about it, as do most of our editors.) Ergo, we should not have a rule against the word, but it's marginally preferable to change it in many cases to "humanity", "people", "peoples", "the world population", "the human species", "modern humans", or some other construction that fits the social, historical, cultural, statistical, human-geographical, evolutionary, or physical-anthropology context in question. We do not need an AWB rampage to politically-correct every instance of "mankind", especially since the word is emphatically not wrong, just not everyone's favorite. Nor do we need an AWB blitz to revert to "mankind"; the entire basis of MOS:RETAIN is if that any given usage is permissible under MoS, leave it alone. Mass revert-warring is just as WP:POINTy (and just as much a grounds for sanction) as doing a mass undiscussed change. They're both futzing with thousands of pages for reasons not sanctions by any policy or guideline.
     — SMcCandlish ¢ 😼  21:10, 3 July 2018 (UTC)

Just a brief correction to the above: it is not "a handful of usage dictionaries" that mitigate against "mankind", it is basically all authorities over the last 30 years that have moved in this direction. When all recent, reliable sources agree about something, I wouldn't call that finding "niche". Still, no rampaging is mandated.
I would also like to point out the fallacy that has frequently been repeated in these discussions, that because "man" and "mankind" have a gender-neutral etymology that therefore they don't have ( or shouldn't be considered to have) gendered connotations. Bollocks. The inclusion or exclusion of women from "mankind" was part of the broader question of gender organization of early modern society, and I dare say that "mankind" was a good deal more ambiguous and possibly gendered in its meaning in 1800 than in 1500. Which then makes sense of the proliferation of more clearly neutral alternatives, which began not in the feminist cultural revolution of the 1960s and 70s but rather back in the 17th century. Newimpartial (talk) 11:09, 4 July 2018 (UTC)
  • Same thing I said at the "mankind" discussion: mankind is indeed gender-neutral, but dated—its use has declined steadily since the 18th century and has been significantly less common than "humanity" since the 1970s. Its removal should not be mandated, but neither should it be granted WP:RETAIN-like protection, as replacing it with "humanity" or another clearly neutral equivalent causes no concrete problems (only ideological ones). Curly "JFC" Turkey 🍁 ¡gobble! 23:07, 3 July 2018 (UTC)
  • I agree with the Gobbler. ;-) As I wrote in the MOS discussion, there is no reason for Wikipedia to move in the opposite direction of every major style guide; news organization guides; and our own manual of style. ... I take that back. There is one reason: To make a political statement.   - Mark D Worthen PsyD (talk) 05:16, 4 July 2018 (UTC)
I propose that the "Manual of Style" be renamed as "Perdaughterual of Style." Jack N. Stock (talk) 05:29, 4 July 2018 (UTC)
Thankfully "troll" is gender neutral. EvergreenFir (talk) 06:27, 4 July 2018 (UTC)

Proposed MoS footnote to discourage mass changes

FYI: Pointer to relevant discussion elsewhere.

Please see WT:Manual of Style#Proposed footnote to discourage mass changes
 — SMcCandlish ¢ 😼  21:51, 3 July 2018 (UTC)

Article that explains the etymology of mankind and its controversy

The Gizmodo article "Think twice before using 'mankind' to mean 'all humanity,' say scholars" explains very well where the word came from and why its use is controversial. (Thanks to user:Clean Copy for the link.) Thinker78 (talk) 04:07, 4 July 2018 (UTC)

That article is rather remarkable. They say that (a) "mankind" is from Old English "mann" that could refer to either sex and could be specified to "waeponmann" or "wifmann" if one sex is desired, (b) the combination generally could refer to both sexes, (c) for the past two centuries it has pretty much always been taken to refer to both sexes, hence (d) one should "think twice" before using it and prefer "humanity". Seldom have I seen the conclusion so not follow from the premise. Wnt (talk) 09:31, 4 July 2018 (UTC)
So, you agree, 'man is man' and 'woman is a kind of man'? Or would you prefer, 'women is a subset of man'? - Alanscottwalker (talk) 10:46, 4 July 2018 (UTC)
Basically, there are 50% chances "mankind" had chauvinistic origins, so although in the general definition "mankind" can be considered gender-neutral, the origins of the world might not have been gender-neutral. To avoid the centuries-old possible use of a man-centric worldview, as is very well possible, and more important, to avoid the looks of gender-bias (MANkind), it is preferred the use of other words to denote all humans, like humanity, which sounds less gender-oriented, or people, who doesn't have the controversial etymological "man" in it. In Spanish there is a similar issue because often it is said "los hombres" (men) or "el hombre" (man) to refer to all humans, so it brings to question the claim that the use of "man" originated purely as designation of more than one gender, as Spanish society has been historically very chauvinistic. Thinker78 (talk) 18:32, 4 July 2018 (UTC)
Yah, but that's huMANity, not huWOMANity, so obviously....... ;) Wnt (talk) 00:44, 5 July 2018 (UTC)
What a lame, reactionary attempt at humour. 'Human' ≠ 'man', anymore than 'woman' just because all of 'man' happens to be in 'human' and only part of 'woman' is. The use of "humanity" does not carry with it the same perceived gender implications as "mankind"--not for most speakers anyway--and your little quip, based in awkward, half-thought-out folk etymology / morphemics as a justification for "analytical/rational" resistance to the emerging norm comes off as, frankly, chauvinistically antagonistic to the larger trend towards gender neutral language. Snow let's rap 23:02, 11 July 2018 (UTC)
Lame? The derogatory term comparing to one with physical impairments? Killiondude (talk) 00:44, 12 July 2018 (UTC)
I've never known the word to be considered derogatory. It's either a clinical term for actual lameness, or it's an idiomatic usage implying an unimpressive effort. I would not be surprised to learn that some communities have decided it is "ableist", but despite having seen a lot or prejudicial language of every sort over the course of my life, I've never heard that word used to derogatorily insult or cast aspersion on a disabled person. The usage, as far as I can tell, is almost always metaphorical, not literal. But rest assured, if it gained enough cultural currency as something directed offensively at others, I would quickly reconsider my own use of the term. I would probably even consider doing so if it had no such literal offensive usage but simply came to be regarded as highly insensitive. Because at some point, even if you disagree with the logic under which a term has been branded as insensitive, and find the objections to be puzzling, you still have to recognize that, at that point, the word has become so charged by social context that your usage runs the risk of imparting additional subtext which you never intended. As far as I can tell though, most people still consider "lame" to be a synonym for "sad, underwhelming" and I'm quite happy to use it in that fashion to describe that "joke". Snow let's rap 03:06, 12 July 2018 (UTC)
More to the point, the Gizmodo article isn't a reliable source but is clickbait junk written by a web content churner with no apparent (much less demonstrated) reputable background in English linguistics, and who is clearly confused in trying (quite poorly) to provide a basis for a language-change activism viewpoint. I've said elsewhere that the fact that some people misinterpret "mankind" as sexist is reason enough to avoid its usage; we don't need to make up, or go along with made up, fake reasons.  — SMcCandlish ¢ 😼  00:28, 9 July 2018 (UTC)
@SMcCandlish: I agree with your conclusions, although personally, as someone who does have a background in linguistics, I would put it slightly differently: most people engage in a kind of subjective folk etymology when they are parsing the a word based on morphemes which they recognize within it; this is an ordinary, useful, and unavoidable feature of cognitive semantics and it is a part of how words evolve in "actual meaning". Most people haven't the first clue about the history of their language, let alone the province of particular words, so engaging in pedantic discussions about word roots and comparative syntax is a massive exercise in missing the forest for the trees (and often conducted by people clearly not trained in the relevant fields who simply wish to try to preserve their preferred interpretation of the meaning of the word and its social consequences, for whatever psychological reasons, typically blundering from one nonsensical linguistic argument to another; actual linguists tend to be rather unbothered by change, given they understand that it is an unavoidable part of the natural phenomena they study).
As a basic tautological matter, a word means what it is received to mean by living speakers, and if a given term is perceived as offensive (or perhaps it is better in this instance to say "inclined to cause irritation in half of us English speakers living on planet Earth today") then that is the reality, and it's pointless to say "well no one felt that way about it when I was young, where I lived!" (which, btw, is almost certainly false; if you (generic/hypothetical 'you', not talking to SMcCandlish here) think women haven't been intuitively reflecting on being discluded by the term for a long, long time, you are probably a man one who hasn't stopped to think for very long about all of the ways language has traditionally put men forward as the default representatives of our species--of which there are many that I assure you do not go unnoticed by women). Snow let's rap 22:44, 11 July 2018 (UTC)
Which is a long way of saying, as I did, that we have reason enough to avoid "mankind" without fake reasons to do so. I have a linguistics minor myself, and understand all of this; I've been trying to keep the discussion from being mired in it, because it's basically immaterial. Even your "a word means what people take it to mean" point doesn't really have much bearing on this, because the word isn't ever taken to mean "men as a class, exclusive of women", except in a rare poetical construct contrasting "womankind" with "mankind"; dictionaries continue to provide the broad definition as the sole or primary one, and RS continue to use it this way. While there's a language-change movement to stamp out use of "mankind", it has not been successful in doing so, or in changing the definition, only in helping a little to shift perception of the appropriateness of the word, a shift that (as you observe) has long been underway without their input. That's what WP cares about, the effect on readers; that is the reason the word should be discouraged here, not for any of these academical and (viz. the Gizmodo article) pseudo-academical ones. WP is making a mistake when it uses wording that causes the reader to mentally rebel, to stop absorbing our material, and to start questioning the project's motives or neutrality. This requires no etymology, and no philosophical or interdisciplinary arguments, just common sense.  — SMcCandlish ¢ 😼  23:06, 11 July 2018 (UTC)
I don't disagree, except for the caveat that the linguistic discussion invariably become part and parcel of the debate whether we'd like it or not, because the utilitarian argument you lay out above eventually always gets met by someone saying "Well, that's just how you perceive it (in your hand-wringing, overly-emotional way), but here's what it really means, because of [X, Y, and Z non-sequitor folk linguistic arguments]" As if a word's semantic effect were in some way a consistent, concrete thing that could be empirically verified by such slap-dash methodology and that such anacrhonisms should prevail over how people actually use and perceive the word in contemporary parlance.
People have been staking out ideological turf surrounding words in that way since forever, and the average Wikipedian is not any more (or in any event, not significantly more) well-versed in the relevant linguistic, semiotic, or empirical analysis such that we cannot expect the same here; indeed, our editors on average are probably closer to the class of people who (for those who have an ideological imperative do so) know just enough about linguistics to feel comfortable constructing a personal theory, but not enough to do so without producing nonsense as a result. I know I see something in that vein virtually every time we have to debate a controversial use of a term that isn't just patently offensive. And incidentally, it comes both ways along the cultural divide surrounding inclusive language; I've had quite the challenge more than once trying to convince editors who wanted to word an article using some obscure/personal gender pronoun (that a subject of a BLP has chosen for themselves) that such an approach is not advisable, using a variation of your "it's about the reader" argument from above. Snow let's rap 00:29, 12 July 2018 (UTC)

RfC: Revisiting the perennial US/U.S. debate

Should MOS:US (WP:Manual of Style#US and U.S.):

  1. Retain its current wording (after some reverting), arrived at several years ago, and stable until October 2017, and stable since then?
  2. Use the newest (recently reverted) version, implemented in a lengthy October 2017 consensus discussion?
  3. Revert to its even earlier wording, which was stable though the early 2010s, despite frequent debate?
  4. Say something substantively different from any of these?

00:51, 6 July 2018 (UTC)

The central matter is whether "US" or "U.S." is the dominant spelling in current (not historical) North American English, across all style guides and reliable sources (i.e., not limited to a particular genre or field). The previous discussion involved detailed source review to answer this question. The current version, based in MOS:COMMONALITY without citing it, relies on "US" being demonstrably dominant; so does the (reverted) newest version, explicit about COMMONALITY; while the MOS:ENGVAR idea suggested in the old version depends on the opposite (ENGVAR only applies to a consistently dominant usage in a country).

The issue raised, for editing, is this: the current version gradually favors "US" over time, and the newest version does so more explicitly, while the old version would keep "U.S." indefinitely in most articles that use it.

Current version (dates to mid-2010s):
US and U.S.

In American and Canadian English, as elsewhere, US has become the dominant abbreviation for United States. However, U.S. (with periods [full points] and without a space) remains common in North American publications, especially in news journalism. At least one major American style guide, The Chicago Manual of Style (since 2010), now deprecates "U.S." and recommends "US". Because use of periods for abbreviations and acronyms should be consistent within any given article, use US in an article with other country abbreviations, and especially avoid constructions like the U.S., UK, and USSR. In longer abbreviations (three letters or more) that incorporate the country's initials (USN, USAF), do not use periods. When the United States is mentioned with one or more other countries in the same sentence, U.S. or US may be too informal, especially at the first mention or as a noun instead of an adjective (France and the United States, not France and the U.S.). Do not use the spaced U. S. or the archaic U.S. of A., except when quoting. Do not use U.S.A. or USA except in a quotation, as part of a proper name (Team USA), or in certain technical/formal uses (e.g., the ISO 3166-1 alpha-3 codes and FIFA country codes).

Newest version (2017):
US and U.S.

US is a commonly used abbreviation for United States, although U.S. – with periods and without a space – remains common in North American publications, including in news journalism. Multiple American style guides, including The Chicago Manual of Style (since 2010), now deprecate "U.S." and recommend "US".

For commonality reasons, use US by default when abbreviating, but retain U.S. in American or Canadian English articles in which it is already established, unless there is a good reason to change it. Because use of periods for abbreviations and acronyms should be consistent within any given article, use US in an article with other country abbreviations, and especially avoid constructions like the U.S. and the UK. In longer abbreviations that incorporate the country's initials (USN, USAF), never use periods. When the United States is mentioned with one or more other countries in the same sentence, US (or U.S.) may be too informal, especially at the first mention or as a noun instead of an adjective (France and the United States, not France and the US). Do not use the spaced U. S. or the archaic U.S. of A., except when quoting. Do not use U.S.A. or USA except in a quotation, as part of a proper name (Team USA), or in certain technical and formal uses (e.g., the ISO 3166-1 alpha-3, FIFA, and IOC country codes).

Early version (early 2010s):
US and U.S.

In American and Canadian English, U.S. (with periods [full stops] and without a space) is the dominant abbreviation for United States, though at least one major American style guide, The Chicago Manual of Style (16th ed.), now deprecates U.S. and prefers US (without periods). US is more common in most other national forms of English. Use of periods for abbreviations and acronyms should be consistent within any given article and congruent with the variety of English used by that article. In longer abbreviations (three letters or more) that incorporate the country's initials (USN, USAF), do not use periods. When the United States is mentioned with one or more other countries in the same sentence, U.S. or US may be too informal, especially at the first mention or as a noun instead of an adjective (France and the United States, not France and the U.S.). Do not use the spaced U. S. or the archaic U.S. of A., except when quoting. Do not use U.S.A. or USA except in a quotation, as part of a proper name (Team USA), or in certain technical/formal uses (e.g., the ISO 3166-1 alpha-3 codes and FIFA country codes).

Please avoid empty WP:ILIKEIT / WP:IKNOWIT comments, as well as wikipolitical arguments about why we have/shouldn't have a style guide, whether a wikiproject should/shouldn't "own" articles in its scope, etc. Please stay on-topic.

This is a procedural RfC suggested by someone else, though dispute since the 2017 change has been minimal. A footnote about inconsistent journalistic usage was elided from the current-version and newest-version copies above, for brevity.  — SMcCandlish ¢ 😼  00:51, 6 July 2018 (UTC)

No preference version
US and U.S.

US and U.S. are commonly-used abbreviations for United States. U.S. – with periods and without a space – remains common in North American publications, including all works of the United States government and in news media, while US is more often used elsewhere.

  • When used as a noun in article prose, prefer United States (avoiding either abbreviation) for better formal writing style. This also avoids mixed-use constructions like the U.S. and the UK in favor of the United States and the United Kingdom, and provides an opportunity for commonality.
  • As an adjective in article prose, either US or U.S. may be used, but don't mix dotted and undotted within the same article. Generally speaking, U.S./U.K. is appropriate for American or Canadian English national variations, and US/UK for others. Prevalence in reliable sources can also be used to determine which to use. Use of either style should be retained in existing articles that they have been established.[a]

US should always be used in tables where other ISO 3166-1 alpha-2 two-letter country codes are in use. Longer abbreviations that incorporate the country's initials (USN, USAF) never use periods, but partial constructions like U.S. Navy and U.S. Air Force may. Do not use the spaced U. S. or the archaic U.S. of A., except when quoting. Do not use U.S.A. or USA except in a quotation, as part of a proper name (Team USA), or in certain technical and formal uses (e.g., the ISO 3166-1 alpha-3, FIFA, and IOC country codes).

Well if this RFC is actually going forward limited to only handling of US/U.S., here is the version I suggest, which does not prescriptively prohibit either style, but gives guidance to avoid the abbreviation for commonality. It recognizes that both dotted and undotted are commonly-used and acceptable, and that neither is a default nor forbidden. This will prevent edit warring and also prevent editors from being sanctioned for following a style they've know their whole lives. I intend to present an expanded form of this sometime in the future to cover other geographical acronyms (like Canadian English frequent use of dotted geographical acronyms like P.E.I., B.C., etc.). -- Netoholic @ 04:56, 7 July 2018 (UTC)

References

  1. ^ This section has changed in the past and may change in the future, mass-changes to articles should be avoided.

Comments on US/U.S.

  • I rarely see the spelling here in the United States as "US", it is usually USA or U.S. - Knowledgekid87 (talk) 00:54, 6 July 2018 (UTC)
    This is not a vote. Do you have some reliable sources on frequency, or the recommendations of modern style guides to cite?  — SMcCandlish ¢ 😼  01:07, 6 July 2018 (UTC)
  • Use the newest wording (i.e., revert to the status quo ante of the last consensus discussion), with current wording as second choice. They are based on overwhelming evidence that "U.S." has not been dominant in North American English for quite some time. Of those publishers who do use it, they are not even consistent with each other (e.g. some newspapers insist on it in headlines but use "US" in running prose, some do exactly the opposite, some use one everywhere, some the other). There is no WP:ENGVAR case that can be made, and the wording in the old version is just patently false. While MoS is not an article, it's grotesque for us to put disproved nonsense in it to advance nationalistic editwarring over a punctuation mark. The newest wording is more practical and will result in less disputation; the current reverted-to wording produces some conflict; the old one was a battleground generator.  — SMcCandlish ¢ 😼  01:13, 6 July 2018 (UTC); revised: 08:53, 9 July 2018 (UTC)
  • I Object to how this RFC was opened. The question is not simply "US vs U.S." but about handling dotted acronyms in certain regional variants of English (per WP:ENGVAR). For example, the preeminent Canadian English style guide The Canadian Style uses dots for all geographical acronyms, such as P.E.I. and B.C.. This RFC was opened with the intent of presenting this question in a limited way and the format of the RFC was not agreed to ahead of time. Calling this "revisiting" a "perennial" discussion in the title of this header betrays the opener's total lack of impartiality on this matter and poisons the question (see WP:RFCBEFORE and WP:RFCST). SMcCandlish's also framing how he wants responses to be made (referencing ILIKEIT) and is already WP:BADGERING here. I'd like to see this RFC speedy closed until we can get a neutral presentation of the actual changes being suggested. -- Netoholic @ 03:27, 6 July 2018 (UTC) I'd like to point out that the opener has taken the opportunity to lay out much of his main arguments within the lead section of this RFC itself. This is just not how to hold a neutral RFC. -- Netoholic @ 04:11, 6 July 2018 (UTC)
    A long thread of responses to this objection has been refactored into the extended discussion section.
  • Gut feeling (no RSs, punctuation is ignored by google and ngram), that excessive/unnecessay dot use is decreasing. —SmokeyJoe (talk) 05:14, 6 July 2018 (UTC)
    • Google Books ngram Viewer - up to 2000: I did just now take a look at this in the Google Books ngram view. In that tool, "US" and "U.S." are aggregated to "U.S.", so cannot distinguish using the out-of-the-box functionality. Link to the ngram query. This analysis does show "U.S./US" > "United States" >> "USA" > "United States of America". Seems "U.S./US" overtook "United States" a bit after 1980, before which "United States" prevailed over all other forms. --User:Ceyockey (talk to me) 16:44, 14 July 2018 (UTC)
      • 1950 to 2008 - changed the analysis window to 1950–2008 and found the order of use unchanged between 2000 and 2008. I tried to take it to 2018, but 2018 was auto-replaced with 2008; appears this is as recent as things go. --User:Ceyockey (talk to me) 16:49, 14 July 2018 (UTC)
  • Whatever the balance of sources, it is clear that modern usage within American material varies to the extent that neither formulation can now be considered integral to American Engvar. As additional sources I would add that the CNN International website uses 'US', as did all the Olympic bid documents from the LA28 committee (I would be interested to know whether CNN's domestic website uses the same, i.e. it's now its house style, or not, i.e. they use unpunctuated style for an international audience?). I'm with SMcC in seeing a trend in this direction for acronyms generally (punctuated style for longer ones like UNESCO died years ago). Outside America (possibly excluding Canada as mentioned above), unpunctuated appears much more common. On the basis of Commonality, ease of reading, and consistency with other acronyms, I would support the current wording. As an aside, I always wondered why USA is deprecated in WP when it is widely used elsewhere; for example I saw it recently in a document submitted to the UN by the US government? MapReader (talk) 07:05, 6 July 2018 (UTC)
    @MapReader: You may be interested to know that the US site (heh) uses "U.S." in the site headings, but article headlines still use "US". — AfroThundr ([[User:|u]] · t · c) 14:33, 6 July 2018 (UTC)
    The headlines and the bodycopy at cnn.com use "US"; it's their menu system that uses "U.S." Deets below.  — SMcCandlish ¢ 😼  01:08, 7 July 2018 (UTC)
  • My take: the entire question is not worth the amount of time and angst we spend on it. I don’t think it matters whether we abbreviate with dots or not, as long as we are consistent within a given article. If the article is consistent... don’t change it. If not... first person to make it consistent “wins”. Blueboar (talk) 11:55, 6 July 2018 (UTC)
  • It seems to me (from my personal observations of usage on the 'net) that a majority of people in the United States use the "US" form, while "U.S." remains the canonical form in government and legal contexts. Internationally, "US" is unquestionably the dominant form. Perhaps we should stick with the current (after reversion) text, or use the newest version with a note that articles regarding government or legal topics are still allowed to use the older form. — AfroThundr (u · t · c) 14:40, 6 July 2018 (UTC)
    That last bit wouldn't be necessary. We don't need the spelling variance except in citations (legal citations take highly specific forms, varying by jurisdiction), because citation style is governed by WP:CITEVAR; that is, a citation can diverge from MoS style in such nit-picks if the citation format requires it. The fact that "U.S. Department of Justice", following Government Printing Office Style Manual style, is what the DoJ itself uses doesn't require anyone else to do so; thus: [6], etc. And WP in particular really doesn't care about "officialness", per WP:OFFICIALNAME.  — SMcCandlish ¢ 😼  20:10, 6 July 2018 (UTC)
    My personal favourite WP:OFFICIALNAME is the 1958 U.S.-UK Mutual Defence Agreement, in which they diplomatically used two types of English in the official abbreviated name. Unfortunately, our MOS:ACRO does not permits this form. Hawkeye7 (discuss) 19:41, 7 July 2018 (UTC)
    If it really were the official title of the document, then it would be permitted, under MOS:TITLES. But it clearly is not the title; it's a Wikipedia-invented WP:NPOVTITLE, a made-up descriptive phrase.  — SMcCandlish ¢ 😼  03:38, 8 July 2018 (UTC)
    It's not a Wikipedia invention; it's the WP:COMMONNAME. eg [7][8][9] Hawkeye7 (discuss) 04:32, 8 July 2018 (UTC)
  • To a large extent, I agree with what Blueboar said: this is a trivial issue. I'm inclined to say that the evidence does point to using US rather than U.S. as a preferred form, and treating the stable form of an existing page, so long as it is consistent, similarly to the way that we treat WP:ENGVAR. Consistency within a page seems most important to me. As for the three wording options above, I find the newest version, with its opaque reference to "commonality", to sound like it was written by a committee, whereas the current/recent version seems to me to be better written and not significantly different unless one counts angels on heads of pins. --Tryptofish (talk) 19:11, 6 July 2018 (UTC)
    It's definitely a trivial issue, but when people revert-war between three versions and demand an RfC, it's probably time to have an RfC. :-)  — SMcCandlish ¢ 😼  20:10, 6 July 2018 (UTC)
    Meh... When editors revert war over trivial things like this, the solution is to strongly chastise ALL those involved for disrupting the project. It always takes two to revert-war. If BOTH are suspended for a day or two, the message will be clear... don't revert-war over trivial things like dots. Blueboar (talk) 20:46, 6 July 2018 (UTC)
    Strange as it may sound (or maybe not), I think the genesis of the most recent dispute over this point comes out of the disputes over US (U.S.?) politics, with the attendant battleground-ing. FYI, there is even a request at the admin requests for closure to have this discussion speedily closed. --Tryptofish (talk) 21:35, 6 July 2018 (UTC)
    Use the current version. I see that other editors are using bold font summaries. Therefore I'll spell out that I think the newest version is badly written so I prefer to use the current version. --Tryptofish (talk) 19:04, 8 July 2018 (UTC)
  • Use the newest wording: this is clear and consistent. --K.e.coffman (talk) 02:34, 7 July 2018 (UTC)
  • Use the newest wording: I think this version is the clearest -- Whats new?(talk) 04:17, 7 July 2018 (UTC)
  • Use the newest wording — If you step back and look at it, MOS:ABBR specifies initialisms should not be rendered with periods. Of all the initialisms that are sometimes rendered with them in various srouces, what is it about U-dot-S-dot that justifies it having been codified as an exception? It can't be WP:ENGVAR because it's not a case of vocabulary, spelling, date formatting or grammar... which are the four listed areas ENGVAR covers. Whether to use periods for initialisms is a matter of style and that's just not covered under ENGVAR. All the arguments that we should follow sources and represent/allow the diverse usage in the "real world" are irrelevant because we don't follow an overarching "use whatever style you want as long as it's consistent" mandate, or else there would be no MOS. We regularly switch out curly quotes for straight ones (MOS:CURLY), hyphens for dashes (MOS:DASH), single quotes for double quotes (MOS:SINGLE), and change whether periods go inside or outside quotation marks (MOS:LQ). We've observed that outside the United States, there is a clear preference overall for initialisms without periods. We've observed that in two countries (the United States and Canada), there is mixed usage, with many arguing that the trend is towards dropping periods. So unless ENGVAR's reach is much more broad than it reads, the entire notion there should be any exception for this one specific initialism seems pretty odd. If US gets an exception, why not PEI, BC, NATO, etc. etc.? No doubt there are people in the UK who prefer it be written "U.K." (and sources that render it that way) but there isn't an entire section in MOS devoted to carving out "U.K." as a sacrosanct rendering meriting an exception. Really the discussion should include the notion of tossing enshrining any exceptions for one initialism out completely, but since that's not on the table, the newest wording—which strikes a balance between resisting wholesale removal of "U.S." and making it clear that new material should adopt the MOS:ABBR guideline as a default—moves towards a clearer state of affairs that doesn't privilege the rendering of one term over any others. —Joeyconnick (talk) 07:10, 7 July 2018 (UTC)
  • Use the newest wording, which is quite clear and explicitly includes language against edit-warring to change it back and forth. CapitalSasha ~ talk 17:31, 7 July 2018 (UTC)
  • Stick with the current version, Use neutral wording, but like Netoholic, I object to how this RfC has been handled, and think it should be struck as not neutrally worded or opened. The "newest wording" is unacceptable as it implicitly disallows use of "U.S." in any new article going forward. --IJBall (contribstalk)
  • I agree with others who have expressed that this is more trouble than it is worth. MOS wars in the past included the incredibly important difference between a hyphen and a dash, also known as the battle of tiny horizontal lines. Today it’s another issue that doesn’t really effect the overall quality of Wikipedia for the reader. (remember the reader? the person we’re all doing this for, not for ourselves to push our preferred rules of The Way Things Ought To Be?) and agree with Blueboar that consistency within individual articles is enough of a standard and also that anyone who edit wars over this in mainspace or MOS gets a swift kick out the door. Beeblebrox (talk) 18:01, 7 July 2018 (UTC)
    Sure. The reason this is being RfCed at VPPOL is because of editwarring over the wording. The triviality of the subject should not lead to such drama, so we should just put it to bed and move on.  — SMcCandlish ¢ 😼  03:44, 8 July 2018 (UTC)
  • Use the newest wording Per Beeblebrox. I am haunted by MOS:DASH, in which the MOS broke links all over the place, forced the development of special editing tools, and remains a pain that just won't go away. My other fear is that the adoption of this RfC will be touted in the media as another instance of Wikipedia's anti-US bias. Hawkeye7 (discuss) 19:41, 7 July 2018 (UTC)
  • Use neutral wording: if strong advice is not being offered as to which style a writer should adopt, it should be left at his own discretion--ie, there should not be thought-swaying either way by the MoS. We have failed to reach a consensus as to whether or not 'U.S.' should be depreciated (or we had the last time I was involved), deciding that it should be an individual decision. But, under no circumstances should 'U.K.' be accepted, or encouraged in any way: it is not a common style in the UK itself, and the American style guides seem to be moving away from it (even if my iPhone obsessively adds the points). I completely agree with the current 'do not mix ...' guidance, which seems to have caused reasonably few problems that I have encountered, and offers some clear direction to copyeditors as to how to deal with "style mixing". Sb2001 23:55, 7 July 2018 (UTC)
  • It doesn't matter whether we use the dots or not. Just block people who edit war over it. NinjaRobotPirate (talk) 00:11, 8 July 2018 (UTC)
  • I don't think an external issue really matters here; after all, it's not something major to the reader so long as they can comprehend the article. In short, I agree with Hawkeye7 et alii, who note that consistency within articles means more than some lines of text in the Manual of Style. (Because, ultimately, that a reader gets the information they want is our end goal, right?) That being said, I do not believe that consensus regarding the implicit or explicit deprecation of any one style vis-à-vis another can be found, and, really, the MOS issues are a bit arcane, to say the least. Anyway, to stop rambling on, I agree wholly with Sb2001: use the neutral, no preference wording. Javert2113 (Siarad.|¤) 02:18, 8 July 2018 (UTC)
  • The magnitude of the debate about this is excessive compared to the magnitude of the underlying dispute. Seriously guys, it doesn't matter that much, and we should stop arguing about this and go build an encyclopedia. Support whatever option puts this most firmly to bed permanently. Tazerdadog (talk) 03:26, 8 July 2018 (UTC)
  • Use the newest wording: Mainly because it is the consensus from a lengthy and reasonably recent discussion (I'm taking SmC's word for this), but also because it is unambiguous. Current version arbitrates nothing except in articles that have other country abbreviations. I don't actually like the newest wording because 1) it makes the preferred style depend upon the history of the article, which defies the purpose of a manual of style; and 2) it introduces unnecessary ENGVAR - there's clearly a common version acceptable everywhere. But I can accept consensus is against me. Bryan Henderson (giraffedata) (talk) 16:25, 14 July 2018 (UTC)

Extended discussion of US/U.S.

  • Here's a copy-paste of my sourcing run from the last round of this discussion, for those who don't want to go look in that thread:
RS citations, with direct quotes (and analysis by SMcCandlish):
Sourcing

I'll get this started, using the stack of style guides closest to my desk (leaves out some stuff like Scientific Style and Format):

  • "10.4", "10.33". The Chicago Manual of Style (16th ed.). University of Chicago. 2010. pp. 489–490, 500:. 10.4: Periods with abbreviations. ... Use no periods with abbreviations that appear in full capitals, whether two letters or more, and even if lowercase letters appear within the abbreviation: VP, CEO, MA, MD, PhD, UK, US, NY, IL .... 10.33: "US" versus United States. In running text, spell out United States as a noun; reserve US for the adjective form only (in which position the abbreviation is generally preferred). See also 10.4. US dollars, US involvement in China, but China's involvement in the United States.  It has a side rule to use "U.S." in publications that use "traditional" US state abbreviations like "Ill." and "Calif.", but WP is not one of these, and CMoS recommends against the practice anyway. This edition's material on this is a reversal from the 15th ed. which still favored "U.S." Notably, MoS began when CMoS 15th was current, and has seen extensive revision over time to match the 16th (as it has also been being updated to match post-2010 editions of New Hart's Rules / Oxford Style Manual and Fowler's, etc., as the rest of the world does.
  • "10.31", "10.32". The Chicago Manual of Style (17th ed.). University of Chicago. 2017. pp. 573–574, 585–586:. 10.4: Periods with abbreviations. ... Ues no periods with abbreviations that include two or more capital letters, even if the abbreviation also includes lowercase letters: VP, CEO, MA, MD, PhD, UK, US, NY, IL. [Also has the previous edition's rule to prefer "U.S." with "Ill." abbreviations.] 10.31: Abbreviating country names. Names of countries are usually spelled out in text but may be abbreviated in tabular matter, lists, and the like. [Recommendation to consult dictionaries for abbreviations rather than making up new ones.] ... Certain initialisms, on the other hand, may be appropriate in regular text, especially after the full form has been established .... 10.32: "US" versus "United States." Where necessary, initialisms for country names can be used in running text according to the guidelines set forth [in previous sections about overuse of abbreviations, etc.] Note that, as a matter of editorial tradition, this manual has long advised spelling out United States as a noun, reserving US for the adjective form only (where it is preferred) and for tabular matter and the like. In a departure, Chicago now permits the use of US as a noun, subject to editorial discretion and provided the meaning is clear from context. US dollars, US involvement in China, China's involvement in the United States or China's involvement in the US.  Brand new edition; hasn't had much real-world impact yet. CMoS has clearly softened on its stance about nouns.
  • Burchfield, R. W., ed. (2004). "acronym". Fowler's Modern English Usage (Revised 3rd ed.). Oxford University Press. pp. 17–18.  Gives no explicit rule, but uses "US", "UK", "USSR" style throughout, and says of things like "U.N.E.S.C.O." that this is an intermediary stage in adoption of an acronym. This material is a bit dated; we don't actually do it that way any longer; a newly introduced acronym will appear as SNRKL not "S.N.R.K.L." in most publications. Burchfield also favors the confusing practice of writing some true acronyms as if words and capitalizing their first letter even if they're not proper names, e.g. "Aids" for AIDS; this practice seems not to have caught on except among some British/Commonwealth news publishers, and I think one or another of the stylistically weirder American publications (New Yorker, maybe? New York Times, but not consistently).]
  • Butterfield, Jeremy, ed. (2015). "acronym". Fowler's Dictionary of Modern English Usage (4th ed.). Oxford University Press. p. 16.  Uses essentially the same wording as Burchfield's edition.
  • "1.6: Abbreviations". MLA Handbook (8th ed.). Modern Language Association. 2016. p. 95. Use neither periods after letters nor spaces between letters for abbrevaitions made up predominantly of capital letters: BC, DVD, NJ, PhD, US.  Has no noun/adjective rules but urges (on the same page cited here) reserving abbreviations for tabular data, citations, and other compressed material.
  • "8.3: Geographic Names". MLA Style Manual and Guide to Scholarly Writing (3rd ed.). Modern Language Association. 2008. pp. 264, 269. [S]pell out in the text the names of countries, with a few exceptions (e.g. USSR). In documentation, however, abbreviate the names of states, provinces , countries, and continents. [List of abbreviations begins] ... US, USA: United States, United States of America  Does not include "U.S.", nor a noun/adjective rule.
  • "7: Shortened forms". Style Manual of Authors, Editors and Printers (5th ed.). Australian Government Publishing Service. 1994. pp. 107, 116–117. 7.5 Abbreviations that consist of more than one capital letter or of capital letters only are written without full stops: ACT, RSPCA, PhD, GPO, IBRD, USA. ... 7.7: Acronyms ... Acronyms are written without full stops. 7.67: The names of countries, except for the former Soviet Union, which is usually designated USSR, should be spelt out in general text. For example: The United Kingdom, the United States, Australia, New Zealand and Japan have agreed ... not The UK, the USA, Australia, NZ and Japan have agreed .... For text, this rule should be waived only in heavily statistical or greatly condensed scientific work. 7.68: In text that uses many shortened forms, the standard abbreviations for name of countries may be used adjectivally: UK tariffs have ...; In her study of NZ foreign policy ..... 7.69: Standard abbreviations for names of countries are used in tables, figures, notes, references and bibliographies, where space considerations are important: UK, USA, Statistics Act 1975 (NZ), s 37.  There may be a newer edition out now; last time I looked it was still in production, but that was a few years ago.
  • Hull, Christine A.; Huckin, Thomas N. (2008). The New Century Handbook (4th ed.). Longman / Pearson Education. pp. 810, 872. 48d: Avoid common misuses of periods. ... Do not use periods with acronyms and other all uppercase abbreviations. [Emphasis in original.] The recent trend is not to use periods with common abbreviations for states, countries, organizations, computer programs, famous eople, and other entities: CA, NOW, MIT ... USA, MS-DOS, JFK ... HTML, AAA .... 56e: Avoid most other abbreviations in formal writing. Place names, including the names of states, countries, provinces, continents, and other locations, should not be abbreviated except in addresses and occasionally when usd as adjectives (for example, in US government).  Uses dot-free acronyms throughout, except for latinisms (e.g., p.m., i.e.). Specifically illustrates
  • Waddingham, Anne, ed. (2014). "10.2.4. All-capital abbreviations". New Hart's Rules (2nd ed.). Oxford University Press. p. 174. Acronyms and initialisms of more than one capital letter take no full points in British and technical usage and are closed up: TUC, MA, EU .... In some US styles certain initialisms may have full points (US/U.S.).  There isn't an adjective/noun usage distinction maintained in New Hart's.
  • Ritter, R. M., ed. (2005). "10.2.4. All-capital abbreviations". New Hart's Rules (1st ed.). Oxford University Press. p. 170–171. Acronyms and initialisms of more than one capital letter take no full points in British and technical usage and are closed up: TUC, MA, EU .... US English uses points in such contexts: U.S., L.A.P.D., R.E.M.  This was wrong even when it was published; the two leading US style guides (CMoS for academic writing, and Associated Press Stylebook for journalism) were already condemning this, and dominant usage of "LAPD" is provable in seconds [10] by an N-gram constrained to US English and the decade leading up to publication of Ritter's book. Ritter's comment appears to be material left over from the 1980s Hart's Rules, when it might have been closer to accurate. "REM" in the sleep sense has been absolutely dominant without periods for decades [11], and in the case of the band name, it's a proper name (also from the '80s) styled however the band likes (the band consistently used the dots, but the press did not [12]).
  • Garner, Bryan A. (2016). "U.S.; U.S.A". Garner's Modern English Usage (4th ed.). Oxford University Press. As shortened forms for United States, these terms retain their periods, despite the modern trend to drop the periods in most initialisms. ... U.S. is best reserved for use as an adjective <U.S. foreign policy> although its use as a noun in headlines is common. In abbreviations incorporating U.S., the periods are typically dropped <USPS>, <USAF>, <USNA>.  Garner seems (at first; see next entry) the primary hold-out in the style-guide world for "U.S.", and does not even acknowledge the usage shift, or that non-US usage might differ. This is weird because the current edition is taking pains to be more descriptive (even extensively using N-gram data) with hundreds of entries updated with usage-shift info; this entry was not updated. Whether this represents Garner not getting around to it or studiously avoiding it is anyone's guess. Despite being published by Oxford, this is a thoroughly American work, and Garner is not a linguist but a lawyer, steeped in legal writing (he's the editor or author of various works on legal writing); it's a register that in the US always uses U.S. except in longer acronyms like USAF. See next entry, however.
  • Garner, Bryan A. (2016). The Chicago Guide to Grammar, Usage, and Punctuation. Chicago University Press. p. 388. 537. Use a period to indicate an abbreviated name or title. (The salutary trend, though, is to omit periods with acronyms and initialisms—hence BBC ...)  I looked at every page the index said had anything to do with abbreviations, acronyms, initialisms, the period, proper names, and proper nouns. There's nothing about "U.S.", nor did I see it used in the prose while skimming, and he uses "UNESCO"-style throughout. This may be evidence that the entry in GMEU, above, simply didn't get updated since the last edition, or it may reflect editorial changes made by someone at the respective publishers; no way to really know.
  • Williams, Malcolm (1997). Bucens, Vitalijs, ed. The Canadian Style: A Guide to Writing and Editing (Revised and Expanded ed.). Public Works and Government Services Canada Translation Bureau / Dundurn Press. pp. 20, 25, 30, 55. 103: Periods. In recent years there has been a trend toward omission of periods in abbreviations. This is particularly true of scientific and technical writing, but the practice has been spreading in general writing as well. a) Do not use periods with the following: [Emphasis in original.] ... abbreviations or acronyms consisting exclusively of upper-case letters or ending in an upper-case letter (except those for personal names, legal references and most place names), e.g.: NAFTA, PhD, YWCA, UN, GST, MiG, CTV. (b) Use periods with geographical abbreviations, e.g. B.C., P.E.I., but not for the two-character symbols recommended by Canada Post . This appears to be self-contradictory, since the CP two-letter symbol for British Columbia is in fact BC. This seems to imply using U.K., U.S., etc., but US is used on p. 30, then U.S.A. on p. 55. So, I give up on what they really want. Regardless, it doesn't actually appear to reflect typical, current Canadian style (it is 20 years old); I lived there in 2005–2006, and did not regularly encounter "U.K." and "U.S.A."
  • "Chapter 4. Abbreviations". Editing Canadian English (2nd ed.). Editors' Association of Canada. 2000. pp. 51–52. Geographical designations: ... 4.19. Abbreviations for names of countries can be used in special circumstances (tables, charts, lists). In text copy, names are usually spelled out.  ECE provides no rule against using dots, and illustrates US/U.S. and UK/U.K., even USSR/U.S.S.R.. However, in the preceding sections on acronyms (§4.8) and initialisms (§4.9) it uniformly illustrates all of them without dots, a clear preference. It has no noun/adjective rule.
  • Hacker, Diana (2006). "38a. The period". The Bedford Handbook (7th ed.). Bedford / St. Martin's. p. 423. In abbreviations: ... A period is not used with US Postal Service abbreviates for states .... Current usage is to omit the period in abbreviations of organization names, academic degrees, and designations for eras.  So, doesn't state a country rule, but illustrates use of US.
  • AMA Manual of Style: A Guide for Authors and Editors (10th ed.). American Medical Association / Oxford University Press. 2007. pp. 334, 451. 'When not to use a period: ... [D]o not use periods with honorifics (courtesy titles), scientific terms, and abbreviations .... JAMA, NIH ... 14.5: Cities, States, Counties, Territories, Possessions; Provinces; Countries. At first mention the name of a state ... or country should be spelled out when it follows the name of a city. [Elided long note that JAMA doesn't do it with "United States" after US places only because its readership is largely American.] ... Names of cities ... and countries should be spelled out in full when they stand alone. ... Abbreviations such as US and UK may be used as modifiers (ie, only when they directly precede the word they modify) but should be expanded in all other contexts. The authors surveyed representative samples of urban populations in the United States and United Kingdom according to US and UK census data.  Uses "US" throughout. [Aside: This passage is, incidentally, proof of use of ie for i.e. in a US style guide; along with frequent use of i.e. in British publications that aren't newspapers, that kills the bogus ENGVAR argument for ie that we were seeing here about a month ago.]
  • "4. Abbreviations". MHRA Style Guide (Third [corrected] ed.). Modern Humanities Research Association. 2015 [2013]. p. 31. 4.4: Use of full stop ... Full stops are omitted in capitalized abbreviations or acronyms for: ... (b) Countries, institutions, societies, and organizations (none of them italicized): UK, USA, BL, BM, UNAM ....  [Aside: This publication is proof of use of Oxford spelling ("the Oxfrod -ize") in British publications besides those of Oxford University Press. It also calls for Latinisms to retain dots when abbreviated: i.e., e.g., and so on]
  • Style Guide for Business and Technical Communication (5th ed.). Franklin Covey. 2012.  Self-inconsistent and confusing. The chapter on abbreviations gives all acronyms and initialisms in RAM and GNP style, but in an abbreviation list wants to not only use U.S. but to use U.S.A. to mean United States of America versus USA to mean United States Army; that's a "diff-caps" approach that is far too assumptive of the reader being in lock-step with the writer's intent for us to use it here.
  • American style guides dating to the 1990s and earlier are more apt to use (and sometimes have a rule in favor of) U.S., e.g. the ACS Style Guide from that era.
  • In academic American style guides this appears to be rare now; the only semi-recent one I can find so far in favor of U.S. is Publication Manual of the APA (5th ed.). American Psychological Association. 2001. . It otherwise uses UMI-style acronyms/initialisms throughout (it gives U.S. as a special exception). It also has the adjective rule for it. No idea what the more recent edition says; the 6th dates to 2009, and I have one around somewhere.
  • US legal style guides use U.S. consistently, because this is the style required by most of the courts that have issued style requirements for legal filings, and is also the preference of the US Government Printing Office's manual, which means that regulatory agencies (which whom lawyers often have to communicate) also use it.
  • I found one 2005 work, The Cooper Hill Stylebook, 2nd ed., still advocating dots in all acronyms and initialisms.
  • Strauss, J.; et al. (2014). The Blue Book of Grammar and Punctuation (11th ed.). , doesn't appear to address the matter, though it seems to give acronyms and initialisms throughout in no-dots, all-caps, no-spaces style.
  • The AMA Handbook of Business Writing'. American Marketing Association. 2010. , appears to be agnostic on dots with initialisms and acronyms, and doesn't address country names in particular.
  • American journalistic style is all over the place, and contradictory. (British/Commonwealth is not; it's all "US" or "USA".) Many news publishers (especially those who employ all-caps headlines) use U.S. in headlines but not in running text; others use U.S. all the time; others don't use it at all, including most non-North American news publishers.
    • "U.S.". Associated Press Stylebook (2015 ed.).  (arranged alphabetically by entry, which is more specific than page numbering; 2015 is the most recent edition I have) strangely recommends to use U.S. in body copy but US in headlines (probably because it recommends against all-caps headlines but for maximal headline compression).
    • The Wall Street Journal Essential Guide to Business Style and Usage. 2002. , says to always use U.S. and never give United States, except "in quotes or for special effect". That's obviously not an encyclopedic writing style.
    • The New York Times Manual of Style and Usage (5th ed.). 2015.  (arranged alphabetically by entry, which is more specific than page numbering), which says "U.S. for United States, but only in headlines, summaries, tables and charts, and when unavoidable in picture captions." Seems like AP Stylebook, right? But then it insists on URL but U.S.A.I.D., U.S.S.R., V.A.; then VC and VCR; but a surprise dodge to Unicef and Unesco, yet U.N.; and finally has a total meltdown: "U.N.AIDS (no spaces) for the United Nations program on H.I.V. and AIDS." Wow. There's just no rhyme or reason to this at all. Pretty much no one else in the world would contemplate writing "U.N.AIDS", much less "H.I.V. and AIDS", or "U.N." then "Unesco".
    • "Reuters Handbook of Journalism". Reuters. 2017. abbreviations. Retrieved 8 October 2017. Generally, omit full stops or periods in acronyms unless the result would spell an unrelated word. Most abbreviations of more than two letters do not take periods. But use periods in most two-letter abbreviations: U.S., U.N. (Exceptions include: EU, UK).  That's an idiosyncratic house style.
    • "BBC News Style Guide". 2017. Grammar, spelling and punctuation section. Retrieved 8 October 2017. . Uses "US President James Tucker" [a hypothetical example, obviously]; advises "UN, Nato, IRA, BBC"; this is consistent with typical British press usage ("US" not "U.S.", but treat pronounceable "word acronyms" in Aids and Unesco style), which can be verified with online style guides from The Guardian, The Economist, London Times, etc.; I'm not going to include them all individually.
  • News search: Just doing a Google News search clearly demonstrates a preference for "US" even in American publications, though (as noted above) particulars vary all over the place, with "U.S." sometimes used in main text but not headlines, or vice versa, or not at all, or in both.
  • Google Ngrams can't be used for this to check out book usage, unfortunately, as they processed "U.S." and "US" as synonymous and merged them.
  • I recall from previous digging that some business-English guides other than that of the Am. Mktg. Assn. also favor "U.S." Marketing ones, which are otherwise similar on many points, tend not to, because they deal with a lot of fancy logo typography, and know that dots in abbreviations in signage and ads impair quick reading when they're superfluous.
  • Sabin, William A. (2005). "When to Use Abbreviations". Gregg Reference Manual (10th ed.). McGraw-Hill. p. 146.  Has no explicit rules that are relevant here. Illustrates and consistently uses no-dots upper case for most acronyms and initialisms: IBM, ZIP, AIDS, CT or CAT scan, URL, CST and EDT, NAACP, SEC. Makes conventionalized exceptions for a few things: Ph.D., laser, a.m./p.m., A.D./B.C.; wants dots after Co., Inc., Ltd. However, does use "U.S." in several examples (at least some of them quoted material).
  • Faigley, Lester (2012). "50b. Acronyms". The Penguin Handbook (4th ed.). Boston: Longman / Pearson. pp. 680–682. Punctuation of abbreviations and acronyms: The trend now is away from using periods with many abbreviations. In formal writing you can still use periods, with certain exceptions. Do not use periods with: 1. Acronyms and initial-letter abbreviations: AFL-CIO, AMA, HMO, NAFTA, NFL, OPEC. 2. Two-letter mailing abbreviations: AZ (Arizona) .... 3. Compass points: NE (northeast) .... 4.) Technical abbreviations: kph (kilometers per hour), SS (sum of squares), SD (standard deviation).  Entire section illustrates all acronyms and initialisms in AIDS, NASA, etc. style (except for assimilated-as-words acronyms like laser, and Latinisms like i.e.). Doesn't make an exception for US, or address it directly.
  • Faigley, Lester (2015). "47b. Acronyms". The Brief Penguin Handbook (5th ed.). Boston: Longman / Pearson. pp. 519–521.  Exact same text on this material as in the larger previous edition.

This is just a start, though it took several hours and I'd rather not do more unless really necessary.

Conclusion so far:
"US" is dominant in English generally. "U.S." is still present aplenty in North American writing, but its usage is wildly inconsistent in American news publishing (even opposite from publication to publication as to whether it's used in headlines vs. body copy), now eschewed in academic publishing (what MoS is almost entirely based on), though found consistently in US legal writing. There's no recent style guide evidence that the dot-bearing spelling is preferred in Canada (the stuff that favors it is also from the '90s); the 2000 Canadian source doesn't favor "U.S." The rule to abbreviate adjectival but not noun use is common but not universal, and may be eroding (CMoS thinks so); however, various guides that do not have this rule instead do not want country names abbreviated at all except in tables, citations, etc. Some just do not really care, though. [Side observation: All these sources in favor of acronyms and initialisms in the form UN and FBI are also in favor of no dots in PhD and other degrees and titles. A semi-recent RfC on that closed without consensus as I recall, because no one did the style-guide research. If it comes up again, the sources in the above list can be used to ensure a closure with consensus for dropping the extraneous dots.]
 — SMcCandlish ¢ >ʌⱷ҅ʌ<  01:54, 8 October 2017 (UTC); updated 08:41, 11 October 2017 (UTC)

 — SMcCandlish ¢ 😼  01:29, 6 July 2018 (UTC)

I've changed the hatting note to reflect that this is no simple list of sources and quotes, but also includes SMcCandlish's analysis and viewpoints. -- Netoholic @ 05:48, 6 July 2018 (UTC)
Sure. I don't see what the point is, when if you actually read the material this is obvious; but whatever you like.  — SMcCandlish ¢ 😼  06:07, 6 July 2018 (UTC)

Thread in response to Netoholic's objection relocated here to keep the comment section un-mired.

  • I understand it as a special case--a proposal that regardless of any general rule about initialism, that in US contexts we should use U.S. (Personal preferences vary--10 years ago I would have written U.S. as a matter of course, but now my own writing tends to have UK style for this. I think that in fact may not just be personal, but reflect a general trend in the United States to use the simplified UK version of initialisms. I think it's rational to discuss special cases for the most widely used instances. I'm not expressing an opinion of the actual merits; just that I do notthink the proposal disruptive or biased or even inappropriate. DGG ( talk ) 04:50, 6 July 2018 (UTC)
    This is not, though, an issue just of handling of US/U.S., no matter how many times SMcCandlish tries to frame it as such. Yes, there is probably an everyday use trend toward dropping dots, but we're concerned about formal writing style - not what shortcuts people use in the age of smart phones and instant messaging. No one (I think) is advocating that we switch to using dots - only that dotted acronyms for geographic locations be considered acceptable use and not dismissed out-of-hand because others use a different style within their WP:ENGVAR. -- Netoholic @ 05:55, 6 July 2018 (UTC)
    Anyone can open an RfC about anything they want, and the one I've presented is factual and balanced. Asking someone for evidence isn't "badgering", it's standard operating procedure. Your issues were not even clearly articulated, but mostly just circular argument and days of throwing shade at an October 6–17, 2017, detailed consensus discussion simply because it didn't give you the answer you like. My concerns are clearer: either the 2017 consensus holds, or there's something wrong with it, so let's settle it. This is perennial; editors been arguing about it the entire time MoS has existed. The 2017 discussion happened and concluded as it did because there is now sufficient RS evidence to be certain. We cannot keep re-litigating this until the end of time. I included an "other" option for you and anyone else with an alternative idea (people tend to object to binary choices). It's perfectly normal to remind people to stay on topic and avoid the arguments to avoid if they are commonly presented at a particular type of RfC and tend to trainwreck them.

    Moving on: there is no ongoing dispute about "UK" vs. "U.K.", etc. This has been covered by MOS:ABBR for over a decade without strife or contention. There's a very stable site-wide consensus to present acronyms/initialisms in "UK, HIV/AIDS, USAF, and UNICEF" format, not "U.K., H.I.V./A.I.D.S., U.S.A.F. [even the USAF doesn't!], and U.N.I.C.E.F." format (nor in daft journalese like "Aids and Unicef"). There is no open question about this, only about "U.S.", because some Americans doggedly insist on this mid-20th-centuryism despite proof that it's no longer dominant usage even in American publishing. And just because the "P.E.I." style exists at all doesn't mean it should be used here instead of "PEI". It is not an ENGVAR matter, since there is no nationwide consistent norm to use that style anywhere in the anglosphere any longer. — SMcCandlishan American ¢ 😼  06:48, 6 July 2018 (UTC)

    "there is no nationwide consistent norm" - If this is the case, then we of course must allow either method to be used. Only if undotted WAS a national norm could we even begin to discuss limiting our MOS in accordance. For articles that are written in American or Canadian English varieties, both methods are common and acceptable. That is enough to say that we should not (and in practicality, can not) enforce one over the other. And please stop attacking people who use this method by saying they "doggedly insist" - you're being exclusionary of writing styles which are common in English varities other than your own. This is not in the spirit of WP:ENGVAR. It is perhaps a mistake to frame ENGVAR as "national varieties" when regional differences exist within nations... but if you're going to focus on "national norms", then we must give high weight to the style guides produce by national bodies such as The Canadian Style (in use by the Canadian government) and the works of the United States government such as the GPO Style Manual (and guides by National Archives, USA.gov, Office of Energy, EPA, NASA, Army, Navy, Air Force, Marines, Congress, Supreme Court). Don't guides used by national governments adhere to (or define) national norms? -- Netoholic @ 07:26, 6 July 2018 (UTC)
    MoS says nothing like that whatsoever. ENGVAR applies when there is a consistent national norm, e.g. colour/color, tyre/tire. Otherwise, a general MoS provision doesn't have an ENGVAR exception. MOS:ABBR is a general provision, to which you're seeking "special exceptions" and now you're insisting on it with the basis that they're not consistenly used in sources. This just doesn't track, sorry.  — SMcCandlish ¢ 😼  09:03, 6 July 2018 (UTC)
    Don't guides used by national governments adhere to (or define) national norms? -- Netoholic @ 09:32, 6 July 2018 (UTC)
    No. I originally responded to this with a run-down of what style guides have any real impact on broad usage and on Wikipedia. I've since refactored that to Wikipedia:Identifying and using style guides. Government style guides determine bureacratese/governmentese/militarese (regulatory language); they also tend to affect legal style a little (a field with its own manuals), and business writing to an extent (which also draws heavily on journalism/marketing style, of course). And that's about it. I've never in my life heard of a English class recommending the GPO Style Manual, for example. It's a quirky style, full of excessive capitalization and a hatred of hyphens, commas, and much other punctuation.  — SMcCandlish ¢ 😼  10:44, 6 July 2018 (UTC); revised: 22:57, 6 July 2018 (UTC)
The "neutral" proposal does include 'Generally speaking, U.S./U.K. is appropriate for American or Canadian English national variations', which I may suggest is advocating that 'U.K.' is acceptable. I do not see 'U.S.' as being the same as 'U.N.I.C.E.F.'--one is an acronym; the other an initialism. My personal preference is for the so-called "journalese" 'Unicef', but I recognize that there is little chance of that viewpoint being adopted. Having just come back from a six-month break, I had rather hoped that the argument would have moved away from combining these two issues. There is compelling evidence for 'US' rather than 'U.S.' If editors choose not to take notice of it, we must offer them a clear choice, rather than trying to prompt them into selecting one style over the other. Sb2001 00:06, 8 July 2018 (UTC)
I'm not certain what you mean. If they're offered a choice, then they'll have to select one style over the other. I think you're indicating that MoS should recommend something specific rather than present a choice for such selection.  — SMcCandlish ¢ 😼  03:32, 8 July 2018 (UTC)
Not at all: I am stating that it is unreasonable to offer a choice and present one side as being more "logical" than the other. Ie, neutral wording should be used in order that it does not appear that decision making is being swayed. Of course they have to make the choice; that does not mean that we have the right to influence it when no decisive conclusion has been drawn on the "US v U.S." issue. Sb2001 15:19, 8 July 2018 (UTC)
Where's that coming from, though? No one's made a logic argument. There's a practicality one, and a how-well-does-it-reflect-reality one, but those aren't arguments about the intrinsic logic of either style. Punctuation is pretty arbitrary, and it shifts over time. That is, after all, why this debate even exists; the usage has shifted over about the last 30 years.  — SMcCandlish ¢ 😼  00:33, 9 July 2018 (UTC)
Perhaps 'logical' was the wrong word ... I'm not talking about which is the "better" one--if it were up to me, I would discourage people from using 'U.S.' The fact of the matter is that we are dealing with a completely unresolved debate, and one which I doubt will be resolved in the foreseeable future. If the MoS does not favour one style, it should not be presenting one-sided wording alongside it. That is the only point I am actually making here: if, amongst ourselves, we are unable to decide, we must actually leave it at the discretion of the individual. Sb2001 00:42, 9 July 2018 (UTC)
It does favor one style; see MOS:ABBR. We were making a single, lone exception for a while for "U.S." on the assumption that it was dominant in current American writing, but this turns out not to be true for some time now. It's not a "completely unresolved debate"; the sourcing is firmly in favor of "US", and so has MoS been for several years (both the current and new wording) until someone decided to try to rewrite it to suit their preferences, against the last rather comprehensive consensus discussion on the matter. We're not unable to decide amongst ourselves; the response so far has overwhelmingly been in favor of either the new or current wording, not the early 2010s wording.  — SMcCandlish ¢ 😼  09:00, 9 July 2018 (UTC)

Update: The Chicago Manual of Style 17th ed. (2017) wasn't included in the original source run (I didn't have it yet at the time). Despite Netoholic's strange claims to the contrary [13][14], it's almost word-for-word identical to the advice in the 16th ed., never even mentioning "U.S." except in the context of old-style envelope addresses using traditional state abbreviations ("Mass., U.S.", "Calif., U.S."). Here's the full relevant text:

The Chicago Manual of Style, 17th ed. (2017), University of Chicago Press, ISBN: 9780226287058

10.4 Periods with abbreviations.
...
3. Use no periods with abbreviations that include two or more capital letters, even if the abbreviation also includes lowercase latters: VP, CEO, MA, MD, PhD, U, US, NY, IL.
4. In publications using traditional state abbreviations, use periods to abbreviate United States and its states and territories: U.S., N.Y., Ill. Note, however, that Chicago recommends using the two-letter postal codes (and therefore US) wherever abbreviations are used....
...
10.28 Abbreviations for Canadian provinces and territories. ... may be abbreviated in bibliographies and the like—using the two-letter postal abbreviations, which have the advantage of applying to both the English and French forms. AB [=] Alberta; ... PE [=] Prince Edward Island ....
...
10.31 Abbreviating country names. ... Certain initialisms, on the other hand [i.e., in lieu of spelled-out names], may be appropriate in regular text, especially after the full form has been established.... UAE (United Arab Emirates), US, UK, GDR ....
...
10.32 "US" versus "United States." ... Note that, as a matter of editorial tradition, this manual has long advised spelling out United States as a noun, reserving US for the adjective form only (where it is preferred) and for tabular matter and the like. In a departure [i.e., from the 16th ed.], Chicago now permits the use of US as a noun, subject to editorial discretion and provided the meaning is clear from context. US dollars; US involvement in China; China's involvement in the United States or China's involvement in the US.

I skipped 10.27 (US states and territories) because it gives the same advice (two-letter postal codes, no dots) as 10.4 and 10.28. This is the same advice as in the 16th ed. (2010), aside from a few copyediting tweaks, and the new "In a departure" note, quoted above.

 — SMcCandlish ¢ 😼  09:00, 6 July 2018 (UTC)

"except in the context of old-style envelope addresses" - THAT is the very meat of this issue. We're NOT talking about data tables that might use either a list of state/province postal codes or that use ISO two- or three-letter country codes. The question at hand is handling of abbreviations in running article prose, for example when an article mentions "actions of the U.S. Navy", "information regarding P.E.I. officials", "historical sites in Vancouver, B.C.", or "U.S. Interstate 787 which terminates in Albany, N.Y.". This is exactly why this RFC needs to be called off and re-thought... the scope doesn't seem to be clear to its opener. You seem to be trying to argue that should be using postal codes in these scenarios. -- Netoholic @ 09:29, 6 July 2018 (UTC)
We already have a whole guideline page on this, MOS:ABBR, and it's clear on this: WP gives acronyms without the dots. It does not matter that a style with dots is attested; it isn't the style we use. You wanted an RfC about MOS:US, after briefly revert-warring [15][16] (after objections [17]) to change it without discussion – and accusing others of having done so when there was actually a large consensus discussion about it before you arrived. Now that there's an RfC, you've switched gears and want to change our entire treatment of acronyms? No. That is not this discussion. You can go start a new RfC on that, because it's a radical change to how WP has been written for about 17 years now. That belongs at WP:VPPRO, being a major proposal, not a minor P&G clarification.  — SMcCandlish ¢ 😼  09:45, 6 July 2018 (UTC)
Is it clear on this? "WP gives acronyms without the dots" seems inaccurate because I see several places where U.S. is used in the examples: "New York is in the U.S.", "U.S. Central Intelligence Agency" and "U.S. government", "Great Northern Railway (U.S.)". #Miscellanea and #Abbreviations widely used include several acronyms with dots (lower-case ones and compass directions). As an aside, why does this page give advice to "please create redirects that contain (US) and (U.S.)" but not the same advice for (UK) and (U.K.) or any other geographic abbreviation? I have never heard of anyone actually doing that in either case, but its just weird how one is singled out. -- Netoholic @ 10:30, 6 July 2018 (UTC)
Because "U.S." is a permissible exception (depending on context) by long consensus. That doesn't mean "U.K." or "P.E.I." are. There is no wording contemplated in this RfC or in any of the editwarred-over versions at MOS:US that make "U.S." never permissible. But nor do any of them make U.S.S.R. or H.I.V./A.I.D.S. permissible; "U.S." is a one-shot variance and only because of constant bickering about that one initialism. What changed (in order) was that "U.S." stopped being mandatory in US English articles something like a decade ago (but was to be left alone if already used), then stopped being mandatory to never change in a US English article that already used it (i.e., it became desirable to normalize "US" to match "UK", etc., if present) a couple of years ago, finally to "US" being actively favored for MOS:COMMONALITY reasons. It strikes me that the RfC isn't even covering that version; I should probably add it for completeness since it was the most recent. I was so used to the version I listed as "current" that I didn't even notice.  — SMcCandlish ¢ 😼  10:54, 6 July 2018 (UTC)
"permissible exception" ... "only because of constant bickering about that one initialism". Wow. To frame this in that way. Wow.-- Netoholic @ 12:05, 6 July 2018 (UTC)
Clearly demonstrable; just read the past discussions [18]. You'll find a marked lack of drama and demands for, say, "U.K." or "N.A.T.O." or "M.S.-D.O.S." Only for "U.S.", and perpetually strident, grounded in a mixture of traditionalism-based emotion and claims that it's the dominant style in US writing, a notion that's been conclusively disproved.  — SMcCandlish ¢ 😼  03:54, 8 July 2018 (UTC)
Derp. I actually did have the 17th ed. in the original source dump, but mislabeled it 16th. Sorry for the duplicate cite, folks.  — SMcCandlish ¢ 😼  11:42, 6 July 2018 (UTC)
  • @MapReader: Yes, CNN.com (accessed from a US IP address) consistently uses "US" both in headlines and in running prose. As for "USA", I'm not really sure why MoS is against that TLA. It predates my arrival on the scene in 2005, I think. Arguments I recall are: 1) it's redundant, since US is shorter; 2) it's not normal US English except in particular circumstances (i.e., it's largely an exonym imposed on the US, like referring to all of the Netherlands as Holland, or trying to tell de.wikipedia.org to rename their München article to Munich. 3) it's ambiguous, because it's the standard acronym of the United States Army (though for most purposes the ambiguity runs the other direction; WP shouldn't refer to the US Army as "USA" except in a reference in its' own main article's lead as a MOS:BOLDSYN). There were probably others.  — SMcCandlish ¢ 😼  11:37, 6 July 2018 (UTC)
    @AfroThundr3007730: CNN's not even long-term consistent on "use U.S. in headlines", and appears to have abandoned it cmopletely without revising old articles. "U.S." appears to have been their traditional style several years ago. All the new material appears to use "US" throughout, headlines and all. Every recent (like this week) article with the abbreviation in a headline uses "US" so far as I can see: [19], [20], [21], [22], etc. I'm reaching these via an American IP address, and have "Set edition preference: US" (at page bottom). However, cnn.com uses "U.S." in its menu system [23]. This seems to be a conflict between their editorial department and the IT/e-content people running the website (who may really be some company of contractors).  — SMcCandlish ¢ 😼  01:05, 7 July 2018 (UTC)
  • So what is clear is that is not clear cut...... so best to leave this up to editor discretion at each article.--Moxy (talk) 11:56, 6 July 2018 (UTC)
    @Moxy: I don't follow your reasoning. We know for a fact that some people do acronyms in "ABC" form, and others use "A.B.C." form. MoS settled on ABC form, to match the majority of style guides and other real-world usage. A single exception was carved out, "U.S.", on the basis that it was a dominant, special, usage in the United States. Source research 16 or so years later disproves the rationale for the exception; it's no longer dominant, and US style guides are turning directly against it. So, why – for that acronym alone – would losing "special" status amount to "do what you like, article by article" rather than "do what MOS:ABBR says" like all other initialisms? Especially after multiple consensus discussions conclude in favor of "US"?  — SMcCandlish ¢ 😼  12:15, 6 July 2018 (UTC)
    Not sure how realistic it is to suggest that 'USA' is an imposed exonym, given its regular chanting by US sports fans at pretty much any international sporting event? MapReader (talk) 15:33, 6 July 2018 (UTC)
    Sure. It's not my argument, just one I've encountered in various forms. The reasoning basically seems to be along these lines: "Most Americans and American publishers don't use that; it's an old-fashioned thing that we retain in a few stock phrases and some special circumstances, but it's not general usage. Non-Americans using it is like Americans insisting that Thailand still be called Siam." I'm not sure I buy it either, but the viewpoint exists. PS: The sports codes are set by the sport governing bodies like IOC and FIFA. They're also abbreviated noun phrases (USA for the entire country name with "of America"). This might be an argument to use "USA" in such a grammatical circumstance: "China's relations with the USA" versus "US interference in China's markets". But style guides mostly suggest using a non-acronym: "China's relations with the United States", and a US/USA rule would be fiddly and widely ignored.  — SMcCandlish ¢ 😼  20:18, 6 July 2018 (UTC)
  • @Blueboar and Tryptofish: US-politics-related shenanigans for this last round of squabbling may be behind it, ultimately, in that this seems to have been sparked by an AWB spree to force "US" widely (I haven't tried to track down the rationale, if any, provided for that). But the RfC demander's concerns are way broader, and seem to actually be grounded in a Canadian demand to use "P.E.I." for Prince Edward Island (though that's not the .ca postal code for it, and we don't normally abbreviate such things except in tables anyway).

    History-wise (and without getting into dramaboard-style diffs), what I see is a bold change (mine) led to a long consensus discussion last year. The resulting version (refined from bold one) was stable after that. No one seemed to care. An editor, irked by a mass change to "enforce" that version (which should have been taken to ANI as a WP:MEATBOT matter) showed up and boldly started rewriting it radically without discussion; someone reverted that; rewriter then tit-for-tat reverted to an older version closer to their preferences. Only one editor appears to have edit-warred and short of 3RR, just 2, to get rid of the newest of these three drafts, after someone already objected to their removal the first time. Only then did discussion ensue, but with the revising bold editor complaining about how bold the previous version was (even though it was really the product of a consensus discussion), and wanting an RfC. But then that discussion turned circular with extraneous stuff that's basically a challenge to the existence of MOS:ABBR. I opened the RfC on the narrower question, since we generally don't nuke entire guideline pages.

    The one who wanted the RfC is upset that their particular (basically off-topic) issues aren't addressed by the RfC but I don't think they can be. The way to try to get rid of WP having a preference for "UNESCO on HIV/AIDS in the UK" style, to permit "U.N.E.S.C.O. on H.I.V./A.I.D.S. in the U.K.", is to have a separate RfC about a major change to MOS:ABBR. And such an RfC would fly about as far as a lead dirigible.
     — SMcCandlish ¢ 😼  23:53, 6 July 2018 (UTC)

    • Again, my take on all of this is that arguing and edit warring about dots is disruptive... and I think we agree on that. However, I think we disagree on the solution. Your solution seems to be: let’s iron this out and make a rule. My take is that trying to make a rule is what has CAUSED most of the disruption. My feeling is that if some editors want to write “U.S.” or “P.E.I.” (or even U.N.E.S.C.O.) ... let them. As long as they are consistent WITHIN any given article, most readers won’t even blink. Trying to formulate a site wide rule on this has ended created MORE disruption than being flexible would cause. So, my solution is: Don’t have a firm rule... say that both forms are allowed. Intentionally devolve the choice to the article level. And if editors edit war ... call them to the carpet for EDIT WARRING, not for violating the style rules. Blueboar (talk) 12:36, 7 July 2018 (UTC)
      I am pretty sure a lot of editors would blink if some started spelling out acronyms like UNESCO and UNICEF with lots of dots! MapReader (talk) 14:01, 7 July 2018 (UTC)
      Or even U.K., U.A.E., and U.S.S.R., for those who like to draw a distinction between word acronyms and initialisms.  — SMcCandlish ¢ 😼  04:06, 8 July 2018 (UTC)
    • The U.N.E.S.C.O. and H.I.V. thing is a strawman/red herring used to throw silliness into the mix, to discredit the opposition. No one is suggesting going to that here. The area of concern is not about organizations or other initialisms but with regards to geographical names only, which are dotted often because you are mixing multi-word name acronyms with single-word name shortenings like listing Canadian provinces P.E.I., Sask., Man., B.C., and such. -- Netoholic @ 16:43, 7 July 2018 (UTC)
      That doesn't make any sense. "Prince Edward Island" and "British Columbia" are multi-word, exactly like the expansions of UNESCO and HIV. If you don't like the UNESCO example because it's a "word acronym" pronounced as a word instead of a series of letter, try HIV, as well as FBI, CIA, GDR, USSR, and a million others. It simply is not contemporary style to write these with dots in them. "U.S." has lingered longer in that form, but it's not the dominant style even the US today; we have no reason to make a "magically special" exception for it. There is no away around this. I don't need to "discredit" you; your traditionalism-based argument simply doesn't stand up. The fact that you can find a couple of style guides that still permit this use is irrelevant; they don't recommend it, and even if they did, they'd still be a minority. "U.S." in North American English simply doesn't rise to the level of national style as, say, colour versus color in British English. No amount of wishing that it were an ENGVAR matter will make it one. If WP had been around in 1983, you would have had an actual case to make. Times change and languages change with them.  — SMcCandlish ¢ 😼  04:04, 8 July 2018 (UTC)
  • @Hawkeye7: What media reports touting WP's supposed anti-US bias? How can that possibly square with WP being massively dominated by US editors, and the principal complaint about our coverage being that it's heavily US-centric (and Western-centric, and male-centric, and liberal/progressive-centric)? And how could using a consistent "US and UK" spelling be "anti-US bias" when major American publishers and style guides also use "US"?  — SMcCandlish ¢ 😼  03:50, 8 July 2018 (UTC)
    Last time round it was over our acceptance of non-US spellings. WP is not dominated by US editors; WMF is. During the Paralympic Games we gathered a lot of statistics on who was editing and where, and while six of the top ten articles by edits were the country-at-the-Paralympics articles, the US did not figure, demonstrating that US editors were actually a minority. I thought I was agreeing with you on this one. Hawkeye7 (discuss) 04:14, 8 July 2018 (UTC)
  • Retain guideline ... but also provide correct information. (1) "US has become the dominant abbreviation for United States." "Dominant"? This is an opinion without substantiation. (2) What's attributed to The Chicago Manual of Style should be revised. The CMS does not deprecate ""U.S." and recommends "US"." What CMS actually says is:

Chicago style is USA (without periods), but we also accept both US and U.S. Other authoritative style manuals and dictionaries vary in their recommendations.

If a style manual is going to be referenced in WP:MOS, it should be referenced correctly. Neutral wording is best when the subject is not conclusive. Pyxis Solitary 09:51, 8 July 2018 (UTC)
No page or section cited. Where are you getting this from? The wording you're giving simply doesn't appear. I've quoted in complete relevant text with section numbers (which are consistent between print and electronic editions) of all the applicable material from CMoS 17, and will do so again below. You appear to actually be quoting staff blog material from ChicagoManualOfStyle.org, specifically copy-pasting from this page; the cross-references it provides (§§ 10.4 and 10.33) do not say what that post says they do, and I've quoted what they actually say verbatim, below. I.e., the website material is contradicting the actual book; the post appears to have been unrevised from the 15th edition (since the 16th says what the 17th does, except, as noted below, in one spot). Their forum even indicates complaints that the book doesn't address "USA/U.S.A." (see second entry here).

Here's what the book actually says:

10.4 Periods with abbreviations.
...
3. Use no periods with abbreviations that include two or more capital letters, even if the abbreviation also includes lowercase latters: VP, CEO, MA, MD, PhD, U, US, NY, IL.
4. In publications using traditional state abbreviations, use periods to abbreviate United States and its states and territories: U.S., N.Y., Ill. Note, however, that Chicago recommends using the two-letter postal codes (and therefore US) wherever abbreviations are used....
...
10.27 Abbreviations for US states and territories. In running text, the names of states, territories, and possessions of the United States should always be spelled out when standing alone and preferably (except for DC) when following the name of a city.... In bibliographies, tabular matter, lists, and mailing addresses, they are usually abbreviated. In all such contexts, Chicago prefers the two-letter postal codes to the convention abbreviations. Note that if traditional bbreviations must be used, some terms may not be subject to abbreviation. [... A table is follows illustrating the difference, with examples like NE versus Neb. or Nebr., and showing not to abbreviate short ones like Ohio in the latter style, only in the postal code style, OH.]...
10.28 Abbreviations for Canadian provinces and territories. ... may be abbreviated in bibliographies and the like—using the two-letter postal abbreviations, which have the advantage of applying to both the English and French forms. AB [=] Alberta; ... PE [=] Prince Edward Island ....
...
10.31 Abbreviating country names. ... Certain initialisms, on the other hand [i.e., in lieu of spelled-out names], may be appropriate in regular text, especially after the full form has been established.... UAE (United Arab Emirates), US, UK, GDR ....
...
10.32 "US" versus "United States." ... Note that, as a matter of editorial tradition, this manual has long advised spelling out United States as a noun, reserving US for the adjective form only (where it is preferred) and for tabular matter and the like. In a departure [i.e., from the 16th ed.], Chicago now permits the use of US as a noun, subject to editorial discretion and provided the meaning is clear from context. US dollars; US involvement in China; China's involvement in the United States or China's involvement in the US.
...
10.33 Mailing addresses—postal versus standard abbreviations. Standard abbreviations preferred by the US Postal Service (first column) are in all caps and do not use periods; these forms are most appropriate for mailing addresses. In tabular matter and the like, Chago prefers the form of abbreviations presented in the second column. ... In running text, spell out rather than abbreviate. [... Table provides examples, e.g. AVE versus Ave., BLDG vs. Bldg.; none of these pertain to placename abbreviations like US or PEI.]

— The Chicago Manual of Style, 17th ed. (2017), University of Chicago Press, ISBN: 9780226287058
This is the same advice as in the 16th ed. (2010), aside from a few copyediting tweaks, and the new "In a departure" note, quoted above.

PS: The dominance of "US" isn't "unsubstantiated"; see #RS citations above. If you want to prove a counter-claim, Pyxis Solitary, you have a tremendous amount of sourcing to do, with works somehow more authoritative than those already cited; I don't see how that could even be possible.
 — SMcCandlish ¢ 😼  00:17, 9 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────

  1. Why did you edit my comment? Why did you alter my comment by removing the quote frame? Where in WP:TALK does it say that a quote box is discouraged or is not appropriate?
  2. What do you mean "Where are you getting this from?" Click on the CMS FAQ link I included when I quoted CMS and you'll see it.
  3. You quote the CMS publication as if everyone has a copy of the book. I'm not going to buy one just to double-check that what you're quoting is precisely what appears in it. Provide a link to those sections. It's not available online? Then I take what you've posted with a grain of salt.
  4. "the post appears to have been unrevised from the 15th edition (since the 16th says what the 17th does, except, as noted below, in one spot)". Scroll down to the bottom of the webpage I cited and you will see: "The Chicago Manual of Style 17th edition text © 2017 by The University of Chicago. The Chicago Manual of Style 16th edition text © 2010 by The University of Chicago. The Chicago Manual of Style Online © 2006, 2007, 2010, 2017 by The University of Chicago." That's what CMS has published — that's what CMS says.
  5. You are trying to push your position down everyone's throat. Provide a reliable source that can be verified by everyone. When it comes to MOS, quoted content from a book that many if not most Jane and John Does don't have at their disposal is insufficient validation.
  6. Life is short, and since you took it upon yourself to lord over my original comment ... this is the last time I am going to respond to this topic. Shame on you. Pyxis Solitary 12:06, 9 July 2018 (UTC)
Generally speaking, we trust editors to be honest about quotations. Complete? Well, maybe not always. But honest about the parts that they type. We do this partly because we're fond of WP:AGF, but also experience has shown that that experienced editors are reasonably smart about their self-interests, at least to the extent of not wanting to get caught in an outright lie. You might not personally happen to have a copy of CMOS at hand, but plenty of other editors do. WhatamIdoing (talk) 22:08, 10 July 2018 (UTC)
And can you imagine me of all people lying about the content of a style guide, when half the people I argue with have the style guide? LOL. I would have be possessed by Donald Trump to do that. >;-)  — SMcCandlish ¢ 😼  18:33, 15 July 2018 (UTC)
I think this all demonstrates that CMOS is not consistent on the issue, as the website FAQ doesn't match the printed book. This could mean that either is wrong, or that there has been a change since the publication of the book. I don't think it matters which is which - either its inconsistent or wrong - neither of which point to a reliable source on the matter. -- Netoholic @ 03:13, 13 July 2018 (UTC)
  • Does it really matter what CMOS says? We are not bound by the CMOS. Sure, it is nice when our guidance is in sync with what other style guides say, but ultimately our guidance is based on our own internal consensus. That consensus currently seems to be to allow both “U.S.” and “US” (but whichever is used, be consistent within an article). This is supported by actual practice at the article level (whenever there are undiscussed attempts to change from one to the other, they are quickly reverted... and it goes both ways). Blueboar (talk) 13:56, 15 July 2018 (UTC)
    It is just one source among many, though a high-quality one on this particular micro-topic  — SMcCandlish ¢ 😼  18:36, 15 July 2018 (UTC)
To take these in numbered series:
  0. Why are you picking fights about talk page trivia, and pretending people who disagree with you are dishonest? No one cares about the former or will buy the latter.
  1. I didn't edit your comment, I editing the disruptively obnoxious framing around it. Your posts are not magically more important than everyone else's that they need to draw attention to themselves with huge visual gimmicks. The talk page guideline permits refactoring of this sort. Taking a "There's not a rule against what I want to do" approach is wikilawyering. It doesn't mean "I can do it no matter what and no one can stop me." Other editors are permitted to refactor within reason. You do not own a talk page you post to, not even your user talk page.
  2. It's called a rhetorical question, which is obvious, since I answered it myself in the sentence that followed.
  3. That's a serious failure to assume good faith. See also Verifiability policy: No one has to buy a source for you, and sources being available online for free is not required. You also seem to be unaware that discretionary sanctions apply to style/titles-related policy discussions, especially with regard to casting aspersions without evidence or otherwise excessively personalizing such disputes.
  4. You're sorely confused about what The Chicago Manual of Style is. It's a book, available in paper and (for a fee) online, with identical text. The webpage you cited is not the CMS or part of it, it's part of the staff-written Q&A blog materials about the CMS, at the CMS website. You also don't seem to understand that a copyright notice applied by a script to an entire website has nothing to do with the last time the content in a page on that website was substantively updated. "That's what CMS has published" is not a sensible statement. The CMS is a publication. The publisher is the University of Chicago Press (also the publisher of the website). It's like mistaking The Magical Mystery Tour for Apple Records, or confusing Game of Thrones with HBO. "That's what CMS says" is a demonstrably incorrect statement, though I ascribe this to the above-mentioned confusions, not to any intent to deceive. You actually do appear to believe what you're saying, despite all evidence presented to you that you've erred.
  5. Source already provided. If you don't want to buy the book, get it from interlibrary loan for free, or just look at a copy in your local bookstore. Or just ask anyone else here who has a copy to look for you. Providing sources and challenging false statements isn't pushing anything down anyone's throats, it's providing sources and challenging false statements. It's much of what we do all day every day here.
  6. Yes, life is short. See point 0, above.
 — SMcCandlish ¢ 😼  18:33, 15 July 2018 (UTC)
Off-topic.  — SMcCandlish ¢ 😼  05:35, 16 July 2018 (UTC)
  • I said I would not respond to this topic again. And I'm not.
    However, this thinly-veiled attempt by SMcCandlish to intimidate me in response to my 9 July 2018 comment in this discussion is a form of harassment. I've responded to this misbehavior on my talk page.
    I suggest that this discussion be closed until another editor that is not so obviously personally vested in the subject creates a new but similar topic. Pyxis Solitary 04:49, 16 July 2018 (UTC)
    I'm not sure what to make of a "this is the last time I am going to respond" statement followed by a response that says it's not a response and reminds us there will be no response then also points us to another response in user talk. That seems very unclear on the concept of not responding

    A {{Ds/alert}} template is not a threat or intimidation, or anything like WP:Harassment. This template (and this template only, without modification) is required by ArbCom to be delivered (not more frequently than once per year) to anyone whose editing seem to indicate they are unaware of the discretionary sanctions (DS) that apply to that particular topic area. It is awareness notice, not a threat or an accusation. I made it very clear when posting it that it had nothing to do with any action I would take myself. Per your request, I have closed this discussion, since it is off-topic anyway.

    If you don't like the template and its wording, see fortuitously ongoing discussion at Template talk:Ds about revising it. If you don't think these templates should be necessary but that DS should still apply, try raising this at WT:ARBCOM. I have tried several times to get rid of this bureaucracy, but ArbCom always refuses or ignores. If you don't think DS should apply to MoS at all, join the club. I tried to have them removed about two weeks ago and ArbCom unanimously refused. We're stuck with it, at least for now. If you have an issue with me personally, use User talk:SMcCandlish; it's what user talk pages are for, not what Village Pump is for. If you plan to respond with grandstanding of this sort every time someones leaves you a procedural notice in user talk, you're going to find that will not go over well.
     — SMcCandlish ¢ 😼  05:35, 16 July 2018 (UTC)

(1)You are in no position to deliver an ArbCom notice to me about my 9 July 2018 comment -- specially since you're so emotionally involved.
(2) "Per your request, I have closed this discussion. You know very well that the "discussion" is the topic, not my comment. Pyxis Solitary 06:58, 16 July 2018 (UTC)

Comment: How about avoiding U.S: and UK altogether? We can easily write United States and United Kingdom without wasting ink. --NaBUru38 (talk) 02:27, 16 July 2018 (UTC)

Doing this is what most style guides recommend, at least for noun usage ("Relations between Canada and the United States") but many like the abbreviation for adjectival cases ("US sanctions on Cuba"). Chicago Manual, weirdly (given its traditionalism) has now started "permitting" the abbreviation in noun use, as do the journalism style guides. Real-world usage isn't consistent. I think people will object that always having to use "United States" (and thus probably also "United Kingdom") will be onerous and pedantic. Even among those who don't mind it in running text, we'd still have the issue tables and other circumstances where the short form would often be desirable.  — SMcCandlish ¢ 😼  05:35, 16 July 2018 (UTC)

WP:DESIST

In doing category cleanup, I found Wikipedia:Desist categorized in Category:Wikipedia behavioral guidelines. I've put {{Essay}} on it and moved it to Category:Wikipedia behavioral essays.  — SMcCandlish ¢ 😼  03:30, 8 July 2018 (UTC)

Good move. Beeblebrox (talk) 06:58, 8 July 2018 (UTC)

ArbCom wants the community to come up with infobox inclusion criteria

FYI: Pointer to relevant discussion elsewhere.

Please see: Wikipedia talk:Manual of Style/Infoboxes § ArbCom wants there to be an RfC and the drafting of infobox inclusion criteria

Short version: In two RFARBs, the Arbitration Committee has said that it can't/won't resolve the perpetual "infobox warring" problem, because this is a content and policy decision that the community has to make. We've been asked repeatedly by ArbCom to develop inclusion criteria for infoboxes so that "The use of infoboxes is neither required nor prohibited for any article" does more than resolve (or devolve) to "fight about it endlessly article by article and category by category". But this has yet to happen, and it won't be easy.

The discussion now open isn't an RfC for !voting, but a place to discuss drafting such criteria for eventual RfCing at Village Pump. SMcCandlish (talk-contribs) 02:32, 9 July 2018 (UTC)

This discussion has been a long time coming and, though it is going to see some vigorous debate no matter what we do (due to this being the perennial battleground between two highly entrenched groups of editors who have litigated the matter repeatedly across numerous articles and tend to show up together en masse) I think we can nevertheless mitigate the tension somewhat by organizing a shortlist of options here. I agree with SMcCandlish that the status quo is not working, and hasn't ever since the inception of the "Infobox wars", if we're to use the somewhat (but not completely) hyperbolic term for this roving battle of wills. So, while I don't favour a one-size-fits-all approach here, I do think that we need a shift towards presumptive inclusion of presumptive disclusion, even if the ultimate guideline ends up being quasi-precatory. That could either be a blanket presumption or inclusion or disclusion for all non-list and non-disambig pages in mainspace, or else a set of presumptions that vary across a selection of articles types (BLPs, historical biographies, geographical entries, taxonomical articles, abstract concepts, works of music, works of literature, ect, ect.).
I know I am going to make myself the least favourite person of one of the afore-mentioned groups either way here, so I am just going to make a call here as to what I expect the general opinion to be amongst the editing corps broadly: I think that most editors are going to err on the side of inclusion either as a general rule or at least for most particular categories. I think the anti-infobox stalwarts, while represented by an active, vocal, and well-organized (by which I mean both their arguments and their propensity for moving together) group of editors, are a minority in the larger Wikipedia population. I think that the utility of infoboxes is largely presumed by the average editor; I won't belabour the reasons in detail, but will try to summarize the arguments I have most often seen asserted in the past by the pro-infobox camp (augmented by my own perspectives):
  • 1) The utilitarian-for-the-reader argument that an infobox serves as a useful encapsulation of vital information which the reader can access at a glance, which (if wisely considered) may actually address the needs which brought a significant number of readers to the article in the first place and which, in all other cases, helps summarize and frame the rest of the article.
  • 2) The utilitarian-for-the-project argument that infoboxes, owing to their consistent and constrained syntax, are incredibly useful to the encyclopedia, to the project, to other Wikimedia movement projects, to analytics researchers, and to other individuals and entities looking to leverage our information for pragmatic purposes. This owing to the fact that the inofbox allows for bot activity and other machine processing and learning mechanisms to extract data in an organized fashion and to analyze, relate, and index both the data itself and the articles they are found on, in a myriad of useful ways. These technical applications are so varied and complex that they go well beyond my ability to effectively summarize here, so I will leave that exhausting task to those who work in these areas (both on project and off, and as part of the broader Wikimedia movement and external to it). But I can say as much as this with confidence and without exaggeration: the applications are myriad and substantial for both research and practical purposes.
  • 3) The style and consistency argument, which has various iterations but which I believe can be boiled down to two inter-related points: A) There is a value in preserving a default approach across Wikipedia's articles (or at least articles within a given vein) and that since most Wikipedia articles already employ an infobox, it is easier to default to this approach, and B) The infobox has become a staple of Wikipedia style and their absence in most categories of article is noticed and disliked by most readers. Needless to say, I think that (even if we assume these assumptions to be true, which is a bit of an if) this third category of argument is by the far the weakest of the three which advocate for a default inclusion approach. But not entirely irrelevant.
Now, having detailed those pro arguments, I don't want to give short-shrift to the anti-infobox perspective, but I fear I have to, for one simple reason: I've never (despite getting RfC'd to a contentious infobox discussion a few times a year since forever) entirely understood the deeply held conviction of a minority of editors that the "Idiot box" is unnecessary and ungainly. While I can't say for a certainty that the trend always holds, my experience has been that the objection to Infoboxes usually boils down to aesthetics--the infobox is said to not look very much like what you would find in a traditional encyclopedia. I don't know if that's necessarily true (I certainly saw very similar templates in some encylopdias when growing up before electronic versions were a reality) and more importantly, I'm not sure if that is a compelling argument anyway: Wikipedia is WP:NOTPAPER after-all. It is worth noting that not every anti-infobox advocate is an absolutist: some simply want the parameters utilized in a box kept to a minimum, and in this respect, I can definitely agree: most IBs to tend to contain excessive detail, and the fields chosen for inclusion can be arbitrary and perplexing at times. If am doing a disservice to the anti-infobox/default-to-non-inclusion advocates and/or have forgotten any obvious pragmatic arguments for their preferred approach, I am sure they will provide a detailed rebuttal, but those are the major categories of argument which I can recall from both sides, in any event.
I think (and I suppose this central discussion will either confirm or refute) that most editors fall somewhere on the inclusion/lean-towards-inclusion spectrum for one of the above three general reasons. But I do think we need to be careful about locking ourselves into binary thinking: there may be alternative, more nuanced, and/or middle-ground approaches out there that have not been widely considered in the past. I personally lean towards a hybrid of the two possibilities I discussed at the opening of my comments here: 1) create a general guideline that presumes inclusion for most articles, but allow it to be rebuttable, and 2) create a more nuanced set of topic-specific guidelines that discuss the policy calculus for each--though I expect most of these, reflecting community consensus, will err towards inclusion too, though probably not all. I do think its important that, even if we do diversify the analysis some, the guidelines should probably be kept in one centralized policy or MoS space. That's about all I can think to say by way of introduction. Except maybe, I recommend buckling your metaphorical seatbelts on this one. Strong (but hopefully fully civil) opinions most certainly incoming. Snow let's rap 12:50, 13 July 2018 (UTC)

Use of copyrighted material undergoing active license negotiation

What does Wikipedia policy say with regards to publishing verbatim government documents whose copyright is under active negotiation? The article Towrang Convict Stockade makes use of Australian government documents, one of which was published under a copyright held by the Roads and Traffic Authority of New South Wales. That agency was covered by an agreement with the Copyright Agency for the use of content in reliance on the government statutory licence until 30 June 2012. However, an agreement with NSW government agencies is currently under negotiation. That would seem to preclude the usage of copyrighted material published by the Roads and Traffic Authority of NSW, under which the document in question was published. Any input on this question would be greatly appreciated.
References

 spintendo  08:27, 9 July 2018 (UTC)

@Spintendo: You seem to be a bit confused. This article uses CC-BY licensed material from the New South Wales Office of Environment and Heritage. The Berger document is a referenced source, not something whose text is actually used in this article. No copyrighted material from the Roads and Traffic Authority is used in this article. The copyright status of a referenced source is completely irrelevant - one would expect that it, like most other sources, would be copyrighted. The Office of Environment and Heritage material is released under CC-BY 4.0. A private business claiming that they have been "in negotiation" to manage copyright for government organisations since 2012 doesn't change the fact that many, many government departments have decided to instead release material under free licenses during that time. The Drover's Wife (talk) 08:37, 9 July 2018 (UTC)
@The Drover's Wife:"The Berger document is a referenced source, not something whose text is actually used in this article." If saying it only made it so. Unfortunately, I believe you may be the one that is confused, as large amounts of text from the Berger document are used in the article, as shown below:
Comparison of texts
Text as it appears in the Wikipedia article
Towrang Convict Stockade
Text as it appears in the
Berger Source Material
It is certainly believed to have had the largest concentration of convicts in southern NSW during the period of its operation. The convicts were guarded by soldiers of various British regiments, including the 28th, 31st, 51st and 80th. The first commander of the stockade was Captain J. Darley (1833 to 1836), followed by Lieutenant R. Waddy (1836-39), Lieutenant R. Sherberras (1839), Captain W. Houghton Tyssen (1841), Lieutenant W. Cookson (1842) and in 1843, the last year of the stockade's operation, Lieutenant Owen Gorman. The stockade is believed to have consisted of a small cottage and a number of huts for the soldiers and their families, together with a garden tended by the military, and huts and boxes or timber cells about 4m square for the convicts further down the Wollondilly River. Towrang was the largest concentration of convicts in southern New South Wales at this time. The convicts were guarded by soldiers of various British regiments, including the 28th, 31st, 51st and 80th. The first commander of the stockade was Captain J. Darley (1833 to 1836), followed by Lieutenant R. Waddy (1836-39), Lieutenant R. Sherberras (1839), Captain W. Houghton Tyssen (1841), Lieutenant W. Cookson (1842) and in 1843, the last year of the stockade's operation, Lieutenant Owen Gorman. The stockade consisted of a small cottage and a number of huts for the soldiers and their families, together with a garden tended by the military, and huts and boxes or timber cells about 4m square for the convicts.
You've just stated that text from the Berger document has not been used in the article. If that is the case, can you explain how the text above was placed exactly where you said it wasn't?  spintendo  22:14, 9 July 2018 (UTC)
@Spintendo: I should point out that the Berger source is also CC-BY-3.0 licensed. As I said above: a private business claiming that they have been "in negotiation" to manage copyright for government organisations since 2012 doesn't change the fact that many, many government departments have decided to instead release material under free licenses during that time. The Copyright Agency is a business - it has no special standing, and its desire to get back the cushy government contracts it had prior to 2012 has no legal bearing on the decisions of government departments in New South Wales and around the country to not assign management of their material to them, and instead release their material under free licenses. The Drover's Wife (talk) 22:27, 9 July 2018 (UTC)
"Many government departments have decided." You must have copy then of exactly which govt departments those are, and the one specifically from RTA which states its texts are available under that license. And if that is the case, would you like to redact your earlier statement, or is it still your assertion that there is no Berger text used in the article?  spintendo  22:39, 9 July 2018 (UTC)
@Spintendo:, your own link tells you that the Berger document is CC-BY-SA 3.0 licensed. I previously pointed out the Office of Environment and Heritage material is released under CC-BY 4.0. The Drover's Wife (talk) 22:44, 9 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────(edit conflict) Spintendo, The Drover's Wife, you might get more input on this if you moved it to WT:CP. But just quickly: if the Berger source is compatibly licenced and the article includes content copied from it, then attribution is required, similar to that already in place for the Office of Environment and Heritage content. That's easily provided, and perhaps is all that's needed (please note, I haven't looked in detail). Justlettersandnumbers (talk) 22:59, 9 July 2018 (UTC)

Correct. I was not aware that one freely-licensed source had closely paraphrased another freely-licensed source - that is easily remedied. But this stuff about The Copyright Agency is rubbish. The Drover's Wife (talk) 23:03, 9 July 2018 (UTC)

Search Box Filtering?

Wikipedia is one of the most useful sites on the Internet. Even so, if it is going to be used everywhere, it needs to apply some filtering to the search box, so topics that are widely viewed as offensive do not inadvertently appear because they contain the same first two or three letters as the search target. Specifically, while using the big screen where displaying pornography is inappropriate, a search for "Alternator" caused an inappropriate image describing "Alt Porn" to appear. It would be seem to be more sensible remove pornography from the look-ahead function so only a deliberate search will find and display it, and to do likewise with other widely-offensive topics. — Preceding unsigned comment added by 198.208.47.94 (talk) 19:04, 9 July 2018 (UTC)

Hi 198.208.47.94. The kind of people who volunteer as unpaid encyclopedia-writers tend to have a strong ethos in favor of freely and openly sharing information. We are also have a primary mission of writing articles as neutrally and impartially as we can. As an open project, we have diverse people from every corner of the planet, with diverse views on controversial topics. We have by necessity developed a rather strong taboo against subjectively imposing individual opinions and passing judgement on anything controversial or culturally-subjective. We have a policy that Wikipedia is not censored. We write educational content, and we firmly decline to pass judgement on which articles or which images some people might consider "offensive". No two people will ever agree on what should or shouldn't be filtered, especially when we serve every country on earth. Some people find images of Muhammad offensive, some people want images in the breast cancer article filtered, some people want bikinis&speedos filtered, someone wanted to filter any image of a woman not wearing a burka, as well as of a million other topics and social-standards. We do not frivolously include potentially offensive content, but we do not apply culturally subjective standards to exclude or hide educational content which some people might find offensive.
The only way that we will avoid displaying "offensive" search images is if we shut off all images from search results. In fact when images were first being added to the search results, I personally raised the concern that maybe we shouldn't do it at all. I foresaw exactly your objection, that you saw images from some random article you weren't looking for. However it was decided that having images in search results was a valuable feature, that it was worth having those images even if it meant some people would occasionally come across something they dislike.
I hope you can at least partially understand and respect that we deliberately-avoid imposing a subjective and cultural judgment on what kind of educational content you can find on Wikipedia. We hope that our dedication to broad and uncensored topic coverage makes up for any unwanted content you accidentally come across. Alsee (talk) 21:37, 9 July 2018 (UTC)
Help:Options to hide an image may be of some use. Gråbergs Gråa Sång (talk) 11:53, 10 July 2018 (UTC)

MOS:WTW addition RfC Terms that can introduce bias

FYI: pointer to relevant discussion elsewhere.

Please see Wikipedia talk:Manual of Style/Words to watch#RfC Terms that can introduce bias

Gist: Should we add a class of "Terms that can introduce bias", listing incorrect use of Arab and Arabic as an examplar? Batternut (talk) 10:44, 10 July 2018 (UTC)

Should the "In wrestling" section be removed from professional wrestling articles?

The "In wrestling" section has been a standard part of professional wrestling biographies for over a decade. It covers mostly character information in a bulleted list format. On May 24, 2018, an editor raised an issue with the section's vague heading to WikiProject Professional wrestling (see WT:PW#In wrestling). The next day, renaming the heading to "Professional wrestling highlights" and adjusting "Championships and accomplishments" into a subsection beneath it was proposed. On June 3, it was considered to have reached consensus after the 5 participants agreed unanimously. In the weeks that followed, a few editors disapproved of the new heading, as well as "Championships and accomplishments" being turned into a subsection. On June 24, clarification of which heading to go forward with was requested, where an additional option to remove the section entirely was proposed. On June 28, the discussion was closed after 10 editors participated, with an "overwhelming consensus" to remove the section but rework any content deemed significant into prose, potentially into a "Professional wrestling persona" section (see WT:PW#Trying to gain clarity (closed)). The changes were immediately enacted into hundreds of articles, causing news of the changes to be spread onto online professional wrestling communities. Many new editors voiced frustration over the removal, with some reverting the changes.

Below is the style recommendations for this section, taken from WikiProject Professional wrestling prior to its removal:

"In wrestling" recommendations per WP:PW/SG

An overview of notable character information is compiled in a bulleted list format. This initial section should be limited to finishing moves, signature moves, managers (and/or wrestlers managed), nicknames, entrance themes, and wrestlers trained. Any taunts, gestures, or other descriptions are better suited for the article prose.

Example of highlights list
  • All items should be sorted alphabetically. An exception is with entrance themes, which can be sorted chronologically if date ranges are sourced.
  • For signature and finishing moves, there must be one reliable source explicitly mentioning that it is a signature move of the wrestler. One reliable source merely mentioning that the wrestler performed the move is not enough.
  • A specially named move should be italicized, with the regular name following in parentheses and wiki-linked.
  • {{Cite episode}} should not be used for citing moves as commentators often call moves wrong or do not give full technical names, leading to speculation.
  • Track names in entrance themes should not be wiki-linked to articles about the compilation albums on which they are sold, unless the article contains further information on the track itself (not just name, number, and wrestler who used it).

This proposal seeks to remove the "In wrestling" section, with the possibility of any of its content that is deemed significant to be contextualized in prose. Much of the information contained within this section would be lost. The content most likely to be reworked is certain Finishing moves, Nicknames and Wrestlers trained. As it stands, Managers are already expected to be covered in prose, primarily in the "Professional wrestling career" section. If necessary, reworked content can be placed within the existing "Professional wrestling persona" section (see WP:PW/SG#Professional wrestling persona).

Below are diffs from various articles, showing before the section's removal, after the removal, and some with content reworked to prose:

Proposal: Should we adopt a default approach of omitting the bulleted list "In wrestling" section, in favor of its notable content being contextualized in prose when appropriate? Prefall 14:53, 10 July 2018 (UTC)

Survey

  • Yes To reiterate my comments from the original discussion, this has long been the most problematic section in professional wrestling biographies, even more so than "career". It is a magnet for cruft, with a majority of edits coming from new or inexperienced users. It has devolved into a database of items ever associated with the wrestler, often poorly sourced at best or outright original research at worst. Even when "properly" maintained, the content itself is mostly trivial, adding very little to the understanding of the subject. Any significant material from this section can be framed more effectively in prose, alongside any additional character or performance information. Prefall 14:54, 10 July 2018 (UTC)
  • Yes Looking at the examples you included, the page is much more encyclopedic. List a number of moves which someone has done has no value. The way it was reworked to explain the basis behind it and put it into context is a much more encyclopedia appropriate way to discuss the identical information. - Galatz גאליץשיחה Talk 15:21, 10 July 2018 (UTC)
  • Absolutely. Drmies (talk) 16:33, 10 July 2018 (UTC)
  • No Content should be condensed and trimmed to essential moves, a bare minimum of Finishing Moves. I believe theme music section should remain untouched, as there is no real alternative to it. Other sections like Nicknames and Managers aren't that essential. The "In Wrestling" section (I'm not attached to that name) can be bloated, but should not be outright removed. It should be improved.206.45.59.254 (talk) 17:15, 10 July 2018 (UTC)
  • No. Fixing what was not broken. Restore each page to it's previous incarnation and figure out a new format that works for everyone, not just the neckbeards from WP:PW. Endlessdan (talk) 17:44, 10 July 2018 (UTC)
  • Could we please try to be civil here Endlessdan? Would this discussion fall under "professional wrestling broadly construed"? If so we should probably mention that Pro Wrestling as a topc is under General Sanctions so no one is surprised.  MPJ-DK  20:54, 10 July 2018 (UTC)
  • Yes The old format had several issues. Now, I think it's better and follows Wikipolicys. --HHH Pedrigree (talk) 17:58, 10 July 2018 (UTC)
  • No The 'In Wrestling' section should be at worst condensed. I would suggest removing 'Signature moves', 'Nicknames' and 'Managers'. The 'In wrestling' section is generally informative and missed on pages it has been removed from. — Preceding unsigned comment added by 86.27.113.12 (talk) 18:07, 10 July 2018 (UTC)
  • No A wrestler's moveset is not "trivial information". Some wrestlers like Daniel Bryan and AJ Styles used to have an unnecessarily long "In wrestling" section, but that can be fixed by limiting the moves to finishing moves and notable signature moves, and removing "nicknames", "managers", "wrestlers managed" and "wrestlers trained" from the section. Removing it altogether rather than fixing it is lazy. Most of the time the wrestler's moves will not be mentioned in the articles, or be mentioned in awkward sentences like "Asuka uses a crossface chickenwing with bodyscissors as a finisher and calls it the "Asuka Lock"", that break the natural flow of the text, and essentially, is just an overcomplicated way of doing exactly the same thing that the bulleted list was doing. Very few wrestler's gimmicks are connected to their finishing and signature moves strongly enough for it to be worked in a prose, and in these particular cases, it can be worked in the prose while also keeping the "In wrestling" section. We should fix what was wrong with the section, not lazily remove it. BLXCKPXGX (talk) 18:45, 10 July 2018 (UTC)
So, where is the limit? What makes a signature move notable? Why Nicknames, managers should be deleted? Just because you say so? --HHH Pedrigree (talk) 18:48, 10 July 2018 (UTC)
What makes a finishing move more notable than signature moves? Because they end a match? How is is that more significant? Just because you say so? 67.244.146.250 (talk) 18:56, 10 July 2018 (UTC)
BLXCKPXGX Said we should limit the section to finishing moves and notable signature moves. My question, what is the diferent between a notable signature and a no-notable signature? That's one of the many problems the section has. --HHH Pedrigree (talk) 18:59, 10 July 2018 (UTC)
Using Triple H as an example, the Pedigree, the spinebuster and the high knee are notable moves. The running clothesline and the abdominal stretch are not. The Tombstone, chokeslam, Last Ride, Old School, etc. are notable Undertaker moves, the Fujiwara armbar and the bearhug are not. And I suggested removing "nicknames", "managers", "wrestlers managed" and "wrestlers trained" to trim down the section, not that I want it, but many are saying the lists were full of trivial information, so leaving only the essential, and what's hard to work in the prose (theme songs) could be the solution. BLXCKPXGX (talk) 19:23, 10 July 2018 (UTC)
That's your point of view, your own criteria. For example, you say "Abdominal stretch isn't notable", I say "Abdominal stretch is notable". We need a criteria for all of them. If a move is signature, we need a source saying "this move is signature". --HHH Pedrigree (talk) 19:26, 10 July 2018 (UTC)
I think we all agree that the spinebuster is a notable Triple H signature move while the abdominal stretch isn't. What criteria am I using? I'll be honest, I don't know, I just know that one is an iconic part of his arsenal and the other isn't. But if we're working it in the prose, wouldn't we have the exact same issue? The user below said: "if, say, John Cena's theme song entrance theme is notable, we'll note it, of course, but in the proper section under "Professional wrestling career", or, "Music", or wherever." What's the criteria used to mention "My Time is Now" but not "Slam Smack" in the text? Or are we just mentioning everything? Which, again, is just an overcomplicated way of doing exactly the same thing that the bulleted list was doing. BLXCKPXGX (talk) 20:00, 10 July 2018 (UTC)
If it's a "I just know" situation, then you must keep in mind WP:OR, WP:SYNTH and WP:ILIKEIT. oknazevad (talk) 01:26, 11 July 2018 (UTC)
  • Yes, do so: per Galatz, we don't need long lists of information that serve no real purpose; per WP:NOTEVERYTHING and WP:IINFO, if, say, John Cena's theme song entrance theme is notable, we'll note it, of course, but in the proper section under "Professional wrestling career", or, "Music", or wherever. HHH Pedrigree, in the discussion below, also laconically summarizes my beliefs regarding policy and the "In wrestling" list. To close, I'd like to quote WP:NOTEVERYTHING: "Information should not be included in this encyclopedia solely because it is true or useful." I believe the "In wrestling" list-sections most certainly fall under that distinction.
    Addendum: perhaps the revival of the Pro Wrestling Wikia might be better for pro-wrestling fans? Javert2113 (Siarad.|¤) 19:16, 10 July 2018 (UTC)
Javert2113 - The Pro Wrestling Wikia never went away, and is still updated... Lee Vilenski (talkcontribs) 13:06, 13 July 2018 (UTC)
I didn't know that. Strike above word "revival", replace with "continued updating". Javert2113 (Siarad.|¤) 15:41, 13 July 2018 (UTC)
Yeah, I used to update a bit on there. I'm sure the wikia would love aditional editors. Lee Vilenski (talkcontribs) 15:46, 13 July 2018 (UTC)
That is not true, Lee. that is way outdated! I looked there but guess what? It is wrong! For example, that [still] lists Bianca Belair’s theme as "We Do It Better" (WWE; 2017-present) & Lacey Evans’ theme as "Bad Girl Good Boy" by Kimberly Korn (NXT; October 20, 2016 – present) but before it was taken down Wikipedia said that Bianca Belair’s current theme is really “Watch Me Shine” by CFO$ & Lacey Evans’ is “Like a Lady” by Nancy Rowland….those songs, which, by the way, are not on WiKia are, in fact, on iTunes. So how can you deny the actuary of that? That is just an example which proves that Wikia is not updated regularly.OnlyRealSpike (talk) 01:31, 20 July 2018 (UTC)
  • Yes, Admittedly I'm not involved with this project but the section comes across as very problematic to properly source, as well as arguments of WP:NOTEVERYTHING. Additionally, the section doesn't come across as particularly 'encyclopedic', but that last one is just my opinion. ToastButterToast (talk) 19:49, 10 July 2018 (UTC)
  • No. If it attracts cruft, the solution is to remove the cruft. If some of it is the result of original research or synthesis, then (a) try to find a reliable source for it, and, if that doesn't work, then (b) remove it. Isn't that how everything on Wikipedia works? Taking a look at Bret Hart's article, 32 moves were listed (2 finishers, and 30 signature moves). I think the list could easily be trimmed to six--Finisher: Sharpshooter; Signature: Second rope elbow drop, Russian legsweep, Sidewalk slam; With Jim Neidhart: Hart Attack. I totally agree that almost all of the rest are moves he used, sometimes consistently, but that very few of the others are important for an understanding of the character. If we can source these six, we've got something worthwhile and in keeping with policy. However, there's no need to delete an entire section from thousands of articles because some have become bloated. In many cases, this has led to a "policy based" deletion of sourced information where no problem ever existed. As for the other sections, I can't speak much about Entrance Themes, since I've never cared much. I think it would be better for people who are more invested in the topic to consider the importance, although I will say that I am concerned to see so many people pushing for elimination because "it's just not important". There's really no way to measure that, and Wikipedia is full of information and articles that are important only to a select group. I'm never going to read about Finnish equestrians, but I would assume that Wikipedia has a bunch of information. Just because I won't read it doesn't mean it's "just not important", though. I'm also not particularly concerned about the "Nicknames" subsection. Some of it seems valuable, while others were used a handful or times, in a single interview, mentioned once on Twitter, etc., and obviously have no place. To use that to justify removing "The Rocket" or "The King of Harts" from Owen Hart's article is obviously an overreaction, although these may work just fine in the prose. The other subsections involved, however, are ones that I find particularly useful (and I know that there has been a lot of negative reaction to the claim of being "useful" lately, with people pointing to an essay about arguments to avoid in deletion discussions. There's nothing binding in that, however, and there is no need for paranoia about people finding the content useful--there have been a lot of disparaging comments about "fanboys", but it's important to note that (a) wrestling fans aren't less important or worthy of respect because they choose to watch a television show that they are aware is not real, and (b) not everybody who reads or edits the articles is an obsessed teenage boy. I'm certainly not a teenager, and I don't watch wrestling. I do, however, have multiple academic publications about professional wrestling. While doing this research, I have made much use of the "Managers" and "Wrestlers Managed" subsections. This has provided a valuable quick glance at a wrestler's career that can then be delved into with reliable sources to discover valuable information that is not necessarily covered in the article. Rewriting these sections as prose would make them difficult to navigate and would often provide choppy, list-like sentences. Certainly, for managers, it's essential to an understanding of the character to have a clear (and well-sourced) list of the wrestlers they have managed. And, on both sides, I would say it is important to keep it under control by leaving out one-time appearances. For example, on the Jake Roberts article, it listed Alice Cooper as a manager. Because this was a one-time deal done to publicize an event, it would fit much better into the prose when discussing Roberts's appearance at WrestleMania III. GaryColemanFan (talk) 20:14, 10 July 2018 (UTC)
  • No. Well, here's my two cents. Which I already gave in the Pro Wrestling Talk Page, so I guess I'm up to four cents? Everyone appears to have jumped the gun, deleting the section before assessing what separates data they consider unimportant from that which is, and I'd like to remind everyone WP:NODEADLINE. No editor appears to dispute that wrestling moves possess encyclopedic significance; currently finishing moves are to be added in prose in recognition of their relevance to the wrestler. However, what quality lends a wrestling move significance remains unanswered within the style-guide or discussion. What specific guideline a signature move as a piece of information violates within WP:NOTEVERYTHING, which a finishing move to be included in the 'Wrestling Persona' sections does not violate has not been adequately identified. Finishing moves are important, but the quality making them more important than a signature remains vague. These distinctions appear arbitrary. Arguments abound that the sections themselves sections tend to contain OR, poor sourcing stemming from frequent fan edits, that a signature is pure WP:FANCRUFT, or that removing it grants a more encyclopedic aesthetic. And each of those may be true. But those are individual violations to be removed on a case-by-case basis; their existence does not demonstrate why all information attempting to be included is not material an encyclopedia should provide. Someone using original research to include a wrestler's frequent use of a piledriver should be removed, it's original research. But whether a piledriver is pertinent information for a wikipedia article is an entirely different question, and one that has not been answered. Discussion of the value or significance of content does not appear to have driven the removal conversation; no rationale has been solidly agreed upon regarding why a move might or might not be important information. Worse, the wider use of the Wrestling Persona alternative opens up up identical WP:FANCRUFT and Original Research concerns the 'In Wrestling' section was deleted for, but this too appears to be ignored. 67.244.146.250 (talk) 20:25, 10 July 2018 (UTC)
  • Yes Remove - over the last 10 years this has failed miserabily - crufty, trivia, edit warring over a move is a "leg lariat" or "a kick", false information inserted, Original Research etc. It's a mess and there is no way anyone can persuade me that a wrestler has 25 signature moves. Nicknames were a mess, too - someone was called a "toolbag" one week and it's an official nickname on Wikipedia and so on - it is the single most abused and edit warred over section.  MPJ-DK  20:51, 10 July 2018 (UTC)
Why don't we fix it then? Removing it rather than fixing it is lazy. No, no wrestler has 25 signature moves. There is no reason for the Fujiwara armbar to be listed as a signature move of The Undertaker for example. Limit the moves to finishing moves and notable signature moves, and remove "nicknames", "managers", "wrestlers managed" and "wrestlers trained" from the section. Just remove all that's trivial, there is no need to gut the entire section. BLXCKPXGX (talk) 21:51, 10 July 2018 (UTC)
I'm not a part of the clean-up effort here and their perspectives may vary, but the problem I see there is that there is no empirical, WP:WEIGHT-based way of deciding what content is important or note-worthy, which means the fields become a constant source of attraction for subjectivized tinkering; no consistent approach can be applied and the section remains a perpetual site of either edit warring or entrenched debate, since the content added is always the product of fan metrics (which are highly variable between these devoted fans), rather than something pulled from reliable sources (which is disallowed as a matter of policy anyway, and further reason to avoid an approach that encourages it). Snow let's rap 22:00, 10 July 2018 (UTC)
Some editors have been trying to fix it for 10 years, with reverts and IPs and fans adding stuff, no good guideline for inclusion etc. It's not like some people haven't tried. MPJ-DK  22:06, 10 July 2018 (UTC)
  • Yes (edit conflict) This section was horribly trivial for ten years. There were no criterion for inclusion, resulting in users adding movees or nicknames that were used once (see this article on WWE.com, where AJ Styles is called the "Georgia Pitbull" for the first and only time, resulting in it being added to his nicknames). Nearly every single technical name for moves were WP:OR. It was overly crufty and broken to the point of no return. The main counterarguments I'm seeing are WP:ILIKEIT, "lots of people find this useful", and "it was here for 10 years so it shouldn't be removed." Prose for the notable moves is a much better alternative. JTP (talkcontribs) 20:59, 10 July 2018 (UTC)
  • Yes, Support - This seems like a reasonable approach and the one which is most broadly consistent with a number of guidelines and MoS recommendations (WP:WEIGHT and WP:PROSE most prominently). Furthermore, the topic matter of pro wrestling has been put under general sanctions now, so without some broad community consensus backing them up, WP:HERE editors working on clean-up in this area would find their efforts slowed to a crawl by SPAs and socks jumping around abusing multiple accounts, flaunting the sanctions while regular good-faith editors obeying the rules would not be able to violate 1RR restrictions. The clean-up brigades therefore have a reasonable request in wanting to establish clear guidelines for what type of formatting is generally expected for these articles. They at first attempted to create this guidance at WP:PW but they were informed that WP:Advice pages prohibits that. So they thereafter diligently constructed this proposal and brought it here for wide community vetting and hopefully approval. Given that I think their approach is the option which is most consistent with actual policies and MoS guidance, I can support it, even though I am generally very wary of default approaches.
And on that last topic, it is worth noting that the proposal does frame this as a default approach; WP:LOCALCONSENSUS would still apply on any article and a discussion on a talk page for a given pro wrestler's article could still adopt another approach. What a support consensus in this discussion would mean would be a simple shifting of the burden; the clean-up crews could begin shifting the content towards a WP:PROSE approach and be able to point to this discussion if asked to make a prima facie case for consensus; local editors would then be able to propose rebutall arguments on the talk page, but the burden would be upon them to establish a clear consensus for an exception. That seems like a very reasonable way to balance the local and community consensus issues here and allow the needed clean-up to take place. Wikipedia is not the place for all possible content and I have become convinced by the editors undertaking the clean-up here that this is a necesary first step to pairing down the articles in question and making our coverage more consistent with our general encyclopedic standards. Snow let's rap 21:54, 10 July 2018 (UTC)
  • Yes/Remove These sections seem to be fancruft. From a policy perspective it is likely most of the material is WP:UNDUE from the point of view of an encyclopedia. In fact all of the 'in-universe' stuff needs to go except for those events/elements which break out into the universe of real-world reliable sources. Jbh Talk 21:59, 10 July 2018 (UTC)
  • No/Reinstate Partly I agree that the Signature move list was way too long and unsourced. However I believe that the Entrance music and especially the Finisher sections/lists are fairly easy to implement and properly source. Entrance musics are easy to source with VODS, as are Finishers. Finishers by definitions are moves that quite frequently finish that respectives matches. Not one or two offs, frequently. For example: Sami Zayn's Blue Thunder Bomb is pretty much his signature move but doesn't finish matches: Should probably not be included. His Helluva Kick does finish his matches on the regular and should be included. So in summary: Remove the Signature Move section, keep the Entrance Theme and Finisher sections. I have no opinion about the Manager section one way or another. DrJackl (talk 22:36, 10 July 2018 (UTC)
  • NO I already gave enough suggestion directed to people want to rollback this change, so It appears "the small group" have jumped the gun, deleting the section before allowing proper outreach to many users to help improve. 10+ years this section been alive. This change should never been jump into removal or else we wont have this.

Returns this good section the only option to end this rockus. Colton Meltzer (talk) 23:17, 11 July 2018 (UTC)


  • NO It’s a handy resource for people who may, for whatever reason, need a quick and easy answer to a question about any number of pieces of information and there’s not a suitable second best place to go online looking for it. In my opinion, removing this would be along the same lines as cutting track listings from albums or trying to work the name of each song into the article about the album. Part of the point of an encyclopedia is to be able to quickly dig up an easy answer to something and abundance of cruft or not, this section largely provides that. Evalas618 23:04, 10 July 2018 (UTC)
  • NO For some then championship section is much longer then their moves, music, etc. Why remove that but keep the long championship listings? I for 1 want to see someone's moves & want to look up their music & some have won every single championship in every company they have been in! Who needs all that? I think their moves & music is more important then their endless championships. — Preceding unsigned comment added by 2602:306:CCE0:8550:81DD:D18E:1485:114A (talk) 23:49, 10 July 2018 (UTC)
  • No - I've been mostly retired for numerous years now, both as a user and an admin, but on this matter would like to give my opinion. Years ago, many many years ago, the question was asked over spoilers for pro wrestling over whether it was an entertainment program or a sport (as in did an event transpire when it occurred in front of a crowd, or when iot was broadcast on television). Wrestling is a carny business, its stupid and illogical and amazing, and part of the story is in the moves and the abilities of the competitors. To catch this in pose, over decades of a career, is impossible especially as times change and without the text reading like a grade schooler trying to pad the word count. This is because the stories in the matches aren't limited to a single move, it's a number of them that build to a particular style. Some things are generic yes, but some things are not and knowing these and what they are is part of the knowledge base for wrestling. Could the In wrestling sections be cleaned up? Undoubtedly yes, but the accusations of cruft and that of diminishing value is as blinded by wall gardening as the inclusionist accusations are. Not everything fits into a narrow box of "is trivial" or "is not trivial" nor can making things have a sweeping removal ever be done without uproar occurring, and to then pass off the uproar as fly-by-nighter-johnny-come-latelys is to ignore the readers of wikipedia at their own peril. Wikipedia is a force for good, but sweeping changes made by 8 people is inevitably going to cause a problem, and its not like these 8 were arbitrators. If things need to change they have to change, but what has happened here was clearly wrong and to much "us vs them" rather than actually looking at why these sections existed without one side reducing it to WP:USEFUL and the other WP:CRUFT. They have their place, they are important, and all-or-nothing is not the way we do things. At least not when I was here. –– Lid(Talk) 00:05, 11 July 2018 (UTC)
  • Yes, remove Professional wrestling articles are now under strict sanctions because the broader editing community was fed up with the constant bickering and edit warring, and the inclusion of large amounts of unsourced trivia and "in universe" content in those articles. I have been very impressed and gratified at the work that many pro wrestling editors are doing to clean things up. I agree completely with Snow Rise that going back to the old ways now would severely interfere with this essential cleanup campaign. Cullen328 Let's discuss it 00:18, 11 July 2018 (UTC)
  • Yes Besides the maintenance issues.. look, even if you could guarantee these would be properly maintained, this type of list is still the definition of cruft. Minutia that is only of interest to the hardcore fan, that does not actually give any additional insight on the subject of the article in a broader sense. --SubSeven (talk) 01:11, 11 July 2018 (UTC)
  • Yes, remove. A trivia magnet bullet list with no clear inclusion criteria is possibly the worst way to present information about a character's persona. I've seen numerous complaints at the WT:PW discussions that it is needed for video games' "create a wrestler" feature. That is totally not what Wikipedia is for! Pro wrestler biographies have a weird double job of being both a biography of the performer and an article about the character. But it is WP:NOTGAMEGUIDE. Nor is it WP:IINFO. These sections just don't work well. Prose is a better format, and allows for context, which serves the Wikipedia purpose of being a general interest encyclopedia better. oknazevad (talk) 01:26, 11 July 2018 (UTC)
  • Nuke from orbit, destroy entire section immediately, and on the off chance anything worthwhile is lost, it's worth it because it might attract CRUFT!!!! seems like a poor choice. Whatever the ultimate consensus is, I would submit that this option is by far the worst. There's no WP:DEADLINE and no need to WP:BITE new editors. Deltopia (talk) 01:57, 11 July 2018 (UTC)
  • I don't get the "Deadline" argument - if a consensus is reached to remove them, who cares if some people go through and remove them quickly or make a five-year plan to hunt them all down? That's just a stall tactic by those who do not like the consensus - if consensus is to allow it I could use "deadline" to stall any work on readding the content? Sorry I was not going to comment in general, but this does not make any sense to me. And if we remain WP:CIVIL no newbies would get bitten, that's not WP:AGF my good chap.  MPJ-DK  02:11, 11 July 2018 (UTC)
  • I haven't seen much in the way of articulated policy or guideline-based reasoning for removal of this content, besides one reference to WP:OR. WP:NOT here and there, but those references are a stretch. Does someone want to lay it out? Conversely, I also see little on the keeping editors. Is there a reason we should keep the content, grounded in policy/guideline? --Izno (talk) 03:39, 11 July 2018 (UTC)
  • Yes - These sections invariably attracted cruft and WP:OR. This is what Roman Reigns' section looked like. The moves list is a very typical example; sources almost never actually describe "Signature moves" so the solution has been to provide multiple sources which show the wrestler used the move a couple of times. This is a blatant case of WP:SYN. Theme songs are also rarely notable enough to get mentioned in WP:RS, so the solution has been to link to iTunes. A good rule of thumb is that if RS don't mention it, then it's not worth keeping around. Everything worth keeping should already be in the prose or could easily be worked into it and anything lost had no place in the encyclopedia to begin with. I recently brought Bobby Heenan to GA status and was surprised to see that almost everything in his "In wrestling" section (every nickname and all but a few of his less notable pairings) was already in the prose! The section was simply superfluous! LM2000 (talk) 03:43, 11 July 2018 (UTC)
  • No - While the section could use cleaning up, I disagree with outright removal. The information is valuable and useful, and the list format is the most efficient method of digesting the information. Removal of the section may follow the letter of the law, but I feel it ignores the spirit of it. Removal of the section may follow some arbitrary rules of conduct, but I feel it goes against the idea of what Wikipedia is. I'm disappointed with the decision to remove a valuable section that I use on many occasions. I feel that if Wikipedia is no longer interested in providing knowledge to the masses, I am no longer interested in supporting Wikipedia. 122.106.169.214 (talk) 04:04, 11 July 2018 (UTC)
  • No - To generally summarize what I posted on the talk page, I feel that the prose compromise is insufficient and needlessly complicates what is a section with use and that has encyclopedic information in it (nicknames of a wrestler, important moves, theme music and wrestlers trained come to mind as well as falling under this category in my view). Prose runs the risk of becoming convoluted in nature and removes the intended resourcefulness of its own self. A prose page for all wrestlers will be hard to do and become more difficult to parse through for information. The length of move-sets has long been a problem and I also believe, despite supporting the keeping of the 'In Wrestling' section, it should be managed at a level and/or trimmed down, but provided information for key moves to a wrestler and additional encyclopedic information is well-cited and reliably-cited, I see no reason to move this sort of information into a prose block. It removes convenience for user and editor and I don't see a reason to do that and remove a chunk of information that I would consider to be worthy of inclusion on this web encyclopedia. In conclusion, I believe sweeping removal (or at the very least dramatic change) of long-standing content that has merit for being in these articles in the first-place is not the way to go about this matter. NotAdamKovic (talk) 04:09, 11 July 2018 (UTC)
  • No with condition - These lists do often turn to WP:FANCRUFT about which wrestling moves are notable and which are not. Some of them even have concerns about whether the wrestler actually did the move, because they did a variation of it or something like that. However, with stringent enforcement of Reliable sources, adhering to standard procedures when material is challenged, and Wikipedia's policy on WP:DUE weight, these moves do have relevance within the realm of wrestling. A wrestler may be well known for doing a certain move as part of their cliche or personality. If they are well known for doing such, we should be able to find sources to that effect. We also need to enforce the No original research policy if this is kept. I'm overall in favor of keeping them if these Wikipedia policies can be enforced on these articles. Tutelary (talk) 05:15, 11 July 2018 (UTC)
Sure, but wouldn't this information be best placed in prose? Lee Vilenski (talkcontribs) 11:29, 13 July 2018 (UTC)
  • Moves that are significant to the wrestler's identity, with good sourcing, should be added to the prose, not put into a list. --SubSeven (talk) 05:48, 11 July 2018 (UTC)
  • Yes - There is no definition of what a signature move is, and there is no official guide that describes what the technical moves are. Therefore all move lists are WP:OR or a violation of WP:SYNTH. Finishing moves are important to the characters, but prose can help provide context that a bullet list lacks. Managers can also be listed in prose with context such as dates and promotions, which provides more info than a straight bullet list. Entrance themes are important to "some" characters, and that too can be included better in prose with an explanation of "why" it is important to that character. The majority of the information in the "In wrestling" sections was impossible to source, so trimming the lists down to what can be properly sourced would result in some very short lists. I don't see how a short context-less list is any more accessible than prose. Nikki311 09:20, 11 July 2018 (UTC)
  • Yes. People who want to have an in-universe article should use the wrestling wikia. This information is not encyclopedic. Natureium (talk) 13:57, 11 July 2018 (UTC)
  • No - While some wrestlers may have long lists of moves, to argue that finishing moves are irrelevant to a wrestler is ignorant. A finishing move, and by extension signature moves, are keys to a wrestler's in-ring performance. This is even more apparent with historical industry changing moves, whether it's now common moves that used to be big moves in previous eras, like the German Suplex or the Brainbuster, to something like the Orange Crush, Burning Hammer, or Emerald Flowsion. I think the scope of this argument has been focused to "Roman Reigns' list has an armdrag on it" (or whatever) and isn't taking into consideration the effect this would have when talking about wrestlers in the context of wrestling history. You can't have an article about Ric Flair without the Figure 4 Leglock. Should these lists be concise, cited, and logical? Sure. But they should not be removed as a whole. Bonevoyage (talk) 19:03, 11 July 2018 (UTC) — Bonevoyage (talkcontribs) has made few or no other edits outside this topic.
As we said one hundred times, if a move is notable and important, we can put in a career or wrestling style section. Lou Thesz includes the creation of the powerbomb in the introduction. Same as Fujinami Dragon suplex and Dragon sleeper. Try to find a source and include Flair's finisher in the article. --HHH Pedrigree (talk) 19:24, 11 July 2018 (UTC)
-Sorry I didn't realize only new opinions were allowed in this discussion area. Bonevoyage (talk) 20:26, 11 July 2018 (UTC)
He didn't disregard your opinion. We have always maintained that if something is significant to the performer and can be reliably sourced, such as Flair's figure four leglock, then it can be included regardless of this section's removal. This proposal itself even mentions that certain finishing moves are likely to be retained. Flair's article may not have been updated to include that detail yet, but you can WP:FIXIT yourself, if you'd like. Prefall 21:01, 11 July 2018 (UTC)
Like someone's theme music isn't "significant to the performer"? I think it is. — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 21:47, 11 July 2018 (UTC)
  • Yes - Like mentioned before, some content can be added to the prose, not put into a list (like finishing moves, managers, "some" entrance themes), but stuff like the signature moves has no clear definition and the nicknames bit is a huge clutter. Really disappointed with the section, even from a long-time pro wrestling fan. 2A02:2F0D:D00:C00:463:23AB:1E16:D947 (talk) 20:01, 11 July 2018 (UTC)
  • Yes - If such content is based on reliably-sourced in-depth coverage, then there should be material for more than a bullet point list. If it is not based on reliably-sourced in-depth coverage, then it doesn't need to be included. The effort that would be put into stopping clean up on this general site should instead be used to fix and maintain specialist sites like the wrestling Wikia. I don't see why we should apologize for making people read actual prose with more than four words per line instead of lists that are utterly meaningless to non-fans. Ian.thomson (talk) 00:21, 12 July 2018 (UTC)
  • No, but change the name The debate was originally about whether the In Wrestling section should be renamed to something else, since many felt the subheading was very vague and didn't accurately represent what the section was about. As far as I'm concerned, the idea of deleting the whole section wasn't brought up until few days before the consensus vote. The vote lasted a couple of days and was closed after an "overwhelming consensus". I feel like the decision was made in a WP:RUSH and as can be seen by the amount of discussion it has led to since then, there are a lot of people who oppose the change. I wholeheartedly agree that the section should be renamed to something else. "Professional wrestling highlights" and "professional wrestling details" were two of the suggestions for the new name. Removing the whole section, however, is not the answer. When it comes to working the contents of In Wrestling into the prose, I'd say that would affect readability, and sometimes a simple list is a better option. It's stated in WP:TRIVIA that "a selectively populated list with a relatively narrow theme is not necessarily trivia, and can be the best way to present some types of information", and I would say that's the case here. Professional wrestling is a combination of theatre and sports, and the finishing moves or entrance theme musics of wrestlers are just as important as championships and other accomplishments. None of this information is trivial in context of wrestling. Another cause of concern amongst the most active WikiProject members seems to be that the section gets edited a lot by people who believe every single move ever done by a certain wrestler should be included in the article. It's unfortunate that this happens, but I don't think WP:SUSCEPTIBLE is a good reason to remove the whole section just like that. Many of the professional wrestling promotions' websites, including World Wrestling Entertainment and New Japan Pro Wrestling, do have a plethora of articles and wrestler profiles listing their finishing moves and entrance music. Those websites can and should be used as sources, and the list of moves can be limited to their signature moves. Not every single punch and kick needs to be listed. All in all, I believe this consensus relies too much on Wikipedia's imperfect policies and guidelines. Sometimes accessibility and informativity should be put ahead of those guidelines (WP:RAP). In my personal opinion, the decision should be reverted, the section should be brought back and the WikiProject should focus on renaming the section and clarifying what moves, nicknames and themes should be included on the list. Kanavarras (talk) 10:28, 12 July 2018 (UTC)
You say “Many of the professional wrestling promotions' websites, including World Wrestling Entertainment and New Japan Pro Wrestling, do have a plethora of articles and wrestler profiles listing their finishing moves and entrance music. Those websites can and should be used as sources, and the list of moves can be limited to their signature moves.” but that just is not true. Where, exactly does WWE list superstar theme music? The fact of the matter is you can’t say because they don’t! Wikipedia was the “only reliable” place that ever did!~~The Greatest— Preceding unsigned comment added by 2602:306:cce0:8550:d424:64a0:7b5c:a6e5 (talk) 08:14, 12 July 2018‎ (UTC)
First of all, no need for the hostility. If Wikipedia is the "only reliable source", then it isn't a reliable source at all, since Wikipedia relies on other sources for its information. However, WWE actually has a record label named WWE Music Group. They compose and release most of the wrestlers' music by themselves, and those releases can be found on Amazon and iTunes. They also have a VERIFIED YouTube channel. All the music on artists' album pages (here's an example with Britney Spears) use similar sources, so that shouldn't be a problem. Kanavarras (talk) 23:43, 12 July 2018 (UTC)
Wikipedia is not a reliable source. If Wikipedia is the only place that listed them, that's a very good indication that it's not a notable concept and shouldn't be included in the articles. --Ahecht (TALK
PAGE
) 13:19, 12 July 2018 (UTC)
Where else is? The only other place that had/has it is way outdated & is missing current/new content! Content that was, in fact, on Wikipedia before it was taken down! So if Wikipedia isn’t a reliable source then where, exactly, is? That right here makes it the **most** reliable source! What part of that is so hard for you to understand? If it can’t be found on Wikipedia when where **can** it be found? Furthermore, it has been on Wikipedia for 10+ years so why take it way now? That makes no logical sense whatsoever!~~ The Greatest— Preceding unsigned comment added by 2602:306:cce0:8550:d424:64a0:7b5c:a6e5 (talk) 10:03, 12 July 2018‎ (UTC)
Firstly you are violating Wikipedia:SIGLINK by not properly signing your posts. Second, everything on Wikipedia must be independently verifiable, see WP:V. If the only place you can find this information is on Wikipedia, then its not verifiable, and therefore should not be kept on wikipedia, regardless of the outcome of this discussion. - Galatz גאליץשיחה Talk 15:02, 12 July 2018 (UTC)
I am signing my posts (now). Don’t you see “~~The Greatest”? I may not be signing them the “official” way or how you want them signed but I am signing them the way I am going to with the was I have been treated! If you have a problem with that then tough crap….“~~The Greatest— Preceding unsigned comment added by 2602:306:cce0:8550:d424:64a0:7b5c:a6e5 (talk) 11:25, 12 July 2018‎ (UTC)
If you wish to contribute to this discussion, Wikipedia has certain requirements for signing posts, and for what the signatures must contain. Sign your posts by using four tildes (~~~~). If you want "The Greatest" to show up as your name, you should register an account with that name first by going to Special:CreateAccount. It literally only takes a few seconds, as all you have to do it enter your desired username, your desired password, and enter the CAPTCHA text. You don't even have to provide an email address. --Ahecht (TALK
PAGE
) 16:25, 12 July 2018 (UTC)
  • No, unless a policy is put in place to replace the section with prose on each relevant page before deleting the information outright I am okay with the section being removed in favour of a "wrestling style" prose section, or something of the sort, but I feel like the sections were basically deleted based on the opinion of a few people with very little way for the general public to even know the debate was happening without digging into a sub-page deep in the editor's side of Wikipedia, a place which not many people generally end up, which has resulted in the information just ceasing to exist. No-one deleting it is making any effort to replace it with a more appropriate format, they're just deleting information outright, which is the problem. — Preceding unsigned comment added by 2001:8003:CC03:AC00:8947:847:85E3:DD23 (talk) 14:24, 12 July 2018 (UTC)
Well, there was a consensus for it's removal, so it was removed. Then there was a conversation over it's removal, and now we are here. The information is not lost, as it will always appear on the history tab; and can be turned into a real section. Lee Vilenski (talkcontribs) 11:29, 13 July 2018 (UTC)
  • No per Lid. GhostOfDanGurney (talk) 03:02, 13 July 2018 (UTC)
  • Support - The above procedure would be simply moving a list of what is usually meaningless cruft into prose (The "Professional Wrestling Persona".) Most of these article are filled with examples of WP:FANCRUFT for every move that the BLP has ever done is "sourced" with a reviewer stating that the move was used. Personally, I'm against meaningless information like this being included in an article. The arguement against the removal of this information are generally based on WP:ILIKEIT, or a confusion on what wikipedia is. Important information should be easy enough to turn into prose. Some pieces of information, such as Jeff Hardy creating his own theme song in TNA, or Petey Williams inventing the "canadian destroyer is information that could very easily be changed into prose. Information on who a person has been managed by (Even if sourced) is irrelevent, unless they were a long term manager, in which case, this should be in this section, or more likely the career section. Information on moves used is no more notable than a list of ways that Lionel Messi attacks during a football match. Lee Vilenski (talkcontribs) 11:26, 13 July 2018 (UTC)
Less so, if you ask me since a) Messi's approach to the ball has actual impact upon his game, and b) the number of ways in which he can approach the ball can be summed up as a relatively closed class of options due to competitive constraints, whereas a pro wrestler's moves a) are completely arbitrary and chosen for theatrical effect, and therefor b) are a completely open class of ever-shifting and potentially infinite options that will invariably add up to mammoth proportions. There's also the rather critical policy matter that Messi's techniques are the subject of substantial WP:WEIGHT of coverage in WP:reliable sources, discussed in encyclopedic context, whereas "finishers" or whathaveyou are not a substantial part of what WP:reliable sources have to say about professional wrestlers and are simply added at the whim of whichever fan would happen to be editing the "In wrestling" section that day. Snow let's rap 13:42, 13 July 2018 (UTC)
I agree. But I was using the simile pretty arbitrarily. In fact, WP:FOOTY has a "playing style" or "Style of play" for this type of entry, which is what the "Professional wrestling Persona" section would be similar too. Lee Vilenski (talkcontribs) 13:52, 13 July 2018 (UTC)
  • No per Lid and others. (Summoned by bot) This information is clearly of great interest to many people, based on comments here of those who don't want to see it disappear. If these topics have WP:WEIGHT in RS reporting on wrestlers, then Wikipedia should present that information in some format. Also, if these sections attract "cruft" from new editors, surely that is an opportunity for us to welcome new content-creators in a non-bitey way. HouseOfChange (talk) 08:55, 15 July 2018 (UTC)
I don't think WP:ITSUSEFUL / WP:ITSINTERESTING works here. It's one of the reasons why professional wrestling articles have been swamped in immense WP:INUNIVERSE detail for such a long period of time. This is also not a simple matter of weight given by reliable sources. When it comes to wrestlers in popular promotions, such as WWE, practically every performance in their career will be covered ten times over in routine coverage from reliable sources. This can range from hundreds to thousands of matches, all with detailed writeups of each move performed during them. One of the major issues with this section is trying to discern which of this information is actually worth noting. This also does not delve into the WP:SYNTH / WP:OR issues with many of the moves performed (as discussed in the section below). To cite the Daniel Bryan and A.J. Styles examples from the proposal, they show just how excessive and problematic this section can become. Prefall 09:59, 15 July 2018 (UTC)
  • No Just try again to source it properly, exactly like we attempt (and often fail at) with prose. InedibleHulk (talk) 13:21, July 15, 2018 (UTC)
  • Yes, anything encyclopedic should be included in well-sourced prose. I agree with Prefall's first post and the one above mine. Doug Weller talk 13:24, 15 July 2018 (UTC)
  • No, but condense and source the content. This is not WrestleCruftPedia. See MPJ-DK's excellent post at the top of the #Example of the "Keep" vote with strict WP:V verification. subection, below.  — SMcCandlish ¢ 😼  17:27, 15 July 2018 (UTC)
  • comment - Anyone who says "keep" should provide their input on when something is notable enough to include - signature moves, nicknames , managers and theme music has gotten very crufty and trivial over the years. If we keep the section we need a good, CLEAR guideline for everyone so that it is easier to maintain.  MPJ-DK  19:22, 15 July 2018 (UTC)
When a reliable source notes a move is a certain wrestler's finisher, that move is notable and suitable under Finishers (with a bullet and citation). Same deal with managers and the Manager section, signatures and the Signature section, all the way down. No synthetic local excuses like "If four sources call it a move a wrestler does, it's a signature move" or "Accompanying someone to ringside makes you their manager" or "If your finisher looks like something a New Japan guy did on a tape you watched, that means he trained you."
Just plain and transparent verifiability, the sort that's currently sorely lacking in wordier cruft like "In the ring, Monsoon dominated opponents with vicious chops, the dreaded Manchurian Splash, and his signature move, the Airplane Spin". Fortunately, nobody bothered to rename and delete his In Wrestling section, so even complete rubes can still easily and quickly see the simple truths those long-winded lies are roughly based on. Would you keep the unsourced format for matching the style of what you think people want, or delete the sourced list for merely resembling the type of place that's fooled you before? InedibleHulk (talk) 01:12, July 16, 2018 (UTC)
  • NO The old In Wrestling section should've been left as it was, and should be reinstated. Condensing the information is one thing, but to remove it completely was a ridiculous decision. I've used that section as a reference for years when reviewing information about wrestler's current and past entrance themes and move sets. It was both informative and fun to skim over every now and then; especially when a wrestler debuted a new theme, as this was sometimes the quickest and easiest place to find the name of the song or artist. As for trying to work the information into the prose, this seems like an equally ridiculous amount of work to people who will now have to go through and try to eloquently write that information into the prose in an effective way, as well as to anyone who came to these articles specifically to find that information; they'll now have to skim through paragraphs and paragraphs of information for something that they could once skip straight to. Reverting it to how it was is much easier on everyone.--MignightDaybreak (talk) 01:23, 16 July 2018 (UTC)
  • Yes. Things like signature moves might not be the extreme point of trivia, but they're not hugely far. Bulleted lists can be a good idea in some situations, but that's only when the relevance of those items is obvious, e.g. the article about a geographic subdivision (like a U.S. county) ought to have a list of its towns, because nothing really needs to be conveyed about the towns aside from their existence there, and virtually everyone knows something about local government in their country and will understand why the towns are mentioned. However, tons of us are agnostic about professional wrestling; we may wonder why "European uppercut" and "Cobra clutch to a facedown opponent" will matter and why those moves are listed when others aren't: are other moves less significant, or are they not signature moves, or does this character have no other moves at all, and what's a signature move anyway? If you're reading Beaver County, Pennsylvania and you see that Aliquippa is a city in the county, you don't need to be told anything about Aliquippa or city to understand its inclusion, but non-wrestling readers will need explanations that a simple list can't give. And finally, when converting stuff into prose, be sure to use reliable sources. I see that the Daniel Bryan article lost sources like [24], YouTube, [25], and [26]; those are primary sources, as they're either raw numbers (Cagematch) or reports derived from the event itself, not secondary sources that are distilled from the primaries. None of these is written by scholars in the field, which for professional wrestling would be something like film studies or media studies. If you can get solid, reviewed sources of this sort, by all means provide a prose section covering these aspects of the wrestler's career. Nyttend (talk) 01:43, 16 July 2018 (UTC)
Dave Meltzer, Bryan Alvarez and Wade Keller are among the closest things wrestling has to noted scholars. That's not to say it always trickles down to their whole staff, but PWTorch and F4Wonline are still generally top dogs on the topic, something like Sports Illustrated or Vanity Fair are to their niches. Setting the bar higher than that would kill off almost all wrestling articles and seriously starve what's left. If they're good enough for our featured article, they should be good enough for other things one doesn't learn at Dartmouth. That said, they were used improperly in synthesis at Daniel Bryan's list (and others); can't hold that against them. InedibleHulk (talk) 03:24, July 16, 2018 (UTC)
  • No - The "In wrestling" section was incredibly useful. I looked up wrestler's finishers on Wikipedia on a monthly basis. When you want to know a wrestler's current or former finishing moves, a bulleted list in a dedicated section is much easier to use than trying to find it in prose. Prose can easily miss information. Using the above example of Daniel Bryan's reworked page, the added prose talks only about his submission finishers; there is not a single mention of his running knee finisher, which he uses frequently. Even if you disagree with my stance that the information is better presented in a bulleted list, having the information presented in a bulleted list is infinitely better than having the information missing. If the "In wrestling" section must be removed, then a mass removal without replacing the information is absolutely not the way to do it. The Bludgeon Brothers have finishing moves called "The Bludgeoning" and "The Reckoning". If someone wants to know what each of those moves are, that information is no longer available on Wikipedia, because it was simply deleted without re-adding it as prose. The removal of the "In wrestling" section is both the wrong thing to do and the wrong way to do it. --Curseofgnome (talk) 07:57, 16 July 2018 (UTC)
Curseofgnome - This isn't a conversation on how to remove the information. If there is missing notable information (Such as Bryans running knee lift), that can be sourced, you can simply add it (See WP:SODOIT.) However, it does need to be sourced. The issues with some of the move names, is that they can't be reliably sourced. They break WP:SYNTH, which is a big pillar of wikipedia, by adding two references, one that says they use a finisher (by name), and then another by the move itself (common name). However, this is incredibly bad. If a "professional wrestling persona" section was created for the Bludgeon Brothers, then those moves could be added, if the moves are sourced. I should mention, most of these articles are WP:BLP articles, and any information that is poorly sourced should really be removed, regardless of the consensus here. Lee Vilenski (talkcontribs) 09:05, 16 July 2018 (UTC)
  • Keep, but cull signature move sections. One of the reasons I left Wikipedia is because I became exasperated with blanket solutions to groups of issues that required individual solutions, and the tendency to throw the proverbial baby out with the bathwater that came along with those blanket solutions. And in this case, the issues with the 'signature moves' subsection are taking over the discussion and editors are trying to apply overly-drastic solutions to all pro wrestling articles. The signature moves sections are mostly a train wreck with little hope of fixing them - for example on the Gran Metallik article, for most of his signature moves that were sourced, the source merely said that he used them in a match, not that they were signature moves. And there's very little chance of finding a reliable source that claims a move as a wrestler's signature move for most wrestlers. Yet if signature moves are deleted wholesale, that leaves no room for things like Bret Hart's Russian legsweep and middle rope elbow drop (which could be sourced because they're part of his 5 Moves Of Doom), or The Rock's spinebuster (as the setup to to the People's Elbow). The prose sections are nice when possible, but they won't be possible for any but the most prominent wrestlers of all time. (And I'm making my first edit since 2013 because I found out about this through a thread on Gamefaqs). (And I sincerely encourage all these motivated, disappointed editors who liked the signature move sections to roll up your sleeves and start moving the material over to the pro wrestling wiki). McJEFF (talk) 00:27, 17 July 2018 (UTC)
Bit funny how even with more than 30 moves, Wikipedia still managed to overlook a full half of the two in this source. InedibleHulk (talk) 05:42, July 17, 2018 (UTC)
It should be noted that wrestlingdata is not a reliable source for moves, only for uncontroversial claims, see WP:PW/RS. Lee Vilenski (talkcontribs) 07:43, 17 July 2018 (UTC)
Nowhere on that page does it note anything about moves. Just says use with caution, mainly for uncontroversial claim. If it's giving attendance as an example, and we know attendance figures are often disputed betweeen promoters and reporters (some more often than others), we can deduce that Gran Metalik's moves are even less controversial. Cases may arise where one source disputes another's claim about whether or not a wrestler used a move, but I can't remember ever seeing that happen. Regarding conflicting information about this man's clothesline, we'll cross that bridge if we come to it. The general controversy here is simply among regular people and pertains only to the inclusion of moves on Wikipedia; it does not carry over to claims about the moves themselves. InedibleHulk (talk) 19:45, July 17, 2018 (UTC)
One of the solutions for this, is a prose version of the section, where clearly notable information could be written into the "persona" section. If a move is very easily sourced, and is clearly notable, then it can be mentioned here. The main issue with the section is that the information is baseless, and rather irrelevent to the WP:BLP for the article. What's the point of saying what moves the person uses, if it isn't expanded on? Lee Vilenski (talkcontribs) 07:43, 17 July 2018 (UTC)
  • Yes; Wikipedia does not need to include all the information that exists. There are no similar lists for other types of performance artists, and anything like this for other performers would be deleted as fancruft. (Imagine allowing things like lists of best high notes at live performances for every singer in popular music…) Just because there are secondary sources for this particular sort of trivia does not mean we need to have standardized sections for this trivia. Jc86035 (talk) 15:56, 17 July 2018 (UTC)
  • If this were in a video game article, it would removed per WP:VGSCOPE. --Izno (talk) 16:42, 17 July 2018 (UTC)
  • No Absolutely not there's quite a few people who came to find this place to complain about the sudden information loss caused and I've talked to a few outside of here who are absolutely disappointed. It was a guide that gave you a quick and dirty rundown for casual viewers. Granted it was sloppy and could have been formatted better, but it was a very useful guide to learn about what a wrestler does really quickly. You could gain so much insight into their style in a couple seconds and what that wrestler is looking to do. A lot of people are upset and I'm included in this. Seriously, you get an understanding of 'oh he's got a DDT so when he goes for the front headlock he's looking for that and I should get on my feet when it's cinched in. Long story short: You don't just rip useful things out because they are ugly. Find a better way to present it if you must, but to know the cornerstone of a wrestler's moveset without mulling through a long article (which may not mention it) is important. Klichka (talk) 06:34, 18 July 2018 (UTC)
Wikipedia isn't designed to provide this type of information to fans. See What Wikipedia is not. It's not because it's ugly, it's due to the fact this type of information is WP:FANCRUFT, excessive information that doesn't help the reader learn about the subject. Simply denoting that they were once managed by Jimmy Hart, or that they do a brainbuster finisher doesn't help the reader learn about the WP:BLP involved. Lee Vilenski (talkcontribs) 07:58, 18 July 2018 (UTC)
I have to object to your assessment. The finisher tells me exactly what they are shooting for, what kind of setup to look for when I watch the wrestler for the first time. Also, some wrestlers are defined by their moves. Jake The Snake is defined by that DDT, he innovated it, in a few seconds I can learn that the pinfall after a DDT means something without having watched him. I can learn a hint that Hulk Hogan had an altered moveset in Japan. Quite a bit of wrestling psychology has been based on the idea of two wrestlers trying to get their finisher in. For quite a few people you're kind of talking about what they are about. Klichka (talk) 04:23, 19 July 2018 (UTC)
Read the Roberts article, the lead "he was known for ... his invention and use of the DDT finishing move". The info you're missing is in the first part of the article. If not, you can create a pro wrestling persona section and include it, like I did with Vader o Lesnar. --HHH Pedrigree (talk) 09:51, 19 July 2018 (UTC)
  • Yes I started this so feel I should comment here. My original request at the wikiproject was not to have it deleted, I was just looking for a solution to a problem that I saw as an outsider. Deleting the section is a valid solution to that problem, as would have been renaming, and I was pleasantly surprised to see the wikiproject take my concerns seriously. I think some of the No !voters above are missing the point of this discussion. It is not to blanket remove the information from wikipedia, it is to remove the information that is not (or poorly) sourced or not notable in the context of a biography. The rest will be incorporated into the prose regarding their career. Sure there may be a bit of disagreement on what is notable or even what constitutes poorly sourced, but that is what talk pages are for. This is normal editing practise and always improves the encyclopaedia. I feel this has been a positive step for a wikiproject and area that has been much maligned recently. AIRcorn (talk) 07:19, 19 July 2018 (UTC)
    • Actually, I would suggest that you have missed the point of the discussion. I don't know that anybody is pushing for keeping all of the information. I think the moves should be trimmed--drastically, in some cases. One of the big objections is to the prose format, in which information is much harder to find, not to mention the fact that the wholesale removal of the content from thousands of articles would mean that a prose section would need to be written for thousands of articles. The section functions well now, and the biggest arguments being used against it are cruft and verifiability. However, when the solution to remove the cruft and source the content is discussed, that's still not good enough, for some reason. It's absolutely baffling--I have written for dozens of actual encyclopedias, yet Wikipedia is the only place I've written for in which editors are concerned that the content might be considered useful or easy to read. GaryColemanFan (talk) 03:00, 20 July 2018 (UTC)
  • Yes. The section tends to lean towards trivia and is quickly cluttered with signature moves which hold no major importance, significant finishers and signatures can be incorporated into the new (better referenced) "Wrestling persona and style" section. Greyjoy talk 06:33, 20 July 2018 (UTC)
  • STRONG NO. I joined Wikipedia and instantly associated myself with the WikiProject Professional wrestling, during the climax of the Yes! Movement, a period where professional wrestling had a high reputation, and this was halfway into this decade long precedent for the highly inclusive and useful "in wrestling" section. However, a mere four years later, a group of deletionist/exclusionist Wikipedians who hold bureaucratic, asinine control of a WikiProject that tens of thousands of fans, if not even more rely on for useful information, including the "in wrestling" section, had a very oligarchic discussion selling out to their deletionist/exclusionist policies and choosing to remove the section and alienate the thousands upon thousands of fans who relied on it for CAWs, understanding a performer's wrestling style, knowing who managed who, what music he came out to, and so forth. I spent all last night reading all about it and what people have said, and this is what I have to say about it. This was a poorly thought out move made by selfish Wikipedians who only care about their deletionist/exclusionist views and obstructing free knowledge, at the expense of the greater good who read articles for information like these. I just don't see why the use of inclusionism would hurt in this case. An example of inclusionist thought supporting the "in wrestling" section is a quote from site founder and fellow inclusionist Jimmy Wales, who stated "Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. That's what we're doing." Many people come to Wikipedia for this information because of the site's high reputation, easy access, and visibility. It would be much harder to find this information on another site because this site is more clean and visible than another. If the information is benefiting many people and its exclusion is hurting many people, whats the point of excluding this information. Trivial and fancruft? Sure. Does that make it excessive and unnecessary? In this case, hell no! In some deletion reviews, despite a vast majority saying delete, sometimes a redirect vote or two opposed to the majority will result in a inclusionist redirect due to there being "plausible target" for one. I feel that keeping the "in wrestling" section, despite its deletionest-regime policy issues, has "plausible target" for the hundreds of thousands of fans who relied on this information in the articles who are now alienated and outraged because of a few deletionist's bureaucratic, authoritative decision that disregarded the needs of the readers. Putting it in prose will exclude lots of information and make knowledge that was once easy and helpful become hard and impossible to come by. And do not come at me with this "fancruft" and "ilikeit" policies, because I am sure as hell not selling out to these deletionist/exclusionists who are going against what Wikipedia stands for and killing it's heart and soul. The only reason this happened anyway is because of the backstage deletionist policies of Wikipedia. I cannot assume good faith about these oligarchists because they only care for their views and not the people's, and they've pretty much caused a situation similar to those like the beating of Rodney King and the 1992 Los Angeles Riots, the 1770 Boston Massacre, the Ferguson Shooting of Michael Brown, the Death of Freddie Gray resulting in the 2015 Baltimore Riots, the Shooting of Trayvon Martin, the Death of Eric Garner, the protests and outcry regarding Donald Trump and his policies, and so forth, except that this involved the "murder" (deletion) of a section titled "In wrestling", and the Internet Wrestling Community is providing harsh backlash to the decision, yet the deletionists ruling over it don't give a fuck and only care about their needs opposed to others. And no, I'm not being uncivil, I'm just passionately delivering my and many other's opinion regarding this matter. I appreciate all of you taking the time to read over this. Please consider it. That is my speech, titled "A Modest Wrestling Information Proposal'. DrewieStewie (talk) 09:20, 20 July 2018 (UTC)
  • DrewieStewie so first of all it is disheartening to read such an uncivil response, especially one that paints a group of people who are all regular editors of professional wrestling articles - you know those articles that really help you understand a wrestler to know that Some NXT guy is using CFO$ "Insert name here" theme. Your hostility undermines your point and surprises me that the removal of entrance themes etc. draws such a vitriolic response from readers. On the other hand it does seem to draw a lot of readers to actually edit Wikipedia for the first time, maybe it'll draw them to actually edit in the future. Also Trivial and fancruft? Sure - that is a large part of the "delete" view right there, both of which are discouraged on Wikipedia. The "keep" contingency seems to think that Wikipedia is just this bucket that anyone can fill with any and all information, like a hippie society there are no rules, just a free for all. That's not what Wikipedia is, that's not what "Jimbo" or anyone else who've helped build Wikipedia are saying.  MPJ-DK  10:46, 20 July 2018 (UTC)
  • DrewieStewie's comments above may be the most disgraceful that I've seen in all my time here on the encyclopedia. I'd consider taking this to WP:ANI but I think there are enough admins on here to handle it if they choose to. Please remember that general sanction now apply for pro wrestling. We can disagree on whether or not it's best to reshuffle bullet-points into the prose but you cannot compare the other side to racists and murderers. Good grief!LM2000 (talk) 11:15, 20 July 2018 (UTC)
  • Drewie, since you have presumed to speak the mind of the venerable community elder Jimbo Wales on this matter, I will do him the courtesy of a ping--which is more useful to our purposes here than a link to his article (believe it or not, we know who he is). I understand that you have mentioned below that you authored that message in a heated state, but while you have admitted that some of the tone of your message was ill-considered, I must respectfully suggest that perhaps you need to consider how solid your reasoning is as well, as with that Jimbo-based line of commentary. Because I'm not aware that he has ever self-identified as an "inclusionist"--boy am I tired of that dichotomy, regardless--and parroting his most famous quote, the mantra of the project, doesn't really prove (or even suggest) where he falls on spectrum of editors on such matters. We all believe in the encyclopedia anyone can edit, and we all accept that it should touch on the many disparate avenues of human experience, inquiry, and endeavour. But it is just as manifest and widely accepted a principle that the encyclopedia is not all things that all people want it to be, nor can our coverage of a given topic be all inclusive of everything every editor wishes it to be. That's just clearly an infeasible approach. So the community has developed a rather detailed framework for deciding what should come in and in what format, with the caveat that individual circumstances often require further nuancing. Keeping fidelity with those policies does not make an editor an "inclusionist", nor a "deletionist", but rather just someone who has faith in the idea that our collective pragmatic wisdom is better than the sum of its parts and, absent really compelling reason for varying the approach of policy (that is, community consensus) in an instant case, we ought to opt for consistency in following said consensus. Snow let's rap 13:26, 20 July 2018 (UTC)
Thanks for the ping. I'm afraid my comment will probably not shed much useful light on anything, but here goes. :-) I think that lots of things should be in Wikipedia, and some things should not. I'm neither an "inclusionist" nor a "deletionist" by nature. I like to call myself an "eventualist" which means that if we get something wrong today, we'll probably get it right eventually. But what I do think is that we are far more likely to get it right sooner rather than later if we all pause to listen to each other, if we actually "try on" the other person's "shoes" so to speak, before we get too heated. For many of the most difficult questions of inclusion or deletion of any particular thing, there are plausible arguments on both sides, and we have to weigh up the balance thoughtfully. We won't always agree, but when we pause to realize that those who weigh things differently are probably not being horrible people, we're more likely to be wise on our own weighing. Separately, Wikipedia:Argumentum ad Jimbonem is a fun read, whenever someone wants to cite me as an authority for anything other than "Please everyone relax a notch or two, and let's be kind to each other and have fun."--Jimbo Wales (talk) 18:56, 20 July 2018 (UTC)

MPJ-DK, LM2000, and Lee Vilenski, I sincerely apologize for coming off as overly harsh right there. I was in an extremely bad mood over something in my private life that isn’t appropriate to share on here, and while I’m still a little upset, I’ve regained my composure. I’m also apologising for my harsh attacks and overly political comparisons. But anyway, a much nicer and not so controversial way to put it: while it is trivial and cruft, I feel it is relevant and reasonable to enough people to not be “fill-up bucket” type information either. That’s the basic jist of it, no politics included. It’s safe to keep everything I said up there, as I’m not gonna try to hide or deny and be honest about what I said. But I do want to make clear more than anything, I apologize for my extremely uncivil, pissed off response. That totally isn’t me. :) DrewieStewie (talk) 11:47, 20 July 2018 (UTC)

Don’t apologize at all! Every single thing you said it true! They don’t like that the truth is coming out & they have nothing to hide behind! All they got to do to “fix” it is bring the “In Wrestling” section back & this would all be over! They know it but they refuse to accept the truth!OnlyRealSpike (talk) 13:11, 20 July 2018 (UTC)

OnlyRealSpike I mean, I totally agree. I agree with what you said too below. I just didn't want to cause any more trouble and put my account at risk though. I stand by many of the stuff I said, but I feel retrospectively that doing stuff such as comparing these otherwise innocent humans outside of this problem to grim real life events was just simply a step too far and inexcusable on my part. You feel me?— Preceding unsigned comment added by DrewieStewie (talkcontribs) 09:20, 20 July 2018 (UTC)

Harsh, yes, but it was needed to get their attention. They want to compare apples to oranges & you just brought real-live to it & it makes them mad. You called them out & got under their skin. But I am sick & tired of them saying 1 thing (calling this a “discussion”) but they already did what they are “talking about” doing! They got the cart before the horse & that is ass backwards! If you knew how I had been treated from the start (before I registered & was just my IP address)….got called “trivial” & “insignificant”, got blocked for a week & just got back I couldn’t care less if they like what I say….don’t hold back, I speak the truth & they despise me for it! This whole thing is nothing but a scam & it pisses me off!OnlyRealSpike (talk) 13:37, 20 July 2018 (UTC)
I think we're getting dangerously close to Godwin's law territory here. --Ahecht (TALK
PAGE
) 13:42, 20 July 2018 (UTC)
Ahecht - Godwin's law may only be half of this. I feel like we may be near to dividing by zero Lee Vilenski (talkcontribs) 13:48, 20 July 2018 (UTC)
To paraphrase one legendary wrestling announcer, this place has literally gone bananas!LM2000 (talk) 18:34, 20 July 2018 (UTC)
  • No Yes, but replace with the "professional wrestling persona" section. Some information naturally lends itself to being displayed in list form rather than prose. "Finishing moves" are a staple feature of biographies on wrestlers - try finding a wrestler's biography that doesn't mention them. And, as this discussion illustrates, this information is clearly of interest to a significant subset of readers. Issues around sourcing and presentation are not a valid rationale for purging the information altogether. McPhail (talk) 19:53, 20 July 2018 (UTC)
For any neural networks or staunchly literal humans trying to follow along at home, an abundance of information in a particular set of resources is not a valid rationale for aiming to isolate and utilize less-informative resources in this unending pursuit of knowledge. You will just run into a loop that way. What my rhetorical friend here is "trying to say" ("as they say") is: Try finding a wrestler's biography that does mention them (them being the moves). InedibleHulk (talk) 20:49, July 20, 2018 (UTC)
And for the smaller minority of wrestling/true crime fans who also happen to read too far into things, don't let my esteemed colleague's adoption of The Zodiac's signature fool you: The man behind the murders has long since been murdered and the man of a thousand names has't terrorized a New York subway station with deadly laughing powder in years. McPhail has voted my way on certain issues, so I won't stand for potential rabib mobs attacking him for giving his position a second thought! InedibleHulk (talk) 21:13, July 20, 2018 (UTC)

Wrestling discussion

I do NOT like that the “In Wrestling” section listing “Fishing Holds”, “Signature Holds” & “Theme Music” has been removed! I am trying to look up some wrestler theme songs & that has always been my go-to for looking it up but that is impossible to do when they have been removed! Where else can that be found? NOWHERE AT ALL! — Preceding unsigned comment added by 2602:306:CCE0:8550:81DD:D18E:1485:114A (talk) 16:32, 10 July 2018 (UTC)

  • Sorry, but that's not what Wikipedia is for, to be your go-to source for information deemed trivial (and usually poorly verified) by Wikipedia editors. Drmies (talk) 16:33, 10 July 2018 (UTC)
  • I don't understand how this information is "trivial". Wikipedia should absolutely be your "go-to source", why would you want to send users elsewhere by making this vital information pertaining to a wrestler's character much harder to find? — Preceding unsigned comment added by 71.14.197.130 (talk) 18:54, 10 July 2018 (UTC)

Worth noting that /r/SquaredCircle on Reddit and possibly other professional wrestling communities are now aware of this discussion. Prefall 18:17, 10 July 2018 (UTC)

Yup, sorry to keep dragging this out for you guys. We value the information a lot though, and see a lot of encyclopedic value in it. 67.244.146.250 (talk) 20:41, 10 July 2018 (UTC)
That's alright; I for one appreciate that the original comment of that Reddit thread does make an effort to contextualize matters and encourage involvement here to conform to our local rules. Predictably, a fair number of people participating there are instead encouraging or demonstrating proclivity towards more disruptive attitudes and tactics, but if they arrive here looking to effectuate that approach, they will find we have significant mechanisms in place to put onerous, uncivil, tendentious, or generally disruptive participants outside of the discussion entirely. I do think that it is likely that the closer of this discussion will take into account that a lot of opposing !votes come from WP:SPA's and factor that into their analysis of the consensus, but so long as SquaredCircle's community members come here to share their opinions in a cogent, civil, and principled manner, they are welcome and will be heard out. Snow let's rap 23:09, 10 July 2018 (UTC)
You guys kept saying people coming from other sources because they were told to. I ultimately disagree, as i see it the majority came here on their own will, because they saw this important information of Encyclopedia section "IN wresting" missing,so they found own way to this discussion/vote/security. Colton Meltzer (talk) 19:57, 11 July 2018 (UTC)
I find that somewhat improbable, given how byzantine Wikipedia projectspace is for a newcomer and the fact that at least four of the above accounts that I've checked were registered immediately after the SquaredCircle call to arms. But it doesn't really matter: everyone is welcome to comment here, provided they follow the rules, treat others civilly, keep comments focused on the matter at hand, and at least make an attempt to understand how community consensus works on this project. Snow let's rap 21:56, 11 July 2018 (UTC)

As I saw in the previous discussion, the In wrestling section has some policies against it. Finishing moves, sources don't include the technical description of the move, so it's OR. Signature moves it's clearly OR since it's hard to find a source saying "signature move". At the end, we made SYNTH (he uses the move X times, it's signature) Nicknames, people includes every YouTube video or promo as nickname (I removed severals and I find again in the article some days later). Entrance themes, for me it's pure trivial. --HHH Pedrigree (talk) 19:07, 10 July 2018 (UTC)

Soumds like there has to be Wikia-wikis about this stuff somewhere? Gråbergs Gråa Sång (talk) 22:14, 10 July 2018 (UTC)
The Pro Wrestling Wikia could work, though it is poorly upkept and a majority of it is copied from here. JTP (talkcontribs) 22:21, 10 July 2018 (UTC)
Entrance themes are part of the character portrayed by the wrestler. Further, change in entrance music also signifies major changes in the character being portrayed. Similarly to articles about musicals or other theatric performances, the music is certainly not trivial (e.g., Cats_(musical)). Secondly, the finishing moves are also part of the character being portrayed. Again, if a character omits or adds certain moves which in general finish a match, these changes indicate change in the character being portrayed. Furthermore, one important part of storytelling is whether the wrestler innovated the finisher, and if another wrestler adopted this finisher from their trainer. If anything, there should be more information regarding the finishers pertaining to the evolution of the character, in particular if they are the innovator, or whether the move was passed on from someone else. All these details are historically significant not only for individual characters, but for the wrestling performance as a whole. In general, it is my opinion that articles about wrestlers should not be treated as articles about athletes, but rather as articles about fictional characters. JackKasket (talk) 03:13, 11 July 2018 (UTC)
  • So here is my counter, if it's so important would a list actually help inform the reader of any of this? I don't see where a list convey the "historical significance" that you mention.  MPJ-DK  03:44, 11 July 2018 (UTC)
  • I would argue that a timeline would be the optimal representation, similar to Carcass_(band)#Band_members. However, maintaining this would be a nightmare, in which case the second best option would be Current/Past lists. Basically, treat this information similarly to other performance arts.JackKasket (talk) 03:57, 11 July 2018 (UTC)
  • How is someone's theme music & move set any different then the number of championships someone has held? For many of of them, their championship listings (in every single promotion they have been in) is much longer then the theme songs they've had & moves they've done. So why take out (all of the) the theme songs & moves but keep (all of) the championships? If you keep the championship reigns they you should also keep the theme music & move set....that just makes logical sense! — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 12:59, 11 July 2018 (UTC)
Championships and awards typically receive far more coverage in reliable sources and are generally more notable to the subject. Entrance themes rarely receive any coverage, which is why most of their inclusions is supported by an iTunes Store link or a database entry (which does not establish notability). Sidenote, signature moves is not intended to be a "move set"—a common misconception and one of the reasons it is better left omitted. Prefall 13:17, 11 July 2018 (UTC)
Let me ask this: say,, if, for example, someone wanted to have (or has) wrestler theme songs on iTunes. Now, let’s say they want to list them in chronological order (starting with Seth Rollins’ 1st theme & ending with his current theme, etc. with other wrestlers). The same holds true with TV programming (Raw, SmackDown, NXT, etc.) or PPVs & so on. Where would people find them, if not on the wrestler pages where they’ve been? You can find the TV programming opening theme. But where is that on the wrestler pages? Please don’t tell me on the “WWE Music Group discography” page because that is only a listing of when the songs were released on iTunes & only those that were released by WWE’s musical department, not if a Kid Rock song is used, etc. Is that not reason enough to keep it? Is that not a historical reference of the character’s development? Why is it not an issue to list the TV show themes but it’s a problem to list the wrestler themes? Someone may want to know what theme song(s) A.J. Styles used when he was in TNA & not just his championships! As for awards/accomplishments, who cares how may times he has been Pro Wrestling Illustrated or Wrestling Observer Newsletter’s Wrestler of the year or in match of the year or how many times he’s won a “WWE Slammy”. Furthermore, a Slammy is not really an award par-say but a gimmicky thing. What about Booker T (or anyone else, for that matter) being listed with a “Hall of Fame” award where there isn’t really a hall of fame? That, too, is a gimmicky thing but it’s still listed? So how are championships & accomplishments really any different then theme music & moves? — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 15:03, 11 July 2018 (UTC)
WP:OTHERSTUFFEXISTS is not a valid argument...if you want to start a discussion to remove than section go ahead, but that has nothing to do with the matter at hand. - Galatz גאליץשיחה Talk 15:52, 11 July 2018 (UTC)
Yes it does! It has EVERYTHING to do with it! It is ABOUT a segment the content THAT IS BEING removed as opposes to contest that is being kept! That makes it VERY relevant to the matter at hand! Furthermore, let me also draw your attention to parts of the very article: “these comparisons are important as the encyclopedia should be consistent in the content that it provides or excludes”, “legitimate comparisons are disregarded without thought or consideration” & “it is important to realize that countering the keep or delete arguments of other people, or dismissing them outright, by simply referring them to this essay by name, and nothing else, is not encouraged” which is exactly what you have done! Therefore, I do make a very valid point! Man, I hate when I’m right…. — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 17:17, 11 July 2018 (UTC)
I appreciate discussion as much as the next guy, but can we at least keep it civil? Snarky comments like "Man, I hate when I'm right" irritate others and are downright rude. Thanks. JTP (talkcontribs) 19:56, 11 July 2018 (UTC)
When Prefall made a overhaul, i agreed with the changes (except for "In Wresting") as stated on previous posts discussion with reasons. This right here, almost like "Donald Trump wins the 2016 President Election fairly" Where this In Wresting section was removed fairly anger many many people. Colton Meltzer (talk) 20:12, 11 July 2018 (UTC)
I am not trying to be snarky - I am being sarcastic, there’s a difference. You my thing me saying “Man, I hate when I'm right” is snarky, but I think being told my comments/opinions “is not a valid argument” is snarky. I quoted an article - apparently intended to discredit my comments/opinions - that clearly states not to do what was done to me. How, exactly is THAT not being snarky? You want to talk about being “civil”, since when was it a crime to make a sarcastic remark when I am being insulted? Isn’t THAT “downright rude”? If I am going to be attacked I am going to fight back so please don’t accuse me of being “snarky” but let others be rude to me & insist on how “wrong” I am - just because someone does not agree with me does not give them the right! I make very valid points, rather or not you or anyone else like them or not! I stand by every single word I said - theme music should NOT be removed & nonsense like Match/Superstar of the Year it kept! You may call this “snarky” but I don’t care….prove me wrong (the entire statement, not just what should/shouldn't be removed)! — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 20:44, 11 July 2018 (UTC)
Championships are gimmicks too. Slammy Awards also have numerous categories that have been legitimately fan voted. Anyway, the difference is that these items typically receive far more coverage than much of the content contained within the "In wrestling" section. But if you think other items should be removed too, a separate discussion can be created.
Most entrance themes are simply not significant to the performer and thus do not receive much coverage outside of a retailer listing or "listen now" link. A catalog of entrance themes being WP:USEFUL is not the greatest argument. WP:Wikipedia is not an indiscriminate collection of information comes to mind. Now, if a theme is actually significant to their persona and has received notable coverage, it can still be written into prose. A couple examples is Steve Austin's "glass shattering" soundbyte ([27][28][29]), or Triple H's use of Motörhead and friendship with frontman Lemmy ([30][31][32]). Prefall 22:48, 11 July 2018 (UTC)
I reiterate my previous point: “what if someone wanted to have (or has) wrestler theme songs on iTunes. Now, let’s say they want to list them in chronological order (starting with Seth Rollins’ 1st theme & ending with his current theme, etc. with other wrestlers). The same holds true with TV programming (Raw, SmackDown, NXT, etc.) or PPVs & so on. Where would people find them, if not on the wrestler pages where they’ve been? You can find the TV programming opening theme. But where is that on the wrestler pages? Please don’t tell me on the ‘WWE Music Group discography’ page because that is only a listing of when the songs were released on iTunes & only those that were released by WWE’s musical department, not if a Kid Rock song is used, etc.” I think that is that not reason enough to keep it! Like I had asked before, “Why is it not an issue to list the TV show themes but it’s a problem to list the wrestler themes? Someone may want to know what theme song(s) A.J. Styles used when he was in TNA & not just his championships!” Therefore, I beg the question: if someone can’t look up somebody’s theme on Wikipedia anymore, then where EXACTLY can they? From what I have seen, NOWHERE WHATSOEVER! Wikipedia is the ONLY PLACE that someone has EVER been able to locate that information! Taking that away is completely unacceptable!
Then they can go on the wrestling Wikia. I'll reiterate the point that Wikipedia only summarizes stuff that other reliable sources have published, so the fact that it doesn't exist elsewhere is a perfect argument against including it here (see also WP:ITSUSEFUL). --Ahecht (TALK
PAGE
) 20:45, 20 July 2018 (UTC)
I don’t care how “insignificant” you think theme music is or how “significant” you think championships are! Have you ever thought that theme music MIGHT VERY WELL be significant to people that WANTS to know that stuff? Bet where do you expect them to go to get that information? Just because it isn’t significant to you does not give you the right to dictate that it can’t be to someone else! — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 23:25, 11 July 2018 (UTC)
I beg the question: if someone can’t look up somebody’s theme on Wikipedia anymore, then where EXACTLY can they? Some have recommended that this content would be much better suited for a fan Wikia, such as the Pro Wrestling Wikia. This extends beyond entrance themes too—for a lot of detailed information that is not hosted here. Prefall 23:44, 11 July 2018 (UTC)
That is WAY OUTDATED! I saw the posting you are talking about & I already looked there but guess what? It is WRONG! For example , there are SEVERAL that I have seen that are NOT accurate! That [still] lists Bianca Belair’s theme as "We Do It Better" (WWE; 2017-present) & Lacey Evans’ theme as "Bad Girl Good Boy" by Kimberly Korn (NXT; October 20, 2016 – present) but before it was taken down Wikipedia said that Bianca Belair’s current theme is REALLY “Watch Me Shine” by CFO$ & Lacey Evans’ is “Like a Lady” by Nancy Rowland! That is JUST A SMALL EXAMPLE of MANY which right there in itself PROVES that you have NO IDEA WHATSOEVER what you are talking about regarding that site! I did not pull that out of my butt so clearly you can’t even get your facts straight! — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 00:15, 12 July 2018 (UTC)
Then go fix that specialist site instead of mucking up this general one. Ian.thomson (talk) 00:17, 12 July 2018 (UTC)
Also, your behavior including SHOUTING IN ALL-CAPS is uncivil bordering on disruptive. Please stop.--WaltCip (talk) 02:15, 12 July 2018 (UTC)
Because I am not a “specialist”….but apparently you think you are if your attack me for speaking the truth! Learn some common sense, people! Oh, that’s right, I forgot….common sense ain’t too common anymore - people are stuck on stupid….
Maybe I gotta use all caps to make a point because clearly nobody is smart enough to understand what is clear as day right in front of their faces….it’s enough to make me sick. — Preceding unsigned comment added by 2602:306:CCE0:8550:418D:E52E:5D61:A083 (talk) 03:11, 12 July 2018 (UTC)
Ok, not withstanding my defense of your questionable all caps habit below, the actual content of your comments is getting increasingly incivil; I would like to direct you to WP:CIV which you will want to read before commenting further here. Civility is one of our five pillar policies in this work space and you will find we take it very seriously. Not only are the liberal "you are so stupid" comments pretty much guaranteeing that anything you have to say about the content is being discounted whole-cloth, but you are very likely to find yourself banned from further participation if you keep it up. We have a low tolerance here for people who bring "more heat than light" to content discussions and the community just recently decided to put the topic area of professional wrestling under WP:general sanctions, because you are not the only visitor from a wrestling community who has shown a refusal to avoid speaking abusively to other contributors here. General sanctions being in effect means that the fuse you light with unkind terminology is shorter than normal and will lead to a block quite quickly if you can't show the self-control necessary to discuss matters without resorting to insults and other WP:personal attacks.
That addressed, I think you should know that when Ian references "specialist" Wikias, he was not talking about platforms that require any more technical knowledge than Wikipedia does, nor expert knowledge of pro wrestling. Wikia is like Wikipedia (created by some of the same people in fact): it is open source and mostly community run. Everything that has ever been added to Wikipedia regarding pro wrestling could be replicated there. What we mean when we say "specialist" is that Wikipedia was never intended to be a wharehouse for all possible information on a given topic. Our objective here is not to preserve every bit of human knowledge on any given topic, but rather to provide an encyclopedic summary of encyclopedic topics. Let me elucidate with an example: let's say you like to play video games. Would you come to Wikipedia to find out how to play a given game? No, you'd come to Wikipedia to learn about the release date or critical reception or development history of the game, but you'd go to a Wikia to learn how to navigate the water level without putting your foot through the TV.
That is what others are talking about here when they suggest Wikia as a place where you could relocate this information, if you were so inclined. And if you aren't willing to pitch in to preserve this content that you feel is so important, then perhaps its not really that important--and demanding we cater to your needs is a tad bit of an entitled way to look at this situation? I knew very little about the technical side of this project when I started editing on Wikipedia, but I kept at it and I'm proud of the content I have created and maintained for the benefit of this with an interest in the topics I can help make available. It doesn't happen over night, but only you can decide if it is worth the effort. Meanwhile, we have bigger fish to fry with regard to maintaining our articles than "Oh, all caps guy liked that The Impalanator once entered to ring to Fat Bottom Girls and ended a match in 1998 with a triple-suplex. Guess we have to rethink this whole thing." That is perhaps appropriate for a Wikia index, but not useful summary information for an encyclopedia article.
When I was reviewing that SquaredCircle page, I noticed that the group had something like 356 thousand subscribers--twelve thousand were online WHILE I WAS READING IT. (See, a little emphasis in moderation goes a lot farther). If just one in a hundred of those subscribers has some Wiki-editing experience and/or a little bit of patience and time to give to a community project (rather than wasting it yelling "idiot" at us here), then that is 3,560 editors for your new project! Do you know how much work that number of editors can get done in short order? In all of the physiology and cognitive science articles I work on, I bet there are fifty total regular editors that I would recognize as reliable editors working in those same areas, if that. Maybe we're not the ideal targets on which to spend your considerable energy and motivation to maintain this informations somewhere in an organized and centralized manner? Snow let's rap 04:03, 12 July 2018 (UTC)
I'm a bit confused as how the consensus was achieved to remove the "In wrestling" -section altogether? On one hand, editors are arguing that the information is mostly/all trivial, which I disagree with. On the other hand, editors are focusing on the difficulty of maintaining that section and cruft that it attracts (as opposed to the content being trivial). These two reasons seem contradictory in the sense that I do not see any evidence of a consensus being achieved that would justify the sudden removal of the section from all articles. JackKasket (talk) 06:57, 12 July 2018 (UTC)
The consensus in question does not yet exist; that is the purpose of the present thread. It may be that you will find some more information about the original thinking behind these reforms at WP:PW, where the original discussion took place. However, because that space is a WP:WikiProject the editors who originally responsible for promoting this change in approach where told that they would have to host a larger discussion before this could become a default approach for all wrestling articles. This is because we have a policy here (WP:Advice pages) which prohibits WikiProjects from unilaterally deciding on changes to be applied over a large number of articles without broader community input/vetting (many years ago we had some WikiProjects which tried to create default rules for every article they felt was in their purview and it got to be quite disruptive). However, if a consensus approach arises out of this discussion, it will be considered a valid default approach for all wrestling articles; variations will still be allowed, but editors will have to meet a much higher burden of proof / win an explicit WP:LOCALCONSENSUS discussion on individual articles in order to ignore this default rule, and that will be very difficult. And because WP:General sanctions will be in effect on those articles, admins will be able to sanction those who disruptively ignore the consensus established here. In effect, this discussion will have almost (but not quite) the effect of a WP:GUIDELINE. If this is all a bit confusing and byzantine-seeming, trust me that you are not alone in that. This is a case of what I would call "advanced" (or at least intermediate) policy work; I would expect that even some very experienced editors might be confused about how this whole thing unfolded and what the impact of this discussion is; if I have failed to explain the matter in a way that makes sense, let me know and I will attempt to clarify.
I agree that there do seem to be multiple competing theories as to why the "In wrestling" section should be traded in for a conventional prose section (as indeed there are multiple theories asserted by those who see value in it, although not all of them very well based in our policies). In addition to the arguments you note above, there is also a feeling amongst some respondents here that WP:PROSE is controlling; in general, we expect content on the encyclopedia to be written in full prose that allows for contextualizing information, where possible. There are also WP:V arguments regarding removing the content, but I am not won over by those; there are many cases with regard to entertainment media where we allow the subject to be its own self-verifying source (plot summaries, for example, usually do not need to be verified by an independent source). However, there are legitimate WP:WEIGHT concerns. Personally I do not see why the WP:TRIVIA and WP:CRUFT-attraction arguments are mutually exclusive, so you'll have to further clarify for me why you do. I also think both the WP:PROSE and WP:WEIGHT arguments raise valid concerns. However, even if some of these different concerns were in conflict with one-another, they could still all point us in the same general direction (imagine you have three legislators in an assembly; one wants to lower the speed limit in municipal areas for safety reasons, another because of the wear on infrastructure, and the third because they want to curb greenhouse gases; they don't all have to have the same motivation in order to stand on the floor and advocate for a change, and the circumstances are similar here). The WP:CLOSER of this discussion (which in this case will probably have to be an admin) will have to find a way to interpret a general consensus from the disparate opinions provided here, weighing all of the opinions, trying to find common ground amongst them, and considering them in light of previous community consensus and already established policies and guidelines. In doing so, the relative numbers of editors supporting one approach or another will be considered, but they will not be strictly determinative of the outcome; the closer can reject a statistically more numerous perspective if they find there is good reason (for example, if the outcome would conflict with a policy that has even more community support), although that is a very rare outcome. The discussion could also be resolved "no consensus", which would be a very bad outcome in this case, as it would leave everybody hanging in limbo and locked in dispute over the appropriate format of these articles even as they come under general sanctions--a recipe for disruption and rapid-fire sanctions.
I hope there is more clarity in this reply than overwhelming bureaucratic project-speak. Again, if I can do anything to make matters clearer, please say as much here or on my talk page. Snow let's rap 07:37, 12 July 2018 (UTC)
  • Thank you! I'll have a gander on the surrounding discussions as well. JackKasket (talk) 08:30, 12 July 2018 (UTC)
(edit conflict) Ehh, I'm sure you and I are not the only ones who would rather they didn't do it, but there is absolutely nothing anywhere in policy or community consensus that says it is incivil or per se disruptive to use all caps, and I wouldn't hold your breath on that ever changing, because flexibility in expression is a value that has a lot of currency in this community, for good and ill. WP:TPG does (wisely) recommend avoiding all caps as "good practice", but there's no requirement.
Personally, I've always found strong reactions to all caps to be puzzling. It is often analogized to shouting because it was often used that way stylistically in written dialogue (not so much literature as often as comic pages and such), but that doesn't mean it actually has the effect of shouting. There are reasons shouting is often considered obnoxious in many contexts; at it's loudest it can actually physically hurt your ears and even at lower volumes it has a physiological stressing effect on people. But neither of those things is true for all caps; in order for it to have an effect upon another person, it has to be mediated through a recipients psychological filter. Meaning it only causes an elevated state of arousal from with participation by the recipient; as opposed to actual shouting, which causes this response rather instinctively regardless of a strong interpretive outlook on the part of the recipient.
Anyway, returning the behavioural policies, I don't think it is fair to describe the all caps habit itself, as regards any firm community consensus, as "uncivil bordering on disruptive". Obnoxious and self-defeating seems accurate though! I would say that it's more the content of what the IP is saying that is getting closer and closer to uncivil, not the way they are saying it. Snow let's rap 03:25, 12 July 2018 (UTC)
Oh, so I suppose you are going to say I was never attacked? I am not allowed to fight back & defend myself when **I** am attacked 1st? Take a look at all the insults & rude comments thrown my way **before** I ever said anything! As I’ve said before to someone else - get your facts straight!— Preceding unsigned comment added by 2602:306:cce0:8550:d424:64a0:7b5c:a6e5 (talk) 09:11, 12 July 2018‎ (UTC)
Just because people don’t like what I say or how I say it doesn’t make it any less true….I speak the honest to God truth - always have, always will!~~ The Greatest — Preceding unsigned comment added by 2602:306:CCE0:8550:D424:64A0:7B5C:A6E5 (talk) 13:00, 12 July 2018 (UTC)
Man, I'm on your side of the argument but you're being illogical, stubborn and toxic. Please. Jcw91 (talk) 03:32, 13 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────

Where did anyone actually say anything about you as a person? Quote something. Presenting logical arguments that you happen to dislike, pointing out problems with your attitude and behavior, and pointing out problems with your arguments are not the same as actually attacking you. Users have repeatedly asked you to behave in a civil and mature manner and if the next response I see from your IP range is anything but that, I'm going on ahead and blocking. Ian.thomson (talk) 16:34, 12 July 2018 (UTC)
Did I say “as a person”? No, I am being attacked by my comment & opinions! Do you really think it is acceptable to say someone’s comment/opinions are “is not a valid argument” (Galatz - 15:52, 11 July 2018), are “snarky” & “are downright rude” (JTP - 19:56, 11 July 2018) “are simply not significant” & “is not the greatest argument” (Prefall - 22:48, 11 July 2018) & therefore don’t matter? What if I find those to be rude personal attacks? Is that “acceptable” & “civil”? No, that is not! Yet I am going to be accused of it? That is laughable to me! If people aren’t going to be “civil” & respectful with me why would/should I be “civil” & respectful with them?
Am I over reacting? Perhaps but I am going to defends myself regardless of if anyone likes it or not! Don’t blame me when I did not “fire the 1st blow” so to speak - I am just firing fire with fire, that does not make me the bad guy that everyone is making me out to be just because they don’t agree with my stance! You say “Presenting logical arguments that you happen to dislike, pointing out problems with your attitude and behavior, and pointing out problems with your arguments are not the same as actually attacking you. Users have repeatedly asked you to behave in a civil and mature manner and if the next response I see from your IP range is anything but that, I'm going on ahead and blocking.” but that is not true when that is exactly what is happening! Why would I “behave in a civil and mature manner” when I am not getting the same? If you are going to block me for standing up for myself that tells me how you treat people & find it acceptable but that’s neither here nor there - I don’t tolerate being bulled yet that is exactly how I have been treated!2602:306:CCE0:8550:D424:64A0:7B5C:A6E5 (talk) 18:23, 12 July 2018 (UTC)The Greatest
Please read WP:Civility#Dealing with incivility, where it says that if you believe someone else is making uncivil comments, you should not make them in retaliation. I'm afraid your "fighting fire with fire" mentality is not the best way to go. JTP (talkcontribs) 18:38, 12 July 2018 (UTC)
Personal attacks are, by definition, about you as a person. They're not simply about your chosen behavior or about how (un)reasonable your arguments are, which are what everyone has been commenting on. You do not get to behave in an uncivil manner, then use WP:NPA as a shield when anyone points out problems with your chosen behavior. You don't get to use WP:CIVIL as a weapon to force others to agree with you. Ian.thomson (talk) 19:18, 12 July 2018 (UTC)

I find it interesting that nobody who opposes this change has bothered to come up with a policy-based counter-proposal or bothered to show that it is possible to properly source an "In wrestling" section (maybe in a sandbox, for example) without any original research, using reliable sources, and not using WP:SYNTH of sources. You can't just say that it's possible, you have to prove that it is and your argument will have more weight. Nikki311 06:13, 13 July 2018 (UTC)

I don't think there's any reason to downplay the opposing side despite disagreeing with them. Plenty of people here and on WikiProject's talk page have pointed out how that would be possible. World Wrestling Entertainment has its own record label slash music department named WWE Music Group, which releases their custom-tailored themes (so majority of WWE's themes) on multiple platoforms, including Amazon, iTunes and their own verified YouTube channel. Those platforms are used as valid and reliable sources on other music-related Wikipedia pages, such as articles about artists' discography. They would for sure be good enough sources on wrestler pages as well. It's a bit more problematic on other promotions, but New Japan Pro Wrestling, for example, lists the names of their wrestlers' entrance themes on their website. When it comes to finishing moves, WWE has a huge amount of articles referring to a wrestler's finishing move, NJPW and many other promotions list those moves in the wrestler bios. Managers and nicknames are a more difficult beast to tackle, but I'd say they have no place in Wikipedia, unlike finishing moves and theme musics. Kanavarras (talk) 06:41, 13 July 2018 (UTC)
My argument is mostly about finishing and signature moves. I'll pick Brock Lesnar as an example, because he is the first person listed on WWE.com. His WWE profile [33] lists the F5 and Kimora Lock as his signature moves (not even as finishers like his Wikipedia profile did prior to the section removal [34]). And nowhere does it describe the technical move name of F5 as "fireman's carry facebuster". Same with New Japan. Kenny Omega's New Japan profile [35] lists his finishing moves as Katayoku no Tenshi, V trigger, and Croyt’s wrath...again with no technical move description. Therefore those can't be used to source the moves unless you only list the move name without the description included. If even the promotions themselves only list a handful of moves considered "finishing" or "signature", how is listing them in a bullet list any more accessible than written in prose with more context? Nikki311 07:05, 13 July 2018 (UTC)
I understand the concern with WP:SYNTH. However, that's only a problem when combining two sources could lead to a misinterpretation of why those two sources are connected. If WWE's own website lists F5 as Brock Lesnar's finishing move and the same website has a video of Brock Lesnar doing a fireman's carry facebuster named F5, it's pretty clear to all users that the two sources are referring to the same move. As stated in WP:NOTSYNTH, it is only a guideline and not a rigid policy, and in this case I wouldn't say combining the two sources is original research. Besides, you would be facing this same problem regardless of whether the moves are mentioned in prose or in a bullet list. In this case bullet list would be better than prose simply because of its easier readability and accessibility, the same way championships and accomplishments are a list instead of a wall of text. Kanavarras (talk) 07:59, 13 July 2018 (UTC)
WP:SYNTH is actually a massively important policy page that represents one of the oldest, strongest and most unviersally supported points of community consensus on this project. It is in fact as rigid as they come with regard to constraints on content on this encyclopedia. Respectfully, you can't have been on the project long if you don't know this, so I'd like to recommend to you and your visiting compatriots here not to be too bold in your policy pontifications until you have greater familiarity with said policies and how they operate in practice. I say this because I've seen a substantial number of "it's 'just' a guideline" comments already in this thread. Guidelines are actually policy and they have substantially secure operation to the circumstances they describe. They have to be vetted by the WP:PROPOSAL process, meaning they only come about if they represent substantially community consensus on the default approach for a given situation (contrast this with WP:ESSAYS which are optional opinions closer in importance to what you seem to think a WP:guideline is. While we do have an WP:Ignore all rules principle that allows us to contemplate exceptions to any policy, you will find that we don't exercise it very much or without very substantial cause, and the burden is upon the parties wishing to ignore those principles to make a compelling argument for why it should be done in that instance. In 999 out of 1,000 situations, the guideline is gonna control (and with regard to WP:SYNTH or anything that has to do with WP:ORIGINALRESEARCH, think closer to 9,999 out 10,000).
Also you actually turned WP:NOTSYNTH completely on its head when you said that it urges that WP:SYNTH can be considered as optional; the supplement says no such thing and, in fact, the opposite is the case, as WP:NOTSYNTH actually just provides extra guidance in how to apply the policy in particular situations. It augments, rahter than contradicts, the policy; this is why the first two sections of the explanatory supplement are "WP:SYNTH is not useless" and "WP:SYNTH is not unnecesary". That said, the point is moot, because, per my comments below, there is a better explanation with regard to sourcing which explains why this information could come in, if WP:V was the only issue with the "In Wrestling" section. Unfortunately, WP:V is just the beginning of the story, and there are much bigger hurdles which actually do preclude the section. Snow let's rap 08:18, 13 July 2018 (UTC)
I am not neglecting the whole WP:SYNTH guideline, I am simply questioning the validity of that argument in this context. Why would combining the two sources (the name of a wrestler's finisher on a wrestling promotion's website, and a video of the wrestler doing a move with the same name) be original research? If no such connections could ever be made, most information in Wikipedia would be classified as WP:SYNTH. Even if combining multiple sources is a problem, it shouldn't affect the whole In Wrestling section. The entrance music, for one, can be verified with just one source and definitely should be included in wrestler articles. I'd say it's comparable to articles about movies where the movie's soundtrack is simply in a list form instead of being worked into the prose or excluded completely. Kanavarras (talk) 08:52, 13 July 2018 (UTC)
Because the video doesn't say "it's a fireman's carry facebuster". --HHH Pedrigree (talk) 09:22, 13 July 2018 (UTC)
I disagree with HHH on this, because I think you are speculating about a scenario when the move is explicitly named in the video. Nevertheless, there may be issues with regard to whether or not the video is a WP:reliable source. However, I do not see why you would need the video in any event: if the other source names the move as the "finisher" and is an RS, it would suffice in itself, so there is no need to even attempt to combine the sources, whether it would involve WP:SYNTH or not. (On the other hand, if both sources are needed to reach a conclusion and one is not RS, then you have both a SYNTH and a WP:V issue). However, notice my comments below; I believe meeting WP:V is actually a relatively easy thing to accomplish for most of the content likely to appear in such lists. It still doesn't make it appropriate encyclopedic content under our other content policies (see WP:ONUS). Snow let's rap 10:10, 13 July 2018 (UTC)
As we said, it's hard to find videos where the finisher is named and includes the technical description. There is some examples, like Shawn Michaels (Sweet Chin Music Superkick) or James Storm (Last Call Superkick). But it's hard to find a video about HHH (The pedigree, double underhook facebuster). I have an example; long time ago I created the article Kahagas. I have these sources [36][37][38] where I see his finisher is named "Osaka Street Cutter". however, I can't find the technical description. It's a stunner, a jumping cutter, springboard cutter? I can find some video in YouTube, but it's gonna be my personal descrption of the move. The name is sourced, of course, but not the technical move. --HHH Pedrigree (talk) 12:42, 13 July 2018 (UTC)
Issues with "technical" nomenclature not withstanding, I actually think that the WP:V argument is by far the weakest for omitting this section. The fact of the matter is, we do have a perfectly valid source for verifying that each individual move or piece of music was utilized in a particular airing of a particular event: the recorded event itself. We routinely permit that media may be its own source for verifying its own content; indeed, in any given day we have many tens of thousands of edits across thousands of articles that do this. Plot synopses (of every form of video entertainment media in existence) never use independent sources, nor do statements describing the events in reality TV shows. And pro wrestling is just a weird amalgamation of reality tv and scripted television fiction. It's perfectly reasonable to use the shows themselves as the source in this respect, and I haven't seen any principled reason put forward to explain why we would deviate from this wholly accepted practice that is so ubiquitous that (despite having seen hundreds of disputes over what should go into a synopsis) so long as the event is a plain facially accurate interpretation of what happens on screen, I've never once seen anybody challenge any form of "in-universe" description of a show on the basis of sourcing--not once. So this is not really a WP:V issue, it's an WP:ONUS issue:
"While information must be verifiable in order to be included in an article, this does not mean that all verifiable information must be included in an article. Consensus may determine that certain information does not improve an article...The onus to achieve consensus for inclusion is on those seeking to include disputed content."
It's not that the information can't be satisfactorily verified; though there may be occasions where that happens (as with the situation you describe where particular descriptive terms are hard to verify, even if the fact that the thing they describe can be verified), mostly verification will be easy to achieve. However, WP:V is just the beginning of the analysis for whether we include a given piece of information and its the following steps where the argument for retaining the "In wrestling" section breaks down. For one, information must have an encyclopedic context, not just be a random assortment of information piled unceasingly on top of itself in unending waves of added fancruft until you have 120k compost heap of indiscriminate information. This touches upon multiple important policies, including WP:WEIGHT, WP:TRIVIA, WP:WWIN, WP:PROSE, and WP:SUMMARYSTYLE, to name just a few. I could write two paragraphs for each of those policies explaining why the "In wrestling" section presents problems of inevitable violations with regard to each. But the common nucleus of those concerns is that we are here to create an encyclopedic summary of article topics, a general narrative which could be used by the completely uninformed reader to achieve a basic understanding of the topic; NOT a complete warehouse of all minutia that can be collected with regard to said topic so that hardcore aficionados can have it all at their fingertips (and stored here as opposed to a more appropriate platform) even though it degrades the quality and consistency of our ability to achieve encyclopedic aims. Snow let's rap 08:06, 13 July 2018 (UTC)
I think the above is the biggest argument that is being forgotten here. Just because something is verifiable, doesn't make it encylopedic. Lists have their place, but have very little bounding in a WP:BLP. Most of these articles have some sort of list on them (Filmographies, discographies, etc), and the articles DO have a need for a list of accomplishments/championships. However, these should also be mentioned in prose! These are usually for information that needs to be an exhaustive list (Which entrance music and moves aren't), and are mentioned in the career sections on BLPs. Lee Vilenski (talkcontribs) 13:27, 13 July 2018 (UTC)
(edit conflict) "we do have a perfectly valid source for verifying that each individual move or piece of music was utilized in a particular airing of a particular event: the recorded event itself." That isn't the case with professional wrestling moves. There is no official guide that describes or defines the technical moves, so I may describe a move one way and someone else may describe it another way...which is where a lot of the edit-warring on these sections actually occurs. We could use the recorded event to source the wrestlers' names for the moves (such as the name F5), but as for what he is actually doing (the technical name) when he is performing that move cannot be sourced with the event itself. Nikki311 13:37, 13 July 2018 (UTC)
That's a useful observation: thanks for that. I had been operating under the assumption that there was at least a little uniformity in how moves are labelled and/or that the announcers for the matches tend to describe said moves as they occur, as in athletic wrestling and other contact sports. If that is not the case, then my WP:V argument is weaker than I presumed and there is yet more reason to omit the section. Snow let's rap 13:50, 13 July 2018 (UTC)
There is uniformity in technical descriptions. There are articles right here on wikipedia with the information Professional_wrestling_moves with sources ranging from WWE articles, interviews, to books, to long-used glossaries from deathvalleydriver.com. It does get a little tricky with named moves, where the same technical move might have several names (e.g. the Tiger Driver) depending on who is doing it or the announcer calling it or the promotion it's being used in. Since media is a reliable source, I'm wondering how create-a-wrestler sections of video games might be fit into that. I dunno, I just wanted to chime in and point out there is uniformity in technical terms, otherwise wrestling schools and trainers would have a very hard time. Bonevoyage (talk) 19:16, 13 July 2018 (UTC)
For some of the more basic moves but certainly not all. I remember an edit war over whether a move was a "wheel kick" or a "heel kick", or as pointed out above "stunner", "jumping cutter", or "springboard cutter". Some of the moves are very similar and even different sources deemed reliable call them different things. Nikki311 13:31, 14 July 2018 (UTC)

This is going to take a while so bear with me....

I will whole heartedly admit that I came here with a grudge. But in fairness please let me explain. When I discovered the “In Wrestling” section missing - when I was looking for something….a wrestler’s theme song, no less - why did I have to go to the Wikipedia:Teahouse (after having to search for it) & ask “I am looking at WWE wrestler pages & there use to be an ‘In Wrestling’ section that listed ‘Finishing Holds’, ‘Signature Holds’ & ‘Theme Music’ but all of that is nowhere to be found anymore. Why has it been removed? I am trying to look up some wrestler theme songs & that was my go-to for looking it up but that is impossible to do when they have been removed.” & was directed here when I was told “You need …. where there is a discussion going on about that very thing.” & that is the only way I would have ever known about it? Why is it that I have seen things on Wikipedia about asking for financial donations to keep it up & running but I never saw anything at all about any type of discussion whatsoever about content changes? If Wikipedia is going to ask the general-public-at-large for financial assistance on the site shouldn’t the same general-public-at-large also therefore have a say about what content is removed? Especially if it had been on the site for over the past 10+ years? Much less it being next to impossible to find & having to go searching for it like I had to? Then, as soon as I make a comment it is immediately shut down & “deemed trivial”, “pure trivial”,“ not a valid argument”,“ simply not significant” & “not the greatest argument”? I beg to differ, Drmies, HHH Pedrigree, Galatz & Prefall! I think the lengths I had to go through to even get here & the treatment I have gotten like I’m nothing but a 2nd, 3rd, ect. thought & that my opinion doesn’t matter at all gives me cause for having an attitude from the start. That is as close to an apology as I am getting….but I’ll be waiting for an apology from Drmies, HHH Pedrigree, Galatz & Prefall for treating me like a nobody!

With that being said, I have a very specific direct question for Drmies, HHH Pedrigree, Galatz & Prefall: who made you all kings (or queens) of the universe to dictate what is or isn’t “trivial” or “significant” at your own sole discretion? I call you 4 out because you sure seem to give yourself that right based on my comment/opinion alone! A right which you do not have! Just because “it’s just not important” to you doesn’t mean it isn’t to somebody else! Who do you to think you have the sole power to determine what you consider important (or unimportant) & push that on everybody else? You have no right to make that call! Do you know how self-centered, narrow-minded & egotistical that makes you?

Now, from my understanding of what I had read, the top section of this thread it says The ‘In wrestling’ section has been a standard part of professional wrestling biographies for over a decade. It covers mostly character information in a bulleted list format.” & I agree with that but it goes on to say that “On May 24, 2018, an editor raised an issue with the section's vague heading to WikiProject Professional wrestling. The next day, renaming the heading to ‘Professional wrestling highlights’ and adjusting ‘Championships and accomplishments’ into a subsection beneath it was proposed. On June 3, it was considered to have reached consensus after the 5 participants agreed unanimously. In the weeks that followed, a few editors disapproved of the new heading, as well as ‘Championships and accomplishments’ being turned into a subsection. On June 24, clarification of which heading to go forward with was requested, where an additional option to remove the section entirely was proposed. On June 28, the discussion was closed after 10 editors participated, with an ‘overwhelming consensus’ to remove the section but rework any content deemed significant into prose, potentially into a ‘Professional wrestling persona’ section. The changes were immediately enacted into hundreds of articles, causing news of the changes to be spread onto online professional wrestling communities. Many new editors voiced frustration over the removal, with some reverting the changes. but what I have a problem with is out of everyone that edits or reads Wikipedia how can ONLY 5 people - out of hundreds of thousands - “agree unanimously” on a change or ONLY 10 people - again, out of hundreds of thousands - make an “overwhelming consensus” to remove an entire section of content? Why then, is it that “many [new] editors voiced frustration over the removal” but the general public doesn’t get any say whatsoever? That very select small group jumped the gun completely deleting the section without allowing any input whatsoever from people that used the information. Then the “recommendations” says that “this proposal seeks to remove the ‘In wrestling’ section”….key word being SEEKS….goes on to say “Much of the information contained within this section would be lost.”….key word being LOST….& adding that “The content most likely to be reworked is certain Finishing moves, Nicknames and Wrestlers trained. As it stands, Managers are already expected to be covered in prose, primarily in the ‘Professional wrestling career’ section. If necessary, reworked content can be placed within the existing ‘Professional wrestling persona’ section.” but that still excludes important content & Prefall’s PROPOSAL is “Should we adopt a default approach of omitting the bulleted list ‘In wrestling’ section, in favor of its notable content being contextualized in prose when appropriate?” but who, exactly, is the end-all be-all that makes that call? Snow says that “The consensus in question does not yet exist; that is the purpose of the present thread.” but if the consensus does not exist yet then why, exactly, is it that the content is ALREADY gone? Being that this is such a huge topic of debate, why, then, did I (& I’m assuming many others) have such a hard time finding out about it? If such a drastic change is made to the “In Wrestling” section then would someone PLEASE explain to me why this whole discussion was brought up AFTER already taking the content down & not BEFORE doing so being that it clearly stated that it SEEKS to make the changes although they have already been done PRIOR TO this discussion? Whoever made the decision to completely remove the “In Wrestling” section out-right was out of line & should never have done it! Why would anybody financially support a website that does that? If Wikipedia is no longer going to provide knowledge content then I am NO LONGER going to be supporting Wikipedia at all if that is how things are done around here!

I would like to thank & make reference to Lid & offer this quote “Not everything fits into a narrow box of ‘is trivial’ or ‘is not trivial’ nor can making things have a sweeping removal ever be done without uproar occurring, and to then pass off the uproar as fly-by-nighter-johnny-come-latelys is to ignore the readers of wikipedia at their own peril. Wikipedia is a force for good, but sweeping changes made by 8 people is inevitably going to cause a problem, and its not like these 8 were arbitrators. If things need to change they have to change, but what has happened here was clearly wrong and to much ‘us vs them’ rather than actually looking at why these sections existed without one side reducing it to WP:USEFUL and the other WP:CRUFT. They have their place, they are important, and all-or-nothing is not the way we do things.” - truer words have never been spoken & that is my exact point - that was just said much better.

I have seen stated that verified but I don’t agree. I am not going to name names but I have known someone from church, middle school & high school that is now an actress. There is a Wikipedia page for her & there is stuff on her Wikipedia page that I know is not verified so clamming that everything on Wikipedia has to be verified does not hold water. I also know a current WWE superstar from their time on the independent circuit with data that is not verified so please don’t tell me that every single thing on Wikipedia has to be verified when that just is not true! If every single thing on Wikipedia really “has” to be verified then, why, exactly, shouldn’t Wikipedia be the [only] reliable go-to source. Why would you want to make people fend for themselves & send them elsewhere by making suck vital information - pertaining to a wrestler’s character - that much harder to find? But it is not really at all (anymore), is it? Too much valuable content is (now) missing because of a few self-centered, narrow-minded people! Wikipedia’s tag line is “The free encyclopedia”. Why is that? Isn’t an encyclopedia where you go to get information? Isn’t the point of an encyclopedia to be able to quickly dig up an easy answer to something? Yet you are taking information AWAY & not providing it?

Nikki had asked why nobody who opposes this change hasn’t bothered to come up with a solution but JackKasket had. Did you not see “I would argue that a timeline would be the optimal representation, similar to Carcass_(band)#Band_members. However, maintaining this would be a nightmare, in which case the second best option would be Current/Past lists. Basically, treat this information similarly to other performance arts.”? How is that not “policy-based”? I am going to attempt other ways.

With all of that being said, I completely agree that the “In Wrestling” section needs to be cleaned up & possibly renamed. However, it should not be completely removed like it already has been! Several of the so-called “signature moves” need to go (for example, a drop kick, clothesline or knee drop are not signature moves) & only keep the main moves that are commonly used & that would clean up a lot right there alone. I also don’t understand way “awards” from magazines (Pro Wrestling Illustrated, Wrestling Observer Newsletter….Rolling Stone [really?]) need to be listed under accomplishments. I know I am going to catch crap for this but I am a firm believer that a wrestler’s theme music IS a part of their professional wrestling persona & therefore SHOULD indeed be KEPT despite those clamming that it is nothing but “trivial” & “unimportant”. Case in point: if you take the time to read “Music in professional wrestling” under “Usage as part of a gimmick” it clearly states that “Entrance themes are often tailored to the gimmick of the wrestler they are written or selected for.”. How does that right there not make it an important part of their persona? That right there makes it valuable information that should be included. My thing about theme music is this: if you can have a championship section & list every single promotion someone has been in, every single championship that person has won in that promotion & how many times they have won each championship why would it be so hard to list the theme music they have used? What is so hard about that? Furthermore, people keep saying that anything that is “important” can be “put into prose” but entrance themes, moves (signature or finisher) & managers can NOT be in prose! Do you really expect someone to have to read paragraph after paragraph just to find a small bit of text? That is simply ridiculous! That kind of stuff MUST be in a bulleted list! The facts speak for themselves - the out-right complete removal of the section is, was & forever will be totally unjustified - it should be retrieved & brought back promptly!

In closing, it is my form opinion that this has never been a “survey” or “discussion” as it is made to appear - this is nothing more than a group of self-centered narrow-minded bigots forming a dictatorship & shoving their views down everybody’s throat. The way I have been treating for opposing that - being “deemed trivial” & “simply not significant” - proves it!

I’m going to let you quiver in your own self pitty....OnlyRealSpike (talk) 01:34, 20 July 2018 (UTC)

  • A wrestler's entrance music could be included, assuming it can be sourced. A good example is Randy Savage, whose entrance music was such an important and memorable part of his persona that it is mentioned in the lead. If you go back to previous edits where it was listed and find a good reference, or can find a reliable source for it elsewhere, it seems to me you could add it back. Jack N. Stock (talk) 03:03, 20 July 2018 (UTC)
  • OnlyRealSpike - quick comments 1) you are given the opportunity to comment now, can we please focus on the topic and not any perceived "incivility"? Your argument loses some of it's punch though by using terms such as bigots, what are people supposed to be biggoted against? 2) If this is the only place it's found - then it should not be here, we should not have content without reliable sources. Also - for 95% or more the theme music really doesn't make that much of a difference - if you're not in WWE/Impact you probably don't have a custom theme and are you telling me that someone in NXT being given "Random CFO$ theme #4" helps you in any way? Not trying to be dismissive, I am genuinely trying to figure out why you believe it's "critical to understanding a wrestler"? Does your knowledge of Sami Callihan's indy career in any way improved by knowing that he has come out to 9 different songs on the independent circuit? Not what he's done, worked with, achieved, won etc. but what music happen to be playing as he walks to the ring and afterwards if he wins the match? I'm just trying to understand the context of your comment.  MPJ-DK  03:17, 20 July 2018 (UTC)
If it is not here - like it has always been for over 10 years - where exactly WOULD it be? Don’t you want people to COME to Wikipedia to find information? Yet it is not provided anymore? That is bullcrap! If I want a wrestler’s theme on my iTunes how do I find out what it’s called? I have always come to Wikipedia to find out! You & everyone else calling it “trivial” & “not relevant” DOES IN FACT make “dismissive” so you saying its not is 2-faced!OnlyRealSpike (talk) 12:55, 20 July 2018 (UTC)
That's quite literally the point. If something isn't sourcable from reliable sources, it has no place on Wikipedia. That's how the website works. If you can't find it elsewhere, we can't rely on it being accurate information. Please read the guideline on reliable sourcing. Please be civil, and discuss the policies.Lee Vilenski (talkcontribs) 13:15, 20 July 2018 (UTC)
OnlyRealSpike - Hello, welcome to Wikipedia. Would you let me inform you of a few pieces of information regarding discussions on the encyclopedia. First, all conversations should be WP:CIVIL. Please don't call anyone a Bigot, or liken volunteers to a dictatorship. Secondly, all talks on wikipedia should be based on wikipedia policies. Could you provide us with some policy based arguments, please? Lee Vilenski (talkcontribs) 08:10, 20 July 2018 (UTC)
So you want me to lie? Every single thing I said is the honest to God truth! The way I have been treated proves it! So who are you to tell me I’m wrong?OnlyRealSpike (talk) 12:55, 20 July 2018 (UTC)
I think you've confused an opinion and truth. You cannot attack people on Wikipedia, there are Procedures in place to stop such things Lee Vilenski (talkcontribs) 13:18, 20 July 2018 (UTC)
You stated Who do you to think you have the sole power to determine what you consider important (or unimportant) & push that on everybody else? You have no right to make that call! - Which isn't true. Wikipedia has literally thousands of guidelines around what information is viable, which types are allowed, and how this should be formatted. For instance, the argument is that this information is deemed to be WP:FANCRUFT, which is excessive information that is only subject specific. It is not that information is unimportant per se, but simply that it has no place on a general encylopedia. There's also some extra information on the article about what Wikipedia is not. It simply isn't a warehouse for all information about a subject. There's also a lot of information that cannot be reliable known as true (See reliable sources). Lee Vilenski (talkcontribs) 08:10, 20 July 2018 (UTC)
Wikipedia is an encylopedia, correct? Where do you go to get information? An encyclopedia! Wow, what a concept….until the information isn’t there! Then it is completely useless! Welcome to Wikipedia….OnlyRealSpike (talk) 12:55, 20 July 2018 (UTC)
There is another arguement about information being really poorly defined. What is a signature move? We can't guess, we need a reliable source to state this... But you'll find very few reliable sources ever state this. (And some list all moves as signature.) Lee Vilenski (talkcontribs) 08:10, 20 July 2018 (UTC)
How are there not any reliable sources? Furthermore, what did I say about my friends (the actress & WWE superstar)? What about stuff on their pages that aren’t verifiably sourced? So don’t talk to me about stuff being “poorly defined”!OnlyRealSpike (talk) 12:55, 20 July 2018 (UTC)
Please read Wikipedia's policy on Verification. Wikipedia is a work in progress, but simply because WP:OTHERSTUFFEXISTS, doesn't make a policy have to fit this. There is information that is not well sourced on wikipedia, but in these cases, we should be tagging them with [citation needed] or otherwise. Lee Vilenski (talkcontribs) 13:23, 20 July 2018 (UTC)
Your last argument regarding entrance themes is a good, and perhaps you have misunderstood. The argument here isn't to simply remove all information, but to move it into written prose. Notable entrance themes should be moved to this section. However, there are wrestlers that have used tens of themes over the years, and most aren't notable. (For instance, Raven comes out to The Offspring's Keep 'Em Separated on the indies... But is this vital, notable information? It isn't. Lee Vilenski (talkcontribs) 08:10, 20 July 2018 (UTC)
Don’t keep giving me this prose crap! Like I had clearly stated: “Furthermore, people keep saying that anything that is ‘important’ can be ‘put into prose’ but entrance themes, moves (signature or finisher) & managers can NOT be in prose! Do you really expect someone to have to read paragraph after paragraph just to find a small bit of text? That is simply ridiculous! That kind of stuff MUST be in a bulleted list!” so what part of that do you not understand? That kind of stuff can not be hidden in the middle of a (set of) paragraph(s) making it next to impossible to find! Before I could just go right down to it but now only “some” of it “could” be like looking for a needle in a haystack! That, in itself, is completely unacceptable! How, exactly, is THAT “misunderstood”?OnlyRealSpike (talk) 12:55, 20 July 2018 (UTC)
Sure they can. We've already discussed how this information is mostly WP:TRIVIA or WP:FANCRUFT, which should be limited on wikipedia (see the policies linked.) A layout style is usually resorted to how the information flows, not how it's seen. On Wikipedia, we do guess as to how people read the information, we simply lay it out as to how it reads. A list of all entrance music that someone has ever used,even if reliably sourced, is excessive. Lee Vilenski (talkcontribs) 13:27, 20 July 2018 (UTC)
Like I had asked before, what if someone wants to put wrestler’s theme music on their iTunes? Where would they go to bet the names of the songs? I had already come here! Where the h-e-double-hockey-sticks do you expect me to go now? Up your butt?OnlyRealSpike (talk) 13:46, 20 July 2018 (UTC)
Then they can go on the wrestling Wikia. I'll reiterate the point that Wikipedia only summarizes stuff that other reliable sources have published, so the fact that it doesn't exist elsewhere is a perfect argument against including it here (see also WP:ITSUSEFUL). --Ahecht (TALK
PAGE
) 20:45, 20 July 2018 (UTC)
  • OnlyRealSpike - I guess I will have to ask again. Can you please tell me how knowing that Sami Callihan has used at least 7 different songs on the indy circuit makes you understand the career or character? Can you please explain to me how reading "Watch Me Shine" listed for Bianca Belair makes you any more aware of her? So far your only argument has been "well what if I want to go to iTunes and find the theme" - at the risk of sounding dismissive here, but that's not really an encylopedic reason. So I want to not be dismissive, I want to understand why this has gotten under your skin, I would love for you to elaborate how listing theme songs for 99% of the wrestlers makes a differnce to you beyond the whole "iTunes" comment. Geniuinly curious.  MPJ-DK  21:13, 20 July 2018 (UTC)
  • Well I guess I won't get an answer from OnlyRealSpike since he was just indef'ed for uncivil behavior. I guess I'll never know then.  MPJ-DK  21:25, 20 July 2018 (UTC)

Example of the "Keep" vote with strict WP:V verification.

  • So taking the feedback of people who vote "keep" and their approach on handling content I have worked on the Sin Cara article, an IP reverted the removal and I did not want to just wholesale remove it since it's being discussed here. So I did an analysis of sources and content. After which I have removed anything that was not found explicitly stated in a reliable source, so it went from this long list to this much shorter list. I figured that instead of a theoretical discussion we should have an actual example of how this would look. There is nothing stating that a "wrestling persona and style" section has to be included, which means that this is the sections and content based on the original style guide that's been in place for over 10 years. I just want people to know what that actually means. This is a WP:BLP and under general sanction, keep that in mind as well.  MPJ-DK  04:16, 16 July 2018 (UTC)
MPJ-DK - The "Incognito Especial" wouldn't be acceptable by WP:SYNTH. And all moves are sourced by an offline source. I am willing to promote WP:GOODFAITH on this article, but if we can literally only source wrestling moves from printed text, there is very little hope for the other thousands of articles out there.
The entrance music issue is different, as arguably, this is notable, as the wrestlers themselves have the music made for them (Original music). However, I'm not sure I would be ok with articles simply referencing iTunes store for this purpose. I think I could be convinced there is a place for any original music created for the talent - But this could once again, simply be written in prose, if the music was notable enough. Lee Vilenski (talkcontribs) 07:55, 16 July 2018 (UTC)
One of my biggest concerns with sourcing itunes or the youtube video, or anything else is it doesn't really say much about it. Randy Orton had a live version of his music done at WrestleMania one year, it was a different version than before (was it the same artist? was it not? do we have a source that proves either argument which could be questioned). Would a link to them singing the music at WrestleMania tell us anything about it? In prose however it could be discussed and a clearer picture could be painted, with proper sourcing. - Galatz גאליץשיחה Talk 13:15, 16 July 2018 (UTC)
I've added his manager, citing WrestlingData. Eight "trademark moves" (clearly synonymous with "signature") ripe for the picking in there, if someone can show which mask fits which move. Or how exactly the Olympic Slam is "modified". InedibleHulk (talk) 22:20, July 16, 2018 (UTC)
And you passed the test! Congratulations, you're now ready to weed even the slightest bit of dubiousness from any and all new and improved sections. That's my story and I'm sticking to it. InedibleHulk (talk) 22:33, July 16, 2018 (UTC)
Is wrestlingdata really reliable for this type of sourcing? I thought it could only be used for really basic information Lee Vilenski (talkcontribs) 12:48, 17 July 2018 (UTC)
This is really basic information. That's why it's on the introductory Profile page. The more complex stuff is in the other tabs. InedibleHulk (talk) 19:34, July 17, 2018 (UTC)
That doesn't make the source anymore reliable. It's clearly unproven. If we were to use the site like this, we'd have to make sure it was reliable for this type of information. Lee Vilenski (talkcontribs) 08:45, 18 July 2018 (UTC)
You could...watch one of their matches? Only in death does duty end (talk) 09:43, 18 July 2018 (UTC)
Please see conversation above as to why this isn't verifiable. What someone might call a facebuster, might be referred to by another as a DDT. This has never been an acceptable way of sourcing. Lee Vilenski (talkcontribs) 10:19, 18 July 2018 (UTC)
I was looking for a source about Lesnar's F5, a fiherman carry facebuster. But suddenly, I found one source calling "spinning facebuster". So... that's the problem. Also, I was looking a video for Kahagas' Osaka Cutter, but I found nothing. --HHH Pedrigree (talk) 12:12, 18 July 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I always thought it was a Death Valley Driver Facebuster... Lee Vilenski (talkcontribs) 12:52, 18 July 2018 (UTC)

A Death Valley Driver is basically a sideways brainbuster, and like all brainbusters and piledrivers, bumping facefirst is quite likely fatal. Lesnar's rough, but not that rough. It's a facebuster from a fireman's carry with a spin, so either of Pedrigree's descriptions works well enough. Anyway, this same mild confusion would affect a reader in prose as much as in a list, so a moot point here.
I took Only in death's suggestion above to mean you could watch matches on YouTube to test whether a source is reliable. If it passes inspection, use that reliable source to verify info on Wikipedia. Not cite the info directly to the matches, which is a terrible idea for a few reasons. InedibleHulk (talk) 18:17, July 18, 2018 (UTC)
Sources are either reliable, not reliable or untested. We can't quote unreliable sources simply because one piece of information is correct. Lee Vilenski (talkcontribs) 08:27, 19 July 2018 (UTC)
WrestlingData is "not yet proven", not deemed unreliable, so we can use it with caution rather than not at all. If "use with caution" doesn't mean testing specific data against the primary sources for validation and making a reasonable effort to rule out contradiction from other secondary sources, I can't guess what it could mean. Can you? InedibleHulk (talk) 15:34, July 20, 2018 (UTC)

Question about templates and categories re: user essays

See here. Reason I'm posting here is that it wasn't until after I saved the page that I noticed no one had posted anything on the page except an edit request (which automatically solicited a response) in eight years, and figured a random message left on the talk page would never be noticed. Sorry if this is forum-shopping: feel free to just copy my message there over here and blank it there if so. Hijiri 88 (やや) 00:08, 11 July 2018 (UTC)

RfC on Spanish/Catalan/Basque regional identites

There is a an RfC at Wikipedia talk:Manual of Style/Biography #RfC on use of Spanish regional identity in biography leads that may be of interest to editors here. --RexxS (talk) 00:23, 11 July 2018 (UTC)

Reference in headers

Hi folks.
Is there any policy that prohibit usage of references [1] in the headers (e.g. Header[1]) of sections and tables (columns)?
Can't find it. I searched the archives for that but to no avail. Thanks.
DAVRONOVA.A. 12:47, 12 July 2018 (UTC)

WP:CITEFOOT which contains: "Citations should not be placed within, or on the same line as, section headings." It would appear that the subsequent clause beginning "For exceptions, see ..." referred to WP:REFPUNCT which says nothing about references in headings.
—Trappist the monk (talk) 13:00, 12 July 2018 (UTC)
@Trappist the monk: Thanks. DAVRONOVA.A. 13:54, 12 July 2018 (UTC)

Chains (unit of measure) RFC

FYI: Pointer to relevant discussion elsewhere.

Please see Wikipedia talk:WikiProject UK Railways#Chains RFC

This is a four-way proposal for a possible variance from WP:Manual of Style/Dates and numbers on the handling of a unit, the chain, in articles on British railways in particular.  — SMcCandlish ¢ 😼  03:42, 14 July 2018 (UTC)

Proposal to draftify UDP-tagged articles

Currently we have just 780 articles tagged with template:Undisclosed paid (UDP), a particular aspect of more general template:COI. I think mere tagging for suspected UDP editing is toothless - the potential paid editor gets the job done anyway and the article becomes indexed by search engines, hanging around indefinitely until someone cleans it. Moving all UDP-tagged articles to the non-indexed draft space and keeping them there untill they're fixed and ready to return to the mainspace could be a good solution. Also in this option, any new UDP-tagged article might be draftified by any registered user. If adopted, the proposal might entail corresponding addendums in relevant pages. Thoughts (support, oppose, comments)? Brandmeistertalk 13:40, 14 July 2018 (UTC)

  • Support I like this idea, as it would remove those problematic articles to a more appropriate space where they can be dealt with properly, subject to the AfC criteria. — AfroThundr (u · t · c) 19:27, 14 July 2018 (UTC)
  • Support This would reduce the automatic "BOGO" that many paid editors count on. John from Idegon (talk) 19:36, 14 July 2018 (UTC)
  • Support Although it would be interesting to know if the relevant templates could also apply noindex as an alternative. —PaleoNeonate – 19:51, 14 July 2018 (UTC)
    • Mainspace pages aren't noindexable. —Cryptic 01:14, 15 July 2018 (UTC)
      • Unless someone changed something again when I wasn't looking, Cryptic, new pages are default NOINDEX, until passed by NPP or 90 days old. Oh, wait....I read that wrong. So, yeah. I like the idea of the UDP template adding the NOINDEX back in addition to draftified. Anything that pushes UPE editors into outing themselves is a good thing in my book. John from Idegon (talk) 02:02, 15 July 2018 (UTC)
        • My point is that either this requires a software change, or that all paid pages are found and fully dealt with before the 90-day cutoff before indexability stops being configurable. Neither of those are realistic in the least. —Cryptic 03:17, 15 July 2018 (UTC)
          • I don't understand the software, nor do I care to. So I'll take your word for it. However, that does not affect the original proposal, ya? John from Idegon (talk) 03:36, 15 July 2018 (UTC)
          • The UPE template already applies NOINDEX and the page will stay NOINDEXed even if patrolled for 90 days after creation. MER-C 13:15, 19 July 2018 (UTC)
            • Good tidbit I was not aware of. But there's also the possibility to alleviate the mainspace and cut off potential traffic to such articles - several dozens UPE articles are already in drafts. Brandmeistertalk 18:59, 20 July 2018 (UTC)
  • Support Are supposed to go through AfC anyway. One thing to consider is the "undisclosed paid articles" that make it through AfC, should we deal with these differently? Doc James (talk · contribs · email) 20:41, 14 July 2018 (UTC)
    • My understanding is that those that have passed AfC do not require cleanup requested in the UDP template, at least in the reviewed AfC version. If UDP is still suspected, they could be sent back to drafts. Brandmeistertalk 21:10, 14 July 2018 (UTC)
      • IMO, and I'm not alone, AfC is kinda like economics. We all know ideally that's how it should work, but in actuality, it doesn't always. John from Idegon (talk) 02:07, 15 July 2018 (UTC)
  • Support This sounds like a good idea, as the authorship violates the site's terms of service. However, would not the lag between creation and detection allow for search engine indexing in some % of cases? Also, could someone point me at a description (or put it here if brief) of how one determines that the content has been paid for, particularly if undisclosed? Thanks. --User:Ceyockey (talk to me) 00:32, 15 July 2018 (UTC)
  • Conditional Support - I'd like a second pair of eyes on each of the articles before they are moved to draftspace. I'm leery about doing this automatically where it allows any editor to unilaterally move any page to draft. Tazerdadog (talk) 01:42, 15 July 2018 (UTC)
    Sticky Prod, as suggested below, is a better solution which I fully support. Tazerdadog (talk) 21:26, 16 July 2018 (UTC)
  • While I support the general idea, I'm not sure moving pages into draftspace where they will disappear from the eyes of other editors is the best way. Natureium (talk) 01:47, 15 July 2018 (UTC)
  • Oppose as written. We should not automatically userfy pages just because someone slapped a template:Undisclosed paid on it. Really, if no one is planning on improving these articles, sending them to draft space is just a delayed WP:CSD G13 death sentence. If we want to delete these articles, we should use the existing CSD or AFD processes, and only send them to draft space if there is a editor without a COI issue who plans to improve the article in the 6 month window. If they haven't already been nominated for deletion under existing policy, and instead are stuck with the Undisclosed paid tag, its because they still add value to the encyclopedia, not withstanding the issue with their primary contributor. Monty845 04:39, 15 July 2018 (UTC)
  • I'd prefer a sticky PROD that couldn't be removed by the creator. TonyBallioni (talk) 04:46, 15 July 2018 (UTC)
  • #1 choice sticky PROD. This deals with the article quickly and keeps it visible for those who may be interested in fixing it. The stickiness should require the remover to place {{oldprodfull}} with con= and conreason= filled out ie disallow 'I just don't like prod's prod removal'. Personally I would like to see that requirement for all PRODs but I know a loosing battle when I see one :) #2 choice support proposal for moving them to draft but it seems to be the less accountable and reviewable of the two. Regardless, if this is to become a regular thing, a tracking category should be added when either is done to facilitate review. Jbh Talk 11:07, 15 July 2018 (UTC)
  • Oppose. As it's currently set up, the draft namespace is only for short-term collaboration on future articles, so unless there are editors who have expressly volunteered to work on an article, and there's agreement that this article is not ready for mainspace, then it shouldn't be draftified. In practical terms, sending an article to draft will be useless if the COI editor is still around, as they're likely to be motivated enough to move it back; and if there are no editors (with a COI or without) watching it, then the move is most likely to result in the silent "expiry" of the draft after six months – this is deletion by the backdoor and should not be encouraged. Additionally, the fact that a given article has been edited by someone suspected of UDP is not a single problem that has a single solution, it's simply an indication of a more basic problem. Fundamentally, this might be an issue of either notability – in which case deletion via the proper channels is the way to proceed, or of neutrality and sourcing – in which case it's better to rewrite the article or simply to remove any suspicious parts, even if this means paring it down to a one-sentence stub. – Uanfala (talk) 13:47, 15 July 2018 (UTC)
    I understand these concerns about "deletion by the backdoor" even if I supported. A good approach if this passes and there is enough will to make it happen, would be to make a temporary trial (i.e. I remember of WP:ACTRIAL), then evaluate with stats if it helped. It may help in some ways: (quickly unindex pages vs deletion processes, permit more time to work on them, for instance) which is why I think it's worth trying. If it results in draft space becoming unwieldy other procedures may need changes... —PaleoNeonate – 16:02, 18 July 2018 (UTC)
  • Support if not fully automatic, per concern raised by Tazerdadog and Monty845. It needs human review, because not every tagging will have been valid, and some valid ones will already have been resolved without removing the tag.  — SMcCandlish ¢ 😼  17:00, 15 July 2018 (UTC)
  • Conditional support - I'm with SMcCandlish here, although I'd prefer mass draftify over leaving them alone. DaßWölf 00:19, 16 July 2018 (UTC)
  • Support. Regulars to the Wikipedia:Conflict of interest/Noticeboard or NPP would observe that this is already starting to become practice when dealing with promotional articles. I prefer sticky prod over draftifying -- spammers sometimes continue to work on the draft and move it into mainspace (either with the original account, socks, meatpuppets or a different spamming company altogether). Paid-for spam in many cases can't be fixed, because the subject may be non-notable and the article's very existence is promotional. Sticky prod satisfies the desire above to have review of any pages affected by this proposal. MER-C 12:15, 16 July 2018 (UTC)
    • Prodding could be a good alternative. To severe oxygen supply for paid efforts and convey WP:GAME message this might entail mass prodding of all such tagged articles and possibly prescribing in policy that articles tagged for UDP might or should be prodded. Brandmeistertalk 19:00, 16 July 2018 (UTC)
      • Only if the spammer and any non-autoconfirmed user (covert advertising frequently involves large sockfarms) are prohibited from removing the deletion messages. MER-C 20:39, 16 July 2018 (UTC)
  • Support, noting similarity to my Wikipedia:Quarantine promotional Undeclared Paid Editor product proposal.
The sticky PROD idea looks just as good. How long until the UPE-PROD results in deletion? In the case of the sticky UPE-PROD idea, who is the non-UPE false positive editor supposed to respond? If they make a response, surely it must demand reading before deletion? Who would read it, how would they be drawn to the response?
I think quarantining outside mainspace has the advantage to retaining UPE edit histories that may be helpful to non-admins in detecting patterns. I continue to submit that there are probably far few UPE people than UPE accounts, and that an awful lot of UPE product is the result of a few Wikipedians among us. The deletion of identified UPE product helps prevent detection of the puppet master. --SmokeyJoe (talk) 04:01, 18 July 2018 (UTC)
  • Support Too often articles that are plain articles are kept "because normal editing van fix that". In fact, the editors claiming that never alter a letter in such articles. Do you remove the spam, you get flak. And if you don not get flak, the spammer put everything back in. The COI-noticeboard also seems ineffective in dealing with that. So this is a good alternative. The Banner talk 13:18, 18 July 2018 (UTC)
  • Support - Way to easy to just let them be. Lee Vilenski (talkcontribs) 13:41, 18 July 2018 (UTC)

Incident thread RE: Usage of AWB (continued)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

This is following on from the above linked incident thread, in which I was informed that I had incorrectly used AWB when I updated "U.S." to "US" in usages of {{Episode table}} following a discussion at the WikiProject Television (Special:PermaLink/848355963#MOS:US); specific details available at the incident thread.

The result was that I would have my AWB permission removed, but now that I have successfully reapplied for it (Special:PermaLink/850161648#User:AlexTheWhovian), I wanted to post here to basically ask permission to revert my edits using AWB (i.e. change "US" back to "U.S." in usages of {{Episode table}}), to restore the pages to how they were previously before my AWB edits, as suggested in both the initial incident thread and the PERM thread. Thought that it might be best to ask here first instead of going straight for it, lest there be another incident thread raised.

@Amaury, AussieLegend, Davey2010, Esuka323, HandThatFeeds, IJBall, Iridescent, JJMC89, John, Netoholic, Nyttend, Only in death, Power~enwiki, Primefac, Pyxis Solitary, Schwede66, SMcCandlish, Snow Rise, Swarm, and The Optimistic One: Pinging every editor that contributed to the initial incident thread and the PERM thread. Cheers. -- AlexTW 02:55, 15 July 2018 (UTC)

You know, I think it's best to not use AWB to "undo" this – let's just let individual editors take care of this on their own... --IJBall (contribstalk) 03:10, 15 July 2018 (UTC)
One of the concerns with the original run was whether due care could ever be given to keeping the articles consistent in their usage of US/U.S. and other dotted/undotted acronyms both inside and outside the Episode table. This is something which is very hard to guarantee on any sort of semi-automated run. That concern is present both in the original run and in any run to restore the old usage. Like IJBall, I think this is something that is best done manually. -- Netoholic @ 03:42, 15 July 2018 (UTC)
Okay, all good. So, there's no issue with keeping US, and we should leave the initial case that raised the issue. Thanks for that, I'll need to remember that for the eventual RFC I was planning. I only raise this based on the previous suggestions of other editors, including administrators, that it should be reverted thusly. Cheers. -- AlexTW 03:59, 15 July 2018 (UTC)
"there's no issue with keeping US" - no.... I didn't say that. I said it should be fixed manually, which involves checking the article for consistent use. As in, you should fix it, but don't use AWB. That you so radically misunderstand (or just hear what you want to hear) is the root cause of this whole thing. I can see no good from you regaining access to these tools when the effects of misunderstanding can be so profound. You want to fix this, open your contribs list, and start fixing. Frankly, I wouldn't have given you back the tool until you'd completed this, as a minimum. -- Netoholic @ 07:14, 15 July 2018 (UTC)
Unless I have an admin state that I have to manually check 2,000+ articles, that won't be going on. What you would or would not have done really has no standing here, as you are not the one who reviewed the application, nor are you the admin who stated in the incident discussion that I could/should reapply. Cheers. -- AlexTW 10:19, 15 July 2018 (UTC)
"Okay, all good. So, there's no issue with keeping US, and we should leave the initial case that raised the issue." Don't jump to conclusions based on the responses from TWO editors.
I don't accept that the massive edit should stay as-is until an individual editor changes US back to U.S. on an individual article — because 99.5% of editors who work on TV articles probably don't know that MOS has not been changed, don't know what was behind the edit and that it was not based on a legitimate decision.
I don't care how you play with your toy as long as how you use it wiki-wide is based on a substantial consensus of editors.
My suggestion for undoing what you did: why don't you create a talk page message similar to those of bot messages, use AWB to post it on the articles you affected, and through it inform editors of those articles that the US can be changed back to U.S. on American and Canadian articles. In whichever manner the rollback is accomplished ... it should be done. Pyxis Solitary 06:53, 15 July 2018 (UTC)
Your personal suggestion has been noted and may be looked into. I'll wait for some administration comments as well (as I can't jump to conclusions based on the responses from four editors), as it was an administrator who recommended I use AWB to revert the edits. Cheers. -- AlexTW 10:19, 15 July 2018 (UTC)
(edit conflict) I strongly suggest that you listen to whatever consensus this thread comes up with regardless of the advanced permission status of those commenting. The dismissive attitude you are expressing towards your fellow editors in this thread is extremely inappropriate and is, in my experience and opinion, one of the behaviors which signals an editor heading for a long IDHT block. I believe that would be a loss to the project should that come to pass.
On the issue raised here my suggestion would be for you to start checking the articles you changed for internal consistency - that means doing it manually unless/until you can get consensus for an AWB run not doing nothing while lobbying for an AWB run. You made the mess so it is your responsibility to work to clean it up. Jbh Talk 11:29, 15 July 2018 (UTC)
Cheers. I'm sure that I'll get around to cleaning it up. -- AlexTW 13:51, 15 July 2018 (UTC)

I wasn't fully aware of the U.S. to US changes until I saw people reverting the edits made by Alex and linking to the admin board discussion in their edit summaries as their justification. I had little choice but to read the entire discussion as I wasn't sure if their reversions were justified or not and I just wanted to make sure. But if you want to change back to U.S. go for it, I don't mind either way. Esuka323 (talk) 11:15, 15 July 2018 (UTC)

  • @AlexTheWhovian: I appreciate your caution, but part of the reason your AWB access has been reinstated was so that you can revert the mass changes you initially performed. The issue was not that you used AWB incorrectly, but that you made a mass style change to a huge number of articles without a formal community discussion. The local consensus on the talk page was not sufficient to override an MOS guideline to the contrary. That's a fairly minor "offense" that was blown out of proportion, IMO, and it's even possible that the community might end up supporting the change. But your AWB was correctly revoked, and you are still expected to revert the changes. You should now understand why AWB is a privilege, and how it can become controversial even with seemingly minor improvements. You do not need to ask permission to use AWB in accordance with the rules, and reverting a controversial change you made is not something you need to ask permission for. What you need to ask permission for is the change itself, via RfC or on a community noticeboard and listed at WP:CD. Swarm 12:07, 15 July 2018 (UTC)
So, if I've got this right... I should have filed an RFC for the initial change, but in my oversight I didn't, and now in an attempt to rectify my apparent transgressions, I need to leave the mistake on a great number of articles for weeks while I file and wait for an RFC to gain permission to undo my mistake? I would have thought Wikipedia would be all against faulty articles. But, anyways, thank you for clearing it up; it does actually help. -- AlexTW 13:51, 15 July 2018 (UTC)
No, it seems you've misread. You don't need permission to undo your mistake. This thread is unnecessary; you're already expected to just do it without further ado. You need permission for the original change you tried to make. Swarm 16:12, 15 July 2018 (UTC)
  • I agree with both IJBall and Netoholic, up top; if editors have a strong argument to make in favor of "U.S." at a particular article, they can make it; the accuracy and presentability of the article isn't affected for readers either way, and in probably 99% of cases it's going to be a WP:DGAF matter. I would add three additional reasons:
    1) The current and immediately previous MOS:US (which one to use is still under discussion in an RfC) both actually favor "US" as a default, either implicitly or explicitly. Even the decade-old wording led to "US" dominating in the long run at WP because of the rule to not use "U.S." then "UK" in the same material. Ergo, a mass-revert to "U.S." would have a WP:POINTy effect if not intent, and would be a WP:NOT#BUREAUCRACY failure. We don't do an unhelpful thing "just because", only to have it slowly be undone again later. That segues into ...
    2) Two wrongs don't make a right. If it was disruptive to mass-change articles to one spelling, it would be disruptive to mass-change them back to the other. We have a whole MOS:STYLEVAR about this, and it's also covered in more general terms at WP:MEATBOT. Mass "twiddles" of this sort are disruptive primarily because they trigger thousands of editors' watchlists for near-pointless trivia that virtually on one cares about and which doesn't noticeably improve the encyclopedia one way or the other for readers.
    3) This mass case in particular is about tabular data, which is a circumstance in which concision is valued. Given the overall meaning and intent of MOS:ABBR, the fact that a "U.S." exception is sometimes permissible cannot be interpreted as if a requirement to use the longer version for subjective reason; here we have an affirmative objective one to prefer the short style.
     — SMcCandlish ¢ 😼  16:57, 15 July 2018 (UTC)
AlexTheWhovian, I agree with SMcCandlish on this. A second AWB run would make sense to undo actual damage to an article, and would (IMHO) be uncontroversial and expected. But in this case, the edit was trivial, and a second run would be more disruptive than useful. If this discussion results in consensus for a mass-revert, then cool beans, but it doesn't look that way right now. I also don't think anyone can honestly expect an editor to manually fix several thousand changes either. Perhaps the best course of action would be to let these edits be dealt with organically by the individual editors watching the articles, with a message on your talk page (per Pyxis Solitary) to let editors know it's okay to revert your changes. — AfroThundr (u · t · c) 17:08, 15 July 2018 (UTC)
That sounds entirely reasonable. Though the message should probably point to this thread and the larger discussion about why not to revert them with AWB. >;-)  — SMcCandlish ¢ 😼  17:22, 15 July 2018 (UTC)
  • It may be helpful to disassociate this discussion from the current US vs U.S. debate (above)... the issue is how best to correct a disruptive automated mass edit. Imagine that Alex had run a script to mass capitalize the word “farm” where ever that word appeared... and now realized that this was an error... What would we tell him to do? Blueboar (talk) 17:35, 15 July 2018 (UTC)
  • Couldn't he run a script that goes through his contributions, hits "undo" on AWB edits from the period in question, saves the edits that can be undone, and logs the ones that can't? This should avoid false positives, and if he's determined to decapitalise "farm" correctly, it should reduce the manual workload significantly. Nyttend (talk) 22:34, 15 July 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Invitation of newly graduated PhDs to edit articles in their domain

Dear all

In order to improve the contents of the wiki articles and expand the coverage of relevant topics, I'd like to propose tracking and invitation of newly graduated PhDs and specialists to edit articles in their relevant domains. It would be wonderful if new specialists got invitations with a list of Wikipedia topics they might be interested in editing

Regards, TZ — Preceding unsigned comment added by Tany Zyu (talkcontribs) 17:42, 15 July 2018 (UTC)

A nice idea, but per WP:EXPERT not a great idea. I also find it unlikely that recent recipients of PHDs are setting as their first task a place to work that offers no pay and no benefits. Beeblebrox (talk) 18:01, 15 July 2018 (UTC)
We'd be asking them to walk into an editing situation entirely alien to them - they are trained to do original research and synthesis. Which of course is just endorsing what Beeblebrox has linked to. Doug Weller talk 18:42, 15 July 2018 (UTC)
To be fair, Wikipedia offers the same benefits as most post-doc and sessional instructor positions. -- Ajraddatz (talk) 05:55, 16 July 2018 (UTC)
I've been involved in quite a bit of outreach over the years, and one of the most basic lessons that I have learned is that our target for new editors is intelligent altruists with spare time on their hands and an interest in Wikipedia. New PhDs certainly meet one of those criteria...... ϢereSpielChequers 22:15, 15 July 2018 (UTC)
Indeed. And we do very well out of not-yet-graduated doctoral students looking for a distraction or excuse not to get on with their thesis. WP:EXPERT certainly does not mean we discourage expertise - a wierd idea. Johnbod (talk) 22:24, 15 July 2018 (UTC)
WereSpielChequers, the altruistic part? --Izno (talk) 23:28, 15 July 2018 (UTC)
I don't know if PhDs are more or less altruistic than society in general. Does anyone have data on that? ϢereSpielChequers 05:37, 16 July 2018 (UTC)
Without repeating what our many essays on expert engagement already say (which I agree with to varying extents), and having worked on this a bit, including Wikipedia:Wikipedia Fellows (although I'm only commenting as a volunteer in this thread), the impression I have is that the ease with which we can get new PhDs to contribute (or academics in general, but especially early career academics) varies significantly by field. That's not to say academics in some fields are more capable of editing, have an easier time adapting to the Wiki Way, or are more interested to edit, but that the activity of contributing to Wikipedia can more easily be considered relevant to one's academic career in some fields rather than others. If you're encouraged to do so professionally, you're more motivated to put in the effort to learn the policies and guidelines and persist when ol' Randy comes by. One good example is sociology, and in particular the emphasis on public sociology. Contributing to Wikipedia is easy to justify as doing public sociology, and the American Sociological Association was among the first participants in the Wikipedia Fellows program. It fits in well with any department that sees as a priority dissemination of knowledge to the general public and/or engaging in collaborative communication of the discipline beyond traditional publishing. Doing public sociology on Wikipedia means engaging with the discipline in a novel way -- that's something people get excited about, and something that makes for an easy conference proposal. There's a similar way in to many humanities and social science fields, but it's a harder sell with others. Generally speaking, academics/professionals in fields like chemistry, electrical engineering, mathematics, physics, business administration, biology, etc. are simply expected to have other priorities. Yes, there are aspects of these (science communication, for example), but it's more often a niche/specialty. $0.02 — Rhododendrites talk \\ 03:02, 16 July 2018 (UTC)

Youtube's wikipedia blurb inclusion on "fake news" terms now appears to be live

YouTube announced it was going to do this a while ago [39], but it now appears to be live: if you search for "global warming" on YouTube now, you are first going to get a hit for the Wikipedia entry for global warming. Further, any video that appears to be named with "global warming" has this blurb box just under the video before other details. This is regardless of the nature of the video, so it's on both those that support/recognize that GW exists as well as those that deny it.

I cannot immediately find any other search term that immediately triggers this, but I'm sure they are there or will be added soon.

We may want to 1) compile that list as we learn of the terms that are listed, and 2) establish semi-protection or be prepared to do so on these pages since I can see this is only going to draw a large amount of traffic including those that are going to be very disagreeable. A further point may be to review those lede sentences that YT is using for all found articles just to make sure that they are presented as neutrally as possible but within the bounds of UNDUE and FRINGE. (The borrowed text from our Global warming article seems fine). --Masem (t) 16:01, 18 July 2018 (UTC)

Found a few more "triggers": "Holocaust" and "Moon landing". --Masem (t) 16:05, 18 July 2018 (UTC)
Wikipedia:YouTube links to Wikipedia was started for this - it's a little thin, but it exists. Chris857 (talk) 16:06, 18 July 2018 (UTC)
They have clearly added more since July 9th, the ones I've found, I added. --Masem (t) 16:13, 18 July 2018 (UTC)
And on double check, those are EB links, not Wikipedia (when they come up on YT). --Masem (t) 16:15, 18 July 2018 (UTC)
I've just looked at YouTube, entered "global warming" as a search term and run the search. The first two entries (after ignoring the ad) are from National Geographic, then others from a variety of sources. Nowhere in the first 100 entries is Wiki shown. [40] According to the logo I'm looking at YouTubeGB, so is this possibly a US-only thing? Martin of Sheffield (talk) 16:24, 18 July 2018 (UTC)
Nope...I get the same here in the US... Nat Geo... then other vids... nothing from Wikipedia. Mobile vs desktop? (I searched via mobile). Blueboar (talk) 17:25, 18 July 2018 (UTC)
Searching from the UK, no entries on Chrome (Desktop) for Wikipedia Lee Vilenski (talkcontribs) 08:49, 19 July 2018 (UTC)
It is very likely that Youtube does a gradual rollout for things like this. I wouldn't be surprised about differences in behavior between various users for several weeks. —TheDJ (talkcontribs) 09:28, 19 July 2018 (UTC)
A/B testing seems a likely scenario for rolling out a feature like this. Screenshot here, for those who can't seen it yet. — AfroThundr (u · t · c) 01:44, 20 July 2018 (UTC)
It looks like the state-sponsored media tags now also link to Wikipedia. When watching videos from CBC News, I am now seeing "CBC is a Canadian public broadcast service Wikipedia" or "SBS is an Australian public broadcast service Wikipedia". The notices have been around since February, but the Wikipedia link is new. --Ahecht (TALK
PAGE
) 21:00, 19 July 2018 (UTC)
Strange, when I ran "The Holocaust" through YouTube search, it came up with Encyclopaedia Britannica... I suppose it's a phased roll-out, with Wikipedia used for particular topics only. Javert2113 (Siarad.|¤) 22:30, 19 July 2018 (UTC)
That was my bad, actually. I was updating the link by Chris857 above, and realized Holocaust and Moon Landing pointed to EB, not WP. Since per that same link that the WMF appeared to agree to a trial of a limited number of pages, this might just be seeing how trying several similar sites works out for them. --Masem (t) 22:34, 19 July 2018 (UTC)
All good, Masem. Hope you're doing well. I'll be keeping an eye on the page, if nothing else. Javert2113 (Siarad.|¤) 22:37, 19 July 2018 (UTC)
Searching for global warming on youtube gives me a wikipedia blurb but that's the only one I've seen. Natureium (talk) 22:40, 19 July 2018 (UTC)

In the other direction, Wikipedia links to about 22,000 unique YouTube URLs (for the top-10 wikipedia languages) - not many considering YouTube is among the top 5 websites. I guess we don't consider YouTube as much as YouTube considers Wikipedia. Sort of like a trade gap. -- GreenC 22:56, 19 July 2018 (UTC)

Merge proposed: WP:NCCOMICS to MOS:COMICS (which is already ~50% NC material)

FYI: Pointer to relevant discussion elsewhere.

Please see Wikipedia talk:Manual of Style/Comics#Merge in WP:NCCOMICS

We have WP:Manual of Style/Comics, the top half of which is naming-conventions material. Then we have WP:Naming conventions (comics), a competing comics naming convention. This is a silly WP:POLICYFORK. Having a combined guideline is thus proposed, based on successfully combined MoS/NC pages in other topics.  — SMcCandlish ¢ 😼  08:43, 19 July 2018 (UTC)

Meta: Consultation on the creation of a separate user group for editing sitewide CSS/JS

Moved from Wikipedia:Village pump (proposals): --Pipetricker (talk) 09:15, 19 July 2018 (UTC)
FYI: Pointer to relevant discussion elsewhere.

(I posted this here after removing it from Cent (the link wasn't to the discussion), but have now reinserted it there pointing to the Meta talk page. There's also a discussion on WP:Village pump (technical).) --Pipetricker (talk) 17:04, 19 July 2018 (UTC)

  • Comment - the specific link to the short discussion on technical is at LINK. The non-meta discussion should presumably focus on which admins get the right Nosebagbear (talk)
    Not everyone is proposing this be limited to admins. It's a technical thing, and could be available to those competent to do the work and vetted with a trust level, like WP:Template editor and WP:Page mover.  — SMcCandlish ¢ 😼  22:25, 18 July 2018 (UTC)
  • There certainly is a discussion at Meta, it's just on the talk page: meta:Talk:Creation of separate user group for editing sitewide CSS/JS.  — SMcCandlish ¢ 😼  22:25, 18 July 2018 (UTC)
    You're right; perhaps I should've just changed the link to point to that talk page rather than removing it from Cent. --Pipetricker (talk) 08:59, 19 July 2018 (UTC)
  • From the way the discussion is going, there will be a few local policy decisions to be made:
    • Should local bureaucrats be allowed to add/remove the interfaceadmin group? (Likely answer here is yes)
    • Should this group be restricted to sysops only? (This will be a lively debate)
    • What process should be used to grant this permission? (May be a global requirement for an RfA; given the nature of the access an RfA-type process would be preferable)
-- Ajraddatz (talk) 22:53, 18 July 2018 (UTC)
I'll briefly repeat what I said over at the Meta talk page: template-editor is actually far more dangerous than this. >;-)  — SMcCandlish ¢ 😼  12:40, 19 July 2018 (UTC)
Not at all. JS editing has caused serious security breaches including some five admin accounts and one steward account, granting OS-level access to a random troll. JS has been used in the past month to cause massive vandalism to Meta (I personally reverted some of the 40,000 edits made within minutes). CSS has been used to disrupt viewing an entire wiki and make it more difficult to revert the vandalism. These are powerful permissions that can do more than anything in the admin toolset, and are finally being moved to a more appropriate place compared with their potential for harm. -- Ajraddatz (talk) 15:30, 19 July 2018 (UTC)
My personal opinions:
  • Sure, local 'crats here should be able to grant/remove it.
  • I see no reason to formally restrict this to sysops only, the same as we don't currently require 'crats or checkusers to also be sysops. It'll probably naturally work out that way anyway for the most part.
  • As for the process for granting it, my take would be:
    • In general, a community discussion along the format of RfA. The goal should be to evaluate both the candidate's trustworthiness and their technical skill.
    • The permission should be removed from anyone who hasn't used it in some reasonable period of time, e.g. 3 months, maybe less.
    • Re-adding the group after resignation or removal-for-nonuse should follow the "cloud" model that's currently used for requesting re-sysop at WP:BN.
    • Anyone who has made good use of this ability while it was part of the sysop package can request "re"-adding per the previous bullet. 'Crats may want to exercise their power to require a new RfX more strongly here depending on the details of the past use, and of course a new RfX should be required if the 'crats wouldn't re-sysop the person.
Anomie 16:39, 19 July 2018 (UTC)
Someone with this permission could insert malicious javascript to hijack admin accounts to perform admin actions on their behalf. Therefore I agree with you that any non-admins granted this right would need to go through an RfX process. I'm not quite as sure about requiring an RfX for existing admins who request it, since they already have the community's trust. Under your proposal, would a new admin candidate have to go through a second RfX to get this userright, or could they request it as part of their RfA and be vetted for both at the same time? --Ahecht (TALK
PAGE
) 20:08, 19 July 2018 (UTC)
I'd hope it could mean be one less thing to consider in a normal RfA. Passing a "normal" RfA would speak to the candidate's trustworthiness, yes, but not to their technical skills with JS and CSS which are necessary for someone wanting the new group.

I'm not sure on allowing a combined RfA for both rights versus requiring separate discussions; the former is fewer separate discussions people have to have, while the latter allows each discussion to focus on the issues unique to each group instead of things getting muddled by mixing them. Anomie 15:54, 20 July 2018 (UTC)

My opinions:
  • Crats should be able to add/remove this. They're the ones who are trusted with the advanced technical tasks (bots) and advanced permissions (sysops).
  • A pseudo-RfX process would be required. Community comment is mandatory. The candidates must have the level of trust of an admin. Their understanding of consensus and technical skills must be beyond reproach. A full-blown RfA is not needed, and a lighter process is sufficient.
  • The bit should be removed for inactivity (3 months is fine), and on request. The "cloud" model for readding is fine.
  • There's no reason to restrict this to sysops only, and I can see plausible cases where I'd support adding this permission without adding sysop. Tazerdadog (talk) 00:38, 20 July 2018 (UTC)
  • It's pretty easy to just do a !vote like for admins on meta: for example. — xaosflux Talk 00:43, 20 July 2018 (UTC)
  • Throw in some rough guidelines like WP:TPEGRANT and it should be a smooth process. ~ Amory (utc) 01:09, 20 July 2018 (UTC)

Merge the Cyrillic advice to one guideline

FYI: Pointer to relevant discussion elsewhere.

Please see Wikipedia talk:Manual of Style#Merge the Cyrillic advice to one guideline

Gist: merge overlapping WP:Naming conventions (Cyrillic), WP:Romanization of Russian, WP:Romanization of Ukrainian into one page, to resolve the WP:POLICYFORK.  — SMcCandlish ¢ 😼  12:44, 19 July 2018 (UTC)

Technical

Remex: My page is recently broken and I can't figure out why

A new parsing tool called Remex is now cleaning up the HTML output for a webpage. It may cause some pages to display in undesirable ways. Be patient while we work out the kinks, and feel free to report problems in a new subsection here:

Visible bullets in infobox

FYI: Pointer to discussion elsewhere

See Template talk:Infobox musical artist#Visible bullets at Limp Bizkit. --Redrose64 🌹 (talk) 20:58, 5 July 2018 (UTC)

Post-Tidy fix may be needed at Template:Infobox NFL team

This link currently shows me different rendering of the bullets under "Playoff appearances (10)" and "Home fields" in {{Infobox NFL team}}. The Tidy version on the left renders normally, with bullets inside the infobox and aligned with the bulleted lists above these bottom sections. The post-Tidy version, which is currently live, shows the bullets for these two sections sitting just outside the box that outlines the infobox. I don't see an obvious cause of this problem. – Jonesey95 (talk) 03:04, 6 July 2018 (UTC)

I hacked the {{Infobox NFL team/sandbox}} with div tags wrapping the problematic list items. Is that terrible? It seems to work. If I put /sandbox into the edit above and preview it, everything looks fine. I wonder if a similar fix would work for Infobox musical artist, or if there is a more general fix that is needed. It seems like it would be a challenge to do something like this to every infobox field that might have bullets in it.
And it doesn't explain why the "Team nicknames" section renders just fine. Is it because the header and data use different numbers in the broken sections? I don't know enough about how infoboxen work to know what effect that numbering has. – Jonesey95 (talk) 03:18, 6 July 2018 (UTC)
Jonesey95: See my response at Template_talk:Infobox_musical_artist#Visible_bullets_at_Limp_Bizkit. The same reasoning applies to this infobox. Presumably, fixing that module would fix this too. SSastry (WMF) (talk) 09:13, 6 July 2018 (UTC)

Peculiar html rendering issue

As of just the last little while, most of the html-defined fields I am currently using on my user page are suddenly rendering a vertical bar (|) that is not in the supplied text; this occurs only in fields which possess some degree of text however. I'm not even sure what the namespace is to which the "{|" syntax points, so I can't investigate further, but I assume that the problem is not isolated to my user page (if I made some kind of error which cause this rendering, it would have had to have been a while back and I can't imagine I went that long without noticing). I've been off project for a few days, so the alteration may have occurred at any point during as far as I know. Anyone have some thoughts? I'm not too concerned about the user page, but I do wonder if there are content or policy pages affected. Thanks in advance for any insight. Snow let's rap 01:23, 8 July 2018 (UTC)

@Snow Rise: You have 4 dozen lint errors and Remex was just enabled. (I have consequently moved your section.) --Izno (talk) 02:30, 8 July 2018 (UTC)
I believe the cause is <span style="border: 1px solid">, which is unclosed. Is it your intent to have that span? I think I got them all (and it was indeed that). There might be still remaining lint errors. --Izno (talk) 02:46, 8 July 2018 (UTC)
I have cleaned the rest of the page a good bit. There are still some remaining lint errors that I don't want to fight with right now. I think they are due to some unclosed span tags bumping into block elements like the horizontal rules. Let me know if I didn't quite get some set of stylings right on the page. --Izno (talk) 04:26, 8 July 2018 (UTC)
It all looks good to me, Izno. I had no idea about the Tidy->Remex shake-up and didn't realize the number of lint errors I had that would no longer get the benefit of Tidy. Thank you for clarifying the matter and for taking the time to clean up so many of the errors--it was a very generous use of your time! Snow let's rap 06:14, 8 July 2018 (UTC)

Unclosed tag in a user message template

I just realized the user message template {{Pending changes reviewer granted}} (formerly {{Reviewer-notice}} and {{Reviewer granted}}) had contained the code <tt>reviewer<tt> with an unclosed <tt> for good 4 years and have affected over four thousand User talk pages. It looks like the code had no effect on appearance but with the recent installment of the Remex parser it has broken all the pages the template was substed onto. Can someone fix them with a bot? (Or is someone already?) And I wonder if there is any other similar case where a subst template has plagued pages with unclosed tags... Nardog (talk) 15:47, 8 July 2018 (UTC)

I'll request a bot task here for High/Medium Linter cleanups for Fluxbot - our review and approval process can be somewhat lengthy. — xaosflux Talk 15:51, 8 July 2018 (UTC)
See Wikipedia:Bots/Requests for approval/Fluxbot 7. — xaosflux Talk 16:00, 8 July 2018 (UTC)
As an FYI, in this use, we should probably use {{subst:tt|reviewer}} rather than fixing the unclosed tag.
As for bot tasks, I think you should probably use separate tasks for this rather than a Fluxbot 7, regardless of bureaucracy. Not all changes can be automated and even those that can will have different approaches (especially e.g. obsolete elements). --Izno (talk) 16:39, 8 July 2018 (UTC)
@Izno: these will mostly not be automated, just explicit batches if approved. As for the error and fix described above, fixing the bad tt close is the "obvious" fix for this error, and the one most normal editors would make, why would you not want to see it fixed that way? — xaosflux Talk 21:57, 8 July 2018 (UTC)
Because it is not just unclosed, it is obsolete. Kill a second bird with the stone. --Izno (talk) 22:32, 8 July 2018 (UTC)
But why subst {{tt}}? That adds extraneous code in the source. If you're suggesting substitution so as not to increase the transclusion count, then I'd rather see the <tt> tag removed entirely. Nardog (talk) 22:44, 8 July 2018 (UTC)
The writer wanted special markup for this text, making there be no markup is a big step. I'll probably withdraw my BRFA on this, I expect this type of argument over every cause of each error to take place and I'm not going to deal with tracking a consensus build for each use case. — xaosflux Talk 23:00, 8 July 2018 (UTC)
I guess you can just throw your hands up. :) I'd welcome these bot tasks--I just think it would be better to take them one at a time--otherwise people will argue that a certain change isn't in the scope of the task, or if it is they'll argue that the scope of the task was too broad, and then you're stuck pausing an entire task. --Izno (talk) 23:11, 8 July 2018 (UTC)
The text was in quotes in addition to <tt> anyway... I'm fine with any option (closing, removing, or {{tt}}) except subst. Nardog (talk) 23:24, 8 July 2018 (UTC)
@Izno: some of these pages are a mess, with variances of CODE, TT, SAMP, etc causing the entire page formatting to break - but there is no way I'm going to track a complicated series of fixes, if I come across these in normal editing the only thing I'm probably ever going to do is add/repair the closing tag - I'm well aware of the bureaucracy around here and that editors are passionate about different methods of markup. If there is consensus that making the pages "better" was fine this would be a non-issue, but trying to get a strong consensus for what the "best" is and changing pages from bad to "the best" in one step is way beyond my patience to manage. Feedback is still welcome of course! — xaosflux Talk 00:41, 9 July 2018 (UTC)
I agree with Xaos about making the jump from "tt was used only for convenient styling" to "we should remove the styling entirely" as well. And yes, mostly just to not deal with the transclusion count. Our current template should probably subst/use the markup directly for that as well (or decide whether one of the tt replacements is better; maybe samp?). --Izno (talk) 23:11, 8 July 2018 (UTC)

Horrible colour and font on article talk page

On Talk:King George V-class battleship (1939) most of the text is in a horrible colour and font. I can't see what is causing this. Can anyone fix it please? DuncanHill (talk) 15:11, 9 July 2018 (UTC)

 Done. An old signature from Ed had a couple unclosed <font>...</font> tags. –Deacon Vorbis (carbon • videos) 15:23, 9 July 2018 (UTC)
Undoubtedly related to MediaWiki's new HTML parser attempting to fix broken HTML differently than Tidy did. I've fixed them. SiBr4 (talk) 15:31, 9 July 2018 (UTC)
How odd, I swear I made the exact same changes you did at the same time (in 2 separate edits even), and it didn't even tell me that there was a conflict. Sorry if it seemed like I was trying to take credit or something. –Deacon Vorbis (carbon • videos) 15:33, 9 July 2018 (UTC)
  • Thank you, looks a lot better now. DuncanHill (talk) 15:41, 9 July 2018 (UTC)
  • Talk:USS Nevada (BB-36) has the same issue, I think I fixed some of it, but there's a lot of that signature... Chris857 (talk) 18:20, 11 July 2018 (UTC)
    The level of my annoyance knows no bounds. --Izno (talk) 18:36, 11 July 2018 (UTC)

Location Map Template Issues

Hi - hopefully someone can help me with this issue. I regularly edit English rugby union league pages on Wikipedia and use location map templates to show the teams in each league. I have not had any real issues until recently when I noticed that using position=top or position=bottom started to create an unusually large space between the location marking and the team in question (see examples below - Whitchurch, Longton, Dudley K). This has caused many of the pages to become very cluttered and make it difficult to work out where teams are. Would appreciate any feedback. Thanks. Jgjsmith006 (talk) 09:37, 10 July 2018 (UTC)

@Jgjsmith006:This is due to an incorrect usage of {{location map~}} made visible by the recent changeover from Tidy to remexHTML. You shouldn't be wrapping the labels in divs to change their size. There is a dedicated parameter named "label_size" which should be used. I've corrected the Whitchurch label in your example, so that you may compare. —TheDJ (talkcontribs) 11:59, 10 July 2018 (UTC)
@Jgjsmith006: Also, 70% is way too small, it is very much against MOS:ACCESS#Font size. I can't read it, so I doubt that one or two other people I could name (RexxS for instance) can read it either. --Redrose64 🌹 (talk) 07:13, 11 July 2018 (UTC)
Thanks Redrose. I will try and make it bigger but the problem is that there is often not enough space for all the times. Perhaps if the maps had more options when to place text (e.g. top left, bottom right etc) it might be easier. I wouldn't mind someone doing a proper West Midlands map (not just the county) so I could fit more of these teams in with bigger text. I had a go at creating maps but couldn't make head or tails of them. Do you know anyone who might be able to help me with this? Cheers. Jgjsmith006 (talk) 19:56, 11 July 2018 (UTC)
Have you considered a dynamic map do achieve that goal? See mw:Help:VisualEditor/Maps for the easy way to do it (in the visual editor). A basic one is easy enough that even I can do it.  ;-) Whatamidoing (WMF) (talk) 02:06, 12 July 2018 (UTC)
Nilfanion (talk · contribs) has created lots of SVG maps like this one. --Redrose64 🌹 (talk) 10:04, 12 July 2018 (UTC)
Thanks guys will try your advice. The maps look better with the new labels and are much clearer at size 75. Nilfanion has done a map before for me but I had forgotten their details - I will get in touch - thank you all once more. Jgjsmith006 (talk) 19:45, 13 July 2018 (UTC)

HTML formatting issues in archived talk pages

I don't know if this has anything to do with Linter, Tidy, or Remex, but I have only begun noticing this since these changes were implemented. Specifically, I have recently been encountering what appears to be HTML errors in talk page archives, usually having to do with unclosed tags that cause the rest of the page to be formatted with that HTML markup. For example, I just came across this: Wikipedia:Administrators' noticeboard/IncidentArchive962#Edit-warring at AIV (permanent link). Unless this is a problem on my end, the rest of the page from that point on is stricken due to <s>added<s> lacking a slash in the closing tag. It appears that the unclosed tag HTML error was added and never fixed (even though a bolding issue was noticed and fixed in the very next edit) before being archived, but the fact that nobody fixed it despite being live for days before archival suggests to me that the endless strikethrough formatting was not rendering at that time. Now it is, though.

This is not the only incident. I have seen similar formatting issues in other archived talk pages, but only recently, such as signature formatting being applied to the rest of the page due to the absence of closing HTML tags. I do not have links to those other particular incidents, since they are rare and I initially did not think much of them. I am beginning to wonder if there might be a connection here, though, since I have been perusing archived talk pages for years and do not recall once ever encountering such issues until the past month.

Might this have anything to do with the new parsing changes? Maybe this is related to mw:Help:Extension:Linter/multiple-unclosed-formatting-tags? Or is this old news and I have only just recently been encountering it?

Lastly, I recently fixed missing closing tags at Wikipedia talk:Courtesy vanishing. I don't know if this is at all related, either. Given how it was clearly causing rendering issues for the entire page after those closing tags were removed in August 2012 during improper signature refactoring by the user subsequent to their post being autosigned in previous edit, I find it difficult to believe that it has gone unnoticed for nearly six years by 38 users over 76 edits. But who knows, maybe it was and this is just all coincidence. —Nøkkenbuer (talkcontribs) 05:53, 15 July 2018 (UTC); revised 08:18, 15 July 2018 (UTC)

@Nøkkenbuer: Yes, this is because of Remex. I've run into these formatting problems at least once. I don't know if there's any plan to fix them right now (you could ask at WT:Linter or WP:BOTREQ), but errors in articles have been given higher priority than old signatures. Jc86035 (talk) 06:54, 15 July 2018 (UTC)
Thanks for the information and confirmation, Jc86035. Should I, or any other editor, manually fix these formatting errors in talk page archives whenever we encounter them? Or should they remain untouched? I understand that talk page archives are almost never edited outside of occasional bot edits, categorization, and manual archival, so I assume a hard no. That is why I have not attempted to fix any of these errors. Assuming we should not, is it worthwhile to report instances here or somewhere? Or would that not be useful information? Any further instruction on this matter is appreciated. —Nøkkenbuer (talkcontribs) 07:10, 15 July 2018 (UTC)
@Nøkkenbuer: I don't know and I can't tell you what to do, but I think that if it's fixable by a bot (i.e. stuff like <s>…<s> → <s>…</s>), it's probably not worth your time. There are thousands upon thousands of them in any case. Jc86035 (talk) 07:16, 15 July 2018 (UTC)
I suppose so, especially since this may just become routine cleanup work for some near-future bots, anyway. If anyone reading this has any input, please give it. Until further notice, I'll just ignore these errors. Actually, what is stated at Wikipedia:Linter § How you can help (permanent link) basically answers my questions. I may not actively seek them out, but I might as well manually fix them whenever they are encountered.Nøkkenbuer (talkcontribs) 07:35, 15 July 2018 (UTC); revised 07:48, 15 July 2018 (UTC)
I would advise against changing archives unless you feel like a glutton for punishment and time wasting, unless you're trying to read something and the styles are causing the text to be difficult to read or are unintelligible. Active talk pages, it might be valuable to clean up. Maybe someone can put together a query for talk pages (any talk pages or those with new section edit link magic word outside mainspace) with errors which do not have "archive" and a / in the page name. --Izno (talk) 23:41, 15 July 2018 (UTC)
I have fixed the WP:VPT archives numbered higher than 145 insofar as fixing the few unclosed <code> tags and similar that were most strikingly affecting readability. The pages still have plenty of other lint errors. --Pipetricker (talk) 10:25, 16 July 2018 (UTC)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

On the contrary, I think this is a fairly huge change that more administrators and the enwiki community at large should take an interest in. Killiondude (talk) 19:57, 9 July 2018 (UTC)
Eh, I don't know about that. I read the page (and the talk page), and the gist seems to be that the local bureaucrats will be able to assign the "delete the Main Page" button separately from the "install malware" button. We might choose to have an "WP:RFJS" to go alongside WP:RFA, but we're still the ones deciding who gets which rights. It doesn't seem like a big deal to me. WhatamIdoing (talk) 02:38, 12 July 2018 (UTC)
  • This is seeming fairly inactive here, and it just got removed as a conversation topic on policy. Surely some consideration of how this is going to be allocated as a user right needs to be considered, even if we're just going to say "admins who ask for it"? Nosebagbear (talk) 21:14, 18 July 2018 (UTC)
    @Nosebagbear: If this is something that communities will be allowed to manage is still being discussed - a trend is that bureaucrats will be able to manage this locally, but follow the discussion at meta:Talk:Creation of separate user group for editing sitewide CSS/JS. — xaosflux Talk 21:19, 18 July 2018 (UTC)
    @Xaosflux: it is, but with the date approaching rapidly a reasonably conditional answer should probably be considered. At least one wiki is currently running its decision process on the issue. — Preceding unsigned comment added by Nosebagbear (talkcontribs) 21:28, 18 July 2018 (UTC)

Not everyone is proposing this be limited to admins. It's a technical thing, and could be available to those competent to do the work and vetted with a trust level WP:Template editor and WP:Page mover.  — SMcCandlish ¢ 😼  22:26, 18 July 2018 (UTC)

This needs so much more trust than TE and PM: if you can serve someone Javascript then you can do anything they can do on the API, including admin functions like deletion and blocking. BethNaught (talk) 22:43, 18 July 2018 (UTC)
Exactly, as stated by Tgr in the consultation, it is advised to give this to users who at LEAST have as much community trust as sysops. That doesn't mean you have to BE a sysop, but that at trust level, they are equal to sysops, just with ALSO skills in a particular area. —TheDJ (talkcontribs) 14:17, 19 July 2018 (UTC)
Note that you don't actually have to be an admin to be a bureaucrat either, even though a bureaucrat could make themself an admin if they wanted to. You don't have to be an admin to be a checkuser either. In both cases, though, most if not all are also admins just because that's the way trust tends to work, and it could turn out to be the same for this new group. Anomie 15:45, 19 July 2018 (UTC)
No, that's not really correct. WMF policy requires all editors who have access to particular, sensitive information to have gone through a community vetting procedure at least as stringent as that for RfA. On emwp, the only procedures that would likely count presently are RfA, RfB and the ArbCom elections. Since no successful candidate at ArbCom and RfB has been other than an admin, it follows that currently, only admins, de facto, can take on the advanced permissions you mention. --RexxS (talk) 12:43, 20 July 2018 (UTC)
"No one has" is not at all the same thing as "no one can".

Also, BTW, Wikipedia:CheckUser#cite_note-1 says that the current CU appointment process also satisfies the WMF requirement (with reference to this diff). Anomie 15:10, 20 July 2018 (UTC)

  • So, a few potential options, (if it turns out to be relevant!) bearing in mind trust level and that EnWiki is so massive that if even 10% (or 5%) of admins along that's a comparatively hefty number in an initial wave
  • a) Self-nomination - seems very risky and somewhat counterproductive in eliminating potential risks, though certainly the easiest
  • b) External Admin nomination - in a similar vein to most WP:PERM rights, perhaps with multiple admins required. Most admins are on good terms with multiple other admins and I'm concerned that any reasonable number wouldn't act as a particularly tough filter. That said, it might be a good intermediate level to handle the initial large group
  • c) Pseudo-RfA or election - this would be chaotically large for the numbers enwiki would face
  • d) ArbCom Decides - perhaps a good method for adding future individiuals but they're busy individuals and would lose a lot of time to handle a large initial group
  • e) Bureaucrats - this might be a better method, if there are sufficient active (7+?), they have some of the highest trust rates in the community and make judgement calls on admin rights. Whether we required 1 bureaucrat, or a certain number would obviously be up for consideration if this was thought best
Nosebagbear (talk) 00:03, 19 July 2018 (UTC)
@Nosebagbear: in the last 30 days, we've had about 6 or 7 admins that actually would have needed this, I don't think we're going to have a "flood" of people that can't be handled. — xaosflux Talk 01:16, 19 July 2018 (UTC)
To ease the transition, would it make sense to automatically grant this userright to all currently active administrators in good standing who have previously made edits to sitewide CSS/JS pages? They've alredy shown that they can be trusted eith editing those pages.--Ahecht (TALK
PAGE
) 15:15, 19 July 2018 (UTC)
If we want to go this way Ahecht, perhaps "in the last (year?)" would be a good caveat. — xaosflux Talk 15:19, 19 July 2018 (UTC)
@Ahecht: I'd hesitate to do it automatically, but giving those admins a fast-track "on request at WP:BN, subject to 'crat veto" (offer valid until some reasonable date) seems reasonable to me. Anomie 15:49, 19 July 2018 (UTC)

Can't delete page

I've been having some trouble with the bar (don't know the name of it) across the near top of a page, the one to the left of the Search Wikipedia box. Certain items don't show up at all, or the drop-downs don't have certain items. In this instance, the Page drop-down doesn't have Delete or delete page or whatever it normally says. I've tried refreshing. I've tried logging out and back in. While I'm here, is there another way to delete the page besides that drop-down? Thanks.--Bbb23 (talk) 01:31, 12 July 2018 (UTC)

Copy the url for the history page and replace "action=history" with "action=delete". —Cryptic 01:34, 12 July 2018 (UTC)
If you have a Page drop-down then I guess you enabled MoreMenu at Special:Preferences#mw-prefsection-gadgets. What is your skin at Special:Preferences#mw-prefsection-rendering, and what is your browser? Did you check whether Delete is under a "More" tab? Do you get Delete under a "More" tab if you disable MoreMenu? PrimeHunter (talk) 02:05, 12 July 2018 (UTC)
Thank you Cryptic; that worked. @PrimeHunter: Vector and Chrome. Delete is not under More. I disabled MoreMenu and delete is now under More. I'm still puzzled why the Page item disappeared.--Bbb23 (talk) 02:21, 12 July 2018 (UTC)
MoreMenu is JavaScript and scripts often have problems, sometimes causing other scripts to fail. It works for me. Does MoreMenu work if you preview a blank version of User:Bbb23/vector.js? PrimeHunter (talk) 02:40, 12 July 2018 (UTC)
Sorry for the late response, PrimeHunter, but I had to get off-wiki last night and couldn't continue this dialog. I'm not sure what you want me to try. I remove all the material from vector.js, click on Show preview, and then see if the Page drop-down has a delete item? Maybe I'm misunderstanding.--Bbb23 (talk) 12:01, 12 July 2018 (UTC)
Exactly. I'm wondering whether one of your user scripts is interfering. This way you can test it without having to actually save another version of your vector.js. If you preview a user js or css page then the previewed version runs instead of the saved version. You can also save an empty js page if you want but the test doesn't require it. PrimeHunter (talk) 12:13, 12 July 2018 (UTC)
No delete item in Page drop-down after Show preview. I know Chrome updates frequently. Could an update have caused the problem? I can tell you the latest version if that helps.--Bbb23 (talk) 12:44, 12 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────This sounds like Wikipedia:Village pump (technical)/Archive 164#Lost the delete button. I'm baffled how this can happen. Bbb23 I know this is a lot to ask, but could you please do the following:

  • In Chrome, go to View > Developer > JavaScript console
  • Run the code localStorage.mmUserRights.contains("delete"). This should return true
  • Also run localStorage.mmCacheDate and let me know what it says.

Doing this will help me figure out what's going wrong, and hopefully fix this bug once and for all. Many many thanks MusikAnimal talk 18:19, 12 July 2018 (UTC)

@MusikAnimal: There is no View in my Chrome.--Bbb23 (talk) 18:27, 12 July 2018 (UTC)
@Bbb23: Oh sorry. To get to the JavaScript console, try step #6 at WP:JSERROR. The keystroke for you is probably Ctrl+⇧ Shift+J MusikAnimal talk 18:29, 12 July 2018 (UTC)
  • @MusikAnimal: When I do that, I get: ... (removed) ... I couldn't format it nicely, so I did the best I could, which ain't great. I didn't do anything after that because all of those incomprehensible error messages made me very nervous. I have no clue what we're doing.--Bbb23 (talk) 18:40, 12 July 2018 (UTC)
    @Bbb23: Hehe no worries, sorry to make you do this! I actually need you to run this code, individually:
  • localStorage.mmUserRights.contains("delete")
  • localStorage.mmCacheDate
And let me know what those say. Thank you so much! MusikAnimal talk 18:55, 12 July 2018 (UTC)
  • @MusikAnimal: Don't think this is what you were expecting:
    localStorage.mmUserRights.contains("delete")
    VM136:1 Uncaught TypeError: localStorage.mmUserRights.contains is not a function at <anonymous>:1:27 (anonymous) @ VM136:1
    localStorage.mmCacheDate
    "1531427563594"
    --Bbb23 (talk) 19:00, 12 July 2018 (UTC)
    @Bbb23: Okay one more thing, run: localStorage.mmUserRights.indexOf("delete") !== -1. It should return true. Also, what version of Chrome are you using? MusikAnimal talk 19:04, 12 July 2018 (UTC)
    @MusikAnimal:. Do the returns on these commands or whatever they are really help you in this instance? Doesn't seem to work at all. But:
    localStorage.mmUserRights.indexOf("delete") !== -1
    VM126:1 Uncaught TypeError: Cannot read property 'indexOf' of undefined at <anonymous>:1:27
    Chrome Version 67.0.3396.99 (Official Build) (64-bit). I am now off to eat at a Chinese restaurant. May not be what NYC has to offer, but it's what we've got here in the hinterlands, and it's surprisingly good. Bon appetit to me.--Bbb23 (talk) 19:12, 12 July 2018 (UTC)
    They are sort of helpful, but indeed they are not returning what is expected. Do you still have MoreMenu turned on? If not, please turn it on, and run localStorage.mmUserRights.indexOf("delete") !== -1 once more. The result from the last command you ran doesn't make sense. In short, clearing your cache should resolve your issue, but I was trying to figure out what was stored in the cache before you cleared it. Oh well. I'll do some more investigation on my own and let you know if I figure anything out. Enjoy your dinner! :) MusikAnimal talk 19:31, 12 July 2018 (UTC)
    I had MoreMenu enabled. Lunch. Thank you for trying to help. I'm hoping it does what inexplicable software problems often do: go away on its own.--Bbb23 (talk) 20:44, 12 July 2018 (UTC)
    So let it be written, so let it be done.--Bbb23 (talk) 02:06, 13 July 2018 (UTC)
    @Bbb23: So it is working for you now? :) If not, WP:BYPASS should fix it. Cheers MusikAnimal talk 16:56, 13 July 2018 (UTC)
    @MusikAnimal: I didn't do a thing. It just started working again yesterday evening and continues to work now.--Bbb23 (talk) 17:04, 13 July 2018 (UTC)
    Well as you reported above, the cache expiry (mmCacheDate) was 1531427563594 in Unix time, which equates to 8:32, 12 July 2018 (UTC) -- around the time you said it magically started working again. That tells me the issue must be cache-related. This is very helpful. I now have some theories as to what might have happened. I'll get to work! Thank you again MusikAnimal talk 17:30, 13 July 2018 (UTC)

Reminder: No editing 06:00–06:30 AM (UTC), 18 July

As previously stated here in June, English Wikipedia will be read-only for up to 30 minutes (06:00 AM to 06:30 AM UTC) on 18 July because of maintenance work. Everyone will be able to read it, but you can’t edit. If everything goes well, this should just take a few minutes, but prepare for 30 minutes to be on the safe side. I'd suggest some kind of banner to warn all editors, but I think it's up to the English Wikipedia community to decide.

You can read more in the tasks linked to from phab:T197134. /Johan (WMF) (talk) 07:46, 12 July 2018 (UTC)

Alternatively (or in addition) to a banner for logged in users, in the past, some wikis decided to put a warning/reminder on the recentchanges page. Up to you. JCrespo (WMF) (talk) 08:25, 12 July 2018 (UTC)
Maybe list this at CENT for a day? I have no idea how hard it is to cook up a banner, but personally I think something official doesn't need community rubber stamping for a helpful notice. Thanks, L3X1 ◊distænt write◊ 01:40, 13 July 2018 (UTC)
I just reread CENT, it seems they don't want this put there, and recommend P:WP, however that looks fairly dead, so if no one else has been bold, I will put up a {{centralized discussion}} tomorrow morning.Thanks, L3X1 ◊distænt write◊ 01:43, 13 July 2018 (UTC)
I didn't even know P:WP existed. Natureium (talk) 19:19, 13 July 2018 (UTC)
That's the trouble with Portal space - not enough awareness. That is, other than the little boxes that get added to certain places, such as the "See also" sections of articles; the top of category pages; and inside WikiProject banner templates. --Redrose64 🌹 (talk) 09:12, 14 July 2018 (UTC)
P:WP is a redirect to Wikipedia:Community portal which is not a Wikipedia:Portal. It's linked in the left pane and had 346,486 views in the past 30 days. PrimeHunter (talk) 10:26, 14 July 2018 (UTC)
Not all portals are the content-related types found in Portal: space. There are also a handful of project-related portals in both the Portal: and the Wikipedia: namespaces. — AfroThundr (u · t · c) 19:07, 14 July 2018 (UTC)
  • I would be happy for this to be put up publically for logged-in users for the 24 hours before it occurs. Nosebagbear (talk)
    • For users in the United States, that’s 2:00A–2:30A Eastern and 11:00P–11:30P Pacific. — pythoncoder  (talk | contribs) 19:58, 13 July 2018 (UTC)

Per the Cent instructions, this discussion being listed on Centralized discussion looks like it is perhaps a (misplaced) notification of this discussion, and not a notification of the upcoming read-only event.

But any way, I think the proper way to announce the read-only time to everyone who is editing this wiki (including those not logged in), and not just to those who read Cent or the Community portal, would be a MediaWiki:Sitenotice. (Examples: one of the more recent uses on this wiki, use on testwiki.)

I think it would make sense to put up a final warning maybe 15 minutes before going read-only, and an earlier warning a couple of hours before that. --Pipetricker (talk) 01:09, 16 July 2018 (UTC)

Sitenotice should work
Hmm, looks like CentralNotice inhibits the use of MediaWiki:Sitenotice:
mw:Manual:Interface/Sitenotice says:
1. If the CentralNotice extension is enabled, it is displayed (even if not defined); see below.
and
The CentralNotice extension supersedes all other notices.
Do I understand that correctly? And if so, can CentralNotice be used? --Pipetricker (talk) 07:45, 16 July 2018 (UTC)
I asked at the phabricator task whether there will be a $wgReadOnly message displayed during the read-only time. --Pipetricker (talk) 09:22, 16 July 2018 (UTC)
At Phabricator, Marostegui wrote that the $wgReadOnly message will show:
Scheduled maintenance on enwiki from 06:00-06:30 UTC. Database in read-only mode.
--Pipetricker (talk) 09:48, 16 July 2018 (UTC) (now going off-line for a couple of weeks)
I just noticed that the above message will be preceded by the message in MediaWiki:Readonlywarning. --Pipetricker (talk) 18:01, 16 July 2018 (UTC)
You can still run Sitenotices; CentralNotice doesn't disable that. Sitenotices have the advantage of not 'leaking' to other wikis. (CentralNotice shows its English-language messages if you set your user interface language to English, no matter what wiki you're on, which means that it is less than ideal for something affecting only the English Wikipedia.)
IMO there are two major purposes in telling regulars here about this kind of event in advance, in addition to a banner during the event itself. The first is that you know exactly who's going to get most of the questions about it afterwards: you. The second is that a 30-minute outage during a 60-minute edit-a-thon would be a pretty bad experience, so ideally people who are planning events will be able to find out what's happening, and schedule around it. Whatamidoing (WMF) (talk) 17:47, 16 July 2018 (UTC)

This is starting in around 37 minutes from now. Cheers. JCrespo (WMF) (talk) 05:23, 18 July 2018 (UTC)

While you've all got your calendars out

Please make a note that there will probably be another round of server switch testing in a few months, with the attendant read-only time. Current best guess is "switch to" in mid-to-late September and "switch back" three weeks later, in October. There will naturally be about a hundred reminders between now and then. Face-wink.svg Whatamidoing (WMF) (talk) 23:03, 13 July 2018 (UTC)

Suggesting this Sitenotice

I don't really have time for this now, but I will post an edit request at MediaWiki talk:Sitenotice in one hour from now, for the following notice, unless there's already a notice up by then:

The English Wikipedia will be read-only for up to 30 minutes beginning 06:00, 18 July UTC (check current UTC time), because of maintenance work. Everyone will be able to read the wiki, but you won't be able to edit.

Feel free to suggest improvements, of course. --Pipetricker (talk) 01:33, 18 July 2018 (UTC)

Note: No Sitenotice was posted. --Pipetricker (talk) 09:00, 18 July 2018 (UTC)

Watchlist problems again

When I bring up my watchlist, it shows articles changed in the past 3 days by default. But the "Period of time to display" drop-down is populated with "1 hour" by default, so that if I click the "Show" button on my watchlist page to refresh it, I only get 1 hour's worth of changes unless I specifically change the drop down. It always resets to 1 hour, even though my preferences are set to 3 days. (IE 11 (sorry -- required by work!), MonoBook skin) WikiDan61ChatMe!ReadMe!! 15:13, 12 July 2018 (UTC)

WikiDan61, instead of clicking 'Show', try clicking the 'Watchlist' link at the top of the page to refresh it. That works with Firefox/MonoBook. BlackcurrantTea (talk) 12:36, 17 July 2018 (UTC)
@BlackcurrantTea: Yes it does, but it's still annoying that, when my preference is to have a 3 day watchlist, the watchlist then populates with 1 hour in the dropdown. This appears to be a new feature rather than a bug, but I can't say that I'm a fan. WikiDan61ChatMe!ReadMe!! 12:51, 17 July 2018 (UTC)
WikiDan61, if you see "Period of time to display" then I guess you have selected "Hide the improved version of the Watchlist" at Special:Preferences#mw-prefsection-watchlist. For me it remembers some settings at "Days to show in watchlist", e.g. 2.9 or 3.1 days but not 3 days which changes to 1 hour like you say. It appears to mainly have problems remembering options which are included in the drop-down box on the watchlist itself. PrimeHunter (talk) 13:33, 17 July 2018 (UTC)
Well, I noticed the problem before the "Improved" watchlist was rolled out, but yes, I have chosen to hide the improvements, because I liked my old tried-and-true Watchlist and found the improved version confusing. WikiDan61ChatMe!ReadMe!! 14:03, 17 July 2018 (UTC)
User:WikiDan61, would you mind checking your Special:GlobalPreferences to see if they're the same as your local Special:Preferences? I think this is a bug in GlobalPrefs (well, a mismatch between what new GlobalPrefs feature offers, and what the suddenly-slightly-outdated watchlist is trying to do). Whatamidoing (WMF) (talk) 18:17, 17 July 2018 (UTC)
@Whatamidoing (WMF): My Special:GlobalPreferences show the proper 3 day watchlist, and none of the options are checked to be made global. WikiDan61ChatMe!ReadMe!! 18:39, 17 July 2018 (UTC)

Old Watchlist Problem

There appears to be a problem with the old watchlist that resets the "Period of time to display: " back to 1 hour when the page loads rather than leaving it at what it was previously or the value selected in the preferences. Keith D (talk) 21:20, 17 July 2018 (UTC)

@Keith D: I moved your post to an existing section. It works for me to change the value in preferences to a non-integer or some other integers. PrimeHunter (talk) 21:37, 17 July 2018 (UTC)
@PrimeHunter: The field is validated but using a decimal it does not appear to work. (Incidentally the ping did not work either) Keith D (talk) 23:40, 17 July 2018 (UTC)

Error deleting file: inconsistent state within the internal storage backends

I'm getting the following error when trying to delete File:Mariko Silver Portrait 2014 1.jpg under F8. Anyone know how to fix this? Thanks, FASTILY 19:18, 12 July 2018 (UTC)

  • FWIW, I've just tried to delete it as well, and still get the same message, so it's not something temporary. Black Kite (talk) 23:16, 12 July 2018 (UTC)
  • Thanks for taking a look. I've filed a bug report: phab:T199499. -FASTILY 04:47, 13 July 2018 (UTC)

Central login

Why is central login not working for Wikidata too? And could someone connect Translatewiki in central login projects (it should be[come] part of Wikimedia, currently is only designated as MediaWiki project)? --Obsuser (talk) 00:14, 13 July 2018 (UTC)

Not sure what you mean by Central login not working for Wikidata since Special:CentralAuth/Obsuser shows Wikidata connected and in fact you edited there few hours ago. Translatewiki is also running on MediaWiki software but it is not part of Wikimedia Foundation projects hence not part of SUL wikis. –Ammarpad (talk) 04:14, 13 July 2018 (UTC)
Sometimes the system don't log in you to all of its projects for some reason. And in some projects it logs you out automatically. Stryn (talk) 06:52, 13 July 2018 (UTC)
Try to delete cookies for wikidata.org. PrimeHunter (talk) 10:58, 13 July 2018 (UTC)

Issues uploading audio files to Wikipedia

I'm trying to upload samples of audio recordings to add to an article I'm working on and am having technical issues.

I've encountered this problem using both the [en.wikipedia.org] and the [en.wikipedia.org]

I'm using Chrome version 67.0.3396.99 (Official Build) (64-bit), which it tells me is up to date, and Windows 10.

The problem is, whenever I try to upload an .mp3 file or .ogg file, wikipedia does not recognise them as those extension types. When I try to upload a .mp3 file, it says "".mpga" is not a permitted file type. Permitted file types are tiff, tif, png, gif, jpg, jpeg, webp, xcf, pdf, mid, ogg, ogv, svg, djvu, oga, flac, opus, wav, webm, mp3." When I attempt to upload a .ogg file, it says "".ogx" is not a permitted file type. Permitted file types are tiff, tif, png, gif, jpg, jpeg, webp, xcf, pdf, mid, ogg, ogv, svg, djvu, oga, flac, opus, wav, webm, mp3."

Now, I've triple checked my files and windows lists them on my screen as .mp3 and .ogg, even when you right click and look at the properties, they say .mp3 and .ogg, NOT .mpga and .ogx

So my computer is telling me they are the right type of file, but when I attempt to upload them to Wikipedia, Wikipedia believes they are a different type of file. If anyone has any advice for me on how to upload these file, it would be very much appreciated and I'm beginning to go crazy. NicklausAU (talk) 04:18, 13 July 2018 (UTC)

I transferred the exact same files from my laptop to my android phone (still using chrome) and the upload worked without any issues. I guess it's no longer as important, but would still be helpful to know about in the future. NicklausAU (talk) 04:33, 13 July 2018 (UTC)

Infoboxes erroneously wrapped in bold tags

While investigating some error logs for the mobile web site, I noticed that 170 pages have incorrect formatting which wraps the infobox in a bold or italic tag. e.g.

'''{{Infobox venue... }}
'''Subject title'' is defined in this line.

I'm not sure what's causing this problem (maybe a result of new pages being copy and pasted or edit conflicts?). I've made a few fixes myself (see Special:Contributions/Jdlrobson but obviously me manually fixing these isn't the most sustainable of ideas!

Can we get this fixed via a bot?

You can use this query] to find pages with the problem.

Jdlrobson (talk) 15:18, 13 July 2018 (UTC)

@Jdlrobson: Wallace Wade Stadium was the first page that showed up in the search, and I cleaned it up. My guess is the infobox on some articles may have been inserted after the bulk of the articles may have already been written and it was accidentally inserted after the bold string for the title. Not all of the articles listed seem to visually have issues - Brisbane, California looks normal, for example. Home Lander (talk) 15:54, 13 July 2018 (UTC)
I don't think it's quite straightforward to fix these with a bot, as many have other underlying formatting issues as well that didn't show up until the switch from html4-tidy to RemexHtml earlier this month. A lot of them do seem like they were articles started by copying and pasting another (especially the ones on ethnic groups and on rugby and football teams), and the errors are just showing up now due to Remex. I've started going through them with AWB, but each one needs a bit of manual processing. --Ahecht (TALK
PAGE
) 16:17, 13 July 2018 (UTC)
Fixed. These are all fixed now, if the insource search is working. – Jonesey95 (talk) 19:01, 13 July 2018 (UTC)

Edits are lost when changing from VisualEditor to regular editor

It seems like when I start editing an article in VisualEditor (e.g to add citations) and then change in source editor mode, the changes don't carry over between the edit windows. Jo-Jo Eumerus (talk, contributions) 17:11, 13 July 2018 (UTC)

It works fine for me, in both directions.. -- RoySmith (talk) 19:11, 13 July 2018 (UTC)
What browser, operating system, skin? --Izno (talk) 19:56, 13 July 2018 (UTC)
Firefox latest, Windows 10 and Vector. Jo-Jo Eumerus (talk, contributions) 21:51, 13 July 2018 (UTC)
Jo-Jo Eumerus, does this happen every time? If you make multiple changes (e.g., to different parts of the article), do you lose all of your work, or just some of it? Whatamidoing (WMF) (talk) 23:09, 13 July 2018 (UTC)
It seems like the issue happens when I try to change through the header buttons (these next to the "view history" button). Formerly then the page changed over with a you have changed the editing mode flag and kept previous edits. Now instead I get the "some changes may not be saved if you leave this page" popup and the edits done in the previous editing mode don't stay. Jo-Jo Eumerus (talk, contributions) 12:24, 14 July 2018 (UTC)
Thanks. I've filed a bug. Since your first edits are from 2012, I'm going to assume that you are using the 2010 wikitext editor. Whatamidoing (WMF) (talk) 21:26, 15 July 2018 (UTC)

Templates do not show up in mobile view Suggestion

Hi! I've recently noticed that templates that are at the bottom of articles like this one Template:Woman's club movement, don't show up in mobile view. Is there any way that we can correct that? I find the templates useful for navigation and would like to use it on my phone. (I have an Android.) Megalibrarygirl (talk) 22:18, 13 July 2018 (UTC)

Navigational templates have class="navbox" and are deliberately omitted from the mobile version. You can click "Desktop" at the bottom of mobile pages to see the desktop version. PrimeHunter (talk) 00:53, 14 July 2018 (UTC)
Time we put this in Wikipedia:Village pump (technical)/FAQ. --Redrose64 🌹 (talk) 12:57, 14 July 2018 (UTC)
Hi! PrimeHunter! I know I can switch to Desktop to see the template, but I think that the mobile view should encompass a view for templates, too. What can we do about that? Redrose64 do you think there is a way to make a proposal to fix this? I think it's important to do since more and more people access Wikipedia in mobile version nowadays. :) Megalibrarygirl (talk) 18:42, 14 July 2018 (UTC)
It's done on purpose to reduce bandwidth usage and page size for mobile users. Many articles have a lot of losely connected navigation templates. They wouldn't be collapsible in mobile, and their width is not designed for narrow screens. Maybe there should be an option to display them without switching to desktop but they are currently not transmitted at all in mobile so it would require a change in the software for the mobile version. This is outside control of the English Wikipedia. phab:T124168 ("Show Navbox templates in mobile skins") has a proposal. I don't know whether it's the primary discussion. PrimeHunter (talk) 19:06, 14 July 2018 (UTC)
Thanks for the answer, PrimeHunter! That makes sense and I understand better why templates wouldn't show up. Megalibrarygirl (talk) 22:37, 15 July 2018 (UTC)

Transparent png files

Is there a limit to the dimensions of a png file above which transparent pixels are rendered as white? I've created a lot of png 'cut-outs' over the years, normally small logos and such for use in infoboxes, but recently I've had a couple of fairly large png files that don't render as transparent. The most recent one is File:Trump baby balloon.png (975 × 1,000 pixels, file size: 775 KB). I can't remember the other, but it was fairly large IIRC. nagualdesign 04:44, 14 July 2018 (UTC)

@Nagualdesign: There is a bug that was recently introduced into the mediawiki software that breaks PNG transparency in thumbnails. It's been reported at T198370, but no developers have responded to even triage it, and fixing it seems to not be a priority. --Ahecht (TALK
PAGE
) 14:11, 14 July 2018 (UTC)
@Ahecht: Okay, thanks for the reply. I was going to reduce the dimensions of the image but I'll just leave it be. Cheers. nagualdesign 14:36, 14 July 2018 (UTC)

Transparent png has white background in the article

Hi, why is it that despite File:Tracks game logo.png and File:Rock, Paper, Shotgun 2018 logo.png being transparent PNGs, their respective articles (Tracks (video game) and Rock, Paper, Shotgun) have white backgrounds? Anarchyte (work | talk) 10:29, 19 July 2018 (UTC) edited: 10:45, 19 July 2018 (UTC)

That is currently being investigated, see the linked phab task. BethNaught (talk) 12:58, 19 July 2018 (UTC)
  • Weirdly enough, in the case of Universal Interactive, the logo renders as a black rectangle. Also PNG-renders of SVG images seem to have similar issues. Lordtobi () 22:25, 20 July 2018 (UTC)

Script problem

I was recently developing a script at User:FR30799386/Actiontog.js based on MediaWiki:Gadget-MobileCategories.js (I have some experience very limited experience with coding). I tried the whole script out on my browser console and the script worked perfectly, but when I try to run it on-wiki the script does not produce any result. Can anybody help out ?12:49, 14 July 2018 (UTC)

User:FR30799386/common.js says:
//importScript('User:FR30799386/MOSDDT.js'); //Linkback: [[User:FR30799386/Actiontog.js]] Added by Script installer
Everything on a line after // is a JavaScript comment. The line should say:
importScript('User:FR30799386/Actiontog.js'); //Linkback: [[User:FR30799386/Actiontog.js]] Added by Script installer
The imported page is determined by importScript. The linkback comment is just a way to affect Special:WhatLinksHere/User:FR30799386/Actiontog.js. To avoid confusion, importScript and a linkback comment should always refer to the same page. The different page names were made by you [41] and not Script installer. PrimeHunter (talk) 13:03, 14 July 2018 (UTC)
PrimeHunter, I loaded the script into my User:FR30799386/minerva.js, anticipating that the mobile skin would override my common.js (Which I believe it does) — FR+ 13:08, 14 July 2018 (UTC)
P.S. I am aware about that anomaly in my common.js, but I don't think that is causing the issue right now.Face-smile.svg — FR+ 13:13, 14 July 2018 (UTC)

Template transcluding articlespace categories onto userpages, Vol. 458

User:Just granpa/Atomic volume and User:Just granpa/Atomic volume (Alternate) are both showing up in Category:Properties of chemical elements by virtue of an artificial transclusion — but I can't find what template is pushing the category in order to get them out, because none of the obvious candidates seem to have that category declaration on them either. Can somebody look into this so the category can be properly cleaned up under WP:USERNOCAT rules? Thanks. Bearcat (talk) 14:26, 14 July 2018 (UTC)

Fixed. The categories were coming from documentation subpages. The subpages were actually holding template code not transluding them. Hence the categories coming from here and here; which are subpages of the categorised subpages. –Ammarpad (talk) 14:59, 14 July 2018 (UTC)
You can enter wikitext at Special:ExpandTemplates and search the result for the category to see where in the page it occurs. Some things are namespace or page name sensitive so you sometimes have to fill out "Context title". PrimeHunter (talk) 16:04, 14 July 2018 (UTC)

\w and \d equivalents in Mediawiki regex?

I've been trying to wrap my head around how to deal with the lack of \w or \d support in our regex functions. \d is fairly easy to deal around [0-9], but \w is nearly impossible to get around. If you use [A-Za-z], you miss out all the diacritics, as well as all non-Latin characters. What's an equivalent way of replacing \w. Better yet, why don't we support \w or \d? Headbomb {t · c · p · b} 16:07, 14 July 2018 (UTC)

Nevermind, found this. It was buried 230 layers deep in documentation, but it was there. Headbomb {t · c · p · b} 16:10, 14 July 2018 (UTC)
it's not mediawiki regex, it's Lua patterns :) I think I'm not the only one, who was confused by what you asked till I got to reading link title --Edgars2007 (talk/contribs) 15:13, 15 July 2018 (UTC)

Least edited pages

Is there a database report, or some other place, where one can locate articles (or any pages, for that matter) that have gone the longest time without being edited? Home Lander (talk) 18:07, 14 July 2018 (UTC)

@Home Lander: Special:AncientPages might help, although it mostly lists disambiguation pages. Jc86035 (talk) 18:16, 14 July 2018 (UTC)
Disambiguation pages dominate the list because there's less reason to edit them than articles proper. –Ammarpad (talk) 19:38, 14 July 2018 (UTC)
Wikipedia:WikiProject Abandoned Articles has deliberately edited all the oldest articles at Special:AncientPages. Wikipedia:Database reports/Forgotten articles ignores disambiguation pages. PrimeHunter (talk) 19:46, 14 July 2018 (UTC)

"Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."

We've just had this question posted by TheTechnician27 at the Teahouse. Can't find anything in recent VPT talk or the archives, so could someone offer a suggestion, please? The text of the question is "Whenever I switch from visual to source editing mode, I get this error message at the top of the page. Additionally, there is no chart showing the difference between the current version and my edit. This had never happened to me, but recently it's happened every time. I get this on two separate computers, and I can't seem to find any information about it. I'd like to find a way to stop this error message from showing up and to get the side-by-side comparison to show up again." Many thanks, Nick Moyes (talk) 20:28, 14 July 2018 (UTC)

@Nick Moyes: The same message generates when using WP:REFILL. I verified this just now on War bride. Load the article, click on Refill, then click "Preview/Save on Wiki" and the message will appear. I left the bare URLs alone on that article so this will continue to work. Home Lander (talk) 20:38, 14 July 2018 (UTC)
I see this message as well when I switch from visual to source editing mode and I also miss the side-by-side comparison. Jo-Jo Eumerus (talk, contributions) 20:40, 14 July 2018 (UTC)
I'm sincerely not inclined to make any more major edits without the 'diff' feature. It's just such a necessity, and I really hope this is an error and not a change in how editing works. TheTechnician27 (talk) 03:27, 17 July 2018 (UTC)
This is definitely a bug, not a feature. It looks like Anomie's got an idea of which change might have triggered this. I have some hope that this will be fixed on the next train. Whatamidoing (WMF) (talk) 18:30, 17 July 2018 (UTC)
I reported this 2 days ago in phab:T199554. Stryn (talk) 20:03, 15 July 2018 (UTC)
Stryn, or someone, can you add in Phabricator that Refill triggers this also? Home Lander (talk) 20:28, 15 July 2018 (UTC)
I did. Also, the message is MediaWiki:Edit form incomplete, which appears to belong to preview (in the older wikitext editors). Whatamidoing (WMF) (talk) 21:21, 15 July 2018 (UTC)

Can't get pages to show in my template

I just created a new citation template, Template:BLKO, but I can't seem to get the page or pages parameters to work, and I can't figure out why, so I need some additional eyes on it. Thanks in advance. howcheng {chat} 23:36, 14 July 2018 (UTC)

I don't think that it's your template but rather is a problem with {{cite wikisource}}. This example from the documentation page has |pages=100–110 but that isn't displayed:
{{cite wikisource |last=Bloggs | first=Fred |editor-first=John| editor-last=Doe |plaintitle=Big Book With Many Chapters and distinct chapter authors|publisher=Book Publishers |date=2001-01-01 |pages=100–110 |chapter=Chapter 2: The History Of The Bloggs Family |isbn=123456789X}}
Bloggs, Fred (2001-01-01). "Wikisource link to Chapter 2: The History Of The Bloggs Family". In Doe, John. Big Book With Many Chapters and distinct chapter authors. Book Publishers. Wikisource. pp. 100–110. ISBN 123456789X. 
{{cite wikisource}} uses {{citation/core}} and feeds that template's |At= parameter with a complicated mess of code that includes |page= and |pages= among a whole bunch of other parameters. You might raise the issue at Template talk:cite wikisource; perhaps there is someone there who knows what that mess of code is supposed to do and can see where is is loosing |page= and |pages=.
—Trappist the monk (talk) 00:08, 15 July 2018 (UTC)
Just fixed the isbn error at the Template:cite wikisource/doc and did some playing around with the other examples. In the above example, changing |plaintitle= to |title= makes the template render with the pages:
Bloggs, Fred (2001-01-01). "Wikisource link to Chapter 2: The History Of The Bloggs Family". In Doe, John. Wikisource link to Big Book With Many Chapters and distinct chapter authors. Book Publishers. Wikisource. pp. 100–110. ISBN 123456789X. 
—Trappist the monk (talk) 00:15, 15 July 2018 (UTC)
I went back and checked my previous usages of {{cite wikisource}} (e.g., Ferdinand III, Holy Roman Emperor § Notes) and you are correct: the page numbers aren't included, so I'll have to take it up at the template talk page. Thanks. howcheng {chat} 03:39, 15 July 2018 (UTC)

Tool idea

I was just thinking about using Template:Copyvios to build a tool that you can click on each article to see if the article has been copied from other sources, but I don’t have the technical knowledge to do it myself. I was wondering if a tool like that already exists and if not, someone will take it upon themselves to develop one?--▸ ‎épine talk 13:27, 15 July 2018 (UTC)

@Épine: See User:Ahecht/Scripts/CVD. --Ahecht (TALK
PAGE
) 15:14, 15 July 2018 (UTC)
@Ahecht: thanks but it has issues that I described on the talk page, can you please take a look?--▸ ‎épine talk 18:39, 15 July 2018 (UTC)
I fixed the script so that it defaults to "wikipedia" if the site name is something other than mediawiki, wikibooks, wikidata, wikimedia, wikinews, wikipedia, wikiquote, wikisource, wikiversity, wikivoyage, or wiktionary. See the script's talk page. --Ahecht (TALK
PAGE
) 20:52, 15 July 2018 (UTC)

Problems with the edit window when there is WikiMarkup color-shading

Referring to this thread, I still have a problem when I copy and paste text and delete it at the same time. The text doesn't get deleted, I get sent to the start of the edit window, and somehow this happened. Actually, that was my attempt to correct the mistake, and I did it wrong too.— Vchimpanzee • talk • contributions • 17:06, 15 July 2018 (UTC)

Did you notice this error on Chrome or in Firefox or in both? -- Magioladitis (talk) 11:12, 16 July 2018 (UTC)

It still happens with Edge at home. I have had the problems with Edge at a library as well. I can't remember now if it happened with Chrome. I'll post when i use Chrome again. No, I won't be using it at home.— Vchimpanzee • talk • contributions • 17:12, 16 July 2018 (UTC)
Can you tell me exactly how you're cutting and pasting? I found phab:T174635, which is about middle-click on a mouse. It's on Linux, but if you're using middle-click, then it might be relevant. Whatamidoing (WMF) (talk) 18:37, 16 July 2018 (UTC)
I hold down the left mouse button, move the mouse over what I want to copy, let go of the mouse button, and press CTRL and C at the same time.— Vchimpanzee • talk • contributions • 18:39, 16 July 2018 (UTC)
Thanks. It's probably not the same thing, then. I've started a new bug report at phab:T199739 for this. Whatamidoing (WMF) (talk) 19:04, 16 July 2018 (UTC)
The problem is not happening with Chrome at this library.— Vchimpanzee • talk • contributions • 16:42, 17 July 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Back at home, I moved some content but when I copies and pressed delete, the content did not disappear. Instead, I had to correct a mistake which was caused by the suspected bug. I had to try again deleting the information I was deleting and copying elsewhere.— Vchimpanzee • talk • contributions • 15:48, 18 July 2018 (UTC)

InternetArchiveBot is malfunctioning

InternetArchiveBot (v2.0beta2) is malfunctioning and making edits like this. I've reported but the edits continue. --Auric talk 12:22, 16 July 2018 (UTC)

Template:Search

Hey all, something seems amiss with {{Search}}. If I employ it here all of the different search options are mashed together.

According to the template documentation, we should be seeing

(wp gwp g bwp b | eb co gct sw arc ht)

I appreciate if anybody can look into this. Thanks, Cyphoidbomb (talk) 15:51, 16 July 2018 (UTC)

@Cyphoidbomb: Looks like more fallout from the change from Tidy to Remex. I've modified the module to add spaces back. --Ahecht (TALK
PAGE
) 17:47, 16 July 2018 (UTC)
@Ahecht: I have no idea what most of that means, but I'm grateful that you were there to figure it out. Face-wink.svg Cyphoidbomb (talk) 04:21, 17 July 2018 (UTC)

Tech News: 2018-29

16:00, 16 July 2018 (UTC)

Adopting unmaintained user script

I've been maintaining a version of Technical 13's CVD script at User:Ahecht/Scripts/CVD, and have fixed a few bugs related to performance, depreciated API calls, and use on non-english Wikipedias. Per the note at User:Technical_13/Scripts/Nav, Other users are encouraged to take on the task of developing and maintaining it. EdJohnston recommended that I ask here if there is any objection to redirecting the unmaintained script to my version (as requested at User talk:Technical 13/Scripts/CVD.js#Requested edit 16 July 2018)? --Ahecht (TALK
PAGE
) 18:12, 16 July 2018 (UTC)

I'd much prefer to have the users update to the new location, is there any idea the number of pages that would need updating? — xaosflux Talk 18:19, 16 July 2018 (UTC)
With a quick search I count about 13. ~ Amory (utc) 18:53, 16 July 2018 (UTC)
@Xaosflux: I count 13 user js pages as well from this search(excluding Technical 13's own vector.js page): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, and 13. I couldn't find any mentions in global.js files at meta, and I didn't search any other languages or projects. --Ahecht (TALK
PAGE
) 19:44, 16 July 2018 (UTC)
@Ahecht: with it being soo little people I'd rather see: (a)Ask the users to update their own pages to point to the new script [or] (a1) have an admin force the updates for them {I don't like that either} - then (b) blank out the old script since its not being used anymore. Users should be making an affirmative choice of "I trust editor X to change javascript that could impact me". — xaosflux Talk 20:08, 16 July 2018 (UTC)
You could even change the old script so it prints a message advising people to use the new one. EdJohnston (talk) 00:33, 17 July 2018 (UTC)
100% OK with that. — xaosflux Talk 00:46, 17 July 2018 (UTC)
Okay, thanks. I'll craft a talk page message and send it out later this week, and figure out the best way to have the old script leave a message if there are any stragglers. --Ahecht (TALK
PAGE
) 14:37, 17 July 2018 (UTC)
I just migrated to my own cut-down version of your script since I don't need all the options, so you can take me off the list.
I also thought, given that copyvio detection is an important part of NPP workflow, that this tool might be useful, and gain a bigger audience, as a Gadget. Do people think that would be worth doing? BethNaught (talk) 14:50, 17 July 2018 (UTC)
I think making it into a gadget would be handy. — AfroThundr (u · t · c) 19:33, 17 July 2018 (UTC)

Watchlist "improvements" - no they're not

Who just turned off "Hide the improved version of the Watchlist" at Preferences → Watchlist, and could they please stop fooling around with my settings? --Redrose64 🌹 (talk) 18:34, 16 July 2018 (UTC)

My watchlist is all 'bleeped' up. Wish the big wigs would stop messing around with such things, without a consensus. GoodDay (talk) 18:39, 16 July 2018 (UTC)

+1 for please turn this of NOW. I've had it turned on as beta, I found it detrimental to my Wikipedia editing, and turned it back off. WMF, you again behind this? --Dirk Beetstra T C 18:42, 16 July 2018 (UTC)

Hi, My watchlist has changed and not for the better, How do I change it back ?, Thanks, –Davey2010Talk 18:38, 16 July 2018 (UTC)

See above discussion. GoodDay (talk) 18:40, 16 July 2018 (UTC)
Ah thanks, Header removed, I really do wish they'd stop with the bullshittery, Everything should be OPT-IN - If you want new things opt-in. –Davey2010Talk 18:44, 16 July 2018 (UTC)
Did it not ask? Went I last went to the watchlist, it showed a little popup, and then asked me if I wanted to opt out. ~ Amory (utc) 18:54, 16 July 2018 (UTC)
Well, if it was, User:Amorymeltzer, it was pretty hidden. Anyway, where do you turn it off when you missed it (or did not get it)? --Dirk Beetstra T C 18:56, 16 July 2018 (UTC)
And is it right next to the standard-edit-window "improvements" - which they are also not. --Dirk Beetstra T C 18:58, 16 July 2018 (UTC)
(edit conflict) Hi Amorymeltzer, Nope a little box came up saying it's a new watchlist then that was it, Thanks, –Davey2010Talk 18:59, 16 July 2018 (UTC)
The setting is in the watchlist tab of your preferences (Special:Preferences#mw-prefsection-watchlist) with the name "Hide the improved version of the Watchlist" under the heading Opt out of improvements. Not sure why I got it and you didn't Davey, especially if you got the first one. ~ Amory (utc) 19:00, 16 July 2018 (UTC)
I have no idea why, Ah well many thanks for your help :) –Davey2010Talk 19:04, 16 July 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── This might be related to a global prefs problem. I'll ping the project manager to make sure that she knows about it. She told me earlier today that extensions that set "hidden" preferences (like the RecentChanges filters and "remember my last editor" for VisualEditor's single edit tab mode – all things that you can't just edit by going to Special:Preferences) are having problems right now, and perhaps this is related. Whatamidoing (WMF) (talk) 19:15, 16 July 2018 (UTC)

Okay, now I can give you a correct answer: This is related to the watchlist filters graduating out of Beta Features. The pref technically didn't exist until the 11:00 PDT SWAT slot. And, as happens occasionally, there was a small problem with prefs, which is already being worked on. In the meantime, you can opt out manually at Special:Preferences#mw-prefsection-watchlist. The setting should be near the end of the watchlist page, located between the ==Token== and ==Revisions scoring== sections. If you don't see it (I didn't the first two or three times), try forcing the page to reload. (And if you still don't see it after reloading the page a couple of times, then please post.)
The problem with the pop-up is that the opt-out button is on the second screen of the tour, so if you immediately cancel the tour, you won't see it. Whatamidoing (WMF) (talk) 20:03, 16 July 2018 (UTC)
I quite like the changes, especially the ability to highlight various namespaces in different colours. Nthep (talk) 20:10, 16 July 2018 (UTC)
For the ones who apparently didn't get the pop-up to opt-out, here is a screenshot of it.
That graduation has been announced multiple times over the last month, on watchlist notice, on Tech News and of course on the VPT (last announce). Trizek (WMF) (talk) 10:16, 17 July 2018 (UTC)
The communication on this was always a bit "clumsy" - that a feature was leaving beta to be under normal support isn't the same as forcing it to be opt-out. I'm so glad global prefs went live so I can opt-out ni one palce, because having to go through those popups at every single project would be a real pain. — xaosflux Talk 11:30, 17 July 2018 (UTC)
It's broken the script that highlights usernames of Administrators. This puzzles me as I have related changes watchlists where the script works fine. Doug Weller talk 18:39, 17 July 2018 (UTC)

New watchlist page layout

What happened here?

2018-07-17 Watchlist page layout.jpg

This new layout appeared this morning, The litter of controls takes up half the viewing area and is a dog's breakfast of different styles. Is this a prototype being tested to see if there is a reaction, or does everyone get it? Aymatth2 (talk) 13:07, 17 July 2018 (UTC)

I quite agree. Mine appeared last night. I'd suggest the whole new panel needs a show/hide option. Martinevans123 (talk) 13:12, 17 July 2018 (UTC)
Got it last night as well. Takes up about as much space as the notifications, explanations, panels, and so forth that I had before, though maybe that was somehow my fault. It's actually cleaned things up for me. I'm happy with it, but maybe if there was the option to put it all on one line it'd look nicer on some people's monitors? Ian.thomson (talk) 13:23, 17 July 2018 (UTC)
(edit conflict) I use Timeless regularly, but I tried looking at this in Monobook and it does look a little broken compared to what I usually see (the buttons in the filters list don't display correctly). As in the picture there's a "hide" button at the right side of the box which says "Active filters"; I hadn't noticed this until five minutes ago. (It's possible to turn the new things off; see this section.) Jc86035 (talk) 13:30, 17 July 2018 (UTC)
Quick link to turn it off if you wish: Special:Preferences#mw-prefsection-watchlist and scroll down to "Opt out of improvements". —DoRD (talk)​ 14:57, 17 July 2018 (UTC)
  • Any objections to putting a ...wait for it..... watchlist notice up about the watchlist and where to change it in preferences in case you missed the popup? — xaosflux Talk 13:25, 17 July 2018 (UTC)
I strongly support this idea. Natureium (talk) 14:12, 17 July 2018 (UTC)
I see six buttons scattered around here, four of which are preferences (active/saved filters, live updates, changes/days). Surely they could all fit on one line, something like:
Mark all changes as seen
This would be cleaner and take up much less space. How do we get it done? Aymatth2 (talk) 15:30, 17 July 2018 (UTC)
  • This good faith change should actually, in my opinion, be reverted. On Monobook there was a 4 or 5 second lag every time I looked at the Watchlist, and even though users can now opt out this will affect new users who may be uncomfortable with it if not fixed (at least on Monobook, and I'm now putting it back to see how it looks on other skins). Randy Kryn (talk) 16:28, 17 July 2018 (UTC)
    There is an opt out, you should use it if u dont like it. —TheDJ (talkcontribs) 18:30, 17 July 2018 (UTC)
    Which is great and all to us users who were here before this new watchlist, who know this isn't the only form the watchlist can take, who know a lot of Wikipedia features have opt out options and who will thus opt out if they don't like it. The issue Randy Kryn describes is that new editors who dislike the watchlist may very well not even realize this is something they can opt out of, especially if they registered after the roll-out. AddWittyNameHere 18:39, 17 July 2018 (UTC)
New users also dont know they can switch to monobook, but tend to be mostly fine. While arguably it might not be perfect, perfection is the enemy of good enough. Further improvements will follow naturally as more feedback comes in. —TheDJ (talkcontribs) 19:06, 17 July 2018 (UTC)
"Dump it in, then fix it if they squawk too loud?" Surely there could have been no consensus on cluttering up the top of the watchlist with all these buttons that will hardy ever be used, when a simple "Change preferences" button (as above) is all that is needed. Aymatth2 (talk) 20:22, 17 July 2018 (UTC)
@TheDJ: If the watchlist was functioning entirely as-should, then I'd mostly agree with you. The problem is that beyond matters of opinion/preference (such as the many new options and filters), there are still some actual, objective flaws in there, especially the increased load-time in at least some set-ups. (Folks may have a preference for or against the new options, for example, but I'd be quite surprised indeed if anyone had a preference for lag. There may be folks who don't particularly care, as well as plenty folks who don't seem to be affected, but that's not the same thing). That should probably have been fixed before making it the default. (I also believe the lay-out/UI could certainly have been tightened up a bit beforehand. No, it might not be the most important thing ever to its functioning, but it plays a really big role in people's first impression and if one wants the largest possible amount of editors to give something a honest try, first impression matters a lot. It doesn't matter if it's good enough below the surface if people can't stand to look at it long enough to determine that fact.) AddWittyNameHere 23:52, 17 July 2018 (UTC)

I've already restored mine to its previous incarnation, as I too was seeing something like the above. A few confusing buttons and a large void of white space. As software it’s not even beta quality and certainly not ready for ready for deployment, I am someone familiar enough with this noticeboard that I knew to look here for the answer, but I fear many if not most editors won’t know or work out how to disable it and so will just put up with it. It should be rolled back, or at least have a prominent notice on it telling editors how to revert the previous version.--JohnBlackburnewordsdeeds 20:29, 17 July 2018 (UTC)

"Further improvements will follow naturally"...I am not sure if I should laugh out loud, given that we are clearly saying that this is not experienced as an improvement, or be in terror of what might be still coming. Oh, no, I get it... this is a promise that this change will be reverted, right? Clean Copytalk 20:41, 17 July 2018 (UTC)
He, if you all want to throw another fit, go right ahead. But it's my personal opinion as a volunteer that you guys had 6 months to give your feedback. 6 months where thousands of people tested. 6 months where improvements were made. And now you want to change the design for something you all are stating to not going to be using ? I really don't see the logic. Please explain. —TheDJ (talkcontribs) 20:52, 17 July 2018 (UTC)
I'm curious: where are the discussions by the beta testers? I'd like to see their reactions. Clean Copytalk 03:20, 18 July 2018 (UTC)
I think you'll find comments at the project's talk page: mw:Edit Review Improvements/New filters for edit review. Whatamidoing (WMF) (talk) 19:12, 19 July 2018 (UTC)
This is another case of You don't like it? Opt out and stop complaining like a 3 year old that didn't have a glass of water with ice, rather than a glass of ice filled with water. There's a big notice explaining you how to opt out if you don't like it, and if you somehow didn't catch it for whatever reason (banner blindness, banner glitch that didn't show up), you now know how to opt out, so just do it and don't hold back improvements for the 99%. I don't like the new watchlist because it interferes with some advanced scripts I'm using, but as far as the default experience, this is a much better watchlist than the old one. The UI could use a bit of tightening, but that will happen over time as more people give it eyeballs, but not so much this should hold back the entire thing. Headbomb {t · c · p · b} 20:57, 17 July 2018 (UTC)
(ec) I'm sure a lot of work will have gone into this (most of which will probably go wholly unrecognised). But sorry, the six month countdown clock was not ticking for me. Perhaps I missed an announcement. On the basis of the above comments, the community doesn't seem to be desperately engaged in, or enthusiastic about, this development. Martinevans123 (talk) 21:01, 17 July 2018 (UTC)
Eh, in such cases you tend to get the people who don't like it speaking up more than those who do. The question is if they have good arguments. I would like the new design were it not that it takes a long time to load the filter panel for me. BethNaught (talk) 21:13, 17 July 2018 (UTC)
Yes, and I suspect, just like with the late-lamented "OBOD", the vast majority of editors will just say "when did I ask for this?", or "but it was OK before", or "how do I get rid of this, as it has no obvious benefit for me?", etc., etc. Martinevans123 (talk) 21:21, 17 July 2018 (UTC)
I'm curious how many power editors have reenabled the OBOD through scripts. And I'm also curious to see whether the volume of complaints dies down as soon as a script is posted that reverts changes that cannot be opted out of. I find that I stop really thinking about a change that I personally find needless the moment I disable it in my preferences: if this is true for more people, we may reach a problematic situation when existing power editors are using a significantly different interface from new editors. Double sharp (talk) 02:53, 18 July 2018 (UTC)
Jorm's Minor Adjustment to Watchlist Interface

Here's my thoughts about what should change. Lots of vertical real-estate could be picked up here. Even more buttons could probably be squished into the top row and with decent CSS can overflow to multiple rows if the screen size required it. --Jorm (talk) 22:24, 17 July 2018 (UTC)

Also, add this to your common.css:

.mw-rcfilters-collapsed .mw-rcfilters-ui-filterTagMultiselectWidget.mw-rcfilters-ui-filterTagMultiselectWidget.oo-ui-widget-enabled .oo-ui-tagMultiselectWidget-handle { margin-bottom: 0; } .oo-ui-tagMultiselectWidget.oo-ui-widget-enabled.oo-ui-tagMultiselectWidget-outlined .oo-ui-tagMultiselectWidget-handle { margin-bottom: 0; } --Jorm (talk) 22:31, 17 July 2018 (UTC)

  • If it ain't broke, don't fix it. The Watchlist feature has been around forever and works well. I just want to see the list of changed pages. I will rarely if ever use the jumble of new buttons. A simple fix would be to make the new style a preference in Special:Preferences#mw-prefsection-watchlist. Change
Blancovinkjeemptysmall.png Hide the improved version of the Watchlist (Rolls back the 2017 interface redesign and all tools added then and since)
to
Blancovinkjeemptysmall.png Use a button-based interface to change your options when you view your watchlist
That is, make it opt-in rather than opt-out. Aymatth2 (talk) 00:00, 18 July 2018 (UTC)
  • Same opinion as Aymatth2. The new watchlist is very slow and takes ages to load. I don't think it's ready for full-scale deployment. DaßWölf 00:04, 18 July 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Possible bug: when I right-clicked/'open new tab' on the earliest of my green-dotted unseen changes, and then went back to the 'Watchlist' tab, every other previously green-dotted edit was turned blue, without me clicking on any of those edits. I liked the changes, but have had to revert until this issue has been fixed. Homeostasis07 (talk) 01:27, 18 July 2018 (UTC)

  • I find it fast, but unusuable for me as it breaks not just the script I use that highlights Admins (Admin highlighter) but also the one that highlights possible vandalism in yellow (not sure where I got that one). Doug Weller talk 07:35, 18 July 2018 (UTC)
The new watchlist filters support highlighting edits flagged by ORES, so you can still get the vandal highlighting. — AfroThundr (u · t · c) 12:20, 18 July 2018 (UTC)
  • "the one that highlights possible vandalism in yellow" that is the highlight option under "Revision scoring on Watchlist" in the Watchlist sections of the preferences. The new watchlist ui does listen to this preference. However, if you have played with the new watchlist setttings, before disabling it in your preferences, then reloaded, instead of going freshly to that page, the old UI will apply the settings as you last had them in the new UI (as below with "Watchlist option "Expand watchlist to show all changes, not just the most recent" not working for me").
    Simply select "Watchlist" from your personal tools and it should be fine (unless you actually disabled the option in your preferences of course).
    "breaks .. the script I use that highlights Admins" That is very weird. You have been reporting script problems on this forum for a while though and I've several times added all your scripts to my own script stack and have not been able to reproduce your problems when you were reporting them. I'm sure there potentially is a problem, but I'm just not hitting that exact sweetspot that you seem to hit. Unfortunately I'm not sure where to look for a fix for that right now :( —TheDJ (talkcontribs) 20:29, 18 July 2018 (UTC)
  • @TheDJ: yes, and I still have them but have given up trying to fix them. Oddly though I no longer have the problem. Doug Weller talk 11:07, 20 July 2018 (UTC)

My watchlist stopped loading

I was just using it a moment ago. Now I get a blank page. It's like my watchlist is deleted or something. What's going on?—CYBERPOWER (Chat) 19:33, 16 July 2018 (UTC)

Does it start working again if you disable the new watchlist filters in Special:Preferences#mw-prefsection-watchlist? Whatamidoing (WMF) (talk) 20:06, 16 July 2018 (UTC)
It actually randomly started working again with this new interface.—CYBERPOWER (Chat) 20:07, 16 July 2018 (UTC)
You may have an issue with a broken script. Trizek (WMF) (talk) 12:18, 17 July 2018 (UTC)

New watchlist UI and history page

What I find disconcerting about the new watchlist user interface is that how it highlights unseen changes differs from how it is done on the history pages. Typically I will find an unseen change on my watchlist and select the history link for that page to see all of the unseen changes, so it's helpful to me if the unseen changes are flagged in the same way. Are there any plans to align the highlighting done on the history page with how it appears on the watchlist? isaacl (talk) 02:00, 18 July 2018 (UTC)

Shhh don't give the devs any ideas :D — xaosflux Talk 02:59, 18 July 2018 (UTC)
That's the idea: give them ideas! More ideas: I would like more choices of colour hues, in particular, less saturated ones. I find the background highlighting (and with the colourful diff viewer as well) a bit dark for legibility. isaacl (talk) 03:14, 18 July 2018 (UTC)
I find it disconcerting, too; but I want the watchlist adjusted to be in line with history-page, and previous watchlist, usage. Even if you want to keep the outline bullet points, let them stand for unvisited pages, as un-colored-in circles intuitively, to me, stand for something unaccomplished, as on a machine-readable test answer form or a voter's ballot. It shouldn't be too hard to switch, or have in preferences. Dhtwiki (talk) 00:19, 19 July 2018 (UTC)
Sorry, I should have clarified that I just mean the two should align. I find the current colour scheme for highlighting the background a bit intrusive, and so right now would prefer that the watchlist highlighting match its previous incarnation, which matches the history page appearance. However with the ability to choose a less saturated colour, it's possible I might gain more appreciation for a different highlighting scheme. isaacl (talk) 02:50, 19 July 2018 (UTC)

Watchlist option "Expand watchlist to show all changes, not just the most recent" not working for me

My watchlist is showing me only the most recent change to each page. I have "Expand watchlist to show all changes, not just the most recent" selected, and I have disabled the recent watchlist enhancements. I tried to uncheck and re-check both of the options, and it appears that the "Expand watchlist to show all changes, not just the most recent" option has no effect: with the "improved" watchlist enabled, I see all changes even if the "expand" setting is disabled, and with the improvements disabled, I see only the most recent change, no matter what the "expand" checkbox setting is.

Can anyone else replicate this issue? I use the vector skin. – Jonesey95 (talk) 14:16, 18 July 2018 (UTC)

@Jonesey95: You are probably refreshing the watchlist page instead of navigating to it from your personal tools or Special:Watchlist. In the new setup, the new watchlist will reflect your settings in the url, and while it starts with your defaults, it will not realise automatically that you changed your preferences (this is a bit confusing I agree). Then when you disable the new filters, and refresh your watchlist, those settings as preserved in the URL are STILL being reflected into your watchlist results (aka the old watchlist, will listen to the url parameters of the new watchlist). By navigating to your watchlist from the personal toolbar, it will start fresh and take your new preference defaults into account.
P.S. In the new watchlist, this specific preference corresponds to the filter setting "latest revision" (or the lack thereof). —TheDJ (talkcontribs) 15:32, 18 July 2018 (UTC)
I've filed phab:T199920 about this, especially since I think it is a problem that we will see more often in the future in other areas of the UI. Fixing it might not be simple however especially as I don't think it is really high priority. —TheDJ (talkcontribs) 20:17, 18 July 2018 (UTC)
Thanks for that explanation. You could be right. I have disabled the new watchlist again until the UI display bugs can be worked out, and I will try clicking on the Watchlist link or using my bookmark to refresh it.
While I'm here, does anyone know if there is a phab task to get rid of the (to my mind, arbitrary and unhelpful) calendar day boundaries within the watchlist? It's frustrating and unnecessary when I have "Expand watchlist to show all changes" turned on, and then go away for multiple days, to have to click on three separate links to catch up on a busy page like VPT. (I'm sure someone will suggest that I never go away for multiple days, and I can see where you're coming from, but sometimes it can't be helped.) – Jonesey95 (talk) 04:36, 19 July 2018 (UTC)
Jonesey95, phab:T10681. --Izno (talk) 05:04, 19 July 2018 (UTC)
Thanks Izno. I wasn't sure if this phab task applied only to Special:RecentChanges or to the Watchlist as well. I wonder why it has stagnated so long, when it seems to be not that hard. They sure did a lot of work to "improve" the watchlist for this latest revision. – Jonesey95 (talk) 05:11, 19 July 2018 (UTC)

Watchlist "live update" misleading icon

When it's not active, it displays as a filled right-caret and normal text. When it's active, it becomes a filled box and inverse text. A right-caret is reasonable for something that could be activated I guess, but it's more usually associated with an expandable tree. A solid box is does not have any typical association with "active". In fact, because it's part of the inverse-text field, it appears as a background-colored box with a foreground outline. That means it looks exactly like an unchecked checkbox. Why are we re-inventing the UI wheel for a simple boolean option? DMacks (talk) 15:45, 18 July 2018 (UTC)

The UI of the whole new interface needs a total revision. Clean Copytalk 17:28, 18 July 2018 (UTC)
@DMacks: are you referring to the near universal symbols for play and stop applied here ? —TheDJ (talkcontribs) 20:14, 18 July 2018 (UTC)
It's mixing multiple mode indicators. If you want to use normal/reverse (one of several standard ways of boolean toggle), or change of icons (if we are accepting a new paradigm of watchlists as a data stream), that would make more sense. It's the mixing, and the appearance of a contradictory meaning, that are my concern. Principle of least astonishment and all that. DMacks (talk) 04:31, 19 July 2018 (UTC)

ERIC

Would anyone have any advice on how to add an optional access parameter to {{ERIC}} that would match the doi-access parameter of the CS1 templates by replacing the standard arrow icon used by external links with a green lock (i.e., Freely accessible)? 142.160.89.97 (talk) 20:41, 16 July 2018 (UTC)

@142.160.89.97: Try {{ERIC/sandbox}}, which will display the lock when you set |lock=yes. If that works for you, I will enable it in the main template--Ahecht (TALK
PAGE
) 21:17, 16 July 2018 (UTC)
That's perfect. Thank you very much, Ahecht! 142.160.89.97 (talk) 21:22, 16 July 2018 (UTC)
I would be better to modify {{Catalog lookup link}} template. Ruslik_Zero 21:29, 16 July 2018 (UTC)
I certainly wouldn't object to that, Ruslik0. 142.160.89.97 (talk) 21:36, 16 July 2018 (UTC)
@Ruslik0 and 142.160.89.97: {{Catalog lookup link}} is an incomprehensible mess, with wikitext if statements nested 10 deep. I don't want to even try to attempt to modify it. It would be a perfect candidate for a Lua rewrite, and the lock icon could be incorporated into that, but I don't have time for a rewrite at the moment. --Ahecht (TALK
PAGE
) 22:09, 16 July 2018 (UTC)
As someone who is no template expert and who has no experience with Lua, why is Lua preferable? 142.160.89.97 (talk) 04:56, 17 July 2018 (UTC)
Because Lua is a real language? I agree that {{catalog lookup link}} is an incomprehensible mess. Code that resembles a wall of text is never good. Adding access icon support to that template as it exists now would only make things worse.
The green access icon originated at cs1|2. Most source identifiers supported there link to sources that lie behind a registration-/pay-wall. Some source identifiers occasionally link to free-to-read sources, (doi, jstor, etc), those identifiers may be marked with the green access icon using |<id>-access=free; some identifiers are never free-to-read. At cs1|2, isbn, ismn, issn, oclc, etc do not get the access icon because they do not link to a source but rather, link to information about the source. {{catalog lookup link}} is transcluded by the stand-alone identifier templates {{ISBN}}, {{ISMN}}, {{ISSN}}, {{OCLC}} for which an access icon is not appropriate; some identifiers are never free-to-read so the access icon is not appropriate for them. Further, as currently written, {{catalog lookup link}} can render links to multiple identifiers so the access icon support would require some sort of mechanism to identify which of the links in the list get the lock and which do not. {{ERIC}} uses {{catalog lookup link}}:
{{ERIC|24680|12345|9876|lock=yes}}
ERIC 24680, 12345, 9876 – these numbers are made up, but what if 12345 is not free-to-read? or what if it is the only one that is free-to-read?
—Trappist the monk (talk) 11:47, 17 July 2018 (UTC)
In the case of ERIC, about 25% of the items are free to read. Obviously, the lock icon would not be used if all the items listed aren't free to read. --Ahecht (TALK
PAGE
) 15:00, 17 July 2018 (UTC)
I applaud your optimism, but I think that nothing is obvious. Editors will apply the access icon parameter when only some of the sources are free-to-read.
Because it amused me to do it, I have hacked a first version of Module:Catalog lookup link. Examples at Template talk:Catalog lookup link.
—Trappist the monk (talk) 15:20, 17 July 2018 (UTC)
I've copied the changes over to {{ERIC}}. If there is consensus to add the option to {{Catalog lookup link}}, it can easily be shifted to there. --Ahecht (TALK
PAGE
) 21:35, 16 July 2018 (UTC)
@Ruslik0, 142.160.89.97, and Trappist the monk: I updated the template so that it uses the |url-access= parameter in the same way that the CS1 templates do instead of using |lock=yes. To display the green lock, you now have to use |url-access=free. This provides the ability to use free, registration, limited, or subscription. --Ahecht (TALK
PAGE
) 15:00, 17 July 2018 (UTC)
I was going to suggest that the better parameter name might be |<id>-access=free where <id> is the identifier, so for ERIC, |eric-access=free; alternately, a generic |id-access=free might be better. cs1|2 does not allow |url-access=free because urls that link |title= and/or |chapter-title= are presumed to be free-to-read so a free-to-read icon for those parameters is redundant. Identifiers, on the other hand, are commonly not free-to-read so a free-to-read icon has value. I note this simply for consistency among the various templates.
—Trappist the monk (talk) 15:20, 17 July 2018 (UTC)
Forgot this: I don't think that use of these icons should deviate from the standard set by cs1|2 for the same icons. It should be presumed that identifiers are not free-to-read so the limited and subscription options are redundant to that presumption.
—Trappist the monk (talk) 15:26, 17 July 2018 (UTC)
@Trappist the monk: In CS1/2, it's different depending on the parameter. Links inserted with|url= are expected to be free to read by default, links inserted with other identifiers are either free or not free depending on ths source (so |doi= is presumed non-free, but |arxiv= is presumed free). In any case, this template is set up to default to the standard external link icon. --Ahecht (TALK
PAGE
) 17:05, 17 July 2018 (UTC)
Yes, I know all that. The general rule is: Don't highlight the norm. Links applied to |title= with |url=, are presumed to be free-to-read (the norm) so it is not possible in cs1|2 to highlight those links with a green access icon. In general, identifier links are presumed to be not-free-to-read (the norm) so it is not possible in cs1|2 to apply the subscription/limited/registration icons to identifier links. Some identifiers are always free-to-read (arxiv, biorxiv, citeseerx, pmc, rfc, ssrn) so cs1|2 automatically applies the green icon to these links. Your edit to {{ERIC}}, inappropriately I think, allows any of the lock icons to be applied to ERIC identifiers.
—Trappist the monk (talk) 09:44, 18 July 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── (edit conflict) Template:Catalog lookup link does not need to be implemented in lua -- it merely needs to use one of the deduplication templates like Template:For nowiki. {{3x|p}}ery (talk) 15:27, 17 July 2018 (UTC)

@Ahecht and Trappist the monk: I've written something in Template:Catalog lookup link/sandbox1 that uses a constant level of nesting via {{separated entries}}, as a less insane pure-wikitext version. The testcasea are yellow, but everything looks visually the same. {{3x|p}}ery (talk) 16:03, 17 July 2018 (UTC){{3x|p}}ery (talk) 15:50, 17 July 2018 (UTC)
@Pppery: I know you are on a crusade against Lua, but this is precisely the sort of template that should be written in Lua. Not only does your version still spin up a Lua module (meaning there's no performance advantage), but it artificially limits the number of inputs to 9. Templates with arbitrary numbers of parameters should not be forced into wikitext for no reason. I tweaked Trappist the monk's module to get the output to match the existing template and implemented it at Template:Catalog_lookup_link/sandbox. I had been working on a shorter module at Module:Sandbox/Ahecht/Catalog_lookup_link, but Trappist's, although longer, is a bit cleaner. --Ahecht (TALK
PAGE
) 16:17, 17 July 2018 (UTC)

Why are some language userboxes italicized and others not?

I just noticed an inconsistency on my user page, where Template:User en and Template:User ga-1 are not in italics but Template:User fr-2 is. I don't speak German but I checked Template:User de-2 anyway, and that's italicized like French.

I can understand not wanting to italicize Chinese, Japanese, etc., but is this just because the foreign-language text from en.wiki's perspective is always meant to be italicized and the Irish one is just obscure enough that no one noticed that it is in error, or what?

Hijiri 88 (やや) 06:31, 17 July 2018 (UTC)

@Hijiri88: Some of them use {{Lang}}, which always italicizes Latn-script text, and the Irish one doesn't. All the templates were created manually by different people. Jc86035 (talk) 07:10, 17 July 2018 (UTC)
@Hijiri88: I answered a pretty similar question at Template talk:Babel#Italicization. Instead of using the userboxes directly, use {{#babel:en|ja-4|fr-2|zh-1|ga-1}}. --Redrose64 🌹 (talk) 07:36, 17 July 2018 (UTC)
@Jc86035 and Redrose64: Cool. Thanks!
... umm ... is one or the other userbox style (not using the userboxes directly vs. using babel, but using Lang so it italicizes vs. not) "wrong" and needing to be updated/fixed?
Hijiri 88 (やや) 07:58, 17 July 2018 (UTC)
@Hijiri88: It is correct to use {{Lang}}, but there is a parameter to turn the italicization off. I think the templates should match the Babel userboxes' styling (i.e. language formatting but no italics). Jc86035 (talk) 08:02, 17 July 2018 (UTC)

Module:Template parameter value

Some weeks back, I made {{Template parameter value}}, which uses Module:Template parameter value. It extracts the value of a specific parameter from a specific template from a specific page. However, when the template is used on the same page that its pulling the value from, it doesn't seem to work, and I can't figure out why. For example, if I use {{tmpv|List of The 100 episodes|Series overview||start1}} on List of The 100 episodes (i.e. pulling the value of the |start1= parameter from the series overview template) (and only in edit preview), I get a blank result; use it on any other page or sandbox, I get March 19, 2014 (2014-03-19). Thoughts? -- AlexTW 14:38, 17 July 2018 (UTC)

It's a bad idea for templates to have this kind of subtle dependency on other templates. {{3x|p}}ery (talk) 15:23, 17 July 2018 (UTC)
Same opinion here. This is not what templates and even modules are designed for. You shouldnt rely on it and you should expect it to break in various ways, now and even more so in the future. We have wikidata and Lua data modules, you should make due with those. When you built houses with match sticks, a collapse is inevitable. —TheDJ (talkcontribs) 18:28, 17 July 2018 (UTC)
Thank you for your opinions, but I was more looking for a fix for the template. Turns out, there is no issue with it, so no match sticks. -- AlexTW 00:31, 18 July 2018 (UTC)
A collapse is in fact inevitable, not because the matchsticks catch fire, but because you've been noticed by the fire inspectors -- I've nominated Template:Template parameter value for deletion. {{3x|p}}ery (talk) 03:06, 18 July 2018 (UTC)
It works for me on List of The 100 episodes and produces "March 19, 2014". Are you previewing a text which actually has the template you search for? It searches the previewed version of the page and not the saved version. But I share the concern of the others. Help:Labeled section transclusion seems a better way but it requires the page to be prepared for the purpose. PrimeHunter (talk) 19:49, 17 July 2018 (UTC)
It seems I was previewing it when editing only the header, but your explanation (It searches the previewed version of the page and not the saved version.) makes sense, and I understand why now. Thank you! (As a side note, the template was created so that pages didn't need to be "prepared".) -- AlexTW 00:31, 18 July 2018 (UTC)

Template coding

An issue has been raised at WP:CANTALK which I need to ask for a template coding expert to assist with. {{Infobox Canada electoral district}} is supposed to include a box which clarifies whether the electoral district in question is a federal one represented in the Canadian House of Commons or a provincial one represented in a provincial or territorial legislative assembly — however, while this box appears to display correctly on active electoral districts such as Argenteuil (note where the infobox says "provincial electoral district") or Nickel Belt (note that this one says "federal electoral district" in the same spot), on defunct districts like Argenteuil—Papineau—Mirabel it seems to disappear, leaving the reader to guess at which level of government the electoral district pertained to.

At the same time, the defunct districts also seem to disappear the "legislature" field which links to what legislative body the representative sat in, which they also shouldn't be doing.

Both of these fields should still be displaying in an electoral district's infobox regardless of whether it's active or defunct, because they're both important pieces of information whose contextual relevance is not dependent on whether the district is currently active or not. So can somebody who knows template coding look into this, and recode the template so that the "federal vs. provincial clarifier" and "legislature" boxes don't disappear on defunct districts? Thanks. Bearcat (talk) 18:05, 17 July 2018 (UTC)

Hi Bearcat. In order for it to display the status has to be set to something. The parameter "fed-status" was empty; I set it to "fed-status=defunct" to fix the problem in Argenteuil—Papineau—Mirabel. For active districts it has to be set to active. See Template:Infobox Canada electoral district#Mandatory parameters These complex infoboxes are very tricky. This one at least is documented; many aren't. StarryGrandma (talk) 20:05, 17 July 2018 (UTC)
Ah, okay, thanks. Bearcat (talk) 20:09, 17 July 2018 (UTC)
Actually someone else added it first. StarryGrandma (talk) 20:11, 17 July 2018 (UTC)

How to find articles that lack citations but have no tag placed on them?

Heading basically says it all, I have come across (by chance) articles that have been unreferenced for years but do not have any citation-related tag on the page, (for example this one) is there a way to automatically generate a list of such articles? - CHAMPION (talk) (contributions) (logs) 05:56, 18 July 2018 (UTC)

Snarky answer: That article had a citation-related tag on it. There are almost 200,000 articles in Category:Articles lacking sources from December 2014 and its companion categories.
Helpful answer: look through any year in songs to get started, like Category:1990 songs. There are thousands of unreferenced song articles. Good look getting them deleted however; I poked the Wikipedia talk:Notability (music) bear a year or two ago and got tons of pushback.
Before you tag a bunch of articles for deletion, please read WP:BEFORE. – Jonesey95 (talk) 06:44, 18 July 2018 (UTC)
@Jonesey95: Haha, missed that, but I'm sure I've seen such articles before (unsourced but no tag) and I added the tag to them (see for example this one, and yes, I am aware of WP:BEFORE and have had a success rate in nominating music articles for deletion. (check my AfD stats) However, I still want my original question answered, which is finding articles that lack citations but have no tag placed on them, like the diff that i just linked. Regards. - CHAMPION (talk) (contributions) (logs) 07:04, 18 July 2018 (UTC)
It depends how perfect a list you want; there are many edge cases. For example, the {{unreferenced}} tag should not have been applied to the example you gave, Hey, Do You Know Me, because that article has an external link that, according to the template documentation, serves as a reference. A better example of an unreferenced article would be Tuzapán. --Worldbruce (talk) 02:15, 19 July 2018 (UTC)
Perhaps a more technical way to find likely candidates for this description would be for someone with the appropriate Wiki-fu to generate a list of articles that contain 1) no citation-related tags, 2) no <ref></ref> tags, 3) no external links, and 4) no "References" header. bd2412 T 02:46, 19 July 2018 (UTC)
I think that the ArticleWizard auto-inserts a ==References== heading. For item 3), you want "no URLs", not just no ==External links==. WhatamIdoing (talk) 19:21, 19 July 2018 (UTC)

Commonscat template + alternatives

Hello, Pywikibot team needs help! There is quite old Commonscat template list in the framework and there is 5 years old request to update it. But none of us is enwiki user. Could anyone please update the task with current Commonscat templates, redirects and alternatives? We can then update the framework, but now we are just stuck waiting for response from any enwiki tech savvy. --Dvorapa (talk) 09:53, 18 July 2018 (UTC)

@Dvorapa: Are you looking for Category:Wikimedia Commons templates, or do you want all the redirects as well? (Shouldn't most categories be linked through Wikidata now?) Jc86035 (talk) 14:02, 18 July 2018 (UTC)
I don't know. On cswiki we have got one Commonscat template, no redirects, so I'm pretty confused by enwiki. The Pywikibot script adds main Commonscat template to the articles and skips articles already containing the template, any of the alternatives, or any of the redirects. So I would like to know, what is the main Commonscat template and what are the alternatives and redirects currently. --Dvorapa (talk) 20:54, 18 July 2018 (UTC)
@Dvorapa: I think it's most of the templates listed under "C" in the category excluding sandboxes (I'm not sure whether you want the ones which only link to galleries). I have no idea why there are so many, but it's probably because of a combination of pre-Lua template inflexibility and individual preference (I have no evidence for this). Jc86035 (talk) 05:36, 19 July 2018 (UTC)
In the Phabricator task there are also some others mentioned:
\* Commonscatmore
\* Airports by country category description
\* BC year in topic ‎
\* C11 year in topic ‎
\* C12 year in topic ‎
\* C13 year in topic ‎
\* C14 year in topic ‎
\* C15 year in topic ‎
\* C16 year in topic ‎
\* C17 year in topic ‎
\* C18 year in topic ‎
\* C19 year in topic ‎
\* C20 year in topic ‎
\* C21 year in topic ‎
\* Cathead Conservatism in
\* Cathead passenger ships of the
\* Howtoreqphoto
\* M1 year in topic
\* Motorsport decade category
...
They probably also do have some form of Commonscat link inside. Can some current list be found somewhere? --Dvorapa (talk) 06:26, 19 July 2018 (UTC)

What's going on?

Page loads, and all seems well. But the page often never actually finishes loading, and Firefox says it's waiting for tools.wmflabs.org. It's not my connexion, as it doesn't happen on other sites. Anyone else having this issue? Adam9007 (talk) 00:28, 19 July 2018 (UTC)

xtools is gathering edit history on the newer pages. If a history exists, the load of the data for xtools is much faster. --Ancheta Wis   (talk | contribs) 00:59, 19 July 2018 (UTC)
Not just you. I seriously thought I was being hacked. It was on Firefox and Chrome, any page on English Wikipedia. Not on Wikisource, didn't happen on Commons. Then I had the idea to remove the last script I had added to my common.js, which was the Zhaofeng_Li/Reflinks.js. Removal of that script cleared everything for me. — Maile (talk) 01:10, 19 July 2018 (UTC)
I don't know why but running Zhaofeng_Li/Reflinks eventually brings a "502 Bad Gateway" message. This started happening a few hours ago. Probably due to maintenance and hopefully it will clear up soon. MarnetteD|Talk 01:21, 19 July 2018 (UTC)
Thanks. I've just commented out Reflinks in my common.js and everything seems to be fine again. Hopefully, I can uncomment it soon. Adam9007 (talk) 01:37, 19 July 2018 (UTC)
No issues here. Amaury (talk | contribs) 01:45, 19 July 2018 (UTC)

Template:Disambiguation needed display error?

Is it just me or is the {{dn|date=March 2018}} at Public interest § Government (permanent link) linking to here and superscripting into the text above? —Nøkkenbuer (talkcontribs) 08:46, 19 July 2018 (UTC)

Yes, but what is the problem? Ruslik_Zero 09:15, 19 July 2018 (UTC)

TemplateStyles enabled on English Wikipedia

Hello, TemplateStyles have been enabled on this wiki. This follows an RfC on the feature from last month.

TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.

TemplateStyles is useful for a few reasons.

  • It makes it possible for templates to work better on mobile.
  • It cuts out confusion on where to apply CSS rules.
  • Editing CSS is currently limited to administrators, which is a major barrier to participation.
  • All stylesheets must be loaded on all pages (whether they actually are used the page or not), which wastes bandwidth and makes debugging style rules more difficult.

You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.

Thank you. CKoerner (WMF) (talk) 11:33, 19 July 2018 (UTC)

There are also basic guidelines for TemplateStyles available. See: WP:TSTYLE. — AfroThundr (u · t · c) 12:09, 19 July 2018 (UTC)

W00t !!!!!! Please rewrite templates to make use of this great new feature, allowing you to write cleaner templates, without inline style statements and with mobile responsiveness etc. At the same time (as always) be careful to not needlessly disrupt the wiki. (For instance, don't move the infobox styling into Module:infobox and accidently break the hundreds of templates that use infobox styling without making use of that Lua module). —TheDJ (talkcontribs) 12:18, 19 July 2018 (UTC)

Yep, WikiProject Portals was mainly waiting on this so we could overhaul how portals look in mobile (among other things). We'll see how far we can take things now that we have stylesheets in our toolbox. — AfroThundr (u · t · c) 22:28, 19 July 2018 (UTC)

Los Angeles area task force

I need some help in cleaning up a move to Wikipedia:WikiProject California/Los Angeles area task force. Thanks. BeenAroundAWhile (talk) 15:06, 19 July 2018 (UTC)

@BeenAroundAWhile: What is the problem here? --Redrose64 🌹 (talk) 16:23, 19 July 2018 (UTC)

Template expanding a range

Can someone please suggest a way to expand a template to cover a range? It would be a template that would have two parameters, {{{1}}} and {{{2}}}, both of which are whole numbers with {{{2}}} greater than {{{1}}}. The template would then return a list with {{{1}}} and {{{2}}} and all the numbers in between.

For example, I'm considering creating a template, {{USCongressOrdinalRange}},

that would be run like: {{USCongressOrdinalRange | 109 | 112 }},
and would return: 109th, 110th, 111th, 112th.
It would effectively expand out to:
{{USCongressOrdinal|109}}, {{USCongressOrdinal|110}}, {{USCongressOrdinal|111}}, {{USCongressOrdinal|112}}.

I would appreciate any suggestions from template experts. Thanks.—GoldRingChip 16:38, 19 July 2018 (UTC)

Implemented at {{x1}}. {{3x|p}}ery (talk) 16:50, 19 July 2018 (UTC)
Thank you, I'll have a look! —GoldRingChip 17:05, 19 July 2018 (UTC)
Update: That worked great. Thanks. —GoldRingChip 17:15, 19 July 2018 (UTC)

Template:Infobox road

Can someone help to get the previous_dab and next_dab parameters to work for UK roads in Template:Infobox road, please? The article I've been looking at is M53 motorway. The syntax in the previous_route and previous_dab parameters was broken but fixing it results in the previous route link at the bottom of the infobox always pointing to a dab page, M50 motorway. This happens whatever is in the previous_dab parameter. That parameter works for other countries. For example, the previous route link in Alabama State Route 46 points to Alabama State Route 45 (pre-1957) when previous_dab is =pre-1957 and changing that to =xyz changes the link to Alabama State Route 45 (xyz). I'm guessing there is some code associated with country=GBR that disables the previous_dab parameter.--Cavrdg (talk) 12:19, 20 July 2018 (UTC)

It looks like |previous_dab= is passed to Module:Infobox road's "browse" function, which then calls Module:Road_data/browse. It looks like the link is eventually produced by Module:Road data/strings/GBR, to which I have attempted to add a dab variable (copying from Module:Road data/strings/USA/AL). It didn't work, unless there is some purging or null-editing required to cause the modules to be re-parsed. That's as far as I got. – Jonesey95 (talk) 14:47, 20 July 2018 (UTC)
I have fixed the issue. I believe the problem was related to Lua's greedy regex rules, which were trying to treat all three of the conditionals (bracketed parts) as one. I split up the format string into a switch table on the state, which seems to work.
For future reference, posting directly to Template talk:Infobox road will generally get a faster response. As the template/module maintainer, I have that page on my watchlist. -happy5214 20:33, 20 July 2018 (UTC)

Timeless Newsletter • Issue 1

Wikimedia beetle.svg
Newsletter • July 2018

Welcome to the first issue of the Timeless newsletter! This issue is being sent or forwarded to everyone who has at some point expressed an interest in the project, give or take, as well as a couple of other potentially relevant pages, so if you would like to continue (or start) receiving this newsletter directly, please sign up for further updates on the meta page.


The news:

The Timeless grant has been selected for funding, and the project is now underway!

While I've had a somewhat slow start working on the project for health reasons, I'm pleased to announce that everything described in the proposal is now either happening, or on its way to happening.

Current progress:

  • The project now has a hub on Meta to serve as a directory for the various related pages, workboards, and local discussions and help pages. It's probably incomplete, especially with regards to specific language projects that might have local pages for Timeless, so if you know of others, please add them!
  • Outreach: I've been talking to various people and groups directly about skinning, desktop/mobile interfaces, project management, specific component support, and other things, and have begun to compile a very shoddy list of skinning problems and random issues on mw.org based on this. Some of this may inform the direction of this project, or possibly this project will result in building a more proper list that can then be used for other things. We shall see.
  • Some development - task triage, code review, bug fixing, and various rabbit holes involving ...overflows.

General plan for the future:

  • Triage the rest of the workboard.
  • Catch up with all the talkpages and other bug reports that have been left various other places that are not the project workboard
  • Do all the bug fixes/features/other things!
  • Some proposals aimed at Commons and Wikisource in particular (maybe, we'll see)

Essentially, the grant as written shall be carried out. This was the plan, and remains the plan. Timelines remain fuzzy, but while there have been some initial delays, I don't particularly expect the timeline for project as a whole to change a whole lot.

Also, for anyone at Wikimania right now: I am also at Wikimania. Come talk to me in person!

Thank you all for your interest and support thus far!

-— Isarra 12:23, 20 July 2018 (UTC)

This issue has been sent regardless of signup status. To receive future issues please add yourself on the massmessage list.

Web form for automating tasks

So the idea lab submission button opens a modal dialog with a form ... I'm assuming it'll eventually generate some MW content. Is that fully rolled out? Things as mundane an AFD and ITN require a lot of copy/paste of complicated templates in different places, it's screaming for a modal dialog and a wizard. --LaserLegs (talk) 15:56, 20 July 2018 (UTC)

@LaserLegs: Twinkle can handle AfD nominations, though I don't know if it handles ITN. Jc86035 (talk) 16:05, 20 July 2018 (UTC)
Yep, Afds are easy with Twinkle, though I've never heard of ITN built into it. Home Lander (talk) 23:37, 20 July 2018 (UTC)

Undo function no longer working in edit mode

Seems a change went into effect within the last few days where now text in the edit window is color-coded to show wikilinks and markup. Unfortunately the undo function (via ctrl+Z or right clicking) no longer seems to be working. I'm using Google Chrome. Is this a known issue? Jweiss11 (talk) 01:51, 21 July 2018 (UTC)

@Jweiss11: I'm assuming you are referring to your browsers "undo" feature not the Wikipedia Undo command correct? — xaosflux Talk 01:56, 21 July 2018 (UTC)
Yes, I'm referring to the brower's "undo" feature. Jweiss11 (talk) 01:57, 21 July 2018 (UTC)
@Jweiss11: Check your gadgets and see if you have Syntax highlighter enabled, if so try disabling and let me know if it fixes your issue. — xaosflux Talk 01:59, 21 July 2018 (UTC)
Also are you using the visual editor? If so, do you have the issue when using the text editor? — xaosflux Talk 02:01, 21 July 2018 (UTC)
I'm not using visual editor and I do not have syntax highlighter checked off in my gadgets, yet it appears to be enabled anyway. Jweiss11 (talk) 02:03, 21 July 2018 (UTC)
@Jweiss11: does your problem present in safemode? — xaosflux Talk 02:06, 21 July 2018 (UTC)
Also, do you have any beta features enabled? — xaosflux Talk 02:07, 21 July 2018 (UTC)
I don't have any beta features enabled. The problem does indeed present in safemode. Jweiss11 (talk) 02:10, 21 July 2018 (UTC)
@Jweiss11: I can't make it fail, try to open an incognito browsing window and don't even log on, just try to edit and see it clears up? — xaosflux Talk 02:41, 21 July 2018 (UTC)
Logging out and using the incognito browsing window both disabled the highlighted syntax and restored the undo function.  But when I log back in, the problem is back. Jweiss11 (talk) 02:50, 21 July 2018 (UTC)
@Jweiss11: try this: go to Special:Preferences#mw-prefsection-betafeatures, ensure you do not have Automatically enable all new beta features enabled. Then enable the New wikitext mode feature, save, turn it back off, save and try again. — xaosflux Talk 03:01, 21 July 2018 (UTC)
Just did all of that. Didn't work. :( Jweiss11 (talk) 03:04, 21 July 2018 (UTC)
You can try Special:Preferences/reset - but it will put you in all defaults, so you may want to take note of what you have first. — xaosflux Talk 03:12, 21 July 2018 (UTC)
Are we sure this is problem local to me? Are you able to undo text edits with syntax highlighter turn on? Jweiss11 (talk) 05:31, 21 July 2018 (UTC)

Proposals

Bot archive all article talk page sections unchanged for five years

(non-admin closure) There is consensus against doing this automatically on all pages. Individual editors can use User:MiszaBot/config to configure automatic archiving on a per-page basis. power~enwiki (π, ν) 19:50, 17 July 2018 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Several years ago I proposed something like this here, and was told by one of the regulars (in a frankly patronising manner) that there was no need to worry about this, as in a matter of months if not weeks the old talkpages would be swept away by the new social media-style set-up, Wikipedia:Flow. Well, here we all are, and the average less-frequented talk page still goes back to say 2006. So once again I propose we set up a bot that auto-archives all article talk page sections that have not changed for 5 years (or 7, or 3, whatever). Few of the ancient points are still at all relevant, and the pages give a very bad impression - often referring to a totally different text. I'd imagine this is fairly easy to get set up, if the support is there. Johnbod (talk) 23:40, 25 June 2018 (UTC)

Thumbs up social media didn't replace talk pages. Pros and cons with proposal. Archiving makes information discovery harder, finding unknown unknowns. Posts are dated so no chance of old threads being mistaken for new and they can contain FAQs and other still-relevant material. They can also contain outdated information and embarrassing comments from early career days. In balance I would weigh on keeping data as open and accessible as is practical ie. not archiving except for constraints of size or frequency. -- GreenC 00:24, 26 June 2018 (UTC)
On highly-viewed or well run talk pages old threads are archived long before this, but on neglected ones they just sit there forever. There is every chance of "old threads being mistaken for new" - I not infrequently see people "replying" to random comments over 10 years old, clearly without realizing this. Many inexperienced users assume the newest posts are at the top. Actual FAQ sections should of course not be affected. Johnbod (talk) 01:56, 26 June 2018 (UTC)
  • I don't see how this would help anything. Edits rearranging talk pages, however minor, makes tracing history harder. Johnuniq (talk) 07:17, 26 June 2018 (UTC)
Doesn't seem to be a problem on articles where the talk page is actually active. Johnbod (talk) 14:45, 26 June 2018 (UTC)
Rather, it's that on those talk pages, the benefits of archiving are considered to weigh up against the downsides; on inactive talk pages, the benefits of archiving are significantly lesser and do imho not weigh up. While yes, inexperienced users (as well as folks just not paying attention) may occasionally mistakenly respond to a really old comment, they likely were already looking to post something on the talk page. People, especially new editors, generally only visit the talkpage to either use it or see if something's been said about a particular subject. In effect, it doesn't matter particularly much whether their response is to a decade-old comment or on a freshly archived talk page: when a talk page hasn't received edits in five years, it's close to a given that unless attention is attracted to said talkpage comment by other means (e.g. helpdesk or teahouse, or by means of the editor committing problematic edits resulting in heightened scrutiny on all their edits) no one is going to respond either way. If the talk page has received more recent edits, it's just particular sections that haven't, it's likely to be on people's watchlists and much like folks are perfectly capable of handling new editors who respond on the wrong part of a user talk page, they're perfectly capable of handling new editors responding in the wrong section of an article talk page. (And if it isn't on people's watchlists, much the same goes as for the fully-dead talkpages: it wouldn't matter whether they respond in the right or wrong section when no one's around to reply anyway) AddWittyNameHere (talk) 20:34, 26 June 2018 (UTC)
  • I really don't see the problem with talk pages containing old posts. Ideally, we would want to have all the past discussions clearly visible on one page, and noramlly archiving enters the picture only when that page starts getting too long. I don't think we should be fragmenting the history and making it more difficult to access past discussions unless there are clear benefits and they outweigh the risks. I don't know how common it is for new users to reply to old posts mistakenly taking them to be still relevant, I can't recall seeing that happen. I do recall seeing new users make proposals that have been rejected before simply because they haven't learned about the archives, and I've seen editors mess up the templates so the link to the archives disappears witout anyone noticing for years. – Uanfala (talk) 11:54, 26 June 2018 (UTC)
Really, do any of you ever look at unarchived talk pages? They are very very rarely worth reading at all beyond 3 years back, and give a pretty bad impression to the uninitiated. Typically there are complaints from c. 2006 about basic failings that were no doubt justified at the time, but are now completely irrelevant. If any good point is raised and a discussion started, that is liable to get archived anyway. A properly-written bot would get the edits right. Johnbod (talk) 14:45, 26 June 2018 (UTC)
Almost all of the article talk pages I look at are unarchived. If there are old posts on a talk page that an editor deems distracting, they can always set up the archive themselves. – Uanfala (talk) 20:41, 26 June 2018 (UTC)
  • On less active topics, old posts are often very relevant. See Talk:Tirana for example, which has never been archived, and is currently at 32,160 bytes (not too large). See Talk:Tirana#About the name! which still ought to be of interest to current editors. Someone started that thread in 2005, and there is a new (apt) contribution from 2008. Also Talk:Tirana#Tirana or Tiranë. It's a perennial proposal to change Albanian cities to the indefinite form (ë instead of a) and that talk thread is quite germane. It was started in 2007 and there is a later contribution from 2009. Under the above mass-archiving proposal, both of these useful threads would be sent away into Archive 1. EdJohnston (talk) 15:32, 26 June 2018 (UTC)
Yes, unless saved, before or after archiving, by someone adding some comment now (like "Best not archived"). Or by making/adding to an FAQ header. Incidentally the top section here illustrates one of my points: a post from 2003 is replied to in 2005 and then in 2012, probably without the last poster realizing he is talking to departed users. Johnbod (talk) 16:59, 26 June 2018 (UTC)
Actually I only meant article talk pages, & have amended at top to clarify. The talk pages of the types you mention normally so rarely have anything at all I agree it's not worth it. And when they do it is more likely to have lasting relevance. Johnbod (talk) 21:09, 26 June 2018 (UTC)
Thanks for the note, weaker oppose - but would still want to see some numbers (and we would never approve a BRFA that can't estimate the load - and if it would be 100,000+ pages it will need a LOT of consensus). — xaosflux Talk 02:21, 27 June 2018 (UTC)
I'd see this as something that only needs to run say annually or bi-annually, and is obviously not urgent, so could be broken down into manageable chunks. I'd like to see some figures too, but I'm afraid I've no idea where/how to get them. Anyone? Johnbod (talk) 13:57, 27 June 2018 (UTC)
  • Support Makes sense to me. Old talk page messages could be confusing (though I'm wondering if this would be restricted to a specific namespace or not), so this sounds like a good idea. SemiHypercube (talk) 20:16, 26 June 2018 (UTC)
  • Oppose - Solutions looking for a problem - If you see an unarchived talkpage → Add this to it = Problem solved. –Davey2010Talk 21:54, 26 June 2018 (UTC)
Actually, no it doesn't; at all. In fact the default 90-day archiving is part of a rather different problem, giving us a bunch of talk pages with 60 or 70 archives that contain almost nothing. Of course the page you link to is entirely incomprehensible to those not professional or keen amateur IT people, and I suspect to quite a few who are. You don't "just add" that at all - it seems you have to go off to a choice of other incomprehensible pages (selected how?) and do something or other there. Then it will archive far more frequently than is usually desirable, annoying User:GreenC, Johnuniq, and others above, as well as me - I don't usually like to see anything more recent than about 9 months archived. These are the reasons such auto-archiving is rarely found, and sometimes removed when it has been added. If there was a simple template for a one-off archive of sections unaltered for over x years then yes, that would go about 10% of the way to solving the problem. But apparently there isn't. Johnbod (talk) 00:05, 27 June 2018 (UTC)
So then people can change the day can't they?..... it's not rocket science and we shouldn't be treating people like they're thick nor should we be spoon feeding them, "You don't "just add" that at all" - Well .... you do .... you copy and paste it = problem solved, Well if you dislike seeing anything over 9 months you're more than welcome to use WP:1CA, Again I feel this is a solution looking for a problem. –Davey2010Talk 01:53, 27 June 2018 (UTC)
That only does a section at a time, and "due to Technical 13's indefinite ban, it is currently unmaintained". Not the same at all. Johnbod (talk) 02:00, 27 June 2018 (UTC)
Try the similar tool by Sigma: User:Σ/Testing facility/Archiver. --Izno (talk) 02:36, 27 June 2018 (UTC)
Ok, thanks - that looks like about 15% of what I'd like. Johnbod (talk) 13:54, 27 June 2018 (UTC)
Well doing a section at a time hardly takes up a lot of time does it ? .... But now that issue's been resolved I'm still seeing no reason for this.... –Davey2010Talk
  • Oppose per Ed. If there's barely anything happening on a page, it's nice to have context. Do people sometimes ignore or miss the dates, and necropost? Sure. Does it really matter at all? No. Not sure what the harm is in having someone try to comment on an old post; if folks are watching, it'll get replies, and if people aren't watching, then no harm done! Don't see any gain or benefit. ~ Amory (utc) 01:08, 27 June 2018 (UTC)
  • Based on my experience – which I readily grant is not everyone else's experience, but which is also sufficient to not be dismissed with a "Really, do any of you ever look at unarchived talk pages?", eh? – I would have qualms about an automated implementation of across-the-board archiving.
    Yes, I do see very infrequent instances of less-experienced editors posting replies to talk pages without realizing that they are adding to threads which have been quiet for years. More frequently, however, I see less-experienced editors creating redundant new threads on talk pages, dealing with issues that were talked to death in threads already archived. Out of sight is out of mind. If we are attempting to protect newbies (and not-so-newbies) from confusion and wasted effort caused by old talk pages remaining visible, we cannot discount the confusion and wasted effort suffered by newbies (and not-so-newbies) who don't know there's another layer of extra-buried talk pages behind the regular talk page.
    Speaking anecdotally, I know that less than 24 hours ago I made improvements to an article driven by fresh comments in a talk page thread last edited in 2013. Infrequently-edited talk pages are often associated with infrequently-edited articles; issues that existed five years ago can and do linger unresolved.
    Consequently, a blanket imposition of automated archiving is problematic. If a talk page isn't desperately cumbersome, 'cosmetic' archiving provides little benefit. Manual or semi-automated archiving (where the talk page's and article's editors determine acceptable thread counts, talk page sizes, and so forth, within reason) is much less likely to throw the baby out with the bathwater, and helps to retain a talk page's focus. TenOfAllTrades(talk) 01:37, 27 June 2018 (UTC)
  • Talk page threads, if closed/handled, give users a glimpse in how the article reached its current status: reading a discussion on why a certain section is written in a certain way is much easier than digging the history. If not handled, discussions may be relevant for many years to come: there is no deadline and I often find useful suggestions which are 5 or even 10 years old. Age is not a predictor of usefulness. --Nemo 14:27, 27 June 2018 (UTC)
  • oppose The only reason, ever, to archive talk pages is because they have become unmanageably long. Simply archiving them because they are old hides useful information. Mangoe (talk) 15:24, 27 June 2018 (UTC)
Yes User:Mangoe agree that is the main problem. Maybe just auto archive the ones that are too long. Doc James (talk · contribs · email) 19:49, 27 June 2018 (UTC)
  • Support There's a lot of lesser-watched pages on my watchlist that get comments on threads that are several years old. Timestamps do not fix basic stupidity or ignorance of WP:NOTFORUM. Ian.thomson (talk) 19:54, 27 June 2018 (UTC)
  • Oppose There's no problem to be solved here; none was even expressed. And in certain articles it would do harm. North8000 (talk) 20:38, 27 June 2018 (UTC)
Oh, you misssed "Few of the ancient points are still at all relevant, and the pages give a very bad impression - often referring to a totally different text", expanded on by various people above. Our talk pages are so full of crap it discourages people from looking at them or using them; we can at least get rid of the really old crap, which is either the usual nonsense, or if there is a valid point, it will almost always have been fixed many years ago. Johnbod (talk) 02:20, 29 June 2018 (UTC)
  • Oppose archiving talk pages for any reason other than the one expressed in the lead sentence of Help:Archiving a talk page: "It is customary to periodically archive old discussions on a talk page when that page becomes too large." Lightly used talk pages should never be archived, especially if such pages contain discussions crucial to the substance of the article's content or if there are past exchanges regarding WP:Requested moves.    Roman Spinner (talkcontribs) 03:25, 29 June 2018 (UTC)
  • Oppose: I cannot see the use of this, quite frankly. I follow several articles and talk pages that are long enough, chronologically, to be archived should this proposal pass, but they're simply not long enough in terms of length; archiving for archiving's sake is rather unnecessary, I believe. And there's really no issue here that requires a resolution; moreover, I believe this idea, if implemented, might substantially degrade the rate of usage of talk pages. I mean, to drop the high-falutin' talk for a second, let's be real: if Alex Q. Public saw an empty talk page (with archives and whatever) for article Orange, do you think they would add to it? No: it's hard being the person who speaks up, more so when an empty page exists. I rest my case. —Javert2113 (Siarad.|¤) 04:12, 29 June 2018 (UTC)
  • Oppose: I don't think there's a pressing need to archive *every* talk page on Wikipedia. Generally, if I come across an old Talk page with lots of old comments, I'll manually archive it or set up an archive bot. It's a bit of a hobby of mine. I think that is sufficient for dealing with the rare page that has gone too large without archiving. — The Hand That Feeds You:Bite 18:51, 29 June 2018 (UTC)
  • Oppose. Odds are that a talk page that hasn't been archived in five years is talking about issues that nobody has settled in five years. It seems excessively optimistic to imagine that there are gnomes running around fixing problems on a mainspace page without dumping some manner of poo on the talk page in sufficient quantity to have forced an archive. Wnt (talk) 21:12, 1 July 2018 (UTC)
  • Oppose - Most of the time it's going to be appropriate, but it's not worth those few times that a thread does pick back up after several years, or those times when an older thread provides important context on little-watched pages. — Rhododendrites talk \\ 16:49, 2 July 2018 (UTC)
  • Not a good idea. See the first section of Talk:Edward Smith-Stanley, 12th Earl of Derby, which began in 2012 and has just been resumed. Yes, this is an unusual situation, but "do X in all situations" is appropriate only if X will never be problematic, or if doing X is a significant improvement and it's worth a few problems. This isn't a significant benefit: if you ignore talk pages with banners only, most of our article talk pages have had only a tiny number of comments, and archiving would be confusing. One week ago, this is what Smith-Stanley's talk page looked like. Even if the issue had gotten resolved in 2012, why archive? It's just one discussion, and you'd be creating a separate archive page for it. I just now hit "Random article" until I found one with a talk page comment, Talk:Quantum mirage. Is it a good idea to have a bot create an archive for pages with this history? This one's exceptional, with no datestamp, but if that post had been properly signed, it wouldn't affect my argument. Nyttend (talk) 11:39, 3 July 2018 (UTC)
  • Oppose I don’t really agree that the reasons suggested for auto archiving are pressing enough for it to be done. Aiken D 18:26, 4 July 2018 (UTC)
  • Support: Stuff that old is rarely relevant, and more often than not already resolved, weird old rants by anons, or weird old rants by editor A against editor B for some alleged slight and either of them active editors any longer. WP's talk pages are for working on content not memorializing people's ability to ignore WP:NOT#FORUM.  — SMcCandlish ¢ 😼  01:56, 5 July 2018 (UTC)
  • Oppose I frequently come across stubs that were tagged for notability 10 years ago and haven't had any major edits since. Often a quick peek at the talk page will reveal concerns that have not been addressed or plans to "wait and see if this topic becomes notable." Sometimes there will even be copyvio or promo content that was removed long ago and reinserted by a single-purpose account. There's no reason that this backstory should be more than a click away. –dlthewave 12:35, 5 July 2018 (UTC)
  • Oppose per the concerns above, plus I prefer not to have my watchlist filled with a bot archiving 5000 talk pages. Compassionate727 (T·C) 03:29, 6 July 2018 (UTC)
  • Oppose unless the talk page is long. The talk-content may be highly relevant, if the article has also been inactive for years. Alsee (talk) 13:19, 8 July 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Remove the perennial suggestions section

This is stale and it isn't going anywhere. Also the proposer has been indef blocked for 'NOTHERE'. Kudpung กุดผึ้ง (talk) 09:27, 20 July 2018 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

In my opinion, the perennial suggestions section is useless. What if the community's opinion changes over time? Instead their opinions are censored to a box. The perennial section needs to go. Axumbasra (talk) 08:53, 27 June 2018 (UTC)

Nothing is censored, however, it does help cut down pointless, hopeless discussions before they happen. New person comes in, they don't know that RFA reform has been talked to death. This is where they learn it. Headbomb {t · c · p · b} 11:21, 27 June 2018 (UTC)
I agree with Headbomb; the perennial box lets people know a subject has been done multiple times already. If the person reviving an old conversation has new information or some other reason to believe the situation has changed since the last edition, they should explain that reasoning in their post. — AfroThundr (u · t · c) 12:10, 27 June 2018 (UTC)
  • Wikipedia: Village pump (proposals) does have a note saying "Check to see whether your idea has already been discussed at perennial proposals" so it might be an idea to look there for newcomers to the Village pump. Vorbee (talk) 15:56, 27 June 2018 (UTC)
  • I see keeping it as helpful. On top of reducing unintentional rehasing of old arguments, someone who wants to make a new case can look up why it was previously rejected and use that info to create a new proposal that addresses the previous objections.--76.65.41.59 (talk) 14:02, 30 June 2018 (UTC)

Agree with User 75.65.41.59. 81.133.110.208 (talk) 12:43, 10 July 2018 (UTC)


The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Have two new permissions: File and Page Remover

(non-admin closure) There is a consensus against this specific proposal, though there's not a clear consensus on the general principle of whether deletion can be devolved to non-admins in some way. power~enwiki (π, ν) 19:47, 17 July 2018 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Hello. I am proposing that we should add two new user permissions: File and Page Remover. The reason why we should have these permissions is that if an discussion at WP:AFD and WP:FFD outcome is delete, someone with the permission could delete it and they wouldn't need to wait for an admin. The rules for Page Removers should be:

  • The user should have an account on Wikipedia for at least a year.
  • The user must have made at least 2,500 edits.
  • The user must display levels of familiarity with doing actions per consensus.
  • The user must be active on WP:AFD
  • The user must not have performed any obvious vandalism for at least a year before applying.
  • The user also should have no WP:3RR and/or behavioral blocks for at least a year before applying.
  • The user must not delete pages without consensus, unless they are obvious vandalism!

The rules for File Removers should be the same :

  • The user must have an account on Wikipedia for at least 6 months.
  • The user must display familiarity with the guidelines of WP:NONFREE and their files should show this.
  • The user must have at least 2,000 edits
  • The user must be active on WP:FFD
  • The user must not have performed any obvious vandalism for at least a year before applying.
  • The user also should have no WP:3RR and/or behavioral blocks for at least a year before applying.
  • The user must not delete files without consensus.

These permissions would absolutely improve the convenience of WP:AFD and WP:FFD discussions, it would also help to rid Wikipedia of attack pages and other vandalism. Thank you. In Memoriam A.H.H.What, you egg?. 09:31, 2 July 2018 (UTC)

  • Oppose The problem with that proposal is that such users would be unable to fix any mistakes they might make. We can't grant them the ability to undelete content because then they could potentially view sensitive material, and allowing them to view such material would require them to go through an RFA-like process anyway. I'm also not sure what problem this is supposed to solve. You wouldn't be granting these users the ability to do speedy deletions, deletions through AfD and FfD are not urgent, and there isn't a problematic backlog of AfDs and FfDs waiting to be deleted. --Ahecht (TALK
    PAGE
    ) 17:14, 2 July 2018 (UTC)
    Not an actual problem. If the page should not have been deleted, any admin could undelete it. The rate of errors, versus rate of business as usual, would be low, so it would be a net increase in productivity.  — SMcCandlish ¢ 😼  00:33, 4 July 2018 (UTC)
  • Oppose If we trust a user enough to delete pages, then we can trust them with the entire admin toolset. Related: Wikipedia:Perennial proposals#Hierarchical structures -FASTILY 06:32, 3 July 2018 (UTC)
    While I don't support this proposal, I have to point out that your comment isn't responsive to the nature of the proposal, which is to get more hands on deck for one particular bit of maintenance, not to vet them for adminship. WP:RFAs fail all the time for reasons that have nothing to do with the candidate's understanding of and trustworthiness around page deletion (most often for civility problems, or failure to fully understand some other, completely unrelated, policy or guideline). All it takes is one slip-up, e.g. pursuing the wrong person at WP:SPA, or having breached WP:3RR and accusing someone of vandalism when the community decides it was a legit content dispute, or insert a zillion other deletion-unrelated things.  — SMcCandlish ¢ 😼  00:40, 4 July 2018 (UTC)
  • Support unbundling the delete permission in general, but I'm not sure about this proposal. I don't think there should be two groups for deleting (especially since the software isn't set up that way currently). I don't think that being unable to revert your action is a serious argument against unbundling; event coordinators can only assign the confirmed permission and stewards can globally suppress an account name but under certain circumstances need to ask a local oversighter to undo it, to give two immediate examples of this that come to mind. I also don't think that people who can delete are instantly trusted by the community with the full toolset. I would personally trust them with everything, but I think there's a case to be made that 'block' is the big ticket item that prevents the community from handing out adminship more liberally. -- Ajraddatz (talk) 17:16, 3 July 2018 (UTC)
    Somewhat OK with this. Agree not being able to undelete shouldn't be a showstopper here. Agree this should not be separate groups. Basically bring the "eliminator" group here. If so I think they should get: delete, deletedhistory, and maybe browsearchive. — xaosflux Talk 18:51, 3 July 2018 (UTC)
    Yes, though I personally dislike the name eliminator and didn't use it when making Pathoschild's global group (:P). Worth noting that other wikis tend to include undelete in the package but also have a one-week discussion period, making eliminator a sort of admin-lite with all the same bureaucracy to get it as regular adminship. I wouldn't want the same process to apply here, though it might be worth having a bit more in-depth process than PERM, whatever that might look like. -- Ajraddatz (talk) 19:28, 3 July 2018 (UTC)
    @Ajraddatz: would prob be best to use that on the back-end since it is common, but we can of course localize it. — xaosflux Talk 00:02, 4 July 2018 (UTC)
    @Xaosflux and Ajraddatz: see my comments below. I can’t imagine granting the ability that delete without the ability to view deleted content. We know the WMF won’t consent to that without an RfA equivalent process, which is one of the many reasons unbundling delete always fails to gain consensus: it’d turn into RfA, Jr. TonyBallioni (talk) 00:14, 4 July 2018 (UTC)
    Why does it need to come with the ability to view deleted content? Strange without I suppose but not technically required. -- Ajraddatz (talk) 00:58, 4 July 2018 (UTC)
    "Hi there. Seven months ago you deleted this page under the obvious vandalism! clause. I don't see how that can be, I remember it being perfectly reasonable. Please justify yourself immediately or I and nineteen of my closest friends will devote an entire WP:ANI archive page to making you look irresponsible. ~~~~" —Cryptic 01:36, 4 July 2018 (UTC)
    Heh, fair point. A sysop could always provide the deleted content or speak to it in such a case, though that would certainly not be ideal. Then again none of this is ideal; but if we want to better utilize the hundreds of users who are involved in deletion-related processes who have no desire to go through RfA this is something we should start to think about. -- Ajraddatz (talk) 01:43, 4 July 2018 (UTC)
  • Regardless of the merits, I don't think "backlogs via NACs" at AfD and FfD are a pressing enough (or at all) concern to justify this proposal. Basically, I think the above is coming at this from the wrong direction and on unsure footing. ~ Amory (utc) 19:11, 3 July 2018 (UTC)
    Agree with this - a better rationale for general unbundling of the delete permission would be to allow trusted users to become involved in the deletion process (beyond NACs) without needing to get the full sysop bit, with the need part being the distinct lack of people willing to go through RfA. This could apply to CSD tagging and deletion discussion closing. I doubt that unbundling the delete permission would ever get serious support, especially since a couple of RfAs have passed this year so people think the process is unbroken again and thus further devolution isn't needed. -- Ajraddatz (talk) 19:28, 3 July 2018 (UTC)
  • Oppose I agree with Fastily. If someone can be trusted with page deletion, why not trust them with all the tools? If there's really a problem with not enough admins, make adminship "no big deal" again. Natureium (talk) 19:34, 3 July 2018 (UTC)
  • Users carrying out administrative tasks should be held to WP:ADMINACCT whether or not they have the admin bit. You can't do that with deletions unless you have deletedhistory and deletedtext permissions, too. —Cryptic 19:40, 3 July 2018 (UTC)
  • Comment This would be useful beyond the cases mentioned here. Last week I had a new page in my user space, but when I went to move it to the mainspace, I was unable to do so due to a redirect page being in the way For some reason I mistakenly thought that I could move a new page over a redirect. Had I known that I could not, I would never have created the new page in the first place. If I had this permission, I could have deleted the redirect page and then moved my new page. As it was, I had to file a WP:Requested Moves request. Of course, this was not obvious vandalism, but an uncontroversial technical move (G6). I would expect thoigh that it could be used on any Wikipedia:Criteria for speedy deletion Hawkeye7 (discuss) 20:17, 3 July 2018 (UTC)
  • Oppose as the ability to delete needs to come with the ability to undelete abd view deleted content. The WMF will not consent to this without an RfA equivalent process for legal and political reasons. Community opinion on this simply doesn’t matter as it would be vetoed by the office. TonyBallioni (talk) 00:09, 4 July 2018 (UTC)
  • Support in theory but not this particular proposal. Deletion is not as dangerous as people think it is (it can always be undone), but various aspects of this are a bit daft. We don't have hard requirements of a sort this specific even for full adminship, for starters. A more specific criticism would be that being active at AfD doesn't indicate anything. There are AfD regulars who are rabid inclusionists and rabid deletionists who are both too often wrong. There are also rubber-stampers who never !vote at AfD unless they're already sure where the consensus will go, because they're trying "sculpt" their AfD stats for a run at WP:RFA some day. Doesn't indicate any understanding of deletion policy. A solid WP:CSD-tagging track record would be a better indicator.  — SMcCandlish ¢ 😼  00:30, 4 July 2018 (UTC)
  • Oppose: I'm not sure I can fully support this proposal as written, given the low standards required. It, indeed, might be best for us to revert to the "RfA is no big deal" if this gains traction: I am entirely uncomfortable with the idea of particular users, through user permissions (which, though no offense is intended to the administration, are granted solely by one person, and sometimes as a matter of course), being able to delete pages without the whole of the community weighing in on said person's suitability. (Moreover, if this passes, the inherent security issues glossed over in the proposal are a serious concern.) In short, the RfA process is the right place to go for this, and not a new permission. Javert2113 (Siarad.|¤) 00:49, 4 July 2018 (UTC)
  • Oppose. I would be very surprised if (delete), (block), or (protect) ever get unbundled from the administrator toolset. Everything else, maybe, but these three seem to be the "core" set of admin tools. I'm not too familiar with WP:FFD, but at least for the past year administrators have been pretty good about closing WP:AFDs on time. The administrative backlog isn't so egregiously long that we need to change our process from how it's been for 15 years. Mz7 (talk) 02:21, 4 July 2018 (UTC)
  • Oppose really don’t see the need for this, and some of the criteria seem pretty arbitrary. Aiken D 18:22, 4 July 2018 (UTC)
  • Oppose While I would actually rather enjoy being able to close FFD discussions properly and completely since file maintenance is my specialty I still do not believe that delete, protect, or block should ever be unbundled from the admin toolkit. Those three all play off well with each other and like others have mentioned, if you delete it you should be able to bring it back. If you want any of three abilities WP:RFA is your only option and I would prefer if it stayed that way. --Majora (talk) 01:01, 10 July 2018 (UTC)
  • Oppose deletion is best left to admins, this would cause many errors Atlantic306 (talk) 20:59, 10 July 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Bot to deliver Template:Ds/alert

Should there be a bot to deliver Template:Ds/alert? (This is basically an advisory RfC to Arbcom.) 17:57, 2 July 2018 (UTC); note added: 08:23, 18 July 2018 (UTC)

We have a long-running problem that is easy to solve technologically:

Short version:
Discretionary sanctions (DS) are not working as intended. Most editors – including topically disruptive ones – are immune to DS for lack of "official awareness" on a per-topic basis. Our awareness templates are disused, because when editors hand them out to each other it looks like a threat rather than an awareness notice. It escalates instead of having the intended effect.

Have a bot neutrally and automatically deliver them, based on participation level on pages that are subject to discretionary sanctions.

The alerts are not admin warnings about user behavior, but notices from anyone that different rules apply to a topic; nothing more. The bot can be crafted to exclude minor edits, new users, rote edits like category fixes, etc.

The details:

  • The Arbitration Committee invented discretionary sanctions (DS) to deal more swiftly with disruptive editing; it is applied on a per-topic basis.
  • No one is actually subject to DS unless they are "aware" that DS apply to the particular topic area in which they are being disruptive.
  • This "official" awareness only happens a very limited number of ways, typically by being a party to an ArbCom case that imposes DS on the topic, being subjected already to disciplinary sanctions in that topic area personally, or receiving a {{Ds/alert}} template on their talk page for that particular topic (this awareness provided by the template is deemed to have expired after one year).
  • Talk pages of articles (and other pages, e.g. topical guidelines) subject to the DS receive a banner about the DS at the top of the talk page (also often used as an editnotice seen when editing the actual article). Despite being prominent, these do not constitute "awareness" on the part of anyone participating on the talk page or editing the non-talk associated page. All it does is provide a means of identifying which pages are subject to DS (rather like wikiproject banners on the same page categorizing by project).
  • ArbCom's intent was that editors active in such topic areas would routinely receive these Ds/alerts so that no one is a) caught by surprise that DS pertain to that topic, or b) able to WP:GAME their way out of sanction by making a show of not being aware of them.
  • However, this does not happen in actual practice.
    • Virtually zero admins ever leave a Ds/alert unless they were already going to impose DS on someone and found that they could not (i.e., in such a case the disruptive party effectively has already system-gamed their way out of sanctions; in theory, one could make an ANI report about the disruptive activity, but ANI typically has higher standards than DS does for what is actionable).
    • If non-admin editors leave a Ds/alert on the talk page of an editor whose behavior in a topic seems to indicate they are unaware of the DS that apply to the subject, this is universally treated as hostile – as a threat, as one-upmanship, or as just "noise". Because it was delivered by a non-admin, it is not treated as a notice of awareness, not read, not understood. In effect there is nothing routine about editors leaving Ds/alerts for each other, despite the intent of the templates, which often make dispute worse rather than calmer.
  • Consequently, the discretionary sanctions system is not actually very functional. This engenders continual disruptive activity in "hot topics", inaction on the part of WP:AE admins, unnecessary re-litigations of previous ArbCom cases (e.g., after WP:ARBAP and WP:ARBAP2, a new ARBAP3 is being contemplated to deal with non-stop disruption at articles on modern American politics, because DS are not being employed – too many disruptive editors are immune to them for lack of Ds/alerts.
  • The obvious solution is for a bot to automatically deliver Ds/alerts on a topical basis to the user talk page of every editor who makes more than X number of non-minor edits within Y timespan at a page (or its talk page) that is covered by discretionary sanctions for the same topic. Delivery would be skipped if the editor has already received a Ds/alert for the same topic within the same year. (The templates could also be left manually by any editor, in the case of DS-covered pages not properly categorized as such.)
  • In considering the proposal, please do not get mired in minor implementation details. These would get hashed out in later discussions developing the bot and considering it for approval. E.g.: excluding new, e.g. non-autoconfirmed, editors from automated notices; ensuring no one's first talk page notice is a DS notice but a welcome message; excluding minor edits; detecting tiny edits (or identical page-after-page edits, or paticular classes of edits like category updates or dispute/cleanup tagging) that were not flagged by an editor as minor; maybe having an opt-out from the bot delivery for gnomes, with presumption of awareness; counting edits made over several days as just one edit (i.e., requiring longer-term participation in a DS topic to receive an auto-notice); ability of an experienced mentor to opt a new editor out of further notices; and so on. No solution is ever going to be 100% perfect, and it need not be, just better than the status quo.
  • Should WMF decide that a community RfC can't directly authorize this bot, ArbCom should take the community input in the RfC as advisory.

Side benefits of this approach:

  • The current scary and TLDR wording of the {{Ds/alert}} template, which ArbCom has declined do anything about despite years of complaints, would be demanded by the community to be trimmed to a short and informative message that: a) Just so you know, DS apply to this topic; and b) this is a good thing because it keeps us focused on the content and sources not on editor personalities. c) Thank you for saying on-topic, reducing dispute, and helping improve our articles.
  • We would no longer need "terrify new editors" messes like {{American politics AE}} atop various articles; the normal {{Ds/talk notice}} used on article talk pages and as editnotices would be sufficient (with a concise parameter for anything special like a 1RR restriction).
  • It will thwart "PoV railroading", by putting all regular editors of a DS topic on equal footing. Currently, drama-prone experienced editors who know the rules well can strategically deliver Ds/alerts to all their opponents, while their "side" are mostly not subject to DS. This is a tagteaming, sanction-gaming, and "civil PoV-pushing" technique that would no longer be effective.

— SMcCandlish ¢ 😼 17:46, 2 July 2018 (UTC); clarified: 17:26, 3 July 2018 (UTC)

Comments on Ds/alert bot proposal

  • Support. This is an excellent idea. It lends itself very well to automation, and would serve an important but unmet need. Beyond the strong argument put forth above, I want to point out that some thought needs to be put into determining which pages would be recognized by the bot as being within a DS topic area, because sometimes not all applicable pages get tagged with the page notices. --Tryptofish (talk) 18:10, 2 July 2018 (UTC)
    • Now that ArbCom has enacted a motion that forbids the use of bots and some kinds of automated tools for delivering alerts, I'm coming back here to update my opinion. I still believe that some sort of, well, bot-like process has value here. If the Arbs feel that there has to be some element of human decision-making to issue an alert to a given editor, I can accept that reasoning. But there should still be room for considering "semi-automated" options. And the bottom-line issue for me is that the DS alert system needs to be made more informational and less threatening, however that may be accomplished. --Tryptofish (talk) 18:46, 5 July 2018 (UTC)
      • ArbCom's motion isn't designed to subvert this proposal. It specifically says "alerts are expected to be manually given at this time" (emphasis mine) and "The Arbitration Committee will fully review the advisory Village Pump discussion after completion and take community comments under consideration." --Ahecht (TALK
        PAGE
        ) 20:01, 5 July 2018 (UTC)
        • I think you are attributing to me something that I did not say. --Tryptofish (talk) 19:27, 6 July 2018 (UTC)
  • Support, as proposer. I've informally suggested this idea for a long time. On numbers, my initial though is that perhaps 10 edits in 1 week to the same DS-covered topic should be enough to trigger the alert. E.g., if you edit Donald Trump, Hilary Clinton, and Talk:Racial views of Donald Trump a total of 10 times this week, you get {{Ds/alert|ap}} if you haven't already received one this year. I would entertain a wide range of alternative numbers. — SMcCandlish ¢ 😼 18:13, 2 July 2018 (UTC)
  • Oppose. Non-admins issue DS warnings all the time. The result is going to be a large number of bot messages (e.g. after responding to a RfC or doing relatively minor gnoming edits) which will just be ignored. The system also won't work on the many pages which are not DS marked but that portions of them fall under DS (ARBPIA is full of these). The current system essentially provides a one warning grace to new (or returning) users in a topic area, which is not a bad thing.Icewhiz (talk) 18:18, 2 July 2018 (UTC)
    "All the time" = about 1/50th of the times that they should, and generally with a "go screw yourself" response. It's almost universally treated with flippant hostility. People who receive these from other editors generally don't read them, and simply go into a tit-for-tat dispute escalation mode. That some pages need to be categorized as subject to particular DS is a very trivial technology problem we can fix in about an hour. Ds/alerts are not warnings; they are informational. This fact is central to both the problem and the solution. A bot delivering the same awareness notice has no effect at all on whether someone gets their "grace period"; it just prevents inveterate disruptors evading sanctions for months or years because most editors are scared to deploy the template on someone else. — SMcCandlish ¢ 😼 18:20, 2 July 2018 (UTC)
    I think the concern about RfC responses and gnomish edits is a valid one, one that I was thinking about raising myself before Icewhiz beat me to it. It might make sense to set a threshold on a per-page basis, rather than per-topic. That way, the editor making gnomish fixes on multiple pages won't get caught up in it. Also, use of the bot should not preclude manual alerting. That way, editors could use discretion to alert users about page sections. --Tryptofish (talk) 18:27, 2 July 2018 (UTC)
    I integrated some of this into revised proposal notes above. — SMcCandlish ¢ 😼 18:16, 3 July 2018 (UTC)
  • Comment - Rather than an exact one year, any automated template should probably be triggered at something like 11 months or 350 days if you're worried about the warnings going stale. MarginalCost (talk) 18:23, 2 July 2018 (UTC)
    The first draft included that, but it's not necessary. No one needs a reminder if they are no longer editing in the topic area. If they are, then they'll auto-receive another notice in due course when they make the X number of edits in Y timespan to the same DS topic after their old notice expired. — SMcCandlish ¢ 😼 18:26, 2 July 2018 (UTC)
    Sure, I'm not saying it should "auto-renew," just that when someone trips the "X edits in Y time" filter, and the bot checks for the last notice, it should run even if the last warning was 364 days ago. MarginalCost (talk) 18:50, 2 July 2018 (UTC)
  • How should the bot know which pages (not topics) are under which DS? --Izno (talk) 18:27, 2 July 2018 (UTC)
    • I think it would have to be based upon a page notice template, or edit notice, already having been put on the page or talkpage. --Tryptofish (talk) 18:29, 2 July 2018 (UTC)
    • (edit conflict) Simplest approach would probably be hidden categories, applied by {{Ds/talk notice}} and its variants (i.e, what Tryptofish said). — SMcCandlish ¢ 😼 18:30, 2 July 2018 (UTC)
      • As I said in my original comment, there would still be the issue of pages that haven't yet been identified with a tag, but which are within the topic area. --Tryptofish (talk) 18:32, 2 July 2018 (UTC)
        Then we add the tag. It isn't necessary that a solution be 100% perfect for us to implement it as an improvement. The point is to bring most people editing within a DS topic into awareness of the DS. If we miss a few that's okay. The status quo is that we're missing almost everyone. — SMcCandlish ¢ 😼 18:41, 2 July 2018 (UTC)
        I agree, but I felt it important to point it out. It's important that editors still be able to issue alerts manually, in addition to any bot. --Tryptofish (talk) 18:45, 2 July 2018 (UTC)
        Oh, sure! This wouldn't prevent that. I've clarified the proposal on this point. — SMcCandlish ¢ 😼 18:53, 2 July 2018 (UTC)
  • Support the concept, assuming the details around thresholds and such can be resolved. This is an area that would benefit from the consistency and perceived neutrality of a bot. --RL0919 (talk) 18:35, 2 July 2018 (UTC)
  • I personally support this idea, but it's my understanding (in my personal capacity, speaking only based on on-wiki statements) that a substantial part – likely a majority – of the committee does not. Kevin (aka L235 · t · c) 18:50, 2 July 2018 (UTC)
    The committee membership changes yearly, and are not a hive mind. They also never collectively do anything to make DS functional. The entire point of this RfC is that the community can and should step in where ArbCom is failing to get the job done. "The Committee has significant autonomy to address unresolvable issues among the community, but at the same time does not exist to subvert community consensus, ... or to decide matters of editorial or site policy." Implicit in this is, of course, that it can't subvert a community consensus that emerges after ArbCom's creation or about something ArbCom has implemented. — SMcCandlish ¢ 😼 18:59, 2 July 2018 (UTC)
  • Support – This system would avoid personalizing the delivery of notices, that always have a potential for being interpreted as criticism. Also, the bot could easily check whether a notice was already served in the prior 12 months, which is a tedious task for editors. — JFG talk 19:23, 2 July 2018 (UTC)
  • Support An obvious solution to the problems outlined above. I think it will be good for editors who may only comment once or twice in an area, if it is worded nicely like SMcCandlish suggested. It would encourage neutral editors to keep the page on their watch list and have more eyes on contentious areas so it hopefully doesn't spiral as easily. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 19:28, 2 July 2018 (UTC)
  • Support a great solution that would save a lot of editor time, and make the process more impartial. Ideally would be a separately named bot so that it can be seen easily on a page history.--Tom (LT) (talk) 19:46, 2 July 2018 (UTC)
  • Would it make sense to only count non-minor edits? I imagine some people would think that too easy to game, but we have a lot of AWBers and HotCaters, and I don't know that we want to spam editors with every Ds notice available for fixing dates and hyphens and categories. Poor Giraffedata! ~ Amory (utc) 19:52, 2 July 2018 (UTC)
    Yep. I added that clarification. (It had been in the first draft but I cut it out accidentally!) — SMcCandlish ¢ 😼 20:51, 2 July 2018 (UTC)
  • I’m of the opinion this is forbidden by WP:AC/DS. It states “Any editor may advise...” Bots are not editors. By my reading, automatic alerts are incompatible with the requirement that an editor be issuing the alert. Even if this is not the case, I’m opposed, as a human touch with specific advice and wording greatly reduces the unintended biting effect of alerts. ~ Rob13Talk 20:21, 2 July 2018 (UTC)
    • Any editor may advise, in that it's not limited to admins or senior, etc. The editor in an AE action has to be notified. Whether it's by an editor or a bot is irrelevant. Sir Joseph (talk) 20:35, 2 July 2018 (UTC)
      • That’s not what it says, and I at least consider it heavily relevant. The community should probably be aware that the Arbitration Committee has jurisdiction over discretionary sanctions procedures, not the community. I doubt we intended automatic alerts. If we did, we would have implemented them. ~ Rob13Talk 20:43, 2 July 2018 (UTC)
      • I agree with Sir Joseph about that. The only reason the wording is "Any editor" is because there wasn't a bot when that was written. It would be a different matter if it had said "Only an editor who qualifies by xyz may...", but it doesn't. I also would advise that ArbCom members should not be too quick to oppose input from the community. --Tryptofish (talk) 20:48, 2 July 2018 (UTC)
        If – due to some wikilawyerly wrangling about jurisdiction/scope/authority between the editorial community, ArbCom, and WMF – it is determined that this RfC can't directly authorize this bot ArbCom will at least need to take it as strongly advisory. — SMcCandlish ¢ 😼 21:06, 2 July 2018 (UTC)
        If ArbCom doesn't want this to happen and passes a motion to that effect, it's not happening. DS is an ArbCom enforcement process and ArbCom has the right to dictate how its remedies are, and aren't, enforced. Kevin (aka L235 · t · c) 22:16, 2 July 2018 (UTC)
        I agree that ArbCom does have that authority, but my advice to them would be to take community sentiment very seriously. --Tryptofish (talk) 23:55, 2 July 2018 (UTC)
    • More to the point, bots are – as a matter of policy – extensions of the editors who operate them, and those editors take responsibility for their edits; they are not considered independent entities; see WP:Bot policy. So this "Bots are not editors" thing is a non-issue. [Policy background: If bots were not formally considered side accounts of their human operators, then bots would actually have no permission to ever make any edit of any kind; WP:Editing policy provides this right to editors in good standing. Yet bots are, obviously, actually permitted to make edits, ergo they qualify as editors in good standing, when they are approved bots (and functioning properly).] — SMcCandlish ¢ 😼 20:51, 2 July 2018 (UTC)
      • Botops are responsible for their bot's edits in theory, but in practice there is a large difference. Botops only get in trouble if they screw up hard technically (demonstrating they should not be trusted with a bot account with high-volume editing abilities) or knowingly let the bot do some stuff that goes against consensus or BRFA scope; a series of 100 stupid edits that would get a human WP:NOTHERE-blocked can be forgiven as a configuration mistake (and fortunately so). In the discussed scheme, it would be extremely different to have a bot deliver notices to everyone according to hardcoded criteria than to have the botop hand out notices themselves (as you note in the OP, this is viewed as personal hostility). TigraanClick here to contact me 09:27, 3 July 2018 (UTC)
        "knowingly let the bot do some stuff that goes against consensus or BRFA scope" – delivering ArbCom-and-community-approved notices in an manner also so approved won't be against consensus or BRFA scope, so this just doesn't arise. — SMcCandlish ¢ 😼 18:20, 3 July 2018 (UTC)
    • Even if AC/DS's wording excludes bots intentionally (which of course is far from clear), for your argument to hold water, it still needs that either (1) ArbCom has the jurisdiction to forbid bots from doing certain kinds of editing (in that case placing DS templates), without a motion or whatever explicitly making this point, globally (for all bots, not just those operated by a sanctioned botop); or (2) a template placed by a bot could be considered not to validly make the recipient aware of DS (when the same template left by the botop would). Both propositions seem far-fetched to me. TigraanClick here to contact me 09:27, 3 July 2018 (UTC)
    • @BU Rob13, "the human touch" as you call it is disallowed, at least initially. Somewhere since the current system was implemented there was discussion/instruction that the alert must be provided by the template, to thwart the problem with the prior notices of using them to do battle. It was felt that standardizing the FYI would help reduce the battle mentality, and so the thread with the alert HAD to begin with the template. There is no instruction to add any followup. Having given many alerts, they are always receive as a seeming threat, and so I devised a way to deescalate that... I gave the same alert to myself, and would follow up with a custom commment in a separate edit saying I had done so. That's the "human touch" I chose to add, but there's no requirement that I do that, and a bot-delivered version could also tell people not to take it personally because everyone in the topic area who edits at the threshold gets thme. NewsAndEventsGuy (talk) 07:32, 4 July 2018 (UTC)
  • Support I support this, I too find that oftentimes the DS alerts are not seen as the friendly notice. Sir Joseph (talk) 20:35, 2 July 2018 (UTC)
  • What is the ideal number of X and Y that avoids people going on AWB-based typo fixes (or comparable mass efforts) from being spammed. Jo-Jo Eumerus (talk, contributions) 20:42, 2 July 2018 (UTC)
    • The bot operator would have to prevent such spamming with a throttle specific to each editor receiving too many alerts, since that would be disruptive and disruptively alerting editors could lead to sanctions for the bot operator under our current procedures. ~ Rob13Talk 20:46, 2 July 2018 (UTC)
    • Also, the proposal has been clarified to exclude minor edits. A smart bot could also exclude AWB/JWB edits, and those made with specific other edit tools (either by tool notes in auto-generated edit summaries, or by specific WP:EDITFILTERs. These are very simple technological tweaks; our bot crafters are generally very competent at this stuff. — SMcCandlish ¢ 😼 20:53, 2 July 2018 (UTC)
  • Support - I'm pretty sure I suggested this 3-4 years ago. I believe it should be set up to deliver the alert when X=1. Some of the most troubling edits are from users whose first edit to an article is a policy violation, frequently followed by more policy-violating edits. It should nipped in the bud as early as possible. If WP:AC/DS doesn't allow bot alerts, change WP:AC/DS. Alternatively, Arbcom can change the requirement that an alert be delivered to an editor before the editor can receive DS sanctions - MrX 🖋 20:48, 2 July 2018 (UTC)
    Would conflict with WP:BITE. We already have WP:UWT to deal with this learning-curve problem, and it has served us well. For those who take the opposite of MrX's position: If we wanted to, we could even tweak the bot to excempt accounts that are not WP:Auto-confirmed, if we wanted to give new editors more leeway than people who should know better already. — SMcCandlish ¢ 😼 20:54, 2 July 2018 (UTC)
    Although MrX is correct that sometimes a new editor can be a big problem, I think that is something better left to editor discretion, rather than the bot. There will be a lot of gnomish etc. single edits, so I think an automatic X=1 is a bad idea. Let those users be notified manually. But I definitely would not set any criteria like auto-confirmed, because there are new users who make trouble. --Tryptofish (talk) 21:05, 2 July 2018 (UTC)
    Your first and last sentences seem contradictory. To clarify, the potential idea is that non-autoconfirmed editors would be left to editor discretion (i.e., manually delivered alerts). I don't feel that strongly about it, but a, anticipating BITE as an objection, and discussion below is already bearing that out. — SMcCandlish ¢ 😼 01:02, 3 July 2018 (UTC)
    Nah, getting a politely worded alert is not a bite—it's a lick on the face and a wag of the tail.- MrX 🖋 21:38, 2 July 2018 (UTC)
  • Support - The technical details can be tweaked over time. GMGtalk 21:15, 2 July 2018 (UTC)
  • Support It also helps in the sense that it simply gives users more information about the topic that they are editing, and where the community stands on it. Seems like it will reduce disruption. — Insertcleverphrasehere (or here) 21:20, 2 July 2018 (UTC)
  • Support. It will help a lot more than the piecemeal method we currently use to give out discretionary sanctions. If such notices are applied automatically (regardless of the threshold that's ultimately used), it's possible editors would take more care in their edits, especially if they aren't previously aware of the sanctions. A bot-issued notice issued casually is not as personally targeted as a tag that's applied by a human in the midst of an edit war, so it's likely that people will take offense. (Although, on the other hand, some people might abuse this system by tagging all their edits as minor. This could probably be resolved with further filtering that could detect semi-automated minor edits vs. manual minor edits.) epicgenius (talk) 21:30, 2 July 2018 (UTC)
  • Minor Edit Query - As the flip side to the point raised directly above by Epicgenius, lots of actually minor edits are not tagged as such, and I feel it would be inappropriate to also tag them with these warnings. Can it can be calibrated to count edits which make a +30/-30 change? I realise that with effort a near 0 byte change can be made, but that is fairly rare and wouldn't disrupt the idea. Newbie gnomes which are fairly common are especially unlikely to remember to tag as minor edits and are most vulnerable to problems with the warning. Nosebagbear (talk) 21:50, 2 July 2018 (UTC)
    About minor edits, I think it's relatively uncommon for a good-faith gnome (or a good-faith RfC respondent on the talk page) to make more than a few edits per page, so I think that a carefully determined minimum number of edits per page before triggering the bot would take care of a lot of that. And for users who make many consecutive minor edits, it's probably a good idea to notify them. For example, for the GMO DS, there are requirements about not changing some wording, so even editors making what they think are minor edits could actually violate the DS. --Tryptofish (talk) 22:04, 2 July 2018 (UTC)
    Both of these seem reasonable; this proposal is to authorize such a bot and set the wheels in motion, not actually write all the code for it on the spot. :-) — SMcCandlish ¢ 😼 00:40, 3 July 2018 (UTC)
  • Support: As a concept, I can fully support this, as the posting of discretionary sanctions is, shall we say, somewhat lax. I'm sure the details which are not laid out here, and any issues arising from those, can be sorted out at a later time. Javert2113 (Siarad.|¤) 22:00, 2 July 2018 (UTC)
  • Oppose. Maybe I'm old fashioned but I like to see bad or at least borderline behavior before issuing a warning. Spamming warnings to all editors who happen to edit a page is a turnoff to new and well-intentioned editors and will lead to warning fatigue for long-term editors. I'm much more likely to ignore messages from bots than those from humans. And yes, I know that there are editors who take it upon themselves to spam warnings to everybody new in a topic area, regardless of how well the new people are behaving. I frown on that. But more importantly, a lack of notifications is clearly not the problem. Take U.S. Politics as an example: a few months ago User:Coffee basically made himself the bot that is proposed above and issued a warning to basically everybody who had made any recent edits to U.S. Politics pages. All those warnings are all still in effect, yet the US politics topic area is a disaster area. The solution to lack of enforcement is, well, enforcement, not automated warnings. And I am fully aware of the irony of me saying that as an admin who has been passively watching several U.S. politics articles for some time now. ~Awilley (talk) 23:26, 2 July 2018 (UTC)
    Awilley, consider that this also would present an opportunity to make the notice much more user friendly and less BITEY, as an automatic notice added by a bot because of some threshold which we would need to explain somehow. GMGtalk 23:35, 2 July 2018 (UTC)
    @Awilley: To repeat a point already made in summary above: ArbCom has been very, very clear that these are not warnings and do not imply wrongdoing. There are nothing but notices to make people aware of the applicability of DS to the topic. Previous attempts to interpret them as warnings and appeal or challenge them have been flat-out rejected by ArbCom as misunderstandings of what the templates are/do/mean. — SMcCandlish ¢ 😼 00:51, 3 July 2018 (UTC)
    @GreenMeansGo, less bitey would be nice in any case, but like I said, lack notification isn't the problem or the solution.
    @SMcCandlish, I fully get that the template says it is does not imply wrongdoing, yet we end up having the same conversation on thousands of user talk pages ("Then why did I get this?"). I'm not able to do the mental gymnastics required to believe that the template isn't a warning. It is clearly a warning that special rules apply to a topic area and that those rules will be enforced by administrators wielding blocks and bans. ~Awilley (talk) 16:06, 3 July 2018 (UTC)
    And users should be aware of that via neutral process with a user-friendly notice that's about the topic not their personal edits; rather than threatened with it by individual PoV pushers who are trying to scare them based on what their last edit was. — SMcCandlish ¢ 😼 17:07, 3 July 2018 (UTC)
  • Oppose The DS warning is scary and I'm concerned about the impact on editor retention. — BillHPike (talk, contribs) 23:31, 2 July 2018 (UTC)
    @Billhpike: Please see the first point under "Side benefits of this approach"; an explicit goal of this proposal is to make them less scary (because ArbCom refuses to do so until the community demands it in a way they cannot ignore any longer). Aside from L3X1's point immediately below, a new editor is going to get one of these eventually if they keep editing in a DS topic area, and they're going to get the scary current version. — SMcCandlish ¢ 😼 00:54, 3 July 2018 (UTC)
  • Support DS is not scary, and anyone new enough to be put off by larger colored notices on their TPs probably shouldn't be working in DS areas. We should add a "What is this" link at the bottom that takes them to an essay explaing very clearly that this is a piece of boilerplate and doesn't mean they are about to be dropkicked off the project. Thanks, L3X1 ◊distænt write◊ 23:39, 2 July 2018 (UTC)
    As this is probably to going get No Consensused and then Perennial Proposalled, I made User:L3X1/sandbox#Sample_essay as a sample for what a non-indepth, brief, easy to use and understand essay on DS could be like. I could have sworn we had essays on DS already, but cannot find them. Feel free to wade in or comment here or on my TP. Thanks, L3X1 ◊distænt write◊ 01:54, 3 July 2018 (UTC)
    Re: "anyone new enough to be put off by larger colored notices on their TPs probably shouldn't be working in DS areas" That's right. We don't want New Editors with fresh viewpoints working in DS areas. Better to just keep the long-term entrenched editors pursuing grudges and enforcing stalemate. ~Awilley (talk) 16:11, 3 July 2018 (UTC)
    Oh, please. You all know I have a dim view of content editors "pursuing grudges and enforcing stalemate", but we all know new editors parachuting in without significant understanding of our policies are going to be in for a very rough time. I'd be more than happy to support a proposal to Gold-lock are articles under DS, and onlu open then up once a quarter to implement whatever changes have received consensus in the interim, as for civility police to ban with prejudice anyone doing anything remotely unhelpful or uncivil, but such a proposal is never to going to make it around. New editors often don't have "fresh viewpoints", they have their POV just like anyone else. Thanks, L3X1 ◊distænt write◊ 16:21, 3 July 2018 (UTC)
    Sorry about the straw man, it was hard to resist. That's said, in my experience new editors often come in with a different perspective that is quite refreshing compared to the baggage carried by long-term entrenched editors. Sometimes the the regulars miss obvious and simple solutions to their problems because they are so caught up in fighting with the other side. Also, I'm not just talking about newbie editors, but also experienced editors wandering into the topic area for the first time. ~Awilley (talk) 17:38, 4 July 2018 (UTC)
  • Oppose I don't want editors who make a copy edit at Dan Quayle or Bulgaria or Electronic cigarette getting a DS alert (yes, this electronic cigarette topic area is under discretionary sanctions, and they have been used against exactly three editors in the 2.5 years they have been around, and two of those three were warned by the committee directly, so ARCA or AE could arguably have been used without DS being needed). This would be so disruptive because as Euryalus (ping since I'm appealing to him without being able to find the exact quotes) has pointed out on numerous occasions, discretionary sanctions have expanded greatly and we'll soon approach the day where arguably everything could be under it if ArbCom is not careful.
    I like the idea for its simplicity, but when we think of the scale of the DS regime, this would cause a lot of TP notifications for a lot of people, most of whom have no clue that ArbCom exists and would be productive contributors to their obscure topic area that has legacy DS without the need to be told about it. TonyBallioni (talk) 01:03, 3 July 2018 (UTC)
    • @TonyBallioni: Detecting and ignoring minor edits (even ones not checked-off as minor) is already part of the proposal. And the scope of a problem is no reason no to work on the problem. If DS are expanding that much, the entire system has to be overhauled anyway; i.e., every new editor will need to be aware of DS the day they start editing, and DS will need to be integrated directly into all behavioral policies and guidelines.
  • Oppose I'm skeptical we can filter out copy editing, counter vandalism, and other uncontroversial editors who move between many articles, and would end up getting spammed with notices. The defacto effect of a DS notice serving as a warning an editor is heading into dangerous waters is lost when we spam them out at everyone, while per policy there is nothing to stop an editor from DS noticing people making totally uncontroversial edits in covered articles, this rarely happens, and doing so with a bot would not be an improvement. Finally, the argument that this would force improvements to the DS notices puts the cart before the horse, get the notices fix first before we authorize expanding their use. Monty845 01:11, 3 July 2018 (UTC)
    • @Monty845: Skeptical on what basis? Do you really think it'll difficult to detect any of the following?: minor edit, short edit, back-to-back edits (to treat them as one), edits made with AV tools, reverts, an editor making the same edit on page after page? It won't be. If it came down to it, we could have a DS noice opt-out user permission (with presumption of DS awareness accepted as the price of entry; WP:GNOMES already tend to assume anything they edit could be under DS since they hit topic after topic). Next, ArmCom is insistent that these templates are just informational notices, not warnings or threats. The waters actually are dangerous and this should not be hidden. Finally, ArbCom have been prodded about all this many times, for years, and just sit on their thumbs. — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
      • @SMcCandlish: I would propose a hypothetical to you: An editor experienced with BLP enforcement notices an editor has made a series of unambiguous BLP violations in an area subject to DS. That editor then goes in, and correctly applies BLP policy in a neutral and dispassionate way to those articles, removing all BLP violations, and then moves on. Large edits, to several articles subject to the same DS, that are not mere reverts. Should that editor get a DS notice? I would argue no, but will the bot be able to tell that is what is going on? DS notices should be for those who are getting WP:Involved (though in this case, obviously not limited to admins) in the nexus of controversy, not passersby who are neutrally enforcing site wide policies, or making other gnomish edits. I think this level of judgement is beyond the likely capabilities of a bot. Once we agree a bot should do this, not being able to implement this sort of judgement will be an argument against such a rule, not an argument against doing this at all. When we agree to general ideas, without a full structure, knowing the details will be controversial, it often ends in a mess. Monty845 15:11, 4 July 2018 (UTC)
  • Support as a reasonable solution top a real problem. EvergreenFir (talk) 01:15, 3 July 2018 (UTC)
  • Oppose I think this is a very well intentioned idea and part of it makes sense, but I too feel it will impact editor retention, especially those that may see the horrid agenda driven POV pushing and near SPA's that tend to haunt some articles and sincerely wish to just help. Having a bot show up at their page just because they make an edit or comment is not the right way to handle this. While it would depersonalize things somewhat and help prevent losers from slapping DS "reminders" on ones page in some childish way to somehow intimidate or passively-aggressively threaten someone they might have had a tiny spat with, I still think having humans do the reminding/notifications is best.--MONGO (talk) 01:23, 3 July 2018 (UTC)
  • Oppose This creates more problem than ever there's with DS alert system. Having bot automatically spamming editors unnecessarily. If human cannot detect why someone needs the notice then they probably shouldn't know, if the template text is perceived as cold and wordy, then modify it. –Ammarpad (talk) 01:36, 3 July 2018 (UTC)
  • Support as part of overall AE/DS reform. Distributing (rewritten) DS alerts frequently and neutrally would help raise awareness and reduce the stigma of receiving a notice. The first time I received an alert, it helped me understand the resources available for dealing with disruptive editors in that topic area.
We also desperately need an easily understandable guide to how the entire process is supposed to work. The links in the current DS alert template lead to pages and pages of vague WikiLegalese, including the expectations section which many editors will recognize as basic requirements for all of Wikipedia. This would also provide an alternative to an unofficial DS FAQ which some editors are attaching to the AP2 alert.
Or we could eliminate the awareness requirement. The first formal warning issued by an admin would serve the same purpose. –dlthewave 02:19, 3 July 2018 (UTC)
One more (tongue-in-cheek) idea: Set the bot to send all of the DS alerts to every editor once a year irregardless so that we're all on the same page. –dlthewave 00:46, 19 July 2018 (UTC)
  • Support This is an obvious solution, it should already have been implemented. A DS alert is less scary or threatening from a bot than from a person. The alert should be non-judgemental, and should not differentiate edits on the basis of being helpful, well-meaning, trivial, controversial, minor or any other characteristic. It should simply and routinely alert editors of articles that have discretionary sanctions, otherwise there is going to be selectivity and bias in this process. Bots do some tasks well so humans can get on with building an encyclopedia. Jack N. Stock (talk) 02:30, 3 July 2018 (UTC)
  • Support per proposer.
    As a side comment, I'm 110% behind the proposer's wise advice: "In considering the proposal, please do not get mired in minor implementation details. These would get hashed out in considering the bot for approval (e.g., perhaps excluding tiny edits that were not flagged by an editor as minor). No solution is ever going to be 100% perfect, and it need not be, just better than the status quo." I've had a comment to that effect near the top of my user page for years.Mandruss  02:38, 3 July 2018 (UTC)
  • Weak Oppose - Such notices should only be delivered if a user is making substantial edits that are not clearly appropriate (e.g. neutral copyedits would be clearly appropriate). A purely numerical measure has been proposed; A qualitative evaluation of the edits is preferable, therefore, this is not a task particularly suitable for a bot (that is not exceptionally advanced). — Godsy (TALKCONT) 03:10, 3 July 2018 (UTC)
    • @Godsy: Except this isn't the actual intent of the templates or ArbCom's creation of them. They're not user-behavior warnings. The fact that people use them as if they are and only as if they are is actually part of the problem. They're just notices that particular topic areas are covered by different rules. Why would/should an editor not be made aware of that? — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
      • @SMcCandlish: I concur with your first four sentences but wholly disagree with your last. Wikipedia:Arbitration Committee/Discretionary sanctions#Awareness and alerts; Why would an editor want to be made aware of anything that opens them up to a potential sanction? — Godsy (TALKCONT) 02:51, 4 July 2018 (UTC)
        • @Godsy: That's not what I asked, though, and chose the wording carefully (other than forgetting the slash, now fixed). I'll rephrase it even more plainly: Why would/should the community not want an editor to be made aware? That is, we collectively have an interest in editors at DS topics being aware of the DS so that they're less likely to be come disruptive, and so that if they do, their disruption can be quickly dealt with. If they never turn disruptive, their awareness does them no harm. It's a win-win either way. Of course an individual editor with questionable motives may want to escape "official awareness", and thereby escape some potential sanctions. But it's maladaptive for the community to enable such escape. Shutting down this loophole is part of the rationale of this proposal. Maybe this is scary to someone who is never disruptive? I dunno. That seems irrational. I edit so widely, as far as I'm concerned I'm aware of all DS and not immune to any of them. I don't go around calling people dickheads, or questioning whether they're editing a page on Himmler because they're crypto-Nazis, or telling them they should screw off, nor do I revert-war in articles, etc. Good for me, good for the project. The only time in recent memory DS was used against me, for a 3-month topic ban, WP:AN overturned it. I'm not terribly afraid of DS. Why is anyone else, unless they're here to start trouble? — SMcCandlish ¢ 😼 03:19, 4 July 2018 (UTC)
          • @SMcCandlish: Alright, I see your point; I'll move to a weak oppose. My tired mind must have added a "want" when I read your reply earlier. I cannot convert to a neutral or support, however, because I do not support editing restrictions in general (outside of blocks, though I believe they should be more restricted in regard to experienced editors because of the lasting stigma). The fewer editors eligible for an editing restriction, the fewer editors can be inappropriately restricted. Unfortunately, I do believe editing restrictions, especially those placed unilaterally, are wrong often enough to be concerned that an automated process would make more people eligible. — Godsy (TALKCONT) 03:38, 4 July 2018 (UTC)
  • Strong support. The problem runs deeper than the proposer describes. Users not only need to be aware of DS before being sanctioned; the evidence of awareness must be from within the last year, while at the same time the DS warnings page asks users not to warn those who have received a warning within the last year. This little mess means that even longstanding editors with low levels of activity may have periods of immunity. To address concerns about scaring away newbies we just need to be careful about the wording. The template already says "It does not imply any misconduct regarding your own contributions to date", and we can be even more explicit; furthermore, if a user is going to be scared away by "you have done nothing wrong but you need to be aware of this", then they are probably not ready to be editing in ARBPIA areas (or wherever). Vanamonde (talk) 03:59, 3 July 2018 (UTC)
  • Support This is the best way to remove the stigma of getting a notice. --Ahecht (TALK
    PAGE
    ) 04:01, 3 July 2018 (UTC)
  • Oppose some tooling is needed, but I don't think more automated messages is necessarily the right answer, and I don't want to endorse a pig in a poke while we don't know what that system will be. As noted above, this will need a lot of work regarding thresholds; the BLP DS specifically are so wide that it's possible no threshold for auto-notification will work. For American Politics, I don't see this as being necessary; disruptive editors on high-profile pages get the notice fairly quickly already. If an editor stops being disruptive without a block being necessary, that's great. For lower-profile DS areas (e.g. Armenia-Azerbaijan), this does nothing to get more admins to patrol the area. A toolserver based "list of editors who might need a DS alert" page may be useful; once that exists there may be more support for automating its usage. power~enwiki (π, ν) 04:57, 3 July 2018 (UTC)
    • @Power~enwiki: This seems to presume that there is some harm in being aware that DS apply to a topic. Someone doing GNOMEy work site-wide probably should be aware of the grand scale of DS, and edit accordingly. I know I do. I presume that DS applies everywhere, and try to be mindful to check the top of the talk page for 1RR and other special restrictions if some unconstructive changes need reverting and aren't obvious anon vandalism. An idea already floated above is that actual new editors (perhaps those not yet autoconfirmed) would be exempt from bot notices. Maybe also have a DS notice opt-out or gnomes (with presumption of awareness). — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
      • As far as ease-of-use improvements, a separate {{ds/reminder}} that is worded to make clear it is a periodic bureaucratic reminder (and can be issued after 11 months instead of having to wait 12) may be helpful now, and would definitely be helpful for a bot or semi-automated system. An official way to allow for voluntary recognition of DS (as I have attempted on my talk page) would also be an improvement. power~enwiki (π, ν) 16:54, 3 July 2018 (UTC)
        Sure. There isn't any reason the auto-notices have to be the same as the current ones; indeed, part of this proposal is to see them changed anyway, to be less menancing, more purely informational. They just need to constitute "official notice". Or we could scrap this "must be made aware" DS condition as silly WP:BUREAUCRACY. It's not actually plausible that someone editing a page with a big DS editnotice and talking on its talk page which has one, too, isn't really aware of the DS. It's a strange fiction of ArbCom that we have to work around, at least for now. If the proposal just got ArbCom to obviate the "awareness" nonsense, then it was successful, just in a different way that actually implementing the notices bot. — SMcCandlish ¢ 😼 17:12, 3 July 2018 (UTC)
  • Support, but further discussion of the implementation should be widely publicized as well Automated notification will remove the stigma of receiving such notices, hence, we can notify for unproblematic edits; even if that is not desirable, the cost of one false positive is not very high. The real drawback is spamming gnomes and other passer-bys (i.e. if we get too many false positives), but the numbers in the implementation can be tweaked to eliminate this (that's where further discussion will be needed); that might set the threshold very high, but if any number of notices gets delivered with that threshold, it is still an improvement over zero. TigraanClick here to contact me 09:43, 3 July 2018 (UTC)
  • Note: The way the Arbitration Committee's discretionary sanctions alerts work is up to the Arbitration Committee, not the community, and people should be aware this discussion can only be advisory. We do have a separation of powers, whether or not SMcCandlish thinks it's "wikilawyerly wrangling" to speak of it. An arbitrator, User:BU Rob 13, has already said so above. There are a handful of community discretionary sanctions, such as WP:CASTE, over which the community does have authority. Perhaps this proposal should be limited to making the alerts for those ds automatic and more user-friendly. Or to advising the committee, of course. Bishonen | talk 09:54, 3 July 2018 (UTC).
    Arghh, that's User:BU Rob13. Very difficult name! bishzilla ROARR!! pocket 10:03, 3 July 2018 (UTC).
    My take: If ArbCom wishes to assert authority here, overriding community consensus, then that authority comes with the responsibility to make the mechanism work effectively. I've seen them discussing the known problems with these alerts, but no solutions have been forthcoming or we wouldn't be here. I would strongly disagree with any assertion that the status quo is the best we (ie they) can do. ―Mandruss  10:13, 3 July 2018 (UTC)
    Personally, I think the mechanism works fine. The fact that editors sometimes react poorly to it seems more a selection issue than a problem with the alert. Editors quick to anger (or who aren’t willing to consider messages from others as coming in good faith) are most likely to get the alerts. ~ Rob13Talk 11:39, 3 July 2018 (UTC)
    It doesn't work fine. Try remembering which editor has received a notice in the past 12 months (as required for DS enforcement) and reconciling that with the fact that you're not supposed to give alerts any more frequently than every 12 months. This --> Wikipedia:Arbitration_Committee/Discretionary_sanctions#Awareness_and_alerts is a bureaucratic mess. Arbcom should either fix it or let us have a bot.- MrX 🖋 15:03, 3 July 2018 (UTC)
    @Bishonen: See already-quoted material above ("The Committee ... does not exist to subvert ..."); there is no such separation of powers; community decisions, including on policy matters (this would be one), cannot be thwarted by ArbCom. And if you actually try to make any separation-of-powers argument in an ArbCom case it'll either be ignored completely or flatly denied (depending on the Arb). I've tried SoP arguments multiple times from a different angle (to end DS being applied to internal policy discussions, because our "judiciary" should not be telling our everyone's-a-legislator "legislature" how we're allowed to formulate policy; we already have community-written behavioral policies and community-operated noticeboards that cover it. — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
    Discretionary sanctions are created by ArbCom. Every sanction placed under them is an arbitration enforcement action. The entirety of the procedures to alert, etc. can be modified only by ArbCom motion. It is not a community policy. ~ Rob13Talk 16:57, 3 July 2018 (UTC)
    This has already been discussed above, BU Rob13. If ArbCom cannot thwart community consensus, it more narrowly cannot thwart community consensus about what it is doing or implementing or failing to do or implement. There isn't any magical loophole in "cannot thwart community consensus". It's a blanket statement, intentionally. — SMcCandlish ¢ 😼 17:14, 3 July 2018 (UTC)
    Except that the Arbitration Committee can override consensus within its scopes and responsibilities. It just cannot create policy by fiat. See WP:CONEXCEPT. ~ Rob13Talk 17:19, 3 July 2018 (UTC)
    You seem to be suggesting that the community is utterly powerless to check-and-balance ArbCom in any way, even with a strong showing of support in a site-wide RfC. I don't think anyone on WP buys that, nor that anyone at WMF does. This attitude just demonstrates exactly why this RfC is needed. See also the first law of holes, and the comments of many in this thread that, procedural quibbles aside, the RfC should at least be taken as advisory. The results so far show that most of those with oppose !votes are either the Arbs themselves, or simply misunderstanding one or more of: the proposal wording, what the notices are/mean, who can use them, what DS is, what bots are capable of, or something else simple and factual. Meanwhile, those who understand these things are in support of the idea, either as laid out or at least in theory/spirit. Pooh-pooh this at your own risk, and especially keep in mind that community faith in both ArbCom and in DS has been steadily decreasing over time. — SMcCandlish ¢ 😼 18:14, 3 July 2018 (UTC)
  • Oppose( I've struck my "oppose" as I still think that this is a matter for Arbcom and !voting might suggest differently - I think this is not a good idea) for a number of reasons. New editors might receive this as the first post on their talk page. For a few that might be a good idea, for most, probably not. DS alerts are signed allowing the person receiving them to ask the person adding it any questions they might have. A bot would be sending out many times the number of alerts that are sent out now, and whose going to answer any questions? We can't expect the help desk or the Tearoom to suddenly take on this workload. People would be automatically receiving alerts in areas where it seems sensible to keep sanctions but where the existing problems are infrequent, and I think that's a bad idea (User:TonyBallioni's point). We have no idea how many alerts would be sent out but I'm sure it would be far more than necessary and that inevitably it would inhibit some editors from editing in the area, or even perhaps editing at all. When all is said and done it's still bitey, and I've seen many editors thinking that a bot notice is from a real person. If the wording can be made friendlier so that no editor responds badly, that would be great but I doubt we can ensure that. I'm all for any suggestions to improve the wording of course. And yes, this area is the Committee's responsibility. I'm sure all of us would welcome more suggestions to improve the use of alerts, but I for one still think that personal alerts are far superior to anything a bot can do. Doug Weller talk 10:43, 3 July 2018 (UTC)
    • @Doug Weller: A bot can refrain from leaving a DS notice as the first post on a talk page. Random editors are not in a position to properly explain DS; that's what WP:AC/DS is for. If topics don't have frequent problems, remove DS from them (DS is for dealing with disruption that ANI can't handle, and ArbCom's short-sightedness about this is practically like an addiction). Why would receiving neutral automated notices inhibit someone more than definitely does the receipt of pointed ones from dispute "enemies" who usually (though wrongly) believe these notices are handy threats they can menace people with? This proposal is not BITEy since part of it is to exclude new users (if the community wants that), though this wasn't spelled out clearly when first posted. Perfect is the enemy of good. ArbCom won't actually take responsibility for it or we wouldn't be here. I've been on every sitting ArbCom's collective ass about the problems with these notices for something like 4 years now, and no action is ever taken. I want to be really clear here: The primary reason I ran for ArbCom last election was to fix DS, because you all won't. (And I got more votes than several of you; you just got fewer opposes because I edit in enough controversial material to have some people who don't like me. In a normal election system, I would be a sitting Arb right now and DS reform would have been under way since January.) If you think the personal alerts are better, it's because you're neither leaving nor receiving them, or you are but seeing this through admin glasses, where the experience of both is markedly different than for an everyday editor. "Adminsplaining"? That should be a word. >;-) — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
  • Oppose per Doug Weller and TonyBallioni. I’d add more (or repeat what they said) but am on a rapidly expiring cellphone. This is well intentioned but too much of a blunt instrument given the number of articles under DS and the importance of nuance in working out which edits might legitimately require a notification and which are off topic or trivial. Some human discretion is necessary here. In passing, it’s suggested that a bot notice would have less aggressive wording - mildly, if there’s a good suggestion for less aggressive wording then let’s adopt it right now. — Euryalus (talk) 11:29, 3 July 2018 (UTC)
    • There is a page for the purpose of "asking for an amendment or extension of existing sanctions": WP:ARCA. (Indeed, I just saw you on that page, SMcCandlish.) Might that be a better place to raise this, Doug Weller and Euryalus? People would be able to add their arguments and opinions just the same as here, and this discussion could also be linked to. Bishonen | talk 11:34, 3 July 2018 (UTC).
      • I suppose. Probably should clarify that there's argument for this being solely in the Committee's area of responsibility to change or keep the same, but meh, I'm perfectly happy with a community debate proceeding here on this issue and us just applying the outcome. I see it as a minor procedural issue either way, and not something integral to the committee's actual Arbitration role. -- Euryalus (talk) 12:07, 3 July 2018 (UTC)
  • Conditional support: As a concept on a limited scale, beginning only with topic areas that receives the highest traffic. I would oppose bot notifications for every DS area. Alex Shih (talk) 12:24, 3 July 2018 (UTC)
  • While I appreciate the idea behind this and am all for people thinking about how to make DS work better, I oppose this proposal as it stands, for several reasons:
    • Firstly, I'm not convinced it's actually solving a real problem. There is not a big problem with editors avoiding sanctions because they are not formally aware of DS. I've just looked through the last ten pages of AE archives, back to the start of March; in that time, three reports were closed because the editors were not formally aware of sanctions. Even in cases where editors do avoid sanctions for lack of awareness, either the experience has the intended effect and they change their ways, or they are back at AE pretty sharpish and sanctioned. Personally I have recently levied a mass topic-ban of ten editors; not one did not meet the awareness criteria.
    • Secondly, a large part of this is outside the community's jurisdiction. I'm not entirely convinced that the community can't establish a bot to hand out these alerts because they need to be done by a real editor (as has been argued above); nonetheless, the form of the alerts is required by arbcom before an editor is sanctioned. So even if the community took it on itself to change {{Ds/alert}}, the only effect would be to make DS more unenforceable, as anyone who had received the modified alert wouldn't count as aware under the awareness requirements. It might well be true that friendlier notifications would be a good thing (and anyone who wants to have a go should create one in their sandbox and inform the arbitration clerks about it) but changes here need to go through the committee.
    • Thirdly, I don't think the practicalities have been thought through, and the difficulties are insurmountable. DS are typically authorised for "pages and edits about <topic X>". "Pages about topic X" is reasonably easy to deal with as has been discussed above through use of talk page notices placing invisible categories. "Edits about X" is much more difficult. They could happen on literally any page anywhere on Wikipedia and be subject to DS. Some obvious cases leap to mind: People asking questions about American politics, or pseudoscientific theories, or Kashmir, or... at the reference desks are subject to DS. Someone who asks several divisive questions about one of these topics would be a prime candidate for the application of DS. In these cases, having a bot to normally distribute these alerts makes formal awareness less likely, not more (unless we're going to spam DS notifications for all possible topics to everyone who edits the WP/WT namespaces). GoldenRing (talk) 12:36, 3 July 2018 (UTC)
      On your first point, I hope you realize there is quite a bit of selection bias in your stats: AE-savvy editors will not report before leaving the notice. The good measure would be how many good cases of AE were not filed because of a lack of notice. And actually, even that is not the whole story - the real measure would be how many AE filings were not made or dismissed because of a lack of notice when the notice would have been made had the bot been in operation. Good luck measuring that, of course. (You might still be correct that there is no problem to fix, but your sampling does not prove anything either way.)
      On the third point, I am not sure I understand. The bot will not be able to notify in the "edit about X" scenario. So what? False positives (e.g. notifying someone who copyedits every page containing {{infobox officeholder}}) are a problem (because spamming), but false negatives are not (as long as editors can still post the notice themselves, it is equivalent to the status quo). TigraanClick here to contact me 13:37, 3 July 2018 (UTC)
      @Tigraan: You're right about selection bias, of course; nonetheless, I don't see lack of notification as a significant problem. If a user is thinking of filing an AE report and realises the editor is not aware, they send on the notification. Either this has the desired effect, or the editor continues on and is at AE a few days later, now fully aware. Regarding the third point, what I mean is that if an editor turns up at the refdesks (for instance) asking those questions, someone will pretty quickly drop the DS template on their TP because it's a process lots of editors are familiar with. Once most editors forget how DS alerts are distributed (beyond "a bot does it") it becomes less likely that the alert will be given in a timely way. The same problem crops up in article space, too; it's possible to make an edit that is covered by DS in vast swathes of articles (I'm tempted to say all articles, but I'm sure there are exceptions) where the main topic isn't obviously related to the DS; consider that any edit containing biographical information about a living person is subject to DS; how will the bot pick out editors making this type of edit?
      The main merit I see in this idea is that a bot notification lacks an obvious target for retaliation. With that thought in mind, what about a bot that delivers alerts to users who have been nominated to receive them? The bot's userpage could have a subpage where you can leave a username and a DS topic code; the bot can deliver the template. This gets around the spamming and false negative/positive problems and takes the heat out of leaving a notification on someone's TP. The bot can also automatically ignore requests that would be a repeat within twelve months. GoldenRing (talk) 15:27, 3 July 2018 (UTC)
      I'd go for that as as second choice, perhaps in a later RfC or something. It would be an improvement of one facet, but miss the overall point, that the purpose of these notices actually has nothing to do with a user's behavior, and is informative, that special rules apply to certain topics. Ultimately, all editors should know this and know what the topics are, at least if they're editing in them actively. — SMcCandlish ¢ 😼 18:25, 3 July 2018 (UTC)
  • Question: Is there any reason not to simply expose every editor who opens a DS page to edit to a banner stating that DS applies? This would notify everybody every time they edit the page, and would be entirely impersonal and always relevant. Cheers, · · · Peter (Southwood) (talk): 14:14, 3 July 2018 (UTC)
    Certain pages under 1RR, such as Donald Trump, display such a notice. We would need a way to log which editors have been notified, since it's likely impossible to add a notice to every DS page. Gun control DS, for example, applies to any gun which has been used in a crime, but only if criminal use is actually included in the article. –dlthewave 14:50, 3 July 2018 (UTC)
    @Dlthewave and Pbsouthwood: This would be one way to do it, but ArbCom has already rejected the idea that editnotices and article talk page notices about DS constitute "awareness". It would be an acceptable outcome of the current proposal if instead of a bot, every DS-covered page produced such an editnotice, and it was considered notice/awareness. Then we would not need to log edits; simply a diff showing an edit at such a page would prove awareness. I've proposed this solution at least twice and ArbCom ignored it or argued against it (depending on the Arb). — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
    Correct me where I am wrong, but as I see it, Arbcom does not make policy, they are the final arbitrators, enforcers and interpreters of policy which is made by the Wikipedia community based on consensus. If this is true, then they have no special say in whether and how the community decides to notify editors that they are editing an article where DS applies, except if they consider that it conflicts with higher policy, terms of use and the like. As volunteers they can indicate their disagreement, and if it is sufficiently strong, resign. As members of the community they can argue against it, and I would expect a high level of reasoning from them, and it may be persuasive, after all they were elected for their demonstrated ability to get to the root of the matter. Nevertheless, I think that the community must make the policy, and arbcom members would be within their remit to abstain from the discussion, which in practice may be indistinguishable from ignoring requests for comment.
    To get back to the point, I think that having notices in the article which display when open to edit may be considered a reliable way of notifying everyone who edits the article. If the notice was there at the time of the edit, the editor may be deemed to have been notified.
    Regarding the identification and tagging of relevant articles: It is not necessary to tag all articles with the banner if it can be added by any autoconfirmed editor, as the same editors who are currently leaving notices on talk pages could with less overall effort, leave a banner in the article, which only needs to be done once, unlike talk page notifications, which must be done for each editor who is to be notified, and every year. Very little surprise is induced, and there is no pointyness or agression implicit in the notice which is directed equally at all editors to the article. This seems less likely to stir up ill feeling than the current or other proposed systems. Cheers, · · · Peter (Southwood) (talk): 18:38, 3 July 2018 (UTC)
    I think that's correct, about ArbCom, as do most other editors. But ArbCom mostly don't seem to think it's correct, which is troubling. They're starting to deny that the community has any say over what they do or how, despite DS itself being the making of policy, and procedures for how and why people can/must notify others is also making policy; it's behavioral and administrative versus content policy. The committee need to re-read WP:ARBPOL, WP:ARBCOM, and related pages.

    The editnotices certainly should be adequate "awareness" – and it would obviate this bot proposal and the whole DS notification and enforcement problem (though Ds/alert might be retained for use when someone seems to need a manual reminder). The problem is that ArbCom keeps rejecting this approach to "awareness" and demanding one-year, user-talk notices that scare people, piss them off, or both.

    Agreed on the banner promulgation. Or ArbCom could make a list of what articles it want under what sanctions. Or whatever. It's not a large problem to solve, from any approach, but a simple WP:AWB job.
    — SMcCandlish ¢ 😼 22:02, 3 July 2018 (UTC)

    Perhaps people are misinterpreting the responses of the arbcom members. I expect them to be cautious, and oppose changes which they believe to be contrary to existing policy, terms of use, and the purposes of the project. Those are things they are expected to do, and were selected to do. I do not think they would oppose a change of policy that would improve the ability of those of us here to build the encyclopaedia to do so more effectively while at the same time making it a more pleasant place to work for people of that mind. This is a testable hypothesis. I would like to test it. Cheers, · · · Peter (Southwood) (talk): 11:10, 4 July 2018 (UTC)
  • Oppose the proposal as it's written. First, like GoldenRing, I'm not convinced that lack of awareness is a significant issue. Second, adding a discretionary sanctions notice to the talk page of every registered editor and IP who has non-trivially edited a BLP? No thanks. --NeilN talk to me 14:40, 3 July 2018 (UTC)
    • However Arbcom should seriously look at dropping the notified-every-year requirement. It's bureaucratic busy-work and not having that requirement in areas covered by various general sanctions hasn't caused any issues as far as I'm aware. --NeilN talk to me 14:49, 3 July 2018 (UTC)
      • @NeilN: I sometimes think so too. But I think we do see this from an AE perspective where everyone is mind-numbingly aware of DS; a user who made a few PIA edits a couple of years ago and got this template-thingy pasted on their TP, and now gets hauled to AE for a 1RR infringement must wonder what on earth is going on and I think the alert is an important protection for these editors. GoldenRing (talk) 15:29, 3 July 2018 (UTC)
  • Probably not allowed. Sounds good in theory, perhaps less good in practice once one considers the alert-spam that will ensue, but in any case my understanding of WP:AC/DS#Alerts would rule this out. That rule provides that "any editor may advise any other editor ...". A bot is not an editor. Any scheme like the one proposed here would need to be cleared first by ArbCom via WP:ARCA. In my view, just doing away with the alert requirement would be better. Sandstein 14:59, 3 July 2018 (UTC)
    @Sandstein: See already-quoted material above ("The Committee ... does not exist to subvert community consensus, ... or to decide matters of editorial or site policy."). The "a bot is not an editor" thing has also already been addressed; bots are side accounts of their human editors, per WP:BOTPOL; they are not some independent entity. Implicit (now made explicit) in this proposal is that if implementation's legalistically invalidated, it should be taken by ArbCom as strongly advisory anyway. "Probably not allowed" can't apply against community advisory input to its own ArbCom. — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
  • Oppose overall - I agree that the status quo isn't ideal, but notifying everyone who edits an article under DS seems like overkill and could be very confusing to newer editors making innocuous edits. That said, support giving ArbCom a clear message that the template needs to be updated and made less scary. -- Ajraddatz (talk) 15:44, 3 July 2018 (UTC)
    • Suggestions for updating the template have been made, and prompts posted a couple of times asking for some response. Let's hope some progress can be made! isaacl (talk) 16:18, 3 July 2018 (UTC)
      And that thread is just one of the times; I and others have raised the issue at ArbCom talk, DS talk, and the DS template talk page, numerous times, with no action. Even, back in the day, getting the template wording changed to stop implying wrongdoing on the part of the recipient took two WP:ARCA cases and over a year; it was like pulling teeth from an allosaurus. ArbCom have been extremely resistant to individual or small-cluster community input on what's wrong with DS. And we were promised another community DS review something like two years ago; never happened. This is a community RfC for a reason. — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
    • @Ajraddatz:, please actually read the proposal. It says nothing remotely like "notifying everyone who makes any edit to an article under DS". — SMcCandlish ¢ 😼 16:47, 3 July 2018 (UTC)
      • I have. New editors typically don't mark edits as minor, and may require multiple edits to make the changes they want. I think this is too big of a hammer for the problem. -- Ajraddatz (talk) 16:50, 3 July 2018 (UTC)
        @Ajraddatz: Several points of discussion have been about excluding new editors from the bot notices; this is now explicitly mentioned in the proposal. Better? — SMcCandlish ¢ 😼 17:31, 3 July 2018 (UTC)
        I still have hesitations, but I also don't know the topic area very well so I'll strike my opposition. I appreciate the work you put in to proposing this. -- Ajraddatz (talk) 19:18, 3 July 2018 (UTC)
  • Oppose I have some sympathy for the idea and my first thought was "why not", but after reading this over and thinking about it, I oppose. The "alert" model not only serves as information for the user, it serves as a double check on the admin - either the admin has to think about, 'how am I going to approach this user and warn, so the bad stuff is cut-off, and the good remains', then actually has to communicate with the editor, or the Admin has to research and think about the history of this editor including what warnings they have received, and whether the boom should be lowered, now. Admins do their best, but a little process thinking break helps. Alanscottwalker (talk) 17:04, 3 July 2018 (UTC)
    • @Alanscottwalker: Please see Template:Ds/alert and WP:AC/DS. This is not an admin template. It's explicitly intended to be left by any editor. It is also not a warning about user behavior, it's a notice that different rules apply to a topic. Nothing more. — SMcCandlish ¢ 😼 17:25, 3 July 2018 (UTC)
      • I was already aware of your argument. Nonetheless, it's admin action that this circuit breaks, and it's admin action that is the teeth behind the alert, no matter how it is worded - it opens the editor to the expanded sole-discretion of another (that is the historical development of why they are called, discretionary). -- Alanscottwalker (talk) 17:33, 3 July 2018 (UTC)
        Elmidae's !vote immediately below this basically gets at it. It doesn't matter if admins are involved somewhere; the point is editors understanding the rules, not who gets to enforce them. — SMcCandlish ¢ 😼 18:30, 3 July 2018 (UTC)
        No. Neither below, nor what you said gets at it. What actually matters is that it is the predicate for expanded sole-power given to 1000s of admins over a particular person, and it functions as a pause, no matter who places it or what it says. Alanscottwalker (talk) 18:46, 3 July 2018 (UTC)
        It can't actually serve that function when most DS/alerts are added by non-admins, which seems to be the case. I've only seen an actual admin leave one a few times, and they were usually doing it not as admins but as WP:INVOLVED participants in the discussion that triggered the desire to post the template. "Drive-by" admin Ds/alert is a rare thing. — SMcCandlish ¢ 😼 22:08, 3 July 2018 (UTC)
I already went over why it serves the function of causing pause even in the case where that admin was not the one to give it in my first post. And the notice is the only built in pause before the admin action. -- Alanscottwalker (talk) 23:02, 3 July 2018 (UTC)
It's not clear to me why you think it matters more to the admin considering action whether the template was delivered by a bot because the editor was editing in that topic area a lot, or because I dropped it off, without comment, for exactly the same reason. — SMcCandlish ¢ 😼 23:42, 3 July 2018 (UTC)
Because when an editor does the alert, the Admin has a built in systematic prompt to investigate and think about, 'why?'. Editor interaction is key, and keyed. There is no why with a bot, the bot just did what it was programmed to do -- leading to, as others note, unthinking programmatic alert litter, and alert litter that is likely to raise alarm and turn-off, no matter how worded, except perhaps in the most experienced, and for them, they will be turned-off by, and resent the littering, itself. In short, if you have a message for me, come tell me what your message is, and we can discuss it, don't tell me I have to take meaning from a bot. The bot's telling me, 'beep, boop', which is meaningless. Either you are serious about alerting me about something you think I am unaware of, or you are not, and a bot can only suggest you're never serious, and that it has no capacity to think about what I need to know. -- Alanscottwalker (talk) 18:15, 5 July 2018 (UTC)
  • Support in combination with making the template look less like a Final Warning Before Summary Execution. If it's made clear that this is merely a heads-up that you are editing in an area with some special rules, then I don't see any downsides. --Elmidae (talk · contribs) 18:05, 3 July 2018 (UTC)
  • Strong support. The template's line "It does not imply any misconduct regarding your own contributions to date" is effectively a lie: that is how the template is used, and of course that's how the template will be interpreted, for naive newbies and irate experienced editors alike, and in neither situation will it calm the situation down. Having a bot neutrally place a simpler and less aggressive message automatically would be a big improvement.
    The wording of the new template and the exact parameters (number of non-trivial edits and time period) are obviously worth debating, but I am confident we would come to a consensus which would avoid the situation where a newbie makes an uncontroversial edit to a page tangentially related to a DS and gets a warning slapped on their talk page. Conditions like adding a welcome message if it's the first edit to their talk would also help this situation. Both of these have been taken into consideration in the very well-thought through proposal, so I am very happy to support it. Bilorv(c)(talk) 19:23, 3 July 2018 (UTC)
  • Oppose In the abstract I support the idea — DS are in place, this is the sort of thing that should be easy to do automatically (see Bellezzasolo's arb.js) — but in practice I'm not sure this is a good idea. For one, even as suggested via minor edits and some well-researched/well-designed limits, this will sweep up a lot of passing editors. That's not inherently a bad thing, except yes, the notice is scary. If I do a double-take whenever I see one, the average editor (new or otherwise) will likely do the same. Yes, the notice should be made less scary, and that's incorporated above, but that's putting the cart before the horse; I wouldn't want to support this until at the very least the notice was less scary. Folks who have never heard of ArbCom but listened to a podcast or caught some breaking news and want to help improve the 'pedia are likely to be most affected or turned off, and that's a problem. Alex Shih's idea of only certain, especially-contentious areas is reasonable, and might be enough to have me change my views here. There will be a lot of questions, and nobody to take responsibility for them. Fully in the realm of the Committee, and they are free to take this if they like, but completely fine if they do not. ~ Amory (utc) 19:47, 3 July 2018 (UTC)
  • Oppose. If anyone wants to discourage new users from editing Wikipedia, this is it. This is really a frightening message. Edit at your own risk and expect what? Consider someone who just started editing and has no idea how DS and administrative noticeboards work. Few to none users are sanctioned each year in most areas covered by DS. In other subject areas (like Eastern Europe), 95% contributors have no trouble and will hardly ever appear at WP:AE. Areas like ARBPIA or Syrian war? Yes, maybe. Try this in ABPIA and see what happens. But I strongly doubt this is going to help. My very best wishes (talk) 19:53, 3 July 2018 (UTC)
  • Oppose. While I sympathize with the proposal, I think it can be easy for experienced editors to fail to appreciate the discouraging effect that any kind of warning can have on newcomers. Even if it is well worded, I think it is still very likely to make some editors fear they have done something wrong or are perhaps getting close to doing something wrong. And even for those who don't take it that way, it can still make them wary of editing in the affected area, and we should not be discouraging newcomers. I think the only people who need to be alerted of DS sanctions are those who appear to be in danger of breaching them. Good editors working constructively in a DS-affected area have no need to even know about them. Boing! said Zebedee (talk) 21:05, 3 July 2018 (UTC)
    So why do thousands of pages and their talk pages have DS editnotices and banners? Can you show that these are driving editors away? The only reason this proposal exists is that ArbCom illogically refuses to accept those notices as "awareness", only user talk page ones. We can't have it both ways. Something has to give, in the direction of WP:Common sense, one way or another. — SMcCandlish ¢ 😼 22:23, 3 July 2018 (UTC)
    I'm sure you understand perfectly well that there's a big difference between an alert on an article talk page and on a user talk page, and that we should be far more careful with the latter (which can overflow into apparent biting where the former does not). Also, I honestly don't think that badgering every opposer (while continuously banging on about an apparent grievance with ArbCom) is doing you any favours. Boing! said Zebedee (talk) 04:53, 4 July 2018 (UTC)
    It's not a difference that's easy to define, and it may have more to do with the wording of the template. People almost invariably react much more negatively to a Ds/alert than they do to other process-mandatory templates like {{Uw-3rr}}, {{ANI-notice}}, {{Socksuspectnotice}}, etc. Why is that? I've addressed your "badgering" accusation elsewhere [46]. Noting that old process hasn't been working and opening an RfC instead isn't a "grievance", it's moving past the roadblock to get stuff done. — SMcCandlish ¢ 😼 20:30, 4 July 2018 (UTC)
  • Strong oppose because it is not possible to algorithmically determine which edits are and are not a substantive interaction with the content of a page. New page patrollers, copyeditors, those who perform similar gnomish edits, and those doing admin tasks on an article (edit requests, XfD implementations, oversight, reverting vandalism, etc) will inevitably just get spammed with notices for pretty much every topic that's under DS sooner or later. These notices will just be ignored as spam, and so despite having received a notice they will not actually be aware. The separate problems of biting new users is also a showstopper - as well explained by others. This is not the first time automatic delivery has been proposed (it comes up quite regularly when arbcom discusses the DS system in any way) and these problems have been raised every time, yet there is still no evidence that anyone in favour of the proposal has even put much thought into them, let alone come up with practical and workable solutions to them that wont themselves cause other issues. Finally I'm sceptical that the problem the OP on this occasion intends to solve is actually a problem that needs solving. Thryduulf (talk) 21:16, 3 July 2018 (UTC)
    This and most other opposes are predicated on the idea that Ds/alert is a warning for bad behavior, when ArbCom has repeatedly disavowed this interpretation and insisted they are just notices that different rules apply to the topic area in question. How is awareness of this fact a harm to the editor – new, gnoming, or deeply involved? And what biting of new users? An explicit part of the proposal is excluding new editors from the notices. It looks like you're responding to your idea of what is proposed based on memory of what someone else once proposed, rather than on what is actually proposed now. The fact that ArbCom keeps ignoring community input about DS and its problems just because it's kinda hard doesn't mean that ArbCom is right, it means they need to listen. (Especially given the frequency with which they're poised to sanction editors for not listing to the community input of other editors. There is no "I'm an Arb, ergo immune to IDHT" clause.) The raising of a technical challenge does not mean the challenge is insurmountable, nor that it must be surmounted with absolute perfection. — SMcCandlish ¢ 😼 22:20, 3 July 2018 (UTC)
  • Support variant During the last review (2013 I think) a major goal was to reduce BATTLE mentality is passing these things out. Some argued then that the only way to achieve that goal was UBIQUITY... make sure everyone gets them. Opposes here generally group into (A) false belief they are still about warning for bad behavior, (B) ignoring the skills of our bot-filter programmers some argue it would would create oceans of spam for trivial or gnomish edits, (C) some correctly point out that some articles are obviously in the topic area ("global warming" falls under WP:ARBCC but its hard to realize a section under Al Gore might as well) but those commenters ignore the nunace that the notice can still manually be given when a circumstance inspires someone to provide it, and (D) Doug Weller (talk · contribs) adds the important observation that new comers will be put off. To address Doug's concern, I would add a time-period factor to the filter, maybe topic edits 5 days apart in a 30 day period or something. Editors who suddenly make a big splash over three days can still be given the notice manually if anyone wants. And to protect regulars from annoyance create the opt-out "Alright already, I know! I know!" suggested by OP SMcCandlish (talk · contribs). Finally I suppose some may try to game the system by marking nonminor edits as minor, but that's easy to deal with. Finally, observation I think the main reason the DS system is perceived as dysfunctional is that it was originally invented to "solve" the dysfunction with regular enforcment and regular sanctions at ANI. I doubt we can legislate our way around what is, at its root, a cultural problem. But we can make it incrementally better. The original goal in converting the old for-cause WARNING into a new no-fault FYI was to reduce BATTLE attitude. The best way to do that is to "fix" regular enforcment, and the least bad alternatives is to make these FYIs ubiquitous. NewsAndEventsGuy (talk) 08:10, 4 July 2018 (UTC)
    • ANOTHER TWEAK, Create an opt-in "HandHolder" service..... for any topic area, invite editors to volunteer to be the desinated go-to editor(s) when people get a notice and have questions. Design the notice to steer them to these volunteers. Tell the bot to run only when there are volunteers to receive such inquiries. Needs a reporting system so people whos questions go unanswered have a recourse. NewsAndEventsGuy (talk) 08:19, 4 July 2018 (UTC)
      • @NewsAndEventsGuy: Would this really bring more value than just pointing to general help forums, i.e. the Help Desk and/or the Teahouse? Folks there can explain what DS are, even if not the precise delimitations of each DS topic area. TigraanClick here to contact me 08:37, 4 July 2018 (UTC)
        • @Tigraan: Up above, Doug Weller (talk · contribs) correctly points out that applying the bot to all areas would create a spike in negative reactions, and Doug said We can't expect the help desk or the Tearoom to suddenly take on this workload. I agree with Doug that it would create a problem from those folks. By recruiting interested topic area "HandHolders" who optin ahead of time, that particular problem goes away NewsAndEventsGuy (talk) 10:19, 4 July 2018 (UTC)
          • @NewsAndEventsGuy: Three points.
            1. I am not convinced by DougWeller's argument that We can't expect the help desk or the [Teahouse] to suddenly take on this workload [of angry notified editors]. Is there evidence that it would swamp other queries, or is that just speculation? Weak evidence from a recent similar experience makes me think it would not be a problem: a couple of months ago, article creation was disallowed for non-autoconfirmed editors, who now have to go through WP:AFC instead. I do not know how much burden this added to AFC reviewers, but as a regular Teahouse respondent, I can say we are not drowning in AFC-related questions; maybe the number increased, but by no way does it swamp the TH. We are talking about 150 to 200 AfC submissions per day, most of those being as many unique editors. Let's say that editors notified for DS are three times as likely to go to the designated help forum than AfC submitters; a similar level of "flooding" would be reached with 50 DS notifications per day. Does that look like a realistic number? (I suspect not, though I really do not know.)
            2. Assume for the sake of the argument that there would be so large number of daily DS complaints/questions, that it could not be managed on the HD/TH (I would say the order of magnitude would be at least 20/day.) Do you really think a new process ("HandHolders") would absorb that number of queries smoothly? Said otherwise, if the established TH/HD that run relatively well cannot handle it, I doubt you can easily set up something that can. Many of Wikipedia's stalled processes would run well if only we could recruit interested topic area specialists, but the thing is that's hard.
            3. Same assumption, and let's say that above N notifications per day, the TH/HD get swamped by angry DS-notified editors. Easy solution: set up the bot to send at most N or N/2 or something notifications per day. In that case the bot will not solve the problem, but it will still be helpful: I have a very hard time believing that number would be below 100/day, and even 10/day would be well enough to justify a bot. You can tweak the numbers, but there will pretty much always be an intermediate area between "bot does nothing and is useless" and "bot sends numerous crowds to storm help forums".
          What I am trying to say here is that your argument rests on unspecified numbers and I strongly suspect your implicit assumptions on those numbers are wrong. I am ready to change my mind if you have evidence to provide, of course. Qualitative arguments could be made (e.g. that TH/HD respondents are not qualified enough to handle specific DS questions, or that notified editors would be very angry and break the TH friendly atmosphere) but the quantitative one seems dubious to me. TigraanClick here to contact me 12:15, 4 July 2018 (UTC)
          • Keeping a volunteer base engaged is a very difficult task. I think it will be easier to keep Teahouse participants involved with explaining discretionary sanctions than to keep a separate volunteer group active to just explain discretionary sanctions. isaacl (talk) 14:50, 5 July 2018 (UTC)
    @NewsAndEventsGuy: I've added both of these ideas to the list of potential implementation details in the RfC text. You have correctly divined that the inspiration for the RfC goes back to the 2013 community review of DS (and what that review did not fix, and the same community sense that these should not be handed out as threats/warnings but evenly). I just didn't want to mire the proposal in old news; wading through that material could take someone hours. — SMcCandlish ¢ 😼 20:39, 4 July 2018 (UTC)
  • Oppose. There are vast topic areas that fall under the DS regime, and within them there are huge number of editord that make a large number of problematic edits, but only a fraction of those editors get dragged to WP:AE, and that's a good thing: this procedure is meant to be used when everything else has failed. Yes, the way they're currently issued (typically between editors who are annoyed at each other after not getting along in the discussions), the DS alerts are usually pretty hostile, but that is a side effect of them being a sort of last resort. If everyone got the alerts, then the message would get diluted. And I'm not comfortable with the idea of new editors getting exposed to the DS system from step one: raising awareness is generally not a bad thing, but here this might deter cautious editors from contributing to articles and it might encourage others to go straight for AE level litigation instead of first trying to discuss things on the talk pages. Also, the implementation issues are not minor at all: 1) how will the bot select the articles? Because the vast majority of articles under DS are not tagged in any way, the bot will be of limited use unless significant editor time gets syphoned into tagging the articles; 2) how will the bot select the editors to warn? This is not as staightforward as it seems: take reverts for example, how will the bot tell if it's the routine everyday reverting of vandalism and test edits or the persistent POV reverts without which a large portion of existing sanctions wouldn't have been imposed? – Uanfala (talk) 19:47, 4 July 2018 (UTC)
    @Uanfala: The reason ArbCom created DS was to enable admins to just deal with disruption on the fly using their own judgement about certain classes of clearly disruptive behavior; that's why it's called discretionary. We have all this AE bureaucra-drama because they're not really doing that. If more editors were subject to DS and DS were applied more routinely to the disruption, that might be resolved. The proposal has no effect on the problem you describe, pro or con, otherwise. It does however, specifically call for working out how to not BITE new editors with auto-delivered DS alerts; so it seems rather strange that "new editors getting exposed to the DS system from step one" is your primary oppose rationale. Did you read detailed version, or just the summary?

    To answer your questions: 1) the bot would select articles on the basis of them being categorized as DS articles by the presence of DS templates or perhaps just by directly detecting the templates. The fact that many DS-covered articles aren't tagged yet is an WP:AWB job (and should get done anyway). Even if it didn't get done, that wouldn't affect the utility of the proposal; its coverage would simply be incomplete, while it would remain better than nothing. (There are also sections, even sentences, that are technically covered by DS, in larger articles that are not as a whole, but that's too fine-grained a thing to automate, or even for most human editors to figure out. This proposal isn't meant to be some kind of year 2118 AI, ha ha. Just to work well enough for our purposes.) 2) They're not warnings, they're notices that different rules apply to the topic. Editors would receive the alerts based on frequency of editing at pages subject to DS, as mentioned in the proposal. The exact specifics of that would be determined in a later discussion. Anti-vandalism edits are typically detectable by a number of means, including tool-created edit summaries, being reverts of recent changes by anons or new accounts, and so on. And we could just exclude all small edits. Detection would not be perfect, but there is no harm in a vandal-fighting editor being simply made aware of DS at a topic, anyway. It's not like our vandalism fighters at American politics pages are the trolls over at Israel/Palestine disputes! I hope this addresses your concerns.
    — SMcCandlish ¢ 😼 02:23, 5 July 2018 (UTC)

  • Oppose I have not seen sufficient evidence that it is necessary, and in particular that it won't cause more harm than good, especially given the multiple concerns noted by people above. I'd note that the 'side benefits' are sometimes of limited relevance. For example, if people see the notification as coming across too harsh, i