Jump to content

User talk:Wugapodes/Archive 14

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 10←Archive 12Archive 13Archive 14Archive 15Archive 16→Archive 20

Tech News: 2020-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • The Starter kit is now available for wiki communities. This page lists technical resources, tools, and recommendations. These are essential to operate a wiki project. This is mostly useful for smaller wikis where the community has limited experience with this. [1]
  • The first features of the Desktop Improvements project are available for logged-in users on all wikis. In order to use them, uncheck Use Legacy Vector in your local or global preferences in section Skin preferences. More improvements are planned. Feedback is welcome.
  • Advanced item On multiple wikis, a UTCLiveClock gadget is available. For wikis that import the gadget directly from mediawiki.org, end users can now choose a different timezone to show instead of UTC.

Problems

  • Advanced item The deployment train for MediaWiki has been blocked this week. [2][3]
  • Translation Notification Bot was sending the same message multiple times to every translator. This has been fixed. [4]
  • Some users were receiving the same notification multiple times. This has been fixed. [5]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from July 28. It will be on non-Wikipedia wikis and some Wikipedias from July 29. It will be on all wikis from JUly 30 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

13:53, 27 July 2020 (UTC)

Interactive graph

Greetings Wugapodes, I have been trying to make an interactive map of covid cases similar to Template:Interactive COVID-19 maps/Cumulative confirmed cases. I am not getting it to work, don't know where it goes wrong? Since you made the mentioned one, I'm asking you this. If you get a free time, can you have a look at this? I get "TypeError: undefined has no properties" when I preview it at mw:Special:GraphSandbox. (Links for dependent sub-pages.) Thanks - Timbaaa -> ping me 15:50, 27 July 2020 (UTC)

I've done some debugging and threw the results up at User:Timbaaa/sandbox/6/wugapodes. You can see the difference between that one and yours at Special:Diff/969815756/970375160 Some notes:
  • The main issue was your map json. Essentially, the graphing software was looking for data fields that didn't exist. I downloaded a fresh json file for Indian states and added the needed fields which you can see in the history at User:Timbaaa/sandbox/6/wugapodes/India Map Data.json. There are some differences between it and your data, so you may want to take a closer look at it.
  • For similar reasons, there were some issues in the mouse-over and hover text code which prevented region name display and case count display. There's debug code which displays that info, and it shouldn't be hard to rework it for your desired style and placement.
  • Your data are weekly updates instead of daily, so for days without data the map bugs out. You'll need to figure out some way to get around this. The two main strategies are to modify your input data format or to modify the graph scale:
  1. Modifying the input data requires automatically adding the needed fields on every update (see the data backend for an example) which is a fair bit of overhead, but modifying the graph code will be easier.
  2. Modifying the scale minimizes overhead since you don't need to do your own data ingest, but the graphing library may not be able to do exactly what you want. If it can be done, it will require some ingenuity, so it will be a lot harder to do at first (if it can be done at all) but will minimize maintenance requirements down the line. Personally I would not recommend this option.
  • I added scale and offset parameters to the map data. You can toy around with positioning of the map by modifying those. I got it pretty big and centered, but you may need to tweak them later on depending on any changes you make.
I'm a little busy with meatspace work at the moment, so I'm sorry I couldn't help more. Ideally we could write a little tutorial on how to do country-specific graphs based on your experiences so let me know how it all goes. The interactive parts of the graph extension are not well documented, so I think that write-up would be a useful supplement to the interactive graph tutorial. If you run into more problems, feel free to get in touch. — Wug·a·po·des​ 23:16, 30 July 2020 (UTC)
Wugapodes, Thanks for taking your time to work it out and for the detailed explanation. I'll tweak around.
I am just starting to get the hang of Vega. If I hit any roadblock(or hopefully once I get what is required), I shall contact you.
One question,
Since the mark.debugmouseposition.update uses text from csv, is there a particular need for geometries.[].properties fields in map json? I'm in no hurry, reply at your convenience. - Timbaaa -> ping me 02:15, 31 July 2020 (UTC)
Wugapodes, Got the required working version. I thick they can be moved to template namespace(without leaving redirect), where I shall parameterize it.

Administrators' newsletter – August 2020

News and updates for administrators from the past month (July 2020).

Administrator changes

added Red Phoenix
readded Euryalus • SQL
removed Jujutacular • Monty845 • Rettetast • Madchester

Oversight changes

readded GB fan
removed Keegan • Opabinia regalis • Premeditated Chaos

Guideline and policy news

Sent by MediaWiki message delivery (talk) 08:21, 1 August 2020 (UTC)

The Signpost: 2 August 2020

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 18:26, 2 August 2020 (UTC)

Tech News: 2020-32

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • All queries to the Wikidata Query Service failed between 17:50 and 17:59 UTC on Thursday 23 July. Some queries failed during a longer period. [6]
  • Interlanguage links were ordered incorrectly for the past few weeks. This problem was also mentioned in Tech News two weeks ago. The problem is now fixed. [7]
  • There is a problem with the global preferences for the "Use Legacy Vector" option. Developers are working on fixing it. [8]
  • A bug in the Wikibase extension had disabled the "move" and "create" types of protection in the main (Gallery) namespace on Wikimedia Commons. New protections could not be added, and existing protections were not enforced, allowing some page moves and page creations that should not have been possible. This has now been fixed. [9]

Changes later this week

  • The video player will change to be simpler and more modern. This week, the current beta feature will become the video player for everyone on most non-Wikipedia wikis. The old player will be removed. [10]
  • Users' global.js and global.css pages will now also be loaded on the mobile site. You can read documentation for how to avoid applying styles to the mobile skin. [11]
  • Advanced item In the MonoBook skin, the searchGoButton identifier is now searchButton. This may affect CSS and JS gadgets. Migration instructions can be found in T255953. This was previously mentioned in issue 27.
  • Advanced item Bot operators can use Pywikibot to regularly archive discussions. The behavior when the bot uses counter to prevent large archives was changed. [12]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from August 4. It will be on non-Wikipedia wikis and some Wikipedias from August 5. It will be on all wikis from August 6 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:43, 3 August 2020 (UTC)

COVID Editnotice

Hi Wugapodes. I noticed your comment above that you're a bit busy right now; my query is low priority, no hurry on this. Just wanted your thoughts on a matter I came across whilst doing overhauls of the Template:Gs system, whenever you have spare time and can get around to it.

Regarding {{COVID19 GS editnotice}}, which was created in response to this request back in March, and ref this, my understanding of edit notices for DS is that they follow ArbCom's procedure on page-level restrictions: if there are page restrictions (either for a whole topic, or for a single article) that an editnotice is required (alongside a talk notice) to meet the sanctioning requirements. The COVID GS doesn't authorise 1RR or other page-level restrictions, instead solely standard discretionary sanctions, whose awareness procedure doesn't require an editnotice. The COVID GS would seem like an anomaly here, as it's the only DS or GS with an active editnotice without any page-level sanctions on the topic.

If my understanding here is correct, would it be okay to delete this editnotice? There are a small number of pages like Coronavirus disease 2019 which have custom page-level sanctions, so would continue to require some form of custom editnotice. Aside from principle/consistency, my bigger concern is that a big red editnotice on articles isn't great for encouraging newer editors to participate (COVID EN reads harsher than the ArbCom DS editnotices imv), so if not required by the bureaucratic powers that be (ie the awareness rules) I was hoping it'd be possible to get this one deleted?

Thank you. ProcrastinatingReader (talk) 00:42, 31 July 2020 (UTC)

Everything that followed - mass editnotice tagging of COVID pages - seems to just be a misunderstanding of the system. The discussion here misinterpreted the editnotice requirement of Administrators should add an editnotice and talk page notice on restricted pages. Editors who ignore or breach page restrictions may be sanctioned by any uninvolved administrator only if the editor was warned about this decision and an editnotice describing the page restriction was placed on the restricted page., resulting in a few editnotices for pages without page-level sanctions. Following that, some editors mass-created COVID editnotices, to the point where about 200 pages are now tagged with them. Somewhat delayed to request deletion now, but they do appear to be improper, and anything that unnecessarily discourages participation should be scrapped imo. ProcrastinatingReader (talk) 01:04, 31 July 2020 (UTC)
@ProcrastinatingReader: That template's used on about 160 pages, which is mainly why I would not recommend deleting it. My understanding of WP:GS/COVID19 is that it allows page restrictions like any other DS/GS topic area, sysops have just preferred page protection (which is a page-level sanction) and individual sanctions. If you want to usurp the title and move the template and point its transclusions there, that's fine, but the COVID editnotice serves a purpose on the pages that use it.
As a bit of an aside, I think your understanding of the general sanctions is too rigid. The point was to give community support to administrators strongly enforcing WP:V and WP:MEDRS without having to invent a connection to the Pseudoscience ArbCom sanctions. The specifics have about as much consensus behind them as a guideline. Actually following them strictly isn't even really possible: a warning about COVID GS requires the editor be "linked to this decision", but there is no decision since it wasn't an ArbCom case. The COVID general sanctions are like the Affordable Care Act: hastily drafted and pretty much only comprehensible if you ignore what words mean.
So unlike ArbCom-created discretionary sanctions, COVID general sanctions is one of the cases where practice dictates policy, rather than policy dictating practice. Given that the template is used so widely, I think this is a question of policy, not technically a template. My understanding is that the COVID GS editnotice is sufficient warning, and the template seems to be used to warn editors that failure to comply with MEDRS will result in them being sanctioned. While that may scare people, we're first and foremost an encyclopedia. Biomedical information is a topic where we have a duty to our readers to ensure the information is correct, even if it means a slow or restrictive editorial process. — Wug·a·po·des​ 02:03, 31 July 2020 (UTC)
Given that, especially my understanding is that the COVID GS editnotice is sufficient warning, and the template seems to be used to warn editors that failure to comply with MEDRS will result in them being sanctioned, do you mean that for COVID the editnotice is treat as the 'awareness' for sanctions, and so {{Gs/alert}} is unneeded to sanction an editor? ProcrastinatingReader (talk) 06:44, 31 July 2020 (UTC)
@ProcrastinatingReader: That's my understanding, yes. The COVID GS text just says editors must be given a warning, not {{Gs/alert}} particularly (though it's preferred I'd bet). If an editor is repeatedly not complying with MEDRS on a page tagged with {{COVID19 GS editnotice}} they can be sanctioned under the COVID GS regardless of whether they have received a Gs/alert template. The only exception I can think of is when the editor is on mobile, since editnotices don't display on mobile devices. This is just my perspective, so if you're going to rely on this, you may want to post at WP:AN or WT:GS/COVID19 to get wider opinions. — Wug·a·po·des​ 18:51, 3 August 2020 (UTC)
Appreciate your thoughts. I think I've spoken to over half a dozen subject admins, and read a bunch of archives, whilst revamping {{Gs}} to try understand the system better to clear up some ambiguities in the templates, but some areas just seem fundamentally hazy. For ArbCom's system, this motion was passed in 2018 to clear it up, but of course that doesn't automatically apply to the GS system (as acknowledged in the discussion). Most GS' seem to authorise "standard discretionary sanctions" so I'd think that they align with ArbCom's full procedures on the matter, including updates, and most (but not all) admins I spoke to seem to agree those awareness procedures apply, but I can't see any formal discussion to say that they should be aligned. I guess to clear it up the best course of action would be to ask at WP:AN, but I don't know whether clarity is a good idea or if it'd just either reduce admin ability to clean up COVID-related disruption just for the sake of principle, or perhaps make the system more broad, depending on which way consensus swings. Maybe it's best to just let it be, until someone feels wronged by current practices and wishes to raise the point themselves. ProcrastinatingReader (talk) 20:28, 3 August 2020 (UTC)
There's a lot to unpack here, and I don't have a ton of time at the moment, but as I've looked into this more, I think I may be wrong. The two most recent GS regimes, WP:GS/COVID and WP:GS/MJ, seem to be anomalies compared to the other GS pages. Those two use "warn" instead of "aware" and do not explicitly require the use of {{gs/alert}}. There's also some discrepancy among other regimes about whether {{gs/alert}} is a should or a must. I'll post at AN about this. — Wug·a·po·des​ 21:47, 3 August 2020 (UTC)
I believe both the sanctions use the terminology "standard discretionary sanctions" intentionally so that the structure remains similar to WP:AC/DS, hence making alerts (or "warnings" on talk pages basically) compulsory. I am probably at some fault here because I wrote GS/MJ, which is also what GS/COVID19 is modeled after. In any case, I think it's in the best interest of editors involved that alerts be required, also keeping GS more in line with acceptable practices. Noting that the sanction itself states Editors ... may be sanctioned by any uninvolved administrator only if the editor was warned about this decision and an editnotice describing the page restriction was placed on the restricted page." (emphasis mine), implying that an editnotice is distinct from a warning. For the sake of transparency, just adding that PR raised this question on IRC and I responded, but since I have your talk page on my watchlist, I'd have come here to clarify anyway. --qedk (t 愛 c) 22:02, 3 August 2020 (UTC)
Yeah, I definitely think consistent is better, but it's not just these pages. In my AN post I point out that GS/IRANPOL and GS/Wrestling differ on whether notification is "should" or "must", and while WP:GS and WP:AC/DS refer to this as "awareness" all four of those pages use "warn" instead of alert which is annoyingly vague. I don't disagree that you can read the text as requiring a warning distinct from an edit notice, and I'd even agree that consensus is likely in favor of requiring. If only to deprive disruptive editors of a chance to wikilawyer, getting firm clarification on these inconsistencies will be a net positive. Odds are it will be snow closed in a few days and then someone can replace the text with a consistent boilerplate. — Wug·a·po·des​ 22:20, 3 August 2020 (UTC)
I'll take it, for the clarification, but honestly when I said "maybe it's best to just let it be, until someone feels wronged by current practices and wishes to raise the point themselves" I wasn't being sarcastic (and I was honestly going to drop this issue here - my IRC query was back on the 31st). After your latest response I was starting to lean towards the idea that GS being able to diverge from ArbCom's requirements is a pro, not a con. Consensus may well be in favour of requiring due to the broadness of sanctions, but if we're being honest, if tightened up this change might allow more problematic edits through on COVID as well. Not sure wikilawyering would've mattered, since I don't think too many questioned or cared about the inconsistencies/ambiguities in GS; DS instead gets the spotlight it seems. Either way, if we're going for clarification we might as well decide if GS should remain aligned with amendments to DS by default, so an ambiguity doesn't arise again in a year, or result in the need for legalese 'motions' to be passed at AN periodically. ProcrastinatingReader (talk) 22:44, 3 August 2020 (UTC)

Summer greetings

July
pale globe-thistle above the Rhine

... with thanks for what you do! --Gerda Arendt (talk) 17:19, 31 July 2020 (UTC)

Thank you Gerda Arendt and for your work as well! I hope you're having a good summer. Have you read this month's Signpost? There's a research report on how the "thank" button increases editor retention that QAI members might find interesting. — Wug·a·po·des​ 00:18, 4 August 2020 (UTC)

Sarbashis Kumar Paul

Can you pull email access from User:Sarbashis Kumar Paul? I got an unsolicited email from him whining for an unblock. I can't think of how he would have picked me in particular, so I assume he's just randomly emailing every established user he comes across. Jackmcbarn (talk) 05:50, 9 August 2020 (UTC)

Kiki Camarena

Hi Wugapodes. Could you reassess the need for partial protection at Kiki Camarena (edit | talk | history | protect | delete | links | watch | logs | views)? There's almost certainly sock/meatpuppetry going on. The dynamic ip's edit-warring there appear to be only two people, one of which appears to be a logged out editor who'd be otherwise blocked if these edits were coming from his/her account. Talk:Kiki_Camarena#stop_deleting/adding_material_under_discussion_to_the_article, related discussion. --Hipal/Ronz (talk) 16:01, 9 August 2020 (UTC)

Tech News: 2020-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • FileImporter and FileExporter became standard features on all Wikis during the first week of August. They help you transfer files from local wikis to Wikimedia Commons with the original file information and history intact. [13]

Problems

  • The mobile skin displays a message at the bottom of the page about who edited last. This message showed raw wikitext. This has now been fixed. Some messages in Structured Discussions and content translation may still appear as raw wikitext. Developers are working on it. [14]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from August 11. It will be on non-Wikipedia wikis and some Wikipedias from August 12. It will be on all wikis from August 13 (calendar).

Future changes

  • All wikis will be read-only for a few minutes on September 1. This is planned between 13:30 and 15:30 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [15][16]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:06, 10 August 2020 (UTC)

Draft:Gaza Sky Geeks

Hi. I may be misinterpreting your actions, but it looks like you restored all revisions of this page after I'd made a point of only restoring the oldest ones (because everything since then is promotional). Now the draft looks the same as it did when it was nominated for G11 a few days ago. I was wondering what the rationale was? Deb (talk) 08:59, 12 August 2020 (UTC)

After hunting around for a while, I found how this user managed to get around you. Please could you check next time? Deb (talk) 09:09, 12 August 2020 (UTC)
@Deb: I didn't realize it was a recent G11 which is my fault. I thought the wrong version had gotten restored, and it just needed a history merge. Sorry about that, do you want me to revert? — Wug·a·po·des​ 19:07, 12 August 2020 (UTC)
No, it's okay, I can see that he didn't quite level with you. I've made changes to the draft version and we'll see how it all pans out. Deb (talk) 19:08, 12 August 2020 (UTC)

Tech News: 2020-34

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • If you revert an edit using the undo link your edit is marked with an undo tag. This will now only happen if you don't change anything in the edit window before publishing the undo. This is to keep users from marking edits as undos when they actually do something else. [17]
  • The new OOUI version will not work with Internet Explorer 8. This means the wikis will look strange and not work well in Internet Explorer 8. This was reported in Tech/News/2020/17. This is because keeping the wikis working with very old browsers creates other problems. [18]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 August. It will be on non-Wikipedia wikis and some Wikipedias from 19 August. It will be on all wikis from 20 August (calendar).

Future changes

  • All wikis will be read-only for a few minutes on September 1. This is planned between 13:30 and 15:30 UTC. More information will be published in Tech News and will also be posted on individual wikis next week. This is a reminder. You can help by translating the announcement message. [19][20]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:40, 17 August 2020 (UTC)

Humid Subtropical Climate

Thank you for your help on this! Based on this articles' history, we will likely have to seek an "IP Block" for the article G. Capo (talk) 20:47, 17 August 2020 (UTC)

@G. Capo: No problem. I applied semi-protection which prevents edits from IP editors and registered editors with fewer than 10 edits and 4 days tenure. That will last until the 23rd, and hopefully it resolves the problem. If not let me or another administrator know and we can make the protection last longer. — Wug·a·po·des​ 22:39, 17 August 2020 (UTC)

Tech News: 2020-35

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 August. It will be on non-Wikipedia wikis and some Wikipedias from 26 August. It will be on all wikis from 27 August (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:59, 24 August 2020 (UTC)

Move

I saw this answer you gave. I'm one of the participants in that dispute. I think those asking for the "temporary" location are asking because a "no consensus" result of a page move discussion will automatically favor their chosen name. While discussions should be closed based on policy and not number of votes, I feel this is not always the case (I went through Category:Closed move reviews and found some examples to the contrary). Worse yet, this particular discussion on article name change appears to have attracted two sockpuppets in the last two weeks alone. I would like to request name change under WP:RMCM, is there any way to ensure the closer focuses purely on the strength of arguments made and disregards the number of votes for each side? VR talk 01:57, 26 August 2020 (UTC)

@Vice regent: Oh, I definitely understand why people care about the temporary name. Since it's just a proxy fight for the larger problem, it's better (and clearer) to just address the big problem. Maybe wishful thinking, but sometimes it helps to just point out the central conflict. As for closing a move discussion, move reviews probably aren't a representative sample as the vast majority are closed well, but I can understand the concern. I actually trust closers of move reviews more than a lot of other areas of the project, so I don't see a bad close as particularly likely. If you're still worried, I would be willing to volunteer as a closer if it sets minds at ease or recommend another editor if need be. It may take some time, but WP:RM really is the best course because it will bring in outside editors who will be able to break the stalemate. — Wug·a·po·des​ 05:26, 26 August 2020 (UTC)
Thanks, it would be great if you could close it! I started the request here Talk:Sexual_slavery_in_Islam#Requested_move_30_August_2020.VR talk 16:56, 30 August 2020 (UTC)

The Signpost: 30 August 2020

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 17:33, 30 August 2020 (UTC)

Tech News: 2020-36

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • This is a reminder. All wikis will be read-only for a few minutes on September 1. This is planned between 14:00 and 15:00 UTC. Please check on the details on the announcement message. [21][22]

Changes later this week

  • There is no new MediaWiki version this week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:08, 31 August 2020 (UTC)

WikiCup 2020 September newsletter

The fourth round of the competition has finished, with 865 points being required to qualify for the final round, nearly twice as many points as last year. It was a hotly competitive round with two contestants with 598 and 605 points being eliminated, and all but two of the contestants who reached the final round having achieved an FA during the round. The highest scorers were

  • Free Hong Kong Bloom6132, with 1478 points gained mainly from 5 featured lists, 12 DYKs and 63 in the news items;
  • IndonesiaHaEr48 with 1318 points gained mainly from 2 featured articles, 5 good articles and 8 DYKs;
  • England Lee Vilenski with 1201 points mainly gained from 2 featured articles and 10 good articles.

Between them, contestants achieved 14 featured articles, 14 featured lists, 2 featured pictures, 87 good articles, 90 DYK entries, 75 ITN entries, 95 featured article candidate reviews and 81 good article reviews. Congratulations to all who participated! It was a generally high-scoring and productive round and I think we can expect a highly competitive finish to the competition.

Remember that any content promoted after the end of round 4 but before the start of round 5 can be claimed in round 5. Remember too that you must claim your points within 10 days of "earning" them. If you are concerned that your nomination will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews. It would be helpful if this list could be cleared of any items no longer relevant. If you want to help out with the WikiCup, please do your bit to keep down the review backlogs! Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages or by email. If you wish to start or stop receiving this newsletter, please feel free to add or remove yourself from Wikipedia:WikiCup/Newsletter/Send. Godot13 (talk), Sturmvogel 66 (talk), Vanamonde (talk), Cwmhiraeth (talk) MediaWiki message delivery (talk) 19:53, 1 September 2020 (UTC)

September

September
Dahlias in Walsdorf

I like today's Main page, with the TFA (thank you for your FAC comments!) on the anniversary day (of both dedication and our concert), a DYK, and a great photographer who didn't make it soon enough, Jürgen Schadeberg, - more on my talk, mostly about the tribute to Brian who shared his sources. --Gerda Arendt (talk) 20:42, 1 September 2020 (UTC)

Administrators' newsletter – September 2020

News and updates for administrators from the past month (August 2020).

Administrator changes

added Eddie891
removed Angela • Jcw69 • Just Chilling • Philg88 • Viajero

CheckUser changes

readded SQL

Guideline and policy news

Arbitration

Sent by MediaWiki message delivery (talk) 09:57, 2 September 2020 (UTC)

August

August
Sunflowers in Walsdorf

A first for me today: a featured list (= a featured topic in this case) on the Main page, see Wikipedia:Main Page history/2020 August 21, an initiative by Aza24 in memory of Brian. --Gerda Arendt (talk) 19:26, 21 August 2020 (UTC)

Rhythm Is It! - I expanded that stub on my dad's birthday because we saw the film together back then, and were impressed. As a ref said: every educator should see it. Don't miss the trailer, for a starter. - A welcome chance to present yet another article by Brian on the Main page, Le Sacre du printemps. --Gerda Arendt (talk) 14:07, 31 August 2020 (UTC)

@Gerda Arendt: I'll have to give it a watch! I don't know much about classical music, but the story reminds me of Britten's opera Noye's Fludde which he wrote in a way that was suitable for amateurs performing outside of opera houses. Thanks for your work on these and for sharing them! — Wug·a·po·des​ 22:08, 4 September 2020 (UTC)

Tech News: 2020-37

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Normally pages can be moved to a title that has no existing page yet or to a page that has only one revision, which is a redirect to the page to be moved. A new user right allows editors to move pages over one-revision pages that redirect to anywhere. [23]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 September. It will be on non-Wikipedia wikis and some Wikipedias from 9 September. It will be on all wikis from 10 September (calendar).
  • Advanced item All MediaWiki API modules will now use watchlist instead of watch. This was inconsistent before. [24]

Future changes

  • The Wikipedia Android app team might work on patrolling tools in the future. You can let them know what tools would be useful for you or for less experienced patrollers. See the page on mediawiki.org.
  • OTRS will be updated to a new version. This will probably take around two days. OTRS agents will not have access to the system during these days. Emails that come in during the update will be delivered when the update is done. The plan is to start around 08:00 UTC on 14 September. This could change. [25]
  • The Wikipedia Android app will send push notifications if users want them. This could help you see for example when someone wrote on your talk page or your edit was reverted. This will need Google Play Services to work. It will also be possible to get the app without Google Play Services but push notifications will not work. Google Play Services is also used to make the app work for Android 4.4 users. [26][27]
  • Advanced item Wikimedia code review could move to GitLab. It would be hosted on Wikimedia servers. You can take part in the consultation.
  • Advanced item Dropdown menus in the Vector skin use a .menu class. This will not work in the future. Scripts can use nav ul instead. .vectorTabs and .vectorMenu will also not work. Some scripts need to be updated. You can read more in Phabricator.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:59, 7 September 2020 (UTC)

Move closure

Continuation of this conversation. The page move seems to have been closed by a non-admin who did not cite any policy and seems only to have counted votes. The closure also happened in the middle of a discussion (less than 1 hour between the last comment and the closure).

Not counting IP votes, there seem to have been 7 votes for "Concubinage in Islam" and 8 votes against it. Of the votes against it:

Given such a contested debate I would have expected the closer to given a detailed rationale for their decision. Please let me know your thoughts.VR talk 16:14, 8 September 2020 (UTC)

@Vice regent: My impression reading through the discussion was that there was no consensus. While move discussions can be closed at any point after 7 days, this one might have benefited from more discussion. Regardless the best way to get clarity is to ask the closer themself. @Vpab15: thanks for taking the time to close the discussion. Would you be able to provide a closing rationale and explain why you decided to close instead of relist? — Wug·a·po·des​ 21:10, 8 September 2020 (UTC)
Sure. I didn't think it would be possible to reach a consensus in that discussion even if it was relisted. There were some good arguments on both sides, so no consensus was the right outcome in my opinion. Vpab15 (talk) 21:54, 8 September 2020 (UTC)
@Wugapodes: Thanks for the response. When you say "no consensus" is that based simply on the number of votes or the grounding of arguments in wiki policy? From my reading of the discussion, those arguing in favor of "sexual slavery" as a WP:COMMONNAME failed to provide WP:Reliable sources in support. I would think discussions should not be judged on number of votes but based on which arguments are in accordance with policy.
@Vpab15: Thanks for the response. Did you feel those favoring the title "sexual slavery" provided WP:Reliable sources that used that name? If so, could you point to that? Additionally, your closure was made a mere 32 mins after the last comment, do you think more time should have been allowed? VR talk 22:08, 8 September 2020 (UTC)
A lot of the sources mention slavery in the title itself. They do mention concubinage too, but some users argued that term could cause confusion and sexual slavery is more recognisable and better meets WP:CRITERIA. I don't think more time would have changed the consensus.
I don't think the first paragraph of your comment is addressed to me, but I did not just count the votes and also looked at the policy arguments, mainly WP:CRITERIA. Vpab15 (talk) 22:38, 8 September 2020 (UTC)
@Vpab15: sure, but were there any sources that mention "sexual slavery"? Would you agree that no such WP:Reliable sources were provided, while at least 35 reliable sources were provided that mention "concubine" (including many in the title itself)? Were there any WP:RS provided that would indicate that "sexual slavery" is more recognisable? VR talk 22:52, 8 September 2020 (UTC)

Sorry, I do not really have anything else to say apart from what I already said. Since the result is no consensus, you can resubmit a request move, ideally no earlier than in three months. Vpab15 (talk) 23:17, 8 September 2020 (UTC)

Tech News: 2020-38

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • The Wikipedia apps briefly showed pages without CSS last week. This meant they looked wrong. It was quickly fixed but cached pages without CSS were shown for a few hours. [28][29]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 September. It will be on non-Wikipedia wikis and some Wikipedias from 16 September. It will be on all wikis from 17 September (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:18, 14 September 2020 (UTC)

Your opinion requested

I know you've been away for a few days, which ironically is the reason for this post (since you might not see a ping) but a comment you made at a phab ticket has resulted in me throwing myself under a bus in this discussion and your input upon your return would be greatly appreciated. Primefac (talk) 15:24, 13 September 2020 (UTC)

@Primefac: Sorry about that; today is the start of our term, so I've been busy the last few days. I've left a comment that hopefully clarifies my intent. I think a lot of AC editors would find the tool useful, but the current level of logging makes it difficult to limit damage. — Wug·a·po·des​ 19:31, 14 September 2020 (UTC)

RFA Poll

Would you please consider reversing the immediate closure of my RFA Poll? There was no opportunity for other admins to provide feedback, and I've already read the instructions and essay that you may have been pointing me to. Please understand that I am in a unique situation, and I am genuinely in need of feedback both positive and negative at this time. -- Sleyece (talk) 00:24, 16 September 2020 (UTC)

Hi Sleyece, I don't think that would be a good idea. First, ORCP is for editors who intend to run for RfA in the near future, and your initial statement made clear that you had no imminent plan to request adminship. Second, ORCP is not for editors seeking general feedback; the second line of the page reads This page is not intended to provide general reviews of editors. To seek feedback on what you can do to improve your contributions to Wikipedia, ask a friendly, experienced editor on the editor's talk page for help. I would recommend you go that route instead of reopening the ORCP thread. Third, giving good feedback takes time, and editors at ORCP are unlikely to invest significant time into an out-of-scope thread.
If you'd like I could look into your contributions and give feedback, recommend some friendly editors who you could reach out to, or both; let me know. So that I (and others) can give useful advice, are there any specific areas or topics you want feedback on? You mention in the ORCP statement that you're looking for a better fit in the community, what have you tried and how did it go? Best — Wug·a·po·des​ 04:03, 16 September 2020 (UTC)
That's okay, I already know some editors that I should reach out to from here. Thank you for this explanation. I completely understand now why you closed the thread early, and I respect that decision. -- Sleyece (talk) 09:27, 16 September 2020 (UTC)

Thank you so much! :)

It all worked out. One minor permission, in case of the sign can I use QuantumRealm instead of QuantumUniverse? As QuantumRealm was my first preference and there is no one else editing with that username so it shouldn't create conflict. Thank you soo soo much for taking the time to help me out. QuantumRealm (meow • telescope) 15:51, 19 September 2020 (UTC)

Also, it has been twice that I changed my username, I noticed when I changed from Angus1986 to AngusMEOW a lot of my green AfD votes were taken away, and now again, all the votes that I cast at AfD(non-nominated ones are missing), is there a way to fix this? [30].

@QuantumUniverse: your signature should have your username. If you still want QuantumRealm you can request that account be renamed so you can take the name. It's called usurpation and you can find info at Wikipedia:Changing username/Usurpations. I don't know much about that process, but the renamers I know are very helpful so I trust you'll be pointed in the right direction. — Wug·a·po·des​ 21:14, 19 September 2020 (UTC)

Minor changes to DYK checklist template

Wugapodes, neither of these should affect your bot, but I made a change to the underlying module that includes the "hookinterest" parameter in one of the checks (it had listed "hookcited" twice, and now lists it once and "hookinterest" once), and I made a change to the DYK checklist template documentation, which, since it's inside a comment line, shouldn't affect anything. If you see any issues, let me know, but I don't expect there to be any. Thanks. BlueMoonset (talk) 06:36, 21 September 2020 (UTC)

Tech News: 2020-39

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • There is a new tag for reverted edits. For example you can see it in the recent changes feed or in the article history. It is added to edits when they have been undone, rollbacked or manually reverted to an older version of the page. [31][32]

Changes later this week

  • The number of times you can do something in a period of time on wiki is limited. This could be the number of edits per minute or the number of users you email in a day. Some users are not affected by all limits because of their user rights. They could soon see the limit even if it does not affect them. [33]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 September. It will be on non-Wikipedia wikis and some Wikipedias from 23 September. It will be on all wikis from 24 September (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:26, 21 September 2020 (UTC)

Category:Outlines of human activities has been nominated for renaming

Category:Outlines of human activities has been nominated for renaming. 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 page. Thank you. —⁠andrybak (talk) 19:50, 22 September 2020 (UTC)

Linguists' portraits

Hello: I happened to notice the favorable mention on your user page of Sebeok's Portrait of Linguists. If you already have a copy, read no further. If you don't: I don't have a copy, have never seen one, and have little shelf space; but I notice that it's titled Portraits, plural; and that Abebooks currently offers a cheap new copy of mistitled Portrait among all the horribly expensive copies of correctly titled Portraits. HTH! -- Hoary (talk) 08:47, 25 September 2020 (UTC)

Kyiv close

I noticed your close/move on Kyiv made some news, e.g. Kyiv Post, and Unian. I'll put something into next week's Signpost and probably quote the close. You can also send me any comments, if you'd like to via email.

Thanks.

Smallbones(smalltalk) 15:42, 18 September 2020 (UTC)

@Smallbones: Cool! I think the close stands on its own, but I'd encourage quoting some of the actual participants. Rhododendrites gave a very good analysis of the conflict within COMMONNAME, ProcrastinatingReader and Mzajac both summarize a bunch of P&Gs in order to support a particular interpretation of COMMONNAME, and the tail end of the !votes show some common sense NAMECHANGE arguments. As for opposes, I really liked Toddy1's comment since it touched on when loanwords actually become part of a language which as a linguist I find cool, but that argument never really caught steam and it's hard to prove or justify with policy; Impru20's rationale lays out the main oppose argument well and the subsequent discussion touches on a lot of the themes in later rationales. I did learn a lot about chicken Kiev though, so thanks everyone for that thread. — Wug·a·po·des​ 22:33, 18 September 2020 (UTC)
I, too, learned much about Chicken Kiev. So much so, it kindled enough WikiLove in my WikiHeart to create a template. Speaking of, here you go:

ProcrastinatingReader (talk) has given you a juicy Chicken Kiev! Chicken Kievs are a signature dish of Russian and Ukrainian cuisine, made of chicken fillet pounded and rolled around cold butter, then coated with eggs and bread crumbs, and either fried or baked. Hopefully, this one has added flavor to your day.

I'm sure closing that discussion made you hungry. Here, have a Chicken Kiev. Or a Chicken Kyiv? Who knows.

Spread the goodness of Chicken Kiev by adding {{subst:Chicken Kiev}} to someone's Talk page with a friendly message! Give a Chicken Kiev to someone you've had disagreements with in the past, or to a good friend.

ProcrastinatingReader (talk) 22:44, 18 September 2020 (UTC)
Uh . . . that page in Unian, yes. (Cough.) Let's take a look: "The campaign followed the ministry's earlier initiative CorrectUA, aimed at promoting proper spelling of Ukrainian cities' names: Kyiv, Odesa, and Liviv." -- Hoary (talk) 09:06, 25 September 2020 (UTC)

Protection

Hey. You recently cleaned up this protection. Could you unprotect the talk page too? It's currently template-editor protected, for some reason. Thank you! ProcrastinatingReader (talk) 16:33, 26 September 2020 (UTC)

Ah, I may have the wrong admin, since I see the protection was recently applied and copied from the old article it seems. Pinging Ohnoitsjamie [34], in case it falls under their purview? Can be changed, too, I guess, rather than removed. Just not sure template editors would be any more qualified to move the page than ECP/admin. Maybe "page-mover move-protected" should be a thing. ProcrastinatingReader (talk) 16:38, 26 September 2020 (UTC)
Hmm, that whole set of pages is weird. With the recent RM, I think we could just try unprotecting all these and should problems arise, we can start fresh without the mix of protection levels. — Wug·a·po·des​ 01:21, 27 September 2020 (UTC)

Edit filter 1070

Special:AbuseFilter/1070 seems to be catching a lot of edits that aren't the LTA that it's supposed to catch. Can you take a look at it and see if you want to narrow it? Jackmcbarn (talk) 17:12, 26 September 2020 (UTC)

The most recent one that went through the filters most certainly isn't a false positive. Can the filter be made not to catch edits that were blocked (by other filters)? Nardog (talk) 17:17, 26 September 2020 (UTC)
@Nardog: (Redacted) Jackmcbarn (talk) 17:24, 26 September 2020 (UTC)
@Jackmcbarn: I really prefer we not discuss this filter in public. Nardog (talk) 17:26, 26 September 2020 (UTC)
@Nardog: Okay, I'll move this to email. Jackmcbarn (talk) 17:27, 26 September 2020 (UTC)
@Jackmcbarn and Nardog: I've modified the filter as suggested and testing on the recent false positives shows them excluded. Take a look and email me if you have other ideas or notice new problems. — Wug·a·po·des​ 02:00, 27 September 2020 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Wugapodes/Archive_14&oldid=984109293"