Just a friendly reminder that this is the deadline day for nomination statements - unless you post one a day or so late as I have done in the past two years. You are no doubt aware of this but as I see no statement from you yet I am getting anxious about the absence of a statement from you. Thus, I add this note.Donner60 (talk)10:03, 14 September 2025 (UTC)[reply]
I left a note for Matarisvan. He has not been online since then. It appears that he became somewhat inactive rather abruptly over the past several weeks. He had only 3 edits in August and 11 this month, all but two on September 11. I see no note on his user page or talk page. But we have all seen some users' activity levels drop entirely or almost entirely over a long period without much if any explanation from them. I suppose, if he doesn't file even a late statement, he could be co-opted if he returns to active use and wants to still be a coordinator. As far as I can tell, he has made good contributions to the project over the last year.Donner60 (talk)23:18, 14 September 2025 (UTC)[reply]
@Donner60 and @Hawkeye7: Hi guys, I enrolled for my Masters program in August, and I had not expected it would be so consuming of my time and energy. I have resumed editing now, and my focus is on updating WPMH FAs to current standards (mostly sfn refs) and adding these FAs to new Featured Topics. I will try to join the November Drive, but I cannot commit until I achieve some of the above goals. Also, I will surely put up my candidacy for the next coordinator election. Also, if there is a possibility of being co-opted as Donner60 posted above, I would like to try. CheersMatarisvan (talk)12:41, 23 October 2025 (UTC)[reply]
I take it that you mean that it refers to you as "Mike Christie/Reference library"? I will investigate... The Bot had trouble with this article; it wasn't expecting that an article would get all the way to featured without being tagged by a single project.Hawkeye7(discuss)01:48, 22 October 2025 (UTC)[reply]
Yes, that is why. It goes through the nominators line looking for users. It determines that a link refers to a user if it is refers to the User namespace. Unfortunately, that includes your library subpage. (It skipped your talk page and contributions because they were not in the User namespace.) So I am going to tell it to ignore links that include a slash. That should resolve the problem. My apologies.Hawkeye7(discuss)02:58, 22 October 2025 (UTC)[reply]
No need to apologize. I had similar problems with ChristieBot in handling GA notifications and there are still some edge cases that I don't think it deals with correctly. Anyway, thanks for fixing it.Mike Christie (talk -contribs -library)03:08, 22 October 2025 (UTC)[reply]
Hi. Something seems amiss with the bot, I think.Look atTalk:Frank Hague, see how you can see the "article milestones" and "identified" link the the FAC nomination page?
Thanks for that. The Bot had an issue with pages lacking an ArticleHistory template. The problem has been resolved, and I have updated these two pages.Hawkeye7(discuss)23:38, 22 October 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
The Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You canread more on the project page.
Autoconfirmed users onsmall andmedium wikis with the CampaignEvents extension can now useEvent Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
View all 31 community-submitted tasks that wereresolved last week. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed.[1]
Updates for technical contributors
The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities.Visit the deployment page to learn more.
The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through theSpecial:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on theproject launch page.[2]
Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using theREST Sandbox. See theMediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
A dedicatedchangelog now exists for the MediaWiki REST API. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, pleasejoin the discussion.
Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked fromQ130635582. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited.[3]
Hi Hawkeye7.According to the talk page of the Milhist bot, you're its owner. I had a question. In 2021, the bot rated the articleBattōtai (song) as start-class, saying it didn't meet the "Coverage and accuracy" criterion. Do you know what that criterion is, and how I can see if the page now meets that?Best wishes,Tenchi irezaru chouteki zo (talk)13:50, 31 October 2025 (UTC)[reply]
The Bot usesLiftwing to determine the "Coverage and accuracy" criterion. So it is based on whether itlooks like a B class article. I ran it again, and Liftwing thinks the current version looks like a C class article. Sometimes, articles are small by their nature. If you disagree with a bot assessment, you can take an article toWikipedia:WikiProject Military history/Assessment/Requests and a human will look at it.Hawkeye7(discuss)21:36, 31 October 2025 (UTC)[reply]
BeanieFan11 (submissions) with 1,035 round points, mostly from 19 good articles and 21 did you know articles about athletes
vigilantcosmicpenguin (submissions) with 819 round points, mostly from 13 good articles and 11 did you know articles about a wide range of topics from abortion topics to African cities
TheNuggeteer (submissions) with 508 round points from 9 good articles, 4 good topic articles and 6 did you know articles mainly about Philippines topics, along with 19 good article reviews
The final round was very productive, and contestants had 2featured articles, 4featured lists, 106good articles, 5good topic articles, 178 article reviews, 76did you know articles, and 9in the news articles. Altogether, Wikipedia has benefited greatly from the activities of WikiCup competitors all through the contest. Well done everyone!
The top eight scorers will receive awards shortly. The following special awards will be made, based on high performance in particular areas of content creation. These prizes are awarded to the competitor who scored the highest in any particular field during the competition.
Gog the Mild (submissions) wins the featured article prize, with 12 featured articles total, and the featured topic prize, with 9 featured topic articles in total
AirshipJungleman29 (submissions) wins the featured picture prize, submitting the only featured picture in the entire contest during round 3
History6042 (submissions) wins the featured content reviewer prize, with 127 featured content reviews. He will also share the ITN prize, with 20 in the news articles in total.
BeanieFan11 (submissions) wins the good article prize, with 100 good articles total, and the DYK prize, with 147 did you know articles in total. He will also share the ITN prize, with 20 in the news articles in total.
Next year's competition will begin on 1 January. You are invited tosign up to participate. The WikiCup is open to all Wikipedians, both novices and experienced editors, and we hope to see you all in the 2026 competition. Until then, it only remains to once again congratulate our worthy winners, and thank all participants for their involvement!
Hi @Hawkeye7, I hope this message finds you well! I wanted to follow up regarding the First Jewish–Roman War article, which has been nominated for Featured Article status. Given your previous valuable input during the Military History A-Class review, I would greatly appreciate it if you could provide any further feedback or thoughts on the article as part of itsFAC discussion.
As it stands, the nomination has been open for a few weeks, but we are still seeking additional consensus to move the process forward. Your insights, especially considering the depth of the topic, would be incredibly helpful in finalizing the nomination.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Administrators will now find thatSpecial:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start).[4]
For users with "Automatically subscribe to topics"enabled in their preferences, starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "Add topic" or "Reply" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time.[5]
Scribunto modules can now be used togenerate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files.[6]
Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments.[7]
Users with large watchlists have long faced timeouts when editingSpecial:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. Acommunity wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish![8]
View all 31 community-submitted tasks that wereresolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query.[9]
Updates for technical contributors
Since 2019 theWikimedia URL Shortener athttps://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means/s/ URLs will not be advertised under article titles via HTMLclass="title-shortlink". The/s/ URLs will keep working.[10]
On Thursday, October 30, theMediaWiki Interfaces andSRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to theService Ops team board.
MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025.[11]
In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia ina Diff blog post.
Ugh, my bad. Sorry. The FAC part is okay, but what I just realized threw me off is that the Article History was second and the projects first, on top. I'm not used to seeing it like that. I'm used to Article History being on top. Sorry to have bothered you for me being confused. I just put the history on top, if that's ok.MisawaSakura (talk)03:54, 4 November 2025 (UTC)[reply]
I have revised a sentence in Early life which you may wish to edit if the change is wrong or incomplete. Also, can you clarify the sentence "The British government filed a patent on the VT fuse in April 1942 and the Americans in September 1943." I can not tell whether the Americans (U.S. Government, I assume) filed a separate patent application or whether the British government filed a patent applicant for Americans, presumably in the United States. Thanks. After that, B class.Donner60 (talk)04:54, 7 November 2025 (UTC)[reply]
The image on your talk page sums it up nicely. I have added a bit about it. (The elephant, not the image.) The real problem was the 400-word limit. I am sorry that your question was removed, but I thought that the ban on questions before start time was a good idea, as in the past it has been a practice of some to nominate at the last minute in order to minimise scrutiny.Hawkeye7(discuss)21:10, 9 November 2025 (UTC)[reply]
I naturally would not have asked it had I realised there was a ban on early questions. Word limit or not, if you don't address it you haven't a hope in hell of getting elected.SpartazHumbug!22:36, 9 November 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Example of a talk page with the new design, in French.
MediaWiki can now display apage indicator automatically while a page is protected. This feature is disabled by default. It can be enabled bycommunity request.[14]
Using the "Show preview" or "Show changes" buttons in the wikitext editor will now carry over certain URL parameters like 'useskin', 'uselang' and 'section'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content.[15][16][17]
Wikivoyage wikis can usecolored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed.[18]
The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging.[19]
The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis.[20]
View all 27 community-submitted tasks that wereresolved last week. For example the inability to lock accounts on mobile sites has been fixed.[21]
TheJWT subject field inOAuth 2 access tokens will soon change from<user id> tomw:<identity type>:<user id>, where<identity type> is typicallyCentralAuth: (forSUL wikis) orlocal:<wiki id> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and thesessionJwt cookie more similar. Old access tokens will still work.[23]
AREL1_45 branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change.[25]
The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support.[26][27]
Hey @Hawkeye7, want to let you know that @FAC Bot messed upAnnouncements/New featured content and you cannot see the newly featured pictures, lists, or topics (diff). Additionally, the formatting is off. I don't know how to fix it without breaking the entire template, so I want to let me know. Also, if the template talk is a better place to let you know, please tell me.❤HistoryTheorist❤03:29, 13 November 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
TheReader Experience team is experimenting withreading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of theAccount Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
As part of theParser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in theExtension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the"Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag theContent Transform Team in Phabricator.
Unsupported Tools: Several issues withVideo2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check thePhabricator board.
Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026.Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please emailhackathon@wikimedia.org.
Hello! Voting in the2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. Alleligible users are allowed to vote. Users with alternate accounts may only vote once.
TheArbitration Committee is the panel of editors responsible for conducting theWikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to imposesite bans,topic bans, editing restrictions, and other measures needed to maintain our editing environment. Thearbitration policy describes the Committee's roles and responsibilities in greater detail.
The Bot expected the December newsletter to be created by now. It has instructions on how to createthe portion it uses if it is not there, and did so, but due to an error on my part an error was still flagged. The latest version of the Bot does not update any pages if it thinks that one is in error. A one-line change fixed this by marking the newly created page as correctly loaded. The articles have been processed, and the problem will not recur.Hawkeye7(discuss)18:08, 18 November 2025 (UTC)[reply]
Hullo mate, I've approved your latest Cross, should I manually add the award to your talk (and theBugle Project News) or wait till MilHistBot does its thing? Cheers,Ian Rose (talk)03:10, 21 November 2025 (UTC)[reply]
WikiProject Articles for creation is holding amonth longBacklog Drive in December! The goal of this drive is toreduce the backlog of unreviewed drafts to less than half a month of outstanding reviews from the current 2+ months. Bonus points will be given for reviewing drafts that have been waiting more than 30 days. The drive is running from 1 December 2025 through 31 December 2025.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Last week, theWikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching forcxfcnmt on Russian Wikipedia will now add suggestions forсчастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week.[29]
Later this week, users of the "Improved Syntax Highlighting"beta feature will have syntax highlighting available inDiscussionTools. This requires that the "Enable editing tools in source mode" preference be set.[30]
Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known asCollaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcominglearning session to see the new feature in action and share your feedback.
View all 24 community-submitted tasks that wereresolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed.[31]
Updates for technical contributors
Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill therecruitment survey.[32]
The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support forformat=xml&xlst={stylesheet} will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026).[33]
The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph orhttps://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review theData Access andRequest a Query pages for details and assistance on alternative access methods.