Latest comment: 1 year ago1 comment1 person in discussion
Happy New Year and Happy New WikiCup! The 2025 competition has just begun and all article creators, expanders, improvers and reviewers are welcome to take part. Even if you are a novice editor, we hope the WikiCup will give you a chance to improve 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 ready for you to take part. Any questions on the scoring, rules or anything else should be directed to one of the judges, or posted to the WikiCup talk page.
For the 2025 WikiCup, we've implemented several changes to the scoring system. The highest-ranking contestants will now receive tournament points at the end of each round, and final rankings are decided by the number of tournament points each contestant has. If you're busy and can't sign up in January, don't worry: Signups are now open throughout the year. To make things fairer for latecomers, the lowest-scoring contestants will no longer be eliminated at the end of each round.
A request for comment is open to discuss whether admins should be advised to warn users rather than issue no-warning blocks to those who have posted promotional content outside of article space.
Technical news
The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Administrators can mass-delete multiple pages created by a user or IP address using Extension:Nuke. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address.
On wikis that use the Patrolled edits feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use filters on Recent Changes may need to update their filter settings.
View all 31 community-submitted tasks that were resolved last week. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been fixed.
Updates for technical contributors
The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. The last group of wikis (Catalan Wikiquote, Wikimedia Finland, Goan Konkani Wikipedia, Kabyle Wikipedia, Portuguese Wikibooks, Wikimedia Sweden) will soon be contacted. If you have questions about this process, please ping Trizek (WMF) at your wiki.
The latest quarterly Technical Community Newsletter is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and 13 other questions to shape the technical direction for next year.
Updates for editors
iOS Wikipedia App users worldwide can now access a personalized Year in Review feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content.
Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in Special:RecentChanges and Special:NewPages.
Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a double redirect). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement.
Wikimedia wikis allow WebAuthn-based second factor checks (such as hardware tokens) during login, but the feature is fragile and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of SUL3 (single user login version 3). Existing keys are unaffected.
For developers that use the MediaWiki History dumps: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the Temporary Accounts initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the mediawiki_user_history dump, the anonymous field will be renamed to is_anonymous. The changes will take effect with the next release of the dumps in February.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor.
Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons. You can now also insert <code> tags using a new toolbar button. Thanks to user stjn for these improvements.
Help is needed to ensure the citation generator works properly on each wiki.
(1) Administrators should update the local versions of the page MediaWiki:Citoid-template-type-map.json to include entries for preprint, standard, and dataset; Here are example diffs to replicate for 'preprint' and for 'standard' and 'dataset'.
(2.1) If the citoid map in the citation template used for these types of references is missing, one will need to be added. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates for 'preprint' and for 'standard' and 'dataset'. The new fields that may need to be supported are archiveID, identifier, repository, organization, repositoryLocation, committee, and versionNumber.
Administrators can now nuke pages created by a user or IP address from the last 90 days, up from the initial 30 days. T380846
A 'Recreated' tag will now be added to pages that were created with the same title as a page which was previously deleted and it can be used as a filter in Special:RecentChanges and Special:NewPages. T56145
News and notes: Let's talk! The WMF executive team delivers a new update; plus, the latest EU policy report, good-bye to the German Wikipedia's Café, and other news from the Wikimedia world.
Community view: 24th Wikipedia Day in New York City Wikimedians and newbies celebrate 24 years of Wikipedia in the Brooklyn Central Library. Special guests Stephen Harrison and Clay Shirky joined in conversation.
Traffic report: A wild drive The start of the year was filled with a few unfortunate losses, tragic disasters, emerging tech forces and A LOT of politics.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Product and Technology Advisory Council (PTAC) has published a draft of their recommendations for the Wikimedia Foundation's Product and Technology department. They have recommended focusing on mobile experiences, particularly contributions. They request community feedback at the talk page by 21 February.
Updates for editors
The "Special pages" portlet link will be moved from the "Toolbox" into the "Navigation" section of the main menu's sidebar by default. This change is because the Toolbox is intended for tools relating to the current page, not tools relating to the site, so the link will be more logically and consistently located. To modify this behavior and update CSS styling, administrators can follow the instructions at T385346.
As part of this year's work around improving the ways readers discover content on the wikis, the Web team will be running an experiment with a small number of readers that displays some suggestions for related or interesting articles within the search bar. Please check out the project page for more information.
View all 22 community-submitted tasks that were resolved last week. For example, the global blocks log will now be shown directly on the Special:CentralAuth page, similarly to global locks, to simplify the workflows for stewards.
Updates for technical contributors
Wikidata now supports a special language as a "default for all languages" for labels and aliases. This is to avoid excessive duplication of the same information across many languages. If your Wikidata queries use labels, you may need to update them as some existing labels are getting removed.
The function getDescription was invoked on every Wiki page read and accounts for ~2.5% of a page's total load time. The calculated value will now be cached, reducing load on Wikimedia servers.
As part of the RESTBase deprecation effort, the /page/related endpoint has been blocked as of February 6, 2025, and will be removed soon. This timeline was chosen to align with the deprecation schedules for older Android and iOS versions. The stable alternative is the "morelike" action API in MediaWiki, and a migration example is available. The MediaWiki Interfaces team can be contacted for any questions.
In depth
The latest quarterly Language and Internationalization newsletter is available. It includes: Updates about the "Contribute" menu; details on some of the newest language editions of Wikipedia; details on new languages supported by the MediaWiki interface; updates on the Community-defined lists feature; and more.
The latest Chart Project newsletter is available. It includes updates on the progress towards bringing better visibility into global charts usage and support for categorizing pages in the Data namespace on Commons.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Communities using growth tools can now showcase one event on the Special:Homepage for newcomers. This feature will help newcomers to be informed about editing activities they can participate in. Administrators can create a new event to showcase at Special:CommunityConfiguration. To learn more about this feature, please read the Diff post, have a look at the documentation, or contact the Growth team.
Updates for editors
Highlighted talk pages improvements
Starting next week, talk pages at these wikis – Spanish Wikipedia, French Wikipedia, Italian Wikipedia, Japanese Wikipedia – will get a new design. This change was extensively tested as a Beta feature and is the last step of talk pages improvements.
You can now navigate to view a redirect page directly from its action pages, such as the history page. Previously, you were forced to first go to the redirect target. This change should help editors who work with redirects a lot. Thanks to user stjn for this improvement.
When a Cite reference is reused many times, wikis currently show either numbers like "1.23" or localized alphabetic markers like "a b c" in the reference list. Previously, if there were so many reuses that the alphabetic markers were all used, an error message was displayed. As part of the work to modernize Cite customization, these errors will no longer be shown and instead the backlinks will fall back to showing numeric markers like "1.23" once the alphabetic markers are all used.
The log entries for each change to an editor's user-groups are now clearer by specifying exactly what has changed, instead of the plain before and after listings. Translators can help to update the localized versions. Thanks to user Msz2001 for these improvements.
A new filter has been added to the Special:Nuke tool, which allows administrators to mass delete pages, to enable users to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below.
Non-administrators can now check which pages are able to be deleted using the Special:Nuke tool. Thanks to user MolecularPilot for this and the previous improvements.
View all 25 community-submitted tasks that were resolved last week. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again.
Updates for technical contributors
Parsoid Read Views is going to be rolling out to most Wiktionaries over the next few weeks, following the successful transition of Wikivoyage to Parsoid Read Views last year. For more information, see the Parsoid/Parser Unification project page.
Developers of tools that run on-wiki should note that mw.Uri is deprecated. Tools requiring mw.Uri must explicitly declare mediawiki.Uri as a ResourceLoader dependency, and should migrate to the browser native URL API soon.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Administrators can now customize how the Babel feature creates categories using Special:CommunityConfiguration/Babel. They can rename language categories, choose whether they should be auto-created, and adjust other settings.
The wikimedia.org portal has been updated – and is receiving some ongoing improvements – to modernize and improve the accessibility of our portal pages. It now has better support for mobile layouts, updated wording and links, and better language support. Additionally, all of the Wikimedia project portals, such as wikibooks.org, now support dark mode when a reader is using that system setting.
One new wiki has been created: a Wiktionary in Santali (wikt:sat:)
View all 30 community-submitted tasks that were resolved last week. For example, a bug was fixed that prevented clicking on search results in the web-interface for some Firefox for Android phone configurations.
Meetings and events
The next Language Community Meeting is happening soon, February 28th at 14:00 UTC. This week's meeting will cover: highlights and technical updates on keyboard and tools for the Sámi languages, Translatewiki.net contributions from the Bahasa Lampung community in Indonesia, and technical Q&A. If you'd like to join, simply sign up on the wiki page.
Technology report: Hear that? The wikis go silent twice a year From patrolling new edits to uploading photos or joining a campaign, you can count on the Wikimedia platform to be up and running — in your language, anywhere in the world. That is, except for a couple of minutes during the equinoctes.
Opinion: Sennecaster's RfA debriefing User Sennecaster shares her thoughts on her recent RfA and the aspects that might have played a role in making it successful.
Latest comment: 1 year ago1 comment1 person in discussion
The first round of the 2025 WikiCup ended on 26 February. As a reminder, we are no longer disqualifying the lowest-scoring contestants; everyone who competed in round 1 will advance to round 2 unless they have withdrawn or been banned from Wikipedia. Instead, the contestants with the highest round-point totals now receive tournament points at the end of each round. Unlike the round points in the main WikiCup table, which are reset at the end of each round, tournament points are carried over between rounds and can only be earned if a competitor is among the top 16 round-point scorers. This table shows all competitors who have received tournament points so far.
Round 1 was very competitive compared with previous years; two contestants scored more than 1,000 round points, and the top 16 contestants all scored more than 500 round points. The following competitors scored more than 800 round points:
Sammi Brie(submissions), with 846 round points from 16 GAs about radio and TV stations, 45 GA reviews, and 3 DYKs.
Hey man im josh(submissions), with 816 round points from 5 FLs about sports and Olympic topics, 46 FL reviews, 3 ITN articles, and a large number of bonus points.
MaranoFan(submissions), with 815 round points primarily from 3 FAs and 1 GA about music, in addition to 9 article reviews.
The full scores for round 1 can be seen here. During this round, contestants have claimed 18 featured articles, 26 featured lists, 1 featured-topic article, 197 good articles, 38 good-topic articles and more than 100 Did You Know articles. In addition, competitors have worked on 23 In the News articles, and they have conducted nearly 550 reviews.
Remember that any content promoted after 26 February but before the start of Round 2 can be claimed in Round 2, which begins on 1 March. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 14:12, 27 February 2025 (UTC)Reply
Tech News: 2025-10
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
All logged-in editors using the mobile view can now edit a full page. The "Edit full page" link is accessible from the "More" menu in the toolbar. This was previously only available to editors using the Advanced mobile contributions setting.
Interface administrators can now help to remove the deprecated Cite CSS code matching "mw-ref" from their local MediaWiki:Common.css. The list of wikis in need of cleanup, and the code to remove, can be found with this global search and in this example, and you can learn more about how to help on the CSS migration project page. The Cite footnote markers ("[1]") are now rendered by Parsoid, and the deprecated CSS is no longer needed. The CSS for backlinks ("mw:referencedBy") should remain in place for now. This cleanup is expected to cause no visible changes for readers. Please help to remove this code before March 20, after which the development team will do it for you.
When editors embed a file (e.g. [[File:MediaWiki.png]]) on a page that is protected with cascading protection, the software will no longer restrict edits to the file description page, only to new file uploads. In contrast, transcluding a file description page (e.g. {{:File:MediaWiki.png}}) will now restrict edits to the page.
When editors revert a file to an earlier version it will now require the same permissions as ordinarily uploading a new version of the file. The software now checks for 'reupload' or 'reupload-own' rights, and respects cascading protection.
When administrators are listing pages for deletion with the Nuke tool, they can now also list associated talk pages and redirects for deletion, alongside pages created by the target, rather than needing to manually delete these pages afterwards.
The previously noted update to Single User Login, which will accommodate browser restrictions on cross-domain cookies by moving login and account creation to a central domain, will now roll out to all users during March and April. The team plans to enable it for all new account creation on Group0 wikis this week. See the SUL3 project page for more details and an updated timeline.
Since last week there has been a bug that shows some interface icons as black squares until the page has fully loaded. It will be fixed this week.
One new wiki has been created: a Wikipedia in Sylheti (w:syl:)
View all 23 community-submitted tasks that were resolved last week. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile.
A request for comment is open to discuss whether AI-generated images (meaning those wholly created by generative AI, not human-created images modified with AI tools) should be banned from use in articles.
A new filter has been added to the Special:Nuke tool, which allows administrators to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below. T378488
Non-administrators can now check which pages are able to be deleted using the Special:Nuke tool. T376378
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Editors who use password managers at multiple wikis may notice changes in the future. The way that our wikis provide information to password managers about reusing passwords across domains has recently been updated, so some password managers might now offer you login credentials that you saved for a different Wikimedia site. Some password managers already did this, and are now doing it for more Wikimedia domains. This is part of the SUL3 project which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use.
The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions in Afrika Baraza and the last ESEAP call, key challenges like search, editing, and offline access are being explored, with upcoming focus groups to dive deeper into these topics. All languages are welcome, and interpretation will be available. Want to share your thoughts? Join the discussion or email aramadan@wikimedia.org!
All wikis will be read-only for a few minutes on March 19. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.
The latest quarterly Growth newsletter is available. It includes: the launch of the Community Updates module, the most recent changes in Community Configuration, and the upcoming test of in-article suggestions for first-time editors.
An old API that was previously used in the Android Wikipedia app is being removed at the end of March. There are no current software uses, but users of the app with a version that is older than 6 months by the time of removal (2025-03-31), will no longer have access to the Suggested Edits feature, until they update their app. You can read more details about this change.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs a datacenter server switchover, redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. Thanks to the Listen to Wikipedia tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can read more about the background and details of this process on the Diff blog. If you want to keep an ear out for the next server switchover, listen to the wikis on March 19 at 14:00 UTC.
On Wikimedia Commons, a new system to select the appropriate file categories has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard.
The Community Tech team is seeking wikis to join a pilot for the Multiblocks feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the project talk page.
Starting March 25, the Editing team will test a new feature for Edit Check at 12 Wikipedias: Multi-Check. Half of the newcomers on these wikis will see all Reference Checks during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented on Phabricator.
The Global reminder bot, which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the listing of existing translations and documentation to check if their language needs updating or creation.
The GlobalPreferences gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults.
View all 26 community-submitted tasks that were resolved last week. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages.
Updates for technical contributors
Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues please report them. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Wikimedia Foundation is seeking your feedback on the drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April.
Updates for editors
The CampaignEvents extension will be released to multiple wikis (see deployment plan for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: Event Registration, Collaboration List, and Invitation Lists. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the extension talk page or in Phabricator (with #campaigns-product-team tag).
Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in Event Registration, as part of the CampaignEvents extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by requesting a configuration change in Phabricator (and adding the #campaigns-product-team tag). Participants of past events can cancel their registration at any time.
Administrators at wikis that have a customized MediaWiki:Sidebar should check that it contains an entry for the Special pages listing. If it does not, they should add it using * specialpages-url|specialpages. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April.
The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon (). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts.
VisualEditor has introduced a new client-side hook for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be shared in the task.
Developers who use the mw.Api JavaScript library, can now identify the tool using it with the userAgent parameter: var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
The Editing team is working on a new Edit check: Peacock check. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: in this Phabricator task, they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging Trizek (WMF).
Single User Login has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in.
Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for MediaWiki REST APIs. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the on the test wiki REST Sandbox special page for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to share feedback about your experience. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects.
Sometimes a small, one line code change can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving maps.wikimedia.org - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a datacenter switchover. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of extensive work by two developers on porting the last component of the maps stack over to kubernetes, where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable.
Meetings and events
MediaWiki Users and Developers Workshop Spring 2025 is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website.
Latest comment: 1 year ago1 comment1 person in 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.
The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the 2.0 overview documentation, which includes guidance related to a few of the breaking changes such as font-size, line-height, and size-icon.
The results of the Developer Satisfaction Survey (2025) are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on.
The 2025 Wikimedia Hackathon will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a visa or e-visa to enter the country.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Later this week, the default thumbnail size will be increased from 220px to 250px. This changes how pages are shown in all wikis and has been requested by some communities for many years, but wasn't previously possible due to technical limitations.
File thumbnails are now stored in discrete sizes. If a page specifies a thumbnail size that's not among the standard sizes (20, 40, 60, 120, 250, 330, 500, 960), then MediaWiki will pick the closest larger thumbnail size but will tell the browser to downscale it to the requested size. In these cases, nothing will change visually but users might load slightly larger images. If it doesn't matter which thumbnail size is used in a page, please pick one of the standard sizes to avoid the extra in-browser down-scaling step.
Updates for editors
The Wikimedia Foundation are working on a system called Edge Uniques which will enable A/B testing, help protect against Distributed denial-of-service attacks (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is so that they can more efficiently build tools which help readers, and make it easier for readers to find what they are looking for.
To improve security for users, a small percentage of logins will now require that the account owner input a one-time password emailed to their account. It is recommended that you check that the email address on your account is set correctly, and that it has been confirmed, and that you have an email set for this purpose.
"Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?" This question will be asked at 7 wikis starting next week, on Recent Changes and Watchlist pages. The Moderator Tools team wants to know more about activities that involve looking at new edits made to your Wikimedia project, and determining whether they adhere to your project's policies.
The latest quarterly Technical Community Newsletter is now available. This edition includes: an invitation for tool maintainers to attend the Toolforge UI Community Feedback Session on April 15th; recent community metrics; and recent technical blog posts.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Wikifunctions is now integrated with Dagbani Wikipedia since April 15. It is the first project that will be able to call functions from Wikifunctions and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function, rather than via a local template.
A new type of lint error has been created: Empty headings (documentation). The Linter extension's purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them.
Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is now also available on Kaggle. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall Structured Contents project, and about the first release that's freely usable.
There is no new MediaWiki version this week.
Meetings and events
The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss Peacock check, which is the latest Edit check that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The meeting will be on April 28, 2025 at 18:00–19:00 UTC and hosted on Zoom.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Event organizers who host collaborative activities on multiple wikis, including Bengali, Japanese, and Korean Wikipedias, will have access to the CampaignEvents extension this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as requested by a community.
The release of the next major version of Codex, the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of breaking changes and minor visual changes. Instructions on handling the breaking and visual changes are documented on this page. Pre-release testing is reported in T386298, with post-release issues tracked in T392379 and T392390.
Users of Wiki Replicas will notice that the database views of ipblocks, ipblocks_ipindex, and ipblocks_compat are now deprecated. Users can query the block and block_target new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025.
The 2025 Wikimedia Hackathon, which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey.
Latest comment: 1 year ago1 comment1 person in discussion
The second round of the 2025 WikiCup ended on 28 April at 23:59 UTC. To reiterate what we said in the previous newsletter, we are no longer disqualifying contestants based on how many points (now known as round points) they received. Instead, the contestants with the highest round-point totals now receive tournament points at the end of each round. These tournament points are carried over between rounds, and can only be earned if a competitor is among the top 16 round-point scorers at the end of each round. This table shows all competitors who have received tournament points so far. Everyone who competed in round 2 will advance to round 3 unless they have withdrawn or been banned.
Round 2 was quite competitive. Four contestants scored more than 1,000 round points, and eight scored more than 500 points (including one who has withdrawn). The following competitors scored at least 800 points:
History6042(submissions) with 1,088 round points from four featured lists about Michelin-starred restaurants, nine good articles and a good topic mostly on Olympic-related subjects, seven ITN articles, and dozens of reviews
Gog the Mild(submissions) with 1,085 round points from three FAs, one GA, and four DYKs on military history, as well as 18 reviews
Arconning(submissions) with 887 round points, mostly from four FLs, six GAs, and seven DYKs on Olympic topics, along with more than two dozen reviews
In addition, we would like to recognize Generalissima(submissions) for her efforts; she scored 801 round points but withdrew before the end of the round.
The full scores for round 2 can be seen here. During this round, contestants have claimed 13 featured articles, 20 featured lists, 4 featured-topic articles, 138 good articles, 7 good-topic articles, and more than 100 Did You Know articles. In addition, competitors have worked on 19 In the News articles, and they have conducted nearly 300 reviews.
Remember that any content promoted after 28 April but before the start of Round 3 can be claimed in Round 3. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 01:02, 29 April 2025 (UTC)Reply
The Signpost: 1 May 2025
Latest comment: 1 year ago1 comment1 person in discussion
News from the WMF: Product & Tech Progress on the Annual Plan A look at some product and tech highlights from the Wikimedia Foundation's Annual Plan (July–December 2024).
Latest comment: 1 year ago1 comment1 person in 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.
Admins can now choose which namespaces are permitted for Event Registration via Community Configuration (documentation). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities.
Editors can now transclude the Collaboration List on a wiki page (documentation). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via Special:AllEvents (example). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page.
Developers who use the moment library in gadgets and user scripts should revise their code to use alternatives like the Intl library or the new mediawiki.DateFormatter library. The moment library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and ask related questions in this Phabricator task.
Developers who maintain a tool that queries the Wikidata term store tables (wbt_*) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. Documentation and related links are available.
The latest Chart Project newsletter is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data.
An RfC was closed with consensus to allow editors to opt-out of seeing "sticky decorative elements". Such elements should now be wrapped in {{sticky decoration wrapper}}. Editors who wish to opt out can follow the instructions at WP:STICKYDECO.
An RfC has resulted in a broad prohibition on the use of AI-generated images in articles. A few common-sense exceptions are recognized.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The "Get shortened URL" link on the sidebar now includes a QR code. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently.
Updates for editors
The Wikimedia Foundation is working on a system called Edge Uniques, which will enable A/B testing, help protect against distributed denial-of-service attacks (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has previously written about this. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the talk page.
Starting May 19, 2025, Event organisers in wikis with the CampaignEvents extension enabled can use Event Registration in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at Special:CommunityConfiguration/CampaignEvents.
The Wikipedia project now has a Wikipedia in Nupe (w:nup:). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to new Wikipedia.
Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the Structured Contents snapshots (beta). The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references.
The /page/data-parsoid REST API endpoint is no longer in use and will be deprecated. It is scheduled to be turned off on June 7, 2025.
The IPv6 support is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out this blog post for an in-depth look at the journey to IPv6.
Latest comment: 1 year ago1 comment1 person in discussion
The Wikipedia Library: Books & Bytes Issue 68, March–April 2025
In this issue we highlight two resource renewals, #EveryBookItsReader, a note about Phabricator, and, as always, a roundup of news and community items related to libraries and digital knowledge.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Editing Team and the Machine Learning Team are working on a new check for newcomers: Peacock check. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are invited to sign up at MediaWiki.org. The deadline to sign up is on May 23, which will be the start date of the test.
Updates for editors
From May 20, 2025, oversighters and checkusers will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. Learn more.
Multiblocks will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please contact the team if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to Special:Block?usecodex=1, and can test the full multiblocks functionality on testwiki. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the help page for more information.
Later this week, the Special:SpecialPages listing of almost all special pages will be updated with a new design. This page has been redesigned to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be previewed at Beta Cluster now, and feedback shared in the task.
The Chart extension is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the deployment timeline.
Wikifunctions will be deployed on May 27 on five Wiktionaries: Hausa, Igbo, Bengali, Malayalam, and Dhivehi/Maldivian. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call functions from Wikifunctions and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function, rather than via a local template.
Later this week, the Wikimedia Foundation will publish a hub for experiments. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement understand new users, how they interact with the internet and how it could affect the Wikimedia movement. Some examples are generated video, the Wikipedia Roblox speedrun game and the Discord bot.
View all 29 community-submitted tasks that were resolved last week. For example, there was a bug with creating an account using the API, which has now been fixed.
Updates for technical contributors
Gadgets and user scripts that interact with Special:Block may need to be updated to work with the new manage blocks interface. Please review the developer guide for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the talk page.
The mw.title object allows you to get information about a specific wiki page in the Lua programming language. Starting this week, a new property will be added to the object, named isDisambiguationPage. This property allows you to check if a page is a disambiguation page, without the need to write a custom function.
User script developers can use a new reverse proxy tool to load javascript and css from gitlab.wikimedia.org with mw.loader.load. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on gitlab.wikimedia.org without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See Tool:Gitlab-content on Wikitech for more information.
The 12th edition of Wiki Workshop 2025, a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can register now.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
A community-wide discussion about a very delicate issue for the development of Abstract Wikipedia is now open on Meta: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. The discussion is open until June 12 at Abstract Wikipedia/Location of Abstract Content, and every opinion is welcomed. The decision will be made and communicated after the consultation period by the Foundation.
Updates for editors
Since last week, on all wikis except the largest 20, people using the mobile visual editor will have additional tools in the menu bar, accessed using the new + toolbar button. To start, the new menu will include options to add: citations, hieroglyphs, and code blocks. Deployment to the remaining wikis is scheduled to happen in June.
The #ifexist parser function will no longer register a link to its target page. This will improve the usefulness of Special:WantedPages, which will eventually only list pages that are the target of an actual red link. This change will happen gradually as the source pages are updated.
This week, the Moderator Tools team will launch a new filter to Recent Changes, starting at Indonesian Wikipedia. This new filter highlights edits that are likely to be reverted. The goal is to help Recent Changes patrollers identify potentially problematic edits. Other wikis will benefit from this filter in the future.
Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading. The feature will be available on both desktop and mobile. Readers of Catalan, Hebrew, and Italian Wikipedias and some sister projects will receive the change between May 21 and mid-June. Readers of other wikis will receive the change later. The goal is to encourage users to read the wikis more. Learn more.
Some users of the Wikipedia Android app can use a new feature for readers, WikiGames, a daily trivia game based on real historical events. The release has started as an A/B test, available to 50% of users in the following languages: English, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish.
The Newsletter extension that is available on MediaWiki.org allows the creation of various newsletters for global users. The extension can now publish new issues as section links on an existing page, instead of requiring a new page for each issue.
The previously deprecated ipblocks views in Wiki Replicas will be removed in the beginning of June. Users are encouraged to query the new block and block_target views instead.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Chart extension is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy Graph extension.
Updates for editors
It is now easier to configure automatic citations for your wiki within the visual editor's citation generator. Administrators can now set a default template by using the _default key in the local MediaWiki:Citoid-template-type-map.json page (example diff). Setting this default will also help to future-proof your existing configurations when new item types are added in the future. You can still set templates for individual item types as they will be preferred to the default template.
Starting the week of June 2, bots logging in using action=login or action=clientlogin will fail more often. This is because of stronger protections against suspicious logins. Bots using bot passwords or using a loginless authentication method such as OAuth are not affected. If your bot is not using one of those, you should update it; using action=login without a bot password was deprecated in 2016. For most bots, this only requires changing what password the bot uses.
From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is async/await syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015.
Scholarship applications to participate in the GLAM Wiki Conference 2025 are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can apply here. Scholarship applications close on June 7th.
An Articles for Creation backlog drive is happening in June 2025, with over 1,600 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Trust and Safety Product team is finalizing work needed to roll out temporary accounts on large Wikipedias later this month. The team has worked with stewards and other users with extended rights to predict and address many use cases that may arise on larger wikis, so that community members can continue to effectively moderate and patrol temporary accounts. This will be the second of three phases of deployment – the last one will take place in September at the earliest. For more information about the recent developments on the project, see this update. If you have any comments or questions, write on the talk page, and join a CEE Catch Up this Tuesday.
Updates for editors
The watchlist expiry feature allows editors to watch pages for a limited period of time. After that period, the page is automatically removed from your watchlist. Starting this week, you can set a preference for the default period of time to watch pages. The preferences also allow you to set different default watch periods for editing existing pages, pages you create, and when using rollback.
Example of a talk page with the new design, in French.
The appearance of talk pages will change at almost all Wikipedias (some have already received this design change, a few will get these changes later). You can read details about the changes on Diff. It is possible to opt out of these changes in user preferences ("Show discussion activity").
Users with specific extended rights (including administrators, bureaucrats, checkusers, oversighters, and stewards) can now have IP addresses of all temporary accounts revealed automatically during time-limited periods where they need to combat high-speed account-hopping vandalism. This feature was requested by stewards.
This week, the Moderator Tools and Machine Learning teams will continue the rollout of a new filter to Recent Changes, releasing it to several more Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: Afrikaans Wikipedia, Belarusian Wikipedia, Bengali Wikipedia, Welsh Wikipedia, Hawaiian Wikipedia, Icelandic Wikipedia, Kazakh Wikipedia, Simple English Wikipedia, Turkish Wikipedia. The rollout will continue in the coming weeks to include the rest of the Wikipedias in this project.
AbuseFilter editors active on Meta-Wiki and large Wikipedias are kindly asked to update AbuseFilter to make it compatible with temporary accounts. A link to the instructions and the private lists of filters needing verification are available on Phabricator.
Lua modules now have access to the name of a page's associated thumbnail image, and on some wikis to the WikiProject assessment information. This is possible using two new properties on mw.title objects, named pageImage and pageAssessments.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
You can nominate your favorite tools for the sixth edition of the Coolest Tool Award. Nominations are anonymous and will be open until June 25. You can re-use the survey to nominate multiple tools.
Foundation staff and technical volunteers use Wikimedia APIs to build the tools, applications, features, and integrations that enhance user experiences. Over the coming years, the MediaWiki Interfaces team will be investing in Wikimedia web (HTTP) APIs to better serve technical volunteer needs and protect Wikimedia infrastructure from potential abuse. You can read more about their plans to evolve the APIs in this Techblog post.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
This week, the Moderator Tools and Machine Learning teams will continue the rollout of a new filter to Recent Changes, releasing it to the third and last batch of Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: Azerbaijani Wikipedia, Latin Wikipedia, Macedonian Wikipedia, Malayalam Wikipedia, Marathi Wikipedia, Norwegian Nynorsk Wikipedia, Punjabi Wikipedia, Swahili Wikipedia, Telugu Wikipedia, Tagalog Wikipedia. The rollout will continue in the coming weeks to include the rest of the Wikipedias in this project.
Updates for editors
Last week, temporary accounts were rolled out on Czech, Korean, and Turkish Wikipedias. This and next week, deployments on larger Wikipedias will follow. Share your thoughts about the project.
Later this week, the Editing team will release Multi Check to all Wikipedias (except English Wikipedia). This feature shows multiple Reference checks within the editing experience. This encourages users to add citations when they add multiple new paragraphs to a Wikipedia article. This feature was previously available as an A/B test. The test shows that users who are shown multiple checks are 1.3 times more likely to add a reference to their edit, and their edit is less likely to be reverted (-34.7%).
A few pages need to be renamed due to software updates and to match more recent Unicode standards. All of these changes are related to title-casing changes. Approximately 71 pages and 3 files will be renamed, across 15 wikis; the complete list is in the task. The developers will rename these pages next week, and they will fix redirects and embedded file links a few minutes later via a system settings update.
View all 24 community-submitted tasks that were resolved last week. For example, a bug was fixed that had caused pages to scroll upwards when text near the top was selected.
Updates for technical contributors
Editors can now use Lua modules to filter and transform tabular data for use with Extension:Chart. This can be used for things like selecting a subset of rows or columns from the source data, converting between units, statistical processing, and many other useful transformations. Information on how to use transforms is available.
The all_links variable in AbuseFilter is now renamed to new_links for consistency with other variables. Old usages will still continue to work.
The latest quarterly Growth newsletter is available. It includes: the recent updates for the "Add a Link" Task, two new Newcomer Engagement Features, and updates to Community Configuration.
Sammi Brie(submissions) with 1,055 round points, mostly from television station articles, including 27 good articles and 9 good topic articles
Everyone who competed in round 3 will advance to round 4 unless they have withdrawn. This table shows all competitors who have received tournament points so far, while the full scores for round 3 can be seen here. During this round, contestants have claimed 4 featured articles, 16 featured lists, 1 featured picture, 9 featured-topic articles, 149 good articles, 27 good-topic articles, and more than 90 Did You Know articles. In addition, competitors have worked on 18 In the News articles, and they have conducted more than 200 reviews.
Remember that any content promoted after 28 June but before the start of Round 4 can be claimed in Round 4. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 14:49, 29 June 2025 (UTC)Reply
Tech News: 2025-27
Latest comment: 1 year ago1 comment1 person in 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.
AbuseFilter maintainers can now match against IP reputation data in AbuseFilters. IP reputation data is information about the proxies and VPNs associated with the user's IP address. This data is not shown publicly and is not generated for actions performed by registered accounts.
Hidden content that is within collapsible parts of wikipages will now be revealed when someone searches the page using the web browser's "Find in page" function (Ctrl+F or ⌘F) in supporting browsers.
A new feature, called Favourite Templates, will be deployed later this week on all projects (except English Wikipedia, which will receive the feature next week), following a piloting phase on Polish and Arabic Wikipedia, and Italian and English Wikisource. The feature will provide a better way for new and experienced contributors to recall and discover templates via the template dialog, by allowing users to put templates on a special "favourite list". The feature works with both the visual editor and the wikitext editor. The feature is a community wishlist focus area.
View all 31 community-submitted tasks that were resolved last week. For example, a bug was fixed that had caused some Notifications to be sent multiple times.
Latest comment: 1 year ago1 comment1 person in discussion
The Wikipedia Library: Books & Bytes Issue 69, May–June 2025
In this issue we highlight a new partnership, Citation Watchlist and, as always, a roundup of news and community items related to libraries and digital knowledge.
Administrator elections will take place this month. Administrator elections are an alternative to RFA that is a gentler process for candidates due to secret voting and multiple people running together. The call for candidates is July 9–15, the discussion phase is July 18–22, and the voting phase is July 23–29. Get ready to submit your candidacy, or (with their consent) to nominate a talented candidate!
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Temporary accounts have been rolled out on 18 large and medium-sized Wikipedias, including German, Japanese, French, and Chinese. Now, about 1/3 of all logged-out activity across wikis is coming from temporary accounts. Users involved in patrolling may be interested in two new documentation pages: Access to IP, explaining everything related to access to temporary account IP addresses, and Repository with a list of new gadgets and user scripts.
Updates for editors
Anyone can play an experimental new game, WikiRun, that lets you race through Wikipedia by clicking from one article to another, aiming to reach a target page in as few steps and in as little time as possible. The project's goal is to explore new ways of engaging readers. Try playing the game and let the team know what you think on the talk page.
Users of the Wikipedia Android app in some languages can now play the new trivia game. Which came first? is a simple history game where you guess which of two events happened earlier on today's date. It was previously available as an A/B test. It is now available to all users in English, German, French, Spanish, Portuguese, Russian, Arabic, Turkish, and Chinese. The goal of the feature is to help engage with new generations of readers.
Users of the iOS Wikipedia App in some languages may see a new tabbed browsing feature that enables you to open multiple tabs while reading. This feature makes it easier to explore related topics and switch between articles. The A/B test is currently running in Arabic, English, and Japanese in selected regions. More details are available on the Tabbed Browsing project page.
A new feature related to Template Recall and Discovery will be deployed later this week to all Wikimedia projects: a template category browser will be introduced to assist users in finding templates to put in their “favourite” list. The browser will allow users to browse a list of templates which have been organised into a given category tree. The feature has been requested by the community through the Community Wishlist.
It is now possible to access watchlist preferences from the watchlist page. Also the redundant button to edit the watchlist has been removed.
As part of MediaWiki 1.44 there is now a unified built-in Notifications system that makes it easier for developers to send, manage, and customize notifications. Check out the updated documentation at Manual:Notifications, information about migration in T388663 and details on deprecated hooks in T389624.
WikidataCon 2025, the conference dedicated to Wikidata is now open for session proposals and for registration. This year's event will be held online from October 31 – November 02 and will explore on the theme of "Connecting People through Linked Open Data".
The administrator elections process has officially started! Interested editors are encouraged to self-nominate or arrange to be nominated by reviewing the instructions at Wikipedia:Administrator elections/July 2025/Candidates.
Here is the schedule:
July 9–15 - Call for candidates
July 18–22 - Discussion phase
July 23–29 - SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. A separate user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Featured templates, a new feature related to Template Recall and Discovery will be deployed this week to all Wikimedia projects: With this feature, editors will be able to quickly access a list of templates that are likely to be useful. These templates will be displayed in a list, under the "featured" tab of the template discovery interface. Administrators can define the list via the Community Configuration interface. The feature fulfills a request by the community through the Community Wishlist.
View all 31 community-submitted tasks that were resolved last week. For example, the request to add Malayalam fonts in the Wikisource Book Export Tool was resolved and now, the rendering of Malayalam letters in exported Wikisource books are accurate.
WikiIndaba 2025 scholarship application and program submission is open until 23:59 GMT on July 20. WikiIndaba is a regional conference for African Wikimedians both on the continent and in the diaspora to unite and grow together. Submit your scholarship application and program proposal now!
WikiCon Brasil 2025 will take place on July 19-20 in Salvador, Bahia, Brazil. The Brazilian community members are encouraged to register and attend!
On July 23, we will start the voting phase. The candidate subpages will close again to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's totals during the election. You must be extended confirmed to vote.
Once voting concludes, we will begin the scrutineering phase, which will last approximately four days, or perhaps a little longer. Once everything is certified, the results will be posted on the results page (you may want to watchlist this page) and transcluded to the main election page. In order to be granted adminship, a candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and must also have received a minimum of 20 support votes. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
The Translation Suggestions feature in the Content Translation tool now has another level of article filters added to the "... More" category. Translators who use the Suggestions feature can now select and receive article suggestions that are customized to geographical locations of their interest using the new "Regions" filter.
Administrators can now limit "Add a Link" to newcomers. The "Add a Link" Structured Task helps new account holders start editing, but some communities have requested the ability to restrict it to its intended audience: newcomers. Administrators can configure this setting within the Community Configuration feature.
For AbuseFilter editors on some wikis, it is now possible to filter edits based on the RevertRisk score of the edit being attempted. It is only populated if the action being evaluated is an edit. For more information, please see the ORES/AbuseFilter variables documentation.
The Beta Cluster wikis have been moved from beta.wmflabs.org to beta.wmcloud.org. Users may need to update URLs in any tools, or in their password managers. Any related issues can be reported in the task.
WikiCite 2025 will take place from 29–31 August, both online and in-person in Bern, Switzerland. The event's goals are to reconnect communities, institutions, and individuals working with open citations, bibliographic data, and the Wikidata/Wikibase ecosystem. Registration is open and the call for proposals will be announced soon.
In the voting phase, the candidate subpages will close to public questions and discussion, and everyone who qualifies to vote will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's vote total during the election. The suffrage requirements are similar to those at RFA.
Once voting concludes, we will begin the scrutineering phase, which will last for approximately four days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Community Tech team will be focusing on wishes related to Watchlists and Recent Changes pages, over the next few months. They are looking for feedback. Please read the latest update, and if you have ideas, please submit a wish on the topic.
Updates for editors
The Wikimedia Commons community has decided to block cross-wiki uploads to Wikimedia Commons, for all users without autoconfirmed rights on that wiki, starting on August 16. This is because of widespread problems related to files that are uploaded by newcomers. Users who are affected by this will get an error message with a link to the less restrictive UploadWizard on Commons. Please help translating the message or give feedback on the message text. Please also update your local help pages to explain this restriction.
On wikis with temporary accounts enabled and Meta-Wiki, administrators may now set up a footer for the Special:Contributions pages of temporary accounts, similar to those which can be shown on IP and user-account pages. They may do it by creating the page named MediaWiki:Sp-contributions-footer-temp.
Wikimania 2025 will run from August 6–9. The program is available for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please register for a free virtual ticket. For example, you may be interested in technical sessions such as:
The MediaWiki Users and Developers Conference, Fall 2025 will be held 28–30 October 2025 in Hanover, Germany. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend.
Latest comment: 1 year ago1 comment1 person in discussion
Hello everyone, and welcome to the 27th issue of the Wikipedia Scripts++ Newsletter, covering all our favorite new and updated user scripts since 2025! Boy, does it feel good to kick off the year with an issue. Yep, it's been a year since we cleared out the 2022-2024 backlog with issues 23 and 24! Good times. Though in this case "a year" just means... 6 months? 😯 The salience of whatever joke I was planning to make here has vanished speedily. Aaron Liu (talk) 21:00, 31 July 2025 (UTC)Reply
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
WikiTextExpander by Polygnotus, is this edition's featured script. At the click of a configurable hotkey, this script will find and replace or link a configurable list of phrases within the selected text in all source editors (even in the comment/reply field!). Besides allowing the quick insertion of templated messages, this script greatly mitigates the WP:WTF? problem by providing both the legibility of familiar words and the convenience of shortcuts. And to those asking, the capitalization of "Wikitext" as "WikiText" was a necessary sacrifice for far-more-memorable acronymy.
Updated scripts
CanonNi: AlertAssistant has been fixed and rewritten using OOUI instead of Twinkle's Morebits. Such modern, very tool. (Do note that the maintainer has since become inactive.)
NguoiDungKhongDinhDanh/AjaxLoader has been updated to use modern JS APIs that replace the browser's URL bar with the link you clicked on to load in place. The "back" (and "forward") buttons also work now. Cool, innit?
andrybak: Unsigned helper no longer shows an error when the message to sign was added in the earliest 50 revisions of a page's history. This is especially relevant to pages with short histories.
BilledMammal/Move+ needs updating to order list of pages handle lists of pages to move correctly regardless of the discussion's page, so that we may avoid repeating fiasco history.
Requested scripts
We need scripts that...
allow sorting lists of citations such as by URI or other identifier
automatically convert the capitalization of citations' titles
collect a list of discussion participants and generate a ping list
In breaking m:Tech/News, Gadgets can now include .vue files. This makes it easier to develop modern user interfaces using Vue.js, in particular using Codex, the official design system of Wikimedia. Codex icons are now also available. The documentation has examples.
New scripts
Appo/Globstory integrates OpenHistoryMap, updating the map whenever hovering/clicking on a location or year, the latter of which changes the map to be (hopefully) accurate to the year selected. It's pretty interesting.
linkinfo Somewhat similar to WP:NavPops, Awesome Aasim/linkinfo(pictured) provides a collection of links to replace the right-click context menu, presented beautifully.
PreviousDiscussions provides a link to search for your username on subpages of another user's userpage and talkpage conveniently.
Twineeea/noRedLinks brings you to the "read" instead of the "create" tab when you visit a red link. Contemplate life's mysteries as you stare into the blank! Deeply.
No, this is not going to be the enduring tradition of S++ for the future. This was meant to be a joke for the special occasion on the first day of the fourth month but was delayed by four months because I'm lazy.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Editors can now enable the User Info card. This feature adds an icon next to usernames on history pages and similar user-contribution log pages. When you tap or click on the icon, it displays data related to that user account such as the number of edits, reverted edits, blocks, and more. It's part of a broader project to make it easier for moderators to evaluate account trustworthiness. The feature can be enabled in your global preferences, and later this week it will be available in local preferences.
Everybody is invited to share comments on Collaborative Contributions, a project recently launched by the Connection team. The project aims to create a new way to display the impact of collaborative editing activities (such as edit-a-thons, backlog drives, and WikiProjects) on the wikis. Post your comments on the project talk page.
Administrators can now define the default block duration for temporary accounts. To do that, they need to create a page named MediaWiki:Ipb-default-expiry-temporary-account and use a value defined in MediaWiki:Ipboptions. This allows administrators to easily block temporary accounts for 90 days, which is functionally equivalent to an indefinite block. The advantage of this solution is that it does not clutter Special:BlockList. More documentation is available.
Gadgets can now include .vue files. This makes it easier to develop modern user interfaces using Vue.js, in particular using Codex, the official design system of Wikimedia. Codex icons can be loaded through the gadget definition. The documentation has examples. For user scripts that use Vue.js, an API module now exists to load Codex icons.
Module developers can now use a Lua interface to simplify the preparation of Lua modules for translation on Meta-Wiki. This improvement makes it easier for translators to find and edit module strings without dealing with raw Lua code. It helps prevent mistakes that could break the module during translation. Module developers and translators are invited to watch the demo video, read more about translatable modules to understand how it works, refer to Meta-Wiki's Module:User Wikimedia project for example usage, and share their feedback on how well it addresses the challenges in their workflow. The interface still has some performance issues, so it should not be used in widely used modules yet.
Developers of external tools that connect to Wikimedia pages must set a user-agent that complies with the user-agent policy. This policy will start to be more strongly enforced in August because of external crawlers that are overusing Wikimedia's resources. Tools that are hosted on Wikimedia's Toolforge or Cloud VPS will not be affected by this for now, but should still set a user-agent. More technical details are available, and related questions are welcome in that task.
Parsoid Read Views is going to be rolling out to some smaller Wikipedias over the next few weeks, following the successful transition of Wikivoyages and Wiktionaries to Parsoid Read Views. For more information, see the Parsoid/Parser Unification project page.
Wikimania 2025 will run from August 6–9. The program is available for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please register for a free virtual ticket. For example, you may be interested in technical sessions such as:
Following a request for comment, there is a new policy outlining the granting of permissions to view the IP addresses of temporary accounts. Temporary account deployment on the English Wikipedia is currently scheduled for September 2025, and editors can request access to the permission ahead of time. Admins are encouraged to keep an eye on the request page; there will likely be a flood of editors requesting the permission when they realize they can no longer see IP addresses.
South Asia (WP:CT/SA) is designated a contentious topic. The topic area is specifically defined as All pages related to the region of South Asia (India, Pakistan, Afghanistan, Sri Lanka, Bangladesh and Nepal), broadly construed, including but not limited to history, politics, ethnicity, and social groups.
Wikimania 2025 is happening in Nairobi, Kenya, and online from August 6 to August 9. This year marks 20 years of Wikimania. Interested users can join the online event. Registration for the virtual event is free and will remain open throughout Wikimania. You can register here now.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
The WikiEditor toolbar now includes its keyboard shortcuts in the tooltips for its buttons. This will help to improve the discoverability of this feature.
The search bar on the Minerva skin (mobile) has been updated to use the same type-ahead search component that is used on the Vector 2022 skin. There are no changes in search functionality but there are minor visual changes. Specifically, the close-search button has been changed from an "X" to a back arrow. This helps to distinguish it from the other "X" button that is used to clear any text.
Editors on some wikis will see a new toggle for "Group results by page" on watchlist, related changes, and recent changes pages. This is an A/B experiment that is planned to start on August 11, and will run for 3–6 weeks on the Bengali, Chinese, Czech, French, Greek, Portuguese, and Urdu Wikipedias. The experiment will examine how making this feature more discoverable might affect editors' ability to find the edits they are looking for.
The multiwiki datasets of Unicode data have been moved to Category:Unicode Module Datasets on Wikimedia Commons, to follow the idea of "One common data source, multiple local wikis". Most wikis have been updated to use the Commons version. You can ask questions at the talkpage.
Lua code can add warnings when something is wrong, by using the mw.addWarning() function. It is now possible to add more than one warning, instead of new warnings replacing old ones. If you maintain a Lua module that used warnings, you should check it still works as expected.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Later this week, people who are logged-in and have the "Discussion tools" Beta Feature enabled will gain the ability to "Thank" individual comments directly from talk pages, rather than needing to navigate to page history. Learn more about this feature.
An A/B test comparing two versions of the desktop donate link launched on testwiki on 12 August and on English Wikipedia 14 August for 0.1% of logged out users on the desktop site. The experiment will run for three weeks, ending on 12 September.
An A/A test to measure the baseline for reader retention was launched 12 August using Experimentation Lab. This measures the percentage of users who revisit a wiki after their initial visit over a 14-day period. No visual changes are expected. The experiment will run through 31 August.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
Template authors can now use additional CSS properties, since the CSS sanitizer used by TemplateStyles was updated. For example: width: fit-content; ruby-align; relative units such as lh; and custom strings in list-style-type. These improvements are a Community Wishlist wish.
On large wikis, the default time period to display edits from, within the Special:RecentChanges page, has been changed from 7 days to 1 day. This is part of a performance improvement project. This should have no user-facing impact due to the quantity of edits on these wikis.
Wikimedia Commons videos were not shown in the Videos tab in Google Search. The problem was investigated and reported to Google who have now fixed the issue.
One new wiki has been created: a Wiktionary in Betawi (wikt:bew:)
Two fields of the recentchanges database table are being removed. rc_new and rc_type are being removed in favor of rc_source. Queries to these older fields will start to fail starting this week and developers should use rc_source instead. These older fields were deprecated over 10 years ago and should not be in use. This is part of work to improve the performance and stability of queries to the recentchanges table.
The latest quarterly Language and Internationalization Newsletter is now available. This edition includes: support for new languages in MediaWiki and translatewiki; the start of the Language Onboarding and Development project to help support the growth of new and small wikis; updates on research projects; and more.
Meetings and events
The next Language Community Meeting is happening soon, August 29th at 15:00 UTC. This week's meeting will cover: the Avro keyboard developers from Wikimedia Bangladesh, who were recently awarded a national award for their contributions to this keyboard; and other topics.
Latest comment: 1 year ago1 comment1 person in discussion
The fourth round of the 2025 WikiCup ended on 29 August. The penultimate round saw three contestants score more than 800 points:
BeanieFan11(submissions) with 1,175 round points, mainly from sports-related articles, including 17 good articles, 27 did you know articles, and 9 in the news articles
AirshipJungleman29(submissions) with 854 round points, mostly from a high-scoring featured article on the Indian leader Rani of Jhansi and two good articles, in addition to 13 featured and good article reviews
Everyone who competed in Round 4 will advance to Round 5 unless they have withdrawn. This table shows all competitors who have received tournament points so far, while the full scores for Round 4 can be seen here. During this round, contestants have claimed 9 featured articles, 12 featured lists, 98 good articles, 9 good topic articles, more than 150 reviews, nearly 100 did you know articles, and 18 in the news articles.
In advance of the fifth and final round, the judges would like to thank every contestant for their hard work. As a reminder, any content promoted after 29 August but before the start of Round 5 can be claimed in Round 5. In addition, note that Round 5 will end on 31 October at 23:59 UTC. Awards at the end of Round 5 will be distributed based on who has the most tournament points over all five rounds, and special awards will be distributed based on high performance in particular areas of content creation (e.g., most featured articles in a single round).
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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges – Cwmhiraeth(talk·contribs), Epicgenius(talk·contribs), Frostly(talk·contribs), Guerillero(talk·contribs) and LeeVilenski(talk·contribs) – are reachable on their talk pages. Good luck!
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Editing team wants to compile a list of templates, jargon terms, and policies used in edit summaries when a copyright violation is removed. This will help them identify the number of edits reverted due to copyright issues. We invite community members from the following Wikis to list these terms in T402601, or to share their list with Trizek_(WMF): Arabic Wikipedia, Czech Wikipedia, German Wikipedia, English Wikipedia, Spanish Wikipedia, Persian Wikipedia, French Wikipedia, Hebrew Wikipedia, Indonesian Wikipedia, Italian Wikipedia, Japanese Wikipedia, Korean Wikipedia, Dutch Wikipedia, Polish Wikipedia, Portuguese Wikipedia, Turkish Wikipedia, Ukrainian Wikipedia, Vietnamese Wikipedia, Chinese Wikipedia. This project is open until September 9th 2025.
Updates for editors
The CampaignEvents extension has been enabled for all Wikisources. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: Event Registration, Collaboration List, and Invitation List. To request the extension for your wiki, visit the Deployment information page.
The lists in the footer of the editing interface, such as "Templates used on this page," will now be organized into columns when there is enough space. This enhancement minimizes scrolling when editing lengthy articles on Wikipedia.
On September 3rd, 2025 we will increase the sampling percentages of our group by toggle experiment of the Special:RecentChanges, Special:Watchlist, and Special:RelatedChanges pages on the Chinese, French, and Portuguese Wikipedias to 100 percent, allowing more editors to be part of this experiment. This adjustment is intended to ensure we have sufficient data to make informed decisions when evaluating the experiment results.
Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading on English Wikipedia beginning the week of September 22. The feature will be available on both desktop and mobile. All non-English wikis received this change in June and July. The goal is to make it easier for users to find articles. Learn more.
Wikifunctions now has a new capability called "lightweight enumeration types", an enumeration type is simply a fixed set of values that's in the type's definition. This capability makes it quick and easy to define such a type, and allows for the reuse of values that are already present in Wikidata. Here is a newsletter to learn more.
The latest Readers Newsletter is now available. This edition includes: the formation of two new teams — Reader Growth and Reader Experience; insights into declining pageviews and account creations; highlights from the Wikimania Nairobi panel on improving the reading experience; upcoming experiments to engage new and existing readers; and more.
An RfC is open on whether use of emojis with no encyclopedic value in mainspace and draftspace (e.g., at the start of paragraphs or in place of bullet points) should be added as a criterion under G15.
An RfC is in progress to amend the structure, rules, and procedures of the Arbitration Committee election and resolve any issues not covered by existing rules.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
The Editing team is working on a new check: Paste check. This check informs newcomers who paste text into Wikipedia that the content might not be accepted. This check is an effort to increase the likelihood that the new content people are adding to Wikipedia is aligned with the Movement's commitment to offering information under a free content license. This check will soon be tested at a few wikis. If your community is interested in this test, please tell us in this task, or contact the team.
Updates for editors
Later this week, users of the "⧼codemirror-beta-feature-title⧽" beta feature will be able to use a linting tool to see errors or other potential problems in wikitext in real time. See the help page for more information.
When browsing a wiki (like en.wikipedia.org), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an "m" domain (like en.m.wikipedia.org). Over the next three weeks, MediaWiki will start displaying the mobile version to mobile devices directly on the standard domain, without this redirect. This change does not affect existing m-dot URLs, or the "Desktop view" opt-out. Learn more.
When an edit changes the categories of a page, the changes to the category membership counts are now happening asynchronously. This improves the speed of saving edits, especially when moving many pages to or from the same category, and reduces the risk of site outages, but it means that the counts can show outdated information for a few minutes.
Edits on Wikidata to qualifiers (properties and values) and references (properties and values) in a Wikidata item statement will now not add entries to the RecentChanges or Watchlist pages on all other Wikis. This is a temporary change to improve performance while other solutions are created. Wikidata's own pages remain unchanged. Learn more.
Japanese-language wikis have had a major upgrade to the way that search works. The new search should generally give more accurate and more relevant search results.
The RFC phase of the July 2025 administrator elections has started. There are 10 RFCs for consideration. You can participate in the RFC phase at Wikipedia:Administrator elections/July 2025/RFCs.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 1 year ago1 comment1 person in 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.
Updates for editors
References lists that are made using the <references/>tag will now automatically display with columns in Vector 2022 when readers are using its 'standard' settings for text-size and page-width.
Starting in the week of October 6, on small wikis and medium wikis that have the CampaignEvents extension enabled, all autoconfirmed users will be able to use Event Registration as an organizer. No changes will be made for large wikis unless requested in Phabricator. This change is being made to make it easier for more people to use Event Registration, especially on wikis that are less likely to have policies related to the Event Organizer right. Learn more.
Users that search using regular expressions (regex) can now use additional features including:
for the intitle: keyword: metacharacters for start-of-line (^) and end-of-line ($) anchors
for both intitle: and insource: keywords: shorthand character classes for digits (\d), whitespace (\s), and word characters (\w); and escape codes for line feed (\r), newline (\n), tab (\t), and unicode (e.g. \uHHHH).
When you search for text that looks like an IP, the system will now show search results. It used to take you to the contributions for that IP instead of showing search results.
View all 24 community-submitted tasks that were resolved last week. For example, a bug was fixed that affected users who used the page-tabs to switch from wikitext editing of a section into the visualeditor.
Updates for technical contributors
The MediaWiki Interfaces team is redesigning the Wikimedia REST API Sandbox with Codex. If you have feedback on improvements for the API documentation or what makes developer experiences smooth (or frustrating), you’re invited to join an upcoming discovery interview, or leave feedback onwiki. Learn more.
Edits to Wikidata aliases (an alternative name for an item or a property) will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. Learn more.
The new Unicode 17.0 version has been released. The datasets on Commons for the Module:Unicode data have been updated. Wikipedias that do not use the Commons datasets should either update their own data or switch to the Commons datasets.
Users of the Wikimedia Enterprise Structured Contents endpoints can now access Parsed Tables. The new Parsed Tables feature extracts and represents Wikipedia tables in structured JSON. This improves machine accessibility as part of the Structured Contents initiative. Structured Contents output is freely available through the On-demand API, or through Wikimedia Cloud Services.
A dataset of English Wikipedia biographical information from Wikimedia Enterprise has been published on Kaggle, for evaluation and research. This provides structured data from more than 1.5 million biographies, including birth and death dates, education, affiliations, careers, awards, and more (from a June 2024 snapshot).
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
On September 24th at 15:00 UTC, all Wikimedia sites users will experience a brief read-only period due to a scheduled datacenter server switchover. The Wikimedia Foundation's Site Reliability Engineering (SRE) team will redirect all traffic from one primary server to its backup. You can listen to the switchover using the "Listen to Wikipedia" tool, where you will hear edits stop for a few minutes during the read-only phase, then resume. This twice-yearly datacenter server switchover ensures reliability by testing the backup datacenter, so that our sites can stay online even if the primary datacenter fails. You can read more about the process on the Diff blog.
Updates for editors
Editors of 60 more Wiktionaries will soon be able to call functions from Wikifunctions and integrate them into their pages. A function takes one or more inputs and transforms them into a desired output, like adding numbers, converting miles to meters, calculating elapsed time, or declining a word into a case. They will join the other 65 Wiktionary language editions, which already have access to embedded Wikifunctions calls. Later this year, plans are in place to expand to more Wiktionaries and the Incubator.
A new parser function has been added: {{#contentmodel}}. Template editors and admins can use it to get the localized or canonical name of the content model of a specific page. The function makes it easier to create and edit system messages, such as MediaWiki:editinginterface, even when you switch types of pages, like wiki, JavaScript, CSS or JSON page.
Adding or editing a DISPLAYTITLE for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the {{DISPLAYTITLE}} would no longer have the literal text "DISPLAYTITLE" or its localized variant added to their articles. A list of pages that may have been affected and might need cleanup is documented in this ticket.
Beta users of the Wikipedia Android app can now try the redesigned Activity tab, which replaces the Edits tab. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging.
Wikifunctions users can now import many essential facts involving geo-coordinates, quantities and time values from Wikidata. This is made possible by the creation of Wikifunctions types for these values, which makes them available for use by functions in Wikifunctions. Learn more about how this works in this video and Wikifunctions' August 1 newsletter (for quantities) and August 22 newsletter (for geo-coordinates).
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
A major software upgrade has been made to Phabricator. The update introduces performance improvements, a refreshed search interface, enhancements to Maniphest task search, updates to user profile pages and project workboards, new Herald automation features, as well as general text input, mobile experience improvements and more.
Updates for editors
The Community Tech team will release the new Community Wishlist extension on October 1, that will improve the way wishes will be submitted. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will also be possible to support individual wishes again, as requested by the community in many instances. The old system will be retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system. You can read more about this in the latest update or you can consult the current documentation on MediaWiki.
As announced on Diff blog, the production trial of the hCaptcha service for bot detection has begun. The trial is currently using hCaptcha to protect account creation on Chinese, Persian, Portuguese, Indonesian, Japanese, and Turkish Wikipedias, where it will replace our existing CAPTCHA (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges.
The CampaignEvents extension has been deployed to Wikimedia Commons. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. On Commons, anyone who is a registered user can use it as an event participant. To use it as an organizer, someone needs to have the event organizer right.
On wikis using the Mentorship system, communities can now opt experienced editors out of Mentorship through Special:CommunityConfiguration/Mentorship. Within this setting, communities may define thresholds, based on edit count and account age, to decide when an editor is considered experienced enough to no longer receive Mentorship.
The Editing Team and the Machine Learning Team are working on a new check for newcomers: Tone check. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Tone language model for the following languages: Arabic, Czech, German, Hebrew, Indonesian, Dutch, Polish, Russian, Turkish, Chinese, Farsi, Italian, Norwegian, Romanian and Latvian. Users from these wikis interested in reviewing this model are invited to sign up at MediaWiki.org. The deadline to sign up is on October 3, which will be the start date of the test.
The rollout of multiblocks had the side effect that non-active block logs may have been shown on Special:Contributions and on blocked users' user and user_talk pages. This issue will be fully resolved in a few days. As part of the fix, messages prefixed with sp-contributions-blocked-notice will be removed and replaced with those prefixed with blocked-notice-logextract in a few weeks. Please help translate the new messages and update any local overrides if needed.
There was a bug with links added using visual editor if they included characters such as [ ] | after the fragment identifier (#). They were not encoded properly creating an incorrect link. This has been fixed.
One new wiki has been created: a Wikiquote in Malay (q:ms:)
View all 21 community-submitted tasks that were resolved last week. For example, the User Info Card now displays currently active global lock/blocks.
Updates for technical contributors
Later this week, editors using Lua modules will be able to use the mw.title.newBatch function to look up the existence of up to 25 pages at once, in a way that only increases the expensive function count once.
A new Unsupported Tools Working Group has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to the Product & Technology Advisory Council (PTAC). The working group will help prioritize and review requests for support of unmaintained extensions, gadgets, bots, and tools. For the first cycle, the group will be prioritizing an unsupported Wikimedia Commons tool.
Latest comment: 1 year ago1 comment1 person in 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.
Weekly highlight
Paste Check is a new Edit Check feature to help avoid and fight copyright violations. When editors paste text into an article, Paste Check prompts them to confirm the origin and licensing of the content. Starting Wednesday, 8 October, 22 wikis will test Paste Check. Paste Check will help new volunteers understand and follow the policies and guidelines necessary to make constructive contributions to Wikipedia projects.
Updates for editors
Mobile devices will receive mobile articles directly on the standard domain (like en.wikipedia.org), instead of via a redirect to an "m" domain (like en.m.wikipedia.org). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the "Desktop view" opt-out remain available. Learn more.
New date filters, creationdate: and lasteditdate:, are now available in the wiki search engine. This allows users to filter search results by a page's first or last revision date. The filters support comparison operators (e.g. >2024) and relative dates (e.g. today-1d), making it easier to find recently updated content or pages within specific age ranges.
Wikifunctions now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created a Latin declination table that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see an example output. If you need any help or have any feedback, please contact the Wikifunctions Team.
An edit link will now appear inside the categories box on article pages for logged in users, which will directly launch the VisualEditor category dialog.
View all 34 community-submitted tasks that were resolved last week. For example, there was a problem downloading pdf files last week and that has been resolved.
Updates for technical contributors
The field rev_sha1 in the revision database table is being removed in favor of content_sha1 in the content database table. See the announcement for more information.
The Reader Experience team will roll out Dark Mode user interface on all Wikimedia sites on October 29, 2025. All anonymous users of Wikimedia sites will have the option to activate a color scheme that features light-colored text on a dark background. This is designed to provide a more comfortable reading experience, especially in low-light situations. Template authors and technical contributors are encouraged to learn how to make pages ready for Dark mode and address any compatibility issues found in templates in their wiki before the enablement. Please contact the Web team for questions or any support on this talk page before the enablement.
Starting on Monday, October 6, API endpoints under the rest.php path will be rerouted through a new internal 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 the Service Ops team board.
After a motion, arbitration enforcement page protections no longer need to be logged in the AELOG. A bot now automatically posts protections at WP:AELOG/P. To facilitate this bot, protection summaries must include a link to the relevant CT page (e.g. [[WP:CT/BLP]]), and you will receive talk page reminders if you forget to specify the contentious topic but otherwise indicate it is an AE action.
Latest comment: 11 months ago1 comment1 person in 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.
Weekly highlight
Last week, improvements to account security and two-factor authentication (2FA) features were enabled across all wikis. These changes include user interface improvements for Special:AccountSecurity, the support of multiple 2FA methods via authenticator apps and portable security keys (previously users could only enable one method), and a new Recovery Codes module which facilitates fewer account lockouts due to lost two-factor apps and devices. As part of the Account Security project, work is continuing through the rest of 2025 on further user experience improvements, and support for passkeys as an alternate second factor.
Updates for editors
Another part of the Account security project is making 2FA generally available to all users. Along with editors with advanced privileges, such as administrators and bureaucrats, 40% of editors now have access to 2FA. You can check if you have access at Special:AccountSecurity. Instructions for activation are on the linked page. The plan is to continue increasing availability if it is determined that the user support capabilities are able to support global usage.
This week, users at wikis where talk page Usability Improvements are already available by default (everywhere except the 12 wikis listed in T379264) will gain the ability to Thank a comment directly from the talk page it appears on. Before this change, Thanking could only be done by visiting the revision history of the talk page. You can learn more about this change.
Users who have not verified their email address will soon be receiving monthly Notification reminders to do so. This is because users who have verified their email can more easily recover their account. These reminders will not be sent if the user is inactive or removes the unverified email from their account.
View all 21 community-submitted tasks that were resolved last week. For example, a fix was made for an occasional error with saving translated paragraphs in the Content Translation tool, and the related error messages are now easier to see.
Updates for technical contributors
The Unsupported Tools Working Group has chosen Video2Commons as the first tool for its pilot cycle. The group will explore ways to improve and sustain the tool over the coming months. Learn more on Meta.
Latest comment: 11 months ago1 comment1 person in 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.
Updates for editors
To optimize how user data is stored in our databases, the saved preferences of users who haven't logged in for over five years and have fewer than 100 edits will be cleared. When those users return, default settings will apply.
View all 20 community-submitted tasks that were resolved last week. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed.
Updates for technical contributors
The work to reroute all traffic to API endpoints under the rest.php route through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to the Service Ops team board.
Edits to Wikidata references or qualifiers will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged.
Traffic report: One click after another Serial-killer miniseries, deceased scientist, government shutdowns and Sandalwood hit "Kantara" crowd the tubes.
Latest comment: 11 months ago1 comment1 person in 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.
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 can read more on the project page.
Autoconfirmed users on small and medium wikis with the CampaignEvents extension can now use Event 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 were resolved 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.
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 the Special:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the project launch page.
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 the REST Sandbox. See the MediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
A dedicated changelog 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, please join 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 from Q130635582. 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.
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 2 featured articles, 4 featured lists, 106 good articles, 5 good topic articles, 178 article reviews, 76 did you know articles, and 9 in 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 to sign 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!
Latest comment: 11 months ago1 comment1 person in 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.
Updates for editors
Administrators will now find that Special: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).
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.
Scribunto modules can now be used to generate 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.
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.
Users with large watchlists have long faced timeouts when editing Special: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. A community wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish!
View all 31 community-submitted tasks that were resolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query.
Updates for technical contributors
Since 2019 the Wikimedia URL Shortener at https://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 HTML class="title-shortlink". The /s/ URLs will keep working.
On Thursday, October 30, the MediaWiki Interfaces and SRE 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 the Service 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.
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 in a Diff blog post.
Latest comment: 10 months ago1 comment1 person in 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.
Updates for editors
Example of a talk page with the new design, in French.
MediaWiki can now display a page indicator automatically while a page is protected. This feature is disabled by default. It can be enabled by community request.
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.
Wikivoyage wikis can use colored 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.
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.
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.
View all 27 community-submitted tasks that were resolved last week. For example the inability to lock accounts on mobile sites has been fixed.
The JWT subject field in OAuth 2 access tokens will soon change from <user id> to mw:<identity type>:<user id>, where <identity type> is typically CentralAuth: (for SUL wikis) or local:<wiki id> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the sessionJwt cookie more similar. Old access tokens will still work.
A REL1_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.
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.
Latest comment: 10 months ago1 comment1 person in 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.
Updates for editors
The Reader Experience team is experimenting with reading 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 the Account 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 the Parser 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 the Extension: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 the Content Transform Team in Phabricator.
Unsupported Tools: Several issues with Video2Commons 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 the Phabricator 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 email hackathon@wikimedia.org.
Latest comment: 10 months ago1 comment1 person in 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.
Updates for editors
Last week, the Wikimedia 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 for cxfcnmt 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.
Later this week, users of the "⧼codemirror-beta-feature-title⧽" beta feature will have syntax highlighting available in DiscussionTools. This requires that the "Enable editing tools in source mode" preference be set.
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 as Collaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcoming learning session to see the new feature in action and share your feedback.
View all 24 community-submitted tasks that were resolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed.
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 the recruitment survey.
The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for format=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).
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 or https://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review the Data Access and Request a Query pages for details and assistance on alternative access methods.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 10 months ago1 comment1 person in 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.
Updates for editors
The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's project page.
The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See Phabricator.
Add a link will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact Trizek (WMF).
View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed.
The Wikimedia Foundation is in the early stages of exploring approaches to Article guidance. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to learn more about the project, and share their thoughts on the talk page.
On December 9, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's totals during the election. You must be extended confirmed to vote.
Once voting concludes, we will begin the scrutineering phase, which typically lasts between a couple days and a week. Once everything is certified, the results will be posted on the results page (you may want to watchlist this page) and transcluded to the main election page. In order to be granted adminship, a candidate who has not been recalled must have received at least 70.0% support, calculated as Support / (Support + Oppose), and must also have received a minimum of 20 support votes. A candidate that has been recalled must have at least 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Starting on November 4, the IP addresses of logged-out editors are no longer being publicly displayed. Instead, they will have a temporary account associated with their edits.
Administrators will now find that Special: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). T382958
An Articles for Creation backlog drive is happening in December 2025, with over 1,000 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!
Latest comment: 10 months ago1 comment1 person in 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.
Weekly highlight
Anybody who wishes to secure their user account can now use two-factor authentication (2FA). This is available to all registered users of all Wikimedia projects. This is part of the Account Security initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions.
Updates for editors
Following last week's deployments, the Add a link feature, which allows editors to add suggested links during editing, will be available to an additional 33 Wikipedias starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact Trizek (WMF).
Last week, the Search Platform team added transliterated as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script are now rewritten into Georgian script to look for more matches. For example, searching for either bedniereba or бедниереба will now suggest the existing article about ბედნიერება ("happiness"). You can recommend other languages where transliterated suggestions would be useful on Phabricator for future development.
Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find more details about the project.
Later this week, the Reader Growth team will launch a mobile web experiment to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias.
The Wikipedia Year in Review 2025, a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025.
A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications.
View all 23 community-submitted tasks that were resolved last week. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved.
Updates for technical contributors
Starting this week, users of the "⧼codemirror-beta-feature-title⧽" beta feature will have CodeMirror as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of CodeEditor. With this, the linters will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience.
Developers are encouraged to take the 2025 Developer Satisfaction Survey, which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated.
In the voting phase, the candidate subpages close to public questions and discussion, and everyone who qualifies to vote has a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's vote total during the election. The suffrage requirements are similar to those at RFA.
Once voting concludes, we will begin the scrutineering phase, which will last for a few days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a non-recall candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Recall candidates must achieve 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 9 months ago1 comment1 person in 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.
Updates for editors
View all 18 community-submitted tasks that were resolved last week. For example, one of the fixes addressed an issue for temporary accounts adding an external URL, which triggered an hCaptcha request in more cases than intended, and did not display the required popup on the first attempt to publish the edit.
Updates for technical contributors
To improve database and site performance, external links to Wikimedia projects will no longer be stored in the database. This means they will not be searchable in Special:LinkSearch, will not be checked by the Spam Blacklist or AbuseFilter as new links, and will not be in the externallinks table on database replicas. In the future this may be extended to other highly-linked trusted websites on a per-wiki basis, such as Creative Commons links on Wikimedia Commons.
Latest comment: 9 months ago1 comment1 person in 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.
Updates for editors
From January, edit filters can be set to automatically suppress their details such as rules and list of attempted edits and actions. This will help oversighters use edit filters to prevent doxxing or other suppressible material.
The next issue of Tech News will be sent out on 12 January 2026 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year.
View all 16 community-submitted tasks that were resolved last week. For example, the crash that occurred when tapping "First Steps" in the Wikipedia Android Year in Review has now been fixed, and the feature opens as expected.
Updates for technical contributors
Interface elements such as diffs and categories generated by MediaWiki used to have the attribute data-mw="interface" to distinguish from wiki content. The attribute has been replaced with data-mw-interface="", to avoid potential conflicts with other data-mw attributes, which are generated by Parsoid.
There is no new MediaWiki version this week or next week.
Meetings and events
The Wikimedia Hackathon Northwestern Europe 2026 will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications just opened mid-December and will close in mid-January or earlier if capacity is reached. With space for approximately 100 participants, early application is encouraged.
Latest comment: 9 months ago1 comment1 person in discussion
Happy New Year and Happy New WikiCup! The 2026 competition has just begun and all article creators, expanders, improvers and reviewers are welcome to take part. Even if you are a novice editor, we hope the WikiCup will give you a chance to improve 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 a bot will set up your submissions page within one day, ready for you to take part. Any questions on the scoring, rules or anything else should be directed to one of the judges, or posted to the WikiCup talk page.
For the 2026 WikiCup, the highest-ranking contestants will receive tournament points at the end of each round, and final rankings are decided by the number of tournament points each contestant has. This is the same scoring system that we had last year. If you're busy and can't sign up in January, don't worry: Signups are open throughout the year. To make things fairer for latecomers, the lowest-scoring contestants are no longer eliminated at the end of each round.
Changes to the Access to Temporary Account IP Addresses Policy's disclosure rules include broadening the consecutive-blocks exception to cover all admin actions and removing the requirement to revision-delete permissible disclosures once they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information.
Latest comment: 8 months ago1 comment1 person in 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.
Weekly highlight
The Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on Meta and Diff. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the talk page.
Updates for editors
As part of the current work of Community Tech team on the Multiple watchlists project, the display of EditWatchlist will be updated as a first step towards multiple watchlists. Additionally, the pagination on Search will be updated too, as a part of the work on the Revamp pagination / page navigation wish.
The Global Watchlist is a MediaWiki extension that lets you see your watchlists from different wikis on the same page. It was recently updated to look more like the regular Watchlist, such as preparing it for temporary accounts in IP masking (including rerouting user links to contributions pages), making page titles bold, and opening links in edit summaries and tags in new browser tabs.
View all 28 community-submitted tasks that were resolved last week. For example, the issue where global blocks did not have the option to disable sending emails, has now been fixed, and will be available for use in the week of January 13.
Latest comment: 8 months ago1 comment1 person in 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.
Updates for editors
The tray shown on Special:Diff in mobile view has been redesigned. It is now collapsed by default, and incorporates a link to undo the edit being viewed, making it easier for mobile editors and reviewers to take action while keeping the interface uncluttered.
The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension continues to improve — it now automatically determines the text direction (ensuring correct display of sites with unusual domain names) and shows detailed descriptions for log actions. Later this week, a new permanent link for page creations and CSS classes for each entry element will be added.
View all 32 community-submitted tasks that were resolved last week. For example, the previously observed issue in Vector 2022, where anchor link targets were obscured by the sticky header, has now been addressed.
Updates for technical contributors
As mentioned in the October 2025 deprecation announcement, MediaWiki Interfaces team will begin sunsetting all transform endpoints containing a trailing slash from the MediaWiki REST API the week of January 26. Changes are expected to roll out to all wikis on or before January 30th. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found, compared, and tested using the REST Sandbox. If you have questions or encounter any problems, please file a ticket in Phabricator to the #MW-Interfaces-Team board.
The WMF Wikidata Platform team (WDP) has published its January 2026 newsletter. It includes updates on the legacy full-graph endpoint decommissioning, the User-Agent policy change, the monthly Blazegraph migration office hours, and efforts to reduce regressions caused by the legacy endpoint shutdown. As a reminder, you can subscribe to the WDP newsletter!
The Wikimedia Hackathon Northwestern Europe 2026 will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications opened mid-December and will close soon or when capacity is reached. It's a two-day, technically oriented hackathon bringing together Wikimedians from the region. Hope to see you there!
Latest comment: 8 months ago1 comment1 person in 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.
All users with registered accounts can now use passkeys for two-factor authentication (2FA). Passkeys are a simple way to log in without using a second device. They verify the user's identity using a fingerprint, face scan, or a PIN code. To set up a passkey, first set up a regular 2FA method. Currently, to log in with a passkey, users must also use a password. Later this quarter, passwordless login will allow users to log in with a single click and a passkey. Users with advanced rights will also be required to have 2FA enabled. This is part of the Account Security project.
Unregistered contributors on blocked IPs or blocked IP ranges can now interact on-wiki to appeal a block by creating a temporary account to appeal a block on the user talk page, unless the "prevent this user from editing their own talk page" is enabled. This solves the problem of logged-out users unable to use the default unblock process via user talk page.
View all 20 community-submitted tasks that were resolved last week. For example, the Two-Factor Authentication (2FA) methods description on the management page has been updated. It is now clearer and easier for users to understand and make use of.
Updates for technical contributors
A new AbuseFilter variable, account_type, has been added to provide a reliable way to determine the account type being created in the createaccount and autocreateaccount actions. As part of this change, the variable accountname has been renamed to account_name, and accountname is now deprecated. Edit filter managers should update any filters that use hardcoded account type checks or the deprecated variable.
Image thumbnails that are requested in non-standard sizes, and using non-standard methods such as direct requests to upload.wikimedia.org/… will stop working in the near future. This change is to prevent ongoing external abuse by web-scrapers and bots. Some users with custom CSS/JS, Interface Admins who can fix gadgets and local skins, and Tool-authors, will need to update their code to use standard thumbnail sizes. Details, search-links, and examples of how to fix them, are available in the task.
Latest comment: 8 months ago1 comment1 person in 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.
Updates for editors
The "Page information" feature, which gives validating information about a page (example), now automatically includes a table of contents. If there is a local MediaWiki:Pageinfo-header page created by individual users, it can now be removed.
View all 21 community-submitted tasks that were resolved last week. For example, VisualEditor previously added bold or italic formatting inside link descriptions, making the wikicode complex. This has now been fixed.
Updates for technical contributors
There was no XML dump on 20 January. Additionally, from now on, dumps will be generated once per month only.
The MediaWiki Interfaces team removed support for all transform endpoints containing a trailing slash from the MediaWiki REST API. All API users currently calling those endpoints are encouraged to transition to the non-trailing slash versions. If you have questions or encounter any problems, please file a ticket in phabricator to the #MW-Interfaces-Team board.
Users are reminded that the Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on Meta and Diff. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the talk page.
Latest comment: 8 months ago1 comment1 person in 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.
Updates for editors
Logged-in contributors who manage large or complex watchlists can now organise and filter watched pages in ways that improve their workflows with the new Watchlist labels feature. By adding custom labels (for example: pages you created, pages being monitored for vandalism, or discussion pages) users can more quickly identify what needs attention, reduce cognitive load, and respond more efficiently. This improves watchlist usability, especially for highly active editors.
A new feature available on Special:Contributions shows temporary accounts that are likely operated by the same person, and so makes patrolling less time-consuming. Upon checking contributions of a temporary account, users with access to temporary account IP addresses can now see a view of contributions from the related temporary accounts. The feature looks up all the IPs associated with a given temporary account within the data retention period and shows all the contributions of all temporary accounts that have used these IPs. Learn more.
When editors preview a wikitext edit, the reminder box that they are only seeing a preview (which is shown at the top), now has a grey/neutral background instead of a yellow/warning background. This makes it easier to distinguish preview notes from actual warnings (for example, edit conflicts or problematic redirect targets), which will now be shown in separate warning or error boxes.
The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension continues to improve — it now properly supports more than one Wikibase site, for example both Wikidata and testwikidata. In addition, issues regarding text direction have been fixed for users who prefer Wikidata or other Wikibase sites in right-to-left (RTL) languages.
The automatic "magic links" for ISBN, RFC, and PMID numbers have been deprecated in wikitext since 2021 due to inflexibility and difficulties with localization. Several wikis have successfully replaced RFC and PMID magic links with equivalent external links, but a template was often required to replace the functionality of the ISBN magic link. There is now a new built-in parser function{{#isbn}} available to replace the basic functionality of the ISBN magic link. This makes it easier for wikis who wish to migrate off of the deprecated magic link functionality to do so.
A new global user group has been created: Local bots. It will be used internally by the software to allow community bots to bypass rate limits that are applied to abusive web scrapers. Accounts that are approved as bots on at least one Wikimedia wiki will be automatically added to this group. It will not change what user permissions the bot has.
The MediaWiki Users and Developers Conference, Spring 2026 will be held March 25–27 in Salt Lake City, USA. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend.
Due to the result of a recent motion, a rough consensus of administrators at the arbitration enforcement noticeboard may impose an expanded topic ban on Israel, Israelis, Jews, Judaism, Palestine, Palestinians, Islam, and/or Arabs, if an editor's Arab-Israeli conflict topic ban is determined to be insufficient to prevent disruption. At least one diff per area expanded into should be cited.
Latest comment: 7 months ago1 comment1 person in 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.
Weekly highlight
The SRE Team will be performing a cleanup of Wikimedia's Etherpad instance, the web-based editor for real-time collaborative document editing. All pads will be permanently deleted after 30 April, 2026 – if there are still migration projects in progress at that point the team can revisit the date on a case by case basis. Please create local backups of any content you wish to keep, as deleted data cannot be recovered. This cleanup helps reduce database size and minimize infrastructure footprint. Etherpad will continue to support real-time collaboration, but long-term storage should not be expected. Additional cleanups may occur in the future without prior notice.
Updates for editors
The Information Retrieval team will be launching an Android mobile app experiment that tests hybrid search capabilities which can handle both semantic and keyword queries. The improvement of on-platform search will enable readers to find what they’re looking for directly on Wikipedia more easily. The experiment will first be launched on Greek Wikipedia in late February, followed by English, French, and Portuguese in March. Read more on Diff blog.
The Reader Growth team will run an experiment for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias.
Previously, site notices (MediaWiki:Sitenotice and MediaWiki:Anonnotice) would only render on the desktop site. Now, they will render on all platforms. Users on mobile web will now see these notices and be informed. Site administrators should be prepared to test and fix notices on mobile devices to avoid interference with articles. To opt out, interface admins can add #siteNotice { display: none; } to MediaWiki:Minerva.css.
View all 19 community-submitted tasks that were resolved last week. For example, an issue on Special:RecentChanges has been fixed. Previously, clicking hide in the active filters caused the "view new changes since…" button to disappear, though it should have remained visible. The button now behaves as expected.
Updates for technical contributors
New documentation is now available to help editors debug on-site search features. It supports troubleshooting when pages do not appear in results, when ranking seems unexpected, and when you need to inspect what content is being indexed, helping make search behavior easier to understand and analyze. Learn more.
Latest comment: 7 months ago1 comment1 person in 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.
Weekly highlight
Reference Check has been deployed to English Wikipedia, completing its rollout across all Wikipedias. The feature prompts newcomers to add a citation before publishing new content, helping reduce common citation-related reverts and improve verifiability. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop and about 17.5 times more likely on mobile web.
Updates for editors
The InterwikiSorting extension, which allowed for the sorting of interwiki links, has been undeployed from Wikipedia. As a result, editors who had enabled interwiki link sorting in non-compact mode (full list format) will now see links reordered. The links moving forward will be listed in the alphabetical order of language code.
Later this week, people who are editing a page-section using the mobile visual editor, will notice a new "Edit full page" button. When tapped, you will be able to edit the entire article. This helps when the change you want to make is outside the section you initially opened.
The Reader Experience team is inviting editors to assess whether dark mode should still be considered "beta" on their wiki, based on their experience of how well it functions on desktop and mobile. If the feature is deemed mature, editors can update the interface messages in MediaWiki:skin-theme-description and MediaWiki:Vector-night-mode-beta-tag to indicate that dark mode is ready and no longer considered beta.
The improved Activity tab which displays user-insights is now available to all users of the Wikipedia iOS app (version 7.9.0 and later). Following earlier A/B testing that showed higher account creation among users with access to the feature, it has been rolled out to 100% of users along with some updates. The Activity tab now shows your edited articles in the timeline, offers editing impact insights like contribution counts and article view trends, and customization options to improve in-app experience for users.
View all 21 community-submitted tasks that were resolved last week. For example, a bug that prevented DiscussionTools from working on mobile has now been fixed, restoring full functionality.
Updates for technical contributors
The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension that makes this possible continues to improve. The latest upgrade is the inclusion of a new hook, ext.globalwatchlist.rebuild, which fires after each watchlist rebuild. This allows you to run gadgets and user scripts for the Special page.
Latest comment: 7 months ago1 comment1 person in discussion
The first round of the 2026 WikiCup ended on 26 February. As some of you may have noticed, good article nomination reviews now receive 10 points, an increase from 5 points in the previous year, as per a consensus at WT:CUP. This point increase has been retroactively applied to all good article reviews for which competitors have claimed points in this round. Peer reviews, which continue to be worth 5 points, are now listed in the same section as featured article candidate reviews, rather than with good article reviews. Everyone who competed in round 1 will advance to round 2 unless they have withdrawn or been banned. No other changes to the round-point system have been made for this year.
Round 1 was competitive. Three contestants scored more than 1,000 round points, and the top 16 contestants all scored more than 300 round points. The following competitors scored more than 800 round points:
Generalissima(submissions) with 1,095 round points, largely from 3 featured articles, 6 good articles, and 5 did you know articles;
MCE89(submissions) with 848 round points, largely from 1 featured article, 8 good articles, 1 did you know article, and 32 FAC and GAN reviews; and
Rollinginhisgrave(submissions) with 838 round points, largely from 1 featured article, 8 good articles, 1 did you know article, and 14 FAC, GAN, and peer reviews.
The full scores for round 1 can be seen here. During this round, contestants have claimed 7 featured articles, 16 featured lists, 2 featured-topic articles, 168 good articles, 13 good-topic articles and more than 50 Did You Know articles. In addition, competitors have worked on 14 In the News articles, and they have conducted nearly 700 reviews. The tournament points table will be updated within the next few days.
Remember that any content promoted after 26 February but before the start of Round 2 can be claimed in Round 2. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 14:56, 27 February 2026 (UTC)Reply
A request for comment is open to discuss retiring CSD criterion R3 in favour of handling such redirects through RfD.
Arbitration
Following a motion, remedy 9.1 of the Conduct in deletion-related editing case has been amended to limit TenPoundHammer to one XfD nomination or PROD per 24-hour period.
Following a motion, the Iskandar323 further POV pushing motion has been rescinded.
The Arbitration Committee has passed a housekeeping motion rescinding a number of outdated remedies and enforcement provisions across multiple legacy cases. In most instances, existing sanctions remain in force and continue to be appealable through the usual processes, while some case-specific remedies were amended or clarified.
Latest comment: 7 months ago1 comment1 person in 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.
Weekly highlight
Wikipedia 25 Birthday mode is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via community configuration on the local wiki.
Paste Check will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check tags all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via Special:EditChecks. Research across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can help to localize this and related features.
The Reader Experience team will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface.
Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one.
Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon.
The Global Watchlist which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The extension now allows activating the language fallback system for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no uselang= URL parameter is provided.
The Wikipedia Android team has started a beta test of hybrid search on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily.
For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will gradually change in March. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule.
View all 27 community-submitted tasks that were resolved last week. For example, the issue preventing users from creating an instance in Wikibase.cloud has now been fixed.
Updates for technical contributors
To help ensure fair use of infrastructure, over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts.
The new Parsoid parser continues to be deployed to additional wikis, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.
The process and criteria for requesting exceptional access to the high volume feed of the Wikimedia Enterprise APIs (at no cost for mission-aligned usecases), have now been published. This is to provide more thorough and clearer documentation for users.
Tech Blog, the blog dedicated to the Wikimedia technical community will be migrating to Diff, the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog.
Latest comment: 7 months ago1 comment1 person in 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.
Weekly highlight
All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the post on the Stewards' noticeboard (translations).
Updates for editors
Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as iCloud Private Relay) will receive clearer guidance on what they need to do to start editing again.
Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools.
Updates for technical contributors
API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and give feedback. You can also sign up for usability tests.
The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read this update to learn more.
The Article Guidance team invites experienced Wikipedia editors from selected pilot wikis and interested contributors from other Wikipedias to fill out this questionnaire which is available in English, Arabic, Bengali, Japanese, Portuguese, Persian, and Turkish. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more on the project page.
Special report: What actually happened during the Wikimedia security incident? A horrifying exploit took place, which could have had catastrophic and far-reaching consequences if used maliciously; instead, it seems to have happened by accident and was used for childish vandalism. How did this happen, and what did the script actually do?
Latest comment: 6 months ago1 comment1 person in 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.
Updates for editors
The ⧼codemirror-beta-feature-title⧽ beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share.
Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks.
On wikis using Flagged Revisions, the number of pending changes shown on Special:PendingChanges previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself.
Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about the changes.
Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'.
View all 28 community-submitted tasks that were resolved last week. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed.
Users of the ⧼codemirror-beta-feature-title⧽ beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome.
The CodeMirror JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the ext.CodeMirror or ext.CodeMirror.lib modules from gadgets and user scripts was deprecated in July 2025. The use of the ext.CodeMirror.switch hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the migration guide for more information.
The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include extension APIs. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for GrowthExperiments and Wikifunctions APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the REST Sandbox (i.e., Special:RestSandbox, available on all wiki projects).
The Scribunto extension provides different pieces of information about the wiki where the module is being used via the mw.site library. Starting last week, the library also provides a way of accessing the wiki ID that can be used to facilitate cross-wiki module maintenance.
The 2026 Coolest Tool Award celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the nomination survey form by 23 March 2026. For more information on privacy and data handling, please see the survey privacy statement.
Latest comment: 6 months ago1 comment1 person in 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.
Weekly highlight
Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Updates for editors
Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced.
Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown.
Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation.
View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.
Updates for technical contributors
Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible.
The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
Latest comment: 6 months ago1 comment1 person in 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.
Weekly highlight
The Beta version of Abstract Wikipedia a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. Read more.
Updates for editors
The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. Read more.
The Wikimedia Apps team is inviting feedback on how editing should work on the Wikipedia mobile apps. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
View all 45 community-submitted tasks that were resolved last week. For example, an issue where citation fetching from the large newspaper archive Newspapers.com was no longer working, due to a block in Citoid requests, has now been fixed.
Following a motion, the GSCASTE extended-confirmed restriction in the Indian military history case has been narrowed. It now applies to caste-related topics in South Asia, and the preemptive protection remedy has been amended accordingly.
Latest comment: 6 months ago1 comment1 person in 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.
Updates for editors
The CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed.
Updates for technical contributors
The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected.
All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
The Action API has had several formats for requested output. One of them, format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots.
The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia.
Latest comment: 5 months ago1 comment1 person in 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.
Weekly highlight
Experienced editors are invited to test the Article guidance feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are available. Also, after reviewing the outlines, please provide feedback on the project talk page. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out the video explaining the feature.
The Growth team has launched an account creation experiment to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed.
Updates for technical contributors
Starting later this week, Edit filter managers who have the ⧼codemirror-beta-feature-title⧽ beta feature enabled will have CodeMirror instead of CodeEditor as the editor at Special:AbuseFilter. This is part of the broader effort to make the user experience more consistent across all editors.
Tools and bots that access the Notifications API (action=query&meta=notifications) will need to update their OAuth or BotPassword grants to also include access to private notifications.
Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia).
Latest comment: 5 months ago1 comment1 person in 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.
Weekly highlight
After two years of development, ⧼codemirror-beta-feature-title⧽, also known as CodeMirror 6, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other benefits to all users of the standard syntax highlighter. A huge thank you to volunteer Bhsd who developed many of the new features, including code folding, autocompletion, and linting.
A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. Download the latest version and explore the update.
Updates for editors
Reading lists is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
An experiment which explores extending Page Previews to mobile web will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. Read more about this experiment and others.
On several wikis, logged-in editors who haven't confirmed their email addresses can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. Learn more.
View all 15 community-submitted tasks that were resolved last week. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed.
Updates for technical contributors
As part of the promotion of CodeMirror from a beta feature, all users will use CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages.
The mirrors.wikimedia.org service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. You can read more.
The image and oldimage table will be removed from wikireplicas. If your tools or queries access image or oldimage directly, please update them to use the file and filerevision table before 28 May.
Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure fair use of infrastructure by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
The Attribution API is now available as a beta. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the REST sandbox on English Wikipedia). Share your feedback on the project talk page.
Latest comment: 5 months ago1 comment1 person in 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.
Updates for editors
There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the Autoconfirmed users group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions.
All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the reading lists beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access.
View all 30 community-submitted tasks that were resolved last week. For example, the issue where infobox images have huge padding in Firefox, has been fixed.
Updates for technical contributors
As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure fair use of infrastructure. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
May 2026 Administrator Election – Call for Candidates
Latest comment: 5 months ago1 comment1 person in discussion
The administrator elections process has officially started! Interested editors are encouraged to self-nominate or arrange to be nominated by reviewing the instructions at Wikipedia:Administrator elections/May 2026/Candidates.
Here is the schedule:
April 29 – May 5: Call for candidates
May 8–12: Discussion phase
May 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 5 months ago1 comment1 person in discussion
The second round of the 2026 WikiCup ended on 28 April. As a reminder for contestants who just joined or are unaware of recent changes to our round-points system, good article nomination reviews now receive 10 points, an increase from 5 points in the previous year, as per a consensus at WT:CUP. Peer reviews, which continue to be worth 5 points, are now listed in the same section as featured article candidate reviews, rather than with good article reviews. Everyone who competed in round 2 will advance to round 3 unless they have withdrawn or been banned. No other changes to the round-point system have been made for this year.
Round 2 was competitive. Three contestants scored more than 1,000 round points; nine scored over 500; and fourteen scored over 300. The top seven contestants had at least one featured article (two of them with two apiece). The following competitors scored more than 800 round points:
MCE89(submissions) with 1,333 points, mainly from good and featured articles about Australian people and geography
Bgsu98(submissions) with 1,149 points, mainly from good articles, featured articles, and featured lists about figure skating, along with many article reviews and two good topics
Olliefant(submissions) with 830 points, mainly from good and featured articles about television shows, episodes and media, along with nearly four dozen good and featured article reviews
The full scores for round 2 can be seen here. During this round, contestants have claimed 12 featured articles, 13 featured lists, 2 featured-topic articles, 106 good articles, 22 good-topic articles and more than 40 Did You Know articles. In addition, competitors have worked on 3 In the News articles, and they have conducted over 200 reviews. The tournament points table has been updated.
Remember that any content promoted after 28 April but before the start of Round 3 can be claimed in Round 3. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 14:48, 29 April 2026 (UTC)Reply
Changes to user permissions made from Meta are now included in the local user permissions log (T6055).
The autoconfirmed user group will soon be modified such that the four-day account age requirement begins when an account makes its first edit (T418484).
Arbitration
The arbitration case SchroCat has been opened. Evidence submissions in this case closed on 15 April.
Per a recent motion, appeals of blocks from the conflict-of-interest VRT queue are, by default, appealed on-wiki through the normal unblock process. However, they may be heard by the Committee if COIVRTers disagree on the interpretation of the evidence or believe ArbCom would be better suited to hear the appeal. Administrators are also advised that loosening or lifting such blocks without the consent of someone with access to the queue or ArbCom can be grounds for desysopping.
Per a recent motion, restrictions issued directly by the Committee may now be enforced with blocks which work exactly like contentious topic blocks.
Latest comment: 5 months ago1 comment1 person in 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.
Weekly highlight
The Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.
The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so.
From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages.
The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed.
Updates for technical contributors
The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
On 13 May, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 4 months ago1 comment1 person in 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.
Weekly highlight
Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.
Updates for editors
The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed.
In the voting phase, the candidate subpages close to public questions and discussion, and everyone who qualifies to vote has a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's vote total during the election. The suffrage requirements are similar to those at RFA.
Once voting concludes, we will begin the scrutineering phase, which will last for a few days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a non-recall candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Recall candidates must achieve 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 4 months ago1 comment1 person in 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.
Weekly highlight
The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.
Updates for editors
An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights.
Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed.
Updates for technical contributors
The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.
Latest comment: 4 months ago1 comment1 person in discussion
News and notes: Offline: Osama Khalid still in prison He has been imprisoned since 2020 for his Wikipedia edits. A fresh campaign is calling for his release.
Recent research: WikiLambda the Ultimate Does Abstract Wikipedia help fight "One ring to rule them all" solutions for knowledge access - or does it implement one itself?
Latest comment: 4 months ago1 comment1 person in 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.
Weekly highlight
Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics.
Updates for editors
For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules.
After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed.
Updates for technical contributors
The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read more.
Mandatory 2FA for bureaucrats: Bureaucrats without two-factor authentication (2FA) enabled have already lost access to their advanced rights on 26 May. Those who do not enable 2FA may be automatically removed from the groups in mid-June 2026, and from that point onward, new members must have 2FA enabled before they can be added. (T423119, T423120)
Latest comment: 4 months ago1 comment1 person in 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.
Updates for editors
The Reader Experience team is conducting an experiment to show the reading lists feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The experiment was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
The Wikimedia Apps team released Phase 1 of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
View all 18 community-submitted tasks that were resolved last week. For example, an issue where images could fail to load for some suggested edits on Special:Homepage, leaving the thumbnail stuck in a loading state, has now been fixed.
Latest comment: 4 months ago1 comment1 person in 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.
Weekly highlight
Wikimedia Enterprise has increased the free usage limits for its API offerings. The monthly request limit for the On-demand API has increased from 5,000 to 50,000 requests, while the Snapshot API limit has increased from 15 to 30 requests per month. In addition, Structured Contents snapshots are now available for free accounts. These changes expand access to Wikimedia Enterprise data for developers, researchers, and organizations using Wikimedia content.
Updates for editors
The refreshed Explore Feed, now called the Home Feed, is rolling out to 50% of users of the Wikipedia Android app. The Home Feed helps readers discover relevant content through two new tabs: Community and For You. The Community tab provides a scrollable feed of curated content and updates from the broader Wikimedia community and movement, while the For You tab offers a full-screen, swipeable experience that shows content tailored to a user's interests. The redesign is part of a broader effort to improve discovery and enhance the learning experience in the Wikipedia app.
The Which came first? daily trivia game is now available in the beta version of the Wikipedia iOS app in English, German, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. The game uses historical events from Wikipedia's "On This Day" content and challenges readers to guess which of two events happened first. The game was previously released on Android. Communities interested in making the game available in their languages can read the instructions and requirements.
Sub-referencing, a new MediaWiki feature that allows editors to reuse references with different details, will begin rolling out to Wikimedia wikis following a successful pilot phase. Deployment will start on 8 June for most Group 1 wikis and French Wikipedia, with additional Wikipedia language editions receiving the feature over the coming months. Communities are encouraged to prepare by checking for untranslated Cite extension messages in their language and reviewing any use of Reference Tooltips, which may require updates to support the new functionality. Wikis using Reference Previews do not need to take any action. Communities may also wish to create the cite-tracking-category-ref-detailstracking category as a hidden category using __HIDDENCAT__ (or a dedicated template), and connect it to the corresponding Wikidata item d:Q129764848.
The Page Previews experiment on mobile web has concluded. The team decided not to roll out the feature after the results showed no statistically significant impact on reader retention, as the primary success metric was retention improvement. Page Previews, which are already available on desktop and in the apps, display a thumbnail, lead paragraph, and link to the full article when readers tap a blue link. The experiment tested this experience on mobile web across six Wikipedias.
The user interface icon library will be updated later this week or next week. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups.
The Universal Language Selector (ULS) interface in MediaWiki, which helps users select content in other languages, has been updated. The new version improves speed and accessibility, and users of Wikimedia projects can now pin languages for quicker language switching. The deployment to Wikimedia sites will happen gradually in the coming weeks. You can test it now as a beta feature by selecting beta features in your profile preferences and share your feedback on the project page.
View all 21 community-submitted tasks that were resolved last week. For example, an issue where the Pageviews Analysis dashboard on pageviews.wmcloud.org stopped updating graph data in May 2026, affecting all users, has been fixed.
Updates for technical contributors
The function signature for mw.util.addPortletLink() has been simplified. Developers can now pass a configuration object instead of a list of positional parameters when creating portlet links. The previous function signature remains supported for backwards compatibility. For example, instead of: mw.util.addPortletLink('p-cactions', '#', 'Stub', 'ca-stubtag', 'Add a stub tag to this page'); use mw.util.addPortletLink('p-cactions', { href: '#', text: 'Stub', id: 'ca-stubtag', tooltip: 'Add a stub tag to this page' });. Script maintainers are encouraged to review existing uses of addPortletLink() and update them where appropriate. This change will be available on all wikis from 11 June. Thanks to community volunteer Gerges for contributing this improvement.
Community Wishlist discussion: Product & Technology introduced changes meant to increase the number and complexity of wishes fulfilled, including the disbanding of the Community Tech team. They are engaging in discussions about a proposed direction for the wishlist from community members. Includes ways to structure annual voting, better tracking of wishes, removing focus areas, and staffing updates.
Latest comment: 3 months ago1 comment1 person in 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.
Weekly highlight
The Reader Growth team has launched an Image Browsing beta feature on the mobile web version of all Wikipedias. The feature shows an image carousel at the top of articles with 3 or more images. Editors can configure this feature with the following controls: to hide a specific image from a page, either use class=notpageimage excluding it from thumbnail previews, or class=noviewer excluding it from MediaViewer. The carousel can also be disabled from a page entirely, with the magic word __NOMEDIAVIEWERCAROUSEL__. To submit feedback or flag bugs, please visit the project page.
Wikitables can now be sorted in descending order on the first click by adding data-sort-order="desc" to the header cell. Previously, by default, clicking a column header for the first time sorts it in ascending order. This addition to a Wikitable gives it more control and flexibility, while the default behavior for subsequent clicks remains unchanged.
Updates for editors
The Article guidance feature is currently being tested with some editors creating new articles on the Simple English, French, and Turkish Wikipedias. The experiment will soon begin on the Arabic and Bangla Wikipedias as well. This feature gives editors community-curated guidance to help them create articles that follow community standards. Experienced editors can continue creating or adapting outlines for specific article types that are commonly created by less experienced contributors. The outlines guide less experienced editors in creating high-quality articles. A quick guide to markups used in outlines can be found on this page. Example outlines that can be adapted and instructions for how to adapt them are on this section of the project page.
Wikis that wish to replace the "indefinitely" button in Special:Block for temporary accounts (for example, wikis that block temporary users only until account expiration) will be able to do so by creating MediaWiki:ipb-indefinite-expiry-temporary-account with the block duration they want.
By the end of June, a valid user-agent string will be required for automated dumps downloads from the dumps.wikimedia.org website. Automated requests that provide a generic or empty user-agent will be blocked. This extends enforcement of the long standing user-agent policy. Access to dumps through Wikimedia Cloud Services will not change.
The roll out of global API rate limits is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited.
On June 17th at 6pm UTC the WMF will be holding Discord call focused on a code review. We've heard through the Developer Satisfaction Survey that volunteers are struggling with code review and we'd like to discuss these experiences with the goal of surfacing workable solutions. You can join the call via the Wikimedia Community Discord server.
The Latin American Wikimedia Conference will host a regional hackathon that will bring together the Wikimedia movement’s technical community including developers, system administrators, data scientists, and users with extended rights. Interested technical contributors can apply for a scholarship to participate until June 21 at midnight (Bolivia time, UTC-4).
Sign up for Wikimania Team Challenges to join this special event. The Team challenges will take place online and in person from July 21 to 22, before Wikimania conference. Everyone is welcome, regardless of skills or Wikimania registration. Teams will work on 10 important challenges supporting the Wikimedia community. For details, visit the Team Challenges page and register there. Registration closes on June 20th at 11pm UTC.
Latest comment: 3 months ago1 comment1 person in 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.
Weekly highlight
Growth features are now available at Wikidata. This update enables access to Mentorship (if configured), Impact module, the Help Panel, and a simplified Newcomer Homepage (without Suggested Edits). Wikidata administrators are still configuring the features through Community Configuration.
Updates for editors
The special page Special:RangeCalculator has been created. It allows users to find an IP range without needing to rely on external tools. Until now, this tool was only available to CheckUsers.
Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The FAQ lists possible actions to take on your wiki to support the deployment. Check the rollout plan for the next deployment steps.
Starting next week, users will get a notification when they are blocked or unblocked from editing, or if this block changes.
Starting next week, abuse filters that are set to "require CAPTCHA verification" will begin to also affect users with the skipcaptcha right, which includes most autoconfirmed users. Bots are exempted. This change only affects edits that trigger an abuse filter. The skipcaptcha right will continue to exempt users from having to solve CAPTCHAs in the ordinary course of using the wikis.
Reference documentation for the Lift Wing API has moved from the API Portal to the interactive REST Sandbox.
Latest comment: 3 months ago1 comment1 person in 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.
Updates for editors
As part of the Account Creation Experiments, the Growth team tested adding a user account icon in the mobile web header for logged-out users, providing direct access to "Create account" and "Log in" actions. The experiment increased account creation by about 20% without negatively affecting edit quality or constructive edit rates. The feature will now be rolled out to all Wikimedia Foundation wikis on mobile web in the first week of July.
After a successful experiment, logged-in users who did not confirm their email address when their account was created see a new banner asking them to complete that process. This helps reduce the risk that users get locked out of their account, and makes account email addresses overall more reliable. This is part of the Account Security project.
An update to Search is refining how the -prefix: behaves when used to exclude results. Previously, using -prefix: with negation could unintentionally broaden search results by adding the namespaces included in the search scope, leading to confusing behavior for users expecting a straightforward exclusion filter. With the update, -prefix: will now strictly exclude matching page titles as intended and may display a warning if the relevant namespace has not been explicitly selected. The behavior of prefix: without negation however remains unchanged.
View all 33 community-submitted tasks that were resolved last week. For example, an issue where reviewers using the Page Curation toolbar were not automatically subscribed to talk page discussions they started has now been fixed. Reviewers will now receive notifications when someone replies to those discussions.
Updates for technical contributors
Starting June 29th, automated downloads from the dumps.wikimedia.org website will be subject to the user-agent policy. Automated requests that provide a generic or empty user-agent will be blocked. Access to dumps through Wikimedia Cloud Services remains unaffected. This is a follow up to the announcement made in the 2026/25 issue of Tech News.
Latest comment: 3 months ago1 comment1 person in discussion
The third round of the 2026 WikiCup ended on 28 June at 23:59 (UTC). As a reminder, good article nomination reviews now receive 10 points, while peer reviews, which continue to be worth 5 points, are now listed in the same section as featured article candidate reviews, rather than with good article reviews. Everyone who competed in round 3 will advance to round 4 unless they have withdrawn or been banned. No other changes to the round-point system have been made for this year.
Round 3 was competitive. Three contestants scored more than 1,000 round points; eight scored over 500; and thirteen scored over 300. The top three contestants had at least one featured article (two of them with two apiece). The following competitors scored more than 800 round points:
MCE89(submissions) with 1567 points, mainly from good and featured articles about Australian people and geography, as well as some article reviews
Bgsu98(submissions) with 1547 points, mainly from good articles, featured articles, featured lists, and a good topic about figure skating, along with 20 article reviews
Reconrabbit(submissions) with 1004 points, mainly from a high-multiplier featured article on European rabbit and several good articles, DYKs, and reviews
A.Cython(submissions) with 1004 points, mainly from good articles about warfare, along with 22 article reviews
Generalissima(submissions) with 859 points, mainly from good and featured articles about rivers and East Asian topics
The full scores for round 3 can be seen here. During this round, contestants have claimed 12 featured articles, 12 featured lists, 7 featured-topic articles, 117 good articles, 74 good-topic articles and more than 30 Did You Know articles. In addition, competitors have worked on 13 In the News articles, and they have conducted nearly 180 reviews. The tournament points table has been updated.
Remember that any content promoted after 28 June but before the start of Round 4 can be claimed in Round 4. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 13:48, 29 June 2026 (UTC)Reply
Latest comment: 3 months ago1 comment1 person in 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.
Updates for editors
View all 34 community-submitted tasks that were resolved last week. For example, an issue where the search bar results on Wikidata, showed English results instead of using the correct language fallback for users of language variants, has now been fixed. Search suggestions will now follow the expected language fallback chain.
Updates for technical contributors
In preparation for Celebrate Women campaign planned for March 2027, the Wikimedia Foundation’s Content Enablement team has launched a 22-question survey to better understand technical contributions by women+ (anyone who identifies as a woman) across Wikimedia projects. The survey takes approximately 15–20 minutes to complete and will remain open until 20 July 2026. The questions are also available on-wiki for review in advance.
The Score extension now supports rendering music scores as SVG images in addition to PNG, addressing a long-standing feature request and resolving historical image quality issues. Both formats are now provided to clients, with PNG in the src attribute and SVG in the srcset attribute.
The new Parsoid parser continues to be deployed to additional wikis, making it easier to introduce new reading and editing features. It was enabled on French Wikipedia, bringing total progress to covering 78.9% of Wikipedia page views. Rollout to English Wikipedia desktop will progress through this week.
The Wikimedia Hackathon 2026 recap blog post is now live. It highlights the projects, sessions, and social activities from this year’s event, and shares initial plans for the 2027 Wikimedia Hackathon.
Latest comment: 2 months ago1 comment1 person in discussion
News and notes: An exclusive club Wikipedia Co-Founder Larry Sanger gets a community ban for canvassing.
In the media: Battle for a soul – who won? Commissars, winners and losers, blocks or bans, a Wiki red card, social engineering on wikis, and Swift action!
On the bright side: Fatherhood, weather, and diplomacy Father's Day, Canada Day, and the 250th anniversary of the United States Declaration of Independence.
Latest comment: 2 months ago1 comment1 person in 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.
Updates for editors
Revise Tone helps newcomers identify passages in Wikipedia articles that may contain non-encyclopedic language and encourages them to consider revising the tone. The feature was A/B tested on the Arabic, English, French, and Portuguese Wikipedias, where newcomer task completion rates increased by 38.7% compared to the default Copyedit task, with no decrease in edit quality. The test ended on July 9, and the feature is now available for everyone on these wikis, configurable via Community Configuration. The plan is to release Revise Tone to more wikis.
View all 38 community-submitted tasks that were resolved last week. For example, an issue where some users of the Wikipedia Android app were logged out immediately after signing in, preventing them from staying logged in and editing pages, has now been fixed.
Updates for technical contributors
Editing a page via user scripts or gadgets was causing watchlist labels that the user had assigned to that page to reset. This has now been fixed.
To work around a Safari bug (see phab:T425211), on Parsoid-enabled wikis, wikilink hrefs now use absolute urls instead of protocol-relative urls. REST API output remains unchanged and continue to use protocol-relative urls. Gadgets, user scripts, bots, and CSS might need to be adapted if they relied on the presence of protocol-relative urls in wikilink hrefs.
The Wikimedia Foundation’s Experiment Platform Team has published a blog post reflecting on its first year of structured experimentation. It highlights successful experiments such as Paste Check, Reference Check, and Tone Check, which improved editing outcomes and have been rolled out to more users, as well as experiments that did not lead to product changes. Read more.
Latest comment: 2 months ago1 comment1 person in 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.
Updates for editors
The Reader Experience team has incorporated community feedback around the placement of watchstar and watchlist buttons for the Reading Lists beta feature, which would allow for saving articles for later reading – a wishlist item to bring the functionality to web. Editors are invited to enable the beta feature to test it out and share their thoughts.
Suggestion Mode offers edit suggestions within the VisualEditor for improving Wikipedia articles. All suggestions are community-configurable. The TextMatch feature is a way for volunteers to create custom local suggestions. The feature searches in articles for strings of text, and now includes support for regular expressions. This gives volunteers greater precision and flexibility over the kinds of local suggestions they can create. Note: Suggestions can be targeted based on the edit count of the person editing as well as other aspects of the page. You can find examples from other communities for inspiration, including TextMatches that detect: typos, grammar-errors, potential advertisements, clichés, incorrect dash or hyphen usage, non-specific time keywords, outdated names, and more. Any feedback is appreciated.
View all 27 community-submitted tasks that were resolved last week. For example, an issue where the SVG Translate tool could use an outdated version of a file, causing existing translations to be overwritten when new ones were uploaded, has now been fixed. Overall, in the last quarter from April – June 2026 about 337 community tasks were resolved by the Wikimedia Foundation.
Updates for technical contributors
On Parsoid-enabled wikis, Parsoid now renders a maximum of 1,250 images per page. A new tracking category, "media-limit-reached", will be soon made available to identify pages where this limit is reached, making it easier to find content whose media output may have been restricted during rendering. See phab:T430854 for more information and to provide feedback.
Latest comment: 2 months ago1 comment1 person in 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.
Updates for editors
Content Translation now supports dark mode, fulfilling a Community Wishlist request. This brings the tool in line with the accessibility features available in the Vector 2022 and Minerva skins, helping reduce visual fatigue for users translating content.
DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links ([[), templates ({{), HTML and parser tags (<), and magic words (__), making it quicker and easier to insert links, templates, and other wiki markup while editing.
The Readers Growth team has concluded its experiment with mobile page previews and will not roll out the feature. Page Previews are a pop-up bottom sheet that appears when readers tap a blue link, showing a thumbnail, lead paragraph, and an option to open the article. The experiment showed flat retention and negative indicator metrics, suggesting that mobile web readers preferred navigating directly to linked articles rather than using page previews.
The Reader Experience team has seen encouraging early results from the Reading Lists feature, with 93% of participating users reporting that it was useful. Reading Lists help active readers save articles for future reading and support their learning goals on Wikimedia projects. The team plans further improvements before expanding the feature to more users.
The Explore Feed Refresh initiative was tested with new and casual Wikipedia app readers. The refreshed feed helps readers discover new and relevant content. After a 10.5% increase in engagement with the feed, Wikimedia Apps team has decided to scale the Home Feed redesign to iOS with the learnings from the Android release applied.
View all 23 community-submitted tasks that were resolved last week. For example, an issue where subject names in the Article Guidance feature were displayed with incorrect capitalization on French Wikipedia, has now been fixed. Subject names will now follow the correct capitalization rules for the language.
Updates for technical contributors
After running several Account Creation Experiments to improve registration completion rates, a new version of the username field on Create Account has been rolled out. It includes a popover summarizing the username policy to provide clearer guidance during account creation. As part of this change, the messages createacct-helpusername and createacct-username-help that several communities have configured will no longer be used. If communities want to customize the guidance shown in the new popover, they can instead edit the following messages: createacct-username-policy-popover-bullet1, createacct-username-policy-popover-bullet2, and createacct-username-policy-popover-bullet3.
Later this week, the CodeMirror syntax highlighter will offer themes. The themes can be picked from a dropdown menu in the full CodeMirror preferences dialog. For wikitext, available themes are default, colorblind-friendly (previously the colorblind preference option on Special:Preferences#mw-prefsection-editing) and no-highlighting. For code languages (i.e., CSS/JavaScript/JSON/Vue/Lua), there are several themes available. These same themes will eventually be available for wikitext, too.
From now on, wikis can restrict editing in the "User" namespace to only the page owner and certain user groups. Read the configuration documentation to learn more.
Latest comment: 2 months ago1 comment1 person in 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.
Updates for editors
The Reader Experience team has developed a patch demo that wraps the page toolbar onto two lines when there is not enough horizontal space for all the buttons. This aims to reduce crowding in the Vector 2022 toolbar, which can occur on some language Wikipedias at certain screen widths.
The Reader Experience team is planning to launch Reading Lists, a Community Wishlist item, which is currently available to try in beta, as a full feature in September. Before then, volunteer translator help is needed for string translations into a number of languages. The feature supports reading and learning goals on Wikipedia.
Next week, the table of contents on Wikimedia Commons file pages will be improved by consolidating the file page table of contents with the page table of contents. This will make it easier to understand a file page’s structure, navigate to specific sections, and share links to individual sections.
View all 24 community-submitted tasks that were resolved last week. For example, an issue where some TIFF images failed to load after clicking their thumbnail, causing a broken image to be displayed instead of the full-size image, has now been fixed.
Updates for technical contributors
The variable and function selector in AbuseFilter has been updated to support search and autocomplete. It will allow filter maintainers to find the desired variable or function more quickly.
The MJPEG and VP8 formats are removed from the video player. The MP4 format (MPEG-4 Part 2) is added instead, which provides higher quality videos to older iPhone devices. It may take a few weeks to retroactively update all existing videos. The default format for modern devices stays the same (VP9/WebM).
Latest comment: 1 month ago1 comment1 person in 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.
Updates for editors
A new ChartWizard is now available on Wikimedia Commons for users interested in creating charts from their own data. The wizard makes the Chart extension more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the wish talk page.
View all 19 community-submitted tasks that were resolved last week. For example, an issue where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed.
Updates for technical contributors
Math formula SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting "MathML with SVG image (client side MathJax rendering)" in your preferences. This change is part of deprecating RESTBase and deprecating Mathoid.
Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use cldsort=timestamp URL argument in category view to sort the entries.
Gadgets and user scripts on Wikimedia wikis may now use ES2018 features and ES2019 features in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all supported browsers.
Latest comment: 1 month ago1 comment1 person in 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.
Weekly highlight
The Worklist feature for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers Event Pathways which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on Worklist Setup Workshop will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC.
Updates for editors
Special:ShortPages displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word __EXPECTSHORTPAGE__.
One new wiki has been created: a Wikipedia in Bole (w:bol:)
Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a fully merged patch from the Reader Experience team which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths.
View all 16 community-submitted tasks that were resolved last week. For example, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error.
Updates for technical contributors
Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. Some Cloud VPS projects still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A migration guide is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. Read more.
Latest comment: 1 month ago1 comment1 person in 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.
Updates for editors
The Special:CreateAccount page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration.
In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics.
View all 42 community-submitted tasks that were resolved last week. For example, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved.
Updates for technical contributors
User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to place it in the page content as well, using the {{#uic:}} parser function. It can be particularly useful in templates like {{Userlinks}} (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their preferences.
Due to user security and privacy risks, we have disabled access to Special:MyPage URLs when specifically using action=raw. If you are impacted by this, consider whether you can use an alternative approach. Special:MyPage URLs can still be accessed and used without action=raw. Specified user page URLs (e.g. User:Myusername) can still be used with action=raw.
Due to an update, the thumbnailing software has been improved. This includes upgrading librsvg to 2.60 and ImageMagick to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors.
Latest comment: 1 month ago1 comment1 person in discussion
The fourth round of the 2026 WikiCup ended on 29 August at 23:59 (UTC). Everyone who competed in round 4 will advance to round 5 unless they have withdrawn or been removed. Round 4 was competitive, though slightly less so than round 3. Three contestants scored more than 1,000 round points; six scored over 500; and nine scored over 300. Each of the top five competitors had hundreds of points accumulated from multiple GAs. The following competitors scored more than 800 round points:
Vanderwaalforces(submissions) with 1,208 points from 2 featured articles, 2 featured lists, and 12 good articles about African leaders, along with over two dozen reviews
A.Cython(submissions) with 1,084 points from 16 good articles and a small good topic about warfare and Greek elections, along with over two dozen reviews
Bgsu98(submissions) with 837 points from 4 FLs and 8 GAs about figure skating, along with two dozen reviews
The full scores for round 4 can be seen here. During this round, contestants have claimed 10 featured articles, 11 featured lists, 8 featured-topic articles, 103 good articles, 6 good-topic articles and more than 30 Did You Know articles. In addition, competitors have worked on 11 In the News articles, and they have conducted 170 peer reviews, FA and GA reviews. The tournament points table has been updated.
Remember that any content promoted after 29 August but before the start of Round 5 can be claimed in Round 5. 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. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 02:42, 30 August 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in 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.
Weekly highlight
A new format for the Community Wishlist is open for feedback. You can read the proposed ideas on Meta. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks.
Updates for editors
The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience.
The Reading Lists feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28.
At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an updated navigation bar in an A/B test. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors.
Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, onlyredirects: and withredirects:, now allow redirects to be searched directly and can be combined with existing keywords such as incategory:, intitle:, and insource:.
The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where searching for pages by category using deepcat could return no results or unrelated results has now been fixed.
Updates for technical contributors
The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org.
The Wikimedia Math API is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native MathML or MathJax. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service.
Latest comment: 1 month ago1 comment1 person in 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.
Updates for editors
Add a Link has been upgraded for English Wikipedia users with improved detection of links that have different capitalization. This will help reduce ambiguous suggestions caused by differences in capitalization in article titles, including articles about cultural goods. A second phase of improvements is planned, which will also prepare the feature for release in other languages.
The Article guidance feature will be enabled by default for junior editors on Simple English and Turkish Wikipedia starting 10 September 2026 following an experiment. Junior editors with 0 to 99 edits will automatically see the feature when they click a red link or use the "Madde oluşturto" option on Turkish Wikipedia to create a new article. The change is intended to help junior editors create higher-quality articles that meet each Wikipedia’s standards. Additional improvements will continue based on the experiment results and community feedback.
The Pageviews Analysis tool which allows users to compare pageviews across multiple pages, turns 10 years old this year and several new features have been added. They include WikiNav which provides insights into how readers of Wikipedia explore the content, editing stats in Siteviews, the ability to lookup articles belonging to a WikiProject, and support for dark mode.
A visually simplified Minerva navigation bar is being tested for logged-out readers using mobile web on the Bengali, Czech, English, Farsi, and Polish Wikipedias. The experiment aims to determine whether simplifying the navigation improves reader retention. The test will run from August 31 to September 28, and no action is required from users.
All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.
View all 25 community-submitted tasks that were resolved last week. For example, an issue where Parsoid could mishandle nested nowiki tags, causing content to be lost and displaying unwanted text has now been fixed.
Updates for technical contributors
Interface administrators can configure gadgets from MediaWiki:Gadgets-definition. The definition format has been updated and no longer requires the ResourceLoader option, as gadgets are always loaded through ResourceLoader. This simplifies gadget configuration by removing an option that is no longer necessary, making gadget definitions easier for administrators.
Latest comment: 25 days ago1 comment1 person in 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.
Weekly highlight
The Future Audiences team has started a discussion on English Wikipedia about a proposed new experiment to show a temporary notice about the new Google Preferred Sources feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the talk page.
Updates for editors
The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on Phabricator or Metawiki.
The Reader Growth team will be running an experiment to test whether compacting article lead sections on mobiles with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming week.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where Wikistats for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed.
Updates for technical contributors
Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can read more.
Speedy deletion criteria G15 has been renamed from "LLM-generated pages without human review" to "Unambiguously LLM-generated pages" and has an additional sign of detection added to it following a RfC.
Latest comment: 12 days ago1 comment1 person in 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.
Weekly highlight
All wikis will be read-only for a few minutes on Wednesday, 23 September 2026 at 14:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Updates for editors
The Growth team tested a new post-edit notice designed to encourage Temporary Account holders to register for a permanent account. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis.
For Wikipedia editors using the "Suggestion mode" Beta Feature, there is a new opt-in user preference for showing "experimental" edit checks and suggestions. These types are listed at Special:EditChecks, and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the configuration details for each suggestion as usual. Administrators can also use this feature to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. Feedback is welcome.
The CEE Technical Village Pump has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe.
A new tool, Starter Kit, is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in this Diff blog post.
The Reader Growth team is launching a retest of the image carousel experiment. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias.
After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the Reading Lists feature from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed.
Updates for technical contributors
The abusefilters list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the formatversion=2 configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the abusefilters list query API, and respond to any breaking changes.
Latest comment: 11 days ago1 comment1 person in 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.
Updates for editors
Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for.
Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their reading lists instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content.
An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October.
The Product and Technology Advisory Council has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to the council's talk page.
A bug in the Global Watchlist is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the relevant help section.
New magic words {{CATEGORYSORT:TIMESTAMP}} and {{CATEGORYSORT:RTIMESTAMP}} are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization.
View all 20 community-submitted tasks that were resolved last week. For example, the issue where Wikistats for Wikipedias was not reachable has now been fixed.
Updates for technical contributors
The datacenter switchover, scheduled on September 23, has been postponed. The equinox exercise revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement.
Produnto has been deployed to mediawiki.org and some Indic language wikis. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in Wikimedia's GitLab. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
A Cross-wiki code collaboration workshop will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.
October 2026 Administrator Elections – Call for Candidates
Latest comment: 11 days ago1 comment1 person in discussion
The administrator elections process has officially started! Qualified editors are encouraged to find at least one experienced nominator. Self-nominations are also allowed. Please review instructions at Wikipedia:Administrator elections/October 2026/Candidates.
Here is the schedule:
September 29–October 5: Nominations phase (we are here)
October 8–12: Discussion phase
October 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed. However, in practice, few candidates succeed without ~10K edits, some content creation, no recent behavioral issues, and a nominator.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Following an RfC, late signatures added to administrator recall petitions after 720 hours from opening are reverted or struck and do not count towards the threshold, even if the petition has not yet been formally closed.
The post-May 2026 administrator elections RfCs concluded with consensus for election monitors to curate blatantly inappropriate questions after posting, and to remove or merge true duplicates, clearly marking merged questions. Calls for candidates will include advisory guidance that users with less than one year’s experience or 5,000 edits generally lack a realistic chance of success.
Technical news
Interface administrators no longer need to specify the ResourceLoader option in the definitions for gadgets on MediaWiki:Gadgets-definition as gadgets are always loaded through ResourceLoader. (T298199)
The list=abusefilters API module now supports formatversion=2 and includes breaking changes to its responses. In particular, the actions property is now a JSON array rather than a string, regardless of the format version. Maintainers of user scripts and other code using this module should check compatibility and update their code as needed. (T435828)
Doug Weller passed away on 30 September 2026. Doug Weller began editing Wikipedia in 2006 and became an administrator in 2008, making nearly 275,000 edits over two decades. He served on the Arbitration Committee from 2015 through 2018 and was also a longtime CheckUser and Oversighter.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The process for this year’s Community Wishlist has been published, incorporating community feedback. The wish submission process will end on November 8. This year, a working group (open for volunteering) that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the triage process. The triage is expected to be completed by late November. Votes for wishes will start in January.
Updates for editors
Editors using the visual editor will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as LLM Paste Check. It is a type of Edit Check that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also be tagged so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can adjust the wording and policy that is linked. The team apologizes that this was rolled out without a delay for translations.
Editors can now easily access the web visual editor directly from the iOS and Android apps. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading.
Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly.
Editors on group1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on Recent Changes and Watchlist when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the project page and share feedback or concerns on the talk page.
View all 36 community-submitted tasks that were resolved last week. For example, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program.
Updates for technical contributors
Wikimedia Brasil has published its Development Best Practices Framework (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the Diff post.
A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a {projectName}/api/ pattern and will act as an alternative path for current REST APIs (for example: {projectName}/w/rest.php/). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October.
On 13 Oct, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
.jpg)
