Wikipedia:Village pump (proposals)/Archive 156

Proposal/RfC: Allow ISBN warnings on articles talk pages with ISBN errors
I can do this using my bot. There is a feature on WPCleaner called "Update ISBN warning messages" on WPCleaner. I have been having a discussion about this feature around two weeks ago. The discussion can be found Wikipedia talk:WPCleaner. The feature adds and removes ISBN warning messages on the talk pages of the affected articles. It tells the ISBN that is affected and it also tell the reason why the ISBN is affected. This will help Wikipedians fix ISBNs much more easily on English Wikipedia. The template is at User:NicoV/ISBN Warning at the moment. This needs to be moved to Template:ISBN warning. The talk pages with an ISBN warning message will be added into Category:Articles with invalid ISBNs. The WPCleaner script can add the warning message for the affected articles and remove the warning message for the articles that have been fixed automatically. I have tested this on my sandbox and it works. This feature is already available on French Wikipedia and User:NicoV kindly said that he can configure WPCleaner so that this can also happen at the English Wikipedia. The output looks like this:

Shall we have this brilliant feature which will help the identification of incorrect ISBNs on English Wikipedia? Pkbwcgs (talk) 10:19, 31 December 2018 (UTC)
 * I thought we already get error messages from apparently faulty ISBNs (and note that this sometimes includes the ISBN as written on the book) - how will this proposal improve things?Nigel Ish (talk) 10:24, 31 December 2018 (UTC)
 * It will only do this to some ISBNs. At the moment, the ISBN errors are in the form of a list. It will also report incorrect ISBN formatting as well and it doesn't say that directly. Pkbwcgs (talk) 10:29, 31 December 2018 (UTC)
 * This can also be updated automatically and this makes it easier to locate faulty ISBNs. I am not sure exactly if it will tell the reason why the ISBN is faulty but this can be added manually. It will certainly list the faulty ISBNs. Pkbwcgs (talk) 10:33, 31 December 2018 (UTC)
 * The main interest I believe is that it's not restricted to ISBN created with templates (which can already be detected as invalid by the template), but it also works for ISBN created with the magic syntax. For example, note 189 on List of shipwrecks in 1946 is using an invalid ISBN but it's not detected because it's done using the magic link. WPCleaner uses several sources for finding invalid ISBN: categories, Check Wiki project, dump analysis... Errors found are listed in WikiProject Check Wikipedia/ISBN errors but the editor of an article is currently unaware of this. --NicoV (Talk on frwiki) 10:44, 31 December 2018 (UTC)
 * It also detects some cases of incorrect syntax which do not produce a magic link (nowiki tags around the ISBN, a colon between ISBN and the number...). --NicoV (Talk on frwiki) 10:46, 31 December 2018 (UTC)


 * I like the idea of a bot that can fix faulty ISBNs. Can I just ask will it do the same for faulty ISSNs (International Standard Serial Numbers)?Vorbee (talk) 14:39, 2 January 2019 (UTC)
 * I think the RfC launched by Pkbwcgs is only for reporting faulty ISBNs with a bot on the article's talk page, not fixing them with a bot. I can probably add some automatic fixing in WPCleaner for ISBN at some point, but it will probably be limited to format problems (wrong dashes, colons, dots...), not problems with the ISBN number itself (wrong length, incorrect checksum...) as it is really difficult to automatically know what is the correct ISBN (or even if the faulty ISBN is real...). Regarding ISSNs, WPCleaner can do the same as with ISBNs, it's just a matter of creating a dedicated warning template and configuring WPCleaner (it's already doing it on frwiki): Pkbwcgs will probably launch another RfC for ISSNs if this one is accepted and it has been put in production. --NicoV (Talk on frwiki) 16:35, 2 January 2019 (UTC)
 * I am doing a lot of help for ISBNs. I got RegEx ready that is ready for my bot to fix faulty ISBNs using AWB (PkbwcgsBot task 5) and I got approval for updating the list of articles with faulty ISBNs and ISSNs everyday (PkbwcgsBot task 8). The faulty pages are listed at WikiProject Check Wikipedia/ISBN errors. However, we don't have ISBN warnings on article talk pages which means that users are unaware of some ISBN errors so notices on talk pages that tell which ISBNs are incorrectly formatted or are invalid. If this RfC succeeds, I will wait for User:NicoV to configure this feature for English Wikipedia and then submit a BRFA for my bot to add and remove these ISBN warning messages everyday using WPCleaner. As User:NicoV said, I will submit another RfC for ISSNs if this one succeeds. However, the top priority is for ISBNs because WikiProject Check Wikipedia/ISBN errors has a huge and long list of faulty ISBNs. Pkbwcgs (talk) 17:11, 2 January 2019 (UTC)
 * If you're interested to see the end result, I've configured WPCleaner on my test account to show it: check User talk:NicoV/List of shipwrecks in 1946 for the message that's written. Each part of the message can be configured (either in Checkwiki's configuration or in WPCleaner's configuration). --NicoV (Talk on frwiki) 18:12, 2 January 2019 (UTC)
 * It looks good but that feature is not working on my WPCleaner test version at the moment. It says "You need to define the 'isbn_warning_template' property in WPCleaner's configuration". Pkbwcgs (talk) 18:30, 2 January 2019 (UTC)
 * Yes, it's because I did the configuration only in my test account (NicoVTest), so the configuration is not available to others. And I also modified WPCleaner to allow user's specific configuration for some parameters. If this RfC is accepted, we can put the configuration in the general configuration page. --NicoV (Talk on frwiki) 20:50, 2 January 2019 (UTC)
 * Okay. I have one question. Will this feature automatically report what is wrong with the ISBN (e.g. incorrect checksum, ISBN too long etc.) and tell this information in the ISBN warning message? Pkbwcgs (talk) 20:54, 2 January 2019 (UTC)
 * It will give the same level of details as the example User talk:NicoV/List of shipwrecks in 1946: for example, in the example, the message says that the checksum is incorrect. Messages can be customized i, Checkwiki's configuration, with some variable parts. --NicoV (Talk on frwiki) 21:25, 2 January 2019 (UTC)
 * That is a brilliant feature and I am sure it will benefit English Wikipedia by users being aware of what is wrong with the ISBN so that it can be fixed. Thanks for creating that feature. I am sure it will help. Pkbwcgs (talk) 22:05, 2 January 2019 (UTC)
 * the first one of these that I check: 0 7209 3995 2 in Lepidosperma squamatum matches the number in the published work at http://museum.wa.gov.au/sites/default/files/1.%20Storr_5.pdf so what do you do about that? Is the number in print authoritative? Graeme Bartlett (talk) 22:45, 2 January 2019 (UTC)
 * That's a good question Graeme Bartlett, and unfortunately I don't have a definitive answer that works for each case. For your example, the ISBN doesn't match the rules for constructing an ISBN: the computed checksum is "X", but the ISBN shows "2".
 * As I mostly work on frwiki, I can explain what I do for books in French: the authority for ISBN published in French (ISBN starting with 2, 978-2 or 979-10) is the French National Library. I usually search there for the book and if the notice exists, it will say either
 * #1) that's actually the ISBN but it is errorneous (in that case, I use a special parameter "isbn erroné" instead of "isbn" to clearly state that the book has been published with an errorneous ISBN)
 * #2) there's an other ISBN (in that case, I user the ISBN on the notice)
 * #3) that's actually the ISBN but nothing says that it is errorneous (in that case, I report the problem to the BNF and they usually fix it within a week, so I end up with case #1 or #2)
 * For books in English, I don't know if there's such an authority... I use Worldcat a lot for them, but I find it useful only when the ISBN in the article is not the same as the one in the notice. In your case, Worldcat has only 2 entries for this book and  and none of them gives the ISBN. Same for the National Library of Australia... So I don't know for this one. Maybe remove the ISBN from the article and use the OCLC or NLA link ? Or consider that the ISBN in print is authoritative and have a special parameter for the cite template to acknowledge that ?
 * I think that before running a bot to put the message on all talk pages, it could be good to do a first pass manually with WPCleaner to fix the easiest ones (CHECKWIKI/WPC 069 dump: invalid syntax, CHECKWIKI/WPC 070 dump: the ones that have the 10 or 13 prefix). --NicoV (Talk on frwiki) 07:53, 3 January 2019 (UTC)
 * I am also going to configure this feature and test it in my userspace. Pkbwcgs (talk) 11:39, 3 January 2019 (UTC)
 * The version of WPCleaner that is available publicly doesn't allow user specific configurations for ISBN warnings (I modified locally my source code to do it with my test account). But I think you can try to configure it on the general configuration page User:NicoV/WikiCleanerConfiguration if you want : in normal use (not bot mode), WPCleaner will only update an existing warning, not create one (that's why I manually created User talk:NicoV/List of shipwrecks in 1946/to do), and only if the modification on the article page has fixed any ISBN related problem. After your test, comment out the configuration to be sure. --NicoV (Talk on frwiki) 11:50, 3 January 2019 (UTC)
 * I am trying it on Benfleet railway station (reference 2 has an ISBN error). My configuration is located at User:Pkbwcgs/WikiCleanerConfiguration and the article in my userspace is located at User:Pkbwcgs/Benfleet railway station. The to do page is located at User talk:Pkbwcgs/Benfleet railway station/to do and the talk page is at User talk:Pkbwcgs/Benfleet railway station. However, the test is not working. What am I doing wrong? Pkbwcgs (talk) 12:03, 3 January 2019 (UTC)
 * Check my previous message: #1 you have to do the configuration in the main configuration's page User:NicoV/WikiCleanerConfiguration because user's specific configuration is not accepted by WPCleaner for those parameters. And you also have to fix at least something related to ISBN in the page User:Pkbwcgs/Benfleet railway station to trigger update of the ISBN warning. Otherwise, everything is done in bot mode, but it's not possible to select on which page it will work. --NicoV (Talk on frwiki) 12:41, 3 January 2019 (UTC)
 * Am I allowed to configure this feature on User:NicoV/WikiCleanerConfiguration and when I am done with testing, shall I revert it? Pkbwcgs (talk) 16:05, 3 January 2019 (UTC)
 * Yes, I think you can change User:NicoV/WikiCleanerConfiguration, use User:NicoVTest/WikiCleanerConfiguration to see what is needed. When you're done testing, you can either revert your modifications or just put them in comment (a # at the beginning of a line is a comment). --NicoV (Talk on frwiki) 16:16, 3 January 2019 (UTC)
 * For some reason, the feature is not changing anything. It is only saying it is retrieving the contents. Pkbwcgs (talk) 16:35, 3 January 2019 (UTC)
 * You have to fix an ISBN problem in your test page with WPCleaner to trigger the update (I did this one for my test). --NicoV (Talk on frwiki) 16:47, 3 January 2019 (UTC)
 * I forgot that there was a menu to add the ISBN warning directly, that's why I was talking about fixing an ISBN in the page. But, I tried to add the warning through the menu and it didn't work: I probably have to modify something in my code to handle the configuration for enwiki (it's different than frwiki). I'll keep you posted. --NicoV (Talk on frwiki) 16:57, 3 January 2019 (UTC)
 * It updated the ISBN warning message here. However, I think English Wikipedia would benefit from this if this warning message can be directly added and removed from the talk page of the article by my bot rather than having another "To do" subpage to make this feature work. Pkbwcgs (talk) 18:32, 3 January 2019 (UTC)
 * Your feature works brilliantly. It was unexpected as I pressed the wrong button but I reverted the edits. However, things like this diff would absolutely benefit Wikipedia. Pkbwcgs (talk) 21:06, 3 January 2019 (UTC)
 * WPCleaner can put the warning directly on the talk page or on the subpage depending on the configuration. The parameter  is for adding a template directly on the talk page (that's what happened in this diff): I think it's not correctly configured for enwiki as todo doesn't accept the list of tasks as a parameter. The parameter   is for the name of the subpage to use when the warning is put on the subpage. To decide whether or not to put the warning on the subpage or on the talk page:   forces the use of the subpage regardless of the other tests ; if the subpage already exists then the warning is put on the subpage ; if there's already a template on the talk page that provides a link to the subpage (from , which seems to be the correct list for todo) then the warning is put on the subpage. --NicoV (Talk on frwiki) 10:16, 4 January 2019 (UTC)

As can be seen in (and in the example in the OP) the rendered template has broken list markup (one asterisk is displayed as such; and a final line has two, not one, bullet points). This needs to be fixed, before any bot run please. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 11:28, 4 January 2019 (UTC)
 * That is a good point. I am actually not sure how to fix that problem. The template is located at User:NicoV/ISBN Warning at the moment if you would like to fix it there. It is transcluded through Template:To do so the problem could also be in that template as well. I have tried to fix it but it didn't work. Pkbwcgs (talk) 12:37, 4 January 2019 (UTC)
 * See User:NicoV/ISBN Warning/Sandbox. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 17:07, 4 January 2019 (UTC)
 * That looks good. Can you please amend WPCleaner so that this feature makes the template render as:

We don't need a "to do" subpage for every talk page; I think it is updating fine so please don't change that. However, we want the line space after. Pkbwcgs (talk) 18:57, 4 January 2019 (UTC)
 * You can try the last version... --NicoV (Talk on frwiki) 23:07, 4 January 2019 (UTC)
 * What do you mean by the "last version"? Pkbwcgs (talk) 12:03, 5 January 2019 (UTC)
 * If you're running WPCleaner normally (throught getdown, or with the provided scripts), it should update itself automatically to the release I did yesterday. Version number is the same. --NicoV (Talk on frwiki) 12:21, 5 January 2019 (UTC)
 * Shall I move the working ISBN warning template from User:NicoV/ISBN Warning to Template:ISBN warning? Pkbwcgs (talk) 12:25, 5 January 2019 (UTC)
 * It will be better if you wish to run the bot. --NicoV (Talk on frwiki) 13:22, 5 January 2019 (UTC)
 * Okay. I would still prefer to gain some consensus before I file the BRFA for this to run. Pkbwcgs (talk) 13:31, 5 January 2019 (UTC)
 * No problem. My own advice would be to rename the template and its documentation subpage, add a note on the documentation saying that consensus is required before using it. At least, you're sure you won't have to modify manually warnings put with the incorrect template name... --NicoV (Talk on frwiki) 14:06, 7 January 2019 (UTC)

Bot to add Template:reflist-talk
There is a bot proposal to add to talk pages that would benefit from it.

The bot would do this:


 * Edit

Do you think this is a good idea?

How pages look with
 * Talk:1923 in literature

How they look without:


 * Talk:Hayashi Hōkō
 * Talk:Brezovica pri Borovnici
 * Talk:Sa'ad Al-Faqih
 * Talk:Freeport-McMoRan
 * Talk:8
 * Talk:E
 * Talk:Propaganda in the Soviet Union
 * Talk:Buildings and architecture of Bristol
 * Talk:Detection limit
 * Talk:Plasmodium ovale

Problems when is missing:
 * Citations get mixed together at the bottom of the page with citations from other sections on the page
 * In long talk pages, clicking the sup-script [1] back and forth is burdensome and hover-over doesn't work (Example)
 * The autogenerated list is mixed in with the last section giving the appearance that section has the citations (Example)
 * Will prevent editors trying to fix the problem by adding template is present. I oppose option B because the bot could encounter the article at a moment when it does not reflect the long-standing consensus. Also, it would be inappropriate to have different criteria for bot edits than for manual edits; if a bot were allowed to change on the basis of the majority of the dates in citations, it would be OK for manual edits too. But currently it not OK for manual edits. Jc3s5h (talk) 21:54, 17 December 2018 (UTC)


 * I clarified a few things. Some words were missing. Also, it is not only ok, but encouraged for humans to do those sort of changes. Headbomb {t · c · p · b} 21:58, 17 December 2018 (UTC)
 * The expectations in MOS:DATEUNIFY would indicate an editor should not change an access-date from 2008-11-18 to November 18, 2008 just because the majority of all citation-related dates was mdy, so long as all or nearly all access-dates used the YYYY-MM-DD format. Also, if the article almost exclusively used mdy in the article overall, because most of the citations only gave a year, just counting a handful of citations that did give a month, date, and year could easily give a false result. Jc3s5h (talk) 22:21, 17 December 2018 (UTC)
 * If the citations don't match the body of the article, then the body didn't really make the article worse than it was before, since it was already inconsistent. If it normalized the citations the 'wrong way', just slap either Use dmy dates or Use mdy dates on it and you'll ensure the long-term stability of the article dates. Headbomb {t · c · p · b} 03:48, 18 December 2018 (UTC)
 * We have had a recent discussion which rejected the expectation that the access date be in the same format as any other dates (only that the access dates be unified among themselves was a consensus there). That's this discussion, which, probably should have been closed as "consensus against" the proposal rather than the "no consensus" close by Compassionate. --Izno (talk) 00:25, 18 December 2018 (UTC)


 * Uggh is this really a mess that needs to be dealt with at all? Citation parameters aren't "prose" they are "data" - they should just be in ISO format. Can you show some good examples of versions of an article that have this "problem"? —  xaosflux  Talk 03:30, 18 December 2018 (UTC)


 * ISO/YYYY-MM-DD are relatively rare in dates save for accessdates. But for a good example, see Cancer, with several inconsistent dates the bot could fix. Headbomb {t · c · p · b} 03:51, 18 December 2018 (UTC)
 * OK, so in Cancer we have:

Bast RC, Croe CM, Hait WN, Hong WK, Kufe DW, Piccart-Gebhart M, Pollock RE, Weichselbaum RR, Yang H, Holland JF (3 October 2016). Holland-Frei Cancer Medicine. Wiley. ISBN 978-1-118-93469-2.

Kleinsmith LJ (2006). Principles of cancer biology. Pearson Benjamin Cummings. ISBN 978-0-8053-4003-7.

Mukherjee, Siddhartha (16 November 2010). The Emperor of All Maladies: A Biography of Cancer. Simon & Schuster. ISBN 978-1-4391-0795-9. Retrieved August 7, 2013.

Pazdur R, Camphausen KA, Wagman LD, Hoskins WJ (May 2009). Cancer Management: A Multidisciplinary Approach. Cmp United Business Media. ISBN 978-1-891483-62-2. Cancer at Google Books. Archived from the original on 15 May 2009.

Tannock I (2005). The basic science of oncology. McGraw-Hill Professional. ISBN 978-0-07-138774-3.

Schwab M (23 September 2008). Encyclopedia of Cancer. Springer Science & Business Media. ISBN 978-3-540-36847-2.


 * What will be changed there - the access date in #3? —  xaosflux  Talk 04:10, 18 December 2018 (UTC)


 * diff. Headbomb {t · c · p · b} 04:39, 18 December 2018 (UTC)
 * thanks for the example, any idea what sort of volume you are trying to address? I'm only seeing this minimally beneficial to readers, with month names already spelled out it isn't fixing any ambiguity. —  xaosflux  Talk 14:13, 18 December 2018 (UTC)


 * honestly it's pretty hard to gauge. I'd guess that in the ballpark of 10% of articles have date inconsistancies, but I don't know how much of that could be fixed by bot before things are trialed. Headbomb {t · c · p · b} 16:25, 18 December 2018 (UTC)
 * 10%! ~ edits just to tweak some date formatting in the references section seems quite excessive to me, are there good arguments for how this will improve usability for readers? — xaosflux  Talk 17:24, 18 December 2018 (UTC)


 * Wouldn't be 10% of all articles edits, just ballpark 10% of articles with MOS:DATEUNIFY issues somewhere, only a fraction of which are in citation templates, and only a fraction of which could be addressed by bots. Headbomb {t · c · p · b} 17:43, 18 December 2018 (UTC)
 * It might be more than 10% if it is fixing mdy/dmy inconsistencies which are common. But if it wasn't a "fast bot" (immediate fix) rather the slow boat to China for a year to process all 5.5m articles, before starting over, changes are saved up and it doesn't thrash watchlists. I think the pro argument is people seem care about fixing date formats so it would save labor - the number of cites being added is exponential compared to number of qualified editors - it keeps getting worse over time. This proposal should be linked from the FA and GA forums as they tend to be most focused and might have concerns we don't know about. --  Green  C  18:10, 18 December 2018 (UTC)


 * 2 Questions - 1) If option B was used, which states "in addition to the above", what happens if the DMY/MDY statement conflicts with majority usage? Which wins?
 * 2) What do we do about date style squabbles? Some articles, usually those with both British and American topics involved, have some mind-numbing disputes over date styles. Would this bot freely replace each date set, each time the DMY/MDY requirement is edited? Nosebagbear (talk) 16:14, 28 December 2018 (UTC)


 * could be several options, but the way I envision things I'd see Use dmy dates/Use mdy dates trumping everything else, since someone placed that on purpose. If there's a squabble, decide which of the two to use, and the bot will follow that decision. Headbomb {t · c · p · b} 21:22, 28 December 2018 (UTC)

Overview
Former discussion: Bot_requests.

The idea is to create a bot/template pair that sends on request a reminder to go back to a particular page. The case use is typically to check back on a discussion on high-traffic pages where a watchlist is inefficient or (on the contrary) when the discussion has very little participation and you want to make sure to come back one week afterwards to assess consensus.

As the reminder would likely take the form of an in-wp post, such a bot needs consensus per WP:BRFA. I believe VPP to be the best (or least worse) forum for that discussion, but do tell if I missed something obvious.

Envisaged technical implementation
A template (e.g. ) that takes one argument, either a fixed date or a duration of time, is left by a user on the page they wish to be reminded of. Template transclusions are watched by a Toolforge bot (running every hour or so?). When the time is up, the bot posts a notification to the requesting user's talk page.

Asking for a notification by this process is public (i.e. other editors know that you asked for an update, when you asked for it etc.).

Depending on the technical details, and if that template gets widespread use, it might become necessary to put limits on the use. I would suggest no more than X pending notifications per user (so that you can put hanging notifications for Christmas 2118 but it eats up one of your slots); I think X=10 is a reasonable starting value if it comes to that, but I do not think it is needed outright.

Possible objections

 * 1) While the bot postings themselves are fairly innocuous (you get 'em only if you ask for 'em), there could still be some clutter in the reminder request templates: e.g. if 100 posters drop just a "remind me" template in a discussion where 5 people are actually participating. I believe (1) that is quite speculative and (2) if it ever becomes a problem, it might be solved by conduct guidelines (e.g. "avoid using this template outside an overwise meaningful post, as this can be considered disruptive").
 * 2) As pointed in the previous discussion, that might duplicate a Community Wishlist item that was among the top 10 (and hence will be worked on by WMF staff). I believe the use case is slightly different (that one is targeted at talk pages, as opposed to articles), and even if it is indeed redundant, I do not see the harm. (As I will be the one handling the bot coding, time wasted duplicating a system can be ignored: I think it would be fun to code. The only question is whether having two systems might be harmful, not useless.)

Comments
I have a better design.

Make a bot that you place on your own talk page (or on a special page if that makes the bot easier to write) with the same fixed date / duration of time arguments.

If I put

on the appropriate page It would wait until January of 2038 and then post the following to my talk page:


 *  Remindme bot reminder notice 


 * On 00:00 1 January, 1970 03:14 (UTC), you requested a 03:14, 19 January 2038 (UTC) reminder. The text of the reminder is:


 *  Check Talk:Cockcroft–Walton generator for replies 


 * -- [Bot signature]

That way you could be reminded of anything. I have a similar reminder set locally that I use to remind me to check the edit history of blocked IP vandals a week after the block expires. That way I can report them if they go right back to vandalizing.

To reduce abuse:

The reminder should happen even if some vandal deletes the request.

There should be a way to cancel a reminder.

Users or admins should be able to cancel reminders for that user.

Reminders should be limited to 255 characters.

Users should be limited to no more than 32 open reminder requests.

A FAQ should explain that this is for Wikipedia-related use only; no "don't forget to buy more Vegemite" reminder requests.

If possible, it should be impossible or at least difficult to set a reminder to be shown on someone else's talk page.

--Guy Macon (talk) 14:06, 18 December 2018 (UTC)


 * If this were done on a user "JSON" page (eg User:Example/remindme.json) it would be: simpler for bots to parse requests (I think), restricted to editing by the same user, or administrators (meaning that vandalism is not an issue, and if the reminder is only sent if the request is present at the time specified, allows cancelation), makes it easier to limit requests (only pay attention to the first 32 json objects). Thoughts? --DannyS712 (talk) 00:59, 27 December 2018 (UTC)


 * Can't you just make a bot-less design? Just put a template on your userpage that displays blank until time XXX, and then displays the reminder you wish it to display. You could probably make a user script that automatically adds such a reminder from any page. —Kusma (t·c) 11:04, 12 January 2019 (UTC)
 * I could start working on a user script, which (i think) wouldn't need community approval (like a bot) because its a script, and would just edit in userspace... --DannyS712 (talk) 17:33, 12 January 2019 (UTC)

Community Wishlist
Hi guys, I might be misreading things, but does this not sound like one of the things in the top then of the community wishlist Article Reminders? Nosebagbear (talk) 19:55, 18 December 2018 (UTC)
 * It does. IMO people interested should get involved with the creation of that feature than rush to implement a bot to do mostly the same thing. Anomie⚔ 03:02, 19 December 2018 (UTC)
 * Indeed. I concur with Anomie. I wouldn't spend too much time on a bot/user script right now. The long-term solution might end up being a MediaWiki extension, which would address the possible objection about bot postings (since there'd be no bot involved). I suspect the implementation would allow for reminders about any page. To be clear, this project isn't "owned" by WMF, per se, rather it's now their responsibility. There have been top 10 wishes implemented by volunteers in the past. So, if you are eager to code you most certainly can be a part of it :) We just need to find the right solution first, one that accommodates the necessary workflows and will work for all wikis.  &mdash; MusikAnimal  talk  23:34, 30 December 2018 (UTC)

Background
In July of 2018, Wikimedia made a call for proposals at their grants idea lab. The request called for ideas to improve Wikipedia community health. My first thought was that although some high-tension areas of Wikipedia are well trafficked and watched, there may be other less visible areas where discussion health may be an issue.

Proposal (Health rating)
To make a template which can be optionally placed at the top of a talk page, with radio buttons, check boxes or single-select options ranking a talk page's health.
 * Information would then
 * Be used to identify areas requiring feedback
 * Create statistical data about areas requiring attention

Wikimedia proposal page
Some discussion regarding this proposal has taken place at Wikimedia
 * the discussion includes:
 * A basic description of the proposal
 * Some example screen shots
 * A call for required experts and collaborators on the project
 * Some ideas about how to proceed on en-wiki.
 * This proposal has been mentioned at Wikipedia_talk:Community_health_initiative_on_English_Wikipedia

Edaham (talk) 02:52, 4 January 2019 (UTC)

Discussion (Health rating)

 * What are the ranking criteria? Personal opinion? If so, what useful purpose would this serve? Would there be any actionable consequences? &middot; &middot; &middot; Peter Southwood (talk): 06:00, 6 January 2019 (UTC)


 * I don't see the point in this, especially since what's a 'healthy' or 'unhealthy' talk page is not something that can be turned into an algorithm. Headbomb {t · c · p · b} 15:21, 6 January 2019 (UTC)
 * I'd go as far as to say that if anyone tried to add this to talk pages, I'd bulk revert and block them for disruption. Someone unilaterally declaring that pages they like the look of are "healthy" and pages they don't like the look of are "unhealthy" is about as uncollegial as one could get. Per the others above, what do you consider "healthy" and "unhealthy", anyway? Is a talkpage full of arguments an unhealthy sign because it's causing people to argue, or a healthy sign because it shows the community is engaged? Is a talkpage that hasn't had a single comment in six years a sign of poor health, or a sign that the attached article is so fantastic nobody can suggest any way to improve it? How do you prevent the usual lunatic fringe from canvassing all their friends to go and mass-downvote Climate Change, Rope worms or Gamergate controversy as "unhealthy"? &#8209; Iridescent 15:52, 6 January 2019 (UTC)
 * (adding) Having now read the proposal in full, changing from "no" to "hell, no". The whole thing seems to be based on what, to put it bluntly, is an absolutely batshit crazy notion of how Wikipedia operates, founded on the fundamental misconception that "the more dispute resolution is taking place regarding a topic, the healthier that topic is". &#8209; Iridescent 16:34, 6 January 2019 (UTC)
 * "Thank you" for linking to rope worms. I possibly did not need to know that. Oh the humanity! |p -- Elmidae (talk · contribs) 16:54, 7 January 2019 (UTC)


 * Looks like a solution in search of a problem. - Sitush (talk) 16:01, 6 January 2019 (UTC)
 * Not sure what this is meant to do, but it sure strikes me as a solution in search of a problem. Until we see a good definition of what "health of a talk page" means, I'm not seeing the need for this. Ealdgyth - Talk 16:27, 6 January 2019 (UTC)
 * No. Solution in search of a problem. Edaham's interpretation of page health is grossly wild and inaccurate. What Iri says. &#x222F; WBG converse 16:50, 6 January 2019 (UTC)
 * er, calm down? I was trying to help via some discussions I’d read on another wiki project. The idea would be to identify problematic areas of the encyclopedia and allow the community to give feedback without having to register complaints across pages. I’ve never made a proposal of this nature before, so please, try to assume good faith. I haven’t actually offered an “interpretation” of page health and deliberately left it open. The page you referenced was an example of a page one could reach via the template (It did actually say that at the top of the page, but I've since blanked it to avoid confusion), so I’m not sure what part of my suggestion could be termed, “grossly” or “wildly” inaccurate. . The idea would be that the resultant average would not be displayed, but be logged and available to people who want to know where problematic areas are and give an idea of health over time. “Mass downvotes” therefore, would be desirable from a point of view of being alerted to a a problematic area. It’s a feedback system. Many thanks for the comments though. Hope I didn’t take too much time out of your day. Edaham (talk) 00:57, 7 January 2019 (UTC)
 * Unlikely. This idea reminds me of two problematic ideas -- one being the "upvoting" and "downvoting" prevalent on American social media, and the other being the "social credit" system being pursued by the Chinese government.  Both of these things have the same problem, namely unreliable raters -- either an ignorant partisan rabble in the American case, or a sinister party elite AI in the case of the Chinese.  In Wikipedia's case, it is moderately conceivable that some effort could be made to try to enlist "neutral" editors to do rating; I've long favored a jury system for settling disputes.  But doing that without making it explicit that you're soliciting jurors and you want a fair decision and making the selection process both random and transparent and then targeting it all toward settling an issue rather than rating a page ... well, there are a lot of details I'd want there before this becomes that. Wnt (talk) 01:06, 7 January 2019 (UTC)
 * just a quick second comment to further clarify, firstly: results of voting needn’t be displayed. This is an opportunity for a user to rate an experience without having to have a discussion. We have lots of areas where people have to grind it out to be heard. We don’t have a system where people can easily and anonymously submit a piece of generic feedback. The data collected would provide a heat map of areas in which people had submitted this info, telling us about both level of interaction and satisfaction on a general scale.
 * secondly: I’m fully wp:MIAB compliant, so feel free to tell me if this is a hit or a miss. Be blunt. I don’t like being called batshit crazy though. Don’t do that if possible, cheers. Edaham (talk) 01:19, 7 January 2019 (UTC)
 * Well, the main problem with a 'heat map' is that the way I understand it, you're going to be looking for talk pages where people are furious at each other. If you find a talk page like that, everyone knows there's a dispute.  Some of them have been on lists of "Wikipedia's lamest edit wars" for a decade or more.  Probably the editors there want some kind of mediation by genuinely disinterested parties, but Wikipedia makes getting that extremely difficult.  Whenever a new editor joins in the fracas to try to impose fair order, they end up sucked into the contention.
 * Also, I am concerned that developing a tool to provide secret results to an elite of Wikipedians would further increase the inequality between editors and therefore contribute to the decline of the project as a whole. We have an unhealthy dynamic in society that computers -> ownership -> special privileges -> dictatorship and it can be argued that "the medium is the message" and that online distribution of content is simply doomed to fail altogether.  I don't know if any counteracting force can be devised, but in the meanwhile I am very wary of drawing new distinctions and privileges.
 * Finally, there's the aspect that quick ratings will inevitably be superficial. If an article about haplotypes is riddled with errors you might have to sit down for half an hour and review multiple papers to get an inkling of it.  If a woman in a painting is naked, a random reader might complain in seconds.  So I wouldn't want to take any results coming out of such a system very seriously. Wnt (talk) 01:59, 7 January 2019 (UTC)


 * Alt suggestion. We have lots of talkpages that few if any editors are looking at, I know this from the number of queries that I have scattered round the project. It would be good to have an AI or something that listed article talkpages with open queries by wikiproject or by time since query raised. Having lists available of such pages would be useful, need not be obtrusive, and if the query has been resolved by editing of the article without updating the talkpage it should be simple for anyone to add ✅ to the section.  Ϣere Spiel  Chequers  14:10, 7 January 2019 (UTC)
 * This can be done simply by reviewing e.g. Special:Recentchangeslinked/Template:WikiProject Video games. --Izno (talk) 16:09, 7 January 2019 (UTC)
 * That's a neat trick, I didn't know that, and I can see it does part of what I suggest. But only part, it risks being swamped by article assessment, tagging for other WikiProjects and other edits. I am sure it would work for the enthusiast who is here more than once a week, but I was thinking more of the person who pops by once a month, or the person exploring a long dormant Wikiproject. Being able to list talkpages with outstanding queries would be useful in such scenarios. Though I suppose you would need to be able to swerve some off your WikiProject and onto more relevant ones.  Ϣere Spiel  Chequers  21:32, 7 January 2019 (UTC)


 * No - We're here to improve and build upon our encyclopedia ... not flaff around dictating what talkpages are healthy and what ones aren't, Solution looking for a problem is what this is. – Davey 2010 Talk 21:25, 7 January 2019 (UTC)


 * This doesn't make any sense at all to me, as there is no definition of "health" and no guide to what the 1-5 scores actually mean, as the definition of "health" is apparently up to individuals to decide for themselves. It's trying to quantify something, but without an objective definition of what that something actually is, any score would be utterly meaningless. Also, the idea that rectifying "bad health" should be a job for admins suggests the proposer does not understand the role of admins. Boing! said Zebedee (talk) 14:45, 13 January 2019 (UTC)

Replies

 * As a proposal for a data gathering system this isn't a direct solution to a problem per se, but if it were framed that way you could consider it thusly:
 * In addition to community feedback being mostly discussion based and therefore difficult to assess and quantify, our current system of assessing feedback doesn't allow for feedback from people who don't want (or no longer want) to contribute to discussions. People can't just engage briefly and then tell us what they thought of that experience. This means we disproportionately hear from people who take the time to repeatedly voice their opinion. Essentially we have one thing. We do not have the other. I think we should have both.
 * Mass down voting, an absence of voting, an abundance of voting are all indicators of community behavior, which would be visible via this system. 100% Accurate voting by genuine editors is neither possible or desirable in such a system.
 * Assessment of the data collected would lead to insights on popularity, areas of conflict and ways of dealing with it, which we have not yet considered. Among these would be a time based approach to rating community health, which could give an indication of health over time - giving us insights on the effectiveness of other initiatives aimed at improving user experiences.
 * Therefore in a nutshell, the problem is that we don't have a means of collecting generic data regarding the health of community experiences, and I am proposing a means of collecting it
 * I don't want to sell this any more than I have, so I will end my proposal by saying that in the (seemingly likely) event that this proposal is rejected, that we should consider ways in which Wikipedians tell us about their experiences and consider whether or not our current methods unduly exclude those who have an opinion but do not have the inclination to openly share it on our discussion pages. Hopefully the consideration of this point will lead to improvements on the proposal, or yet better ideas. Sorry about all the bold text but I really wanted to make a couple of points stand out.

Edaham (talk) 02:11, 7 January 2019 (UTC)
 * If people are not willing openly to express their opinions then they have no particular right to a voice here. One of the key points of Wikipedia is collaboration, and secret voting is not the way to achieve that. Hence, just about the only things that are secret here are ArbCom voting and legally protected information (eg: checkuser).


 * Your proposal seems like an even more extreme version of the oft-derided "friendly space" in its attempt to mollycoddle people. Real life is tough, real life needs interaction (unless you're a hermit), and real life involves disagreements: you have to stand up to be counted. In any event, both the method and the underlying theory of this proposal are fatally flawed, as others have pointed out. - Sitush (talk) 13:34, 7 January 2019 (UTC)
 * arriving a bit late to the party aren’t we? Come to help clear away the styrofoam cups? Voting (for something) and collecting survey data aren’t the same thing. Not really connecting is it. Edaham (talk) 15:53, 7 January 2019 (UTC)
 * Do what? Did you see my comment above of several days ago? Not late to anything. I understand you may be pissed that your proposal is being shot down but there's no need for that. If you can't see the problems with your proposal now, you probably never will. However, I was responding to you clarification: letting people complain anonymously (and, believe me, that is what you are proposing) isn't helpful. If they have a problem and want it fixed then they need to engage: shit or get off the pot. - Sitush (talk) 16:09, 7 January 2019 (UTC)
 * Just wow. Nice take down! You won Wikipedia! Im not pissed at all. Incredulous is the word. Surveys aren’t unusual in large projects, where it’s easy to gather large amounts of data. Wikipedia doesn’t really have customers, so the concepts typical to customer satisfaction might be a bit alien. I get that. Do you have an alternative suggestion? Although I think the proposal and its ramifications have been misunderstood somewhat I can understand the concerns raised. I’ll have think about it and resubmit an idea when it’s brushed up a bit. Edaham (talk) 16:33, 7 January 2019 (UTC)
 * No alternative suggestion because, as I said at the outset, I think you're trying to find a solution to a problem that does not exist. Just because surveys can be done does not mean that they should be done. And if you hadn't got stroppy with me, I wouldn't have retorted in similar vein. - Sitush (talk) 16:46, 7 January 2019 (UTC)
 * I assumed that was friendly and cheeky banter. I didn’t feel like you were being stroppy. A very interesting word actually with a murky etymology. To say, in a “strop” further mangles it because it then shares a pronunciation with a word for a piece of sharpening leather, with an unrelated etymology to the original word, which is synonymous with irksome. Probably a discussion for elsewhere. The reason this particular survey ought to be done is because if such data were pouring in, reviewing its change over time could be used to gauge the effects of other initiatives. Working out whether or not something we put effort into had a desired effect is a job, which ought to be done because it will divert us from wasting effort in the future. If we reduce the purpose of the discussion to that salient point and build up from there we might come up with something better. I say we, because I’m an optimist at heart and believe that with a little more warming you’ll come around to the edaham camp eventually. Edaham (talk) 17:01, 7 January 2019 (UTC)
 * This is getting at a real problem (low-traffic talk pages), but since the beginning, we've been less about voting and more discussion and consensus. Good principle, bad execution. The best way to make inactive talk pages active is to post notices elsewhere about discussions that are active or things editors want to bring attention to. - PrussianOwl (talk) 23:08, 8 January 2019 (UTC)
 * probably due to the way I originally framed the idea, my fault, we are having a really really hard time getting past the idea of voting. This isn’t voting. People vote for an outcome, as in will we have custard or ice cream for desert. This isn’t voting. It’s not. It’s not voting. The intention of the idea is that we have other schemes to improve community health. We don’t actually gauge (except by looking and judging) if they are having a positive impact. (Or do we?) If people are able to contribute marketing data at a roughly constant rate, we can measure that rate to see if our initiatives had impact. We’d be looking to find correlation between the data we obtain, and the things we are doing to improve the place. There’s lots of ways of doing this and the thing I’ve suggested is rudimentary and roughly sketched to the point that it has scuppered the idea apparently.


 * I mean you could probably just find correlation between community health initiatives and the frequency of the use of the “retire” template and the use of obscenities on talk pages, so this certainly isn’t the only way of handling things. People already contribute lots of data which reveals their general satisfaction, via their lexical input and the parsing thereof.


 * Also, on a side note, I let a friend of mine look at my comments and replies, which I made in a lighthearted and humorous spirit, and they said that given the nature of the conversation I’m probably coming off as grumpy and flippant. Sorry if that’s the case. Believe me I’m very happy to have the opportunity to contribute ideas in this forum! Edaham (talk) 02:40, 9 January 2019 (UTC)

Divide Village pump tabs to create a separate "history" component
Divide "Village pump" tabs into "Policy/Policy history", "Technical/Technical history", "Proposals/Proposals history", "Idea lab/Idea lab history", "Miscellaneous/Miscellaneous history". This would save a "click" when reviewing the various subdivisions of the Village pump. There would be no need to repeat the terms as I am doing now for illustration purposes only. And in fact the terms could be stacked vertically to save space, with the name "history" below the name of the tab. Bus stop (talk) 15:20, 14 January 2019 (UTC)
 * This would save a click for what? What are you trying to access? --Izno (talk) 17:54, 14 January 2019 (UTC)
 * "What are you trying to access?" I would be trying to access the history of a given subdivision of the Village pump. Let us say I was interested in developments at the Policy subdivision, the Proposals subdivision, and the Miscellaneous subdivision. Rather than click on Policy and then history, I would simply click on "Policy-history", saving a click. Bus stop (talk) 18:15, 14 January 2019 (UTC)
 * This is silly. Personalize your own view or enable popups so you can hover over the names at the top and access the history without navigating to another page. Killiondude (talk) 19:05, 14 January 2019 (UTC)
 * Thank you, . I enabled popups. That is cool. I was not aware of that. Bus stop (talk) 19:18, 14 January 2019 (UTC)
 * Followup. I turned it off. It is annoying. Bus stop (talk) 21:18, 14 January 2019 (UTC)

Rollback feature
My proposal is, after rolling back a user's edit, automatically open their talkpage. I know there is WP:Twinkle but that is not automatically work/open talk page. There are no features in preferences. If there are any Java scripts or features, then it will be very help for rollbackers. Thanks, Siddiqsazzad001     09:00, 14 January 2019 (UTC)


 * ✅ Script made. After rolling back a user's edit, open their talk page. Doesn't work if you have a script installed to require confirmation before rolling back. See User:DannyS712/Rollback talk --DannyS712 (talk) 09:27, 14 January 2019 (UTC)


 * Thanks dude! It's working. I am the first user who used this script. :) Siddiqsazzad001     14:58, 14 January 2019 (UTC)
 * Should I give you an award? :P ― Abelmoschus Esculentus  ( talk •  contribs ) 15:03, 14 January 2019 (UTC)
 * Me? or Siddiqsazzad001? idk... --DannyS712 (talk) 16:54, 14 January 2019 (UTC)
 * Nah just joking with Siddiqsazzad :) ― Abelmoschus Esculentus  ( talk •  contribs ) 23:12, 14 January 2019 (UTC)
 * Absolutely. They deserve an award for having such a great user script idea... --DannyS712 (talk) 23:54, 14 January 2019 (UTC)

Introduction of page deletion right
Hello, Following a recent discussion with other editors off-wiki,I would like to suggest a page deletion right that would allow trusted non-admins (or maybe extended-confirmed users) to delete pages that have been created by users with less than 100 edits and 14 days as long as the article is less than 10 days old and has not been editied by a few users above that limit to allow for the quicker handling of blatant speedy deletion candidates.

Thanks, RhinosF1 (talk) 17:15, 22 January 2019 (UTC)
 * If a non-admin is "trusted" enough to delete pages, they might as well run for RFA. A userright of the sort you're describing would be needless duplication of that, but without the rest of the toolset to deal with blocking and/or protection that is usually needed in these kind of situations. -- Tavix ( talk ) 17:21, 22 January 2019 (UTC)
 * I understand your concern, while we wouldn't be able to block etc. and this would apply in cases where 90% a block would be needed, it would save up a large amount of admin time.
 * On point 2 - A user may not feel ready for RfA but be confident in what constitutes a G11 or U5 - that is why a limit on the articles that would be eligible was also suggested
 * RhinosF1 (talk) 17:27, 22 January 2019 (UTC)
 * If they feel confident in that knowledge, they are allowed to tag an article G11 or U5. An admin will be along shortly to delete it.  -- Jayron 32 17:27, 22 January 2019 (UTC)
 * What is the evidence that existing admins are not deleting these articles in sufficient time? Are they sitting around for days or weeks not being acted on?  What of the existing workload necessitates the extra help?  What is your data showing that?  -- Jayron 32 17:27, 22 January 2019 (UTC)
 * It can take a hour or so for a Blantantly violation to be deleted - the chance that user will edit again is minimal so a block could be done in a few days time. RhinosF1 (talk) 17:32, 22 January 2019 (UTC)
 * And your point is? An hour is hardly an issue.  And I don't know on what basis you'd think that the editor wouldn't edit again.  Risker (talk) 17:45, 22 January 2019 (UTC)


 * This is a WP:PERENNIAL suggestion. --Izno (talk) 17:28, 22 January 2019 (UTC)
 * What problem is this meant to address? As noted above, if users are that trusted, they should be admins. 331dot (talk) 17:32, 22 January 2019 (UTC)
 * As with my self my CSD log shows that I could be trusted in deletion under CSD criteria but I wouldn't run for admin yet. RhinosF1 (talk) 17:34, 22 January 2019 (UTC)
 * It's your choice to not go into an RfA, but that doesn't mean we should open up this can of worms. I see no serious issue with backlogs of CSD's. Were any admins involved in this off-wiki discussion? For that matter why was it off-wiki? 331dot (talk) 17:37, 22 January 2019 (UTC)
 * It was on one of the IRC Channels and I haven't gone into an RfA because I don't think I'd be approved its WP:TOOSOON. RhinosF1 (talk) 17:46, 22 January 2019 (UTC)
 * As I said, that's your choice. If you are as trusted as you claim, an RfA should be a shoo-in.  I don't think we should be creating additional levels of users as sort of "pseudo-admins" just because people haven't yet qualified as actual admins. Oppose. 331dot (talk) 17:49, 22 January 2019 (UTC)
 * Do you genuinely think I would have a chance of passing an RfA. RhinosF1 (talk) 18:29, 22 January 2019 (UTC)

Is there an evident need for this right? To me, it just seems like an unnecessary hat that hat collectors might desire for. Atcovi (Talk - Contribs) 17:40, 22 January 2019 (UTC)
 * Oppose there's no chronic CSD backlog, and nobody should be unilaterally deleting pages except in the most blatant circumstances (such as WP:G10). power~enwiki ( π, ν ) 17:42, 22 January 2019 (UTC)
 * No evidence is given that there is ever any serious backlog at CSD - as someone who regularly stops by there, it is more likely that most categories will be empty than that there will be a backlog that takes more than half an hour's work to clear. I do pretty strongly believe that deletion is one of the few administrative tools that genuinely speaks to the need for an RFA. I think it might be easier to pass an RFA today than it was 3 or more years ago, and might even be easier than when I passed almost 11 years ago. Risker (talk) 17:48, 22 January 2019 (UTC)
 * Yes, this is probably the easiest time to pass an RfA since I've been active again. TonyBallioni (talk) 17:51, 22 January 2019 (UTC)
 * Oppose per the standard "The WMF will not grant the ability to view deleted content without an RfA equivalent process, and if you can't see deleted content the ability to delete is somewhat useless on its own." also, for all the reasons above. TonyBallioni (talk) 17:49, 22 January 2019 (UTC)
 * Oppose - This is a solution looking for a problem - Admins aren't expected to be on 24/7 365 days a year, Please remember like us admins too are volunteers, Anyway as Tarvix notes if you want to delete pages then run for RFA. – Davey 2010 Talk 17:57, 22 January 2019 (UTC)
 * You said you discussed this on IRC. If there's an emergency necessitating page deletion, ping an admin on IRC. Natureium (talk) 17:59, 22 January 2019 (UTC)
 * Or failing that go to https://en.wikipedia.org/wiki/Special:Log?type=delete&user=&page=&wpdate=&tagfilter=&subtype= and it will show the last/newest deletion (meaning the last admin who was on) :). – Davey 2010 Talk 18:25, 22 January 2019 (UTC)
 * also this tool. — xaosflux  Talk 18:31, 22 January 2019 (UTC)
 * Thanks for the information. RhinosF1 (talk) 18:28, 22 January 2019 (UTC)

Based on the discussion so far, I am withdrawing the proposal per WP:SNOW. RhinosF1 (talk) 18:13, 22 January 2019 (UTC)


 * I'd like to leave a comment here that I started a discussion to list "spinning out the core admin toolkit" at WP:PEREN. Please take a moment to review and/or help with the homework to add it to the page. --Izno (talk) 20:49, 22 January 2019 (UTC)

Display a link to WikiProject/topic specific guidelines when editing an article?
Often first-time editors have trouble knowing the guidelines behind the specific subject they are editing. For example an inexperienced user may not know the general guidelines behind WikiProject Schools (usually don't list administrators below senior level, and don't include the text/lyrics of the school/fight song), and so he or she may do a faux pas. I suggest finding a way to display a convenient link to the topic-specific guidelines for a particular article when any user edits the page. So if Johnny edits an article about anime, he sees a link to the guidelines. Or when Susie edits about her high school, she sees a link to its topic-specific guidelines. It may also help for each sett of guidelines to have an "in a nutshell" before the nitty gritty details. WhisperToMe (talk) 03:46, 8 January 2019 (UTC)
 * I think Editnotice already does that. It can display links and short note as you're suggesting and is active atop editing pane on any page where it's activated. –Ammarpad (talk) 06:19, 8 January 2019 (UTC)
 * If there's a way to automatically append an editnotice for any page tagged with a certain WikiProject tag (so instead of having to manually add an edit-notice to every relevant page, it gets automatically added), that would be great. WhisperToMe (talk) 10:22, 8 January 2019 (UTC)
 * This is done for BLPs and disambiguation pages through MediaWiki:Common.js; you'd need a consensus that a particular category of articles should display a notice. Galobtter (pingó mió) 13:56, 9 January 2019 (UTC)
 * Thanks for the tip! I went ahead and notified the Schools WikiProject: Wikipedia talk:WikiProject Schools WhisperToMe (talk) 12:54, 10 January 2019 (UTC)
 * Also notified Anime and manga, China, and Japan WhisperToMe (talk) 05:57, 11 January 2019 (UTC)


 * There are few issues here which you may not be aware of, this is not as easy as it looks. To my knowledge only BLPs and Disambiguation pages have such notice injection via Common.js, and they're the exception rather than the norm. First of all, for that to be implemented to set pages, they need to have a master category where all members are directly in irrespective of any other categorization: See how Category:Living people and Category:Disambiguation pages are. This currently does not exist for schools. Category:Schools holds subcategories not the articles themselves. You need to have consensus to change that first. Second, editnotice of pages in Category:Living people is showing a core policy while that of Category:Disambiguation pages is showing a disambiguation guideline with wide acceptance, both are not WikiProject notices, you need to make a strong case why a single WikiProject should've this and what if other WikiProjects come forward requesting same. This is assuming you surmounted the first problem about  Category:Schools. –Ammarpad (talk) 07:03, 14 January 2019 (UTC)
 * Thanks for notifying me of the programming issues. I wonder which Wikipedians have the most experience with this sort of thing.
 * I feel WP:Schools needs this because the projects editors have agreed on various content guidelines (such as in Wikipedia_talk:WikiProject_Schools, which was done because people keep adding long lists of school administrators to articles) that are intended for all articles in the project scope and enforced by project members, but without a notice displaying on the editing screen, drive-by editors and first-time editors won't know about any of these: they only see the common notice displayed at the bottom. Then they might be surprised or upset when their changes are reverted. They may not even be individually notified on their talk pages; while there might be a revert that does state who made the change, they may not be aware of the commenting system (using four tildes), and they may not understand how to approach the other editor. They won't know about the project guidelines as they may not even know what a WikiProject is. Telling the user this information in personalized talk page messages is the only way in which they can be expected to learn about it. It's important to consider the position of a person highly inexperienced with Wikipedia.
 * Project members themselves may dislike making multiple reverts of low-quality content, with low-quality partly due to falling afoul of agreed guidelines. While notices will not stop determined vandals, cutting down on low-quality edits would lessen administrator workload and project user workload. Freeing up administration means there's more time to do content creation; I had proposed to the others checking school attendance boundaries and matching communities (cities/towns/neighborhoods) with schools, but another editor gently reminded me that most of them were focused on administration stuff and that I would likely be alone in this task.
 * WhisperToMe (talk) 07:13, 14 January 2019 (UTC)
 * OK, the proposal can go ahead here on VPR or on that talkpage, since the issues to discuss are now clear.–Ammarpad (talk) 07:59, 15 January 2019 (UTC)

Convert infobox comedian to wrapper
See Template talk:Infobox comedian. Comments invited. Thanks Capankajsmilyo(Talk 02:51, 16 January 2019 (UTC)

about non-free files
Non-free files today will eventually enter public domain. When that day comes, they are supposed to be transferred to Commons. I propose that Wikipedia should set up a standard procedure for such files, and there should be a few tweaks to current procedures to help this process in the future. Here is a list according to my perceived priority:
 * 1) User:Theo's Little Bot reduces size for non-free files, but currently there is nothing in place to track whether an image is shrinked, other than the file histories. I suggest:
 * 2) When Bot reduces a file, insert a short note in EXIF, saying something like image shrinked by bot. I think this is the best solution such that reduced images are earmarked. Should they be transferred to Commons, another bot, commonshelper, or a built-in MediaWiki functionality, could be developed to identify or block them based on EXIF. This measure should be adopted by all image-shrinking bots across all wikis.
 * 3) If 1.1 is not possible, alternatively, include all bot-reduced images in a tracking category.
 * 4) Before transferring to Commons, the original high-res files should be restored and reverted to. This could be done by a bot with admin rights. Say design a Template:Restore for transfer. A trusted user (autopatrollers?) tagging a file with this will let a bot restore all revisions and revert to the first version, which should be the best for most files. (A non-trusted user's tagging would be ignored, or reverted by the bot.) A note should be put up nonetheless, to remind users of picking the best for transfer.
 * 5) There could be something to track when and where a file was made. An anonymous photo taken and published in USA in 1930 would probably enter PD in 2026. This something can help the transfer process by then.--Roy17 (talk) 01:01, 10 January 2019 (UTC)


 * Keep in mind that most editors that upload non-free already start with reduced image, there is no "old" version at the original resolution to go back to. Additionally, remember that commons wants works that are PD everywhere, and that requires a bit more knowledge about the origin of a work than our current systems allows. I'm all for some bot to tag potential non-free into a human-reviewed list as "Possibly now PD" and have humans do that work after checking things, but definitely not a bot do all the work. --M asem (t) 01:11, 10 January 2019 (UTC)
 * Also on your point 1, the file history will show the bot reduction. We don't need to add anything to an EXIF (and not all files will have an EXIF). --M asem (t) 01:11, 10 January 2019 (UTC)
 * I am aware of that. Still we could do the little thing to foolproof any bot-reduced images ending up on Commons. If a reduced image were transferred and an enwp admin deleted the local page, almost no one from commons could verify whether the file had been reduced. I have seen many cases of users transferring files (early wiki uploads, textlogos etc.) by downloading a scaled down preview from local wikis and uploading on Commons manually, such that local admins have to do the proper transfer again before deletion. This will certainly happen with bot-reduced non-free files. I believe it is best to mark the reduced images themselves, whether in EXIF for jpg and tif, or as some other forms of embedded codes, or a watermark. The marking must be machine readable. This lets Commons reject files straight. A template message could also be added to current local file pages to warn of reduced images. The more precautions taken, the less likely we make mistakes.
 * Many images would stay on local wikis for a long time until they enter PD. External sources often become 404 not found in the wait. The best version is of course an external original, in case the wiki one had been edited. But if the wiki one were the one to be transferred, the largest is the best.
 * I did not suggest a fully automated restore and transfer. The bot only does the restore part. A file could well be fair use for 150 years before entering PD. (Say a 20yo photographer takes the only image of a deceased person and lives to 100, and the rule of life+70 applies.) The original year does not really imply the actual PD date, but such extreme cases are not common. Many files should enter PD the latest 120–150 years after creation. Wiki editors in 2020s and 2030s will soon have to handle files from 1920s and 1930s. It will become a regular maintenance task in future. Some sort of preemptive cataloguing should be beneficial.
 * I believe this is something that should be implemented across all wikis, but I post here because enwp is the most active and attended by most tech-savvy users.--Roy17 (talk) 04:02, 10 January 2019 (UTC)
 * To determine copyright status of a file, the following parameters are the most essential: authorship/copyright claimant, year created, year published, and countries of origin. Here is my invention on yuewp, tweaking information and creating two templates, that categorise some uploads into cat:files created in YYYY or before: yue:special:diff/1246619, yue:t:before and yue:t:between.--Roy17 (talk) 04:19, 10 January 2019 (UTC)


 * I don't think a bot should mess with the files themselves other than reducing their size but what harm would there be in having Category:Non-free files that were reduced by a bot or similar? Additionally/alternatively, I think it would be good if the bot that resized the image added a template that says "This file was automatically resized by a bot and previous versions deleted per F5. If you believe the resize was in error, you can request refund..." or something like this. Then you could track these files through the template's transclusions. Regards So  Why  11:36, 10 January 2019 (UTC)


 * Template:Do not move to Commons already includes a field for expiry, which then adds the file to Category:Media now suitable for Commons. Problem is, not that many people seem to use it. Having a bot that undeletes original higher resolution files for transfer seems fine, so long as the bot also immediately PRODS the file, meaning if the file is not transferred in seven days, and the PROD replaced with Template:Now Commons, then the old revision should be automatically re-deleted. It also should merely restore the previous version, not revert to it, so that in the meanwhile we are still using the low-resolution version under fair use in our articles. The reversion should need to be done by a human prior to transfer. Also, the only user group we have that is specifically related to competency with files is file mover. So that's the only group where it would make sense to have an undelete-by-proxy option.  G M G  talk  12:00, 10 January 2019 (UTC)
 * Very few of these non-free files are about to have copyright expiring soon. Also it is not Wikipedia's job to archive these files. Instead we should explore other archives that will have stored the files (legally), and be ready to copy those copies once it is copyright expired. Also the bot will not know why a previous file was not used. There may be errors, or other quality issues. So manual intervention would be needed. For non-free files often there is not eough information to determine copyright expiry either, as original photographer and country are often missing information. Graeme Bartlett (talk) 02:58, 11 January 2019 (UTC)
 * I certainly agree with #1 (easy tracking), but not with the rest. Keep in mind that deciding when an image becomes PD can be complicated some times. In stead, allow users who believe that a specific image is already in the PD, or will be there within a month (or perhaps a shorter period), make a request about that individual image. עוד מישהו Od Mishehu 13:11, 13 January 2019 (UTC)
 * Following the new development of FileImporter, we are now able to transfer all undeleted revisions to commons directly. The part of reverting to the original can be dropped, because this can be done on Commons after successful transfer.--Roy17 (talk) 17:21, 16 January 2019 (UTC)

All user pages are automatically protected to the associated user's access level
I'm proposing that all user pages on Wikipedia will be automatically protected to the user acess levels of their associated users. For example, an IP or new user's will be pending changes protected, mine will be extended-confirmed protected, and so on. The reason I think this should be done is because they are very sensitive to vandalism (basically as much as biographies of living people), there is rarely any reason for anyone except for the users themselves to edit their pages (other than maintenance such as updating deprecated templates, which mostly adminstrators and such will do anyway), and no one wants to go their own page to see that all of its content has been replaced with "This user is bad don't listen to them" by an IP-vandal. (Note that this was only an idea I had; not sure if it can actually work with the current software.) Geolodus (talk) 10:05, 12 January 2019 (UTC)
 * After reading the replies, I've changed my view and now consider this a bad idea. Feel free to close/archive this discussion as rejected, or whatever. Geolodus (talk) 15:03, 17 January 2019 (UTC)
 * Why? This is still the encyclopedia that anyone can edit, and there is no evidence that they are very sensitive to vandalism (basically as much as biographies of living people). Besides, the Recent Changes page for new user Userpage edits mostly consists of OK edits. Jo-Jo Eumerus (talk, contributions) 10:42, 12 January 2019 (UTC)


 * Oppose, you do not WP:OWN your userpage. Also, any vandalism to user pages is not directed at articles. I much prefer having graffiti on my userpage to something really bad like changing numbers in articles. —Kusma (t·c) 11:01, 12 January 2019 (UTC)
 * Oppose. IP editors cannot currently edit user pages, which I think is probably the main concern here (data: filter 803). In fact useful edits can often be made to user pages. Also, allowing only admins to edit admin user pages seems to me like a terrible idea. -- zzuuzz (talk) 15:10, 12 January 2019 (UTC)
 * Further to that, an admin whose user page gets vandalized frequently has the power to protect their own page, so it does not need to be automatic. bd2412  T 15:37, 15 January 2019 (UTC)
 * Oppose Userpage vandalism is uncommon and easily dealt with. New and unregistered users can't even edit other people's userpages anyway, and I don't think we need any more restrictions. funplussmart (talk) 20:27, 12 January 2019 (UTC)
 * Oppose...If I've read this right, wouldn't that mean only admins being able to edit admin pages?! Although it would quiten down the noise from the WP:Founder's page a whole lot :D  ——  SerialNumber  54129  20:38, 12 January 2019 (UTC)
 * And of course Our Beloved Founder (BBHB) could have protected his user page already if he wanted to. --Guy Macon (talk) 16:30, 13 January 2019 (UTC)


 * Oppose, unless you can show that there is a current, major problem here. We do have an edit filter to prevent anons or new users from editing other users' user pages; we probably don't need any more than that. עוד מישהו Od Mishehu 13:06, 13 January 2019 (UTC)
 * Oppose Wikipedia is built around the principle that anyone can edit it. However, in some particular circumstances ex. vandalism, we can request at WP:RFPP.  Please see this WP:PPDRV.  Siddiqsazzad001     05:06, 14 January 2019 (UTC)
 * Oppose Per WP:PREEMPTIVE, Applying page protection in a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed if applied for these reasons. ― Abelmoschus Esculentus  ( talk •  contribs ) 05:18, 14 January 2019 (UTC)

Bot for outreachdashboard.wmflabs.org
Please see a proposal discussion at Wikipedia talk:Requests for permissions regarding adding a service account for the outreach dashboard account creation workflow. Thank you, — xaosflux  Talk 15:20, 17 January 2019 (UTC)

Use ReCaptcha 2.0 for Wikipedia
Recaptcha 2.0 allows a one-click verification that will speed up editing and publishing. Look into it at []. Thank you. --Whatever Floats your Zel! (talk) 18:47, 17 January 2019 (UTC)
 * See Perennial proposals for why this has been rejected in the past. --DannyS712 (talk) 18:55, 17 January 2019 (UTC)
 * Gotcha, makes sense. --Whatever Floats your Zel! (talk) 19:10, 17 January 2019 (UTC)

RfC: Expanding G13
Proposal: Should G13 be expanded to include stale userspace drafts with Userspace draft? --DannyS712 (talk) 02:07, 23 January 2019 (UTC)

Currently, WP:G13 applies to:

Any pages that have not been edited by a human in six months found in:
 * 1) Draft namespace,
 * 2) Userspace with an AFC submission template
 * 3) Userspace with no content except the article wizard placeholder text.

This proposal would expand the second part of G13, resulting in:

Any pages that have not been edited by a human in six months found in:
 * 1) Draft namespace,
 * 2) Userspace with an AFC submission or Userspace draft template
 * 3) Userspace with no content except the article wizard placeholder text.

--DannyS712 (talk) 02:08, 23 January 2019 (UTC)

Withdrawn given the very clear lack of support for this proposal, I am withdrawing this RfC. Thanks, --DannyS712 (talk) 16:38, 24 January 2019 (UTC)

Survey
Please cast your !votes as Yes (or Support) or No (or Oppose), optionally with a one-sentence explanation. Please do not engage in back-and-forth discussion, which should be in the Threaded Discussion. (Back-and-forth in the Survey makes it more difficult for the closer.)
 * Support as proposer --DannyS712 (talk) 03:03, 24 January 2019 (UTC)
 * Support for indef blocked users and those who have left Wikipedia or retired from it, Oppose for actively editing users. << FR (mobileUndo) 03:06, 23 January 2019 (UTC)
 * Oppose, there at the very least needs to be a one week notice. Preferably a month long notice. I don't want something in my userspace deleted out of nowhere simply because I forgot it was there. Headbomb {t · c · p · b} 05:42, 24 January 2019 (UTC)
 * Oppose. When users put Userspace draft on their drafts they did so in the understanding the draft would not be deleted after six months. If rules are to be changed, then create a new userspace draft template, and clearly give that a six month time limit rule so everyone understands what is happening, and can elect themselves to use that template if they wish. There are some users, User:Giano for example, who create valuable articles in their user space, some of which may languish for years without attention. I would hate for Giano's userspace articles to be deleted merely because he has chosen not to touch them for over six months. SilkTork (talk) 09:40, 24 January 2019 (UTC)
 * Strongly Oppose" I have dozens of half finished articles in user space, representing hundreds of hours of work and research. I have often taken over two years to finish a page and put it in main space. This is a ridiculous suggestion. Giano    (talk) 09:53, 24 January 2019 (UTC)
 * Oppose This will achieve nothing but the loss of potential articles. Graeme Bartlett (talk) 10:53, 24 January 2019 (UTC)
 * Oppose as unhelpful, unless the intention is to lose articles and writers in approximately equal measure. ——  SerialNumber  54129  11:18, 24 January 2019 (UTC)
 * Oppose per SilkTork. Would create more trouble. ― Abelmoschus Esculentus  ( talk •  contribs ) 11:35, 24 January 2019 (UTC)
 * Oppose per most above. I, too, have a number of (very old) drafts in my userspace and I would loathe for someone to delete them just because I didn't touch them. WP:U5 already exists to handle those drafts created just to be hosted in userspace indefinitely and should be sufficient for any actual abuse of userspace for hosting purposes. Regards So  Why  11:53, 24 January 2019 (UTC)
 * Oppose We should only delete pages that are unsatisfactory (in any name space) and the procedures in WP:UP are suitable as they stand with no benefit in trying to guess what are the user's future intentions. Thincat (talk) 12:05, 24 January 2019 (UTC)
 * Oppose. Blank them instead, with Inactive userpage blanked. We did G13 because of the vast number of AfC drafts made by IPs. —SmokeyJoe (talk) 12:07, 24 January 2019 (UTC)
 * Oppose per BARF, an article I started in my userspace in 2010, returned to in 2016 and which is now in article space. I see no benefit and plenty of annoyance to deleting these drafts in the userspaces of active editors.  Someone coming and managing my userspace for me will likely just leave me entirely lacking in gruntle.  EdChem (talk) 12:46, 24 January 2019 (UTC)
 * Oppose. Keeping AfC from getting cluttered is one matter, deleting pages from other editors' userspace without a discussion is quite another. Give editors a place to work on articles slowly. Novusuna talk 12:55, 24 January 2019 (UTC)
 * Weak Support The proposal makes sense, but I understand that we can lose potential articles from this. That is why it is important for any draft (not just userspace drafts) to be reviewed before deletion, and why we have templates such as promising draft funplussmart (talk) 13:00, 24 January 2019 (UTC)
 * Oppose - It made sense to have a time limit for drafts that have been submitted to the AfC process... but there is no need for a time limit for those NOT submitted for review (as there is no “process” to end). Blueboar (talk) 13:11, 24 January 2019 (UTC)
 * Oppose. (A) This should be at WT:CSD, the accepted forum for speedy deletion criteria. (B) What problem does this solve? (C) Please leave other people's userspace alone unless you have a very good reason not to. —Kusma (t·c) 13:25, 24 January 2019 (UTC)
 * Oppose. This encyclopedia has no deadline. We rely heavily for our content on established users creating and improving articles in their own userspace. I do not believe that we benefit by setting limits on the speed at which these users work. --RexxS (talk) 14:18, 24 January 2019 (UTC)
 * Oppose - There is no need to delete pages that could possibly become articles, especially with the help of other users who may desire to claim, or build upon, stale drafts. Most very bad userspace drafts can already be discussed at WP:MFD or are eligible for speedy deletion under another criterion. ComplexRational (talk) 16:17, 24 January 2019 (UTC)

Threaded Discussion

 * Could we just clarify that Userspace draft (which currently has about 40,000 transclusions) is not exclusively placed on a draft by its author, and that in fact it is often put on drafts by editors who are systematically going through user pages? This means that the proposed G13 extension has the potential to affect virtually all drafts in userspace. – Uanfala (talk) 02:32, 23 January 2019 (UTC)
 * I think it should apply to such cases, because if a userspace draft is so stale that it was first dagged with Userspace draft, and then another 6 months have passed without it being edited, its unlikely to be improved in the future. --DannyS712 (talk) 03:06, 23 January 2019 (UTC)
 * Put another way, you want to 1) Reduce the time for a page to enter Category:Stale userspace drafts from 12 months to 6 months; and 2) make pages in Category:Stale userspace drafts eligible for G13? Thus eliminating the category entirely (or rather, making it a db category). ~  Amory  (u • t • c) 16:14, 23 January 2019 (UTC)
 * Sorry if I'm missing something, but what's the point of speedy deleting userspace drafts? What is the ultimate problem that this is trying to solve? – Uanfala (talk) 23:07, 23 January 2019 (UTC)
 * For the same reason that other CSD exist - not needing to go through the long deletion process for a clear delete decision. Wikipedia talk:Criteria for speedy deletion/Archive 65 explained that stale drafts in draft space shouldn't require having an AfC tag to be deleted, and this would partially extend that to userspace drafts. Again, WP:REFUND would apply. --DannyS712 (talk) 00:25, 24 January 2019 (UTC)
 * , I think is more asking - why do these drafts need to be deleted just for being old (through any process)? Galobtter (pingó mió) 12:15, 24 January 2019 (UTC)
 * There is a significant difference between userspace drafts marked with an AfC tag, and those that are not. Those that are tagged have been submitted to the community for a review process.  It makes sense to have an end date for that process.  Userspace drafts that are NOT marked with an AfC tag, however, have NOT been submitted to the community for review.  Such material is not part of ANY process that needs ending.  It does the project no harm to simply ignore such material... unless it contains stuff that should be deleted outright (attack pages, promotional material, etc.) Blueboar (talk) 12:53, 24 January 2019 (UTC)
 * Just trying to think outside the box here... Would it help if we stopped referring to non-AfC material in userspace by the word “draft”? What if we called this material: “user’s notes and ideas” (or something like that)?  A change in terminology might clarify the status of the material in question, and thus what needs a time limit and what does not. Blueboar (talk) 13:57, 24 January 2019 (UTC)
 * In general, that would be more accurate, but for pages explicitly marked as "drafts" I think the word draft is appropriate. --DannyS712 (talk) 16:06, 24 January 2019 (UTC)


 * Speedy deletions are designed to bypass the normal deletion process as a convenience in uncontroversial circumstances. However, examples can be provided of editors such as sometimes taking years to work on articles that they create, and that demonstrates that you can't set an uncontroversial criterion for deleting userspace pages.  Of course, there are many abandoned userspace pages, but you won't find a reliable way of identifying those that can be deleted uncontroversially. The normal deletion processes are perfectly adequate for dealing with suspected abandoned userspace pages, and that should provide a sufficient safety net for avoiding deletion of pages which are still being worked upon, no matter how slowly. --RexxS (talk) 14:33, 24 January 2019 (UTC)
 * Agree that the regular deletion process can be used... but the more fundamental question is this: Why do we even want to delete these “abandoned” userspace pages in the first place? Is there any benefit to doing so? Is there a downside to simply ignoring them? Blueboar (talk) 14:58, 24 January 2019 (UTC)


 * Rather than just considering the age of the draft, what about taking into account the activity of the user. I see a lot of things created by a user that made a few edits and then disappeared. I agree with the Opposes above that there is no reason to delete anything in user space as someone may be working on it very slowly. But if the user has not made any edit to anything in a long period - say 5 years, then they probably aren't coming back. This would cleanup some dead stuff that does keep getting updated by bots for various things. MB 16:06, 24 January 2019 (UTC)
 * Huh? Why are there any bots getting involved here? I can understand why bots might be tracking AfC submissions, but why would a bot be looking at material that has NOT been submitted to AfC? Again... I don’t understand the rational behind any of this. Blueboar (talk) 16:44, 24 January 2019 (UTC)


 * Given this feedback, I have withdrawn my proposal. --DannyS712 (talk) 16:38, 24 January 2019 (UTC)

Auto-archive old IP warnings
Previous discussion at Bot requests/Archive 78

I imagine it's fairly confusing for IP users to have to scroll through lots of old warnings from previous users of their IP before getting to their actual message. We have Old IP warnings top (or wan or ow, but that can be bikeshedded about later), but it's rarely used—thoughts a bot to automatically apply it to everything more than a yearish ago? Gaelan 💬✏️ 19:49, 11 January 2019 (UTC)
 * Support I don't think IP warnings need to stay up more than a few months. In my experience, vandalism from IPs comes in bursts that rarely last more than two days (probably because of blocking).
 * I think this is a good idea. No opinion of length of time I thought a year was too short but who knows. Technically it would work like an archive bot but instead of archiving to a sub-page, it would archive to within the top/bottom portion of . It would look at the most recent post within a section to find the date, and if that section leads off with a warning. There are ways for things to not go right like if a warning is not within a section and has followup posts etc, so this would not be a perfect solution more of a best-effort, if it can't understand the formatting it leaves alone. --  Green  C  20:09, 11 January 2019 (UTC)
 * I don't think its a great idea to send a bot around to chase all these. However, I'm assuming most of these warning etc are coming from tools like Huggle/Twinkle/etc - if so, approving a general concept that "archiving old (time to be determined) IP talk warnings to history" is allowed - these tool systems could add that functionality to their warning routines. —  xaosflux  Talk 20:21, 11 January 2019 (UTC)
 * Support - Having looked at this for a few examples I'm surprised to see a lot dating back to 2006 ..., I personally would say warnings should be archived after a year and a half from when they were left, 2-3 years seems too excessive and just a year seems too short, – Davey 2010 Talk 20:24, 11 January 2019 (UTC)
 * I imagine most IPs people edit with are dynamic ones that don't last all that long, but I have no idea. Gaelan 💬✏️ 20:50, 11 January 2019 (UTC)


 * There's some previous discussion here here here and here, and in fact several other places which people should probably look at before anything. There's been more than one bot (and editors like BD2412) already doing this at various times. As with anything there's going to be some complicating factors: if it's anything recent the IP should probably not be actively or recently blocked, range blocked, or globally blocked. The bot probably shouldn't archive or blank sockpuppetry tags, whois tags and shared IP templates, and probably shouldn't blank spam-related backlinks, some custom notices, and intelligible non-warnings, IMO. I don't think the question is whether it should be done, as it's something that's been done for a long time, but the bike-shed details which were avoided in the proposal. And of course who is going to write and run the bot. Personally I think as a general rule a year is probably too short. (should probably also ping Dirk and Petrb) . -- zzuuzz (talk) 21:43, 11 January 2019 (UTC)
 * Support. I have previously requested a bot for this and the conversation died out with no one taking it up. As with others in this discussion, I would propose very specific limitations, those being that all discussions older than five years be removed from the page so long as the IP has not been the subject of a block within the past two years. Personally, I have been blanking tags if the page is pre-2010s, because IP addresses can be reassigned in that length of time - and even if they are not, Wikipedia is not a permanent directory of IP addresses. bd2412  T 22:15, 11 January 2019 (UTC)
 * Comment the more complicated the policy, the more time consuming becomes writing and running the bot, the less chance anyone will take up the project, the greater the chance it never happens. --  Green  C  22:39, 11 January 2019 (UTC)
 * Well then let's start with something easy, that everyone can agree on, like ten-year-old warnings. bd2412  T 04:38, 12 January 2019 (UTC)
 * That's how you do it. Start with something conservative and uncontroversial. Proof of concept for everyone to see. Once the bot is approved and running, taking it to the next step is considerably easier. Trying to build a complete castle from day 1 is probably an over-reach technically and with the community. -- Green  C  00:41, 27 January 2019 (UTC)
 * Comment Thoughts on this as a starting point?
 * When an IP user makes an edit… (no point in making a ton of spam cleaning up inactive users' talk pages)
 * If the IP has had no activity in the past 3 years… (activity = contributions, receiving talk messages, being blocked, even if the block was issued >5 years ago)
 * If the talk page consists only of templates from a whitelist… (for starters, uw- templates, along with their ClueBot and Huggle variants, and the Shared IP Notice Twinkle uses)
 * Wrap the talk page in Old IP warnings top.
 * It's super conservative, but would cover most cases and we could expand it in the future. Gaelan 💬✏️ 05:03, 12 January 2019 (UTC)


 * Support archiving any notice that's more than a year old. That doesn't include "school" notices and similar, or any block notices that are still in effect (e.g., hardblocked IP addresses). Would also recommend removing 100% of sock tags on IP addresses that are more than a year old, even sooner if it's a known dynamic or mobile phone IP.  These warnings and tags are quite likely to scare away potential new users, and serve little to no useful purpose for the administration of the project. Risker (talk) 05:36, 12 January 2019 (UTC)
 * Oppose as is I'm with User:Zzuuzz here., I think a year can be too short. I'm not sure we can get one size fits all. Doug Weller  talk 13:08, 12 January 2019 (UTC)
 * I'm sure it can be done with a little preparation, but yes I think just blanking pages after a year is probably a bit too much. If we're to start going after the low hanging fruit I'd probably go with something like Gaelan said above: No activity for 5 years, no talk page history for 5 years, and only automated warnings in the history. Five years is again super conservative, but it's about the longest block you'll see and it's probably a good starting point for a general rule. I know BD2412 has complained about the backlinks before, so I don't know if wrapping the warnings would be as helpful as just blanking them. If it could (or would) be fitted into existing tools for when an IP edits that would be useful, but I don't really see any problem with a bot doing it on a schedule. My main concern really is just blanking what could be useful notes or discussions which can help understand edits made years earlier. Some may dismiss this stuff as some sort of waste of space, but historically I think it can be really useful. -- zzuuzz (talk) 14:53, 12 January 2019 (UTC)
 * Yes, backlinks have been one of my main concerns because sometimes an editor needs to get an accurate sense of what is linking to a title from all namespaces, and a bunch of IP talk page links just muddy that view. We should not keep these in any form longer than is necessary to pass on the message to the IP about them. bd2412  T 17:30, 19 January 2019 (UTC)
 * Comment As I have stated before, I have no problem with archiving or even blanking of old warnings/remarks. I have a problem with outright deletion of old-IP talkpages, which is something that should NEVER be done.
 * In my view, there is no issue with archiving (or even blanking) anything (like regular archiving) anything on a shared IP (yes, I know, detection) after even 2-3 months, and anything on a static IP (that has not been used for over 1-2 years). I would prefer just archiving everything as that leaves tracks better visible and avoids having to select what not to blank.
 * To reiterate my reasoning: plain vandalism on an IP is untraceable to a person. But any form of systematic vandalism (most specifically spam, but also socking, strong COI, string single-purpose editing) is always done by a certain person (/organisation).  The IP is changing, the person/organisation is not.  Say Mr. X. is spamming www.mrx.com to a page using IP 1.1.1.1 and we give them a level 1 warning that they should not do that, and Mr. X. is coming back 1 hour later using IP 1.1.1.2, he technically deserves a level 2 warning, not another level 1 warning.  It is, obviously, the same person.  Some spammers rack up 10 level-1 warnings because no-one notices that they are actually spamming.  On the spam blacklist that is still enough to say 'they do not listen, we tried to warn but warnings do not arrive'.  Regarding age of that: if Mr. X. in 2009 spams a handful of times (on IP 1.1.1.1), racks up a level-4 warning and stops .. and comes back in 2019 starting (on 1.1.1.2) to rack up a handful of warnings, it is still the same physical entity spamming (unless the domain changed owner, which can be seen).  They may expect that rules have changed on Wikipedia, but 4 warnings in 2009 and an unheeded level-1 warning in 2019 could be enough to just blacklist to stop further disruption (on 10 years we will likely be a bit softer ..).  If such user talkpage is deleted, the track of 1.1.1.1 is lost.  However, we can see far back that 1.1.1.1 has spammed the same site, but without the talkpages it is very hard to detect (you need admin rights, seeing that there are deleted revids on the page).  (note, we have cases where companies/entities are spamming for 8-10 years, it appears a long time, but it is not).  --Dirk Beetstra T  C 05:31, 13 January 2019 (UTC)


 * Is there a reason why we cannot simply add an existing archive bot with a 1-year or 2-year archive time to every non-blank IP talk page that contains material older than 1 or 2 years? If I do this manually when I add a warning to an IP talk page, is there a preferred bot? --Guy Macon (talk) 16:24, 13 January 2019 (UTC)
 * It would need to run from the expiry of the last block, not the time the warning was left—if an IP has been unblocked after a long period (e.g. a year-long block as a believed open proxy) and within minutes of the block being lifted the problems resume, we obviously want to know the background. I'm sure it wouldn't be difficult to code a bot to do this, but one of the existing bots couldn't be used off-the-peg. &#8209; Iridescent 16:34, 13 January 2019 (UTC)


 * Support whatever the details, this is a good idea. Headbomb {t · c · p · b} 06:08, 14 January 2019 (UTC)
 * I like the general idea, assuming "archived" means archived and not just blanked. I also wonder if, as opposed to a bot, it wouldn't be possible to add some sort of function to existing tools such as Twinkle to semi-automate use of old ip warnings top, which doens't archive but does collapse old warnings. we could leave it up to the best judgement of the warning user, as it is now without any new policy. Beeblebrox (talk) 18:44, 19 January 2019 (UTC)


 * Tentative support. I quite like the idea of modifying Twinkle, Huggle, et al. to automatically collapse old warnings when issuing new ones, since those tools are how a great many warnings are issued in the first place. Novusuna talk 22:08, 21 January 2019 (UTC)
 * Support modifying Twinkle, Huggle etc. If we run a bot to do this, we should take into account that this will pop up as "You have a new message" for the IPs in question, which might be a little confusing and definitely counterproductive for users with dynamic IPs.  Daß &thinsp;  Wölf  23:40, 26 January 2019 (UTC)

RfC of potential interest
An RfC is underway that includes a proposal, and a discussion (that interested "watchers of this page" wound enhance by participating) I hope that many will! The discussion is located at Wikipedia talk:Twinkle. Thank you.--John Cline (talk) 06:10, 29 January 2019 (UTC)

Reference desks
The thread about the Reference Desks that was moved to a subpage seems to have about run down. Is it going to be brought to a conclusion? --76.69.46.228 (talk) 08:55, 23 January 2019 (UTC)
 * The discussion still seems to be active with people posting today as well and the default time for an RFC to stay open is 30 days, so there is still time. Anyone is free to request a close by uninvolved editors at WP:RFCl once the 30 days are over although this probably needs closing by a larger number of experienced editors. Regards So  Why  12:04, 23 January 2019 (UTC)
 * Sorry, I didn't realize there was a default duration. --76.69.46.228 (talk) 20:50, 24 January 2019 (UTC)
 * Okay, we're now past 30 days (and on the relocated thread it's also being suggested that it's time to close it). Now what? --76.69.46.228 (talk) 07:58, 30 January 2019 (UTC)
 * It is already listed at WP:ANRFC but I would not hold my breath for a timely closure on that one. It is a very large discussion with many proposed options. The main policy question (shut down the whole thing or not) is little more than a show of hands (no real discussion / consensus-building). I would commend anyone extracts actionable information from that mess, but sometimes, RfCs simply fail... Tigraan Click here to contact me 08:17, 30 January 2019 (UTC)

Public Domain 2019 Russia

 * EN: Dear colleagues, please comment on CentralNotice banner proposal for Public Domain 2019 Russia uploads & article contest. (18 February - 31 March, all IPs from Russia, Wp/Ws/Commons, 1 banner impression per two weeks). Thank you. JukoFF (talk) 15:02, 30 January 2019 (UTC)

2nd chance script
Following a request at WP:SCRIPTREQ on the advice of, the awesome and  have respectively written a script and a module to automate large portions of 2nd chance. I'm particularly interested in using the user script, as it automates away a large portion of the technical/legal steps in 2nd chance for the new users who receive that template. I'll be sending DannyS712 some requested changes to the script, but it's just about at the level I'd like to test it on real unblock requests.

I'm here to ask for consensus to do a limited trial of this script on real blocked users. In particular, when I would've otherwise used 2nd chance, I'd like to add this user script to the user's common.js and notify the user on their talk page how to use the script. The trial will last until three users have used this user script to request unblock for a second time after their unblock request was declined as 2nd chance. Because this requires directly editing another user's common.js, I'd like to get the community's sign-off before doing this test. Best, Kevin ( aka L235 ·&#32; t ·&#32; c) 19:33, 21 January 2019 (UTC)
 * I wanted to test the user script out on myself over at test wiki, and asked for admin and iadmin (there, not here) so I could block User:DannyS712 test and try it from that account, and be able to edit any bugs that come up. I'd prefer to do that before we start editing the common.js of a blocked use. declined my request for permissions, directing my to one of the wikis dedicated to messing around with admin powers, but if this is going to become a tool that blocked users have installed then I hope that they will reconsider. --DannyS712 (talk) 19:37, 21 January 2019 (UTC)
 * Open an account at the beta cluster and I'll get you the testing permissions. Based on a couple tests I did here, though, it seems like it works well enough to test with a few users here. Kevin ( aka L235 ·&#32; t ·&#32; c) 19:40, 21 January 2019 (UTC)
 * See your talk page --DannyS712 (talk) 19:50, 21 January 2019 (UTC)


 * Ummm....you're looking for permission to forcefully add personal javascript to other users, and citing legal requirements, and this script appears to also include  scripts from other users - if so, I'm really strongly opposed to this for security concerns alone. —  xaosflux  Talk 21:33, 21 January 2019 (UTC)
 * I'd be happy to, once I iron out the kinks, have it moved to the mediawiki space so that I can't edit it. The only thing my code imports is another function of mine, which likewise can be moved. We already add javascript for other users (common.js, skins, etc) under the belief that it is secure if only iadmins can edit it, which would be the case with this script once its moved. I'd don't see how this creates any new security concerns, given that this would be limited to 1) users already told to attempt a "second chance" and 2) makes no edits without being activated by the user and 3) the code itself is (imo) pretty easy to read and see that it has no hidden edits --DannyS712 (talk) 21:41, 21 January 2019 (UTC)
 * Common scripts (such as vector.js, common.js) are not just secure because their write access is severely limited, but because they are highly visible (i.e. highly watchlisted). Significant changes to such pages generally undego a propose/review/execute/monitor process for each edit.  Forcing changes in to arbitrary User:username/common.js files would also require that everyone who will participate in this process become an interface administrator, contrary to one of the goals of reducing this access. —  xaosflux  Talk 21:51, 21 January 2019 (UTC)
 * Alternatively, every time a blocked user has an unblock request declined as 2nd chance, a note is put somewhere (a dedicated page, iadmin noticeboard?) which user it is, and then a pre-existing iadmin can add the one line of code to that user's common.js (importScript ( 'MediaWiki:Second chance.js' );) or something like that. --DannyS712 (talk) 21:57, 21 January 2019 (UTC)
 * We can also package it as a gadget of some kind if the concern is not having the user's consent, but I'd expect that would take considerable texting testing Kevin ( aka L235 ·&#32; t ·&#32; c) 00:59, 22 January 2019 (UTC) beforehand. Best, Kevin ( aka L235 ·&#32; t ·&#32; c) 22:27, 21 January 2019 (UTC)
 * Testing? --DannyS712 (talk) 22:30, 21 January 2019 (UTC)

Hi. Until I can test this out at the beta cluster, I don't think its ready for even a discussion about inclusion. Thus, this should be put until T212327 is solved, since I need to be able to confirm my accounts there. --DannyS712 (talk) 04:23, 22 January 2019 (UTC)
 * Though I think this is a bad idea as referenced above, it should be trivial to have your alt account load this to their own user.js and have someone block your account. — xaosflux  Talk 04:46, 22 January 2019 (UTC)
 * I have added the script to "my" userspace on test wiki, and have the test account import it, so if beta isn't working can you please just block User:DannyS712 test on testwiki for a week? And, can you also give me importer there so I have a variety of pages to test the script with, to ensure that there aren't any bugs? --DannyS712 (talk) 06:31, 22 January 2019 (UTC)
 * We could make this into a gadget and add a line to the template asking them to enable the gadget and proceed from there. <b style="font-family:monospace;"><< FR (mobileUndo)</b> 06:41, 22 January 2019 (UTC)
 * I'd much prefer to see that type of mechanism. From a non-technical aspect, such a request should be an option to 'make it easier' for the blocked person, not necessarily the only way we would ever unblock them IMHO. —  xaosflux  Talk 12:30, 22 January 2019 (UTC)
 * the block is made, importer is issued even rarer than interface admin (plus you would need to get a steward to do it) - feel free to copy/paste a reasonable number of test pages there and just mark for speedy delete when done. — xaosflux  Talk 12:28, 22 January 2019 (UTC)
 * Oh, okay. Thanks --DannyS712 (talk) 16:17, 22 January 2019 (UTC)
 * I'm not actually totally sure what the current concern is. Are you worried that your account on the beta cluster will be compromised? It's a testing site, there's no content on it and accounts can be easily locked in any case. What if we obtained the blocked user's consent before adding the script? Would that alleviate your concerns at all? Best, Kevin ( aka L235 ·&#32; t ·&#32; c) 08:48, 26 January 2019 (UTC)
 * Its that I can't log in to the beta cluster with my test account at all. I've tested it a bit on test wiki, and will go do some more tests now --DannyS712 (talk) 09:02, 26 January 2019 (UTC)
 * Hey so I have a version 2.0 of the script that should work for beta testing on users that agree. Maybe we can ask if anyone is willing to be blocked for a day to try it? --DannyS712 (talk) 10:15, 26 January 2019 (UTC)
 * The idea above of publishing as a gadget, and telling the user to opt-in to it sounds best to me. Additionally, process wise: this should always be optional (i.e. tasks we want an editor to perform should be able to be done even without script assistance). —  xaosflux  Talk 15:50, 26 January 2019 (UTC)
 * , I would just create a new testing account for now, and not worry about a specific name on a test cluster instead of waiting for that ticket to be resolved (which could potentially be a very long time). Feel free to let me know if you need any rights on the beta cluster. SQL <sup style="font-size: 5pt;color:#999">Query me!  16:08, 26 January 2019 (UTC)
 * In that case, I have made a new account. For this (my main account), can you add admin and iadmin rights? Thanks --DannyS712 (talk) 17:28, 26 January 2019 (UTC)
 * , Sure thing, done! SQL <sup style="font-size: 5pt;color:#999">Query me!  17:36, 26 January 2019 (UTC)


 * Do people use this template that much anymore? I'm fairly active in CAT:RFU, and I don't think I've ever seen this used. is what is used most often now, if a template is used, and most other times when 2nd chance is an option, you'll have a non-templated response. Not really a technical comment as much of a "are we discussing something that would ever be used?" TonyBallioni (talk) 19:00, 26 January 2019 (UTC)
 * I uss it quite a lot but feel guilty doing so becuase it's not actually that plausible for the new editors to follow the technical instructions. I'm sure if it's an actual option it'd be used more. Kevin ( aka L235 ·&#32; t ·&#32; c) 19:34, 26 January 2019 (UTC)
 * Idk, I just make the scripts lol; maybe if we have this, more people would take advantage of a second chance? --DannyS712 (talk) 19:36, 26 January 2019 (UTC)
 * Yeah, I figured you used it since you brought it up :) I don't think I've seen anyone else use it, though. I was talking to about it, and I honestly didn't know this existed before today because I've never seen it used.From a practical standpoint as well, I don't think the language is that useful and if I were a blocked user I'd just give up on ever being unblocked if someone templated me with it, because its a wall of text and the message I'd get was We don't trust you. I don't think a script will change the fact that the template is really poorly designed/worded for the task it is intended for. TonyBallioni (talk) 19:40, 26 January 2019 (UTC)
 * Well, if you look at https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Gadget-secondChance.js, I tried to soften the language. Of course, for some reason its not working on the beta cluster, but it does work on test wiki and stuff, so I'll try to troubleshoot the issue --DannyS712 (talk) 19:55, 26 January 2019 (UTC)
 * I mean, a block is probably a good clear message that "we don't trust you". How are we supposed to respond to appeals from, e.g., VOA blocks? 2nd chance gives a good middle ground between a straight unblock (it allows you to edit real WP articles, subject only to being posted to the user talk page) and a decline (it doesn't actually change the block). Kevin ( aka L235 ·&#32; t ·&#32; c) 20:00, 26 January 2019 (UTC)
 * hey. I've been testing it out more on the beta cluster and I've run into 2 issues so far. The first is dealing with captcha, which I think I solved. The second is abuse filters. Global rule 11 (https://deployment.wikimedia.beta.wmflabs.org/wiki/Special:AbuseFilter/11) prevented me from adding external links, but I'd like to be able to see what specifically it scans for so I can change my regex accordingly. I can't see it, because its marked private. Can one of you give me admin on the deployment page, so I can fix my script? --DannyS712 (talk) 20:18, 26 January 2019 (UTC)
 * , re: how are we supposed to respond: if it’s clearly a high school kid messing around I normally unblock on their word that they won’t do it again if the unblock request is reasonable. No need for identifying helpful content or whatever. If it’s an LTA who is claiming to be reformed, a deeper discussion than a template is needed, IMO. I don’t really see a situation where I’d support using the 2nd chance procedure outside of having someone explain how to add sourced content for an unsourced content block. Either it’s way over the top (high school kids) or not enough (LTAs). Blocks of “regulars” tend to be too complex for it as well. TonyBallioni (talk) 22:58, 26 January 2019 (UTC)
 * So I read the private filter, and I think I found a work-around that will stop it from messing with my script:

"&! (user_blocked & page_namespace == 3)"

However, I can't actually test it, because the global filter requires "abusefilter-modify-global" to modify. I'm sorry to keep bothering you guys, but would you mind adding me to one of the user groups that includes this? See https://deployment.wikimedia.beta.wmflabs.org/wiki/Special:GlobalGroupPermissions for the list.

Thanks so much, --DannyS712 (talk) 23:32, 26 January 2019 (UTC)
 * , Done! SQL <sup style="font-size: 5pt;color:#999">Query me!  02:30, 27 January 2019 (UTC)
 * see the newest version at https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Gadget-secondChance.js. I think this is ready for some testing. There is a current AN discussion about unblocking someone under the standard offer. Maybe see if they would be willing to try it? I'm not pinging them, since this would need IAdmin approval (among others) first, and since that editor is currently unblocked (but only to participate in the AN discussion), rendering the script useless (it only works if you're actually blocked in its current form). Thanks, --DannyS712 (talk) 00:52, 31 January 2019 (UTC)

Full screen edit button
Sometimes when I am editing a longer page or section, I like to drag the corners of the edit box to take up the largest amount of space that it can on the screen. This requires some maneuvering and adjustment. It occurs to me that others may also like to do this, so it would be nice to have a single button that automatically expands the edit window to the largest size it can occupy without going offscreen. Is this doable? bd2412 T 16:58, 30 January 2019 (UTC)


 * - YOU CAN EXTEND THE SCREEN?! Why did no-one tell me? I don't know about the proposal but the issue alone is enough to be helpful! Nosebagbear (talk) 17:42, 30 January 2019 (UTC)
 * Or shrink it, as the case may be, assuming that you're using the 2010-era WikiEditor. Just drag the little triangular-ish lines in the lower right corner of the main editing window.  If there's a particular size that fits well for you, then you can set that size in your personal CSS pages.  (Check WP:VPT's archives for directions.)  WhatamIdoing (talk) 04:06, 1 February 2019 (UTC)

BLP Dating
I would like to suggest that as we are not "Hello" magazine we do not cover a relationship until someone is engaged, or some other defining point that may be suggested. I am concerned that without a defining point undue interest in someone's relationships is not healthy and looks like stalking. Britmax (talk) 10:21, 25 January 2019 (UTC)
 * Surely the most important factor is how reliable sources cover the relationship, and not what stage the relationship is at? Iffy★Chat -- 10:45, 25 January 2019 (UTC)
 * We should only mention relationships when they have been covered by reliable secondary sources (which Hello and gossip columns are not) and are relevant to the encyclopedic coverage of a person. As Iffy said, the coverage is more important than the stage of the relationship, but in practice it is very unlikely that any current short-term relationship will attract such coverage and be a relevant part of a person's encyclopedic biography. This doesn't require any change to current policy and guidelines, but just proper enforcement, particularly when it comes to biographies of living people. Do you have any examples where you feel that our current content inappropriately invades privacy? Phil Bridger (talk) 12:45, 25 January 2019 (UTC)
 * How do you know that Hello is not reliable. My guess is that they have some sort of fact-checking operation and some incentive to get their facts right. The "litigation" section of their articles lists two suits for invasion of privacy but none for making false statements. I get that Hello is read by the The Sort Of Persons With Whom We Do Not Wish To Associate, but that's different from being unreliable for statements of fact. Herostratus (talk) 03:33, 27 January 2019 (UTC)
 * I'm thinking that Herostratus is probably correct: Celebrity gossip magazines tend to get their facts right, and if one says that Sally Star and Joe Film are dating (and especially if several of them say the same thing), then you can generally "rely" upon them to get their facts correct.  Whether to include that (reliably sourced) information is a matter of WP:DUE.  If sources overall put a lot of emphasis on this relationship (e.g., more stories in gossip magazines about dating than stories anywhere about anything else), then we should include it.  But I think in the typical case, User:Britmax's sense that this is undue is correct.  The only difference is that I'd say that it's "WP:UNDUE", as well as regular-dictionary-definition undue.   WhatamIdoing (talk) 04:02, 1 February 2019 (UTC)
 * Oh, absolutely on that point. We shouldn't report on dating relationships, and on non-marriage relationships unless its at the level of crypto-marriage. And not at all if there're any privacy concerns whatsoever. In fact, WP:NOTNEWS engages on this. Most people, reading only the title, assume NOTNEWS says we don't cover very recent events, when it says no such thing. But it does say "news reporting about celebrities... can be very frequent and cover a lot of trivia, but using all these sources would lead to over-detailed articles that look like a diary" and "routine news reporting of... celebrities is not a sufficient basis for inclusion in the encyclopedia". So there's your rule to cite.


 * I was just making the point that sometimes there's some unwarranted snobbery regarding some sources. For instance, some people would disdain Cosmopolitan as a source, but here is a piece from a Cosmo fact-checker. "Any material that is vaguely health-oriented has to be verified by a medical doctor or published medical literature" and her job is to that. "All descriptions of beauty tricks must come from interviews and are cross-checked with follow-up emails or calls from the research team.... Every word in Cosmo, surprisingly, is verified with a professional rigor that far exceeds virtually all Internet publications and daily newspapers". (Incidentally, your Important Book by your Distinguished Professor is usually not independently fact-checked.) So, I don't know what kind of operation Hello is, but I'm not going to base my assessment on snobbery. Herostratus (talk) 04:59, 1 February 2019 (UTC)

Suggestion to rename several country articles
The Wikipedia edict to “Use commonly recognizable names” has, in some cases, led to the use of article titles that have become obsolete. Many editors wish to use an article name they learned many years ago and with which they are comfortable. (By that rational, some of us elderly Wikipedians might wish to use “Belgian Congo” for the article on the “Democratic Republic of the Congo”.) The following proposed article moves are all controversial. In each case, the proposed article title is somewhat less familiar than the current title. I wish to put them out here for discussion before I make any formal move proposals.

I have included references to ten recognized English language authorities on country names:
 * 1) The United Nations
 * 2) The United States Department of State
 * 3) The British Foreign and Commonwealth Office
 * 4) Global Affairs Canada
 * 5) The Australian Department of Foreign Affairs and Trade
 * 6) The South African Department of International Relations and Cooperation
 * 7) The Irish Department of Foreign Affairs and Trade
 * 8) The New Zealand Ministry of Foreign Affairs and Trade
 * 9) The International Organization for Standardization
 * 10) The World Trade Organization

Move Ivory Coast to Côte d'Ivoire
Since 1986, the Republic of Côte d'Ivoire has preferred to use its French country name “Côte d'Ivoire” in the English language rather than a literal translation of its name such as “Ivory Coast”. The United Nations, the United States Department of State, the British Foreign and Commonwealth Office, Global Affairs Canada, the Australian Department of Foreign Affairs and Trade, the South African Department of International Relations and Cooperation, the Irish Department of Foreign Affairs and Trade, the New Zealand Ministry of Foreign Affairs and Trade, the International Organization for Standardization, and the World Trade Organization all use the country name “Côte d'Ivoire”. Without question, the article for this country should be moved to “Côte d'Ivoire”.


 * Support this has long been the country name. Using the non-standard name just misleads people. Legacypac (talk) 17:28, 1 February 2019 (UTC)
 * Oppose raising it in this way. Do a proper WP:RM proposal at the article. Johnbod (talk) 18:05, 1 February 2019 (UTC)
 * Oppose - Another hotly contested move with numerous past requests at Talk:Ivory Coast, this needs to be discussed at the roper venue. - Knowledgekid87 (talk) 18:18, 1 February 2019 (UTC)

Move East Timor to Timor-Leste
Since its founding in 2002, the Democratic Republic of Timor-Leste has preferred to use its Portuguese country name “Timor-Leste” in the English language rather than a translated version of its name such as “East Timor”. The United Nations, the United States Department of State, Global Affairs Canada, the Australian Department of Foreign Affairs and Trade, the New Zealand Ministry of Foreign Affairs and Trade, the International Organization for Standardization, and the World Trade Organization all use the country name “Timor-Leste”. The British Foreign and Commonwealth Office and the Irish Department of Foreign Affairs and Trade use the unhyphenated country name “Timor Leste”. The South African Department of International Relations and Cooperation continues to use the country name “East Timor”. I believe the article for this country should be moved to “Timor-Leste”.


 * Support long the country name and the one internationally recognized. Timor means East so East Timor is actually a dumb name but then Leste also means east, anyway we should go with the name officially recognized. Legacypac (talk) 17:28, 1 February 2019 (UTC)
 * Don't care, but Oppose raising it in this way. Do a proper WP:RM proposal at the article. Johnbod (talk) 18:05, 1 February 2019 (UTC)


 * Oppose - I want to note that a previous move request last occurred in October, 2018 Talk:East Timor. The name seems to be hotly contested and needs a proper move request. - Knowledgekid87 (talk) 18:16, 1 February 2019 (UTC)

Move Cape Verde to Cabo Verde
Since its founding in 1975, the Republic of Cabo Verde has preferred to use its Portuguese country name “Cabo Verde” in the English language rather than a translated version of its name such as “Cape Verde”. The United Nations, the United States Department of State, Global Affairs Canada, the Australian Department of Foreign Affairs and Trade, the New Zealand Ministry of Foreign Affairs and Trade, the International Organization for Standardization, and the World Trade Organization all use the country name “Côte d'Ivoire”. The British Foreign and Commonwealth Office, the South African Department of International Relations and Cooperation, and the Irish Department of Foreign Affairs and Trade continue to use the country name “Cape Verde”. I believe the article for this country should be moved to “Cabo Verde”.


 * Support been there and it is "Cabo Verde". This is not a big enough change to confuse anyome but brings Wikipedia in line wity the official name not a partial translation of the official name. Verde is Green so why do we use a half English half Portuguese name exactly? Legacypac (talk) 17:28, 1 February 2019 (UTC)
 * Don't care, but Oppose raising it in this way. Do a proper WP:RM proposal at the article. Johnbod (talk) 18:05, 1 February 2019 (UTC)

Move Czech Republic to Czechia
Since its founding in 1993, the Czech Republic has preferred to use “Czechia” (“Česko” in the Czech language) for the country’s name and reserve the name “Czech Republic” (“Česká republika” in the Czech language) for the country’s government. The United Nations, the United States Department of State, and the International Organization for Standardization all use the country name “Czechia”. The British Foreign and Commonwealth Office, Global Affairs Canada, the Australian Department of Foreign Affairs and Trade, the South African Department of International Relations and Cooperation, the Irish Department of Foreign Affairs and Trade, the New Zealand Ministry of Foreign Affairs and Trade, and the World Trade Organization continue to use the country name “Czech Republic”. The Czech language Wikipedia uses “Česko” as the article title for this country, and I believe the English language Wikipedia should use “Czechia” accordingly. This proposal has been debated numerous times, most recently at Talk:Czech Republic.


 * Support the country changed its name. Google maps has been updated. At some point we need to recognize reality and use the correct name here. 17:28, 1 February 2019 (UTC)
 * Oppose, and oppose raising it in this way. Do a proper WP:RM proposal at the article. Johnbod (talk) 18:05, 1 February 2019 (UTC)
 * oppose, both because it doesn't appear that the name change has "taken" (yet) and agree to the need to do a proper move proposal. Mangoe (talk) 18:10, 1 February 2019 (UTC)

Not a country, but move Washington, D.C. to District of Columbia
Created in 1791, the capital district of the United States is the “District of Columbia” and the city coterminous with the district since 1871 is the “City of Washington”. The United States Postal Service address for the city is “Washington DC”, which replaced the previous United States Post Office city address “Washington, D.C.” in 1963. The term “Washington, D.C.” is still approved by the Associated Press Stylebook and Briefing on Media Law, although it has been officially obsolete for 56 years. Most denizens of the city refer to their location as simply the “District”. The United States Census Bureau considers the District of Columbia to be a “state/territory-equivalent” and the City of Washington to be a “county-equivalent”. Currently, District of Columbia redirects to Washington, D.C.. I believe the primary article for the District should be moved to District of Columbia and a new article should be created for Washington (city) or the current Washington, D.C..

Yours aye, Buaidh  talk contribs 04:24, 1 February 2019 (UTC)
 * Isn't this what WP:RMCM is for? Killiondude (talk) 04:42, 1 February 2019 (UTC)
 * Yes it is, but I wanted a general discussion of this topic before I submit any specific move proposals.  Buaidh  talk contribs 17:29, 1 February 2019 (UTC)
 * Why? WhatamIdoing (talk) 18:21, 1 February 2019 (UTC)


 * I'm not really bothered about what name they are at but I would suggest that you look for another 10 sources that use the common name. The 10 you used are all political and may not reflect what a countries newspapers or the general public would call them in English. As for the last one not a chance. Is anybody outside of the US (and I would suspect some citizens) going to know that the District of Columbia is the capital city? If you search Google US and Google Canada it's fairly obvious that Washington, D.C. is a lot more familiar. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 06:38, 1 February 2019 (UTC)
 * And, as far as Czech Republic/Czechia goes, that has been dicussed to death many times. Very nearly all reliable sources in English call it the Czech Republic, whatever governments might want. Phil Bridger (talk) 10:58, 1 February 2019 (UTC)
 * That is unlikely to be true in the newer sources. Legacypac (talk) 17:28, 1 February 2019 (UTC)
 * Washington and the District of Columbia are 2 different things, similar to the fact that Boston and Massachusetts are 2 different things, renaming Washington, D.C. to District of Columbia would be the equivalent (if it wasn't for Washington and the District of Columbia having the same boundaries) of renaming Boston to Massachusetts.  Crouch, Swale  ( talk ) 11:01, 1 February 2019 (UTC)
 * Actually they are two names for the same thing exactly. Same territory, same government, same citizens. Both names are commonly used depemding on context. Legacypac (talk) 17:28, 1 February 2019 (UTC)
 * This is correct. DC is really, in practice, only a naming convention when the city has to be treated as a pseudo-state at the federal government level; there's no separate existence to the District from the city, and the distinction is worth only a couple of sentences in the article, which perhaps not coincidentally is how long the DC article has gotten when people have tried over the years to make it a separate article. Mangoe (talk) 17:59, 1 February 2019 (UTC)
 * "Washington" is the name of a settlement, as opposed to a territory, even though the names may be used interchangeably, compare this to London/Greater London for example. Maybe there should be separate articles, though since (as pointed out) they cover roughly the same area that may be unnecessary.  Crouch, Swale  ( talk ) 17:36, 1 February 2019 (UTC)
 * Stop trying to draw analogies with Britain. It's just not the same. It's more like the situation in Maryland where Baltimore City acts within the state governmental hierarchy as though it were a county unto itself; Baltimore County, which surrounds it, is in every way utterly separate. The only ways in which there is a district here is that (a) since the postal system is organized by states, it has to be a state, and (b) certain national govermental functions which are divided up by state are called "federal thing of the District of Columbia". But there's no organizational or geographical distinction between the district and the city. Mangoe (talk) 18:06, 1 February 2019 (UTC)
 * Oppose - Can we please have a proper discussion for this in the right place? - Knowledgekid87 (talk) 18:27, 1 February 2019 (UTC)

General comments on all 5 proposals
I have one comment that applies equally to all of these proposals... See WP:Official names. Blueboar (talk) 18:16, 1 February 2019 (UTC)

Reduce number of vandalism warning levels
It has long been my view that four warning levels is rather excessive. People really only should need to be told once to stop. The only caveat is whether they actually read the message, but those who clearly don't are also those for whom extra warnings are useless.

On nearly every other Wikimedia project I edit, usually only one or two warnings are given at the most. I think two levels would be a good compromise, retaining the softly-worded first level (in case of good-faith mistakes) and the third level while eliminating the second and fourth levels. Those who continue vandalizing after they know it's blockable don't need another warning (level 4), and level 2 warnings could easily be merged into level 1. This would decrease patrollers' workload while also decreasing the total amount of vandalism.--Jasper Deng (talk) 03:56, 28 December 2018 (UTC)


 * Support too many levels. I don't warn when a level 4 is needed I report. Vandals know they are doing vandalism. Legacypac (talk) 04:04, 28 December 2018 (UTC)


 * Not sure if I'll end up actually participating in this as far as support/oppose goes, but are you proposing this for only the uw-vandalism series, for selected user talk warnings, or for all user talk warnings?-- SkyGazer 512 <span style="background: linear-gradient(aqua, #d580ff);">Oh no, what did I do this time? 04:07, 28 December 2018 (UTC)
 * I guess it's uw-vandalism only since that is only warning template series for vandalism ― Abelmoschus Esculentus talk /  contribs 04:08, 28 December 2018 (UTC)
 * For now, I'm just proposing it for the vandalism templates, but I do want to bring it up as a general point of discussion. Other templates for which we should be reducing the number of warning levels are those related to spamming (since spam often falls in the same realm as vandalism), introducing deliberate factual errors, creating inappropriate pages, and maybe even BLP violations.--Jasper Deng (talk) 04:18, 28 December 2018 (UTC)
 * Sounds reasonable. I personally would probably support defining the other templates besides vandalism whose number of warning levels should be reduced as ones designed for any user whose is very likely to be acting in bad faith; imo, adding original research and expanding plot summaries unnecessarily should be treated very differently than blatant vandalism as far as warnings go.-- SkyGazer 512 <span style="background: linear-gradient(aqua, #d580ff);">Oh no, what did I do this time? 04:51, 28 December 2018 (UTC)
 * Support I don't think tolerating vandalism is a good idea. ― Abelmoschus Esculentus talk /  contribs 04:09, 28 December 2018 (UTC)
 * Is there any way to gather statistics on the effectiveness of the warnings? How many people get two warnings and then become productive Wikipedians? How many new editors change their ways after three or four warnings? Jack N. Stock (talk) 05:05, 28 December 2018 (UTC)
 * Support provisionally, although like Jack just above I think it's better to make this sort of decision with more data. Enterprisey (talk!) 05:08, 28 December 2018 (UTC)
 * Oppose. There's no requirement to go through all four levels. For egregious vandalism, I'll start with level 2, or I'll escalate 1 to 3. I also have no qualms blocking for clear vandalism after a level-3 warning has been given, since it mentions the possibility of a block. —C.Fred (talk) 05:09, 28 December 2018 (UTC)
 * I myself always start with at least level 2 unless I suspect it to be a genuine good-faith mistake. Long ago, I've had AIV requests declined after I did not go through all four levels. In the vast majority of vandalism cases, we really only need a single warning, not even two. So there is virtually no legitimate use case for all four levels.--Jasper Deng (talk) 05:36, 28 December 2018 (UTC)
 * Two warnings - Mild and Serious - should be enough. Legacypac (talk) 05:58, 28 December 2018 (UTC)
 * Please create a sandbox showing the proposed new warnings (could be fairly rough but enough to see likely wording). Johnuniq (talk) 06:23, 28 December 2018 (UTC)
 * I would keep uw-vandalism3 as-is, remove level 4 entirely, and pretty much keep level 1 with the modification that "did not appear to be constructive" is wikilinked to WP:VAND. This way, we can introduce the notion of vandalism without scaring the user by explicitly labelling them as such.--Jasper Deng (talk) 00:20, 29 December 2018 (UTC)
 * Comment On the one hand, there are edge cases, where I might have to see several edits from a user before I'm sure they are vandalizing, so a series of warnings (of one type or another) is called for by AGF. On the other hand, I have blocked a user after as few as one warning when the user was rapidly vandalizing many articles. I no longer monitor AIV, because after carefully reviewing each request, I almost never did anything because the case did not require blocking (ie, not vandalism, stale, etc.). The few times I thought blocking was called for, another admin usually blocked while I was reviewing the report. - Donald Albury 14:36, 28 December 2018 (UTC)
 * Unneeded - Like Jasper D o eng, I start with level 2 for vandalism. There's no need for a lvl 1, since a good faith vandalism mistake doesn't really exist - I tag them as lvl 1 disruptive instead. I wouldn't mind removing the bottom one, but I suspect people would then want to rephrase them and I think that would be counterproductive. I would definitely NOT want a reduction for the others warning templates. Nosebagbear (talk) 15:01, 28 December 2018 (UTC)
 * Support - While it may be unneeded, the extra warnings are also unneeded. While some admins see the 3rd warning as enough warning, I imagine that not all do, and may not block until after the final warning.  I also support the single warning idea, however, leave the 1st warning for WP:AGF. -  ZLEA  Talk \ Contribs 16:47, 28 December 2018 (UTC)
 * Unneeded As has already been said, there is no requirement to progress 1, 2, 3, 4 through the existing templates. Just give the appropriate level warning according to the situation, or no warning at all if that is what is warranted.  G M G  <sup style="color:#000;font-family:Impact">talk  20:30, 28 December 2018 (UTC)
 * Oppose we block as needed and when appropriate warning has been given or when no warning has been given at all if bad enough. This change would have no impact on admins. The advantage of the 4 stages of warning is mainly that it prevents people playing Huggle the Video Game® from reporting good faith IPs/school children and requesting indefinite blocks for stuff that isn't vandalism/doesn't need a block. Changing the warning levels would dramatically increase the bad reports at AIV and waste admin time in areas where it isn't needed. TonyBallioni (talk) 20:33, 28 December 2018 (UTC)
 * Support Those suggesting that there is no need use all 4 levels in turn are correct. They are also fundamentally wrong about the lack of need to reduce the number of levels. As usual, they look at things narrowly, through their own myopic lens. The vast majority of non-admin vandal fighters will not come here. They will plod on with the 1-2-3-4 warnings in fear of ANI if an over-vigilant Admin. reports them or refuses to enact a block because 1-2-3-4 has not been followed. There should be an immediate reduction from 4 to 3. In 6 months, 3 to 2.  Leaky  Caldron  20:40, 28 December 2018 (UTC)
 * Loving the personal attacks. Do you want 1, 2, 3 or 4 warnings for that ? Nick (talk) 20:43, 28 December 2018 (UTC)


 * Oppose there is no requirement to go 1-4. Use common sense. But graduated warnings have a purpose, just not for obvious trolling and blatant vandalism. Praxidicae (talk) 20:43, 28 December 2018 (UTC)
 * Oppose per Praxidicae. If you don't feel a certain warning level is appropriate, use the one you feel fits the situation. DonIago (talk) 20:53, 28 December 2018 (UTC)
 * Can any opposer give a single case of nonaccidental vandalism where all four levels’ use has been useful? Because if we are always skipping levels, then there’s a redundancy, and it has always been the case in my experience that I am skipping level 1 and giving at most two warnings in total. Also, Huggle and ClueBot NG automatically escalate by just one level at a time in many situations where a quicker one is warranted. If those who use the tool are making frivolous reports after going through all four, then that quite frankly is abuse of the tool and does not address the broader problem.  my surname is not “Dong”.—Jasper Deng (talk) 22:02, 28 December 2018 (UTC)
 * Jasper Deng, the point is that what Leaky caldron is saying as a negative is actually a benefit: it really cuts down on bad AIV reports from people who are new and decided on their 3rd day on the project that they were going to dive into anti-vandal work without realizing how Wikipedia works. If you're an experienced user, use your judgement as to which warnings to give. Having the graduated warning system is very useful for new users who want to get involved with anti-vandal work, however. Basically the warnings exist equally to train them as much as warn vandals. TonyBallioni (talk) 22:12, 28 December 2018 (UTC)
 * I contend that the amount of vandalism eliminated will result in a net decrease in the amount of work. It might result in more work at AIV itself, but result in a net reduction of reverts, making vandalism-fighting less high-speed and less tempting to rush. Also, I seriously doubt it will result in a decrease in the amount of frivolous reports. Those who make them should, if anything, be educated earlier on NOTVAND rather than later, and we get a net reduction of frivolous warnings and consequently less BITE'y behavior overall. --Jasper Deng (talk) 00:27, 29 December 2018 (UTC)
 * The argument "Can any opposer give a single case of nonaccidental vandalism where all four levels’ use has been useful?" contains a logical fallacy. It is not true that the only reason to have four levels is so that all four levels may be used on the same vandal. I often start at 2 and go to 4. I have seen other editors start at 1 and go to 3. Neither of us individually use all four, but together we do. --Guy Macon (talk) 01:58, 2 February 2019 (UTC)
 * Oppose. Like others have stated, there is no requirement to go through all of the warning levels. But the warning levels do have their purpose, including for reports at WP:AIV. Some newbies just don't get the point and need at least two warnings. I don't see that four warnings are needed unless the editor missed the talk page messages somehow, but anyway. Flyer22 Reborn (talk) 22:16, 28 December 2018 (UTC)
 * oppose unnecessary. If I only want 2 levels warning for serious people, I will start level 3 directly. If someone is a newcomer, we should remain level 1 per WP:BITE Hhkohh (talk) 22:17, 28 December 2018 (UTC)
 * I did not advocate removing level 1. See the second paragraph of my proposal.--Jasper Deng (talk) 00:27, 29 December 2018 (UTC)
 * Seen and known but I sometimes give them level either 1 or 2 depending on their edits Hhkohh (talk) 01:14, 30 December 2018 (UTC)
 * Neutral per Johnuniq. Without a sandbox version of these new templates, I have no idea what I'm !voting on here. I completely sympathize with the idea; every time someone gives the goatse LTA the obligatory four warnings before reporting to AIV, I want to come out swinging with a clue-bat, but I can't imagine how these would be phrased so as not to be overly WP:BITEy when it comes to kids making test edits, or when the RC patroller made a mistake and flagged a good edit, etc. I'm open to ideas, though. Suffusion of Yellow (talk) 22:20, 28 December 2018 (UTC)
 * I've also had a request or two turned down at AIV. But if the editor is clearly vandalizing or clearly otherwise editing disruptively and I have warned the editor at least twice (via template warnings or non-template warnings), that is usually enough to get the editor blocked. Some admins will make a WP:NOTHERE block. Flyer22 Reborn (talk) 22:27, 28 December 2018 (UTC)

- anything that doesn't fit the mold is "vandalism" and sees no reason to try to cooperate - any idiot can leave whatever message they want (no matter how wrong) and so there's no point in paying attention to messages - because the reporting user was wrong to use the vandalism warning, the reported user's edits were somehow in the right Meanwhile, the reporting user gets frustrated because I have to stop and properly explain to someone who sincerely believes they're trying to help how their behavior wasn't helpful. Now, the counter example of LTAs is brought up, and for fuck's sake if it's an LTA just report them on sight. If someone is leaving automated warnings for an LTA to enable a report button, they should have their tools taken away so they can learn how warning and reporting users actually works. TL;DR: ''Three levels (maybe a mistake, warning, final warning) seem good for users who are manually warning and reporting but I feel like any automated warning tools should stick to four levels. Take away tools from people who use them to the exclusion of common sense.'' Ian.thomson (talk) 22:42, 28 December 2018 (UTC)
 * Oppose - This adds unnecessary bureaucracy to the process and regarding an issue that hasn't shown a need for any kind of change. The number of warning levels exist in order to make the process easy for patrollers, accommodate for all situations that occur, and (most importantly) assume good faith by default with bots, editors, and automated tools. There's currently no requirement that users be warned with all four warning levels and have made a fifth disruptive edit before they're blocked. As stated above multiple times by other users: I warn users very differently depending on the severity of the vandalism or disruption, their past warnings, their block log, how quickly they're attempting to push disruptive edits, what pages they're making bad-faith disruptive edits to, if sock puppetry or abuse of multiple accounts or editing while logged out is suspected, and many other factors. I use this information to either start the user at a level 2 or 3 warning compared to a level 1 warning, start the user at a level 4im warning, block the user only after they've been given a level 3 warning as opposed to waiting until after they've been given a level 4 warning, or use a different method to warn the user alltogether. The warning level system, which warnings are left first, or when action is taken earlier as opposed to waiting until the user has been warned four times and has made a fifth disruptive edit - is widely practiced and used on a judgment-level basis, and administrators who regularly handle this disruption already know to review reports at AIV, ANI, or other places thoroughly, verify and determine if the edits constitute vandalism or bad-faith disruption or not, determine if the user was sufficiently warned given the disruptive edits made, and do this before they consider action.  ~Oshwah~  (talk) (contribs)   22:34, 28 December 2018 (UTC)
 * On the fence I usually start off at uw-2 and work up through uw-4 before blocking someone (unless it's pretty obvious they know what they're doing). This is not to say that uw-1 messages are useless: I use uw-test1 almost consistently in place of uw-vandalism1 when I feel that uw-vandalism2 might not yet be appropriate.  There is no uw-test4 because, well, they're obviously engaging in vandalism -- that suggests uw-test and uw-vandalism need to be merged.  That said, I manually post warnings just to be sure I'm using the right one.  I've encountered plenty of middle-experience users using Twinkle who issue generic vandalism warnings for any revertable actions (instead of uw-delete, uw-npov, uw-notcensored, uw-agf, uw-npa, uw-fringe, uw-nor, uw-spam...), ignoring WP:NOTVAND to the point of failing WP:AGF.  The reported user (who wanted to be productive) then gets it in their head that either:
 * Ian.thomson, this is the best description of the issues surrounding AIV I have ever read. Also, yes, if its an LTA, we block on sight. TonyBallioni (talk) 23:33, 28 December 2018 (UTC)
 * I completely agree with Ian.thomson regarding how users tend to default their patrol actions to leaving a vandalism warning template compared to a more in-depth and explanatory warning (or God forbid, a custom warning... lol) for the actual problem - such as NPOV issues, unexplained content removal, adding content without a reference, test edits, or other actions that can be done and entirely in good faith. I consistently see users who patrol recent changes and do this, and it bothers me a lot when I see that. If anything, I think that certain templates shouldn't be automatically grouped into just warning the user for "vandalism" if a level 3 or 4 warning is left. I'll also add that automated tools should separate previous warnings left and know if it was for vandalism and blatant disruption vs the others, and not automatically stack and leave the next warning level template regardless of what the user was previously talked to about - especially if this or a similar proposal in the future should ever pass. Example: A user is warned twice (level 1 and 2) for content removal without an explanation, but a day later an editor leaves a warning for vandalism - in this situation, since the user wasn't warned for vandalism before, they shouldn't receive a level 3 warning for vandalism.  ~Oshwah~  (talk) (contribs)   00:03, 29 December 2018 (UTC)


 * Meh I tend to think a better idea would be to make it clear that you don't have to work through all four stages or even start at the "general note" stage when it comes to blatant and obvious vandalism like writing "poop" or something similar in an article. I, and I belive many others, choose the template they belive is right for the situation, which sometimes means going straight to level 3 or 4, but in less clear cases starting lower. Beeblebrox (talk) 23:00, 28 December 2018 (UTC)
 * Support. Vandals know what they're doing. Having four levels makes editors feel they have to clunk through them in case they're later told they've jumped the gun. SarahSV (talk) 23:03, 28 December 2018 (UTC)


 * Opposition This... can already been achieved. Yes, 1-4 are there and are meant to be used, however... there is warning 4im. If 1-4 doesn’t cut it, then you can use a 4im. In the rare event you need to give an instant only one warning to a vandal, just give a 4im. 4im exists, and “one warning only” is EXACTLY what 4im is. Essentially, you’re reinventing the wheel. This system has more flexibility with the ability for 1-4 and also in extreme cases skipping those. This’ll just add less flexibility and versatility to the system, you won’t put a littering person in jail for life, would you? Best regards, Redactyll Letsa taco 'bou it, son! 23:07, 28 December 2018 (UTC) 23:07, 28 December 2018 (UTC)
 * This proposal is emphatically not about my preferences for giving warnings but about setting a project-wide precedent; I propose it because I see others wasting time and resources with giving all four warnings to blatant vandals. I might give that littering person a warning the first time if it were by accident (hence my proposal to keep two levels), but I would not hesitate to fine them if egregious. Also, since blocks are not punitive, this is not a proper analogy.--Jasper Deng (talk) 00:21, 29 December 2018 (UTC)
 * Support CLCStudent (talk) 23:11, 28 December 2018 (UTC)
 * Comment: The German Wikipedia, second largest after the English one, has only two warning levels for all cases, and a "-im" version if level 2 is applied directly. See de:Wikipedia:Huggle/Vorlagen. I personally never liked these templates; they instantly confront the editor with a big red stop icon and tell the user that their edits have been "unhelpful". However, it does seem to work there. Just for your consideration. Disclosure: I have been invited to this discussion by a notice on my talk page, likely based on my Huggle activity. ~ ToBeFree (talk) 23:14, 28 December 2018 (UTC)
 * Oppose 2, Support 3; I use uw-vandal1 for cases of people trying to do something that they might think is right, clearly isn't, and could be construed as vandalism. I use uw-vandal2 as a first warning for obvious cases of vandalism. I think 3 and 4 could be merged. At play there is an issue that if it is rapid fire a person may commit more vandalism without having seen an incoming warning and then end up being blocked before they've had a chance to read a warning. 2 warnings alone might not allow for this. --Hammersoft (talk) 23:42, 28 December 2018 (UTC)
 * Oppose - I've never interpreted the four warning levels as implying that all four need to be used in succession. In fact, I probably never have used all four in that way. I prefer level 1 for newbie edits likely made in good faith, as the text of the warning bears that out. If it appears deliberately-disruptive but is relatively benign, starting out with level 2 is perfectly reasonable and assumes no intent. With severely-damaging edits, there's no reason why one couldn't go straight from 2 to 4, or if continued disruption after level 1 belies bad faith then level 3 can be next.
 * I feel that the distinction between "probably good faith" and "probably bad faith" should be maintained; the "Hello, I'm Sable232" and direction to the Help Desk are good for the former, but sound laughably patronizing (or even condescending) to the latter and may prompt further disruption. --Sable232 (talk) 23:56, 28 December 2018 (UTC)


 * Strong oppose: no-one is saying you have to use all four in order, as if the vandal is levelling up at each step and once they've surpassed level 4 it's time for the boss battle. The last thing we need is more BITE and merging level 2 and level 1 would do exactly that. Plenty of edits that I revert are unhelpful but done out of ignorance rather than malice, and I need a pre-written message to slap on their talk pages to explain why I undid it, but something kindly written enough to not scare them away. — Bilorv(c)(talk) 00:26, 29 December 2018 (UTC)
 * Weak Oppose I am a big fan of the three strikes rule and think a solid argument could be made for dropping the level 4 warning. Once you have been told to STOP a given pattern of behavior three times, a 4th warning should not be needed. However, dropping things down to two warnings is a bridge too far for me. And some of the comments above make good points by noting that multiple warnings helps keep overenthusiastic newbies from reporting people too quickly. Also correctly noted, there is no requirement to go through all 4 levels of warning. If the behavior in question is obviously bad faith start with a level 2 or 3 warning. There is actually no firm requirement to issue warnings at all when dealing with egregious behavior. I have issued more than a few no warning blocks. It all depends on the exigent circumstances. Editors should adjust their response to the nature of the problem. How serious is the disruption? What is the chance that it is good faith mistakes (and so on)? Dealing with disruptive behavior requires a lot of situational judgement. -Ad Orientem (talk) 00:46, 29 December 2018 (UTC)
 * Oppose It's easy enough to issue a level 2, 3, or 4 warning "off the rip"; much harder to allow for good faith errors if the 2nd warning automatically triggers an AIV report. If anything, make sure it is abundantly clear in the instructions that it is acceptable to increase the automated level based on the patrolling editor's interpretation of severity and the clarity of a nefarious intent.--John Cline (talk) 00:50, 29 December 2018 (UTC)
 * Oppose A better solution would be for people to stop defaulting to level 1 warnings for malicious vandalism. Choose whatever warning level is appropriate based on the edit. I recommend setting your twinkle default to level 2 if you are lazy like I am. Natureium (talk) 04:14, 29 December 2018 (UTC)
 * Oppose Current system is a flexible tool to cater the appropriateness of warnings and levels as one see fits. I am an active vandal fighter and one of the handful counter vandalism program/course graduates. My vote based on my knowledge and experience as below.
 * 1) New IP editors (most of the vandals) - WP:Assume good faith. Warning level start at 1 and increasing accordingly to 4 before reporting to AIV.
 * 2) Choose the warning level appropriately to justify the nature of the edit or the behaviors of the vandalized editors. Any level warning can serve as the starting level and the warning level could skipped (such as from level 2 to level 4 for example) for clear malicious vandalized edits.
 * 3) Level 4 or (im) warning. It could be given to a vandalized editor who performs egregious vandalized edits across multi-pages in a quick succession or inserts shocking inappropriate image(s).
 * 4) an (im) warning. It could be given to the vandalized editor and report them to AIV at once if any abhorrent personal attack(s) such threat of legal action or threats of violence against an editor on their talk/user page.
 * 5) If any of the template wording is not suitable or additional details need to be included, one CAN always write a personalized warning messages and give warning level on the vandalized editor talk page without using the warning templates. Thank you. <b style="font-family:Georgia;font-size:80%;color:#FA0"> CASSIOPEIA</b>(<b style="#0000FF">talk</b>) 06:27, 29 December 2018 (UTC)
 * Oppose If you don't think all 4 warnings are necessary, just skip to level 4 or 4im. <b style="color:#090">Semi</b><i style="color:#099">Hyper</i><u style="color:#009">cube 14:50, 29 December 2018 (UTC)
 * Comment: Perhaps an alternative is to keep the different warnings for different levels of disruption, but remove the presumption that there must/should be some sort of escalation through them before action must be taken (and ensure that those who act - especially at AIV and the like, understand this.Nigel Ish (talk) 15:24, 29 December 2018 (UTC)
 * Oppose In my admittedly limited experience most vandals stop before I have to file an AIV report, but sometimes it takes multiple warnings to get their attention. Level 4im is available for editors who feel that a single report should be enough. Besides I often use, , etc, which likewise have four levels.  Strawberry4Ever (talk) 16:06, 29 December 2018 (UTC)
 * Meh AFAIK, there's no requirement to escalate in the order 1, 2, 3, 4, report. I tend to use 4im or start on 3 if it's obvious vandalism.  Probably best to keep it as it is but definitely support a measure to avoid instruction creep requiring anti-vandals to escalate in the aforementioned order.  Leave it to the discretion of users.    SITH   (talk)   16:55, 29 December 2018 (UTC)
 * This thread doesn't seem to have any relationship with Middle Eastern military history task force... ― Abelmoschus Esculentus talk /  contribs 08:02, 30 December 2018 (UTC)


 * Oppose I'm probably one of the guilty ones who go through all the levels when probably not required, but I certainly don't see it as a requirement in the most egregious cases, and I've seen lots of IP edits who stop after the 2nd warning. I have seen plenty of individuals who get reported to AIV before the final warning if they are particularly egregious, and there are also no restrictions in placing a higher level warning, as outlined above. Agent00x (talk) 23:18, 29 December 2018 (UTC)
 * Support. If one really does use all current levels, that amounts to five specific, distinct incidences of vandalism before a vandal is blocked, one for each level of warning plus the vandalism-after-final-warning that leads to a report. That's too many. So some say skip levels. Then what's the point of having so many levels? I've long thought we should reduce the number of warning levels, and I'm glad to see I'm not alone. As for how many levels, I'm fine with two. That way the number of incidents of vandalism before a block is three. And maybe it's just the baseball fan in me, but "three strikes you're out" is a fine paradigm. oknazevad (talk) 06:24, 30 December 2018 (UTC)
 * Question for the supporters: My personal preference is to not use the template at Template:Uw-vandalism1 for obvious vandalism like "H1TLER WUZ R1GHT!" or "qwertyuiopasdfghjklzxcvbnm!" because I don't think that vandals should be sent to the help desk. I also don't like the redundant "I am X" (I already have a signature at the end) or the insincere "hello" (I am warning them, not greeting them). Instead I use Template:Uw-vandalism2 as the first warning. And no, I have never been criticized for that choice. Other editors clearly like to use Uw-vandalism1 as the first warning. So are you proposing that I cannot use the template that I prefer or are you proposing that those other editors cannot use the template that they prefer? --Guy Macon (talk) 09:16, 30 December 2018 (UTC)
 * (...Sound of Crickets...) --Guy Macon (talk) 04:23, 3 January 2019 (UTC)
 * (...Chirp...) --Guy Macon (talk) 14:44, 6 January 2019 (UTC)
 * (...CHIRP...) --Guy Macon (talk) 02:01, 2 February 2019 (UTC)
 * Oppose. I don't think I've ever used all four levels, but I think flexibility is beneficial. 331dot (talk) 09:29, 30 December 2018 (UTC)
 * ’’’Meh’’’. I’m with those above who note that there is no requirement to follow the 1234 increasing level of naughtiness warnings. Roxy, the dog . wooF 16:39, 30 December 2018 (UTC)
 * Support. As someone who handles problematic edits by new users, I believe that only two warnings are necessary. For those who are opposing this based upon flexibility reasons, I totally understand your point of view and it wouldn't be that bad if things were to stay as they are. I frequently accelerate the warnings that I give to users who make severe problematic edits so that they receive level 2 warnings to begin with rather than level 1 or even that they receive a level 3 warning, if they make a significantly problematic edit after receiving a level 1 warning. So why do I believe that only two warnings are necessary? Because in the multiple years that I've been handling problematic edits from users, I've never seen anyone redeem themselves on that specific account. I'm guessing if someone matures from making this kind of edit, it is likely to be 5 - 10 years from when they made the account that has problematic edits attached to it. So what happens then? I believe they make a new account and go on to be productive members of the community from their first edit without the stain of the problematic edits made in their youth being associated to that account. Often I've noticed that new users who are here to contribute positively to the Wikipedia make good edits right from the start or as an IP before they make an account. Assuming that most, if not all new accounts will make problematic edits within their first edits is a flawed assumption to make because it just doesn't seem to happen that way. Sure, there are users who make mistakes that aren't vandalism related, like not being aware of NPOV or making formatting errors but on the whole, there are little to none productive users who produce edits that seem like vandalism within their first few edits to Wikipedia. Practically every account that within their first few edits make problematic edits that look like vandalism are here to vandalise. So on that basis, clear vandalism should be given 1 - 2 warnings before that user is blocked from disrupting Wikipedia any further. Thank you. -&#61;Troop&#61;- (talk) 17:37, 30 December 2018 (UTC)
 * Oppose per AGF. Four warnings has always been the norm. Skipping levels is occasionally appropriate for particularly egregious vandalism, and then it's up to the discretion of the responding admin whether to block. Reducing the number of warnings required would have no effect other than to increase the number of inappropriate blocks. Brad  v  🍁 17:42, 30 December 2018 (UTC)
 * Oppose. However, it should be made clear that it is not required for anti-vandalism fighters to start at level 1 and work their way up.  We also more test-or-vandalism templates at level 2-4; I can often say either it's a disruptive test or vandalism (especially with the Visual Editor, when the user may not even be aware of the problem), but neither the uw-test nor the uw-vand template series say what I'm trying to say.  Also, WP:AIV should not require that a level 4 warning be issued.  But that's a different proposal.  — Arthur Rubin  (talk) 09:42, 31 December 2018 (UTC)
 * Eliminate level 3 I don't see a need to warn again after level 3, if someone vandalized after being told clearly that what they are doing is vandalism and may lead to a block, they should not be warned further, as this just gives them more chances to vandalize, so I would like to just get rid of the level 3 warning for vandalism and go straight from 2 to something like 4. I find it annoying when people(or bots) go 1 by 1 thought all 4 warnings for an account with no purpose other than adding racial slurs or profanity. We still must keep level 1 for unclear cases where a mistake could be good faith, I know some will say just leave a custom message, but this takes time and would make me much slower at removing vandalism. I could see merging uw-test1 and uw-vand1. Tornado chaser (talk) 20:09, 31 December 2018 (UTC)
 * Oppose. The levels don’t have to go to 1–4 — you start at a level based on if the edit is good faith or not. —  python coder    (talk &#124; contribs) 22:33, 31 December 2018 (UTC)
 * Support. Excessive warnings are just a waste of time for all concerned--simplify, simplify, simplify. I've been a lot less active on anti-vandalism for the past few years, but there used to be some admins patrolling AIV who were very fussy about denying even mild blocks if some newbie IP or SPA wasn't given four full warnings in a very tight timeframe. This proposal seems to be heading towards "reject", but could closer please note that a major reason is that opposers don't think more than 1-2 warnings are necessary to justify a block? --Hobbes Goodyear (talk) 02:50, 2 January 2019 (UTC)
 * Oppose 2, Support 3 per Hammersoft. Level 1 for possible good faith edits, specifying why the edit is not appropriate. For intentional violations, start with level 2. Eliminate level 3, level 4 remains the final warning. Jc3s5h (talk) 04:14, 2 January 2019 (UTC)
 * Oppose The levels are really a check on automated tools and bots, there's no reason to jump through them all manually for blatant vandalism. Notices for good faith edits can be escalated by automated reverts, so fewer levels would result in more false positives in AIV. Qzd (talk) 01:41, 3 January 2019 (UTC)
 * Oppose, but change the level 1 warning to wikilink "did not appear to be constructive" to WP:VAND, which should do to give the hint that blocks can come from this activity. bd2412  T 02:30, 3 January 2019 (UTC)
 * Oppose. I mean you need these levels of nuance. I have seen editors who have been stepped up the ladder 1-2-3-4 and turned out to be useful editors. It's rare, but it doesn't happen never. I had one guy, like a year ago, who insisted on adding HTML tags. It took a while, stepped up the warning levels (also some actual person talk) and eventually even blocked for a bit, but he got it. And then he made good edits and AFAIK still is. And he wasn't summarily shunned from this human community, which don't we have enough of that in the world. So allow me this tool please. I have gone level 2-level 4 often enough, or even level 4 directly on rare occasions. But leave me the tools so I don't always have to do that. Herostratus (talk) 03:06, 3 January 2019 (UTC)
 * Strongly oppose. Usually while recent-changes patrolling, I utilize all four warning levels whenever necessary, to their full potential. From experience, it appears that the current four-warning system works well; in my opinion, reducing the amount of warnings to two would give the warned too little leeway. Anon. U. 14:41, 3 January 2019 (UTC)
 * Uneeded  Warnings should be given out on a case by case basis. Sometimes 3 warnings are enough and sometimes edit warring noticeboard is the way to go. I guess in certain situations, four is enough. It all depends, I believe that showing specific examples in the help pages on when to report after 3 warnings and when to go straight to a level 2, 3 or only warning would also be helpful. JC7V (talk) 22:04, 4 January 2019 (UTC)
 * Support I agree that not all of them are needed, but I think we should only go down to 3 --DannyS712 (talk) 22:09, 4 January 2019 (UTC)
 * Oppose As others have pointed out there is no requirement that you go, 1, 2, 3, 4, 4in, then AIV, although personally I would always go up like that (as long as there is a 4in) without missing any out, I would not necessarily wait until after 4in to report/block.  Crouch, Swale  ( talk ) 22:12, 4 January 2019 (UTC)
 * Oppose per WP:CREEP, in that doing so reinforces a view not supported by policy that an editor must be warned a certain number of times before blocking. Except for things like discretionary sanctions enforcement, warning a user is a courtesy, not a requirement. Ivanvector (Talk/Edits) 22:16, 4 January 2019 (UTC)
 * Unnecessary. There already is an "only warning" template. And all the others can be used to suit any situation. No requirement to go through the levels sequentially. -- &oelig; &trade; 06:26, 6 January 2019 (UTC)
 * Oppose, there is no need to go 1, 2, 3, 4 .. and all have their use, sometimes a start of 2 is good; sometimes a start of 3 is good; sometimes 2, 4; sometimes 4im. --Dirk Beetstra T  C 12:29, 6 January 2019 (UTC)
 * Oppose. mostly per Jack n Stock. it should be possible to get figures on the effectiveness or otherwise of each warning level and make changes accordingly. most of the blocks I issue are without 4 warnings, but we should look at stats on this, and remember that the current system has flexibility. But also not every newbie gets it right and some people do give vandalism warnings when they are really in an editing dispute. When they do I would rather they gave the current vandalism 1 than something stronger. Also don't forget the Visual Editor fiasco, what happens the next time some foundation mistake means that we have goodfaith newbies making edits that are indistinguishable from sneaky vandalism?  Ϣere Spiel  Chequers  12:49, 6 January 2019 (UTC)
 * Comment The number of people here who appear to oppose the idea because "they" do not use all 4 warnings actually make a very good case for supporting the proposal. If people use the existing warnings in a discretionary manner but not all 4, then surely it supports reducing to 3, which can still be used in a discretionary manner? To say "I personally don't use all 4 but I oppose reducing to three" is like saying I drink milk so I must catch the next train Leaky  Caldron  13:30, 6 January 2019 (UTC)
 * I think you misunderstand the 'I personnaly don' t use all 4 but I oppose reducing to three' thought. The way I meant it (and I think that is what most people mean here), is that sometimes I start with a 1, and then go to 3 and/or 4.  Sometimes I start with a 2, then go to immediately to 4.  The different levels are of different strength.  I hardly ever use all 4 on one user (and I don't think that it is really meant to be used like that), but I do use all 4 (better: all of them).  I do a lot of work on anti-spam, and my general order is 1-3-4 for not-too-bad-stuff, and 2-4 on bad stuff, and 4im on the really bad stuff.  XLinkBot uses (non-warning)-1-2-3-4.  With spammers it is very depending on the case: if I do a level 1, and the editor edits after that reverting my removal, then clearly this is a spammer and a next warning is a 4, if they do a next edit and stop, I don't warn further, if they spam on, likely they get a 3 or a 4 next.
 * The 4 levels (adding a self-written non-warning AGF remark for the 'sorry, we don't need that stuff here', and the 4im making 6 levels) are needed to have a more fine-grained tuning of the message you want to convey, but I do not advocate that non-bots should ALWAYS do 1-2-3-4-AIV. --Dirk Beetstra T  C 13:47, 6 January 2019 (UTC)
 * Thanks. I haven't misunderstood. I also use the available tags in many varying ways. 2. 3. 4. 1.3.4. 1.2.4. 3.4. 2.4, etc. But I see no need for 4 fixed notices. Leaky  Caldron  13:54, 6 January 2019 (UTC)
 * Comment - "Templating editors" is one of Wikipedia's rudest features. If an editor is a genuine vandal he might as well be blocked.  If an editor is making understandable mistakes (starting an article about his high school basketball team) he deserves a sympathetic message written by a genuine human being.  But even if professional patrollers feel like they need a canned message to blast at the legions of nobodies they oversee, they should at the very least not sequence these messages according to some kind of escalating-strike system of the authoritarian, but simply use the message that is right for the circumstance.  Somebody blanking an article (if not a vandal) on his first edit should be told that he really screwed up, not that his good faith edits have been reverted.  Somebody deleting whitespace for the 55th time should still get a mild message if it is unproductive, and if the templater really wants to go further he should write his own message about further measures.  Still, if an editor has to get eight such messages from eight different templaters, maybe it'll convey the message better without some admin process being invoked.  So no 1,2,3,4, but random access.  You might try renaming some of the templates so it is clearer what you're saying at people. Wnt (talk) 16:58, 6 January 2019 (UTC)


 * Oppose I've found all 4 levels useful. For egregious cases, 4IM warnings (or straight to AIV with no warning at all) is an option.  For simple "students adding stupid shit to articles", several warnings is useful (as they may not notice the first one).  For other behavior that can have warnings, there is a need for a pattern of behavior before a block would be reasonable. power~enwiki ( π,  ν ) 22:13, 6 January 2019 (UTC)


 * Support I'd reduce it to 2: "Hey, looks like you're testing things out, please stop" for good-faith screwing around (without malicious intent) and "Cut it out or we'll block you" for stuff with obvious malicious intent. -- Jayron <b style="color:#090">32</b> 02:50, 7 January 2019 (UTC)


 * Oppose as per Power~enwiki above TheMesquito  buzz  02:55, 7 January 2019 (UTC)
 * Support reducing number of warnings to 3, not only for vandalism as such, but for other types of disruption in general. Robert McClenon (talk) 03:33, 7 January 2019 (UTC)


 * Oppose – If disruption is often misconstrued as vandalism then that category shouldn't have the quickest route to reporting at a noticeboard. My routine is to start with level1, because that's the most explicit, bland, and unlikely to give a vandal the satisfaction of having provoked anyone. uw-disruption1 is my favorite catch-all message for cluing people in. I usually don't report until the fifth incident, probably because my early reporting was considered premature and I saw such a routine prescribed. That doesn't stop some of my level1 warnings being followed by indef blocks, presumably not because I'm taken seriously but because an admin undertakes their own investigation or is receiving alerts I'm not aware of. Dhtwiki (talk) 05:16, 7 January 2019 (UTC)


 * Support reducing from 4 to 3 levels. Imho, we only need "AGF", "we really don't like that" and "stop or you will be blocked". As such, most level 3 and level 4 warnings can easily be combined, e.g. uw-vandalism3 (Please stop your disruptive editing. If you continue to vandalize Wikipedia, you may be blocked from editing.) and uw-vandalism4 (You may be blocked from editing without further warning the next time you vandalize Wikipedia.) use some of the same language and could easily be merged into one warning that says Please stop your disruptive editing. You may be blocked from editing without further warning the next time you vandalize Wikipedia. The question we should consider is not really whether one has to use all levels before going to AIV but whether there is really any point in doing so. Having four warning levels only serves a real purpose if there are frequent cases where editors will stop their behavior after four warnings but not three (I don't really see that this happens that often although I'd like to see some stats on the effectiveness of each warning level). Regards So  Why  08:44, 7 January 2019 (UTC)
 * Support - Four is too many, two seems like too few, so it looks like three would be optimal. In any case, for instances of obvious vandalism, in which there is absolutely no doubt that the editor involved knew they vandalizing, I either report them immediately, if the vandalism was major, or skip Level 1 altogether if the vandalism was minor.  Even if the number of levels is decreased, we need to make it clearer -- especially to admins working AIV -- that there is no absolute necessity to work through all the levels before any action can be taken.  Too often real vandals are free to vandalize again because the admin working AIV sticks too closely to the "letter of the law" and refuses to block because insufficient warnings were given. That's harmful to the project, in my opinion, and the balance needs to be changed. Beyond My Ken (talk) 17:22, 7 January 2019 (UTC)
 * This is an extremely relevant and important point. Associated Admin. process needs to be looked at. Leaky  Caldron  17:35, 7 January 2019 (UTC)
 * Reduce to 3 at most - Per BMK and others here. ←Baseball Bugs What's up, Doc? carrots→ 17:42, 7 January 2019 (UTC)
 * Oppose, there is sometimes reason to use all four levels, and sometimes there is not. Some vandals should be blocked without warning. Others stop after slow escalation of warnings, which is the ideal result (end to disruption without a block, and perhaps with some learning on the side of the vandal). The fact the levels are there does not mean you have to use them. —Kusma (t·c) 12:56, 8 January 2019 (UTC)
 * Oppose. In some cases (many?), you really can't tell if someone needs all four levels.  How does it hurt to try?  If you have good reason to doubt that the person will listen to all four of them, then as noted by many others above, that's when you skip one or two or even three of the levels.  If the problem is that AIV reports get declined because unneeded warnings aren't being given, the solution is to remind AIV-monitoring admins of WP:BURO, not to remove options that are sometimes beneficial.  Nyttend (talk) 13:07, 8 January 2019 (UTC)


 * Oppose The user might not know that what they did is vandalism. — Eli355 ( talk  •  contribs ) 21:45, 8 January 2019 (UTC)


 * Support. One warning is enough, in areas where vandalism/trolling is rife. It's a cost-benefit balance between not biting the newbies and letting the trolls shut down a useful part of Wikipedia. -- The Anome (talk) 17:40, 12 January 2019 (UTC)


 * Oppose We have an "im" series of warning templates that can be used if one wishes, and editors can always chose to skip warning levels. funplussmart (talk) 19:05, 12 January 2019 (UTC)


 * Comment. I don't see how there can be a one-size-fits-all answer to this question. Context matters and what was said matters. Is the vandalism at least funny? Or on the other hand does it conceivably create a hostile environment for another editor? I would be tolerant of humor but less tolerant of the attempt to make others feel uncomfortable. Bus stop (talk) 21:14, 12 January 2019 (UTC)


 * Oppose for much the same reasons as many others. There is no requirement that we step through all four warnings, and that should probably be emphasized more strongly. The warnings we have now exist for different purposes. 1 is a polite notice for things that could be mistakes, 2 is neutral, 3 is a warning, and 4 is the final warning. For egregious vandalism, it's not uncommon to go straight to 3 or 4im. For less egregious cases, just a 1 or a 2 is sometimes enough to deter further vandalism. Novusuna talk 21:54, 21 January 2019 (UTC)
 * Oppose - doesn't everybody start at level 2 anyway? Level 1 has, in my experience, been restricted to the newest of new users. On the basis that we're already in effect on a 2-3-4 path rather than a 1-2-3-4 path, further shortening seems over-harsh. Cabayi (talk) 22:02, 21 January 2019 (UTC)
 * Oppose - I'll often start at level 2, generally what I'm reverting is fairly obviously unhelpful. Level 1 is useful for good faith mistakes, or things like breaking syntax, which, while maybe vandalism, could just as easily be newbie syndrome. If L2 is ignored I'll either do a 2-3-4, or just a 2-4 (if they're just redoing the vandalism without engaging is a good example). Things like inserting racism get a 4im, if any warning at all. But all the templates are useful. &#x2230; Bellezzasolo &#x2721;   Discuss  22:11, 21 January 2019 (UTC)
 * Support - My first thought was to oppose this but after reading through the comments I support reducing the number of vandalism warnings. A lot of the support reasons actually make sense. I think 4 warnings in any case is too many while 2 in some instances are not enough. 3 is a good number reminds me of baseball "three strikes and your out". Granted we don't have to start with level 1 warnings but I believe level 3 and 4 should be merged into one. In cases of WP:BLP violations I believe only 2 warnings should be used (i.e. level 1 and level 4). From my experience users who violate the WP:BLP do it on purpose and if the first warning doesn't get the message across they continue until blocked.   Alucard 16  ❯❯❯ chat?    13:55, 24 January 2019 (UTC)
 * Comment - I think there is confusion between having multiple levels of warnings and using multiple levels of warnings. In my opinion, having a range of warnings is a good thing... it gives us options (a choice) to use, whether we actually use them or not.  Which warnings to use is situational.  So... I have to oppose getting rid of the templates... but support continuing to give editors the freedom to choose which are appropriate to use in a particular case (and to skip those that are not appropriate). Blueboar (talk) 14:39, 24 January 2019 (UTC)

Proposal to protect articles related to India-Pakistan conflict
A proposal is being discussed to apply the equivalent of extended confirmed protection to any article related to conflicts between India and Pakistan. Interested editors are invited to comment on the proposal. Ivanvector (Talk/Edits) 15:54, 4 February 2019 (UTC)

Protect the reference desk from democratic closure debate
WP isn't a democracy. If you haven't been burned somehow by the ref desk, but you asked for or agreed to its closure recently, it probably wasn't none of your bloody business! Unusually, the fate of, the refdesk anyway, shouldn't be open to voting. The reference desk holds experts near the site, encourages the creation of amateur experts tied to the site, and it has been a door for new arrivals to open since forever, as well as topical educational discussion removed from the actual content and so forth etc. The vandal is delight. I am disappoint. Please protect the reference desk above our level. Unless it somehow challenges the integrity of the wider site, the refdesk should be permitted to die, when it begins to do so, without anybody who cannot withstand their own moments, and doesn't really care one way or the other anyway, being able to pull the plug. ~ R.T.G 07:43, 3 February 2019 (UTC)
 * Have you weighed in at Village pump (proposals)/Indefinitely semiprotecting the refdesk? Bus stop (talk) 08:28, 3 February 2019 (UTC)
 * Question. &, shouldn't this be moved there a new proposal?  &#8213; <em style="color:black">Matthew J. Long  -Talk-<sup style="font-size:75%">☖  21:21, 3 February 2019 (UTC)
 * I didn't think it was appropriate to discuss propriety in situ. ~ R.T.G 21:34, 3 February 2019 (UTC)


 * I think this is more of a comment than a "proposal". In that sense I agree with Mandruss and Guy Macon in their closing of this section. But I found the closing abrupt and tasteless. I find the comment interesting that "If you haven't been burned somehow by the ref desk, but you asked for or agreed to its closure recently, it probably wasn't none of your bloody business!" It sort of boggled my mind that people who don't use the Ref desks present arguments such as the one which goes "your time could be better spent building the encyclopedia". Kind of myopic, isn't it? Bus stop (talk) 21:36, 3 February 2019 (UTC)
 * It is no more of a comment than it is less of a proposal, as far as I can see. ~ R.T.G 21:42, 3 February 2019 (UTC)
 * What is the proposal—shut your cake hole if it doesn't affect you? Bus stop (talk) 21:46, 3 February 2019 (UTC)
 * Even if it is not a proposal, wouldn't this best be served in the discussion section of the main proposal? &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  21:52, 3 February 2019 (UTC)
 * Sarcasm is where you act stupid and expect others to believe it is not possible, that you can be stupid, and it would be stupid to let people shut down the ref desk, now evidenced to a powerful possibility that they might. Or maybe not...? +Exactly. 2x Must challenge. ~ R.T.G 21:54, 3 February 2019 (UTC)
 * The only reason I am asking is because I am about to close the discussion as no consensus per recommendation. I am very confused as to where sarcasm factors into anything here. &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  22:00, 3 February 2019 (UTC)
 * would you prefer this comment be made as part of that record before it is closed in case this comes up again, or would you prefer this be left open here and archived separately? &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  22:31, 3 February 2019 (UTC)
 * It is a proposal which should not be discussed alongside the closure of the reference desks, as it concerns their validity. I don't want to give an opinion there, and that's what this proposal is about. ~ R.T.G 22:41, 3 February 2019 (UTC)
 * I don't want to give an opinion about this particular thing there, but there it is, blatantly coerced, and I want to discuss the coercion outside its arena. ~ R.T.G 22:46, 3 February 2019 (UTC)
 * Wikipedia is going to categorise the world. I am trying to oppose anything which might stand in the way, before it gets hurt. ~ R.T.G 22:49, 3 February 2019 (UTC)
 * "oppose anything which might stand in the way, before it gets hurt" That reminds me of this Geico commercial. Bus stop (talk) 22:53, 3 February 2019 (UTC)
 * Commercial? ~ R.T.G 22:58, 3 February 2019 (UTC)
 * "4. (of chemicals) supplied in bulk and not of the highest purity." ~ R.T.G 23:01, 3 February 2019 (UTC)
 * Understood. Thank you for your response. &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  23:09, 3 February 2019 (UTC)
 * I'm just spinning it out for fun but I'm serious about my approach, apologies. ~ R.T.G 23:13, 3 February 2019 (UTC)
 * Don't worry! I get you. :D &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  23:24, 3 February 2019 (UTC)
 * What is the proposal here? If it's that we hereby declare the Reference Desks exempt from normal Wikipedia self-governance process, I Obviously oppose as blatant violation of basic Wikipedia principles. This thread has been closed twice by two editors including me, and re-opened twice by two editors including the OP. It still needs to be closed. &#8213; Mandruss  &#9742;  01:58, 4 February 2019 (UTC)
 * Why is the opposal obvious? Would you support a sudden vote to remove the main page and start only on random stubs? No? ~ R.T.G 02:21, 4 February 2019 (UTC)

"Quote? " ~ R.T.G 02:35, 4 February 2019 (UTC)
 * A !vote (not vote, as Wikipedia is not a democracy) to remove the main page would likely be a WP:SNOW close after less than a day. That doesn't mean that the main page needs to be protected from the process. Conversely, if there were a !vote with wide participation that the main page should go, then the main page should go. That's how things are done around here. &#8213; Mandruss  &#9742;  02:40, 4 February 2019 (UTC)
 * Possibly. Is not the concept of a reference desk much like the concept of a main page in the role it performs for the encyclopaedia? ~ R.T.G 02:44, 4 February 2019 (UTC)
 * Apparently you are not getting the point, which is: We generally don't form consensuses to protect things from the consensus process. If you wish to propose that RD removal be added to Perennial proposals, propose away, but (1) I suspect it would have difficulty passing, and (2) even if passed, it would not be the absolute protection that you seem to be proposing here. &#8213; Mandruss  &#9742;  02:59, 4 February 2019 (UTC)
 * I'm sorry, and if you delete something like the Main Page, well, that's considred vandalism. What caused this ball to roll? Also... Vandalism... So look man, if you want to discuss the nature of the refdesk, let's go. If you want to complain, about people being able to make proposals, on the /village Pump, I suspect that is a form of proposal, new you'd suspect, which should have its own section for you, every time. I think you are the one who said it sounds like, a suggested perennial proposal however. So it's an issue. As I said, I avoided getting involved with that, so I didn't read it too deeply. Could you imagine any reason the refdesks should experience more protection than say, List of frivolous political parties? ~ R.T.G 07:50, 4 February 2019 (UTC)
 * Here is what Wikipedia says, Stop talking about editors when you are deciding how to handle content, unless they have done something to vandalise, or inaccuracies, or other damages, like deleting the refdesk inappropriately. I opened this thing with a paragraph. If you read that, and want to delete it because it might stop you deleting the refdesk this evening, YOU..! I am here because I am avoiding you, apparently. Get up off the refdesk if you aren't asking it a question. It is not simply a page. You aren't deleting ANI or ARBCOM today, are you? Now your friend intersects. ~ R.T.G 08:05, 4 February 2019 (UTC)
 * You can break a guys bones when he says he needs a break but eventually the humour wears off, and then the police have to help and, it's all very messy what, apparently youse, are trying to do this last few days, about the refdesk. Has it been wearing RFC tags? Go on. You, apparently you, or whoever you are protecting me from, ~ R.T.G 08:11, 4 February 2019 (UTC)

Somewhere in another discussion, someone suggested closing the Wikipedia Reference Desk in case it might not be helping so much as responsible, for an individual sock puppetry attacker. It got votes rapid and was not especially convincingly opposed. Isn't it wise to suggest, not adding a level of protection to pages, but a level of appreciation to voluntary efforts of the Reference Desk? Or... ~ R.T.G 09:10, 4 February 2019 (UTC)

Phone number tag for edits
Recently I report to oversight a piece of vandalism that had a phone number in it. I wonder, could we make a tag for edits like "possible phone number"? Could the system recognize something that looks like a phone number? As far I can figure there is no reason to put a phone number in any article or for that matter any page. Richard-of-Earth (talk) 05:35, 6 February 2019 (UTC)

New ideas and proposals are discussed here.
PROPOSAL: At the top of this page, change "New ideas and proposals are discussed here." to "New proposals are discussed here."

I could just try a BOLD edit, but this way gets more attention and should be more durable if it passes.


 * Support as proposer. The current language blurs the line between this page and Wikipedia:Village pump (idea lab) (emphasis mine), and may contribute to misuse of this page for things that belong at VPI or elsewhere. &#8213; Mandruss  &#9742;  23:19, 1 February 2019 (UTC)
 * Question: I am not sure whether I could draw a clear line between an “idea” and a “proposal” ... could you elaborate? Blueboar (talk) 00:38, 2 February 2019 (UTC)
 * Like most everything, it's probably impossible (and unuseful) to draw a "clear line". But two things seem clear to me: (1) VPI was created for vague, unformed, blue-sky "Hey, what do y'all think about" discussions, and (2) this page is often used for same. If the usage distinction is unimportant, we can and should simplify the landscape by eliminating VPI. In any case, I'm not proposing anything more than the mere elimination of two words at the top of the page, so don't read too much into this; what editors do with that change, if anything, is a separate question. &#8213; Mandruss  &#9742;  02:03, 2 February 2019 (UTC)


 * Support. Seems reasonable enough. &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  01:41, 2 February 2019 (UTC)
 * Tentative support. If you can word a clear differentiation between the idea lab and proposals, it would make sense. As it stands, to me (a fairly new editor), I don't get the difference between the two. I follow both and can't figure out when something would be posted there versus here. (It seems logical that "idea lab" would be for tossing out an idea and gathering feedback and input, and then those ideas would be fleshed out and a version that could be implemented would be posted as a proposal.) Schazjmd (talk) 02:00, 2 February 2019 (UTC)
 * As I suggested above, I really don't want this to become a referendum on our usage of VPR and VPI. That would be worthwhile in my opinion, but it seems overly ambitious for me at this time. I'm resisting the urge to go there, or at least any further there than I already have. If editors feel the page is better with those two words, they should Oppose. &#8213; Mandruss  &#9742;  02:34, 2 February 2019 (UTC)
 * Support as proposed.--John Cline (talk) 04:44, 2 February 2019 (UTC)
 * Support as it's a simple avoidance of a possible stumble  J  947 &thinsp;(c) , at 05:10, 2 February 2019 (UTC)
 * I've ✅ the change. Galobtter (pingó mió) 06:58, 3 February 2019 (UTC)
 * Support ~ R.T.G 21:40, 3 February 2019 (UTC)

Indefinitely semiprotecting the refdesk

 * Pictogram voting wait.svg

On WP:GAB, add a section along with "Examples of bad unblock requests" that says "Avoiding common mistakes"
I think this would be useful for editors wishing to be unblocked along with the bad unblock requests because it shows what to watch out for when requesting an unblock. Examples of common mistakes that could be included may be making threats, failure to stay calm, and blaming others for their actions. Mstrojny (talk) 21:33, 14 February 2019 (UTC)

Requirement for page numbers
I hereby propose that the Wikimedia Foundation fund development of a time machine. Said time machine would be used to visit everybody in history who has ever published anything more than one page long without putting a page number on every page. The purpose of this visit will be to get them to retroactively add said page numbers, and thereby avoid the wrath and contempt of legions of future encyclopedists wishing to cite their publications as a source. -- RoySmith (talk) 16:13, 13 February 2019 (UTC)
 * m:Grants:Project/Rapid  G M G  <sup style="color:#000;font-family:Impact">talk  16:17, 13 February 2019 (UTC)


 * Do you know how to build a time machine? Vorbee (talk) 19:56, 13 February 2019 (UTC)
 * From his post it appears that Roy doesn't know how to build one, but this would be a much more useful project for the Foundation (God bless them, peace be upon them, and anything else we can say to honour them) to pursue than some of what they currently spend money on. Phil Bridger (talk) 21:34, 13 February 2019 (UTC)


 * Support, and can we get the makers of Audiobooks to include something indicating what page number of the printed book you're listing to while we're at it? ~  ONUnicorn (Talk&#124;Contribs) problem solving 21:41, 13 February 2019 (UTC)
 * Oppose We should completely abolish the use of page numbers and fully move towards the Memex/Project Xanadu reality of citations, where everything is connected to everything else in a giant web of hypertext and where every reference can natively lead to the exact part of the text used, whether it is smaller or bigger than a page, and regardless of whether the text is in a written form or not. – Uanfala (talk) 22:16, 13 February 2019 (UTC)
 * Just use, or if you're too lazy to count, – Finnusertop (talk ⋅ contribs) 08:33, 14 February 2019 (UTC)
 * You could fund some online archive (or petition an existing one) to systematically add page numbers to everything they have that needs them. Then you just need to get everybody to agree that this is the definitive page numbering for those publications. But then, a time machine might turn out to have more uses... —Kusma (t·c) 10:59, 14 February 2019 (UTC)
 * You know, I never really understood the killing baby Hitler thing, when you could just buy Gavrilo Princip lunch at a different sandwich shop, save 70 million additional people, and also not have to kill a baby.  G M G  <sup style="color:#000;font-family:Impact">talk  11:50, 14 February 2019 (UTC)

Semiprotect Drew Radovich
It's getting vandalized — Preceding unsigned comment added by Brainiac245 (talk • contribs) 19:30, 15 February 2019 (UTC)
 * Please use WP:RPP to request that a page be protected. Danski454 (talk) 19:43, 15 February 2019 (UTC)

Category:Republic of Macedonia has been nominated for discussion (over 600 subcategories)
Category:Republic of Macedonia has been nominated for renaming, along with hundreds of its subcategories. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion Thank you! &#8213; <em style="color:black">Matthew J. Long -Talk-<sup style="font-size:75%">☖  17:59, 23 February 2019 (UTC)

Datebot proposal - closed
Per request at WP:RFCL, I have closed the recent RfC proposing a "Datebot". Since the RfC was archived before closure, I'm posting the result below.

This is a proposal to increase date consistency in citations, per MOS:DATEUNIFY. Specifically, a bot would look for templates like and bring present dates in line with desired usage on that specific article.
 * Use dmy dates
 * Use mdy dates


 * There was no consensus for a bot to automatically attempt to increase the consistency of date formats within articles.

The proposal, discussion, and full close can be found at Village pump (proposals)/Archive 156

Thanks, --DannyS712 (talk) 00:16, 17 February 2019 (UTC)

Protecting large categories
We currently give pre-emptive protection to templates that have a large number of transclusions, because a single vandalism edit can damage a large number of pages. Why not categories with lots of articles included? If you place Category redirect on Cat:A, a bot will move its articles to destination Cat:B. If someone redirected an exceptionally large category, we might have thousands of pages bot-moved to the wrong place, and unlike reverting template vandalism (which requires only a single reversion per vandal edit and a wait for the job queue), someone would have to revert each of the bot category-move edits. (Catalot would simplify this, but since a category generally contains articles that belong in it, you couldn't move everything from Cat:B to Cat:A without moving pages that belonged in B.) This isn't a matter of WP:BEANS either, as Grawp's been doing such a thing for years if I remember rightly. Nyttend (talk) 00:28, 8 February 2019 (UTC)
 * I had no idea the articles were moved - should they be? I hope someone keeps an eye on Category:Wikipedia non-empty soft redirected categories (currently empty). Perhaps the bot should need an admin to activate it. Johnbod (talk) 05:36, 8 February 2019 (UTC)
 * I think the reason we don't do this is a) categories are at the bottom of the page, so not very visible and not a promising vandal target, b) if adding a template to a category is enough to make a bot move it around, you can do the same trick to reverse the move and c) I don't think that such category vandalism happens frequently. Jo-Jo Eumerus (talk, contributions) 06:28, 8 February 2019 (UTC)
 * Nyttend already explained why your suggestion in b) would not work. I'll try to explain it again. If we start with 100 articles in Cat:A and 100 in Cat:B, and Cat:A is redirected to Cat:B, then we will have no articles in Cat:A and 200 in Cat:B. Reversing the process will then give us 200 articles in Cat:A and none in Cat:B, which is not the same as the starting point. Phil Bridger (talk) 08:19, 9 February 2019 (UTC)
 * Exactly. Yes, it's not a common problem, but even with a 200-article situation, this procedure may only be undone by spending quite silly amounts of time (to quote WP:HISTMERGE out of context).  Lots of categories have far more than this; consider redirecting Category:American Freemasons to Category:American amputees, and you'd have 585 articles to sort through.  (It would be even worse if there are amputee Freemasons, since the old category would simply be removed from the article and you'd have no indication that the article was previously in both.)  And that assumes you've only redirected one category; take several massive categories and redirect them all to the same place, and you might end up with ten thousand articles in the same category.  With a couple of minutes' search, I just identified ten completely unprotected categories containing over 150,000 articles total, and I know that these categories are added directly in the article (as opposed to being template-transcluded) and that there's very low risk of duplication.  The chance that this specific incident will occur is small, for sure, but should it occur, the risk is great enough that we need to do something about it — either protect these categories or amend the bot's workings, e.g. it only runs if the person who redirected the category is autoconfirmed.  Nyttend (talk) 00:08, 12 February 2019 (UTC)
 * FYI, the bot has a seven-day waiting period after a category redirect is created before it will start moving anything out of the redirected category. That does allow an opportunity for interested users to monitor newly-created redirects and revert any vandalism before a problem occurs. But, like much else on Wikipedia, it does require vigilance.  --R'n'B (call me Russ) 00:44, 12 February 2019 (UTC)
 * I asked R'n'B to come here because he runs the bot (or one of the bots) in question, User:RussBot. Nyttend (talk) 01:17, 12 February 2019 (UTC)
 * Would it be easier to just create an edit filter for redirecting categories? --DannyS712 (talk) 01:28, 12 February 2019 (UTC)
 * Maybe, or you could have the existing new-redirect filter look at category edits too. But I'm still concerned that this and the current 7-day delay wouldn't be enough, since not many people pay attention to specific categories or filters of this sort.  I'd rather see the bot pay attention to an editor's standing, or semiprotect pages, or something else.  Building on Johnbod's idea: what if the bot would run only when a fully-protected page was marked as "yes"?  Either it could run on all the non-empty redirects at once, or we could have a way to tell it to run only on some of them.  Nyttend (talk) 01:48, 12 February 2019 (UTC)

I think the correct solution is to create a filter to watch for redirecting existing categories, and for users to create pages with links to and keep an eye on the "related changes" link on that page (e.g this page). These measures, along with a 1 week delay, should be enough to prevent the cateories from being merged in this way. עוד מישהו Od Mishehu 12:54, 18 February 2019 (UTC)

Advanced futures and parameters of the search engine exported to the Wikipedia mobile version
At February 2019, the advanced search features are available only for the Desktop version of Wikipedia. They automatically disappear, while switching to the mobile view, which is linked at the end of each page.

Why don't you extend and make them available for the mobile view, that probably is more used than the Desktop one?? — Preceding unsigned comment added by 84.223.68.157 (talk) 18:39, 22 February 2019 (UTC)