Wikipedia:Village pump (idea lab)/Archive 27

Village pump
- Policy
- Technical
- Proposals (persistent)
- Idea lab
- WMF
- Miscellaneous

Village pump (idea lab) archive

This page contains discussions that have been archived from Village pump (idea lab). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

< Older discussions · Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56

Sandbox page for ips

hello im a ip editor and i want my own sandbox 58.9.138.7 (talk) 03:25, 4 November 2018 (UTC)

You can use Wikipedia:Sandbox. Hddty. (talk) 10:36, 4 November 2018 (UTC)

And if you want a sandbox entirely of your own, you could go a bit obliquely and for example create a subpage of your talk page, say User talk:58.9.138.7/Sandbox. – Uanfala (talk) 13:14, 4 November 2018 (UTC)

Obvious answer: create and use a username! Martin of Sheffield (talk) 15:29, 4 November 2018 (UTC)

Let a Bot delete user subpages

Since you cannot directly delete your own subpages, how about we let a bot – who is Administrator – delete user subpages that have been requested to be (speedy) deleted by their user? Colonestarrice (talk) 23:00, 21 October 2018 (UTC)

Of anything in CAT:CSD Category:Candidates_for_speedy_deletion_by_user is almost never backlogged. — xaosflux ^Talk 23:14, 21 October 2018 (UTC)

Oopsie. I can page-move the entire village pump to my own subpage space, and tag it for immediate bot-deletion :) Alsee (talk) 19:08, 25 October 2018 (UTC)

The village pumps are move protected so you can't actually Galobtter (pingó mió) 19:13, 25 October 2018 (UTC)

Good point... the village pump is a bad example, but many other pages could be disrupted in that way. Andrewa (talk) 03:29, 5 November 2018 (UTC)

Open call for Project Grants

Greetings! The Project Grants program is accepting proposals until November 30 to fund both experimental and proven ideas such as research, offline outreach (including editathon series, workshops, etc), online organizing (including contests), or providing other support for community building for Wikimedia projects.

We offer the following resources to help you plan your project and complete a grant proposal:

Also accepting candidates to join the Project Grants Committee through November 15.

With thanks, I JethroBT (WMF) 19:46, 5 November 2018 (UTC)

Degradation of Sociology Related Pages - Recommend Mass Protection Upgrades

In an attempt to broaden my horizons, and better understand the unusual current political climate in the United States, I've been reviewing the always contentious sociology articles to determine what I should know about the current sociological literature.

I had wished that the pop sociology, like pop science was just shallow and poorly thought out, but this seems to be a pandemic in the sociology articles particularly Any article ending in the word Feminism, Sexism or Privilege. Of course we should expect edit wars in these sections, the topics are inflammatory, the debate is heated, and frankly the literature seems a little incoherent(I'm used to nice measureable empirical STEM topics).

There are so many issues in these article not least of which include:

Example farms: The article white privilege seems to have a wiktionary like seciton
Over quoting: This is common when people want to be weasels, and make their statements seem credible, they just stick them near a quote which sounds vaguely similar
Focusing on recent events, instead of citing long standing secondary sources. This is in particular a side effect of the explosion of political unrest and rape allegations in the US.
Accusation of bias on either side when wikipedia is just supposed to report what non primary sources have said.
Nonsense placed right in the middle of the article, buy users that probably would not edit if the article were even semi-protected.

In particular the current political polarization specifically in the United States seems to be negatively affecting the edit quality of these articles.

I recently had some anonymous user revert an edit in which I removed a paragraph which did not have a <ref> but did refer to an article by an author neither of which I could determine to have ever existed, despite the fact that it was apparently published only 4 years ago. The editor in question, left some barely coherent edit summary "found references, this is user opinion of ethanpet to counter published research to fit an anti perspective.", when indeed I am simply enforcing Wikipedia's policy of not putting huge unverifiable paragraphs in the middle of an article. The revision in question is:

https://en.wikipedia.org/w/index.php?title=Social_privilege&oldid=prev&diff=865240125&diffmode=source

You'll see the paragraph looks like it was computer generated.

For this reason I recommend a temporary broad spectrum edit protection on such articles until they can be stabilized, or they are unlikely to reach a point where they are good articles. Sure once they're good articles we can revert sloppy uncited cor copypasta paragraphs, but at the moment this seems to make up the majority of the material.

To get an idea of what I mean, just start at Feminism or Sexism, and start looking through the see also section, and other linked items in the category or infobox

I know we can never prevent bad actors or just poor wikipedians from degrading the quality of articles. But I think some administrator review might be necessary to stem the tide, and I'm not sure it would be appropriate for me to just go protection request bombing the entire project.

Ethanpet113 (talk) 10:40, 26 October 2018 (UTC)

I would suggest, if you're really trying to broaden your horizons, perhaps you should start by not assuming that there are no sociologists working on sociology articles. And also by not spamming dozens of tags when there's only one problem section in an article. Simonm223 (talk) 18:18, 26 October 2018 (UTC)

Oppose any mass edit protection of articles related to race and gender, and suggest, after looking at the proposer's edit history that this suggestion is somewhat tendentious Simonm223 (talk) 15:31, 29 October 2018 (UTC)
Oppose We don't lock down pages because they happen to accumulate unclear writing. We also don't insinuate that editors contribute the way they do because they are mentally ill. XOR'easter (talk) 14:24, 30 October 2018 (UTC)

Page size on Feminism is 153 kB, page size on Sexism is 183 kB. Personally, I think these longer pages suffer from the kitchen sink syndrome. That's why I just suggested in a different thread to just put a hard cap on page size to 60-80 kB. Seahawk01 (talk) 05:21, 6 November 2018 (UTC)

Set hard cap on page size to help combat hot-button issue page explosion

Hello, I would like to suggest setting a hard cap on page size. Perhaps 50 - 60 kB. I am noticing a lot of pages that deal with hot-button issues just explode with no common thread into a mishmash of sections that don't really relate to each other. Then, how can someone edit that? And, also, there doesn't seem to be a lot of people that are interested in bringing order to these pages.

Two examples would be Economic inequality and Affordable housing.

Now, on the other hand, there are excellent articles that are over the suggested 40 kB. For example Fourth Amendment. But, I could point to a lot of very important Fourth Amendment related pages that are truly neglected like Terry stop. So, maybe, clustering all that high-powered editing talent in those select, high-profile pages starves other pages of attention.

In addition, I would like to suggest a purge of all class C pages. Maybe issue a one month warning. Then, if the pages don't shape up, mask them and only allow editors to view until they at least make a grade B.

I like Wikipedia and have used it for a long time. But, I feel a bit sad that such important topics like "economic inequality" and "affordable housing", which are so important to our society, and are ranked #1 on Google, are such a mess. So, I think Wikipedia should really make an effort to provide valuable, well-thought-out articles on these issues.

Thanks Seahawk01 (talk) 03:50, 2 November 2018 (UTC)

One more suggestion, re: grade C pages...why not put a letter grade right on the front of the page for everyone to see like Los Angeles does with restaurants. Seahawk01 (talk) 04:00, 2 November 2018 (UTC)

Seahawk01, I think you've already identified the main problem with your idea, some pages just need to be longer. Maybe a better idea is automatically adding large articles below a certain grade to a category to allow them to be reviewed? (forgive me if this already exists) Since if an article is FA or GA, we don't care that it is very long because it is obviously for a reason. zchrykng (talk) 04:54, 2 November 2018 (UTC)

Hi zchrykng, well, I agree...some pages just want to be long. I just saw Netherlands which looks great and I have no complaints! I guess my problem is I feel some pages just ought to be removed...grade C pages on important issues doesn't really look good. Economic inequality gets 1000 page views a day. That's 1000 people a day that get to see everyone's Econ 101 pet theory and no really coherent structure. Ah well, parts of Wikipedia I love, parts I hate :-) Seahawk01 (talk) 05:09, 2 November 2018 (UTC)

Seahawk01, yeah... I just don't think deletion/masking is a good solution to the problem. The fewer people who can see articles the fewer people who might be able to make improvements. And if someone comes here and can't find an article on what they are looking for they might decide to start a draft on that subject when the article already exists, but was hidden. I do totally agree that there is a lot of junk out there, but I don't think sweeping it under the rug is the best idea, better to put it out in the sunlight to get sterilized. :) zchrykng (talk) 05:18, 2 November 2018 (UTC)

Zchrykng, how about the rating idea? Los Angeles and New York City require that restaurants put a large letter grade in their window from the Health Department. The idea is to shame people into complying...so same idea here...put a large letter grade on the page...Economic inequality gets a large C on the front and Fourth Amendment gets a large A. Seahawk01 (talk) 05:27, 2 November 2018 (UTC)

Seahawk01, that could work. My worry would be about people using it as one more way to try to game the system. If there could be a way to protect against that, I could see it working. zchrykng (talk) 05:36, 2 November 2018 (UTC)

Zchrykng, I see, it's a tough problem since Wikipedia is so large. I've encountered the same with people leaving warnings on top of pages they don't like. Well, I'll put a little more thought into it and come back with a better proposal :-) Thanks for taking the time to hash this out with me! Seahawk01 (talk) 05:50, 2 November 2018 (UTC)

@Seahawk01: there is a gadget that lets you see the quality assessment under the page title. You obviously have to be logged in for this, though. Daß Wölf 22:39, 3 November 2018 (UTC)

@Daß Wölf: very nice, thanks for pointing this out! Seahawk01 (talk) 05:41, 6 November 2018 (UTC)

Class C pages

I've hived this off into a subpage since you suggestion "In addition ... least make a grade B" doesn't have much to do with over-long pages. There are a lot of class C and start class pages that are stubs and ought to remain as such. For instance consider Joseph Jones (trade unionist) which I would suggest is about the right length for someone who was notable but is hardly worth a GA or FA length article. Perhaps the existing crude classification needs some thought. Stub articles are valuable, calling one a stub should not be regarded as dismissive. Short articles will never climb the class scale, perhaps the criteria need to be adjusted so that a good stub or short article could be regarded as C = "complete" rather that C = "third rate". Martin of Sheffield (talk) 23:07, 3 November 2018 (UTC)

No comment about Jones but there has been a trend this year to award GA to shorter articles for which the broad coverage of a topic still ends up being short, so GA length might not be as long as one would think. Best, Barkeep49 (talk) 06:15, 5 November 2018 (UTC)

I would agree with this. A nice, short article that acts as a supporting article to some other topic definitely has a place in an encyclopedia. Seahawk01 (talk) 05:14, 6 November 2018 (UTC)

Suggest big, yellow "very long" notice on edit page of long articles

I'm going to throw in another suggestion. Just like semi-locked pages have a warning, why not put a big, yellow "very long, please consider splitting, consolidating or placing info on more appropriate page" notice on top of the edit page for pages longer than 60-80 kB. That way, people will notice when they try to edit a page, that they are adding to something that is probably too big to begin with. Seahawk01 (talk) 05:28, 6 November 2018 (UTC)

Template:Very long GMG ^talk 11:45, 6 November 2018 (UTC)

@GreenMeansGo:, yes, that's a good template. But, my suggestion is to put that on the editing page, above the textbox where you enter text, so people see it when they are about to add more to an already too long page. Seahawk01 (talk) 00:13, 7 November 2018 (UTC)

Use article title for cities, etc., in within infoboxes

I would like to test the water for a potential proposal for a guideline change. What are the arguments for and against? How much support is there? Has the idea been given a thorough hearing before? If so, can anybody locate those discussion(s) without too much effort?

POTENTIALLY PROPOSED: Unless there is a local consensus to deviate, the names of neighborhoods, villages, towns, cities, etc. in infoboxes should be shown as per the title of the corresponding article. Honolulu, not Honolulu, Hawaii, not Honolulu, Hawaii, U.S.. Prace, Czech Republic. Maidstone, but Egerton, Kent. Et cetera.

It goes without saying that such a guideline would save a ton of discussion. My question is whether that editor time is justified, or whether the article title would suffice in most cases. The guideline would also improve consistency and coherence in location references by providing a single way to refer to each location. ―Mandruss ☎ 13:36, 6 November 2018 (UTC)

Why not? It seems easy enough. Something similar is done in {{Infobox person}}, where the infobox name defaults to the page title. No objection ProgrammingGeek^talktome 19:59, 6 November 2018 (UTC)

The infobox name already defaults to the page title. The suggestion is to require local consensus to change it, e.g. to display "Honolulu, Hawaii" in Honolulu, or display "Egerton" in Egerton, Kent. I oppose. A comma-separated name like Egerton, Kent is often made due to a need for disambiguation. The infobox title has no such need. I don't know of any situation where disambiguation in the page title is recommended to be used anywhere in the article content. If other Kent villages don't say ", Kent" in the infobox then why should Egerton just because there are other things called Egerton? PrimeHunter (talk) 21:54, 6 November 2018 (UTC)

@PrimeHunter: I guess I was unclear. The proposal would apply to location names within infoboxes, such as places of birth. I have attempted to make the section heading more clear. ―Mandruss ☎ 05:08, 7 November 2018 (UTC)

I think it's a bad idea to create any sort of default rule for this. Certainly, sometimes disambiguation is overkill, London, Greater London, Home Counties, England, Great Britain, United Kingdom, Europe, Earth, Solar System, Milky Way, Local Group, Universe is certainly unneeded, London would suffice. However, on the counter argument, sometimes additional context is needed for place names. Take a hypothetical Ontario politician who was born in London, UK but spent most of his life in Ontario politics; certainly if his infobox just said "London", it may confuse readers because London, Ontario is a different place, and so in that sort of case we may want to specify even though the article on the UK city doesn't have any disambiguator in the title; an article about an Ontario person may lead a reader to think of "London" as the Ontario city. There's many different reasons I can find to want to have the city name in the infobox be different from the article title, so much so that any policy to that effect would make a significant number of articles less useful for readers, rather than more. --Jayron 32 13:30, 8 November 2018 (UTC)

Articles which ask a question

The idea is of the approaching of topics by asking a question in the title and then dealing with that question in the article. It at first might seem unsettling, but its been done once or twice, and I'm asking here for opinions on the idea as a general approach to at least list the "big questions" out there, and then do the article. Your thoughts? -Inowen (nlfte) 04:31, 28 October 2018 (UTC)

Could you (or anyone else) give examples of the once or twice? Nosebagbear (talk) 10:00, 28 October 2018 (UTC)

There was a similar question regarding section headings asked; I'd say there was a general concern voiced there with only one user supporting the notion (the one who started the discussion). I was most definitely one of the ones concerned with the idea. --Izno (talk) 16:22, 28 October 2018 (UTC)

@Nosebagbear: The one example I know of, others may know more, is Who is a Jew?, which has been around since late 2004 [1]. The idea is that some questions like that one are perennial and can be treated as entities in their own right. -Inowen (nlfte) 22:40, 28 October 2018 (UTC) PS: It gets into the problem of allowing too many questions, then the questions list can be pruned down. This isn't a question answer site, at least not in that way, but some questions stand out. -Inowen (nlfte)

I have no problem with it and indeed Who is a Jew? is a good example. History is full of perennial questions that are the subject of books, papers. What caused the Roman Empire to Collapse? For professional historians asking good questions is an important part of the craft. But if the article is framed as a question seems besides the point, it might be framed as a theory such as great man theory, which might also be framed as a question ("Is history driven by individuals or society?"). Or it might be a commonly recognized phrase Decline and Fall of the Roman Empire. Depends on the historiographic tradition. -- GreenC 23:06, 28 October 2018 (UTC)

Is this about whether article titles should ask questions? I do not think that would be a very good idea - paper encyclopedias are not likely to have article titles which ask questions. Vorbee (talk) 20:18, 1 November 2018 (UTC)

Big questions. How did life begin? Is there a God? How did water form? What created air? Why is the sky blue? These are simple and perennial. -Inowen (nlfte) 22:18, 1 November 2018 (UTC)

Yup. Why is the sky blue? (Enclopedia Britannica) has a bunch of questions. Although these are not proper encyclopedia articles but a series of essays called Demystified. A genre of article we might consider, probably hostable on Wikibooks. -- GreenC 22:50, 1 November 2018 (UTC)

I would be more inclined to make such titles redirects to articles about the subject of the question, unless the question itself is the subject of the article. zchrykng (talk) 02:28, 2 November 2018 (UTC)

I agree these could get out of hand, but I suggest that keeping a centralized list of articles (and maybe sections) which are in the question form is easy to do, and that the number of such questions be limited, not unlimited. -Inowen (nlfte) 22:56, 2 November 2018 (UTC)

How would you limit them? Vorbee (talk) 16:53, 3 November 2018 (UTC)

Thanks for the question. I would just go ahead and start the Big questions article as a list (done!), and do as a good a job as possible at listing the very biggest questions, and putting them in a sensible order, such that other questions will have to come later. Pruning from the bottom up is a lot easier than pruning from various rows in the middle. -Inowen (nlfte) 04:46, 11 November 2018 (UTC)

Thank you, Vorbee (talk) 09:12, 11 November 2018 (UTC)

Automatic United States Congressional Election updates via API driven bots

I've noticed that quite a lot of Wikipedia pages for Us Congressional Districts are out of date missing 2016 results. Two examples that I updated earlier today include the Colorado's 1st congressional districtand Colorado's 4th congressional district. This strikes me as quite surprising as given the existence of election resultAPI's. It would be fairly trivial to code a bot that automatically generates infoboxes containing such information and add them to the appropriate page. I'm myself a rather poor self-taught scripter with no experience creating wiki-bots but am willing to help code part of the bot if somebody is willing to perhaps help me with the wiki part of the bot. Zubin12 (talk) 04:12, 11 November 2018 (UTC)

Partial blocks and bans

Moved from Wikipedia:Village pump (policy)

Many of you are aware that the blocking system will get a major overhaul with the introduction of "partial blocks" (see Wikipedia:Community health initiative on English Wikipedia/Per-user page, namespace, and upload blocking). Partial blocks will fundamentally change how policies are enforced. Assuming that blocks remain preventative rather than punitive, I think partial blocks have the potential to make current enforcement policies obsolete.

For example, currently a topic-banned user is only blocked when they breach the ban. But with partial blocks, the user can simply be blocked from editing relevant pages upon the ban being enacted. This can potentially result in blocks and bans becoming practically synonymous.

I am not quite sure how our current procedures will change as a result of partial blocks. I personally feel that we could eventually merge blocks and bans together with this new system. But that's just what I think. funplussmart (talk) 20:00, 9 November 2018 (UTC)

This board is not for musing. It is for proposing changes to policies/guidelines.--Bbb23 (talk) 01:11, 10 November 2018 (UTC)

Category blocks will (thank god) not be implemented on en.wiki yet, even when article blocks are rolled out, and there would need to be a policy change when it’s technically feasible because of the major implications category blocks would have (it would transfer de facto blocking ability to non-admins).

Just because we have the technical ability to do something does not drive a policy change, especially when the technical change is a decade old dream that no one has bothered to rethink to see if it’s still a good idea. TonyBallioni (talk) 01:18, 10 November 2018 (UTC)

Sure, partial blocks and category blocks will be great. We should’ve had them put in in the first place. I thought the Village Pump was the best place to bring up my thoughts on how it will affect the banning policy.

And Tony brought up something I didn’t think about: category blocks are affected by additions and removals from the relevant category, giving non-admins the ability to control the pages a user is blocked from. funplussmart (talk) 03:46, 10 November 2018 (UTC)

My point was that this will be a terrible change to Wikipedia and that admins should avoid placing them because of the chaos it will unleash (I will not place a single one), but like everyone else here has said, this isn’t the place for musing. TonyBallioni (talk) 19:29, 10 November 2018 (UTC)

@TonyBallioni:, suppose you see two unblockables edit-warring with one another over a single page that attracts a fair amount of edits .

Blocking would mean an inevitable drama-fest whilst sysop-protection would result in a disability for the mere mortals of the wiki.

I tend to think that a single-page block for both of them will be preferable than either:-) ∯WBG^converse 11:39, 11 November 2018 (UTC)

I agree, though, that Category block is pure BS, unless we radically redefine how categories are maintained and manipulated. ∯WBG^converse 11:41, 11 November 2018 (UTC)

I have opinions on this, but it still belongs in Village Pump Ideas not here, at this point Nosebagbear (talk) 19:01, 10 November 2018 (UTC)

I am all in favour of article bans - I think it would encourage narrower bans/blocks and would work well. Even in a TBAN it would probably make sense to place article blocks on the actual pages that caused the problem.

I am wildly against category bans - and this point would hold up even if the "non-admins can change categories and thus blocks" issue didn't exist. Categories are broad, varied, non-coordinated, frequently poorly created. A proposal to use them would have to demonstrate how the issues of using them were outweighed by the benefits, and I don't think it does. Does someone have a reasonable case - it would seem fairly crucial to any future proposal? Nosebagbear (talk) 21:17, 10 November 2018 (UTC)

Category bans: If this feature can be constrained to particular categories, there's a way to make it useful: hidden special categories, which are only permitted to be applied by an admin (on pain of a block or something), which correspond to ArbCom cases that address particular topics (and maybe other ones, like topic bans created at AE or ANI). If someone's topic banned from, say, "mathematics and statistics" articles, an admin-operated bot could add all articles in those content categories to a new ban-tracking category that combined them (maybe something with a code number, so it's opaque to readers who see hidden categories). — SMcCandlish ☏ ¢ 😼 10:40, 11 November 2018 (UTC)

need push on improving social issues pages

Hello, I'd like to suggest a push to improve social issues pages. Maybe select 100 core issues and 100-500 recent events and try to get every page to WP:GOOD level. I am suggesting this because I am encountering so many pages I think really should present the public with solid, well thought out information that are a mishmash of ideas, are 4-6 times the recommended page size (WP:SPLIT) and have no idea about summary style (WP:SUMMARY).

Just to give a few examples of some class C social issue pages: Economic inequality, Affordable housing, Racial profiling, Police reform (US), Sexism, Public health, Education, Environmentalism, Police, Crime

Seahawk01 (talk) 05:40, 13 November 2018 (UTC)

Icons for interwiki links to sister project pages

I'm generally a bit surprised/annoyed when what appears to be a normal internal link leads me to a Wiktionary entry. It would be a lot less surprising and more helpful if I could know ahead of time that a particular link leads there, say, by including a small Wiktionary logo next to the link as a visual cue. I'm focusing on Wiktionary here because those seem to be by far the most common offenders. Other projects could be included here, but those are usually done with templates that set the link off and make the destination clear.

I'm not sure about the technical feasibility of implementing this, or if it's been suggested before and rejected, so any feedback would be appreciated. –Deacon Vorbis (carbon • videos) 16:17, 12 November 2018 (UTC)

WP:POP? Cabayi (talk) 16:48, 12 November 2018 (UTC)

Interwiki links should have a slightly different color, which is my first cue. We can make those a significantly color for you if you are having trouble with these links by adding some CSS in your common.css page. --Izno (talk) 17:19, 12 November 2018 (UTC)

@Deacon Vorbis: As Izno mentioned, you can add a line or two to your Special:MyPage/common.css to make these links stand out. To make it a different color, you could add the following (replace "#066" and "#046" with the colors of your choice):

.mw-parser-output a.extiw, .mw-parser-output a.extiw:active { color: #066; }
.mw-parser-output a.extiw:visited { color: #046; }

If you want an icon similar to the external link icon, you could add something like:

.extiw {
	background: url(https://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/12px-Wikimedia-logo.svg.png) center right no-repeat;
	padding-right: 13px;
}

--Ahecht (TALK
PAGE) 21:04, 12 November 2018 (UTC)

Thanks for the info, all. That gives me something to tweak my own display with. I guess there's not much interest in making something more prominently visible like this the default, then? –Deacon Vorbis (carbon • videos) 14:03, 13 November 2018 (UTC)

Semi-automate the SPI/CU process

From what I understand, Checkuser is only performed when an admin requests it. But considering the wide prevalence of sock-puppets and the general dearth of administrators, can't this at least be semi-automated? If two editors from the same IP (appropriately extended to the same subnet) edit the same page or pages in the same domain within a specific time frame, they are very likely socks and their names/IPs should be added to a private list somewhere to be acted upon (perhaps by SPI clerks or similar). Editing the same talk page should throw up even redder flags somewhere. There are obviously legitimates cases like alternate accounts that need to be accounted for.

I'm assuming here that something like this doesn't already exist. If there are pages available that detail what goes on behind the scenes with SPIs, please link me to them. But, in this day and age where Machine learning has gone mainstream, there ought to be better technical solutions to handle the endless meat and sock-puppets on this site. Something needs to be done to allow editors to edit and collaborate in peace without having to deal this nonsense. Thanks.—Cpt.a.haddock (talk) (please ping when replying) 12:33, 15 November 2018 (UTC)

That's a bad idea, as it would flag lots of editors using an ISP with carrier-grade NAT. For example, if I ever edit from work, I'm sharing just 4 IP addresses with 65,000 people, many of whom are likely to share my interests. --Ahecht (TALK
PAGE) 21:49, 15 November 2018 (UTC)

Believe me, if we could automate sockpuppet detection, we would have done so by now. Checkusers do keep some relevant information on a private wiki, but none of this is anywhere near as straightforward as "two users on one IP = sockpuppets". Even small ISPs are assigned banks of IP addresses that consist of somewhere from 30,000 to several million individual addresses that users are randomly assigned each time they log on; for IPv6 these numbers are orders of magnitude more absurd (think quadrillions) and the addresses can be reassigned each time a request goes through a router. And even sometimes when we see edits coming from a single IP with identical useragents and overlapping within minutes, it's possible (because of network address translation) that they're still not actually the same person. As for requesting checkuser, anyone (not just admins) can request it if they think they have a good reason, but it's ultimately up to the checkusers to decide whether or not to use the tool since we're the ones accountable for its use. Ivanvector (^Talk/_Edits) 22:03, 15 November 2018 (UTC)

@Ahecht and Ivanvector:: Sure. But all that can/should be taken into account. Even if 10 legitimate users are editing using the same IP, it's only immediately problematic if they're editing the same page(s). And multiple editors editing certain types of pages such as the same noticeboards or even the same talk pages can surely throw up flags. There could be some kind of scoring system to denote the likelihood of socking. This could at least be a start.

I believe that Wikipedia already has a system where it classifies certain subnets as belonging to educational institutions, etc. There are probably databases out there that also do this. Do institutions/ISPs that have migrated to IPv6 continue to use a small NAT pool?

Is there somewhere I can read more about how WP handles this issue and if it has anything planned?—Cpt.a.haddock (talk) (please ping when replying) 08:52, 16 November 2018 (UTC)

I fail to see how the astronomically high ratio of false-positives (where positive means, in this case "A person who is using multiple IP addresses to dodge a block") in any way makes this a useful feature. That even ignores the liability-based and Foundation-level restrictions intentionally placed on the use of the CU tool, which this entirely bypasses. It should also be noted that CU use is meant to be confirmatory and not investigatory; that is CU evidence is meant to confirm what behavioral evidence has likely already determined. CU is far more useful in weeding out sockfarms or the like, but evenso, you need a reason to ask for a checkuser, and you're reason is generally got to be good enough that the evidence is likely enough to block the IP or username on it's own. --Jayron 32 13:41, 16 November 2018 (UTC)

I'm mostly interested in weeding out sock-farms. I don't see why there should be an astronomically high ratio of false-positives. If the requirements for a candidate match are strict, then the likelihood of a false positive comes down proportionally. As you and others have noted, there are so many parameters that could be used to narrow things down:

Exact IP address
Same subnet

Account for known IP pools and whatnot.

Browser signature
Recency of account
Proximity of edit timestamps
Page(s) edited

Similar page(s) edited
Same talk page(s) edited
Same noticeboard pages edited

Restrict analysis to a 48-hour window

Essentially, a bot will be building evidence the same way an actual editor would barring the IP address and browser signature. The bot would present the evidence privately along with a probable match score which will then be evaluated by appropriately privileged users. Yes, I suppose that this is a bit like fishing albeit, by a bot. The bot also need not be restricted to English Wikipedia.

Has the foundation or anyone else performed any studies on the prevalence of sock forms and manipulation of content on WP? Thank you.—Cpt.a.haddock (talk) (please ping when replying) 15:51, 17 November 2018 (UTC)

This would be at the very least grossly unethical, and would likely expose the WMF to serious legal liabilities. No discussion on en-wiki could make this happen, since the WMF would immediately disable any such bot and probably globally ban its creator. (That there must be a valid reason to check a user is policy imposed at Meta level, not something from which an individual wiki can choose to deviate.) Unless and until you can convince the WMF board to allow it, no discussion of a checkuserbot is going to serve any useful purpose. ‑ Iridescent 20:43, 17 November 2018 (UTC)

I do mean that this should be a domain-wide WMF-backed initiative. Where should one go to "convince the WMF board"? Is meta.wikimedia the place? I'd like to know all there is to know about anti-socking initiatives that have been considered/adopted by the foundation. If you are aware of where I can look these up, please let me know. Thank you.—Cpt.a.haddock (talk) (please ping when replying) 21:01, 17 November 2018 (UTC)

This idea would not be approved by the community, and on the off-chance it does, will probably be vetoed by WMF-legal. It's a bad idea. Vermont (talk) 21:34, 17 November 2018 (UTC)

I appreciate your efforts Cpt.a.haddock but I don't think that the parameters that you have set forth would help you catch the particular socks that you are after or very many sockfarms for various reasons. I created a report that may help you though. Everyone that has added the link in the last five years is there and it will include good faith additions as well as other false positives such as restoring the link from where it was pulled by vandals. This means you have some sifting to do...this is much like the false positives that Jayron alluded to. A bonus is that this gives you a cross wiki picture and lets you see who is adding it on other projects. I would also recommend that you post to COIN which may be better adapted than ANI to track promotional sockfarm activities.
— Berean Hunter (talk) 12:40, 18 November 2018 (UTC)

Thank you, Berean Hunter. That link is so much better than using insource: searches! FWIW, the ISHA gang is not the ones that really exasperates me. And I guess my questions here are better off asked on meta.wikimedia. Cheers.—Cpt.a.haddock (talk) (please ping when replying) 08:26, 19 November 2018 (UTC)

Map colors

I find many maps on Wikipedia that are supposed to reflect rankings very difficult to understand. This is because the coloring or shading is either arbitrary or unclear (sometimes because on a map the shades and differences do not seem to be the same as they are against a white background). The coloring or shading should be visually intuitive and distinguishable. This means that, for colors, it should not be arbitrary. Consider the map at Social Progress Index. Instead of progressing in color along a scale of intensity or a standard hue sequence such as ROYGBIV, it jumps all around, making a reader translate it rather than see the message. There should be some guidance (guidelines)in making these maps so that they are useful tools rather than puzzles. Kdammers (talk) 06:10, 18 November 2018 (UTC)

That sounds like something for Wikipedia:WikiProject Maps/Conventions. There are challenges with standardized colors like maps at Commons, colors used in sources, and colors with special meaning or tradition for a subject. I guess commons:File:2017 Social Progress Index map.svg is inspired by the common association red = bad and green = good. The source https://www.socialprogress.org (doesn't depict the same year) has similar but not identical colors. PrimeHunter (talk) 00:27, 19 November 2018 (UTC)

Poor articles

Is there a place to list and draw attraction to poor articles, particularly articles which are of high-importance? -Inowen (nlfte) 04:32, 14 October 2018 (UTC)

On your personal "to-do" list perhaps? Failing that the article's talk page, or a related project's talk page. Martin of Sheffield (talk) 07:56, 14 October 2018 (UTC)

I think I found it: WP:AFI. But it seems to need improvements itself. -Inowen (nlfte) 18:51, 14 October 2018 (UTC)

Many of these will be marked as stubs, so you can look for stubs belonging to projects. One example tool is this: https://tools.wmflabs.org/enwp10/cgi-bin/list2.fcgi?run=yes&projecta=Physics&importance=Top-Class&quality=Start-Class or Chemistry actually has some high importance stubs: https://tools.wmflabs.org/enwp10/cgi-bin/list2.fcgi?run=yes&projecta=Chemistry&importance=High-Class&quality=Stub-Class . THere is also a good chance that some high importance topics have not been written about yet. Graeme Bartlett (talk) 22:09, 29 October 2018 (UTC)

Sometimes (but not always) the relevant projects will be a good place. But it is not news to regulars that many important articles are poor. Johnbod (talk) 22:48, 29 October 2018 (UTC)

What about if there was a threat that poor articles be removed? Wouldn't that motivate projects to take charge? Seahawk01 (talk) 06:46, 2 November 2018 (UTC)

Inowen, Also people can request copy editing help for an article at WIkiProject copy editing guild . JC7V (talk) 20:36, 17 November 2018 (UTC)

They can go for articles for deletion, and if they are not up to good merits, they can have a tag at the top warning that they may go to articles for deletion. Vorbee (talk) 18:05, 3 November 2018 (UTC)

Hi Vorbee, what about poor articles on important topics? For example, C-Class, High Importance Wikiproject articles? Could you delete those and then turn them into stubs or something? Thanks for the clarification! Seahawk01 (talk) 23:25, 5 November 2018 (UTC)

Why would anyone want to threaten people with deletion, if "they" (who is that, if it's not you and me?) don't get articles up to your standards, right this minute? That's not going to promote collaboration. That's not going to help us build the project.

Wikipedia:Deletion is not cleanup. (WP:Stubbing sometimes is.) If you see a sentence, paragraph, or section that could be improved (e.g., by adding sources or re-writing the language), then fix it!. If you see a sentence that you believe is harming the article, then take it out. But don't go around saying that if the WP:VOLUNTEERS don't met your standards on your time table, then all their work should be completely discarded. That's uncollegial and destructive.

If you're thinking that threats work, then you should go read some more psychology. (Oh, and while you've got those books in hand, you might as well improve the related articles, okay?) What actually works is quietly helping people. If you find a new article that someone started today, or an expansion that a new editor made to an existing article, and you add a source or a fact (after waiting an hour or so to make sure they're done – Wikipedia:Avoiding edit-conflicts is important), then when they come back tomorrow, they'll feel encouraged and interested and maybe even learn how to edit better. That's how you get good content. WhatamIdoing (talk) 23:35, 19 November 2018 (UTC)

OK I take the above points that it would not be practical to delete articles if the article is of high importance. If the article is a poor article, how about having an tag saying "This article may need clean up" heading it? Vorbee (talk) 07:57, 21 November 2018 (UTC)

@WhatamIdoing: ah, well...I'm new to Wikipedia. Seems like my saying "threat" was ill-considered. Perhaps I should read up on "herding cats"...then I can also channel all my research into creating a page about this topic as well :-) Seahawk01 (talk) 01:17, 22 November 2018 (UTC)

Regarding the initial post, I happened upon Category:Wikipedia article challenges and thought having a challenge on vital articles might be helpful. Last week I made a post about this here as well (see below). I am seeing here at Village Pump / Idea Lab a general resignation and attitude that "Wikipedia is a work in progress," but I disagree since Wikipedia is such an important point of reference for so many people and feel fundamentally there should be more attention paid to provide the public with WP:GOOD quality articles on major societal issues. Seahawk01 (talk) 03:13, 23 November 2018 (UTC)

I think you're right that we need improvements on articles these basic subjects. But... it's really, really hard. Like, you wouldn't believe how hard those "simple" subjects can be. I don't know if you've looked at the WP:FAs much, but one of the things that's striking is how many of the featured articles are on obscure subjects: an unpopular book, an uncontroversial weather event, a boring film. The usual explanation is that if nobody cares about the subject, then nobody cares enough to disagree with what the article says. Compare that to, say, last year's attempt to improve Acne, which is a subject that every person above the age of 12 has some opinions about, and which prompted disputes over things like whether to mention the belief (urban legend?) that smoking tobacco might reduce acne. The general subjects are hard because everyone believes that their own views are The Right™ views, and everyone has views on general subjects. WhatamIdoing (talk) 17:15, 23 November 2018 (UTC)

Thanks for the reply back WhatamIdoing. I did briefly look over the WP:FA list. I remember one was the shortest highway in New York state. So, that's pretty obscure! And, when I first started here a month or so ago I remember a discussion in the Teahouse about a page on nuclear power...how it had become bloated by years of people either for or against coming and adding their thoughts (with disregard for page flow, storytelling, etc). So, maybe it is just the nature of the beast and I'm so new at editing that I'm just idealistic. Before I started editing, I had used Wikipedia for years and always thought highly of it. But, I just used to look at pages like math history. Now that I started editing, I wanted to write about stop and frisk and related topics and am discovering how many problems social issues pages can have. As a side note, I did split economic inequality and split affordable housing (twice). But, to get a page on a topic like that in shape is too much work for one person. Better to pick smaller topics. Thanks again for your input. Seahawk01 (talk) 03:59, 24 November 2018 (UTC)

unbundling DYK queuing

I'd like to discuss the idea of unbundling DYK queuing so that trusted editors could apply for the tool to move prep to queue. I think it might solve multiple problems to have maybe twelve editors working in teams of two with that tool, each team responsible for moving, say, Prep 1 to Queue 1 for every iteration. Being responsible always for Queue 1 might make these editors take real pains to provide a detailed final review to prevent errors from appearing on the main page, whereas overworked admins sometimes may be just trying to feed the beast. Having two people responsible for that exact definite job would mean that even in times when RL inteferes, like during a holiday weekend, we'd be less likely to end up with six empty queues two hours before DYK is due to go up. I believe there would be multiple experienced editors who would be interested in doing this one important job for WP, but wouldn't necessarily be interested in applying for admin. valereee (talk) 04:45, 25 November 2018 (UTC)

I think you might be in the wrong place with this question. The queues are where content is placed to appear on Wikipedia's main page. You are asking for a specific project to allow access to main page editing by non-admins. — Maile (talk) 13:06, 25 November 2018 (UTC)

I asked here because it said Idea Lab was for developing ideas, but happy to ask for discussion somewhere else if someone can point me to a more appropriate place. I don't want to propose anything yet or ask for polling, just discuss what might be workable to solve these issues. valereee (talk) 13:20, 25 November 2018 (UTC)

This conversation has moved back to WT:DYK as the project itself decides on its template restrictions. — Maile (talk) 13:39, 25 November 2018 (UTC)

The newer Advanced Search to become default feature soon

Three days later, the newer Advanced Search feature, currently a Beta Feature, will become default feature in all wikis. However, I have issues with it mainly because its Namespace checklist vertical window is very narrow and inconvenient to browse/surf. Due to the one-vertical-column formatting, clicking one of desired namespaces becomes harder, especially for users who have enjoyed the older Advanced Search, which divides the namespace options into columns. I was given a suggestion to discuss this locally. I am thinking ideas about what to do with the newer feature, like proposal to create the "Hide the improved version of Advanced Search" option, asking developers to delay the move, create a Phab ticket about the Namespace list, etc. George Ho (talk) 21:46, 25 November 2018 (UTC)

Simple English tab on all English (en.) pages

The Simple English version of Wikipedia is a very useful tool when reading something but you need it explained from a more basic or layman's viewpoint. I'd propose to add a dedicated tab, or link, at the top of each English page, only if there is an equivalent Simple English alternative, so that new readers to pages can instantly get a simplified version of the page. Similarly, on all Simple English pages, there should be a direct link back to the standard English page. One proposal is to have a tab along the other tabs like "Article, Talk", etc., another would be to have a sentence at the start of each article, in italics, saying "This article is also available in Simple English: <articlename>" and the <articlename> is linked.Byziden (talk) 16:46, 24 November 2018 (UTC)

That sounds like a good idea to me. Bus stop (talk) 16:51, 24 November 2018 (UTC)

From how I understand it, though, SE articles aren't supposed to aim at a basic/layman viewpoint; they're just supposed to use simple vocabulary (as much as is possible for a given topic) and sentence structure. Even taking that into account, I think the quality of articles over there is on the whole very poor, and I'm not sure nudging someone there is necessarily a good idea. There was a pretty long discussion over there about closing it down, but there was a lot of resistance to the idea. –Deacon Vorbis (carbon • videos) 17:01, 24 November 2018 (UTC)

+1 - I think it's a great idea, Ofcourse the project has flaws but then again every project does. –Davey2010^Talk 17:20, 24 November 2018 (UTC)

There's a pretty nifty userscript by Djsasso that does this: User:Djsasso/SimpleWPTab.js and it's companion on simplewiki: w:simple:User:Djsasso/enWPTab.js. — AfroThundr ^{(u · t · c)} 23:40, 25 November 2018 (UTC)

It should already show up in the languages area on the left sidebar on desktop views. ~ ONUnicorn^{(Talk|Contribs)}problem solving 20:15, 27 November 2018 (UTC)

WebCite

In 2013 there was a proposal for the Foundation to take over the running of WebCite (see Meta:WebCite). The idea was supported by WebCite themselves. Alternative suggestions were that the Foundation should support WebCite in some lesser way; with technical support or monetary grants for instance. The proposal was closed without saying what has actually happened, if anything.

Since then, the site has had frequent, lengthy, and unexplained outages (see Talk:WebCite). WebCite is very important for Wikipedia. It enables us to safely protect references against linkrot. Is it time to reopen this proposal? SpinningSpark 12:30, 27 November 2018 (UTC)

The landscape has changed somewhat since that proposal. We now have a better idea how many links there are across all wiki languages (WebCite is about 5% of all archive links on Enwiki), and WMF has a good working relationship with Internet Archive including IABot and WaybackMedic. There are also new players like archive.is which are effective at archiving WebCite archives, and I suspect Internet Archive would be open to it as well. In the end it's not our responsibility to fund WebCite as an entity, we only care there are archives of the pages. If we fund a site like WebCite, why not fund Internet Archive, Archive.is and everything else? If WebCite can't supports itself, why are we outsourcing our most critical pillar of WP:V to them when there are other quality competitors who don't require funding.

This can be accomplished IMO simply be capturing the WebCite archives somewhere else as backup, in case WebCite ever go down permanently. We can also begin the process of moving links away from WebCite to other providers, we've got bots ready to go at a moments notice it could be finished in a week or two. But it would require consensus discussion because despite the unreliability of WebCite (weeks long outages etc) there are users who want to and will continue using them. -- GreenC 15:26, 27 November 2018 (UTC)

To me, the great selling point of WebCite is it will archive on request. You can guarantee that there is an archive of the page you used as a source on the day that you looked at it. SpinningSpark 18:37, 27 November 2018 (UTC)

Oh others have that these days. On Wayback it's called Save Page Now (SPN). On archive.is also available. In fact I would argue WebCite has the least robust because they will report the page is saved and provide the URL, but then start a background process and email when ready. If the page is not saved for some reason, but in the mean time you added the URL into Wikipedia, this creates link rot. My bot has cleaned up thousands like this, why WebCite has the largest percentage of link rot. -- GreenC 18:45, 27 November 2018 (UTC)

Enforcing WP:JOBTITLES

We still have many bios with political offices that are inconsistent with capitalizing & non-capitalizing. The best example is the bios of US governors & lieutenant governors. Can we enforce WP:JOBTITLES to settle the dispute? GoodDay (talk) 02:27, 26 November 2018 (UTC)

Are these bona fide disputes, or just things no one has fixed yet? --Jayron 32 02:36, 26 November 2018 (UTC)

It's suppose to be settled at JOBTITLES. But, not everyone is abiding by it or at least, not everyone is making the effort to implement it consistently. A combination of some dispute & apathy, seems the core. Possible cause? lack of awareness across the community. GoodDay (talk) 03:27, 26 November 2018 (UTC)

Might be disagreement as well. JOBTITLES is part of the Wikipedia:Manual of Style which is prefixed with "This guideline is a part of the English Wikipedia's Manual of Style. It is a generally accepted standard that editors should attempt to follow, though it is best treated with common sense, and occasional exceptions may apply. Any substantive edit to this page should reflect consensus. When in doubt, discuss first on the talk page." Jo-Jo Eumerus (talk, contributions) 07:10, 26 November 2018 (UTC)

I opened an Rfc at the WP:Manual of Style page. GoodDay (talk) 00:11, 28 November 2018 (UTC)

What to do about OMACL links?

A decade or more ago, various (entirely good-faith) Wikipedians added exlinks to omacl.org, which was at the time was the Online Medieval and Classical Library - which hosted a range of historical texts. But now, as an IP editor points out, omacl.org redirects to a payday lender. I expect that the domain has expired and has been bought by that loans company. We have nearly 200 links to omacl.org, which obviously we need to fix somehow. The IP fixed that particular link by changing the domain to mcllibrary.org, and that site appears to host the correct documents (and for a few of the other links we have, at least). I'm a touch skittish about that site, because it seems to be hosted by another individual person - and I fear that if we put work into changing all the links there, in a few years that person may abandon his project, and the same kind of domain-lapse problem will recur. It would be better if we could fix the links to a more stable location, like the Internet Archive, or a University department. So my questions are:

is there such a host that has this content?
should we change the links wholesale to that, or must we consider each link on its merits?
is there a partitially automated process (e.g. Twinkle) that someone could use to simplify this task? 200 edits is a lot for a person, but too little for a fully automated bot task.

I'll prod a couple of the related wikiprojects for their input. -- Finlay McWalter··–·Talk 18:13, 27 November 2018 (UTC)

@Finlay McWalter: You can leave a comment on User talk:InternetArchiveBot or its operator's talk page to ensure these references are updated to archive.org links (or if they are not updated, then they can't be updated). For all others, you will probably have to 1-by-1 replace the links, and then I would recommend ensuring those links are saved on Internet Archive also. --Izno (talk) 22:37, 27 November 2018 (UTC)

I don't remember ever looking at this site, but it appears from the list of links (see above) that it offered older English translations (therefore PD) of fairly well-known sources, in machine-readable text divided into chapters. This is not what the Internet Archive does best -- it's more like what Project Gutenberg does. But I don't know of any reliable way to convert the links to gutenberg without checking each one. Andrew Dalby 14:13, 28 November 2018 (UTC)

Just to comment that the idea that documents hosted by university departments are stable is misplaced confidence. They are just as suscepible to linkrot as anywhere else, possibly more so. The documents often only stay up as long as a particular course is being run or a particular professor needs them. I've fixed hundred of such links that have gone dead. SpinningSpark 14:50, 28 November 2018 (UTC)

Victims lists are becoming a source of constant debate and argument

The inclusion of lists of non-notable victims is becoming problematic. It seems that they are being added by editors to articles dealing with mass casualty WP:EVENTs which is causing frequent, often lengthy and sometimes acrimonious debates over whether such lists are appropriate and/or violate WP:NOTMEMORIAL and NOT:EVERYTHING with local consensus proving either elusive or dramatically varying from one article to another depending on shows up and how determined they are to bludgeon their way through. This is getting out of hand and we really need to establish some kind of guideline for the sake of consistency and putting a stop to these endless debates. I personally believe that in most cases they are unencyclopedic, add nothing of substance to the article and violate, at least in spirit, NOTMEMORIAL. But even if a decision is made to allow them, which I would strongly oppose, that would be better than the status quo. My personal preference would be to amend NOTMEMORIAL to expressly prohibit lists of non-notable victims. Obvious and commonsense exceptions would include otherwise nonnotable victims who were significantly involved in the EVENT. Which is to say they did more than just die. Generally these will simply be named in the article narrative. I also would be fine with including an WP:EL external link to a suitable memorial website or news site that lists the victims. I do realize that this has been discussed before, but the status quo is just not working. Thoughts? -Ad Orientem (talk) 15:09, 19 November 2018 (UTC)

I also think that these lists add little to the article narrative. If a person had a notable role in an event, as documented in reliable sources, their role can be noted as part of the prose narrative of the event. If the person is otherwise wiki-notable (has or could have a stand-alone article based on their life outside of the event) then they can also be mentioned in the prose of the article. I am at a loss as to what the possible use is of lists of otherwise unnotable names, dropped into such an article without context, serves in the story of such events. Such lists serve little more than to act as a memorial to the victims, and while they can often be referenced, they rarely serve any relevant purpose, and as such, should go. --Jayron 32 15:24, 19 November 2018 (UTC)

We've gone round in circles on this issue at Talk:Thousand Oaks shooting and it was previously discussed here. I'm firmly in the "no unless the people are notable" camp, but some people aren't and always try to have a list.--♦IanMacM♦ ^{(talk to me)} 15:27, 19 November 2018 (UTC)

- This needs to be broadened somewhat to include participants or crewmembers. USS Monitor contains a list of crewmen who are non-notable and don't perform any important actions. People who do something significant should mentioned in the text, but a list of people who were simply present has no value, regardless of their status as victims or whatever.--Sturmvogel 66 (talk) 15:30, 19 November 2018 (UTC)
  - Citing lists from more articles that should also be removed doesn't really help build a case... --Jayron 32 15:35, 19 November 2018 (UTC)
They should be removed in general. Where one or more victims had a role, as was the case in the Sandy Hook shooting, they can be described in prose. Makes it very easy to draw the line of what to not include. --Masem (t) 15:40, 19 November 2018 (UTC)
- To add to my argument, victim lists tend to be a matter of RECENTISM as well as sensationalist reporting (if the incident involved innocent civilians). A question to ask is if twenty years later, will those victim lists be essential to an article? Nearly all the time, that answer is no. I do realize that locally/regionally/nationally there will often be memorials to such victims, but that's just not information appropriate for an encyclopedia if these people were non-notable. What value is there knowing that Jane Smith and John Doe died in the event if they otherwise had no role in it? --Masem (t) 17:32, 19 November 2018 (UTC)

We are not "memorializing" anyone. You have to know intention to charge that we are memorializing. Show me where "Jane Smith" or "John Doe" died in an incident. Names happen to often reflect ethnicities. Names are often "non-generic". Hometowns, ages—all of humanity is not a pile of undifferentiated biomass. Bus stop (talk) 17:50, 19 November 2018 (UTC)

In 10-20 years, unfortunately, yes they are, if they are non-notable persons before the event. The vast majority of humans are non-notable, and rarely gain notability post-death. And why do we care about ethnicity, save for cases when that was a reason for the mass death (eg the recent shooting in Pennsylvania) in which case we can say the broad description about them. --Masem (t) 18:15, 19 November 2018 (UTC)

"why do we care about ethnicity" I don't know. But we do. And it is not just ethnicity. It is age too. And a minimal few other factors. Occupations and home towns have informative value. Bus stop (talk) 18:32, 19 November 2018 (UTC)

This is fundamentally an WP:ILIKEIT argument. Whether an individual picks their nose has some degree of informative value. Whether it belongs in an encyclopedia article or not is a different question. Parsecboy (talk) 18:37, 19 November 2018 (UTC)

"Whether an individual picks their nose has some degree of informative value." That is why we exercise judgement as to how extensive our coverage is of the lives of decedents. Bus stop (talk) 18:40, 19 November 2018 (UTC)

But you just said "all information is constructive" - you can't have your cake and eat it too, my friend. Parsecboy (talk) 18:42, 19 November 2018 (UTC)

Yes, I wasn't speaking about Wikipedia. All information is informative. Most of it fails to inform. The value of information is a function of our ability to decipher it. Bus stop (talk) 18:51, 19 November 2018 (UTC)

"All information is informative. Most of it fails to inform." GMG ^talk 18:55, 19 November 2018 (UTC)

We can summarize any critical ethnicity/gender/age/etc. breakdown if it seems appropriate in the prose given what the event was (eg we frequently break down nationalities of passengers in international aircraft disasters, or in cases of school shootings, how many were students and how many were teachers/others). We absolutely should not be guessing on names, hometowns (which doesn't confirm anything on ethnicity) or other details. --Masem (t) 19:28, 19 November 2018 (UTC)

Bus stop, you literally said "Our primary purpose is compiling information. You are mistaken if you think our primary purpose is providing constructive information. That is because ultimately all information is constructive." (until you removed it after I pointed out you contradicted it here - rather poor form, I'd say). So unless you have a mouse in your pocket, and you're working on your own website, I can only assume you were talking about writing articles on Wikipedia. Again, you're trying to have your cake and eat it too. You either make distinctions about what information is useful for an encyclopedia article and what isn't (like you seem to suggest above) or you don't (like you did in the comment you have now removed). If the former, you need to provide an explanation about how such information as you'd like to include is relevant in an encyclopedia article (as opposed to a newspaper article or a genealogical archive, for instance), and if the latter, then you have no leg to stand on, policy-wise. Parsecboy (talk) 19:30, 19 November 2018 (UTC)

Let's stop being silly. If there aren't space constraints, editors should be allowed to build articles. This is the sort of information being removed. The "Casualty" section is entirely constructive to the article. We see no excess of information in that "Casualty" section of that article, which of course I am presenting merely as an example. Bus stop (talk) 15:45, 19 November 2018 (UTC)
That sort of information probably should be removed. There are practically never space constraints, but we still don't include every piece of information. It's just article bloat – that's what WP:INDISCRIMINATE is for. Continuing to use this article as an example, I can't see how someone wanting to read and learn about the collision could ever care about the names, ages, and home towns of the dead. –Deacon Vorbis (carbon • videos) 15:58, 19 November 2018 (UTC)
I would say many readers would "care about the names, ages, and home towns of the dead." I know I would. Bus stop (talk) 16:22, 19 November 2018 (UTC)
Well, it's trivial to find a minimum of 1 person in the world who would be interested in anything. However, I think the better test would be to look at the general trends at Wikipedia towards lists of people's names. There's nothing inherently different between, say, the list of people who died in a particular event compared to say, the list of people who attended a certain school or worked for a certain corporation or attended a particular concert or some such. What is Wikipedia's guidance for those sorts of events. Whatever that is, we should probably have similar guidance here. There's nothing extra special about dying over any other life event, after all. --Jayron 32 16:49, 19 November 2018 (UTC)

Perhaps so, but show me an encyclopedia that lists that information. They'll give the number of casualties, but not details. Similarly, you'll often find histories of individual ships that are seriously damaged or sunk that lack detailed information on crew losses or casualties. Hell, a lot of my sources have different loss figures for the same event. The key thing for me here is WP:SUMMARY; naming the casualties/participants/etc. isn't summarizing anything.--Sturmvogel 66 (talk) 16:54, 19 November 2018 (UTC)

Responding to Jayron32 and Sturmvogel 66—the specifics matter. Part of the huge impacts these events have are their fatalities. There is a risk in generalizing. It is not "there were 7 deaths". It is "these are the people who died." We should not want to elaborate beyond a certain point. But it is also ludicrous to think that we have covered an incident by lumping all of humanity into one pile. There were specific people who died. There are minimum identifying features that should be included if we are covering an incident. That includes names, probably ages, and perhaps a few more identifying features. In the case of American sailors the hometown is a logical and completely defensible piece of information for inclusion. Do we want to know their dog's name, whether they are married or not, number of children, hobbies? No, we don't. Specific people with specific identities died and our coverage of these topics should allude in some small way to their identities. Bus stop (talk) 17:50, 19 November 2018 (UTC)

Specific people with specific names also attended a university, or worked for a corporation, or attended a concert. You've not established how these lists are distinct from others where we avoid naming otherwise non-notable people in them. --Jayron 32 17:56, 19 November 2018 (UTC)

"You've not established how these lists are distinct from others" Nor need I. Reality has established the distinction of these lists. We are not here primarily to educate people. Yes, most of the time we try to digest information in accordance with the views of sources. But identities of decedents do not require any special explanation. We are documenting by minimal means the identities of the fatalities that are of central importance to the incident being written about. Bus stop (talk) 18:09, 19 November 2018 (UTC)

You keep repeating that. It doesn't become true merely through your will to say it over and over. --Jayron 32 18:13, 19 November 2018 (UTC)

"We are not here primarily to educate people." GMG ^talk 18:17, 19 November 2018 (UTC)

Discussed in November 2017 as linked by Ianmacm above. Discussed more recently in July 2018, here. People keep bringing the issue to the community, and the community keeps punting, saying that it needs case-by-case evaluation and even a default guideline would be bad. This, despite the indisputable fact that the arguments are the same in every case. If any argument has ever included something particular about that case as distinct from other cases, I haven't seen it. That means that case-by-case evaluation is a ridiculous waste of editor time. Until it can be brought to the community without case-by-case on the table—or the community magically comes to its senses—I don't see how we're not condemned to the status quo indefinitely—repeating the same arguments again and again, with the outcomes variously determined by who shows up for the discussions. ―Mandruss ☎ 16:03, 19 November 2018 (UTC)

Summarize the core arguments with links to examples, in an essay. Anyone can do it - demonstrate the repeating arguments. It would be a good first step to creating a guideline. -- GreenC 17:27, 19 November 2018 (UTC)

Does the inclusion of victims names add to the understanding of the articles subject for the general reader? I can think of some cases where it does but generally no it does not. Therefore I would support a policy along the lines of "Normally victims should not be mentioned by name in articles. Exceptions should be discussed on the article talk page and a consensus formed before being added." Lyndaship (talk) 16:17, 19 November 2018 (UTC)
This seems like a parallel discussion to one ongoing at WT:NOT. --Izno (talk) 17:33, 19 November 2018 (UTC)
IMO, the ultimate where trying to write the article without a victim list would be completely bizarre is Ariel Castro kidnappings...Naraht (talk) 17:51, 19 November 2018 (UTC)
That article does not have a victim list, so it is a bad example. --Jayron 32 17:54, 19 November 2018 (UTC)
Maybe look again? The victim list is in the very first sentence of the article. Not all victim lists use list formatting. WhatamIdoing (talk) 23:53, 19 November 2018 (UTC)
No, that article does not have a victim list. What that article has is three people whose story of integral to the prose narrative and we, of course, don't scrub their names from that narrative, which would be stupid. That article has zero connection to what is being discussed here, which is a list of people who died during an event, without any part of the narrative. So no, that article is not in any way a useful example because nothing in this discussion would change a single character of text of that article regardless of what the consensus comes up with. Try again. --Jayron 32 04:35, 20 November 2018 (UTC)
It's a list of the victim's names, and therefore it's a "victim list" in plain English. And we are (and IMO should be) discussing all victim lists, not just lists of people who die passively. WhatamIdoing (talk) 20:54, 21 November 2018 (UTC)

Naming victims that are essential to properly summarize the crime/event in the prose of the article is fine. You just don't need a separate table for that. --Masem (t) 18:16, 19 November 2018 (UTC)

I think it's a matter of scope. Including the names of victims of a crime where there is only one victim (Killing of Jamal Khashoggi as an extreme example) is necessary. A "victims list" of hundreds of people is obviously not necessary; for example listing all 851 people injured at 2017 Las Vegas shooting would clearly be excessive. Even listing 58 people dead is likely excessive. When there are roughly 10 victims, it's often the case that the media will cover all of them in enough detail. I'd lean towards including it on the Thousand Oaks page or the Pittsburgh synagogue shooting article, but could be convinced otherwise. I certainly don't see any advantage to saying the victims included a 48-year-old bouncer; a 33-year-old Marine Corps veteran; and a 27-year-old Navy veteran over giving names (with references that have further info). power~enwiki (π, ν) 18:26, 19 November 2018 (UTC)
The first question we really need to address is, what value does a list of names of non-notable individuals really add to an article? Unless you personally know the individual in question, a name is meaningless. The second question is, should an encyclopedia be in the business of providing enough material on a non-notable individual that their name is not meaningless? No, we obviously should not. News outlets generally include such information, which is all well and good, but we are not a newspaper. Parsecboy (talk) 18:39, 19 November 2018 (UTC)

"a name is meaningless" Doesn't a name sometimes suggest an ethnicity? Bus stop (talk) 18:47, 19 November 2018 (UTC)

Sometimes, but frequently not. Without clicking the link, tell me where Vincent Rodriguez III is from. Moreover, what relevance is that for an encyclopedia article about an event? In other words, it would be relevant to know where a person is from if the article is about that person, but if the article is about an event, and they are a non-notable individual where their place of origin has no bearing on said event, why do we care? Parsecboy (talk) 19:41, 19 November 2018 (UTC)

As unhappy as I am about lists of names of non-notable people in articles, I think that battle is lost: Passengers of the RMS Titanic. - Donald Albury 19:22, 19 November 2018 (UTC)

I find interesting a section for Passengers by ethnicity. Bus stop (talk) 19:30, 19 November 2018 (UTC)

We routinely include breakdown numbers by nationality/ethnicity in any mass-transport international accident. --Masem (t) 19:34, 19 November 2018 (UTC)

Sounds like a summary to me.--Sturmvogel 66 (talk) 20:16, 19 November 2018 (UTC)

Some people are hyper-involved ("geeky"?) with the Titanic, they known every passenger and their background. Books on this subject. Not a typical example. -- GreenC 21:42, 19 November 2018 (UTC)

"they known every passenger and their background" And why do you think this is so? There may be reasons particular to the Titanic incident, but I don't think that explains all. No matter the incident the reader wants to know the identities of the people involved. Editors here are arguing that this information shouldn't be in the article. But who are we writing the article for? Oh, we know what is best for the reader? That is the height of hubris. We are not talking about extraneous or tangentially related facts. The identities of the deceased are clearly within the scope of the article. I don't think it is our role to deprive readers of relevant information just because we think they should not be interested in this information. And I will be the first to admit that I am interested in this information. The reason we are interested in knowing a little bit about the identities of the deceased is because we want specifics. When it comes to fatalities we want specifics on who died. It is unsatisfactory to simply be told "7 people died". The reader has an appetite for more information in the form of "which 7 people died?" Wikipedia is not here to WP:RIGHTGREATWRONGS. It doesn't matter that some editors think the reader doesn't need to know this information. The ultimate question in this discussion is one of WP:WEIGHT. Obviously too much information on decedents is too much weight. But names and ages clearly are not too much weight. Bus stop (talk) 22:44, 19 November 2018 (UTC)

A random idea is if what if these lists existed at Wikisource (as long as they are properly sourced)? They can then be linked too from WP articles. --Masem (t) 19:34, 19 November 2018 (UTC)
Often people who are victims will then receive coverage in the media, so that they become notable, but it is just a one-event situation, so then they should be listed or mentioned in the article about the event. So if adequate sources exist then the victims should be included. Graeme Bartlett (talk) 22:27, 19 November 2018 (UTC)

Victim lists proposal #1

So OK. Normally I'm of the mind to let the editors decide, but if it is true that "Victims lists are becoming a source of constant debate and argument", that wastes energy. So how about a compromise? Make a rule called WP:VICTIMS with something like this:

Articles on events in which two or more people were killed or injured -- airplane crashes for instance -- may usually give the names of the victims if there were ten or fewer. If there were eleven or more, articles should usually not include the names of the victims.

As always, common sense exceptions may be made. Bluelinked names are exempt from this rule, may always be given, and do not count against this "rule of ten" limit. There is no requirement to give victim's names; it is allowed if someone wants to (and there are ten or fewer).

The names and descriptions of victims should be in sentence or paragraph form, not list format. Normal sourcing rules apply, of course.

What's good about this is that it quashes arguments, pretty much. Why ten? I dunno -- got to have some number. Make it eight or twelve if you like. Ten is not really an imposition on the article. You can ten names and bit more into a short paragraph. It doesn't unbalance the article.

As to having the names in paragraph rather than list format: 1) it makes them a little less prominent; they don't take up half a screen, and 2) lists of victims just drive some people nuts, perhaps for that reason. Let's try to gruntle both sides a little.

Sure this is arbitrary but arbitrary works. Like for baseball players, there's an arbitrary rule: if you had even one at bat in the major leagues, you get an article, even it it was in 1887 and we don't even know your first name. If you had a fifteen year career in the minor leagues, you're not in. (Unless you meet WP:BIO and someone can successfully argue for you.) Fair or not I don't know, but there are virtually no arguments about ballplayers. We have lots of rules like that -- state legislators, etc. Works a charm. Herostratus (talk) 22:34, 19 November 2018 (UTC)

I don't think you are addressing the core issues here. Sure—we can place arbitrary limits. But what are we discussing? Names of deceased fall squarely within the scope of articles on incidents with fatalities. Certainly we can't include all decedents in World War II. But it is entirely incorrect for us to decide that readers should not want to know the identities of people who lost their lives in incidents. Elsewhere this information exists for current tragedies and there is no reason I know of to make Wikipedia the truncated source on these tragedies. Bus stop (talk) 23:03, 19 November 2018 (UTC)

I would oppose that if proposed, as my objections to the lists have nothing to do with the size of the lists. You won't find "hey it takes up so much space in the article" in any of my arguments to date. ―Mandruss ☎ 23:09, 19 November 2018 (UTC)

I would oppose that. (The baseball thing is not arbitrary, but basically an objective means to determine if a player played in one profession game). It is a number that will be gamed. It is better not have to have the lists in the first place. --Masem (t) 23:14, 19 November 2018 (UTC)

"It is better not have to have the lists in the first place." The same can be said for anything—"It is best not to include the names of alleged assailants", "It is best not to include the make and model of the gun used", "It is best not to include the street address of the venue of the incident", "It is best not to include the name of the venue". In your wisdom you feel the reader should not satiate their appetite for information pertaining to the identities of the deceased at our article; they will have to go elsewhere if they want that despicable information. You are making an arbitrary value judgement. Bus stop (talk) 23:28, 19 November 2018 (UTC)

We're talking about victim lists, not prose information. If any of those elements are essential to be able to summarize the event clearly, then they should be included. Victim lists are rarely essential - there may be victims that were known to try to take action to stop the event, but those names can be included in prose. --Masem (t) 00:19, 20 November 2018 (UTC)

I agree that we are talking about victim lists. I strongly favor victim lists of otherwise non-notable people including only rudimentary information such as name and age and sometimes a few other bare pieces of information such as occupation and hometown if applicable. That is the crux of this discussion. My examples might not have been good—you are correct to point out that my examples take place in prose. I stand corrected. Bus stop (talk) 00:36, 20 November 2018 (UTC)

Herostratus, I think that's a functional proposal. You'll need to add some weasel words to accommodate the existence of the Passengers of the RMS Titanic (and similar) list articles, but I think that won't be too hard.

The hard part will be getting entrenched editors to compromise on a rule that would let them get back to the work were all WP:HERE to do, instead of setting ourselves up for having this discussion at least twice a year for the next decade. So for all those who are thinking about opposing it: If you want to have lists, wouldn't you at least like to start with something that says that it's possible, under certain circumstances? And for those who hate these lists, do you really want to have this discussion again next week over the Camp Fire (2018) victims, or could you live with a compromise that at least rules out victim lists that include the names of dozens of non-notable people? WhatamIdoing (talk) 00:09, 20 November 2018 (UTC)

No, I do not want to have this discussion again at Camp Fire or any future articles. What I want is for the community to confront the issue head-on and decide, once and for all (or at least for the next decade or so, since WP:CCC), whether the lists should be included as default or omitted as default, with provision for exceptions by local consensus in either case. While I would prefer the latter, I would much prefer the former to the status quo. ―Mandruss ☎ 00:21, 20 November 2018 (UTC)

Do you think that the default needs to be either "yes to all" or "no to all"? Wouldn't "Yes if it's a short list, and no if it's not" be an acceptable compromise? WhatamIdoing (talk) 01:53, 20 November 2018 (UTC)

@WhatamIdoing: As I said above, my objections to the lists have nothing to do with the size of the lists. These principles are not something it's ok to ignore as long as you only ignore them in small quantities. But if the community decided on include as default, I can certainly see the need for a rule-of-thumb limit on size. As a practical matter I wouldn't try to address both issues in one proposal. ―Mandruss ☎ 02:04, 20 November 2018 (UTC)

The Day the Music Died names all (four) victims from that mass casualty event. One of them is non-notable. Are you going to remove his name, because you oppose all victim lists in principle? If not, why not? WhatamIdoing (talk) 16:25, 21 November 2018 (UTC)

@WhatamIdoing: I wouldn't require "notability". I think a significant non-passive role in the event should suffice. Certainly the pilot of a plane that crashed qualifies as a significant non-passive role in the crash. He's named 19 times in that article, and he's very likely discussed at length in reliable sources because of his role, not his death. It's not hard at all to see the difference between him and, say, one of the victims of the Thousand Oaks shooting. ―Mandruss ☎ 18:54, 21 November 2018 (UTC)

The arguments I've remember you putting forth in the past are that victim lists are a policy violation (which presumably includes even this short one), that they are invasions of privacy for people who aren't public figures (which definitely includes this one), and that names are meaningless to almost everyone (which basically assumes that all readers are from your culture, so that if a name doesn't mean anything to you, then you conclude that it won't mean anything to anyone. For example, if an editor doesn't happen to know that a "Vicente Rodriguez" is probably Hispanic but a "Vincent Rodriguez" (i.e., a French or English first name with a Spanish family name) has a higher chance of being Filipino, then you conclude that almost nobody will, which is probably not true).

So now you add that you would exclude the names of passive victims. All right, I can agree that the pilot of that flight probably wasn't a passive victim. So let's look at John F. Kennedy Jr. plane crash, which also lists all the people who died, two of which did nothing other than happen to be in an airplane that crashed. One of them wasn't notable, either. Why wouldn't you blank the name of this non-notable passive victim? She doesn't fit into any of your previously articulated exceptions: She's not a public figure, she died passively, and you have declared that names are meaningless. But I don't think you would remove it. Why not?

(She fits perfectly into my circumstances in which we should include names: It's a very short list, and it's unseemly to list nearly everyone by name except one or two). WhatamIdoing (talk) 21:09, 21 November 2018 (UTC)

@WhatamIdoing: Carolyn Bessette is named because she's notable enough to warrant a BLP. Lauren Bessette was at least a fairly high-profile individual, being a part of the Kennedy "family" by marriage as JFK Jr.'s sister-in-law. Privacy is hardly a consideration for either Bessette.
No doubt you could find other cases that get around those arguments, but don't bother. Until I encountered this thread my only interest has been in victims lists for random mass killings (RMK). As I expressed elsewhere, things get more complicated very quickly as you expand scope, and the result is often no improvement at all. Perfect is the enemy of better. I see little benefit in a General Theory of Lists of Dead People in Articles About Any Imaginable Subject, or rather I don't think the lack of such a theory should be allowed to impede improvement in the RMK area. John F. Kennedy Jr. plane crash is not in the same class as Thousand Oaks shooting. ―Mandruss ☎ 21:49, 21 November 2018 (UTC)

Mandruss—you say above in reference to a pilot that "he's very likely discussed at length in reliable sources". Reliable sources also happen to discuss the victims of the "Thousand Oaks shooting". In my opinion we should not be splitting hairs and making distinctions that editors think are significant. You are distinguishing between non-passive roles and passive roles. But those are your criteria. How do you know that the reader has no interest in knowing the identities of those people that editor Mandruss considers "passive"? Bus stop (talk) 22:01, 21 November 2018 (UTC)

No thanks. ―Mandruss ☎ 22:08, 21 November 2018 (UTC)

"No thanks" to what? Bus stop (talk) 22:23, 21 November 2018 (UTC)

WhatamIdoing—Wikipedia is WP:NOTPAPER. A separate page for listing brief identifying factors pertaining to fatalities such as name and age is feasible when the number of victims would take up too much space to be practicable on a main article page. Bus stop (talk) 00:27, 20 November 2018 (UTC)

Enh, what I'm seeing here is a couple-few guys who who don't want to compromise. Whether my idea is good or not, whether it could be adopted or not... who knows? When the most clearly expressed positions are "No, we must never list victims names, and no, no compromise from that position is possible" versus "Yes, we must always allow all names of all victims, and no, no compromise from that position is possible"... We're not going to solve the problem and you're going to have these discussions forever. You will; I won't, because I will have forgotten about it, because I don't much care, because it doesn't matter, really. The best-for-the-Wikipedia thing to do is to fix this problem. Holding fast to an entrenched position -- any position -- is not the best-for-the-Wikipedia thing to do. There's no core policies at stake here, and there's no "right" or "wrong" position. Give a little. Herostratus (talk) 02:24, 20 November 2018 (UTC)

Totally unfair. Not one editor has said we must "we must always allow all names of all victims, and no, no compromise from that position is possible". Not one. Nobody has denied that there are many policies and guidelines that might justify excluding a name (or any other fact), such as WP:N, WP:BDP, WP:WEIGHT, WP:MOS, etc etc. Disputing that there is are universal grounds exclusion does not assert that there are never grounds for exclusion. There has been a straw man that we are insisting that we name thousands or millions of casualties for every war, but that is but a straw man. Funny how fake news works: they repeat a falsehood often enough and eventually a lot of people start thinking it must be true. --Dennis Bratland (talk) 22:28, 21 November 2018 (UTC)

Opppse. Just for the record. My reasons are already documented. - wolf 15:51, 20 November 2018 (UTC)

Victim lists proposal #2

As a different suggestion, I would argue that fully sourced victim lists can be listed over at Wikisource and linked back to the en.wiki article, eliminating any victim lists within en.wiki. Articles in prose can still discuss notable victims and talk about specific victims that had a role in the event, but the tables should be omitted in favor of the Wikisource version. (This also makes those lists available for other Wikiprojects). --Masem (t) 00:30, 20 November 2018 (UTC)

Why at Wikisource? Why not a separate page on Wikipedia? Why wouldn't a separate article called "List of decedents in XYZ tragedy" serve that purpose, and only in instances where space constraints require that solution? Bus stop (talk) 00:42, 20 November 2018 (UTC)

I don't think that Wikisource accepts those. Wikidata would, and Wikibooks might. WhatamIdoing (talk) 00:58, 20 November 2018 (UTC)

This is quite a good idea I think. Herostratus (talk) 02:18, 20 November 2018 (UTC)

Wikidata sounds fine by me.--Sturmvogel 66 (talk) 02:34, 20 November 2018 (UTC)

Wikidata sounds good. The proponents of these lists state that they have some sort of informative nature, data wise. Wikidata sounds like the perfect place for this kind of info. Numbers, birthplaces, occupations....that's all uncontextualised data. How about it @Bus stop: and @Dennis Bratland:? You get to keep these lists and encyclopedia articles will stop looking like bad journalism. Otherwise, there is absolutely nothing from preventing people from making lists of Holocaust deaths, deaths in the World Wars, deaths in automobile accidents in (insert region). Why is a person who died in a collision more important than a Holocaust death? Or what is the difference between a ship collision or an automobile collision? Because one was a soldier? Well then, what if it was a soldier travelling to work? Those sailors on the ship were sleeping. Llammakey (talk) 12:41, 20 November 2018 (UTC)

Whether is Wikidata/Wikisource/whatever, I am fine with any sister project that is designed to take raw data without additional commentary. That's the whole point of the suggestion. --Masem (t) 15:10, 20 November 2018 (UTC)

And yes, this could be used for things like Victims of the Holocaust. The only key criteria is that the lists should primarily be sourced to reliable third-party sources... an obvious "next step" I could see would be arguing for the alumni of every high school and college on the same principle, but those lists are not published by third-parties (outside local papers), and thus not appropriate. --Masem (t) 15:16, 20 November 2018 (UTC)

Both of the two proposals so far follow the unexamined premise of here, that casualty names in articles and lists are becoming a problem. Not so. They have always been an unresolved bone of contention. There has never been strong consensus on what this policy means.
I strongly suggest going to the WP:NOT archives and searching for NOTMEMORIAL and similar terms. Review the perennial debates over this policy. NOTMEMORIAL was added in 2004, and in the 14 years since, it has been tweaked slightly here and there, and a lot of effort has gone into what belongs in the non-article namespaces. But the part about the article namespace has not really changed meaningfully, and the meaning has remained controversial throughout.
This isnt like COI or BLP or RS, where new editors have trouble understanding policy, but after some time and experience, we all converge on a general agreement on why these policies exist and what they mean. Wikpedia's best, most experienced editors split into two entrenched camps on whether or not 'not memorial' applies only to article creation/retention, or if it also restrictes consents within articles. No revision of the text in 14 years has touched that simple question because there is no consensus on that question.
It would be great if a proposal could pass that said in plain terms whether or not, like WP:NNC (Notability guidelines do not apply to content within an article), it does or does not limit content of articles. If anyone thinks they can win global consensus for a clear decision one way or the other, more power to them. Please do so, and put this debate to rest.
From what I can tell, it won't pass because Wikipedia is deeply divided. If we can't agree on that, then we have to admit that NOTMEMORIAL isn't much of a policy, since it doesn't represent a global consensus. There is probably global consensus that content with no purpose other than to honor the dead doesn't belong. But the obvious question "does this content in this article serve no purpose except to honor the dead?" has to be answered on a case by case basis. Decided by local consensus. No easy appeal to the top-down dictates of policy, like some simplistic 10-victim rule. No way is there global support for assigning an arbitrary numeric limit like 10 casualties, and no way is there consensus to shift all of it over to some other wikiproject.
The best, most realistic outcome would be a frank admission that this isn't something that Wikipedia has a firm position on, and it will vary from article to article. There are beautiful FAs and FLs with no casualty names mentioned, and beautiful ones with non-notable casualties included. It depends, and that's fine. --Dennis Bratland (talk) 04:02, 20 November 2018 (UTC)

It will (continue to) vary from article to article only because the participants vary. The arguments do not vary from article to article. (While I haven't survey-studied all past discussions to make sure that's a 100% true statement, I've made the claim numerous times in numerous venues and it has never been disputed, let alone shown to be untrue. I think that's a reasonably fair test of its accuracy. It's true for the half-dozen or so article-level discussions where I've participated.) ―Mandruss ☎ 13:41, 20 November 2018 (UTC)

Reading on, I see your comments about a ship collision. Note that I'm speaking only of articles about random mass killings. The wider the scope, the more complex the question and the less likely any consensus will be achievable. I suggest keeping the scope narrow for that reason. Random mass killings have very little in common with ship collisions, so I don't see how it makes sense to lump them together. ―Mandruss ☎ 13:58, 20 November 2018 (UTC)

Can anyone point to an article that they feel has been negatively impacted by the inclusion of lists of non-notable victims? Bus stop (talk) 06:01, 20 November 2018 (UTC)

Comment - Using this article as an example, it is about a collision between two ships. There are people involved that are mentioned by name because of their role in the investigation and its outcome, and they are already notable per WP:MILPERSON. There are otherwise non-notable people mentioned by name because of their involvement in the cause of the collision and/or the outcome of the investigation (eg: the commanding officer was criminally charged). As a result of the collision, seven non-notable people died. This is where the debate comes in: there is no need to add these names, either as a list or in prose. They have no relevance to the article. Except for the few people that might actually know them, these names are essentially meaningingless. You swap out any of those names for "John Smith" or "Bob Jones" and it would make no difference to the reader. The names do not lend, in any way, to the reader's understanding of the subject matter in the article. They have nothing do with the cause of the collision, they play no active role in the outcome. They just had the misfortune of dying. Noting that seven people died and they were all from the US ship is all that is needed, along with the numbers injured from each ship. Adding the names just needlessly memorializes them and Wikipedia is not an obituary. A couple editors, specifically Dennis Bratland and Bus stop, have argued vehemently to have the names included, but so far, despite numerous posts on multiple pages over several days, have failed to show how these names are in any way relevant to the article.
This is an example of same type of debates taking place on multiple pages, with these two, and a few other like-minded editors, arguing to have memorial lists of non-notable victims in articles about mass-death events. Some of these pages now have these needless lists, and they are being used to bolster an WP:OSE argument in support of even more such lists. This is why we need clear language in a WP policy to address this, and prevent further debates which have become massive timesinks, for years now, causing a great deal of discord, disruption and clearly irrelevant content. - wolf 07:44, 20 November 2018 (UTC)

thewolfchild—you say "Some of these pages now have these needless lists, and they are being used to bolster an WP:OSE argument in support of even more such lists." Yet I also find you saying "OK Dennis, you go make a case for having a list of everyone killed in World War II (would want to leave any WWII article readers "hanging" now, would we?)" Aren't you making an Other stuff exists argument right there? Isn't your reasoning that we don't have a list of all the casualties at our World War II article (50 to 85 million fatalities) therefore we should not list the casualties at the "USS Fitzgerald and MV ACX Crystal collision" (7 fatalities) as seen in this version of the article in the "Casualties" section? Bus stop (talk) 23:29, 20 November 2018 (UTC)

"Yet you also find me saying"...? Are you trying to paint the two comments as contradictory? - wolf 00:24, 21 November 2018 (UTC)

Referencing the World War II article when discussing the USS Fitzgerald and MV ACX Crystal collision article is an WP:OSE argument, isn't it? Bus stop (talk) 01:35, 21 November 2018 (UTC)

Erm, you seem to be missing the whole point of an "OSE argument", which is "justification". For example, Dennis tried to use the Titanic passengers page to "justify" adding those seven names to Fitzgerald/Crystal collision page. So I was then asking if that in turn justified having a list of all the WWII victims. That's not me "making" an OSE argument, it's asking how far he was willing to take his. Let me know if you need anything else explained, I'm happy to help, as long as we remain on topic. - wolf 01:58, 21 November 2018 (UTC)

You also said to me "But we no more need their names to complete this article than we need a list of the names of all ≈80 million people that died in World War II to complete, or understand, any of the articles here about that subject." Bus stop (talk) 02:13, 21 November 2018 (UTC)

Actually, there was more to that comment; "Again, I will ask you; how are these names pertinent to the article? How do they lend to the reader's understanding of how the collision occurred, and what transpired after? Yes, seven people died, and that is noted. But we no more need their names to complete this article than we need a list of the names of all ≈80 million people that died in World War II to complete, or understand, any of the articles here about that subject." Unfortunately, Dennis jumped in there right after and I never did a response from you. So how about answering those questions now? (It's somewhat overdue). Thanks - wolf•

thewolfchild—you want me to now respond here to a post you made on an article Talk page 5 days ago? OK. You ask "How do they lend to the reader's understanding of how the collision occurred"? We are not only concerned with "how the collision occurred". That is an area of inquiry that you are putting before us. But it is hardly the only area a reader might inquire about. What you are studiously avoiding is the version of the article containing the so-called victim list. It is a section called "Casualties". It tells us the positions aboard the vessel of each of the deceased, their names, their ages, and their home towns. We are not only concerned with "how the collision occurred". We are also concerned with the identities of the deceased. The names are proper nouns and they don't really shed light on the particular question you pose.

But proper nouns of this sort are not unusual at all. Why are we told at the Thousand Oaks shooting article that it takes place at the "Borderline Bar and Grill"? Please tell me why we are giving the reader that proper name. And the name of the perpetrator—why do we need to know it was "Ian David Long"? Please explain to me why we are giving the reader that proper name. Now that the reader knows it occurred at the "Borderline Bar and Grill" and that the assailant's name is "Ian David Long"—do they now understand the event? I'm obviously not arguing against providing this information. Quite the opposite. A reader wants to know these specifics. There are specifics that can be dispensed with. But brief, rudimentary identification of key components is best included in an article. This gets us back to "who died"? Omitting that is truncating the article. I would contend the "Thousand Oaks shooting" article is a truncated article. The names and ages of the deceased should be included and unfortunately they are not. That is a defect in the article and it should be corrected by adding rudimentary information related to their identities.

Finally, we have articles such as The Perfect Storm (film) and The Perfect Storm (book). Didn't Sebastian Junger have to know information about the deceased such as their home towns? Don't writers consult Wikipedia articles? To the article's credit, the crew of the "Andrea Gail", upon which Sebastian Junger's book is based, though the 6 crew members are "non-notable", are noted in our article by name, age, and hometown. Bus stop (talk) 20:57, 21 November 2018 (UTC)

You are the one that brought up the (partial) quote from the Fitzgerald/Crystal collision talk page (and have done so about a half-dozen times). I just pointed out that the quote was incomplete, that you never responded (and why), and asked if you would respond now, considering all the questions you seem to expect me to answer.

You still have not addressed the questions I asked. Instead, you abbreviated the quote to a single question that suits you and then launched into a lengthy reply where you've now introduced yet another article, this one about a mass-shooting.

As with any mass-death event, the names of the non-notable victims are irrelevant (unless they are individually notable, outside of the event, or had a notable role in the event, other then dying). In a mass-shooting, the name of the shooter is notable and relevant (do you dispute that?). I don't really have an opinion on the name of the bar, but if it's just a random, average bar, with no bearing on the event, I don't see a reason to name it. If the event takes place a location relevant to the event, (eg: a gay bar, and the perpetrator was homophobic) or notable location, (eg: Disney World), then yes, the location should be named in the article.

The seven names are not relevant to the ship collison article and you still haven't shown how they are. You just keep going on about how we should include these names because the readers might be interested in them, though you also admitted you have no idea why they would be.

"This gets us back to "who died"?" - Who cares? Except those few who might actually know these people, and as has already been made abundantly clear to you, Wikipedia is not an obituary.

If writer's are "consulting" Wikipedia articles for research, they should be using the sources cited in those articles. That is why we add them, so people can verify content. if they can't find the names of mass-death event victims in the sources, then those names shouldn't be in the article anyway. - wolf 23:44, 21 November 2018 (UTC)

thewolfchild—how would you justify omitting the name "Borderline Bar and Grill" from the article Thousand Oaks shooting? You say I don't really have an opinion on the name of the bar, but if it's just a random, average bar, with no bearing on the event, I don't see a reason to name it. Bus stop (talk) 09:03, 22 November 2018 (UTC)

I don't see why I would need to "justify" that, but I did explain my reasoning for it already. Conversely, I take it that you believe the article absolutely must have the name of the bar included. Why? What bearing did it have on the either the cause or the outcome of the event? How does adding that name, as opposed to simply saying "a local country & western bar", lend in any way to the reader's understanding of the event? - wolf 17:49, 22 November 2018 (UTC)

Short numbers of names (as proposed by Herostratus above take up a handful of bytes and don't seem too out of place (users read articles, not policies). For longer lists why not simply create a page "List of victims of XYZ" and hat-note to it? Martin of Sheffield (talk) 07:57, 20 November 2018 (UTC)

Thewolfchild, I pointed to sources that gave detailed reasons why the particulars of the 7 casualties mattered, and why they were not interchangeable with just any 7 people anywhere. You have repeatedly claimed nobody has given you reasons, and every time I remind you that indeed I have, you ignore it. Now you’re coming here to repeat the same false claims. If you disagree with the reasons that were given, you could criticize them directly. But instead of doing that, you pretend they don’t exist, and repeat your demand to be told what value the names add. I told you, others told you, and you responded by demanding someone tell you. What you’re doing is called sealioning. --Dennis Bratland (talk) 08:42, 20 November 2018 (UTC)

So, resorting to insults now, Dennis? That's disappointing. You've lowered yourself and diminished your standing in this debate. I have read all your lengthy comments, it's one of the reasons I mentioned you by name. I have not "ignored" your responses, the fact remains that despite all the "reasons" you've given, you have not provided any kind of sufficient rationale to justify the inclusion of those names. You have not shown how they, in any way, are encyclopaedic, relevant to the article, or enhance the reader's understanding of the article's subject matter. You keep claiming that none of the policies or guidelines cited by any opposers apply, while relying heavily on wp:ose as a justification to add those names. Tell you what; explain why those seven are so special, or explain why WP should list of all 2300+ military personnel killed at Pearl Harbor, all 2900+ civilians killed during 9/11, or all 80 million people killed during WWII. You can't justify one without the other. - wolf 15:36, 20 November 2018 (UTC)

Insults? Listen to the way you denigrate the editors whom you don't agree with. You describe them as unresponsive, unreasonable, criticize them for lengthy responses yet go on and on repeating the same demands for answers. You get answers that you happen do disagree with, and instead of simply saying so, you paint those who disagree with you in a negative light. But you're the one who feels insulted?

It would be much more productive to 1) stop re-fighting the Fitzgerald ship collision debate. You won, in case you forgot. Never seen anybody complain so much after getting a majority of editors to support them. Hate to see how bitter you can be when you don't get your way. Let it go now. 2) Seriously read the old discussions on 'not memorial'. The ones from 2006, the ones year after year after that. The thing to notice is how many editors (names you recognize as admins, from writing FAs, as leaders with years of contributions) confidently see a place for lists or prose mentions of people who were casualties but not main actors in events. Your point of view has many adherents. Many fine, experienced, important editors. But there are just as many fine editors who don't feel obligated to list thousands or millions of dead for every event, just because they do list some names for other events. You say "You can't justify one without the other" and that's fine. Many editors think a consistent standard applies to every event of any kind, and many say, no, it depends. For 14 years, nobody has formed a strong consensus on it.

Maybe now you can change that and get a policy change that settles it. But history suggests you won't, in which case you ought to try to make peace with the reality. --Dennis Bratland (talk) 16:58, 20 November 2018 (UTC)

Riiight, I've been just awful, haven't I, Dennis? Look at how deeply I obviously hurt you with my scathing comment about kittens. As for the topic at hand; I simply cited the Talk:USS Fitzgerald and MV ACX Crystal collision discussion as an example of the issue being debated, and the reason that Ad Orientem wisely brought this here for a wider audience and hopefully some kind of solution. I didn't even mention the consensus there. Aside from the topic, I only mentioned that you and BS are arguing for the inclusion of non-notable names of victims. And while I just used the word "vehemently", I could've said 'page-dominating, persistent bludgeoning'... but I didn't. And don't need to either. People can just look at that page for themselves, or here, or here, or here or... here. These are all current talk page debates involving this topic, and a helluva lota' posts by you. Now, I tried this once before, and you blew it, but I'll try it again; I've said what I've needed to say here, (unless there's another proposal, or someone replies to me), so I will now step back and allow others to discuss. You've said enough, haven't you? How about you do the same? I think you can do it... this time. G'nite - wolf 00:13, 21 November 2018 (UTC)

Please stop. --Dennis Bratland (talk) 01:03, 21 November 2018 (UTC)

I could, I've already shown that. The question is, Dennis; can you? - wolf 01:58, 21 November 2018 (UTC)

@Martin of Sheffield; it's not about size, it's about relevance. Non-notable victims of mass-death events simply do not need to be mentioned on WP for any other reason than being one of the unfortunate to die in that event. Wikipedia articles are not obituaries, it's not the purpose of an encyclopaedia to memorialize such people. However, if people want to find or create a well-sourced off-site list and link to it as an external link, that is a different matter. - wolf 15:47, 20 November 2018 (UTC)

Support. Just for the record. I don't see a problem with this proposal at this time, as I just mentioned in reply to a similar comment just above. - wolf 15:54, 20 November 2018 (UTC)

Victim lists proposal #3

Bare lists of victims, which only compile names and basic information (age, birthplace, occupation, etc.) are to be deprecated. Victims of crimes and disasters and other tragic events may be named as a normal part of a quality prose narrative, but lists of names with no context are not useful to most readers anymore than lists of names are in other Wikipedia articles, and advice for creating lists of names of otherwise non-notable people are as applicable to victim's lists as anywhere else in Wikipedia, and victims lists are not accorded any special exemptions from the normal practices of creating lists of otherwise non-notable people.

The goal here, is not to scrub the names of victims from articles, but to avoid the bad writing of slapping in "contextless" lists just because, or to afford "special status" to people because they died during a notable tragic event. The role of Wikipedia is not to create a remembrance of people who died in such ways, though we should also not be afraid to include names where the actions of those people during events would have come up anyways in the course of writing a prose narrative about the event. Simply put: if you think a person's role in an event in which they died bears coverage, it should be covered in the prose narrative. Simply creating a contextless list of non-notable people is not good writing, in this type of article or in any other. --Jayron 32 12:07, 20 November 2018 (UTC)

In the case of random mass killings, there are often a few reliable sources reporting enough about each victim that someone could construct what they believe to be a "quality prose narrative" that includes every victim. So, for those who oppose the lists largely for privacy reasons (in the same spirit as WP:BLPNAME), this proposal as worded does nothing to address those concerns.
What each victim was doing, or what they said, just before they got killed is simply not encyclopedic information, but news organizations report it because they are not encyclopedias. Similarly, we rightly omit much of the tabloidish play-by-play detail about the killers' movements and actions in these events.
Further, inclusion of little bio blurbs about each victim—that she was a mother of three and he was active in school orchestra—is nothing but memorialization, feeding the purely emotion-based desire to give the victims as much individual attention as the killers. Again, that could and would be considered a "quality prose narrative" by some editors. ―Mandruss ☎ 14:16, 20 November 2018 (UTC)

Which we could thus probably add in a bit of BLP1E: if the names of persons that are victims of these events meet BLP1E, then even if there are mini-bios of each person from RSes at the time of the event, we don't include them. (The fact that they are generally memorialized that way is, to me, a sign of sensationalist news reporting, to prey on sympathy from the reader, which at WP , has no place). --Masem (t) 15:08, 20 November 2018 (UTC)

No, the point is that we don't treat victims of tragic events differently than we treat people in any other event. If a person does something worth note in an event, we don't conspicuously avoid naming them during the narrative. For example, let's say we have some fire which dozens of people die, and one of the victims rescued several people before succumbing. Let's also say that consensus is that this part of the story is relevant to the overall narrative. Saying "John Doe, one of the residents of the building, rescued several other residents before dying himself in the blaze". If John Doe's involvement is important enough to the story of the event, we don't avoid naming him. What we shouldn't do is include the names of people whose role in the story is not noteworthy of itself except that they died. "Jane Smith was watching TV when she died in the blaze" is a rather mundane event. "Jane Smith was watching TV" is not, under normal circumstances, a relevant, noteworthy detail of her life. That she died while doing it is unremarkable, so it doesn't bear writing about in the event. So we needn't mention that event (thus not her name) in the narrative. If she did nothing in the course of the event that is important for the narrative, then we don't also need to create a list of victims just to make sure they are named. Naming is not of itself sufficient reason to include. If we would include a person anyways, go ahead and name them. If we have no other reason to include them except that they were present and died in the event, we shouldn't. Just like we wouldn't include a complete list of people who were present, in an unremarkable way, at other events. --Jayron 32 16:30, 20 November 2018 (UTC)

@Jayron32: Fine, but you're reading a ton into "quality prose narrative" that is not present in the proposed language. Many others will interpret that vague phrase very differently; instead of endlessly debating the meaning of NOTMEMORIAL, we would now be endlessly debating the meaning of this new guideline. My goal is to substantially reduce the endless debating, and in fact that's a goal consistent with the heading of this level 2 section which I didn't initiate. ―Mandruss ☎ 17:02, 20 November 2018 (UTC)

That's fine. Lets work out a better wording then that captures the spirit of the proposal, but has less ambiguity here. This is VPIL and not VPP for a reason. This isn't a vote, this is a workshop to create the new policy so we have good stuff to bring to a vote. Feel free to propose something else. --Jayron 32 17:08, 20 November 2018 (UTC)

@Jayron32: Ok, let me sleep on it once or twice. It's far easier to shoot something down than to offer a better solution, I know. ―Mandruss ☎ 17:16, 20 November 2018 (UTC)

"Simply creating a contextless list of non-notable people is not good writing, in this type of article or in any other." (Jayron32 12:07, 20 Nov) I precisely disagree. I prefer contextless lists in many instances. The crux of this discussion happens to be contextless lists of non-notable people. Can anyone point to an article in stable condition that is negatively impacted by a ~~contactless~~ contextless list? User:Thewolfchild above attempted to do that above but did not link to the past version which contained a section called "Casualties". It is worth examining that past version because I would contend it is constructive to the article. "Contextless" is not the negative quality it is purported to be. I'll admit that I was surprised that one of the most starkly contextless lists made it into the 2016 Oakland warehouse fire but even there I would defend it as entirely constructive to the article. I argue we do not have to digest all information for the reader. We are not producing articles that tie up all loose ends. It doesn't matter if some things do not make sense. We are discussing articles in which "senselessness" is a key quality. The argument some of you are making is to take away all crumbs of clues as to the nature of what transpired in the addressed event. Everything is a clue even if an incomplete clue. We should step back and let competent and seasoned editors that are familiar with our already-existing policies and guidelines do what they do pretty well—create articles on the unfortunately proliferating series of tragedies—especially lone gunmen shooting up establishments. No one would disagree that the senselessness of these events defy description. Consider 2017 Las Vegas shooting. Whether there is a victim list or not almost doesn't matter. We should let editors write articles. I think that in every instance that there is a victim list it is constructive to the article. What I find unproductive is the attempt to control other editors. It is not the end of the world or the doom of Wikipedia if "contextless list of non-notable people" are included in articles. Bus stop (talk) 15:24, 20 November 2018 (UTC)

Can anyone point to an article in stable condition that is negatively impacted by a contactless [contextless] list? That's the second time you've asked that question in this discussion. It was ignored the first time I suspect because it's such a vacuous question (that's certainly the reason I ignored it). List opponents feel that any article containing a list is "negatively impacted" by it—for the reasons we have thoroughly articulated in discussion after discussion, of which you are fully aware. That you disagree with those arguments goes without saying. ―Mandruss ☎ 15:31, 20 November 2018 (UTC)

Every argument you are making is countermanded by replacing "articles about events where there were lots of deaths" with "articles about literally anything else". Any argument you make for these types of articles should be applicable to articles on other subjects. What is the harm in including a list of every graduate from a University? What is the harm in including a list of every person who attended Live Aid? You've asserted that dying somehow makes these people special, but to make special note of someone merely because they died, and for no other reason, is the exact definition of a memorial. And consensus has determined that memorializing the dead is not, of itself, sufficient grounds for relevancy to an article. --Jayron 32 16:20, 20 November 2018 (UTC)

Mandruss—a productive discussion might involve not only pointing to articles negatively impacted by uncontextualized victim lists but also speaking about how that particular article is damaged by the presence of such uncontextualized victim lists. Can you possibly criticize this uncontextualized victim list? It contains Jewish names and ages. I contend that a reader derives tons of information from such lists—in almost every instance. Bus stop (talk) 15:49, 20 November 2018 (UTC)

Sure, that's illustrative. The article already clearly establishes that the dead were Jewish. You don't need "Jewish names" to show that (as if most readers know what a "Jewish name" is anyway). As for ages, that too can be summarized if it's deemed relevant; we could say that the dead ranged from 54 to 97. That's encyclopedic information. ―Mandruss ☎ 16:02, 20 November 2018 (UTC)

That's like saying we don't need additional information if we already have information asserting a given point. There is no rule about that on Wikipedia and there should not be any rule about that on Wikipedia. Why would you prefer a range of ages when a particular person, identified as male or female, can be associated with a particular age? And all Jewish names are not the same either. Jewish names can break down into more religious-sounding names and less religious-sounding names. The question which you are not addressing is what is wrong with the list. My original question was—can you point to an article and show how the victim list damages the article. We know there are alternative means of including information. But why are you going to great lengths to prevent other editors from creating an article such as the linked-to section of this article. Please tell me what is wrong with the present version of that article. Bus stop (talk) 16:28, 20 November 2018 (UTC)

Yes, the list bloats the article and includes information which is not vital to the narrative. --Jayron 32 16:31, 20 November 2018 (UTC)

"the list bloats the article" The article is not overly long. Bus stop (talk) 16:43, 20 November 2018 (UTC)

The length of the article is irrelevent. The level of detail is. Details which are not vital to the narrative should not be included, even in short articles. Look, you know that you don't win this argument by simply repeating yourself over and over, right? I think your position is clear, and I'm not sure it will be worthwhile to respond to your increasingly repetitive demands. We get it. You want to include the lists. Lets hear from other people on the matter. --Jayron 32 16:48, 20 November 2018 (UTC)

Why would you prefer a range of ages when a particular person, identified as male or female, can be associated with a particular age? For the reasons I've given in discussion after discussion, including several where you've been present and I know you've seen them. You have a particular talent for not hearing opponents' arguments, repeatedly demanding that they give reasons that they have already given countless times, and I'm beginning to fantasize about a topic ban from victims' lists. I'm not aware of a single other editor that does this in this topic area. ―Mandruss ☎ 16:37, 20 November 2018 (UTC)

"For the reasons I've given in discussion after discussion, including several where you've been present" I must have been out to lunch. Bus stop (talk) 17:02, 20 November 2018 (UTC)

Finally, something we can agree on. ―Mandruss ☎ 17:07, 20 November 2018 (UTC)

"You have a particular talent for not hearing opponents' arguments, repeatedly demanding that they give reasons that they have already given countless times, and I'm beginning to fantasize about a topic ban from victims' lists." Perhaps you should learn to repeat yourself. Just because you've said something once, especially in another thread, is not a reason you cannot say it again. You are shying away from debate. Bus stop (talk) 17:19, 20 November 2018 (UTC)

I promise to consistently "shy away from" repetitive debate. You know very well where to find my arguments if you truly have any interest in them. ―Mandruss ☎ 17:23, 20 November 2018 (UTC)

"I promise to consistently 'shy away from' repetitive debate." When a person asks you a question you should answer it. It is as simple as that. You don't know where they are going with their line of reasoning. You are stymying debate by constant grandstanding. Bus stop (talk) 17:33, 20 November 2018 (UTC)

No, what you're doing is trying to win the debate by sheer force of will: You seem to think that because you spoke last, you won. That's not how these things work. What you're doing is repeatedly asking the same questions over again, once you've been given the answers, as though by asking the question again, you invalidate the prior answer. That's called sealioning, and is not a productive means of reaching consensus. It's much better to make your point and go on. --Jayron 32 17:37, 20 November 2018 (UTC)

Jayron32—I think everyone is trying to "win the debate by sheer force of will". This is a debate between allowing editors of adequate competence to construct articles as they see fit, with Talk page discussion as need be, versus creating many more rules to supplement the already existing rules. WP:MEMORIAL actually does not apply to anything. That is because WP:BIO already serves the purpose of preventing the creation of articles on non-notable people. The question of whether there should be a list of victims is a simple decision best left to editorial discretion. My argument is simple. Bulleted lists have their value. I don't understand why a fuss is made over such lists. But if editors want to argue over them, let them argue over them on article Talk pages. In short I don't think Ad Orientem should have started this discussion. I'm sure Ad Orientem meant well but this is a can of worms. Bus stop (talk) 18:21, 20 November 2018 (UTC)

We actually do have a rule about arbitrary information, that's WP:NOT#IINFO (you could also argue that a victim list without context falls under WP:NOT#STATS too). --Masem (t) 17:07, 20 November 2018 (UTC)

This seems like a good proposal. If there's some information about particular victims that would be valuable to the encyclopedia and is well-sourced, then the names can be included as part of that. For example, if there were a disaster or shooting and many sources discussed the actions of one of the dead victims during the event, then that might be worth including in the description of what happened. If there are many sources about what a survivor did in relation to the event afterwards (activism, writing a book about it, whatever), then that might be included in the article as related. Basically, if a survivor's name cannot be included into prose containing some significant thing they did related to the event, then it probably shouldn't be included at all. Even if that's the case, inclusion should of course be subject to the normal BLP and NPOV restraints. I just don't know if lists of unlinked names should be included except maybe on list articles. Red Rock Canyon (talk) 15:54, 20 November 2018 (UTC)

Red Rock Canyon—I disagree. The absence of contextualization in this instance is not a problem. There is nothing that needs to be fixed. We are only talking about rudimentary details about lives lost. Not only does the inclusion of that material not matter but in fact it is constructive to the article. Bus stop (talk) 16:01, 20 November 2018 (UTC)

I think everyone knows you disagree. You've made yourself very clear in your 21 posts on this subject so far. Red Rock Canyon (talk) 16:04, 20 November 2018 (UTC)

Red Rock Canyon—"context", in the final analysis, is a red herring because tons of information can be conveyed in the absence of context. This version, which unfortunately has been reverted, tells us tons of information on the 7 people who died in a ship collision. How can that be construed as unconstructive to that article? Bus stop (talk) 16:37, 20 November 2018 (UTC)

Because it's not a encyclopedic summary of the incident. Too much detail.--Sturmvogel 66 (talk) 16:41, 20 November 2018 (UTC)

This is a proposal that is closely in line with my own thinking and preferences. -Ad Orientem (talk) 16:25, 20 November 2018 (UTC)

Support, in theory. Just for the record. Agree there shouldn't be lists. If a person, in the event being documented, is notable, either for having a bio/blp page of their own, or they played a notable role in the event, other than being injured or killed, then they should be noted in the article prose, along with appropriate sourcing. This proposal could work in conjunction with proposal #2. - wolf 16:42, 20 November 2018 (UTC)

I too like this proposal. I do feel though that we need a rider along the lines that Editors who wish to add names need to obtain consensus on the talk page to add them if challenged ie the default is no names and the burden to add is imposed on the editor who wishes to add. Lyndaship (talk) 16:44, 20 November 2018 (UTC)
I'm not sure I'd go that far. I think that we let people write the narrative, and if some event in the narrative is determined to be trivial, we remove that event. The name itself would go with it. Efforts to shoehorn in unremarkable text into a narrative are rather obvious, and most everyone will see through such efforts to work a "list" in the back door that way, per WP:GAME. However, WP:BOLD is still good policy, and we shouldn't demand that people avoid names during the normal writing process. Prior approval is not required for good-faith editing. --Jayron 32 16:52, 20 November 2018 (UTC)

This is an improvement on the previous proposals. There are different approaches to article content. But it's still simplistic, and it's one of those broad laws that only begs the question. What is sufficient context? Wikipedia has thousands of stand alone and embedded lists. Non-prose lists are very often a very good format, following various acceptable approaches found in guidance like Wikipedia:Stand-alone lists, Wikipedia:Manual of Style/Lists and Wikipedia:Manual of Style/Embedded lists. Saying names are fine in a quality prose narrative again begs the question. Now editors will debate whether the prose is of sufficient quality. Why not recognize that local consensus is what really decides all of this? If you're going to let local consensus decide whether a prose list is of sufficient quality, why not trust local consensus to decide if the article as a whole works structured one way or the other? There will never be global consensus for ideas as broad as "there shouldn't be lists". If embedded lists of casualties are bad, what about embedded lists of songs, even though none are bluelinked? Or a list of albums, some bluelinked, many not.
What about this embedded list of patents for things that are mostly not very significant in of themselves, but taken as a whole, tell a story. It brings us back to why we endorse redundant categories and lists and navigation templates and portals and prose containing the same information. A prose description of an inventor who has a long series of patents for inventions great and minor is fine, but the same information can also be given in bulleted list form, and for some readers, convey meaning better.
We can't prescribe what to do in every case in a top-down directive. Perhaps the real problems is treating names of the dead as a special case. Articles are full of things, in prose and in lists, and some of those things are highly notable, of great significance, and some of those things, names, patents, inventions, filmography or discography, that are worth mentions but not otherwise of great importance. It depends. --Dennis Bratland (talk) 17:30, 20 November 2018 (UTC)

We can't prescribe what to do in every case, but we certainly can decide on a default that would require a local consensus to override. Arguments to override would be required to show what sets the case apart from the majority. This would reflect the fact that the factors are the same in a very large majority of cases. As I expressed above, the scope should be narrow enough to make the preceding statement true for the cases within that scope; i.e. random mass killings wouldn't necessarily be covered by the same guideline as ship collisions or aircraft crashes. I see this as little different from different article title naming conventions for different categories of articles, which AFAIK has worked fairly well without an excess of debate or edit-warring. ―Mandruss ☎ 17:44, 20 November 2018 (UTC)
Sure, but do we need a policy-level directive for that? We already have a default: WP:LISTPEOPLE. It says bluelinked names. Then it goes on with "some common exceptions". WP:CSC does the same: lists of blue linked items, and plausible red links are the "standard", but lists of non-notable things are OK, though it cautions editors to "consider carefully". We have enough guidance here, we have a default, with "don't try this at home" cautions for those daring to try advanced kung fu. What we need is to focus on the perpetual debates caused by WP:NOTMEMORIAL's vague wording. Admit consensus doesn't support it limiting article content so we can stop arguing over it and focus on more subtle discussions over whether this list in this article makes it better or not. --Dennis Bratland (talk) 17:53, 20 November 2018 (UTC)
Clarification: LISTPEOPLE does not say "bluelinked names". It says that the most common (=not the only allowable) criteria is "notable people". This means red-linked names if the person is notable, but nobody has written the article yet, then it's acceptable, but a blue-linked name that was redirected because the person isn't notable is not acceptable. WhatamIdoing (talk) 19:08, 28 November 2018 (UTC)
Sure. I said "bluelinked names" as a shorthand for "meeting WP:BIO as a blue link to an article or a redlink to a plausibly notable article". I didn't think the word count here needed to go any higher and everyone generally knows enough about these guidelines to know what I meant.
Anyways: anyone who thinks not-memorial applies to both article topics and to content should propose plain English words to that effect. Lacking strong consensus for that, admit that there isn't strong consensus that it applies that way. Everyone agrees you can't create a new article about someone for no reason except as a memorial memorial; they have to be notable. Only some editors think this means mentioning a non-notable dead person carries any special burden that wouldn't apply to whether or not we can mention any other fact. --Dennis Bratland (talk) 00:34, 29 November 2018 (UTC)

I've never seen LISTPEOPLE cited in a victims list discussion. I assume the reason is that it applies to list articles. Same for CSC. For the most part—although "list of victims" articles have actually been proposed at least once in this saga—we're not talking about list articles but about lists within event articles. In my opinion LISTPEOPLE and CSC would support arguments for a new guideline establishing a default of omit, but they aren't substitutes for one. ―Mandruss ☎ 18:01, 20 November 2018 (UTC)
WP:USEPROSE applies specifically to embedded lists. MOS:LIST reiterates all these principles, for both types of list. There are cautions on indiscriminate items, poorly defined lists, not using lists when prose is better. It's all there. Maybe everyone is so busy arguing over 'not memorial' they don't take the time to look at the basic guidance on lists. You can have casualties on an embedded list, stand alone list, or enumerated in prose, but only if it meets numerous criteria for quality. What we don't have is a single policy that lets someone do a drive-by deletion of casualties in all cases with a simple "per policy X". They have to get down in the details, know the context, and collaborate. It's a good thing, and it does work. --Dennis Bratland (talk) 19:11, 20 November 2018 (UTC)
I hate to state the obvious, but if that were sufficient it would have sufficed. In years of these discussions, I've yet to see any arguments of that nature, let alone see them prevail. Even if they were made widely by the "omit" side, it would be a rare closer who would close in their favor if the "include" side had a clear majority and made reasonable-sounding arguments. The solution is to make the guideline simple and more specific, using all that more general stuff as its basis. You could call it a derivative guideline. I understand the WP:CREEP objection to something like that, but the status quo clearly isn't working and I prefer some CREEP to the status quo. ―Mandruss ☎ 19:24, 20 November 2018 (UTC)
It's not a guideline. If 'not memorial' were a guideline, rather than policy, it wouldn't be such a battleground. Policies are powerful weapons that let one nuke content wholesale, silencing dissent. Guidelines ask us to bend and compromise and see nuance. Demoting it to a guideline would accomplish much.
Or end the 14 years of debate over 'not memorial' by changing it match the de facto state of affairs: there is no global support for applying 'not memorial' to article content, only article creation/retention. For the sake of proving a point, we could start with a proposal to make it say the opposite, that it does limit article content. Succeed or fail, those proposals would shift the debate away from not memorial towards other content guidance like the list guidelines, as well as WP:WEIGHT and other guidance on content triviality vs importance. --Dennis Bratland (talk) 20:06, 20 November 2018 (UTC)

NOTMEMORIAL is used to limit content in articles. We have several articles that fall into "crime against a single victim" where the victim was not notable, most of these start with "death of..." or "murder of..." for example Murder of Meredith Kercher. Just enough information about her background is given to understand family member roles (in the case history) and why she was where she was when she was killed. Not a full blown biography with flowerly langauge to make Kercher seem any more important, only that the murder and investigation had drawn enough attention to be a long-term news story. That's proper application of NOTMEMORIAL. --Masem (t) 20:20, 20 November 2018 (UTC)
Wouldn't WP:BIO serve the same purpose? In my opinion an article title defines an article and suggests its scope (which is really two ways of saying the same thing). Bus stop (talk) 20:23, 20 November 2018 (UTC)
I agree with this proposal. Contextless lists of victims should be deprecated and the default position should be to avoid having them. But I wonder how far we'll get on this proposal.--♦IanMacM♦ ^{(talk to me)} 05:53, 22 November 2018 (UTC)

I think that the reason that LISTPEOPLE isn't brought up is because editors don't think it will help them "win". The most relevant guideline is actually WP:SOURCELIST, which turns out to be even less helpful. Translated and applied to the case of people who died during an event, it says "Include the victim's names when they're WP:DUE, and don't when they're not". And that leaves editors exactly where they started, with some people absolutely convinced that the names are never-ever-ever DUE, and some people absolutely convinced that they frequently are, and perhaps most of us really not caring unless it gets really unwieldy, but trying to stay out of the line of fire between the two entrenched camps.
The longer this argument goes on, the more I think that the problem might be most efficiently solved with a TBAN for about a half-dozen editors. WhatamIdoing (talk) 19:17, 28 November 2018 (UTC)
You can TBAN for persistent disruption, but you can't TBAN for caring too much about an issue. The problem here has not been with the participants, for the most part, but with the community's tendency to establish guidance that is so vague and watered down as to be completely useless, basically saying "If you feel X is better, do it; otherwise, don't do it." Duh. Thanks for all the help. Village Pump is frequented by too many experienced editors who can only sing one song: "Don't bother us, just go work it out in article talk." That's abdication of responsibility in my view. Perhaps the new discussion at VPP will bear fruit. Perhaps not. ―Mandruss ☎ 01:22, 29 November 2018 (UTC)
You're almost right about "guidance that is so vague and watered down as to be completely useless". If it's a should, and not a shall, then it belongs as a guideline, not a policy. Everyone gets that guidelines, like the extremely useful and successful MOS, are not ironclad, yet over time articles progress to meet that ideal, and those exceptions that need to deviate either gain consensus or lose it. Mere informational pages, like WP:WBA, are extremely influential even though the lack any force of law. NOTMEMORIAL wouldn't be such an odd duck if it were a guideline. As a policy, it's an embarrassment, precisely because it doesn't represent a global consensus. If it did have a strong consensus behind it, the language would have grown tighter and more clear over the last decade and a half, not remained mired in dispute. --Dennis Bratland (talk) 02:17, 29 November 2018 (UTC)
For anyone else who is seized by curiosity: our longest policy uses the word should 58 times. WP:COPYVIO uses it 12 times, and WP:COPYRIGHT uses it 11 times. The Terms of Use use it 8 times. I don't believe that the should–shall distinction reflects our actual practice. WhatamIdoing (talk) 06:28, 30 November 2018 (UTC)
Support There's a lot of text here to wade through to get down to the bottom of this discussion. I've come to the following conclusions based on what I have read: 1.) Something aught to be done to address the problem, something specific so that editors can stop debating the point so often, and 2.) the arguments like "we need to know victims' names in order to understand the context" are utterly unconvincing, right up there with "It isn't hurting anything to include such a list" (um, yes it is: it hurts my attention span, even if the article is short) and "it is constructive to the article.to include this information" (which is so subjective it makes me want to vomit in terror). I am not convinced that leaving the issue up to individual articles is a best option because that is exactly where it seems the conflicts keep taking place. We could probably use a guideline that reigns in editors who feel compelled to add these lists, because those editors seem to be doing it for the wrong reasons (i.e., memorialization, beneath a veneer of contextualization). I have never been a participant in those debates, and at a certain level I do not care. But as a Wikipedia reader, I would be truly annoyed to come across these victims' lists because in most cases I would only come away believing, "Well, I guess if *I* die of lung cancer some day, maybe MY name will get to be on a Wikipedia list of 'Victims of lung cancer'.'" Because, you know, I DIED from it! You have to know who I am to understand the context! (no, ah, no you don't, not really). A loose noose (talk) 10:01, 24 November 2018 (UTC)

I don't think we exclude material because individual editors find annoyance in inclusion of that material. "But as a Wikipedia reader, I would be truly annoyed to come across these victims' lists" Bus stop (talk) 15:30, 24 November 2018 (UTC)

Support option 3 (support option 2 as additional, and oppose option 1, although for consistency even option 1 or the terrible counter-option "all crimes must include a victim list" would be better than repeated rehashing of the question). Where identification of particular victims, whether killed or injured or unharmed, is necessary to understand an event, whether criminal or otherwise, they should be included contextually in the article. Where their individual inclusion is not necessary to understand an event, they should not be. If there ever happens to be an event with an overwhelming quantity of notable (bluelinked) victims, then including a list of those would be reasonable. ^~Hydronium^~Hydroxide^~(Talk)~ 02:22, 25 November 2018 (UTC)

Gross Page size change

In the edit record of edits on the watchlist, there are indicators next to every edit detailing the "page size change in bytes". This is obviously a very useful tool for the most part, determining when someone has removed or added a large amount of information to the article and so can be used to detect major changes. However, there are occasions where pages are edited in very large fashions, such as a restructuring or cleanup, that add a lot in some places but delete a lot in other places. Because of this, substantial edits are made to seem smaller because the net gain or loss is small.

My proposal is to add a second indicator that details the gross change in bytes. This way, large restructurings that have net byte change of zero are still shown as more significant than other, more minor edits. After thinking of different ways to do this, I have come up with two ideas: First, a second parenthesis could be added that details gross and is bolded if the gross change is more than 500 bytes, or the current parenthesis bracket could be expanded in a way that shows something like (gross change, +/- net change), where if the net change is high, the whole thing is bolded that color, while if the net change is low but the gross change is high, the indicator is bolded blue (for small nets and gross, the gross could stay blue and the net could be whatever color?). Thank you for your time, IntegralPython (talk) 03:33, 30 November 2018 (UTC)

Do you have any examples of major edits being hidden in this way? They must be extremely rare. I don't recall ever seeing one. I've seen many edits that show zero bytes change, or some low number where the actual change involved more bytes, but these are invariably something quite minor. I wouldn't count refactorings like changing section order as being a major change. That doesn't significantly affect the information. SpinningSpark 08:12, 30 November 2018 (UTC)

Looking back on it, it may not be as common as I initially thought. I have edits show in drop down groups on the watchlist, so when it displays the summary in the header of said group, many times reverted edits show as (0) when in fact there was a large edit that was then reverted. This also happens to me when people make many small changes to an article in different edits, so I see now that most of what I was thinking about will not apply to most users. I might try in some time to make myself a js that does it for me. Thank you though, IntegralPython (talk) 15:02, 30 November 2018 (UTC)

Flicker Creative Commons

I think CC-BY-NC-ND, CC-BY-NC-SA, CC-BY-NC, CC-BY-ND (all creative commons) Flicker images should be allowed here on the English Wikipedia. I found this discussion on the commons about the same issue (c:Commons_talk:Flickr_files#Why_are_NoDerivatives_&_NonCommercial_not_allowed?) and it got a reply saying some Wikipedias allow these types of Flickr images to be uploaded locally but not globally (as the commons does not allow them as the commons does more the just illustrate Wikipedia). Using the images locally wouldn't be a commercial use as Wikipedia is not an commercial entity, so these images should be allow to be uploaded to Wikipedia. – BrandonXLF ^(t@lk) 02:58, 1 December 2018 (UTC)

c:Commons:Licensing/Justifications explains the importance of allowing derivatives and commercial use. It wouldn't be copyright violations to upload those CC NC or ND licensed flicker images. But in the same vein, we could use a lot more images under fair use than we do currently; the point of being strict about having truly free images and limiting non-free images is so that Wikipedia remains a truly "free" encyclopaedia; both free to use, and free to re-use in any manner (see WP:5P3). Galobtter (pingó mió) 03:15, 1 December 2018 (UTC)

Feature Request: Add a 'Reading-mode' button to ease the reading of Wikipedia's articles

Hi,

I wish to read for hours articles as any user, but it occurs that the reading (on PC) of these articles is not enough comfortable as the white color background tires my eyes. I have to stop reading for a moment.

I wish to see a button called 'Reading-Mode' located before the title of article (Eye icon). By pressing this button, it will allow me to change the white color background of the article to a gray or yellow color (see example below). The purpose will be to let me choose as user what make my reading more comfortable.

example: https://i.stack.imgur.com/7RYcp.jpg — Preceding unsigned comment added by Alexmio (talk • contribs) 14:32, 14 November 2018 (UTC)

@Alexmio: Wikipedia is always in "reading mode" unless you click the edit button. However, if you want to change the background color, you can do so by adding the following line to your common.css file, located at Special:MyPage/common.css (replace #F1ECE8 with the color of your choice):

.mw-body {background-color: #F1ECE8;}

If you want to be able to toggle it with an eye icon, you can instead insert the following into your common.js file, located at Special:MyPage/common.js (replace #F1ECE8 with the color of your choice):

var readingBG = "#F1ECE8";
mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Ahecht/Scripts/ReadingMode.js&action=raw&ctype=text/javascript' ); //[[User:Ahecht/Scripts/ReadingMode.js]]

--Ahecht (TALK
PAGE) 17:37, 14 November 2018 (UTC)

Many of us that use Google on our 60+ inch TV's add the "Dark Mode" extension - chrome://extensions/?id=dmghijelimhndkbmpgbldicpogfkceaj . Simply a toggle button.--Moxy (talk) 21:15, 14 November 2018 (UTC)

This link goes to the extension on the webstore; I personally use this extension in general but use this nice vector dark skin on Wikipedia. Galobtter (pingó mió) 07:56, 15 November 2018 (UTC)

Firefox also has something known as Reader view which removes a lot of clutter. There are probably extensions available for other browsers. Besides what others have noted above, you can also install a dark theme.—Cpt.a.haddock (talk) (please ping when replying) 11:31, 15 November 2018 (UTC)

There's a related wishlist item you can vote for: m:Community Wishlist Survey 2019/Reading/Accessibility settings for everyone.
Sidenote: @Alexmio: I occasionally use a bookmarklet to achieve this at various websites. You just drag the link given there into your bookmarks/bar, edit it to change the two instances of "tan" to "#F1ECE8" (screenshot), and then use it whenever you want at any website. Quiddity (talk) 00:43, 25 November 2018 (UTC)

I sympathize. I use this user stylesheet for en.wikipedia.org:

#mw-head-base, #content, #mw-navigation {
    background-color: #f3f3f1; /* 6S 95L */
}
#toc {
    background-color: #e7e6e4;
}

It sets everything to roughly the TOC's default background, then darkens the TOC accordingly. —wing gundam 02:17, 2 December 2018 (UTC)

article assessment system is in need of repair

Hello, I'm a pretty new editor here...maybe one month. At first, I kept encountering lots of "class C - high importance" pages. So, I just assumed they were bad. But, then I started leaving messages on various WikiProject Talk pages and never get a reply. I assume they are dead? Even though they seem to have many members. Finally, I decided to get a "start class" article reassessed. I go look at one WikiProject assessment page and they have a queue of 11 articles and the oldest one is from 2013...five years waiting for reassessment!

So, my question to Idea Lab is whether Wikipedia needs to do something about article assessment by the WikiProjects. Perhaps a better messaging system is in order? Well, that was my one idea. Thanks for the consideration! Seahawk01 (talk) 04:56, 27 November 2018 (UTC)

User:Nettrom and User:EpochFail have been working on WP:ORES scores for articles, so that we can automate some of this. But the general rule of thumb is: if it seems significantly incorrect, then you should Wikipedia:Be bold and fix it.

The easiest cases are articles that are marked as stubs but are obviously too long for that status. (My favorite rule of thumb: if it's got more than 10 sentences, then it's not a stub.) The absolutely minimum case for B-class is that every content section (not counting the introduction or ==See also== or anything like that) contains at least one Wikipedia:Inline citation. With those two ideas in mind, and the willingness to walk away from any dispute and let the other editor(s) have their way, you could probably find and fix many outdated assessments. (The full rules are at Wikipedia:1.0/Assess, but they are only followed approximately, so don't get too hung up on the details.) WhatamIdoing (talk) 19:34, 28 November 2018 (UTC)

Seahawk01: There is also a script to make article assessment easier — see WP:RATER. — pythoncoder (talk | contribs) 23:05, 28 November 2018 (UTC)

Thanks WhatamIdoing, I left messages with both User:Nettrom and User:EpochFail offering some simple suggestions on improving article quality ratings. Seahawk01 (talk) 01:48, 1 December 2018 (UTC)

WhatamIdoing and pythoncoder, thanks...great information about assessments. But, I'm still a bit confused about how assessments and Wikiprojects intersect. Maybe it will all come to me in a flash over the next week or two...I'm still a bit new :-)

Also, I would say that part of this post is about assessments, but part is a general complaint about dead Wikiprojects...or at least lack of communications inside the Wikiprojects and a need for a better messaging system. Seahawk01 (talk) 01:55, 1 December 2018 (UTC)

@Seahawk01: Assessments are supposed to be done from within a wikiproject, and thus theoretically they could use different scales but in practice everyone uses more or less the same one and assessment is done by new page patrol and the like. Also, even if some parts of a wikiproject are active, assessment pages often are not. So it may be a communication issue as you said. — pythoncoder (talk | contribs) 03:17, 1 December 2018 (UTC)

@Seahawk01: The level of activity of wikiprojects is extremely variable. You are quite right that many for all intents and purposes are dead. On the other hand, others are extremely active. I am in the electronics wikiproject, and review requests usually get dealt with eventually (though there may be a long wait before someone takes an interest in that particular subject). The Military wikiproject is probably the best example of a well organised project. They have an established, well-used review process for getting articles to Class A. I'm not a great fan of new page patrol routinely adding wikiproject banners. Usually, the person doing this has no interest in the subject, is likely assessing it inaccurately (especially for importance), and is merely proliferating useless banners for semi-dead wiki-projects. SpinningSpark 09:59, 1 December 2018 (UTC)

When I assess articles, I usually skip the |importance= (sometimes called |priority= ratings, unless I'm very familiar with the group. WhatamIdoing (talk) 07:03, 3 December 2018 (UTC)

A hack to allow reversion on mobile

Just want to put this here in case anybody wants it, I have developed a hack which allows a editor to undo an edit while on the mobile interface here. Comments, criticism, bugs, requests welcomed. — $f r +$ 09:03, 29 November 2018 (UTC)

The mobile editor seriously needs to change. Oshawott 12 ==()== Talk to me! 05:00, 3 December 2018 (UTC)

+1 —

f r +

06:30, 4 December 2018 (UTC)

The mysterious floating orb

Go to Bohol Sea.

Look top right.

See "coords" and a globe?

Click the globe.

Did you know it makes a map appear?

I was thinking about consistent maps for bodies of water, and that was pointed out to me. I never knew about that. Should that be made more prominent or the link put elsewhere or something? Anna Frodesiak (talk) 01:05, 2 December 2018 (UTC)

Be aware that the map is just zoomed in on a simple Mercator projection. The result is that for higher latitudes the map appears stretched E-W. You would do better to click on the coordinates and select a map once you are above around 40° N or S. Martin of Sheffield (talk) 11:12, 2 December 2018 (UTC)

Maybe a separate "Interactive map" with the globe icon next to it in the info box rather than buried by the Coords would help people discover it. Jayzlimno (talk) 13:45, 2 December 2018 (UTC)

That sounds pretty good. Anna Frodesiak (talk) 22:11, 2 December 2018 (UTC)

Thank you Anna - I did not know that clicking on the globe made a map appear, until you had pointed it out. Vorbee (talk) 16:23, 5 December 2018 (UTC)

KKK

Hey guys, when you look up the KKK, go to the dates where the 1st generation began and ended. The real exact date the 1st generation ended was in 1872. Just to let you know. Thanks!

Slenderman4962 — Preceding unsigned comment added by Slenderman4962 (talk • contribs) 16:12, 4 December 2018 (UTC)

@Slenderman4962: Thanks for the help. You'll want to do 2 things to fix this. 1) Find where you read this so others can read it to 2) Raise the point at Talk:Ku Klux Klan so that people can fix the article with the information from your source. I hope that helps! --Jayron 32 16:54, 5 December 2018 (UTC)

"I'll skip that... I know nothing about Brexit"

I'm concerned about the limited number of experienced editors / administrators who are taking a large step back from Brexit-related articles / debates (on the basis of lack of knowledge of the subject) and leaving the same small pool of editors to reiterate their positions with ever-decreasing politeness.

Crunch time for Brexit is coming up. There is a crucial vote in the UK's parliament on Tuesday 11 December 2018.

Stewart, Heather (28 November 2018). "Brexit: how the meaningful vote will work". The Guardian. Retrieved 1 December 2018.

and prior to it a head-to-head TV deabate between the Prime Minister, Theresa May and the Leader of the Opposition, Jeremy Corbyn, on Sunday 9 December 2018.

Mason, Chris (29 November 2018). "Brexit debate: Clash over whether BBC or ITV will host debate". BBC News. Retrieved 1 December 2018.

In July 2018 the BBC printed the following four Brexit outcomes:

Leave with a deal
Leave without a deal
Stay in the EU
Hold another referendum

Staff writer (19 July 2018). "At-a-glance: The UK's four Brexit options". BBC News. Retrieved 1 December 2018.

There's a lot of POV-pushing between possible outcomes going on.

Elaborated on in November 2018 by Bloomberg News.

Ross-Thomas, Emma (15 November 2018). "Confused about Brexit? Here's what you need to know". Bloomberg News. Retrieved 4 December 2018.

Is there some way of widening the pool? There is a Brexit Task Force WP:BREXITTF and I did think about issuing invites on talk pages but who to? It could do more harm than good. I also wrote an essay in my namespace WP:BREXIT101 trying to give a rough guide to Brexit for editors if anyone wants to read it. --The Vintage Feminist (talk) 05:06, 1 December 2018 (UTC)

Speaking for myself, the whole area is changing so rapidly that any attempt to move beyond a bland minimalist description is bound to fall foul of WP:NOTNEWS and WP:NOTCRYSTAL. Further pretty well any attempt to explain entrenched positions is likely to be WP:POV and lead to WP:BATTLEGROUND. I would seriously suggest that editors who are holding back and waiting to see what happens are doing the right thing. There's always Wikinews if you feel you want to make a dynamic contribution. Martin of Sheffield (talk) 11:47, 4 December 2018 (UTC)

@Martin of Sheffield: I was thinking more of AfDs and RfCs being responded to by the same pool of editors while other editors run a mile. Also see my answer below. --The Vintage Feminist (talk) 16:18, 4 December 2018 (UTC)

I think the BBC has a couple of objective explanations/infographics as to what's the options in the brexit process are -- it could be a starting point. If you think there's POV pushing try WP:NPOVN? ProgrammingGeek^talktome 14:44, 4 December 2018 (UTC)

@ProgrammingGeek: Thanks, I do post on noticeboards when there's a discussion, I find there's a tendency to step back. As an example — forget Brexit a second — imagine a shopping list:

Bread
Cheese
Milk
Carrots

A second draft of the list reads:

Bread
Cheese
Carrots

Then someone argues with you that the carrots in the second list are not the same as the carrots as in the first list because they are now numbered differently. Sounds daft doesn't it? Yet when the meaningful vote went from being an amendment on the bill to a section of the Act of Parliament that was the discussion, diff 1, diff 2, diff 3, diff 4, diff 5, diff 6 etc. Today I was able to add the ref Parliament’s 'meaningful vote' on Brexit from Institute for Government saying "The bill was further amended during its passage. Section 13 now says...", hopefully that will be the end of it. I have to say I agree with the comment in this diff It strikes me that those who oppose the use of the current description of the article's subject essentially do not accept that this article should exist at all! A few more voices saying "wait, this has nothing to do with the complexities of Brexit or working out what may happen in the future, it's just re-numbering" that would really have helped. --The Vintage Feminist (talk) 16:18, 4 December 2018 (UTC)

A personal response. As a experienced editor I know to avoid topics where I am personally involved like a ton of bricks. 52% of the population who were allowed to vote in Cameron's tawdry advisory referendum voted to give him a good kicking, 92% of experienced Labour party members voted to remain in spite of Cameron. With Liberal Democrats all voted to remain. Some one with a Wikimedia Foundation grant may like to discover the pro-remain views of UK Wikimedians, but high ninetys is my predictions. I don't think any experienced Wikimedian could edit a Brexit article.

Why? This is extreme WP:OR, extreme WP:POV. The Proleave stance is based on prejudice- the Pro-remain stance on fact, cited opinions that use WP:RS. The Proleave lobby is very small:- and yahoo-Henrys don't edit and the backwoods men hate people they haven't met and people who own a computer.

The one thing we have learned is that- the leave yahoo brigade invent thinktanks who claim to be independent. Nothing that appears in the media can be trusted. Even if I wished to enter this maelstrom- I couldn't find a WS:RS. So I apologise if I keep my politics separate from WP, and offer Steve Bray (activist) as the closest I dare come. ClemRutter (talk) 18:49, 4 December 2018 (UTC)

I'm afraid none of us will affect what happens in Britain this week by our editing, but more revealing articles on those thinktanks, their supporters, etc. will do good in the longer term.

For full disclosure, I currently avoid by editing on Vicipaedia, where rapid news-led changes are pointless (the probability is that no one will read them). But I am planning to work on the thinktanks and propagandists. Andrew Dalby 10:18, 9 December 2018 (UTC)

This bit of discussion shows how quickly perspectives change. The consensus at that page a year ago was that citations of right wing thinktanks in the big media are not even worth mentioning. Andrew Dalby 14:40, 9 December 2018 (UTC)

Edit consolidation

For us, occasional editors who do not get it perfect the 1st time, allow us to eliminate missteps from & clean up the history by adding to the "View history" tab - "Compare selection revisions" button, a function to consolidate the intermediate revisions by the same user into just 1 resulting edit with description. This should reduce storage and clutter in revision searching. — Preceding unsigned comment added by N8HSU (talk • contribs) 23:11, 11 December 2018 (UTC)

I'm not sure if this works for attribution reasons? I'm not sure though programmingGeek(talk, contribs) 04:08, 12 December 2018 (UTC)

A course on Wikipedia similar to ones on Coursera or EdX

Any comments on this idea - A course on Wikipedia similar to ones on Coursera or EdX:

Problem: Learning about the intricacies of Wikipedia is difficult for a new editor and sometimes the process is discouraging and very slow. Navigating Wikipedia policies, guidelines and essays takes time, and mistakes by new editors increases the workload of older editors. Also, learning about Wikipedia can be made more fun, structured and efficient through such an online course for Wikipedia like the ones on Coursera (https://www.coursera.org/) or edX (https://www.edx.org/). A proper course with videos, quizzes, interactive elements, the history of Wikipedia and basic help navigating wikipedia for future editors, how the largest volunteer community in the world works, how things are resolved on controversial topics, so many things can be covered sequentially. The course can cover the whole of Wikipedia as well as WikiMedia, Commons, Wikidata etc and how all the other Wikis are part of the larger Wikipedia universe.
Who would benefit: All new editors, prospective editors and for those just curious about wanting to know more about Wikipedia itself. It would also provide an educational platform for teachers across the world to teach their students about Wikipedia in a more thorough and structured way.
Proposed solution: A course on Wikipedia on Coursera or Edx. (Even YouTube)
More comments: I know that Wikipedia – The Missing Manual and WP:The Wikipedia Adventure exists. But The Wikipedia Adventure would need to be expanded and updated extensively to cover this idea, it also doesn't cover the other wikis. I understand that there are other more experienced editors who help clear things out when there is a confusion related to how Wikipedia works, Talk pages are there as well as the TeaHouse etc.
DiplomatTesterMan (talk) 03:10, 10 November 2018 (UTC)

The Wiki Education Foundation has developed training materials for the student classroom program. They include guides such as Editing Wikipedia and online tutorials. Perhaps some of this could be adapted for orienting new Wikipedia editors. StarryGrandma (talk) 17:12, 10 November 2018 (UTC)

@StarryGrandma: Thank you for pointing this out. I had never heard of Wiki Education Foundation till now. Thanks for adding the links! They are doing some great work! :) I will try asking for some feedback from a member. DiplomatTesterMan (talk) 10:50, 11 November 2018 (UTC)

Well the dead horse I've been beating on this for a long time is getting video summaries for each major policy/guideline. There's potentially grant funding available that could cover things like space and equipment, maybe even a couple cheap actors. Writing scripts is easy enough. But I don't know anyone who has, for example, substantial experience producing content for youtube who would have the knowledge and expertise to bring the whole thing together and get a good production quality out of it. I'd love to snag someone like the GeographyNow crew who would be on board to see the whole thing through, but as of now I just continue to beat the horse. GMG ^talk 16:43, 11 November 2018 (UTC)
Well I'm fairly decent at various video production tasks, so I'd be down for this. WelpThatWorked (talk) 16:44, 12 December 2018 (UTC)
Comment: I have a brief case full of training booklets that have been produced for edit-a-thons and training sessions- and the they are all wanting. Dive in: Commons:Category:Wikimedia UK training booklets . If you want a quick fix, you could try Commons:File:Newspeak House- Strengthening an article manual.pdf

I have been a proponent of independent resource-based learning for decades, whereby tutorial material is written, and the learner or a trainer chooses the route through them. The resource sheets are written for different ability levels, in differing languages and in many ways resemble a wiki, catalogued and linked. The tutor will talk to resource- the independant learner would choose their own route. The resource bank would now include youtube type clips.
There is a massive need for a printed manual- but it must reflect Wikipedia as it is today. Forget teaching newbies about creating new articles: New page patrol and the draft space review backlog will zap most of those. Forget about teaching syntax: newbies usually edit with visual editor, or on cellphones/mobile phones. The experience we had when we started is not the same as the newbie gets today. Similarly, the language used by academics is not the same as that needed to write a tutorial sheet. The test I use to evaluate tutorial sheets is how they explain referencing.
Material used for tutorial material is not written in the same way as explanatory promotional material even if the content may appear similar. Both are needed. Active editors can provide the content, and the foundation can help with typesetting and editoral skills- the trainer can select the most appropriate for his students. I think the message is that we should have a serious look at the problem and appreciate that there is no one correct way, but having nothing is wrong. ClemRutter (talk) 18:34, 12 November 2018 (UTC)

@GreenMeansGo: Mention of making individual video summaries for the guidelines is a great idea, more implementable and workable at a smaller level than an "entire" course on Wikipedia. Thanks for the mention about the potential grant funding available for all this, I had totally overlooked how it would cover something like this. The mention of production quality like GeographyNow is a good aim. At a personal level I could request a few people for decent level individual videos, provided the funding say even for a sample. But then I am hesitating for various reasons, including personal reasons, so I think I am also going to be beating a dead horse too for sometime until I get the confidence to go ahead with it! :D :D I did leave mention of this idea on the talk pages of two Wikipedia Education Foundation members and one, User:Ian (Wiki Ed) acknowledged that he would convey the idea to his colleagues. DiplomatTesterMan (talk) 15:39, 23 November 2018 (UTC)

@ClemRutter: Thanks for all these points. The points you mentioned about newbies are very relevant. I had hoped the course would not only be to train new editors, but an entire course in itself. (Like a Bachelors degree in Wikipedia, or a non-credit certificate course from a respected University, MBA Encyclopedia Management :D :D :D) Anyway... getting ahead of myself, thanks for the reference to the PDF too. DiplomatTesterMan (talk) 15:39, 23 November 2018 (UTC)

@DiplomatTesterMan: Ramjohn probably has more pull than any of us could have as far as connecting the logistical dots. I did work up an example of a draft script a few months ago, just to illustrate the kind of thing I'm talking about. Very much shooting for a GeoNow or Crash Course type vibe, being informative and minimally entertaining, while keeping things super low budget and not taking ourselves entirely too seriously. (Incidentally, I've already emailed both GeoNow and Crash Course begging for interest and neither ever replied.)

But the idea is to make some passive way of learning policy, something where you can cook dinner or browse reddit and still absorb information about policy. At least enough to get you to the point that when a new editor actually sits down to read the full text, they already have a general idea of what it is they're reading and how it's applied. GMG ^talk 15:59, 23 November 2018 (UTC)

@GreenMeansGo: I went through the link -example of a draft script. Noticed how you wrote "start what is probably a waste of time" for the first edit summary. :D ... it's a good script. But then actually converting it into a video is another matter....
This has made me think that if a script like yours, coupled up with good reasons and more content, a larger outline can be drafted in to a grant proposal made with Project Goal, Project Plan, Activities, Impact etc etc. (with the grant only being for the final production of the videos, So say you are a scriptwriter, you will be included in the proposal, but the grant wont be towards the scriptwriter, or any writers at this stage. It will merely be for the actually camerawork and the video editing, etc that can be worked out). Now once the entire outline has been developed, Wikipedia communities all over the world can be tagged and pinged with the only aim that someone needs to actually make the video... and since an entire outline has already been drafted... it may work out. I think this is a more logical way of going about it. (WOW! This is exciting :D :D)

I also noticed a couple of videos on YouTube with over 150,000 views such as How to Edit a Wikipedia Article, but this kind of video is NOT the aim at all, so the proposal will have to build on this and answer what new things the new video attempts... as you wrote "something where you can cook dinner or browse reddit and still absorb information about policy", "production quality like GeographyNow"... DiplomatTesterMan (talk) 15:57, 7 December 2018 (UTC)

Well DiplomatTesterMan, the problem with many currently available videos is going to first and foremost be that they're not published under a free license. Now, some videos are freely licensed. See video to the right that I just found and uploaded. (Shout out to Wikipedia:Art+Feminism.)

Unfortunately the problem with that video is that it is immensely text based. So basically what that means is that it ain't worth nothin if you don't speak English. If we were going to try to put together a series, part of the goal would ideally be to make it basically contain as little text as possible, and as many...lets be honest...visual gags that are cross culturally relevant as we can. What you set yourself up for there is that anybody can slap on non-English subtitles and the video content would still make sense. For that matter, you could dub it over with non-English audio if you wanted, and still, something like a big leather bound book as a visual gag is still going to communicate the meaning effectively. GMG ^talk 16:12, 7 December 2018 (UTC)

@GreenMeansGo: The grant proposal would categorically state clearly that the video is going to be made under a creative commons license and can be used anywhere on Wikipedia, and also uploaded anywhere else of course since it is creative commons. And yes, no heavy text based videos and universally understood creative gags, yes to all these ideas. (When I gave the example of How to Edit a Wikipedia Article I was just giving an example of what exists and why these videos are NOT what we want. But view count means that such videos have a viewrship, a strong point to add in the grant proposal draft for reasons why videos are a good idea.) And yes, English is the priority language, I understand that, I myself would prefer the video was in English and subtitles in other languages as needed. DiplomatTesterMan (talk) 16:22, 7 December 2018 (UTC)

Well, at the extreme end of that, you could go with a video that is entirely based on voice-over. Then the native language wouldn't matter.

But overall, yeah. Writing a script is easy. (Most of us are here to begin with because we're amateur writers giving away our work for free.) But I expect we would still need to find someone with some kind of production experience. I wouldn't have any idea how to write a proposal for...justifying studio time, detailed equipment needed, etc. GMG ^talk 16:27, 7 December 2018 (UTC)

@GreenMeansGo: Yes, only a voice over solves the issue of language. As for writing the cost part, So I do have limited experience as a professional video editor (8 months), but it's been over two years and I am out of touch with the financial part of it all. So I will not rush to write down figures just now. And since I live in India, I guess figures will be a little (a lot) different as compared to say UK, US etc but that is besides the point for now. There are other aspects of the proposal that can be worked upon first, see, i quickly copied a sample proposal and pasted it in my userspace as an example - Video (Grant) Proposal Example. This can be developed accordingly. After the initial proposal has be drawn up, (i want to call this an IDEA PROPOSAL rather than a GRANT PROPOSAL just now), then maybe an admin or someone can mass message Wikipedia users seeing if anyone here can help with the production part (outlining the finances first...). DiplomatTesterMan (talk) 16:58, 7 December 2018 (UTC)

I wonder if User:Fuzheado or User:Rosiestep would be able to give any pointers as to how they got that super fancy video they showed at WikiCon North America. GMG ^talk 17:04, 7 December 2018 (UTC)

I tip my hat to Fuzheado for that video. --Rosiestep (talk) 17:07, 7 December 2018 (UTC)

Video is a splendid thing. So is printing, and many introductory pages exist, scattered in various places including user subpages. Mine is User:Jim.henderson/Wikipedia is collaborative which, on the theory that too many intros are technical (list of rules, how to format refs, etc), takes more a sociological or political tack. I print it as a single sheet folded as four pages and pass it out at edit-athons, where it is often well received. The usual problem with nicely printed pamphlets is distribution; the papers must be brought to the user. My sheet can simply be run off on your printer, giving a result far less pretty than what any competent print shop will produce, but it's easy. it would be prettier and easier if it were in a WP format instead of a Wikimarkup page. Jim.henderson (talk) 17:36, 23 November 2018 (UTC)

@Jim.henderson: Thank you for the inputs! Yes, printing is splendid too, actually I think better than videos :D :D... but then videos will cater to a different set of people, who do not think print is that splendid :D. I went through your writeup! It's nice and really simply written! Reminds me of "Simple Wikipedia." (Even this can be converted into a video script and made interactive), coupled with the above ideas into one proposal maybe! DiplomatTesterMan (talk) 16:02, 7 December 2018 (UTC)

What we do will depend on what resources we can muster, @DiplomatTesterMan: and what we've got are writers. As it happens, I learned most my writing skills when I was young, far back into the 20th century, and improved them in BBS discussions and later in editing SimpleWP. I haven't learned anything about making videos, much less instructional games. Those who have made our instructional videos, haven't impressed me with their command of the art. This is not counting promotional videos full of skillful razzle-dazzle and not trying to convey a major load of information.

A couple days ago I was in an edit-athon where we showed videos. To me, they seemed terribly inadequate. For that setting, even a moderately poor live presentation is better than our typically poorly constructed and plotted videos. What I should improve, for these purposes, is my own live speaking skills. This is in my own environment, New York City, where we have many live events and improving them would make a difference. Most newbies, however, are not in a city with an active local Chapter, and must learn from dead material, whether paper or video, made for home consumption.

Those who make this material must know not just the topic, but how to present it. For us who are competent only at writing, it's a somewhat different kind of writing. It's another skill that I, at least, should cultivate by extending my little four-page folio with material of similar style but covering technical questions such as notability and references. Which, once written raises for me the question of home binding since I'm still going with the theory that it ought to be printed at the instructor's home for passing out as a takeaway at our live sessions. Jim.henderson (talk) 03:46, 8 December 2018 (UTC)

Flag upcoming events for editing once the event has occurred

There are frequently statements such as "The new season at Actor's Theatre will open on October 12, 2017 with a production of Hamlet". I question whether such statements are ever justified (they may be just promotional), but if they are included, they should be flagged with and automatic mechanism that alerts somebody to the necessity of updating once the predicted event occurs. Here is my proposed logic for such a flag:

{{the verb tense used in this statement must be updated on October 12, 2017}}--Toploftical (talk) 19:50, 13 December 2018 (UTC)

@Toploftical: There's a template for that work already: {{Update after}}. Read the documentation for more details. –Ammarpad (talk) 21:45, 13 December 2018 (UTC)

thx--Toploftical (talk) 22:03, 13 December 2018 (UTC)

A hypothetical Wikipedia UI revamp

I come across a hypothetical Wikipedia UI revamp mockup with a clean interface and a night mode toggle button. See mockup here: phab:M270 --Agusbou2015 (talk) 17:59, 14 December 2018 (UTC)

Dealing with spoken audio files

What is the best way to deal with spoken audio files on English Wikipedia?

Currently you can put a pronunciation in the lead and a complete article recording can be linked via {{Spoken Wikipedia}} (a little box at the bottom of articles, in the external links section).

But how to work with multiple audio files? For example Channel Tunnel could include "Channel Tunnel" in an English accent, "Chunnel" in an English accent, "Le tunnel sous la Manche" in French. Then there may be an Australian accent for the lead (using metric) and an American version (using Imperial). Finally a recording of the whole article.

What about creating a subpage, eg Channel Tunnel/spoken? It would have several advantages:

A central spot for whole article readings, simple subject pronunciations and mid-length recordings of the first sentence or lead.
Allow access to recordings with different accents and subjects in different language if notable. Without cluttering the article itself.

Before I complete a load of article subject pronunciations I am looking for suggestions on how to link to spoken audio files.--Commander Keane (talk) 05:16, 18 December 2018 (UTC)

First off, there's no subpage structure in mainspace. Channel Tunnel/spoken is an independent page not a subpage of Channel Tunnel. Also I think part of the problem why Wikipedia:WikiProject Spoken Wikipedia is inactive is largely because of the ineffectiveness of representing dynamic content in a static audio. Wikipedia changes all the time, the moment you record an article, the audio can become outdated the very next minute. Wikipedia is first and foremost text-based. If one wants hear article being read they can use screen reading softwares which one can customize to accent they wants and also have the added advantage of reading the current version of the page unlike recorded audio. –Ammarpad (talk) 08:14, 18 December 2018 (UTC)

I agree with what you said, but I intend to purely record article titles. Unlike whole articles, these rarely change. Also, you cannot beat a human pronunciation by a local when compared to screen reading software.--Commander Keane (talk) 08:36, 18 December 2018 (UTC)

You can add them to the commons category and make sure that is linked on the page. That would be my recommendation. --Izno (talk) 02:12, 19 December 2018 (UTC)

Automatically detecting paid revisions

I'm working on detecting paid revisions with a framework that requires weak heuristics for their detection. But I've no experience as an editor, so heuristics that I come up with probably aren't going to be very effective. Does this sound interesting to any experienced editors out here?

The framework that I'm working with. Paper supporting the framework. — Preceding unsigned comment added by Apiarant (talk • contribs) 20:25, 18 November 2018 (UTC)

I'd be concerned that such a heuristic can't tell the difference between paid editing and COI editing, as different policies apply to both. Or worse, not tell the distinction between paid editing and editing on an organization page as extensive edits to organization pages can be symptoms of spamming, paid editing or mere interest. Heuristics don't have mind reading powers, after all. Jo-Jo Eumerus (talk, contributions) 06:57, 19 November 2018 (UTC)

This is no rocket science. Heuristics cannot differentiate paid and COI editing. Even humans only do so by looking at the surrounding factors, prior knowledge or confession not by merely by looking at revisions. –Ammarpad (talk) 07:14, 19 November 2018 (UTC)

Sorry, I should've been a bit more clear and gone in a little more detail about the framework. Indeed, the difficulty with detecting paid editing is that we don't read minds. And so, any auto-detection method that uses what we already know (like revisions made by self-disclosed paid editors) doesn't have much base knowledge to work with in the first place. Snorkel (the framework above) tries to improve this limited knowledge problem by trying to squeeze more out of shakier sources of knowledge, like experienced Wikipedians' judgments and their personal heuristics. A short summary of how it does this:

(1) Instead of applying heuristics directly, Snorkel (the framework above) can take a large collection of heuristics (which are never wholly correct) and model the ways that they are correct and incorrect with respect to each other, as a whole.

(2) From considering all heuristics, Snorkel can then make probabilistic claims about revisions. It can declare how unsure the sum of the heuristics should be.

(3) These probabilistic statements can be applied to edits that no one's really sure about. But now we have newly explicit knowledge that we didn't have before -- even if the knowledge is fuzzy. This probabilistic knowledge can improve other methods. Like the types of models that ORES works on.

Snorkel is a state-of-the-art thing that made a little splash. But it isn't a quick and easy solution; there's a lot of work to do. A first step is collecting a set of heuristics to model. And of course, if its performance looks shaky when testing offline, then it won't be brought online. Apiarant (talk) 10:30, 20 November 2018 (UTC)

I don't see how this could possibly work in the context of Wikipedia. As a concrete example, I've created numerous articles on artworks currently in Tate Britain; how could your system possibly detect whether I'm doing so out of an interest in the topic (unproblematic), because I'm an employee of the gallery and consequently know a lot about its contents and want to share this knowledge in my spare time (legitimate COI), because I'm an employee of the gallery and hope to boost interest in my workplace (inappropriate COI) or because I'm a PR agent hired to the gallery to raise its profile (unauthorised paid editing)? Even expert human admins find it very difficult to distinguish between interest, COI and UPI. Any attempt to automate the process will generate huge numbers of false positives, and Wikipedia is not going to look favourably at any system which flags significant numbers of good-faith editors as potential spammers. ‑ Iridescent 10:43, 20 November 2018 (UTC)

It's a pretty messy problem -- I agree. Whether this can work comes down to whether there are sufficient behavioral differences between paid and good-faith editors' behavior (as far as they are revealed to Wikipedia). If there aren't sufficient differences, then that's that. We don't have evidence to work with to build cases, so to speak. But if we've got the evidence, then whether we can produce an automated solution comes down to a technical challenge of finding the right model to capture these differences. As you've said, some of these differences might be quite subtle and difficult to observe, even for experienced humans. The nice thing about Snorkel is that we aren't asking for it to work with the evidence all by itself. Snorkel works because it gets "help" from people in the form of heuristics. And the more diverse and richer the knowledge-base of those heuristics, the better Snorkel can do -- sort of like a Wiki. The end model is (kind of) collaboratively edited.

More personally, my reason for the proposal: As the central repository of knowledge for the world, it's a shame that Wikipedia doesn't have the type of money big companies have for state-of-the-art automation (like Google / Facebook's ads, Amazon's recommended purchases, etc.). But Wikipedia has passionate volunteers. Snorkel has the potential to bridge volunteers and efficient solutions that work at scale, especially given stagnating growth in number of new editors. Apiarant (talk) 23:37, 23 November 2018 (UTC)

Apiarant, MER-C generates a list of suspicious (possibly COI/PAID) articles regularly. Probably someone you'd want talk to about this; and other editors who frequent WP:COIN. The heuristics could help in finding paid rewrites of existing articles that slip through the cracks. One identifier of paid spam is promotional articles from new editors that are too well done (someone who is paid often try to do a good job of it). Galobtter (pingó mió) 10:58, 20 November 2018 (UTC)

to expand on Iridescent's example, even for commercial organization, it is reasonable that individual hobbyists will be interested in all the products from a company. This even holds for non-consumer products==one of the revelations of WP is the range of things hobbyists can get fascinated in, and there's a even better example, Wikia. What I tend to find most suspicious is a deep interest in products from unrelated companies, but this is why most UPEs know at least enough to pick a different user name each time. Many of us working with UPE detection go by writing style--but this is less helpful one might think, since even the most characteristic PR quirks are copied by good faith editors whose idea of appropriate stye has been contaminated by exposure to the huge amount of PR in the world, and in particular by the large amount already in WP, which they copy thinking this is what we want--naive good faith editors have even said this explicitly, that they've deliberately copied the style of what they find here.

It should be possible to find a heuristic as good as any one of us, but none of us are really very good. It should even be possible to find one as good as the combined consensus here, but that will only be slightly better, for we often disagree on anything not utterly obvious. That's why the practical emphasis is on removing promotional articles, no matter by whom they are written. Very few people or firms will hire an editor to write non-promotional articles about themselves. DGG ( talk ) 20:29, 27 November 2018 (UTC)

Apiarant, I think the big issue here is the difference between trying to identify a paid edit vs trying to identify paid editors. I don't think you can extract enough of a signal in the context of a single edit to reliably and usefully flag any but the most blatant cases. (We have edit filters that catch usernames which substantially match the article title or article content, which catch a lot of clueless COI accounts. See (recent changes examples). It would be more challenging, but much more viable, to attempt to identify paid editors based on the collective context of their editing history. Most paid editors use a disposable accounts with only a handful of edits, a new account for each article they want to push. With such a short history these accounts are created in an endless stream, they are generally pretty obvious, but they are hard to firmly deal with. They just come back with a new account, and there's a painful tension between an "obvious" disposable accounts and a presumption of Good Faith for accounts with little or no clear bad-history. At the other end of the spectrum long term paid accounts are far less common, far more insidious, and it can take a painfully long time to dig through their edit history to build a strong case against them. A quality tool to identity one or both classes of paid-accounts would be more useful than trying to classify individual edits. Alsee (talk) 01:31, 8 December 2018 (UTC)

@BU Rob13: If I recall correctly, weren't somebody associated with you researching into the same locus? ∯WBG^converse 19:51, 20 December 2018 (UTC)

I had been interested in finding someone who might want to go that route. I don't believe I ever got any firm commitment from anyone, though some were interested. ~ Rob₁₃^Talk

Avoiding unnecessary deleting and undeleting

To avoid unnecessary deleting and undeleting, wasting the editor's time and Wikipedia's server's time, we need abilities for admins to do these to a page:
1. Select some of its visible edits, and delete only those. (This is not the same as hiding some edits.)
2. Select some of its visible edits, and move only those.
3. Move its deleted edits, while keeping them deleted.
4. If the previous, select some of its deleted edits, and move only those, while keeping them deleted.
- Anthony Appleyard (talk) 06:01, 10 December 2018 (UTC)

1. Also have history merge without deleting the target (could be combined with selective revision move. Graeme Bartlett (talk) 10:29, 10 December 2018 (UTC)

Most of these are impossible unless T20493 • Tthis happens:(∯WBG^converse 19:46, 20 December 2018 (UTC)

WP:Draftify - Guideline or Not

WP:DRAFTIFY seems to be causing a bump in recent irritation, as regards improper usage, clashing with other guidelines etc etc.

Currently it is stated to be an explanatory supplement. I am not sure this is the case - WP:NPPDRAFT includes only the bare minimum, and I believe the rules of usage in DRAFTIFY are beyond a mere supplement.

In any case, I am aware there are various issues - so I thought I would create a discussion point for people to hopefully comment on and moot solutions (if applicable). Nosebagbear (talk)

Please feel free to start sub-headers for different issues

@Nosebagbear: It feels like a version of this discussion is happening already. Best, Barkeep49 (talk) 17:52, 20 December 2018 (UTC)

@Barkeep49: - you are right of course, I'll the question and your link here, since they seem a beneficial link. If someone wants to rephrase purely into a link they may do so. Nosebagbear (talk) 17:58, 20 December 2018 (UTC)

Project grant request

Dear all

I've submitted a grant application to the Wikimedia Foundation to continue to work at UNESCO in 2019 and would really appreciate it if you would consider endorsing it (the blue button at the bottom of the infobox). In 2019 we want to focus on:

Helping UN agencies adopt open licensing and share content on Wikimedia projects
Share UNESCO content at large scale (100,000s of images)
Build the relationships between UN agencies and Wikimedia organisations to run projects
Continue to write and improve instructions on Wikimedia projects (list of previous documentation on my user page) to make it easier for everyone to run projects

This will be the last time we ask WMF for funding, we have a grant proposal outlined for a large external grant for 2020 but without this year's funding we won’t get to where we need to be.

Thanks very much

John Cummings (talk) 10:11, 22 December 2018 (UTC)

Actions other than Undo

Historically, there have been only two ways to fix an edit. Either revert it in its entirety or allow it to stay. This has led to a certain mentality among patrollers to revert even when the edit could have been improved. I personally have come across edits which could have been fixed by adding a citation needed tag or a spelling correction. Often a portion of the edit is incorrect, the rest is okay, however there is only one way to fix it, revert. Suppose we had a extension/script which allowed you to correct these edits, add a citation tag, fix spelling mistakes, remove problematic portions or copy-edit a edit while in diff mode. That would make life a lot more easier and prevent biting of newbies.

Is there such a script/extension ? Would a lot of editors benefit from such a tool ? Or is it just me who think such a tool is necessary ? — $f r +$ 17:37, 23 December 2018 (UTC)

m:Community Wishlist Survey 2019/Citations/Dealing with unsourced additions - "citation needed" button is related. — JJMC89 (T·C) 22:16, 23 December 2018 (UTC)

And since the community wishlist entry (linked by JJMC89) was not accepted, I have begun work myself on a button like this. I'm hoping to present it at the NYC Wikipedia Day meetup, so it'll probably be in testable condition in early January. Enterprisey (talk!) 04:49, 24 December 2018 (UTC)

Uh. "only two ways to fix it" ? "only one way to fix it: revert" ? You know those aren't the only options, yes? DS (talk) 05:45, 24 December 2018 (UTC)

Yes; however, if you're not going to alt-tab away from Huggle, those are the only options. Ditto if you want to deal with a page-ful of recent changes quickly. Obviously it's better to use more options (such as the ones mentioned in the original comment by fr), but in practice I don't think that happens often (supported by my RC-watching while designing this feature). Enterprisey (talk!) 05:54, 24 December 2018 (UTC)

Ummm. There's the most important option: editing it. Get out of diff mode and actually edit the article. I'm actually shocked that the obvious answer is no longer obvious. Risker (talk) 07:04, 24 December 2018 (UTC)
Risker, what I was asking in the original proposal was an ability to perform the common editing tasks in diff mode. — $f r +$ 10:57, 24 December 2018 (UTC)

Get Google API key

I believe we should get a Google API key, for the purpose of using their API to keep up to date numbers and improve accuracy. For instance, the key would allow for pages relating to youtube to keep current video statistics, and thereby remove the menial task of having to get them manually. The issue is that the account monitoring the key (as an account is needed for the key) would have to be created officially (Maybe by staff?), because otherwise the key would be under the name of an individual and probably break some rule. Thoughts? WelpThatWorked (talk) 18:57, 20 December 2018 (UTC)

Sounds like a bot task to me. Would need consensus and probably an RfC. --AntiCompositeNumber (talk) 19:26, 20 December 2018 (UTC)

Does wikidata use bots? This sounds like something wikidata would be good at. Ivanvector (^Talk/_Edits) 21:44, 20 December 2018 (UTC)

What does the Google API terms of service say about licensing and usage restrictions? -- GreenC 22:03, 20 December 2018 (UTC)

To answer the question: Section 5e says it is prohibited to "Scrape, build databases, or otherwise create permanent copies of [Google API] content". Data scraped from the API into Wikidata would probably not be permitted - unless Google says otherwise. Google uses Wikidata. There is a Wikipedian who helped create Wikidata then hired by Google. He would be the one to ask. -- GreenC 22:18, 20 December 2018 (UTC)

Yea, I wasn't thinking of using it as a scraper, I was thinking more like grabbing small (notable) data such as the view numbers for the youtube top viewed videos list. WelpThatWorked (talk) 00:19, 21 December 2018 (UTC)

@WelpThatWorked and GreenC: If the data is publicly accessible then it's probably better to save it to the Internet Archive than to e.g. dump it in Wikidata (unlimited storage for all practical purposes, easily automated, acceptable in some jurisdictions as legal evidence, data is kept indefinitely, no licensing/database rights issues). I'm already doing this for the three top videos lists (tool archive-things on Toolforge – all of the video pages linked from those articles are saved once an hour); if you make a list of YouTube videos somewhere on-wiki I could also use that list. Wikidata also tends to avoid discarding old but correct data, so adding this data there would start to become unwieldy after a short time. Jc86035 (talk) 06:59, 22 December 2018 (UTC)

Sounds like exactly what the Google Terms of Service say not to do. Being publicly accessible isn't the same as public domain. They apparently don't want API data scraped and saved into "otherwise permanent copies". There are licensing/database rights issues. Section 5e. -- GreenC 16:04, 22 December 2018 (UTC)

Yea, so I wasn't intending to scrape with it, but use it for keeping small statistics of the notable variety up to date. WelpThatWorked (talk) 16:19, 22 December 2018 (UTC)

Sorry, my paraphrasing does not accurately represent the Terms of Service. I used the word "scrap", but the Terms of Service say much more. The Terms of Service can be found in Section 5e. I would recommend reading Section 5e, and not relying on what I say. For example 5E says:

Scrape, build databases, or otherwise create permanent copies of such content, or keep cached copies longer than permitted by the cache header

Is the intention to create permanent copies of the data?

Copy, translate, modify, create a derivative work of, sell, lease, lend, convey, distribute, publicly display, or sublicense to any third party

Is Wikipedia a third party? Does Wikipedia content have a license that is incompatible with the Google API Terms of Service?

Misrepresent the source or ownership

Is Google's ownership and the source of the data not being represented?

Remove, obscure, or alter any copyright, trademark, or other proprietary rights notices; or falsify or delete any author attributions, legal notices, or other labels of the origin or source of material

Is API data concerning legal notices, etc.. not being represented?

I don't have answers to these questions, but they seems like good questions. At the very least any regular and automated retrieval of Google API data into Wikipedia should be vetted with Mediawiki Legal, and/or Google. -- GreenC 16:53, 22 December 2018 (UTC)

@GreenC and WelpThatWorked: Clarification: the archive-things script is archiving the YouTube video HTML pages themselves, not making calls to Google's API. I don't believe this would be against Google's TOS, since it doesn't involve the API and IA has been archiving videos based on tweet mentions (i.e. a lot of videos). We don't have to worry about copyright for IA because IA assumes fair use by default, and small amounts of data – e.g. for the YouTube Rewind dislikes graph – wouldn't qualify as violating any sort of database copyright.

Maybe what could be done is that the script could edit the articles every few hours to add some of the data that it's downloaded (since it's downloading the pages anyway so that it can also archive the images), although I'm not really sure how to do that. Jc86035 (talk) 11:13, 25 December 2018 (UTC)

Suggest Wikipedia does not mention IRC as a source for help

Hello, I have 1,000+ edits over about six weeks. Things were going along lovely. I found everyone friendly. The Teahouse was working great and same with the Help Desk, Idea Lab (here) was a place to offer suggestions. Couldn't complain at all about my Wikipedia experience. That is, until last week when I went through Wikipedia:Questions to the #wikipedia-en-help IRC chat room...that was a big mistake and after that everything turned dark.

I had a simple question about stubs and ended up having someone put the article I was working on into draft space. Then I had two other people jump all over me. It was quite a shock.

Doing further research I found: Wikipedia:IRC and discover that this is a freenode channel, run by volunteers, but not affiliated with Wikipedia. To quote from that page:

When the channels are used to attack Wikipedians, or when IRC discussions are cited as justification for an on-wiki action, the resulting atmosphere is very damaging to the project's collaborative relationships.

Looking further for policy about IRC, I found this: Wikipedia:IRC/wikipedia-en-help. It is the first Wikipedia help page I ever found which says in big bold letters that the #1 channel guideline is "don't be a jerk", so I am assuming there are a lot of people who like to act like jerks there.

Lastly, I reference this: Wikipedia:Dispute resolution which says:

Resolve disputes as soon as they arise. When two editors disagree over what to do with an article, they must talk things through politely and rationally.

So, in the chat room, people took unilateral actions and made on-wiki changes without any discussions. I repeatedly asked for them to post on my Talk page, but this was ignored. Placing the article in question into draft space was a major hassle. Other people were also working on the page and now they won't be able to find it. This has drained my enthusiasm for Wikipedia and made me really question why I should even volunteer my time.

To sum up, I really think Wikipedia should not endorse the IRC chatroom at all, take all links down and especially take down the link at Wikipedia:Questions. — Preceding unsigned comment added by Seahawk01 (talk • contribs) 02:49, 11 December 2018 (UTC)

You clearly read the instructions, since you're quoting them, but you've ignored the "no public logging" that's listed in multiple places. I've removed your link. Natureium (talk) 03:06, 11 December 2018 (UTC)

I see two issues here. First, there were legitimate content issues with the article; an article that started New York City is suffering a crisis in housing affordability. Although the city's skyline has been filled with construction cranes for a long time, net affordable units continue to be lost. New York City is one of the most expensive places to live in America. There is a crushing rent burden on the poor, working poor and elderly. Homelessness in the city is currently at an historic high. had some obvious NPOV issues. Second, this seems like a mis-use of page-mover permissions, and moving to draft-space in general. Moving an article to draft-space shouldn't allow non-admins to unilaterally delete articles. power~enwiki (π, ν) 03:17, 11 December 2018 (UTC)

@Seahawk01: While the en-help chatroom isn't "officially" affiliated with Wikipedia or the Wikimedia Foundation (the non-profit that "owns" Wikipedia), there is a bit of a process of registering a single hashtag channel that starts with the word "Wikipedia" on Freenode to avoid misuse. So I doubt the channel itself will get "unapproved", so to speak, since that would be more difficult than getting it approved to begin with.

Sounds like there was some communication issues that could've been better dealt with to make the decisions made bite less; however, that doesn't mean that the decisions made need to be reversed, per se. That doesn't mean that the help channel needs to not exist.

Also, FYI (also to Power~enwiki) all because the article is in draftspace doesn't mean other people can't work on it, nor is it a way of "unilateral deletion". Rather, it's a way to prevent outright deletion from occurring. You express concern that people might not be able to find it. Perhaps link to it on your user page, or talk page. Generally speaking, if they can't find your talk page, they'd have some difficulty collaborating with other editors, anyway. I dream of horses (My talk page) (My edits) @ 04:33, 11 December 2018 (UTC)

@Seahawk01: Wikipedia encourages editors to be WP:BOLD in trying to improve articles. Pre-approval or permission from the article's creator is not necessary as explained in WP:OWN, and this is one of the things that new editors such as yourself often are surprised to find out. Any Wikipedia article can be edited by anyone anywhere in the world at anytime, and the only real restriction in place is that the edits be made in accordance with relevant policies and guidelines. When disagreements over article content, etc. occur, the best place to discuss things is generally considered to be on the article's talk page, not the article creator's user talk page, since this makes it easier for anyone interested to comment and also maintain a record of any discussion for future reference.

Articles are draftified for various reasons, but mostly because someone feels that there might be something worth working on and improving as opposed to something which has zero or very little value. In the draft namespace, you can continue to work on bringing things up to article standards and addressing any issues raised by others. You can post links to the draft on the talk pages of relevant WikiProjects to also try and get others involved as well. As long as the draft doesn't become abandoned, it should always be there for you to continue to work.

It makes no difference whether people editing the article found out about it from IRC, the Teahouse, or even this disucssion here because the minute you added it to the mainspace it became pretty much fair game for all to edit; so, trying state that IRC is the problem here sort of indicates a bit of a misunderstanding as to how Wikipedia has been set up to work. -- Marchjuly (talk) 05:23, 11 December 2018 (UTC)

I agree with @I dream of horses: here, but I don't think anyone in the channel was particularly BITE'y about it and the article is definitely notable, and I'm actually doing some research right now to improve it. To be frank, I think this article would do so much better in the draftspace to prevent deletion. @Seahawk01: None of us where trying to be mean in the IRC channel, we where trying to help you and prevent the article from getting deleted. TheMesquito^buzz 14:25, 11 December 2018 (UTC)

@Seahawk01: Can we get a dedicated on site wikipedia IRC, that'd be really cool! -- HentaiDoujinMaster (talk) 00:25, 22 December 2018 (UTC)

HentaiDoujinMaster, see also WP:IRC. It's not hosted by the WMF, though; I dunno if they'd agree to set up servers. Maybe if Freenode goes under, I suppose. Enterprisey (talk!) 09:10, 22 December 2018 (UTC)

Wikipedia redesign

Duplicate proposal See Wikipedia:Village pump (proposals)#Wikipedia interaction redesign — Preceding unsigned comment added by Anomie (talk • contribs) 03:18, 19 December 2018 (UTC)

Broken unblock requests

I've noticed that our "you are blocked" templates, such as {{Uw-block}}, can confuse new editors. Some edit the template's instructions instead of making a proper unblock request. For example: 1, 2, 3. I was thinking that maybe we should edit the templates to warn people not to edit the example unblock request. Then I thought, "Why not use an edit filter?" So, then I wasn't sure which way to go, or if maybe the problem is rare enough that it doesn't even matter all that much. Any thoughts? NinjaRobotPirate (talk) 09:40, 24 December 2018 (UTC)

I've seen the same and have had to fix an unblock request for someone who did it incorrectly in that way; an edit filter sounds like a good idea. Galobtter (pingó mió) 11:04, 24 December 2018 (UTC)

Does the "you are blocked" template {Uw-block} distinguish between people who are temporarily blocked and people who are permanently blocked? Vorbee (talk) 18:49, 27 December 2018 (UTC)

Setting the parameter |indef=yes will change "temporarily" to "indefinitely". --AntiCompositeNumber (talk) 19:02, 27 December 2018 (UTC)

Pronunciations (see archive 13)

Discussion was left in 2008 regarding trying to find software (or volunteers) to put pronunciations into the entries in Wikipedia. While I don't usually have a problem with regular words, I do have a problem with foreign words or locations, such as places in the Middle East. Have we gotten anywhere on this discussion / suggestion? ErinBS — Preceding unsigned comment added by ErinBS (talk • contribs) 11:55, 30 December 2018 (UTC)

ErinBS Wikipedia:Village pump (idea lab)/Archive 13 dates from 2014 and I've found no discussion on this topic there. If you wish to revive an old discussion you will have to provide a precise link.

The problem with pronunciations in articles is that most of them are unsourced and appear to be "original research", an activity editors are not supposed to indulge in. The original researchers may think the pronunciation familiar to them is common knowledge and not be aware that folks somewhere else pronounce the same word differently. See, for example, various discussions at Talk:Baltimore to get an idea of the complexities that can arise: Bhunacat10 (talk), 20:54, 2 January 2019 (UTC)

Tracking consensus and listing arguments

I have been wondering how were consensuses (or lack thereof) determined for extended discussions (those that are very long, with multiple layers of replies). Did every participant read the arguments and comments that have already been put forward (so that arguments do not become repetitive) before they start putting forth their own argument? I would if I were to participate in these discussions, but I doubt that every participant has done it or would do it.

I think it would be beneficial to have, at the top, a list of logically valid arguments that have been put forward thus far in the discussion in order to aid those who join later in knowing the state of the debate. It should have two sections: ‘arguments for‘ and ‘arguments against.‘ Each argument on the can have an objection or a counterargument from the other side written right under it. Some arguments can be put into a syllogistic form (premises and conclusion) for clarity and for aiding their evaluation. The list would also help the closer of the discussion in determining whether consensus has been reached and what exactly is the consensus. VarunSoon (talk) 23:51, 30 December 2018 (UTC)

Above and beyond the complication of this (not to mention people disagreeing about what exactly one argument means), I suspect writing it in syllogistic form is probably a bit too much too ask. Though it might pare down certain issues - we could really test editors and require their arguments to be in symbolic form. Nosebagbear (talk) 13:33, 31 December 2018 (UTC)

Using propositional calculus? - Donald Albury 15:16, 31 December 2018 (UTC)

No, the arguments need not be required to be symbolized. We do not even have to require every argument to be stated out in syllogistic form; what I mean is that it is an option when it is necessary (which would be quite rare). For example:

Arguments for deleting categories of Wikipedians by his/her philosophy (Side 1)

These categories fail WP:USERCATNO, specifically because they are based on advocacy (such as Category:Calvinist Wikipedians and Category:Creation Science Wikipedians) or are divisive (such as Category:Evangelical Wikipedians, Category:Pastafarian Wikipedians, and Category:Social Darwinist Wikipedians) or both. For example, if an atheist Wikipedian comes across a category that lists creationist Wikipedians, hostile attitude is likely to form, and this attitude towards specific users can obstruct cooperation and discussion when the he/she crosses path with Wikipedians that he/she knows is on that list.

Arguments against deleting categories of Wikipedians by his/her philosophy (Side 2)

Having a user's userbox automatically put the user in certain category facilitate that user in his/her search of other users who hold a similar view or belief. A Catholic user would be able to easily find fellow Catholic users. A compatibilist user would be able to easily find fellow compatibilist users. In other words, these categories are useful for informing a user that he/she, as a person who holds view x, is not alone on Wikipedia.
Side 1's response: The utility generated by this ability does not overcome the utility loss (mentioned above) generated by preserving these categories. Also, if the number is what matters here then there is no need to display the username of similar users.
Having religious categories facilitate the search for help from members of a particular religion in writing articles relating to that religion, such as those about doctrines and those about rites.
Side 1's response: The WikiProjects already have this covered. A WikiProject about a particular religion surely has members who are also members of that religion.

VarunSoon (talk) 08:02, 1 January 2019 (UTC)

I can see this proposal causing far more disagreement, about things like whether an argument is valid or not or is the same as someone else's argument, than it prevents. It might be good for the closer of a complex discussion to summarize arguments in this way, but I think that doing so during a discussion will end up being counterproductive. Some people simply like arguing for the sake of arguing, and this would just give them extra things to argue about. Phil Bridger (talk) 13:55, 1 January 2019 (UTC)

My main concern is with a user joining a discussion (concerning an issue) and entering his/her input without reading everything above (things that have already been input by other users) first, causing already-mentioned arguments to be repeated. Also, for the closer to have to go through everything by himself/herself is, in my view, too much to be done by a single person for judging the presence of consensus (or lack thereof) accurately. Third, consensus might not be reached among the participants because there are those who, because of the complexity of the discussion, have not considered every point that has been made in the discussion, causing discussions that could have ended in a consensus to end with no consensus. In other words, past long discussions, at least in my view, have been chaotic or not orderly enough for them to settle an issue efficiently (settle an issue without letting it to continue existing and be brought up again in the future) and effectively (producing consensus accurately). Lastly, I modify my proposal such that any arguments, even logically invalid or logically unsound ones, can be added to the list if they are not a repetition of the ones already added. VarunSoon (talk) 02:07, 2 January 2019 (UTC)

For preventing development hell: User:Nosebagbear, User:Donald Albury, User:Phil Bridger VarunSoon (talk) 07:09, 5 January 2019 (UTC)

I have nothing to add to what I wrote above, which remains my position. Phil Bridger (talk) 09:19, 6 January 2019 (UTC)

@Phil Bridger: Aren't disputes about repetitiveness and logical validity already present in the current system, even without the implementation of my proposal? For example, if person A says 'Your argument has already been addressed,' then person B can say 'No, my argument is not the same as that of person X and person Y.' Also, logical validity can be determined by examining the argument's structure alone. My proposal is for new discussions only (those started after the implementation); the first participant would add an argument either in the section for arguments in favor or the section for arguments against (or both, if he/she wants to express his/her ambivalence); when the second participant joins in, he/she can either add a different argument or second the one that was already added (by adding his/her signature under it; he/she may also edit it in order to rephrase it). VarunSoon (talk) 12:00, 6 January 2019 (UTC)

Template for royal pronouns?

"Her Majesty" occurs on the wiki 17,469 times. Scrolling thorough the results, it seems that about half of them refer to the current monarch of England. When the queen dies, we'll have a lot of work to do to fix all of those. I wonder if it would be a good idea to create a "their majesty" template and start changing things over now, so that when we actually have to change it over we can do it in one place. As a bonus, if we're still around in 20-80 years when we have a queen again, it would make our lives much easier. Gaelan 💬✏️ 07:24, 5 January 2019 (UTC)

@Gaelan: I couple of questions. Where did you get that number (17,469) from? And, how do you know which ones are meant to refer to the current monarch (throughout time) and which are meant to refer specifically to the current monarch as of now? Just wondering, --DannyS712 (talk) 07:40, 5 January 2019 (UTC)

@DannyS712: 1) a search on "her majesty" 2) eyeballing the first few pages of that Gaelan 💬✏️ 07:42, 5 January 2019 (UTC)

I can't replicate either of your results; a search for "her majesty" returns 6000 results not 17,469, and almost none relate to the current monarch. ‑ Iridescent 08:31, 5 January 2019 (UTC)

Oh, I forgot the quotes. (I had the quotes in my comment not as part of my search but just in the conventional English sense.) Good catch. Gaelan 💬✏️ 08:59, 5 January 2019 (UTC)

Even in the results without quotes, looks like some page moves will need to be done though I can't see that many uses relating to the current monarch. Galobtter (pingó mió) 09:27, 5 January 2019 (UTC)

I would imagine, too, that most things referring to QEII would remain "Her" while only references/redirects to the ~~office~~ title would need changing. ~ Amory (u • t • c) 01:37, 6 January 2019 (UTC)

Given that the third in line to the throne (Prince George of Cambridge) is only 5, you're making a lot of assumptions (some a 'bit iffy') in assuming a "queen again" in 20-80 years time. Besides which, "Imagining the Queen's Death' is technically an offence, and more to the point some people do live past 112 – see Oldest people! :-) Martin of Sheffield (talk) 11:04, 5 January 2019 (UTC)

Does "Imagining the queen's death" consitute high treason? And doesn't that still technically carry the death penalty? Somebody had better be careful. Phil Bridger (talk) 12:32, 5 January 2019 (UTC)

When the queen dies Quite the assumption that the Queen isn't an immortal robot-alien sent to rule us for all eternity. Assuming however, that she will die, I'm not finding too many instances where this would have to change in the search results and in most cases we'd probably have to do more changes than changing "her majesty" to "his majesty" to the pages and thus a template could confuse things by having some things up to date and some not. Galobtter (pingó mió) 15:50, 5 January 2019 (UTC)

I agree. Despite the fact that I might be liable for the death penalty by saying so, the current queen of my country is clearly mortal, and at her age we can expect her to die in the next decade or two. I'm sure we have enough editors who follow the British royal family to make the required changes when that happens. Maybe our dear leader will even join in doing so, because I believe that he is a fan of the monarchy. Phil Bridger (talk) 19:42, 5 January 2019 (UTC)

Preparations for the passing of the monarch have been made by the UK government, the BBC, and other governments (down to broadcasters having black ties and suits ready at all times), so I don't think it's an offence. isaacl (talk) 22:21, 5 January 2019 (UTC)

With all those preparations, isn't it weird that they haven't included wikipedia‽ ~ Amory (u • t • c) 01:37, 6 January 2019 (UTC)

I don't think so; I wouldn't expect the UK government or the BBC to undertake editing Wikipedia. Even leaving aside the paid editing concerns they would encounter, keeping Wikipedia up-to-date isn't within their scope, just as they wouldn't update other encyclopedias. isaacl (talk) 21:12, 6 January 2019 (UTC)

We catch various agencies of the UK government fiddling with Wikipedia all the time, with various degrees of hamfistedness when it comes to the attempt to conceal their tracks. Here's the Home Office to get you started. ‑ Iridescent 21:31, 6 January 2019 (UTC)

Sorry, I should have said for the purpose of transitioning the pronouns from Her to His. I presume all of the ongoing fiddling is for a political purpose, and so there is incentive to do so. There is no political upside to helping the world's encyclopedias to update their pronoun usage. isaacl (talk) 21:35, 6 January 2019 (UTC)

Now see, I distinctly remember a discussion in the Swiss parliament where a MP questioned whether the Swiss government has a policy for editing Wikipedia (apparently it happens quite frequently) and trivial updates and the like were among the things that the Swiss government does. Jo-Jo Eumerus (talk, contributions) 21:37, 6 January 2019 (UTC)

Let's come at this from a different direction. Yes, organizations (such as private businesses and government agencies) like to edit their Wikipedia articles to keep the information up-to-date, like the current top officials and the current mission. But as per the original question, is it weird that we haven't heard of a plan for governments to update Wikipedia to change the pronouns from Her to His on the passing of Queen Elizabeth II? Given that it won't be obscure news, virtually shutting down at least parts of the UK for a period of time, I don't really expect governments to do this. isaacl (talk) 21:42, 6 January 2019 (UTC)

I think Amory's comment was intended to be much more light-hearted than the way you and others are interpreting it. I may be wrong, but the message that I get from that comment is that Wikipedia is nowhere near the most important thing in the world - something that we should all bear in mind. Phil Bridger (talk) 21:49, 6 January 2019 (UTC)

I imagine it was; the interrobang was invented to express surprise or incredulity in a question [2]. I chose to address the incredulity aspect, but it was probably a rhetorical question. isaacl (talk) 21:55, 6 January 2019 (UTC)

Articles should only use the term "Her Majesty" when referring to someone's style and title or when it is part of a direct quote. In most cases there will be no reason to change the gender when in the fullness of time a male heir ascends to the throne of the United Kingdom and her realms beyond the seas. Incidentally, a lot of articles would have to change queen to king, but fortunately there are hundreds of editors who would joyfully muck in. TFD (talk) 19:43, 6 January 2019 (UTC)

Quite. We don't routinely refer to Jesus as "Jesus Christ" or to Muhammad as "the Prophet Muhammad PBUH", so we shouldn't routinely refer to the current monarch of the United Kingdom and some other places as "Her Majesty". If we do so then that should be changed now, rather than waiting till she dies. Phil Bridger (talk) 20:42, 6 January 2019 (UTC)

Political position

Most articles have fields in the info-box for both ideology and political position. While there is usually agreement about ideology, there are often differences over political position. See for example Talk:Liberal Party of Canada#Drop "Center-Left", Talk:Democratic Party (United States)#Political position discussion, Talk:Labour Party (UK)#Centre-left to left wing for current arguments.

Essentially these arguments boil down to where the ideologies belong on the political spectrum.

Reliable sources are in disagreement over how to characterize various ideologies. For example, Robert M. MacIver said conservatives are right, liberals are center and socialists are left. Seymour Martin Lipset said that in the U.S. the Republicans are the Right and the Democrats are the Left. Some scholars define center left to include social liberals and socialists. Arthur M. Schlesinger Jr. defined the center as anything between fascism on the right and communism on the left. All of these definitions and more are routinely cited in reliable sources, but there is no agreement on which to use.

I think that instead of arguing the issue over dozens if not hundreds of article talk pages, with no consistency in decisions, we either have a consist policy or determine that the field should not be used.

TFD (talk) 19:35, 6 January 2019 (UTC)

I would support the removal of the parameter in the info box as it has been such a problem that recently we had to install an edit filter that is having problems pls see Wikipedia:Edit filter/Requested/Archive_12#Far-right/far-left. Other than that I think we should get our content from the best academic sources there are. There's a whole academic discipline dedicated to this so I don't foresee any problems finding high-quality sources..... it's one of those topics we don't need the news for.--Moxy (talk) 03:55, 7 January 2019 (UTC)

Moxy, the problem is though, as shown by the examples I provided, that reliable sources do not use the terms consistently with one other. Hence the Democratic Party of the U.S. can be reliably sourced as center, center-left or left-wing in books that agree on what its ideology is. It is centrist because it is a liberal party, center left because it is similar in some ways to European social democratic parties and left because it is the more left of the two major parties. Each of these descriptions only make sense if context is provided, which an info-box does not do. TFD (talk) 04:44, 7 January 2019 (UTC)

The current commonly used one-dimensional left-right political spectrum is inadequate for sorting political ideologies. That is because it is not clear what is the necessary characteristic(s) for an ideology or a political party to be categorized as left-wing or left-leaning, or to be categorized as right-wing or right-leaning. Is the left defined by social liberalism or by anti-capitalism? Is the right defined by conservatism or by pro-capitalism?

There are several reasons for this inadequacy:

Liberalism is characterized by the support for both liberties and equality. However, there are many areas in which the two came into conflict with one another. This has led to emphasis on one of the two over the other. The emphasis on liberties over equality have become known as classical liberalism, which then became part of libertarianism. The emphasis on equality over liberties have become known as progressive liberalism.
Conservatism needs to be anchored by its adherents to a specific culture in order to make clear what they are attempting to preserve or restore. In other words a conservative ideology needs a modifier. For examples, American conservatism, monarchism, Islamic conservatism, etc.
The relationship between fascism and other ideologies is complicated, causing its placement on the political spectrum a difficult one.

Because the reliable sources disagree with one another (for the reasons described above), I recommend that the use of a term with the word 'left,' 'right,' or 'center' in it be avoided entirely and that we let the terms such as 'progressive liberalism' or 'libertarianism' do the informing. VarunSoon (talk) 04:35, 7 January 2019 (UTC)

This would be ideal in my view...but don't think we'll be able to suppress the opinions and terms used by a specific academic community. I will support any policy that would use more academic specific terms over news use jargon.--Moxy (talk) 05:00, 7 January 2019 (UTC)

Removing the infobox parameter wouldn't mean that the terms couldn't be used in the article if there's something worth including. A lot of the time news sources offer a range of descriptions that aren't easy to condense into a two word phrase, and academic sources are slow to reflect changes. I'd support removing the infobox parameter if a proposal comes of this discussion. Ralbegen (talk) 16:39, 7 January 2019 (UTC)

The political left-right idea only goes so far. It's better to list actual ideologies than anything like "center-right" or "far-left". That's not even getting into other political compasses (8values, the authoritarian-libertarian axis, etc.) - PrussianOwl (talk) 23:04, 8 January 2019 (UTC)

Dark Mode

The title explains itself, really. Many white-background sites (YouTube, Reddit, Twitter, etc) are adding a "dark mode" option. Why doesn't Wikipedia add one? Xninetynine (talk) 01:16, 9 January 2019 (UTC)X99

@Xninetynine: See User:BrandonXLF/invert for a script that does this --DannyS712 (talk) 01:22, 9 January 2019 (UTC)

Wikipedia:Wikipedia Signpost/2018-12-24/News_and_notes -- PrussianOwl (talk) 01:26, 9 January 2019 (UTC)

@DannyS712: I looked at the example picture for the script. It reverses the colors, much the same way a Mac does, but because of this, it inverts the picture colors as well. A Wikipedia Dark Mode would have to keep the original colors, or everyone in the picture looks like some kind of demon. Xninetynine (talk) 18:01, 9 January 2019 (UTC)X99

@Xninetynine: I can try to work up a user script. --DannyS712 (talk) 18:04, 9 January 2019 (UTC)

@DannyS712: There is an option in Preferences that changes the display to black with green text (in my opinion, Wikipedia for Aliens). Maybe you could start there, in terms of writing a script. Xninetynine (talk) 18:11, 9 January 2019 (UTC)X99

There's already mw:Skin:Vector-DarkCSS (which works quite well, in my opinion) and a night mode will be developed as part of the community wishlist per m:Community Wishlist Survey 2019/Results Galobtter (pingó mió) 18:15, 9 January 2019 (UTC)

Colors for the edit filter log

When I "examine" an attempted edit that was disallowed, it takes me a while to see what changes were attempted. Can we get a few colors there to show what is different? Anna Frodesiak (talk) 14:11, 9 January 2019 (UTC)

@Anna Frodesiak: have you tried the 'details' view instead of the 'examine' view - it has diff screens. — xaosflux ^Talk 15:04, 9 January 2019 (UTC)

I say, Xaosflux, you're right. I'm sure I never saw the red diff at the top part of details. I remember telling myself ages ago, "Details doesn't tell the tale. Use examine." I must be going bananas. Please don't recall me on the grounds of insanity. It's treatable!

Anna Frodesiak (talk) 20:15, 9 January 2019 (UTC)

@Anna Frodesiak: You can try this one: User:Anomie/linkclassifier. Siddiqsazzad001 <Talk/> 04:34, 16 January 2019 (UTC)

I don't think that script will help with Anna Frodesiak's issue here. Anomie ⚔ 12:46, 16 January 2019 (UTC)

GDPR geoblocking

This was probably discussed before but I couldn't find anything in the archives. In the last six months a number of US websites have stopped showing content to EU users (e.g. NY Daily News, LA Times) or show a limited selection of the content (e.g. USA Today), and this doesn't seem to be going away any time soon. There's a number of workarounds that allow those of us in the EU to easily view those pages (Google Cache, Internet Archive, Archive.fo), however these are probably not known/used by the average Wikipedia reader who just wants to follow a reference. Hence I propose to automatically link pages from the GPDR-affected websites to the Internet Archive (easily possible via e.g. https://web.archive.org/*/https://...) for visitors who geolocate to the European Union.

I don't believe there are GDPR impediments to us doing so, since we'd be only linking to the Archive website which we do anyways and the restricted websites wouldn't be gathering EU users' data, and as for other legal issues we regularly link to archived versions of dead webpages from those sites anyway. I suppose this will require programming work, but the payoff will be big as there are many links to these websites on Wikipedia. Thoughts? Daß Wölf 18:06, 22 December 2018 (UTC)

Sounds good to me. Could be added to an existing bot WelpThatWorked (talk) 18:24, 22 December 2018 (UTC)

A bot? What would you want this bot to do? Bot's cant change content based on the private ip addresses of readers. — xaosflux ^Talk 18:53, 22 December 2018 (UTC)

For uses of {{cite news}} archive the source given in |url= at web.archive.org and note the archive address in |archive-url= & the date in |archive-date=. Cabayi (talk) 19:41, 22 December 2018 (UTC)

InternetArchiveBot managed by @Cyberpower678: and @Kaldari: deals with most of our archive.org stuff right now, would want to hear ideas from them. — xaosflux ^Talk 19:54, 22 December 2018 (UTC)

I don't think this is a good idea for a number of reasons. Legislative blocks are happening all over the world, there's no way we can constantly try to fix them. Blocks are at the mercy of human decree, they come and go constantly. Wikipedia is not so technically flexible to edit 100s of thousands (millions) of pages every time there is change in a block so that someone somewhere isn't blocked at that particular time and place. What about the blocks in China, much worse. The dead link system is meant to fix permanent dead links ie. link rot. It doesn't do well as a tool to fix political problems. -- GreenC 20:44, 22 December 2018 (UTC)

This is not a censorship, but a self-censorship issue: a small number of US companies have for whatever reason decided to close up shop rather than comply with EU privacy regulations. I'd rather not speculate on their motives. Yes, this does happen, and yes, they happen to own some major US news outlets, and do affect tons of pages on Wikipedia. However, unlike in the case of China, we can do something about it.

If we solve this via MediaWiki, e.g. by serving something like https://www.nydailynews.com/^{[original link]} in place of https://www.nydailynews.com/ to visitors who geolocate to the EU, we would avoid the disturbance of editing 100,000s of pages, but even preemptively adding archive links to these references would result only in a small eyesore for users outside the geoblock area. Daß Wölf 12:19, 23 December 2018 (UTC)

I personally always preemptively add archive links. Not every one favors that solution, but I think any potential for link rot is worse categorically. What could be done, besides such activity, would be to hack up a script making all links to certain websites go through archive.org. I would guess that this script would not have consensus as either a) for everyone or b) even just opt-out for logged in users, but it would at least be an opt-in for logged-in editors. --Izno (talk) 22:17, 22 December 2018 (UTC)

Some service for readers affected by American companies' geoblocking would be nice. But we could also just treat the LA Times like paywalled sources and try to use more open sources instead whenever we can. That is also better than sending a huge amount of workaround traffic to the Internet Archive that could potentially go to more accessible sources instead. —Kusma (t·c) 14:09, 23 December 2018 (UTC)

For news sources—which is what we're talking about here—there are strong arguments against the use of archive sites, since they provide a snapshot of the source at a given time and consequently won't show any subsequent retraction or correction. I can't imagine such a proposal ever gaining consensus. ‑ Iridescent 09:24, 6 January 2019 (UTC)
The GDPR question notwithstanding, Izno's idea seems to be a good solution generally, i.e. having a gadget affected users could use that automatically adds an IA link to (certain) sources so that those users could at least see the sources. Issues of later corrections exist already with offline news sources without them being disallowed. Regards So Why 10:18, 6 January 2019 (UTC)

User:SoWhy, Would this be a browser plugin? Similar to the official Wayback add-on [3]. -- GreenC 21:30, 7 January 2019 (UTC)

I think a userscript would suffice that people can turn on on this page. Javascript should be able to add a Wayback link to all external links in references if so desired. Regards So Why 06:42, 8 January 2019 (UTC)

I'm having trouble understanding how this is materially different from the problems we've been dealing with for years, e.g., that some Google Books or YouTube videos are only available to users who geolocate to particular countries. Why should we accept "This website won't show this content to people in Germany because of German copyright laws" but try to build a workaround for "This website won't show this content to people in Germany because of German privacy laws"?

(I wonder whether the decision to block content is primarily a business decision about expenses vs revenue, or if it might not be a deliberate act of civil resistance. Submitting to regulation by a foreign power – even if it weren't one that has somewhat weaker views on the freedom of the press – is not something that I really expect serious American newspapers to do unthinkingly.) WhatamIdoing (talk) 20:36, 21 January 2019 (UTC)

IDEAS: Need Your Thoughts on the Use of AI in Wikipedia

Many of you might not know, Wikipedia has already been using Artificial Intelligence to manage work. For instance, a team led by Aaron Halfaker designed the Objective Revision Evaluation Service, an open-source machine learning-based service designed to generate real-time predictions on edit quality and article quality. ORES has already been incorporated in over 20 Wikipedia applications to support a variety of critical tasks such as counter-vandalism, task routing and the Wikipedia education program.

We want to know your thoughts on how we should use AI in Wikipedia. Please reach out to me by bowen-yu@umn.edu or my talk page! We are working with Aaron Halfaker and his team to make ORES better. You can find more details on our project here. Look forward to hearing from you! Bobo.03 (talk) 01:51, 4 January 2019 (UTC)

Thanks for posting Bobo.03. I'm looking forward to working with anyone who is concerned/interested/etc. in AI's in our spaces. Our goal in working with Bobo is to better match ORES to the needs and values of editors. Please consider taking the time to let us know what you think. --Halfak (WMF) (talk) 15:56, 4 January 2019 (UTC)

ORES is being used in places other than vandalism. Am I correct that this step of development is focusing on that? Best, Barkeep49 (talk) 02:07, 5 January 2019 (UTC)

@Barkeep49: Yes, you are correct. We mainly plan to focus on vandalism-related applications for now. Bobo.03 (talk) 21:17, 7 January 2019 (UTC)

Thank you for this. A question which arises is how does one define Artificial Intelligence - for example, are bots A.I. ? Vorbee (talk) 09:13, 6 January 2019 (UTC)

@Vorbee: Good question! It's a board and open concept, and there is a whole Wikipedia page discuss it:) I think for us, we refer it as an algorithmic system implemented by machine learning. Does it make sense to you? Bobo.03 (talk) 21:22, 7 January 2019 (UTC)

Yes, that makes sense - I have had a brief look at the Wikipedia article on Artificial Intelligence. Vorbee (talk) 21:03, 8 January 2019 (UTC)

Throwing my hat into the ring: language detection of sources so that |language= can be filled in automatically. Actually I have no hats as I keep throwing them away. -- GreenC 21:22, 7 January 2019 (UTC)
This is done by reftoolbar's cite filling. Galobtter (pingó mió) 21:25, 7 January 2019 (UTC)
Oh nice. Do you know if it is AI-based detection? -- GreenC 21:37, 8 January 2019 (UTC)
Reftoolbar uses this bit of code which appears to mainly call m:Citoid for citation and language filling. Galobtter (pingó mió) 15:54, 9 January 2019 (UTC)
I believe that Citoid relies entirely on the language specified by the webpage, but User:Mvolz (WMF) could tell you with certainty. WhatamIdoing (talk) 20:38, 21 January 2019 (UTC)

Why not to link an only-text mode of visualization at the end of Wikipedia web pages?

Hi. Is there the possibility for switching to a text-only mode, without images?

At the end of the page users visualize a link "mobile view" or "desktop", enabling them to switch from a mode of visualizazion (mobile or desktop view) to the other.

It may be hopefully added a third text-only mode of visualizationthat is useful for users with visual impairments or with speed-up a slow Internet Connection, so as not to have to block images in their browser option settings, or to install a text-based web browser on their Internet devices.

A text-only mode can benefit the server workload, moving also to an even more improved [Web Traffic performance for those specific but non extraordinary operating scenarios. — Preceding unsigned comment added by 78.14.139.111 (talk) 23:23, 9 January 2019 (UTC)

Moved this discussion from Talk:Wikipedia#Why not to link an only-text mode of visualization at the end of Wikipedia web pages?. --Ahecht (TALK
PAGE) 15:46, 10 January 2019 (UTC)

Your browser can be set not to load external files (of certain kinds). If you want to speed up your receipt of this data, you should use the capabilities of your platform which could be used for all websites rather than our platform, which would only help you on Wikipedia. So no, we shouldn't do that work. --Izno (talk) 17:38, 10 January 2019 (UTC)

It seems to me that someone (Google?) was using a stripped-down version of Wikipedia for people in lower-bandwidth places (e.g., mobile users in India) a couple of years ago. I don't remember the details, but perhaps someone else will know more about it. WhatamIdoing (talk) 21:12, 21 January 2019 (UTC)

Sign up limitation

Accounts created which be limited to 5 users per IP on one year, to prevent sock puppets, vandalism and disruptive edits. Also, IP and user blocks should be extented. (Don't forget to ping me) ImmortalWizard(chat) 14:41, 19 January 2019 (UTC)

Ignoring the fact that IP addresses change, what about people that share an IP address with other library patrons, or university students that share an IP address with other people living in dorms? Should only 5 students per year be able to make a wikipedia account? Natureium (talk) 20:10, 19 January 2019 (UTC)

Natureium Well, I was just sayin' in general. Sidenote: in my uni, the ip is blocked. It should be somehow identified by experts which of them are larger ip addresses. 20:16, 19 January 2019 (UTC) — Preceding unsigned comment added by ImmortalWizard (talk • contribs)

This wouldn't work at all - I don't keep count but I would say I must get atleast 1 new IP each week or certainly 1 every other week .... so I would assume others in my area or who's got the same Internet provider as me would also get new IPs each week/every other week .... Can't see how this could work.... –Davey2010^Talk 15:28, 20 January 2019 (UTC)
Most people can get a new IP address at home whenever they want, so it won't stop anyone who's determined to have an account anyway. OTOH, it'd be a serious obstacle for anyone running Wikipedia:Edit-a-thons, which is the source of new accounts that is (by far) the least likely to be engaged in vandalism, spam, or sockpuppeting. WhatamIdoing (talk) 21:53, 21 January 2019 (UTC)
This would not be possibly without significant changes to the meta:Data retention guidelines , as IP information for registered accounts is limited to 90 days currently. — xaosflux ^Talk 21:56, 21 January 2019 (UTC)

An idea for the deprecation of indefinite blocks

I'd like to develop a proposal for deprecating the use of indefinite blocks. If the idea survives the scrutiny of this lab, I will. I am prepared to discard the idea, without animosity, if it does not. As a preventive measure, nothing appreciable is lost by using blocks with a prescribed duration instead; a duration capped at a maximum of perhaps 10 or 15 years. I realize that there are, and will continue to be, cases where the restriction is meant to never expire and suggest that in these eventualities, the respective accounts should be locked indefinitely, not blocked.

Since this is not a proposal, there's no "survey" section, and nothing to support or oppose, so: please don't. Please do: ask questions if things are not clear, mention concerns that you may have, and measures that could mitigate your concerns (if such mitigation is possible), speak with candor if you believe there is no realistic means to achieve the desired end, or if you feel the idea is lacking in merit or somehow in need, and most of all, be a colleague and expect the same from others as well. Thank you.--John Cline (talk) 09:57, 9 December 2018 (UTC)

Discussion (indefinite blocks)

Hello @John Cline: just curious to know what prompted this idea. Any specific incident? Additionally, what problem are you hoping this will solve? – Teratix ₵ 10:07, 9 December 2018 (UTC)
Thank you Teratix, for asking this of me. I apologize for the tardy reply which I did not anticipate. I have considered this (off and on) for several years as it relates to several users whom I esteem that have become indefinitely blocked for cause of some sort. I perceive that no appeal will ever succeed for them in spite of their eligibility to otherwise return and I lament the permanence of their absence. On the day I posted this idea I had noticed this edit on my watchlist involving Chzz, perhaps the most helpful editor I had ever had the privilege to know. In my opinion, deprecating the indef block in favor of a specified duration will resolve any such inability at negotiating while facilitating a return path for many qualified editors who rightfully deserve the chance that such quarter provides. Thank you again.--John Cline (talk) 06:43, 18 December 2018 (UTC)
I don't know much about the circumstances surrounding Chzz's block, and I couldn't hold a definitive opinion without access to the off-wiki evidence that led to the block. But as TonyBallioni noted when declining the appeal, Chzz does have options if they wish to appeal the block – the standard offer or an appeal to Arbcom. I don't think there is any reason why they wouldn't be unblocked if they submitted a convincing request. Even if this proposal was implemented, I'm struggling to think of editors who would be dedicated enough to Wikipedia to wait 10 or 15 years to return and would do something serious enough to receive a block of that duration, so I'm not sure there would be any difference in practice. – Teratix ₵ 08:52, 18 December 2018 (UTC)
You make several good points in your reply; I primarily agree. Remember this is an idea which is inherently rife with opportunities for improvement. It very well may be that 5 years is a better maximum than the 10 or 15 I originally suggested. I will mention one more editor that has been dedicated in his hope to one day return, in spite of what I regard as having been treated very poorly: Δ. I'd imagine he has accepted that appealing his block is a fools errand at best; and we are poorer for it, in my opinion.--John Cline (talk) 13:21, 18 December 2018 (UTC)
How would a 10 or 15 year block be better than an indefinite block? Any block may be repealed. I recently unblocked an editor that I had blocked seven years earlier, and haven't regreted it, yet. - Donald Albury 19:32, 9 December 2018 (UTC)
I agree Donald Albury that "any block may be repealed" (including a block of a specified duration) and that is certainly a good thing. Nevertheless, any appeal may likewise be denied and the difference is that the indef denial remains always in force where the set duration will expire on a given day which ensures that one's hope to return can become more than hopelessness which many former editors undoubtedly feel.--John Cline (talk) 06:43, 18 December 2018 (UTC)
What problem do you see this as solving? The entire point of "indefinite" is that it lasts until we see evidence that someone isn't going to repeat the issue that got them blocked. Why would someone who we deem unwelcome nine years after their block miraculously become welcome the following year? ‑ Iridescent 19:53, 9 December 2018 (UTC)
Thank you for your question Iridescent, I am sorry that my reply was delayed. You are absolutely correct that "the entire point of 'indefinite' is that it lasts until we see evidence that someone isn't going to repeat the issue that got them blocked" which is precisely the flaw that dooms the process as well. It is extremely rare, if ever, that we agree on anything let alone that a user will not repeat the problematic behavior that originally got them blocked, and hardly worth a derisive debate when any such recidivism can simply be re-blocked so much more easily. There's nothing miraculous about a formerly blocked editor using the rope given by this to show which intractable side (where consensus could not emerge) was actually correct.--John Cline (talk) 06:43, 18 December 2018 (UTC)
I am not aware of a problem with indefinite blocks. They are not handed out lightly. When they are given they almost always fall under one of three headings. Either the editor is clearly NOTHERE, their behavior has been judged as so disruptive that the community has banned them, or they have engaged in one or more activities generally understood as zero tolerance offenses. The idea of unblocking obvious vandalism only accounts because of the passage of some arbitrary time frame does not strike me as a good idea. -Ad Orientem (talk) 20:35, 9 December 2018 (UTC)
I agree with you Ad Orientem; there certainly are situations where the passage of an arbitrary time frame would not be enough justification for granting an unblocking of the account which is why I stated, up front, that "there are, and will continue to be, cases where the restriction is meant to never expire and suggest that in these eventualities, the respective accounts should be locked indefinitely, not blocked.--John Cline (talk) 06:43, 18 December 2018 (UTC)
I don't see this helping anything. Certain types of topic bans possibly should expire by default after 5 or 10 years; the effort in keeping track of the original cause after that long may not be worth it (and they can be re-imposed if necessary). Blocks, on the other hand, are easy to track as they will be related to the most recent edits in the edit history. power~enwiki (π, ν) 03:22, 11 December 2018 (UTC)
Thank you Power~enwiki, again I ask that you pardon my tardy reply; the circumstances were not of my design. One of the problems I have with the status quo is the inability to track and review related matters surrounding blocks and bans where I suggest an indef block adds to the woes, relates to the fact that the appeal is quite often processed off-Wikipedia, and the foundations determination not to acknowledge any third party standing whatsoever literally makes it impossible to inquire about the status of such a blocked or banned user. You often wouldn't know that an appeal had been endeavored at all (let alone why it was ultimately denied). At least if there was some cause related to conduct, the block log might necessarily reflect the failed appeal when and if the block was renewed to the maximum duration or changed to a locked status. These are all positive steps for openness and accountability, in my opinion, and enough reason to consider changing our current methodology.--John Cline (talk) 06:43, 18 December 2018 (UTC)
I don't understand this comment at all, and that if this is what you believe, your entire proposal is based on a fundamental misunderstanding. Except for a very small number of people who have been globally banned by WMF Legal (and who we couldn't unblock or vary the block terms of, even if we so wanted), the foundation has no input whatsoever into either blocks or unblocks on English Wikipedia. Someone wanting to appeal an indefinite block is entirely within their rights to use either the {{unblock}} template or to email UTRS but in either case their appeal is heard by English Wikipedia editors. If someone who's been blocked for five years, ten years, or whatever arbitrary period you choose is somebody who's unable to persuade a single admin that they should be given a second chance (it only takes one admin to unblock, after all) then they're almost certainly someone who remains unwelcome. ‑ Iridescent 20:30, 19 December 2018 (UTC)
Thank you for commenting, I appreciate it. I am sorry for the confusion my comments engendered. One thing that is clear, however, is the emerging consensus that this idea is not one the community would be willing to support. I am sufficiently dissuaded and prepared to move on. My thanks again, to you and all others for helping me realize these things. Cheers.--John Cline (talk) 07:08, 20 December 2018 (UTC)
Re-sending notification to Teratix, Donald Albury, Iridescent, and Ad Orientem which originally failed.--John Cline (talk) 07:08, 18 December 2018 (UTC)
Comment Per my above comment this looks like a solution in search of a problem that IMO does not exist. I would likely oppose any proposal along the suggested lines. -Ad Orientem (talk) 14:27, 18 December 2018 (UTC)
Thank you. I understand.--John Cline (talk) 15:48, 18 December 2018 (UTC)
Thanks for bringing this up here, I think it's good that we scrutinize our policies from time to time. I think, perhaps, you have confused "indefinite" with "infinite" in your suggestion - we do not block accounts forever (although some wikis do, eswiki I believe has a "permanent block" in their policy) but there are some indefinite blocks for which the conditions for lifting are unattainable (i.e. blocked sockpuppets). I personally would counter with an argument in the other direction: all blocks should be indefinite, meaning simply that they have no fixed expiry and are entirely dependent on the blocked user indicating they understand why they were blocked and will not repeat the behaviour. If they do then the block is lifted, and if they do not then they remain blocked. Blocks with fixed duration are inherently inequitable: the duration of a block is dependent on the blocking admin's assessment of the severity of the situation, and so sanctions for the same misconduct vary greatly depending on which of the several hundred independent administrators happens to be first to act. If we had a table of offences and recommended sanctions then perhaps this would be less of an issue, but we don't, it's just the wild west out there. And of course IPs should not be blocked without a fixed expiry, so maybe this whole thing is just out the window. I guess I'm kind of off on a tangent now. Thanks for the morning thought exercise, anyway :) Ivanvector (^Talk/_Edits) 14:05, 20 December 2018 (UTC)
You're welcome Ivanvector, and thank you for sharing your insight, as well: greatly enhancing the discussion with thoughtfully placed comments of worthwhile consideration. I am certainly glad that they came before me. Best regards.--John Cline (talk) 22:18, 23 December 2018 (UTC)
Oppose Standard offer is available for indef'd editors as is the option for the indef'd editor to edit on other Wikipedias to show that they are still capable of being constructive. Putting arbitrary number lengths on it don't seem to be the answer. I do agree however that someone who vandalizing when they are 12 can be constructive editing when they are 21 but that in no way justifies putting excessive block lengths as opposed to indeffing.JC7V (talk) 22:13, 4 January 2019 (UTC)
- I don't think you meant quite that. For many editors here, "edit on other Wikipedias" would require learning another language first, which is surely not intended to be a requirement. Most people who try the standard offer go to another English-language wiki, e.g., Wikisource or Commons. WhatamIdoing (talk) 19:21, 21 January 2019 (UTC)
Oppose Ad Orientem almost verbatim expressed my thoughts. PrussianOwl (talk) 23:00, 8 January 2019 (UTC)
John, it sounds like you'd prefer a situation in which indefs were more clearly sub-divided into two classes, approximately meaning "Hopefully short" (e.g., editors who need to make some changes) and "Never" (e.g., spammers). Splitting these would more clearly communicate the blocker's intentions. WhatamIdoing (talk) 19:29, 21 January 2019 (UTC)
It would be an inherent result; and yes: one which I would prefer. Nevertheless, I have acquiesced the opposing rationale, and remain.--John Cline (talk) 09:21, 22 January 2019 (UTC)

Idea for new wikiproject: article components

I have a new idea for a WikiProject.

Name Wikipedia:WikiProject Article Components;
- Other possible names: Wikipedia:WikiProject Article Elements
- Wikipedia:WikiProject Article Sections
- Wikipedia:WikiProject Article Structure
- Wikipedia:WikiProject Article Format
- key focus: add common sections to articles; such as:
  - "See Also" section, and
  - at least one Nav Box
- Possible effects:
  - promote awareness of broad topical areas at Wikipedia, showing clear relationship between articles and topic.
  - "See also" sections and nav boxes might become as common as categories; i.e., would show broad connections within topical areas.
- Other possible sections to include:
  - "External Links"
  - at least one portal link for each article as well.

feel free to provide any comments. thanks!! --Sm8900 (talk) 15:24, 12 February 2020 (UTC)

Adding a navbox often (usually?) implies updating the navbox to include the article to which it is added. This would usually be a good thing as long as the navbox is appropriate to the article. There will probably be some people opposed to adding navboxes because this is Wikipedia, and there are usually some people opposed to anything. A project for this could help.
A see also section is only useful if there are links that need to be there. If a see also section is added, it would be helpful to annotate the links as recommended in MoS so that the reader has some idea of what they are about. Tooltip popups give the start of the lead section, but sometimes that does not help, and tooltips popups are not universally available.
External links. See comment about 'See also' sections. Add 'External links' sections only when there are valid external links to add.
Most articles are not included in a portal. What level of association with an existing portal would be acceptable to justify a link?
Are there no existing projects which already cover this scope, or could be slightly expanded to include this scope? · · · Peter Southwood ^(talk): 08:11, 13 February 2020 (UTC)

I love navboxes but my love for them has meant that I particularly notice when others say they are a scourge of the site, because I feel very sad when they say so. At this point, I'll just wish you good luck and warn that you're likely to encounter quite some resistance in bringing more navboxes to Wikipedia, but I wish you all the best. --bodnotbod (talk) 10:21, 13 February 2020 (UTC)
Rather than a wikiproject, have you considered a signpost article or two? This would give you the opportunity to explain why you think such changes would be helpful, if you make a good case you are likely to influence many editors. I suspect that others from the opposite extreme will make a case as to why the See also section is really a temporary parking ground for links that should be included in the article. But for such changes discussion is a good start, then if you have consensus that these changes would improve the pedia, try making the appropriate changes to MOS and the FA criteria. WikiProjects are most common in covering particular topics, they can also be useful in maintenance, but best to get consensus first Ϣere SpielChequers 11:04, 13 February 2020 (UTC)
Rather than a new WikiProject, you might try reviving WikiProject Navigation templates with a slightly broader focus. I agree with other comments' points that the navigational sections mentioned are not always desirable; these essays on avoiding template creep and how not everything needs a navbox provide vivid examples of how well-meaning additions can work out poorly. – Teratix ₵ 13:13, 13 February 2020 (UTC)

Okay, all of these comments sound interesting. I appreciate all of the comments and ideas here. thanks!!! --Sm8900 (talk) 17:56, 20 February 2020 (UTC)