Latest comment: 27 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: 14 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: 13 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.
Latest comment: 12 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.
Drafts that go unedited for six months are eligible for deletion, in accordance with our draftspace policy, and this one has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission, and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.
If your submission has already been deleted by the time you read this, you can request its undeletion. An administrator will, in most cases, restore the draft so you can continue to work on it.
Latest comment: 4 days ago13 comments4 people in discussion
When you removed the protection from my talk page your explanation for that was "Editing on several occasions after retirement, so full protection is no longer appropriate." I have no recollection of that. Perhaps it is my age, now 82. Could you point out those edits for me. Thanks Kwork2 (talk) 15:30, 5 October 2026 (UTC)Reply
Thanks for explaining how to find the edits. But aside from the current issue with one question to the Zionism article, which I admit was a mistake, I see nothing that I would consider an actual edit. The closest was this which I had forgotten, and I think should not be considered an issue:
The article contains this statement: "Kirk promoted the antisemitic Cultural Marxism conspiracy theory, and described universities as "islands of totalitarianism." The wording could use some adjustment because that seems to imply that he was antisemitic although none of the three supporting sources claims that. Kwork2 Sorry if I signed incorrectly, it has been ten years since editing even a talk page, and I have no intention of returning. Just something I noticed. Kwork2 (talk) 12:42, 11 September 2025 (UTC)Reply
Yes, there's significant BLP violations on this page.
Posting a comment is editing whatever page it's posted on. Anything that shows up in your contributions is an edit to a page. ~ Jenson (SilverLocust💬) 21:34, 5 October 2026 (UTC)Reply
So you are counting my correcting typos to articles on rare occasions as though they were edits, even though they were not at all articles I edited but just random articles I happened to have read for their information? Kwork2 (talk) 13:52, 6 October 2026 (UTC)Reply
That is both amusing and pathetic because administrators apparently feel no need at all to enforce WP:NPOV, which is, or should be, the foundational basis of all work done on Wikipedia and the basis of the claim that it is an encyclopedia:
All encyclopedic content on Wikipedia must be written from a neutral point of view (NPOV), which means representing fairly, proportionately, and, as far as possible, without editorial bias, all the significant views that have been published by reliable sources on a topic.
NPOV is a fundamental principle of Wikipedia and of other Wikimedia projects. It is also one of Wikipedia's three core content policies; the other two are "Verifiability" and "No original research". These policies jointly determine the type and quality of material acceptable in Wikipedia articles, and because they work in harmony, they cannot be interpreted in isolation from one another.
"Pathetic" is a word to avoid when you're under a civility restriction, have violated multiple topic bans, and are trying to prevent other editors from being able to address issues on your talk page (by arguing against its unprotection). If you find apparent NPOV issues on topics from which you are not banned, then you are free to point those out or address them. ~ Jenson (SilverLocust💬) 20:06, 6 October 2026 (UTC)Reply
Just what issues need to be discussed on my talk page? Anyone who thought there was a need to do that could have at any time simply requested that the pages protection be removed. That never happened. Does anyone feel a need to discuss the few typos I corrected over the last eleven years? Or is there some other heinous violation, over those eleven years, that needs discussion on my talk page? Kwork2 (talk) 22:19, 6 October 2026 (UTC)Reply
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.
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. 
Administrator changes
Oversight changes
Guideline and policy news
Miscellaneous
Technical news
Arbitration
Obituaries