This is an archive of past discussions with User:Philosopher. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Thanks for signing up for the Feedback Dashboard response team! I wanted to let you know that the tool just got an important update (see here for details). I also wanted to invite you to the IRC office hours session that Steven and I are going to hold this Sunday, December 4. Hope you can make it and share your experience/questions with us! Thanks again, Maryana (WMF) (talk) 00:02, 3 December 2011 (UTC)
I have opened a discussion at Wikipedia talk:Notability (organizations and companies)#US elementary schools: Inherent notability: for "Blue Ribbon Schools" as to whether the 5200 schools which have been found awarded the "Blue Ribbon" seal of approval get inherent notability, or if they each have to satisfy WP:ORG via significant coverage in multiple reliable and independent sources.I'm not sure if I'm supposed to notify those who commented at the AFD or the Deletion Review. I received no notification of the Deletion Review, and I was the one who initiated the AFD. I would have certainly had something to say at the Deletion Review, which was closed after 2 days. Edison (talk) 19:12, 7 December 2011 (UTC)
Should the discussion I opened be made an "RFC?" I don't believe I've ever opened one and am not sure of the process. I'd like to see a wide input on this notability issue rather than just starting another AFD. Edison (talk) 19:45, 7 December 2011 (UTC)
The RfC tag seems to be used fairly often these days, so I think you could open it as an RfC - I don't think I've ever opened an RFC either, though I've helped close at least one. Thanks for notifying me about the discussion, btw, but I think I'm going to sit this one out - I support the idea of inherent notability for some subjects, but have no idea whether this subject is appropriate for inherent notability or not. --PhilosopherLet us reason together.21:31, 7 December 2011 (UTC)
As far as notification, Raymie should have notified you of the DR - and I should have noticed that that hadn't happened and notified you myself, sorry. Then again, I would have just undone the redirection on my own w/o a DR if I'd been asked, so... --PhilosopherLet us reason together.21:44, 7 December 2011 (UTC)
Hey Philosopher, I hope you're having a great day. As you are familiar with legal matters (according to your user page and my prior interactions with you, anyway), would you mind taking a quick look at Wikipedia talk:Articles for creation/Law practice optimization to see if there is any encyclopedic potential with this article? Asking because I've never heard of "Law Practice Optimizers" before and it sounds like one of hundreds of non-notable consultancy "fields". This is in reference to User talk:CharlieEchoTango#Finding Citations; if you have any comments, and suggestions, I'd like to hear them. Best regards, CharlieEchoTango (contact) 17:39, 8 December 2011 (UTC)
We are currently running a study on the effects of adding additional information to SuggestBot’s recommendations. Participation in the study is voluntary. Should you wish to not participate in the study, or have questions or concerns, you can find contact information in the consent information sheet.
We have added information about the readership and quality of the suggested articles using a Low/Medium/High scale. For readership the scale goes from Low to High , while for quality the scale goes from Low to High .
SuggestBot predicts that you will enjoy editing some of these articles. Have fun!
SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. We appreciate that you have signed up to receive suggestions regularly, your contributions make Wikipedia better — thanks for helping!
Thanks! One criticism though: I don't think that modifying {{Information}} would be the best way to do it on Commons; it should probably be done in the licensing templates instead. While you could do it in {{Information}}, that would require editing every image page on Commons to add the parameter and would require everyone to correctly specify the value of the parameter corresponding to the licensing tags.
I see my reference to {{Free media}} is confusing. Here on enwiki, every free license template contains {{Free media}}, which handles adding of Category:All free media. So the obvious thing to do here is modify that template to take a parameter and modify all the calls to it in the various licensing templates to pass that parameter. Of course, everything on Commons is supposed to be free media, so you probably don't have the equivalent in your licensing templates. You could create a helper template (along the lines of our {{Free media}}) to apply this category, or you could just have the appropriate licensing tags apply the category directly if that's how Commons likes to do things.
Hello, Philosopher. You have new messages at MediaWiki talk:Titleblacklist. Message added 15:33, 15 December 2011 (UTC). You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
I see that you gave Lmatt AWB access. Please take it away. His excessive vandalism is highly disruptive.
He changed the templateEarthsatmosphere to Earth's atmosphere and then modified pages under a 1RR restriction. This is a simply a highly disruptive nonsense change. So far, he has only modified a few pages with this, but there are about 20 that might be affected.
He changed the cite templates on those same pages so they they no longer match the templates, similar to the following.
the reason I created the category is that the majority of items in Category:NA-Class_Maps_articles appear to be files - and all of those articles for example File_talk:1490_map.jpg&action=edit got tagged by the Bot as class=File, importance=NA which seems great.
However I had not already created the Category:File-Class_Maps_articles, so they all appear to show up as Category:NA-Class_Maps_articles which you'll see if you look at File_talk:1490_map.jpg
I've tried purging various pages, I've tried updating the documentation on the template, i've tried running the webform assessment update bot - and it's also run on it's own a few times (i think - or at least it's been a couple of weeks) and I've finally got to the point where I don't know which bit I didn't do in order to get that to work.
my last option (that I've not attempted out of fear of messing it up) might be to directly edit this page User:WP_1.0_bot/Tables/Project/Maps but that still doesn't explain to me why the File class articles end up in the NA class articles category.
I'm a bit confused to be fair - it all seems like it ought to work ok - but perhaps I 've missed something obvious and so I thought I'd ask you as you clearly know a fair bit about this sort of stuff. Sorry to be a burden. EdwardLane (talk) 02:10, 29 December 2011 (UTC)
My fault - I used the default categorization, not the extended version in the project template - meaning that it didn't know what to do with "File" and threw it in with everything else it didn't know what to do with in NA. I've expanded the template - it may take a bit for the database to update, but the articles should be in the right categories now. --PhilosopherLet us reason together.02:53, 30 December 2011 (UTC)
Thanks and it may have been my fault - as I probably didn't mention the extended categories when we started the thing up - but that was in ignorance of what files actually ought to be part of wp maps so no one at fault :) I just 'purged' a file and it appeared in the category correctly so it looks like it will get sorted over time now. Thanks very much. EdwardLane (talk) 11:39, 30 December 2011 (UTC)
We are currently running a study on the effects of adding additional information to SuggestBot’s recommendations. Participation in the study is voluntary. Should you wish to not participate in the study, or have questions or concerns, you can find contact information in the consent information sheet.
We have added information about the readership and quality of the suggested articles using a Low/Medium/High scale. For readership the scale goes from Low to High , while for quality the scale goes from Low to High .
SuggestBot predicts that you will enjoy editing some of these articles. Have fun!
SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. We appreciate that you have signed up to receive suggestions regularly, your contributions make Wikipedia better — thanks for helping!
Hello Philosopher, I was just letting you know that I would like to request rollback permission. I would mainly want to use it for reverting things that are vandalism. I have done this in the past with Twinkle, but I have heard that this interface is much better. See my history for details. Thanks!
--RubinkumarTalk22:53, 6 January 2012 (UTC)
Just so you know, if you look my contributions, and switch to the 500 edits per page view, you can see that I have nominated around 30 pages for CSD, as I have warned vandals about 25 times making the total amount around 55. --RubinkumarTalk15:04, 7 January 2012 (UTC)
Following consensus at the 2021 RfA review, the autopatrolled user right has been removed from the administrators user group; admins can grant themselves the autopatrolled permission if they wish to remain autopatrolled.
The functionaries email list (functionaries-enlists.wikimedia.org) will no longer accept incoming emails apart from those sent by list members and WMF staff. Private concerns, apart from those requiring oversight, should be directly sent to the Arbitration Committee.
Happy New Year and Happy New WikiCup! The 2022 competition has just begun and all article creators, expanders, improvers and reviewers are welcome to take part. Even if you are a novice editor you should be able to advance to at least the second round, improving your editing skills as you go. If you have already signed up, your submissions page can be found here. If you have not yet signed up, you can add your name here and the judges will set up your submissions page. Any questions on the rules or on anything else should be directed to one of the judges, or posted to the WikiCup talk page. Signups will close at the end of January, and the first round will end on 26 February; the 64 highest scorers at that time will move on to round 2. The judges for the WikiCup this year are: Sturmvogel 66 (talk·contribs·email) and Cwmhiraeth (talk·contribs·email). Good luck! MediaWiki message delivery (talk) 14:37, 5 January 2022 (UTC)
Welcome to the 2022 WikiCup!
Happy New Year and Happy New WikiCup! The 2022 competition has just begun and all article creators, expanders, improvers and reviewers are welcome to take part. Even if you are a novice editor you should be able to advance to at least the second round, improving your editing skills as you go. If you have already signed up, your submissions page can be found here. If you have not yet signed up, you can add your name here and the judges will set up your submissions page. Any questions on the rules or on anything else should be directed to one of the judges, or posted to the WikiCup talk page. Signups will close at the end of January, and the first round will end on 26 February; the 64 highest scorers at that time will move on to round 2. The judges for the WikiCup this year are: Sturmvogel 66 (talk·contribs·email) and Cwmhiraeth (talk·contribs·email). Good luck! MediaWiki message delivery (talk) 15:02, 5 January 2022 (UTC)
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
A oauth_consumer variable has been added to the AbuseFilter to enable identifying changes made by specific tools. [3]
Gadgets are now able to directly include JSON pages. This means some gadgets can now be configured by administrators without needing the interface administrator permission, such as with the Geonotice gadget. [4]
Gadgets can now specify page actions on which they are available. For example, |actions=edit,history will load a gadget only while editing and on history pages. [5]
Gadgets can now be loaded on demand with the withgadget URL parameter. This can be used to replace an earlier snippet that typically looks like withJS or withCSS. [6]
Four special pages (and their API counterparts) now have a maximum database query execution time of 30 seconds. These special pages are: RecentChanges, Watchlist, Contributions, and Log. This change will help with site performance and stability. You can read more details about this change including some possible solutions if this affects your workflows. [10]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 January. It will be on non-Wikipedia wikis and some Wikipedias from 12 January. It will be on all wikis from 13 January (calendar).
Events
Community Wishlist Survey 2022 begins. All contributors to the Wikimedia projects can propose for tools and platform improvements. The proposal phase takes place from 10 January 18:00 UTC to 23 January 18:00 UTC. Learn more.
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
When using WikiEditor (also known as the 2010 wikitext editor), people will now see a warning if they link to disambiguation pages. If you click "Review link" in the warning, it will ask you to correct the link to a more specific term. You can read more information about this completed 2021 Community Wishlist item.
When asked to create a new page or talk page section, input fields can be "preloaded" with some text. This feature is now limited to wikitext pages. This is so users can't be tricked into making malicious edits. There is a discussion about if this feature should be re-enabled for some content types.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 January. It will be on non-Wikipedia wikis and some Wikipedias from 19 January. It will be on all wikis from 20 January (calendar).
Events
Community Wishlist Survey 2022 continues. All contributors to the Wikimedia projects can propose for tools and platform improvements. The proposal phase takes place from 10 January 18:00 UTC to 23 January 18:00 UTC. Learn more.
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
The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 January. It will be on non-Wikipedia wikis and some Wikipedias from 26 January. It will be on all wikis from 27 January (calendar).
The following languages can now be used with syntax highlighting: BDD, Elpi, LilyPond, Maxima, Rita, Savi, Sed, Sophia, Spice, .SRCINFO.
You can now access your watchlist from outside of the user menu in the new Vector skin. The watchlist link appears next to the notification icons if you are at the top of the page. [12]
Events
You can see the results of the Coolest Tool Award 2021 and learn more about 14 tools which were selected this year.
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 a gadget should support the new ?withgadget URL parameter that was announced 3 weeks ago, then it must now also specify supportsUrlLoad in the gadget definition (documentation). [13]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 February. It will be on non-Wikipedia wikis and some Wikipedias from 2 February. It will be on all wikis from 3 February (calendar).
Future changes
A change that was announced last year was delayed. It is now ready to move ahead:
The user group oversight will be renamed suppress. This is for technical reasons. This is the technical name. It doesn't affect what you call the editors with this user right on your wiki. This is planned to happen in three weeks. You can comment in Phabricator if you have objections. As usual, these labels can be translated on translatewiki (direct links are available) or by administrators on your wiki.
Graphs are unavailable due to technical issues. Updates on reimplementing the Graph extension, which will be known as the Chart extension, can be found on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever.
Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020.
Overall
In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired).
January 2020
Yeah, you're not gonna be able to get away with this anymore.
A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022.
On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved.
In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code).
A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18.
Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it.
May 2020
We heard you like bots, so we made a bot that reports the status of your bots, so now you can use bots while you use bots
MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status.
In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored.
On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors).
David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so".
The user group oversight will be renamed suppress in around 3 weeks. This will not affect the name shown to users and is simply a change in the technical name of the user group. The change is being made for technical reasons. You can comment in Phabricator if you have objections.
The Reply Tool feature, which is a part of Discussion Tools, will be opt-out for everyone logged in or logged out starting 7 February 2022. Editors wishing to comment on this can do so in the relevant Village Pump discussion.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Category counts are sometimes wrong. They will now be completely recounted at the beginning of every month. [14]
Problems
A code-change last week to fix a bug with Live Preview may have caused problems with some local gadgets and user-scripts. Any code with skin-specific behaviour for vector should be updated to also check for vector-2022. A code-snippet, global search, and example are available.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 February. It will be on non-Wikipedia wikis and some Wikipedias from 9 February. It will be on all wikis from 10 February (calendar).
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
Purging a category page with fewer than 5,000 members will now recount it completely. This will allow editors to fix incorrect counts when it is wrong. [15]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 February. It will be on non-Wikipedia wikis and some Wikipedias from 16 February. It will be on all wikis from 17 February (calendar).
In the AbuseFilter extension, the rmspecials() function has been updated so that it does not remove the "space" character. Wikis are advised to wrap all the uses of rmspecials() with rmwhitespace() wherever necessary to keep filters' behavior unchanged. You can use the search function on Special:AbuseFilter to locate its usage. [16]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
At Wikipedias, all new accounts now get the Growth features by default when creating an account. Communities are encouraged to update their help resources. Previously, only 80% of new accounts would get the Growth features. A few Wikipedias remain unaffected by this change. [18]
You can now prevent specific images that are used in a page from appearing in other locations, such as within PagePreviews or Search results. This is done with the markup class=notpageimage. For example, [[File:Example.png|class=notpageimage]]. [19]
There has been a change to the HTML of Special:Contributions, Special:MergeHistory, and History pages, to support the grouping of changes by date in the mobile skin. While unlikely, this may affect gadgets and user scripts. A list of all the HTML changes is on Phabricator.
The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 February. It will be on non-Wikipedia wikis and some Wikipedias from 23 February. It will be on all wikis from 24 February (calendar).
Future changes
The software to play videos and audio files on pages will change soon on all wikis. The old player will be removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [20][21]
Toolforge's underlying operating system is being updated. If you maintain any tools there, there are two options for migrating your tools into the new system. There are details, deadlines, and instructions on Wikitech. [22]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Mentors using the Growth Mentor dashboard will now see newcomers assigned to them who have made at least one edit, up to 200 edits. Previously, all newcomers assigned to the mentor were visible on the dashboard, even ones without any edit or ones who made hundred of edits. Mentors can still change these values using the filters on their dashboard. Also, the last choice of filters will now be saved. [24][25]
The user group oversight was renamed suppress. This is for technical reasons. You may need to update any local references to the old name, e.g. gadgets, links to Special:Listusers, or uses of NUMBERINGROUP.
Problems
The recent change to the HTML of tracking changes pages caused some problems for screenreaders. This is being fixed. [26]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 March. It will be on non-Wikipedia wikis and some Wikipedias from 2 March. It will be on all wikis from 3 March (calendar).
Future changes
Working with templates will become easier. Several improvements are planned for March 9 on most wikis and on March 16 on English Wikipedia. The improvements include: Bracket matching, syntax highlighting colors, finding and inserting templates, and related visual editor features.
If you are a template developer or an interface administrator, and you are intentionally overriding or using the default CSS styles of user feedback boxes (the classes: successbox, messagebox, errorbox, warningbox), please note that these classes and associated CSS will soon be removed from MediaWiki core. This is to prevent problems when the same class-names are also used on a wiki. Please let us know by commenting at phab:T300314 if you think you might be affected.
A RfC is open to discuss prohibiting draftification of articles over 90 days old.
Technical news
The deployment of the reply tool as an opt-out feature, as announced in last month's newsletter, has been delayed to 7 March. Feedback and comments are being welcomed at Wikipedia talk:Talk pages project. (T296645)
And so ends the first round of the WikiCup. Last year anyone who scored more than zero points moved on to Round 2, but this was not the case this year, and a score of 13 or more was required to proceed. The top scorers in Round 1 were:
Epicgenius, a finalist last year, who led the field with 1906 points, gained from 32 GAs and 19 DYKs, all on the topic of New York buildings.
AryKun, new to the contest, was second with 1588 points, having achieved 2 FAs, 11 GAs and various other submissions, mostly on the subject of birds.
Bloom6132, a WikiCup veteran, was in third place with 682 points, garnered from 51 In the news items and several DYKs.
GhostRiver was close behind with 679 points, gained from achieving 12 GAs, mostly on ice hockey players, and 35 GARs.
Kavyansh.Singh was in fifth place with 551 points, with an FA, a FL, and many reviews.
SounderBruce was next with 454 points, gained from an FA and various other submissions, mostly on United States highways.
Ktin, another WikiCup veteran, was in seventh place with 412 points, mostly gained from In the news items.
These contestants, like all the others who qualified for Round 2, now have to start scoring points again from scratch. Between them, contestants completed reviews of a large number of good articles as the contest ran concurrently with a GAN backlog drive. Well done all! To qualify for Round 3, contestants will need to finish Round 2 among the top thirty-two participants.
Remember that any content promoted after the end of Round 1 but before the start of Round 2 can be claimed in Round 2. Anything that should have been claimed for in Round 1 is no longer eligible for points. 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 Wikipedia:WikiCup/Reviews Needed.
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
There was a problem with some interface labels last week. It will be fixed this week. This change was part of ongoing work to simplify the support for skins which do not have active maintainers. [27]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 March. It will be on non-Wikipedia wikis and some Wikipedias from 9 March. It will be on all wikis from 10 March (calendar).
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 Wikipedia Android app it is now possible to change the toolbar at the bottom so the tools you use more often are easier to click on. The app now also has a focused reading mode. [28][29]
Problems
There was a problem with the collection of some page-view data from June 2021 to January 2022 on all wikis. This means the statistics are incomplete. To help calculate which projects and regions were most affected, relevant datasets are being retained for 30 extra days. You can read more on Meta-wiki.
There was a problem with the databases on March 10. All wikis were unreachable for logged-in users for 12 minutes. Logged-out users could read pages but could not edit or access uncached content then. [30]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 March. It will be on non-Wikipedia wikis and some Wikipedias from 16 March. It will be on all wikis from 17 March (calendar).
Access to Special:RevisionDelete has been expanded to include users who have deletelogentry and deletedhistory rights through their group memberships. Before, only those with the deleterevision right could access this special page. [32]
On the Special:Undelete pages for diffs and revisions, there will be a link back to the main Undelete page with the list of revisions. [33]
Future changes
The Wikimedia Foundation has announced the IP Masking implementation strategy and next steps. The announcement can be read here.
The Wikimedia Hackathon 2022 will take place as a hybrid event on 20-22 May 2022. The Hackathon will be held online and there are grants available to support local in-person meetups around the world. Grants can be requested until 20 March.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
New code release schedule for this week
There will be four MediaWiki releases this week, instead of just one. This is an experiment which should lead to fewer problems and to faster feature updates. The releases will be on all wikis, at different times, on Monday, Tuesday, and Wednesday. You can read more about this project.
The Jupyter notebooks tool PAWS has been updated to a new interface. [36]
Future changes
Interactive maps via Kartographer will soon work on wikis using the FlaggedRevisions extension. Please tell us which improvements you want to see in Kartographer. You can take this survey in simple English. [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.
Recent changes
There is a simple new Wikimedia Commons upload tool available for macOS users, Sunflower.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 March. It will be on non-Wikipedia wikis and some Wikipedias from 30 March. It will be on all wikis from 31 March (calendar).
Some wikis will be in read-only for a few minutes because of regular database maintenance. It will be performed on 29 March at 7:00 UTC (targeted wikis) and on 31 March at 7:00 UTC (targeted wikis). [38][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.
Problems
For a few days last week, edits that were suggested to newcomers were not tagged in the Special:RecentChanges feed. This bug has been fixed. [40]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 April. It will be on non-Wikipedia wikis and some Wikipedias from 6 April. It will be on all wikis from 7 April (calendar).
Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 7 April at 7:00 UTC (targeted wikis).
Future changes
Starting next week, Tech News' title will be translatable. When the newsletter is distributed, its title may not be Tech News: 2022-14 anymore. It may affect some filters that have been set up by some communities. [41]
Access to Special:RevisionDelete has been expanded to include users who have the deletelogentry and deletedhistory rights. This means that those in the Researcher user group and Checkusers who are not administrators can now access Special:RevisionDelete. The users able to view the special page after this change are the 3 users in the Researcher group, as there are currently no checkusers who are not already administrators. (T301928)
When viewing deleted revisions or diffs on Special:Undelete a back link to the undelete page for the associated page is now present. (T284114)
.jpg)
_(cropped_to_40%25).jpg){kind=small}
_shown_in_her_laboratory_in_1947.jpg)
