User talk:Wugapodes/Archive 33

Growth team newsletter #24
Welcome to the twenty-fourth newsletter from the Growth team!

Newcomer experience projects
The Growth team partnered with other WMF teams to conduct several experiments around increasing account creation and new editor retention. Results from four of these experiments are now available:


 * Thank you pages & banners - Encourage donors to create accounts through thank you pages and banners.
 * Marketing experiment - Run ads on-wiki and off-wiki to see how this impacts account activation.
 * "Add an image" GLAM events - Host GLAM events that focus on using the "Add an image" tool.
 * Welcome emails - Experiment sending welcome emails to newly created accounts.

Newcomer tasks

 * Several communities suggested improving "add a link", by suggesting underlinked articles first. We released this change to Growth pilot wikis. We will review the data and collect feedback before considering releasing it to more wikis.
 * The deployment of the "add a link" to all Wikipedias is still in progress. Suggested links use a prediction model, which has to be trained. The deployments will resume after we finish training all models.

Mentorship

 * When someone wants to signup as a mentor, they are now informed if they don't meet the defined criteria.
 * Workshop hosts asked us to have workshop attendees assigned to them. They can soon use a custom URL parameter. This way, workshop hosts will continue mentoring the event's attendees after the workshop. It will be available in February.
 * Have you considered to help new editors on your wiki, by signing up to be a Mentor?
 * Please visit Special:MentorDashboard to check on the conditions to be a mentor, and sign up.
 * If your wiki does not have Mentorship enabled, consider setting it up. The Growth team can provide advice and assist as needed. Please ping Trizek (WMF) for assistance.

Other news

 * In Special:SpecialPages, Growth experiments now have their own section.
 * This newsletter will have a new publication period, 6 times a year: January, March, May, July, September, November.

Translations

 * Newsletter translation: We are looking for translators for this newsletter. If you are interested and have the needed English language proficiency to assist, then please add your name to this list. You will receive an invite on your talk page to translate the newsletter when it is ready.
 * Interface translation: You can also help by translating the interface, or reviewing translations to make them more inclusive. Interface translations are hosted at translatewiki.net.

 Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.• Help with translations  14:44, 31 January 2023 (UTC)

Administrators' newsletter – February 2023
News and updates for administrators from the past month (January 2023).

Administrator changes
 * Gnome-colors-view-refresh.svg Gimmetrow
 * Gnome-colors-list-remove.svg Bjelleklang · Bob the Wikipedian · Leithp · WhisperToMe · 100 inactive admins



CheckUser changes
 * Gnome-colors-list-remove.svg BDD · Bradv · Donald Albury · Maxim · MusikAnimal

Oversighter changes
 * Gnome-colors-list-remove.svg BDD · Bradv · Donald Albury · Maxim

Guideline and policy news
 * Following an RfC, the administrator policy now requires that prior written consent be gained from the Arbitration Committee to mark a block as only appealable to the committee.
 * Following a community discussion, consensus has been found to impose the extended-confirmed restriction over the topic areas of Armenia and Azerbaijan and Kurds and Kurdistan.

Technical news
 * The Vector 2022 skin has become the default for desktop users of the English Wikipedia.

Arbitration Miscellaneous
 * The arbitration case Armenia-Azerbaijan 3 has been opened and the proposed decision is expected 24 February 2023.
 * In December, the contentious topics procedure was adopted which replaces the former discretionary sanctions system. The contentious topics procedure is now in effect following an initial implementation period. There is a detailed summary of the changes and administrator instructions for the new procedure. The arbitration clerk team are taking suggestions, concerns, and unresolved questions about this new system at their noticeboard.
 * Voting in the 2023 Steward elections will begin on 05 February 2023, 21:00 (UTC) and end on 26 February 2023, 21:00 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
 * Voting in the 2023 Community Wishlist Survey will begin on 10 February 2023 and end on 24 February 2023. You can submit, discuss and revise proposals until 6 February 2023.
 * Tech tip: Syntax highlighting is available in both the 2011 and 2017 Wikitext editors. It can help make editing paragraphs with many references or complicated templates easier.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 01:38, 2 February 2023 (UTC)

WugBot not moving approved nominations
Hi, Wugs. While looking through the DYK nominations page, I noticed that Did you know nominations/Martin Research and Did you know nominations/Statistics of Deadly Quarrels are still transcluded there, despite having been approved for days. WugBot's DYKMoverBot task is listed as being run every two hours, and it's swept the nominations page quite a few times since. I've carried out a null edit and have purged the first nomination, so maybe something else is the problem. I did think that it was perhaps due to the use of DYK checklist, but if that were the case I'd expect a lot more unmoved nominations. Just wanted to flag it to you, in case something was malfunctioning for the bot. Thanks, Sdrqaz (talk) 23:42, 1 February 2023 (UTC)
 * thanks for letting me know, it should be fixed now. The issue was the use of ... in the hidden comments. WugBot assumed that the next "}}" would be the end of DYK checklist, but this was not the case in these noms. I added some special logic to ignore "}}" when it's in the same line as {{tq| which doesn't exactly fix the issue but unless people start nesting even more templates it should be robust. — Wug·a·po·des​ 03:07, 2 February 2023 (UTC)
 * Ah, it worked! So it was DYK checklist after all{{nbsp}}... doing my reviews the old-fashioned way seems to have been justified {{smiley3|wink}} (not to mention the havoc it wreaks on screen-readers). Thanks for the quick resolution. Sdrqaz (talk) 03:57, 2 February 2023 (UTC)

Feedback request: All RFCs request for comment
Your feedback is requested &#32;at Wikipedia talk:Overcategorization&#32; on a "All RFCs" request for comment. Thank you for helping out! You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name. Message delivered to you with love by Yapperbot :) &#124; Is this wrong? Contact my bot operator. &#124; Sent at 17:30, 4 February 2023 (UTC)

The Signpost: 4 February 2023
 * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 21:46, 4 February 2023 (UTC)

Tech News: 2023-06
 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
 * In the Vector 2022 skin, logged-out users using the full-width toggle will be able to see the setting of their choice even after refreshing pages or opening new ones. This only applies to wikis where Vector 2022 is the default.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * Previously, we announced when some wikis would be in read-only for a few minutes because of a switch of their main database. These switches will not be announced any more, as the read-only time has become non-significant. Switches will continue to happen at 7AM UTC on Tuesdays and Thursdays.
 * Across all the wikis, in the Vector 2022 skin, logged-in users will see the page-related links such as "What links here" in a new side menu. It will be displayed on the other side of the screen. This change had previously been made on Czech, English, and Vietnamese Wikipedias.
 * Community Wishlist Survey 2023 will stop receiving new proposals on Monday, 6 February 2023, at 18:00 UTC. Proposers should complete any edits by then, to give time for translations and review. Voting will begin on Friday, 10 February.

Future changes
 * Octicons-tools.svg Gadgets and user scripts will be changing to load on desktop and mobile sites. Previously they would only load on the desktop site. It is recommended that wiki administrators audit the gadget definitions prior to this change, and add  for any gadgets which should not load on mobile. More details are available.

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

MediaWiki message delivery 10:19, 6 February 2023 (UTC)

Question from Ryan Irshaid on Draft:Captain Jihad Irshaid (00:56, 4 February 2023)
How to add photos too draft page --Ryan Irshaid (talk) 00:56, 4 February 2023 (UTC)


 * Hi, here's our tutorial on adding images to pages. — Wug·a·po·des​ 21:36, 7 February 2023 (UTC)

Feedback request: All RFCs request for comment
Your feedback is requested &#32;at Wikipedia:Neutral point of view/Noticeboard&#32; on a "All RFCs" request for comment. Thank you for helping out! You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name. Message delivered to you with love by Yapperbot :) &#124; Is this wrong? Contact my bot operator. &#124; Sent at 22:31, 10 February 2023 (UTC)

Tech News: 2023-07
 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
 * On wikis where patrolled edits are enabled, changes made to the mentor list by autopatrolled mentors are not correctly marked as patrolled. It will be fixed later this week.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * The Reply tool and other parts of DiscussionTools will be deployed for all editors using the mobile site. You can read more about this decision.

Future changes
 * All wikis will be read-only for a few minutes on March 1. This is planned for 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.

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

MediaWiki message delivery 01:47, 14 February 2023 (UTC)

Since I'm sure you have tons of free time
I don't want to muddy the RFAR further, so, since you foolishly answered me at the RFAR, I'll pester you. Just a little. If that's OK. When it says up at the top of the RFAR "Initiated by the Arbitration Committee, invoking its jurisdiction over all matters previously heard...", what does that mean? Was there a vote or straw poll or discussion, and the result was that a majority of the Arbs thought this case request should be posted? Or did some smaller subset of Arbs decide to do so? Not many Arbs have posted anything yet, which seems odd if ArbCom asked that a request be posted. I feel like the answer to that question should be transparent enough that it's OK to ask.

FWIW (probably not much) I remain troubled by the way this case was opened, even after your answers, but I guess you guys have enough on your plate that arguing with me about a done deal would be a waste of time, so I won't post at the RFAR further. I'm useless as far as whether a case is needed or not. My default position, if I know *nothing* about something, is that K.e.coffman is presumed to be probably right, and Icewhiz is presumed to be probably wrong (and, additionally, presumed evil). When they agree, my heuristic breaks down. So I have no opinion on the truth or falsity of the article. But geez, that article doesn't seem like any peer-reviewed paper I've ever seen. It looks more like a deeply referenced attack masquerading as an editorial. And I keep getting hung up on the number of times it says "this essay" in the abstract. Maybe "peer-reviewed" means something fundamentally different to an engineer than it does in the softer sciences.

Sorry, I'm wasting your time now. Thanks for any insight you can provide on the first paragraph. You can ignore the second. --Floquenbeam (talk) 23:08, 14 February 2023 (UTC)


 * Hi, not a waste of time so no need to apologize for asking. As a disclaimer, this is just my perspective on the situation, and others will likely have different perspectives. About a year ago, we declined hearing a case in this area 8-7, so from the start we already had a sense of where members were at. At various times and from various people, we were contacted regarding this piece. The recent AN thread and sock block brought these various threads back to life. So there were really two issues to discuss: would we want to have a case here and if so how to go about it. Given that we were 8-7 last time, that first question was already at a "maybe" and would have been better to do in a case request anyway. As to the second, how to go about a case, is where that first sentence of the request comes up. There's the typical route of waiting for someone to request a case, but a concern I raised (echoing my opposition to declining last time) was whether things would get worse before someone filed---you can get a sense from the statements that most people with knowledge of the area aren't filled with confidence that we'll listen. So the other option was taking up a case on our own initiative, which isn't unheard of. For example, the EEML case was initiated by then-sitting arbitrator Newyorkbrad who also served as a drafting arbitrator. One concern that was brought up is the history of harassment, and given that the case would cover topics already arbitrated and the effectiveness of remedies, it was suggested that the request by initiated by the Committee (subject to an on-wiki vote) rather than whichever member drew the short straw of posting it.So with all that context, the answer to your broad question is that we talked this over for a few days and thought through what would be the most effective way to go about it, but there was no formal "motion to post" or preliminary vote on whether to take the case. So obviously I can't speak for everyone, but I think that's why comments are slow to come. Part of the point of posting is to get community feedback, and I can imagine someone being fine with opening the door for wider feedback even if they're on the fence or opposed (I've done so in other situations). It could also be a time issue; we posted it on a Monday and most of us have day jobs during the week. I've had times where I completely forget about ArbCom for a few days only to have someone remind me I need to vote on something I wrote. Sorry for the roundabout answer, but hopefully that helps give you a sense of how the whole thing came to be.To your second paragraph, as someone in the softer sciences myself, I think you're right that there's a fair bit of difference across fields. To be clear, I have healthy skepticism of the paper; my interest in its peer-reviewed status isn't that peer review guarantees accuracy, but that two reviewers and an editorial board thought this information was interesting enough that other historians would want to know about it. As for the tone, it's certainly negative but having read my fair share of humanities papers, it's not particularly surprising to me. Nevins, Pesetsky, and Rodrigues (2009) published a response article in Language which is a relatively famous paper in the debate around linguistic relativity and the Pirahã language, and it's tone is quite negative. Even if you're not familiar with the topic, I think you'll see the structural parallels of "a deeply referenced attack" especially in section 2.2 where Nevins et al. basically go page by page through the critiqued author's work quoting a multitude of mistakes and dubious statements. I could go into why I think humanities and social sciences probably have more of these negative-tone articles, but I've already taken enough of your time on tangents. Hopefully this all helps orient you to what's been going on, and let me know if you want me to clarify anything. — Wug·a·po·des 01:05, 15 February 2023 (UTC)
 * Thanks, Wugapodes, for taking the time. That satisfies my curiosity/concern for paragraph one, and I agree paragraph two is mostly a tangent. Floquenbeam (talk) 14:57, 15 February 2023 (UTC)

The Signpost: 20 February 2023
 * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 18:04, 20 February 2023 (UTC)

Tech News: 2023-08
 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
 * Last week, during planned maintenance of Cloud Services, unforeseen complications forced the team to turn off all tools for 2–3 hours to prevent data corruption. Work is ongoing to prevent similar problems in the future.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * The voting phase for the Community Wishlist Survey 2023 ends on 24 February at 18:00 UTC. The results of the survey will be announced on 28 February.

Future changes
 * All wikis will be read-only for a few minutes on March 1. This is planned for 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.

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

MediaWiki message delivery 01:56, 21 February 2023 (UTC)

Feedback request: All RFCs request for comment
Your feedback is requested &#32;at Talk:Death and funeral of Constantine II of Greece&#32; on a "All RFCs" request for comment. Thank you for helping out! You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name. Message delivered to you with love by Yapperbot :) &#124; Is this wrong? Contact my bot operator. &#124; Sent at 02:30, 23 February 2023 (UTC)

Brief question about your Arbcom comment
Sorry to be a bother; I have been following along with the Holocaust in Poland case and I noticed you mention in your vote that the Grabowski–Klein paper is a second instance of public censure, but I couldn't immediately determine the first instance. Were you alluding to this 2019 piece in Haaretz?I wish you the best of luck in helping to resolve this mess. Shells-shells (talk) 05:42, 23 February 2023 (UTC)
 * yes. See [|the previous case request] which was related to that work. — Wug·a·po·des 18:10, 25 February 2023 (UTC)

Tech News: 2023-09
 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
 * Last week, in some areas of the world, there were problems with loading pages for 20 minutes and saving edits for 55 minutes. These issues were caused by a problem with our caching servers due to unforseen events during a routine maintenance task.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * All wikis will be read-only for a few minutes on March 1. This is planned for 14:00 UTC.

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

MediaWiki message delivery 23:45, 27 February 2023 (UTC)

February stories
Thank you for improving articles in February! - I wonder what could be done in the infoboxes matter we talked about. After around five years without major disputes, we have RfC after RfC, not only wasting editors' time but also not improving friendliness among editors. : without any evidence, I am still (after I basically left the topic in 2016) accused of having forced infoboxes systematically into articles and driven editors away, - both not true, and never intended. Yes, I made a list of reverts of added infoboxes, - that was all I can remember. I made it for my defense in the arb case, and then added what else I found, often a longstanding infobox silently disappearing when an article was improved to FA. --Gerda Arendt (talk) 10:53, 21 February 2023 (UTC)

My story on 24 February is about Artemy Vedel (TFA by Amitchell235), and I made a suggestion for more peace, - what do you think? --Gerda Arendt (talk) 16:16, 24 February 2023 (UTC)
 * Hi and I'm sorry to hear that you've had to deal with personal comments like that. Your idea is a good one and strikes me as a suggestion to use BRD. My only worry is that when BRD starts to break down, the typical solution is an RfC, so depending on how the BRD cycle goes at each article, it might not reduce those by much. Hopefully I'm wrong! The Artemy Vedel article is a fitting choice for the anniversary of the invasion, and the Prayer for Ukraine fact about its SNL performance is one I did not know! Thanks for sharing. — Wug·a·po·des 22:47, 25 February 2023 (UTC)
 * Thank you. I'm on my way to a funeral tomorrow, long trip, which will keep me away until Tuesday. You could comment on the article talk, no? For backstory look at Siegfried (opera), and Sibelius, where BRD worked (and where I asked how many more RfCs do we need, in 2021 I believe). --Gerda Arendt (talk) 06:04, 26 February 2023 (UTC)
 * back - today: two women whose birthday we celebrate today, 99 and 90! --Gerda Arendt (talk) 12:26, 28 February 2023 (UTC)

Administrators' newsletter – March 2023
News and updates for administrators from the past month (February 2023).

Administrator changes
 * Gnome-colors-view-refresh.svg The Wordsmith
 * Gnome-colors-list-remove.svg Fuhghettaboutit · Spinningspark (deceased)



CheckUser changes
 * Gnome-colors-view-refresh.svg Callanecc

Oversighter changes
 * Gnome-colors-view-refresh.svg Callanecc

Guideline and policy news
 * Following a request for comment, F10 (useless non-media files) has been deprecated.
 * Following a request for comment, the Portal CSD criteria (P1 (portal subject to CSD as an article) and P2 (underpopulated portal)) have been deprecated.
 * A request for comment is open to discuss making the closing instructions for the requested moves process a guideline.

Technical news
 * The results of the 2023 Community Wishlist Survey have been posted.

Arbitration
 * Remedy 11 ("Request for Comment") of the Conduct in deletion-related editing case has been rescinded.
 * The proposed decision for the Armenia-Azerbaijan 3 case is expected 7 March 2023.
 * A case related to the Holocaust in Poland is expected to be opened soon.

Miscellaneous
 * The 2023 appointees for the Ombuds commission are AGK, Ameisenigel, Bennylin, Daniuu, Emufarmers, Faendalimas, JJMC89, MdsShakil, Minorax and Renvoy as regular members and Zabe as advisory members.
 * Following the 2023 Steward Elections, the following editors have been appointed as stewards: Mykola7, Superpes15, and Xaosflux.
 * The Terms of Use update cycle has started, which includes a [p]roposal for better addressing undisclosed paid editing. Feedback is being accepted until 24 April 2023.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 13:20, 1 March 2023 (UTC)

WikiCup 2023 March newsletter
So ends the first round of the 2023 WikiCup. Everyone with a positive score moved on to Round 2, with 54 contestants qualifying. The top scorers in Round 1 were:


 * Unlimitedlead with 1205 points, a WikiCup newcomer, led the field with two featured articles on historical figures and several featured article candidate reviews.
 * Epicgenius was in second place with 789 points; a seasoned WikiCup competitor he specialises in buildings and locations in New York.
 * 🇩🇪 FrB.TG was in third place with 625 points, garnered from a featured article on a filmmaker which qualified for an impressive number of bonus points.
 * 🇺🇸 TheJoebro64, another WikiCup newcomer, came next with 600 points gained from two featured articles on video games.
 * Iazyges was in fifth place with 532 points, from two featured articles on classical history.

The top sixteen contestants at the end of Round 1 had all scored over 300 points; these included LunaEatsTuna,  Thebiguglyalien,  Sammi Brie,  Trainsandotherthings,  🏴󠁧󠁢󠁥󠁮󠁧󠁿 Lee Vilenski, 🇮🇩 Juxlos,  Unexpectedlydian,  SounderBruce, 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Kosack,  BennyOnTheLoose and  PCN02WPS. It was a high-scoring start to the competition.

These contestants, like all the others, now have to start again from scratch. The first round finished on February 26. Remember that any content promoted after that date but before the start of Round 2 can be claimed in Round 2. Some contestants made claims before the new submissions pages were set up, and they will need to resubmit them. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points. If you are concerned that your nomination—whether it is at good article candidates, a featured process, or anywhere else—will not receive the necessary reviews, please list it on WikiCup/Reviews Needed.

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. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove yourself from WikiCup/Newsletter/Send. Sturmvogel 66 and Cwmhiraeth. MediaWiki message delivery (talk) 19:37, 2 March 2023 (UTC)

Tech News: 2023-10
 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 Community Wishlist Survey 2023 edition has been concluded. Community Tech has published the results of the survey and will provide an update on what is next in April 2023.
 * On wikis which use LanguageConverter to handle multiple writing systems, articles which used custom conversion rules in the wikitext (primarily on Chinese Wikipedia) would have these rules applied inconsistently in the table of contents, especially in the Vector 2022 skin. This has now been fixed.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * A search system has been added to the Preferences screen. This will let you find different options more easily. Making it work on mobile devices will happen soon.

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

MediaWiki message delivery 23:48, 6 March 2023 (UTC)

blast from the past
hi.

this thing seems to be in deep coma for a long while now, but i want to ask anyway: any news/update regarding the state of "chess browser"?

peace. קיפודנחש (aka kipod) (talk) 16:27, 2 March 2023 (UTC)
 * Hi קיפודנחש (aka kipod), it's been on the back-burned for quite some time, yes. The Arbitration Committee has eaten up most of my wiki-related time budget (and even my arbcom-related software stuff has stalled with recent events). Odds are good that my end of development will pick back up in the second half of this year or early next year once things slow down or my term on the committee ends. You might also be interested in looking at Lichess's pgn widget which might be a useful resource given it outsources some of our maintenance burden to an upstream team. I haven't looked into it much, so there are some open questions about i18n and a11y that would need to be investigated. It would also probably set us back a fair bit in terms of development, so there are costs as well. Haven't really thought it through, but it seems like a cool widget to be aware of even when thinking about development directions. — Wug·a·po·des 02:38, 4 March 2023 (UTC)
 * thanks!
 * i don't know that "back burner" is proper description here. in my village we used to call it "stalled" (or at best, "on ice")... :)
 * regarding "arbcom": don't they grant early release for good behavior? :)
 * i'll bug you again if it's still stalled in a year or so (and if i'll still be around and will still remember, both of which are far from guaranteed).
 * regarding the widget you linked:
 * if i understand correctly, it imports all kinds of shit from all over the place (specifically, "chessops/parsePgn"), so i doubt it's useful or rather, appropriate for chessbrowser extension.
 * the whole idea here was to farm the "analyze" job to php, and limit the JS side to presentation. if we want to do the whole shebang in JS, then my little "chess viewer" which operates on hewiki for 10 years or more (and on several other wikis several years also) is better fit for mw: it's more compact, and does not import shitload of stuff, and written specifically for mw. one could, of course, take the widget's code and massage it such that it will use the data which is seeded in the DOM by the php side, but at this point lose the perceived advantage of "outsourcing" the maintenance burden to the upstream project is lost, and the modified code has to be maintained locally.
 * in addition, the widget is written using ts, which is kind of js preprocessor, and i doubt it's a good fit for mediawiki.
 * peace. קיפודנחש (aka kipod) (talk) 16:21, 4 March 2023 (UTC)
 * @קיפודנחש Unforutnately the reward for doing your work is getting to do more work. My goal is to get through the current round of work and then spend some time on my "stalled" projects. That will probably be around July, so we'll see how much ChessBrowser work I can get done then. In any case, I don't plan to run for another term on the committee, so ChessBrowser is already my first priority post-ArbCom.As for the lichess widget, I think you've got a good analysis of why it wouldn't work well here, and I appreciate you looking into it! — Wug·a·po·des 01:50, 8 March 2023 (UTC)

I mentioned you.
Hi Wugapodes; i imagine you'll get a ping from my having mentioned you at ANI; there's no call for you to respond (unless you want to, obviously), it was just a courtesy ping because i referred to an action of yours from a couple of years ago. Sorry for the intrusion, i now return you to your previously scheduled activity. Happy days ~ LindsayHello 20:17, 7 March 2023 (UTC)


 * @LindsayH No intrusion at all! I appreciate being kept in the loop. I don't remember the discussion too well, but feel free to ping me again is you have any questions about it. — Wug·a·po·des 01:58, 8 March 2023 (UTC)

The Signpost: 9 March 2023
 * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 05:43, 9 March 2023 (UTC)

Tech News: 2023-11
 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
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * Starting on Wednesday, a new set of Wikipedias will get "Add a link" . This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally.

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

MediaWiki message delivery 23:18, 13 March 2023 (UTC)

Question from Brwnmich597 (21:13, 10 March 2023)
I want to be a "real-boy".. Trying everything under the sun to add my voice to Wikipedia. Is it me? (smell bad?) What?

Love me,

Michael B. (smile) ghettostone/ editor/chief --Michael R. Brown User:Brwnmich597  21:13, 10 March 2023 (UTC)


 * Hi @Brwnmich597, while I don't think you smell bad, the draft's references and related formatting do. :) I will provide some you additional information about autobiographies and having a Wikipedia article about you on your talk page.  S0091 (talk) 15:55, 12 March 2023 (UTC)
 * Thank you... (very good). I appreciate the response.  My growth is happening now!
 * S0091- so, so, good... made me smile. ( I will read all I can and try to imporve skill set)
 * I appreciate it.
 * Mike (brwnmich597) Brown Michael R. Brown User:Brwnmich597 19:53, 15 March 2023 (UTC)

Apology
The rollback was an accidental misclick. <sub style="border:1px solid #228B22;padding:1px;">Piotr Konieczny aka Prokonsul Piotrus&#124; reply here 07:34, 16 March 2023 (UTC)


 * Easy to do, thanks for letting me know. — Wug·a·po·des 19:48, 16 March 2023 (UTC)

MediaWiki:Contactpage-arbcom-block-appeal-prior-onwiki
I'd like to remove MediaWiki:Contactpage-arbcom-block-appeal-prior-onwiki from Category:Pages with templates in the wrong namespace (and stop the page from showing the error message as well), and think the new version of unblock at Template:Unblock/sandbox should do the trick. Running it by you first in case you see a problem with updating the template that I don't. – wbm1058 (talk) 04:18, 20 March 2023 (UTC)

The Signpost: 20 March 2023
<div class="hlist" style="margin-top:10px; font-size:90%; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;"> * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 11:18, 20 March 2023 (UTC)

Tech News: 2023-12
<section begin="technews-2023-W12"/> 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
 * Last week, some users experienced issues loading image thumbnails. This was due to incorrectly cached images.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).
 * Octicons-gift.svg A link to the user's page will appear on  — some user scripts which previously added this link may cause conflicts. This feature request was voted #17 in the 2023 Community Wishlist Survey.
 * Octicons-gift.svg The edit window will be resizable and larger by default. This feature request was voted #80 in the 2023 Community Wishlist Survey.
 * There will be a new option for Administrators when they are unblocking a user, to add the unblocked user’s user page to their watchlist. This will work both via and via the API.

Meetings
 * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on 24 March at 17:00 (UTC). See details and how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe. <section end="technews-2023-W12"/>

MediaWiki message delivery 01:24, 21 March 2023 (UTC)

Tech News: 2023-13
<section begin="technews-2023-W13"/> 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 AbuseFilter condition limit was increased from 1000 to 2000.
 * Some Global AbuseFilter actions will no longer apply to local projects.
 * Desktop users are now able to subscribe to talk pages by clicking on the link in the  menu. If you subscribe to a talk page, you receive notifications when new topics are started on that talk page. This is separate from putting the page on your watchlist or subscribing to a single discussion.

Changes later this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from . It will be on non-Wikipedia wikis and some Wikipedias from . It will be on all wikis from (calendar).

Future changes
 * You will be able to choose visual diffs on all history pages at the Wiktionaries and Wikipedias.
 * Octicons-tools.svg The legacy Mobile Content Service is going away in July 2023. Developers are encouraged to switch to Parsoid or another API before then to ensure service continuity.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe. <section end="technews-2023-W13"/>

MediaWiki message delivery 01:12, 28 March 2023 (UTC)

Question from Hardword1 (15:30, 30 March 2023)
Hi, Thank you for support, the question is, Can I add a you tube link to my Resource? --Hardword1 (talk) 15:30, 30 March 2023 (UTC)


 * Hi and welcome to Wikipedia! Our policy on including YouTube videos points out that in most cases YouTube videos are probably not appropriate to link, but it's a case by case basis. What YouTube video are you trying to use? What article or draft is it for? — Wug·a·po·des 18:25, 30 March 2023 (UTC)
 * Thank you, I appreciate your support. Hardword1 (talk) 19:55, 31 March 2023 (UTC)

Growth team newsletter #25
Welcome to the twenty-fifth newsletter from the Growth team! Help with translations

Celebrations
Leveling up release


 * We released Leveling up features to our pilot wikis on March 22 for an initial A/B test.
 * In this test, we use post-edit dialogs (pop-ups shown after publishing an edit) and notifications to encourage new editors to try new types of newcomer-friendly suggested edits.
 * We are closely monitoring the short term impact of this feature as well as the longer term effect on newcomer productivity and retention. If the experiment shows positive results, we will release this feature to more wikis.

5,000+ images added via the newcomer task in February


 * In February 2023, 5,035 images were added via the newcomer “add an image” feature (on all wikis where available); 155 were reverted.
 * Since the feature “add an image” was launched: 36,803 images have been added; 2,957 images were reverted.

Recent changes

 * Add a link
 * Community Ambassadors completed an initial evaluation that confirmed that prioritizing underlinked articles resulted in better article suggestions. We then evaluated the change on Growth pilot wikis, and results suggest that more newcomers are successfully completing the task and experiencing fewer reverts. We have now deployed the new prioritization model to all wikis with "add a link" enabled.
 * We continue the deployment of "add a link" to more wikis. These changes are regularly announced in Tech News. To know if newcomers at your wiki have access to this feature, please visit your Homepage.
 * The Impact module was deployed on our pilot wikis, where we conducted an A/B test. We published initial findings, and a data scientist is now completing experiment analysis.
 * Donor Thank you page experiment – Donors land on a “thank you” page after donation, and that landing page now includes a call to action to try editing: Example Thank you page in French. This promising feature is tested at several Wikipedias.
 * Growth features are now the default experience on both test.wikipedia.org and test2.wikipedia.org. You can test our features there.

Upcoming work

 * Add an image – We plan to offer section-level image suggestions as a structured task for newcomers.
 * We are starting design work.
 * Growth team Ambassadors helped with an initial evaluation of these section-level image suggestions.
 * We will start a community consultation in which we share initial ideas and designs soon.
 * IP Editing: Privacy Enhancement and Abuse Mitigation – We will support this project for all Growth Team maintained products and extensions that may be affected by IP Masking.

'' Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe. '' 13:10, 1 April 2023 (UTC)

Question from Matt the wiki master on Blocking policy (16:48, 1 April 2023)
Hello, I have been told multiple times that I am going to be banned for "Disruptive Edits" and "Adding Unsoursed Information. I have not been told why it's disruptive or how to add citations. Please help me. --Matt the wiki master (talk) 16:48, 1 April 2023 (UTC)

The Signpost: 03 April 2023
<div class="hlist" style="margin-top:10px; font-size:90%; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;"> * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 16:47, 3 April 2023 (UTC)