Maayong pag-abot sa atongtubaan! Kining maong panid gitagana alang sa komunikasyon sa mga miyembro ning atong katilingban sa Wikipedyang Sinugboanon.
Mahimo kang motabang sa paghimo saWikipedya ngadto sa usa ka ikapadayeg ngaensiklopedya pinaagi sapag-usab sa mga nasulat na nga mga artikulo ugpagsulat og mga bag-ong artikulo. Konmaghimo ka og akawnt mangalan kanimo ang imong mga sinulat.
Latest comment:16 Hunyo1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
You cannominate your favorite tools for the sixth edition of theCoolest 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 canread more about their plans to evolve the APIs in this Techblog post.
This year, the Wikimedia community will vote in late August through September 2025 to fill two (2) seats on the Foundation Board. Could you – or someone you know – be a good fit to join the Wikimedia Foundation's Board of Trustees? [3]
Learn more about what it takes to stand for these leadership positions and how to submit your candidacy onthis Meta-wiki page or encourage someone else to run in this year's election.
Best regards,
Abhishek Suryawanshi Chair of the Elections Committee
On behalf of the Elections Committee and Governance Committee
Latest comment:23 Hunyo1 comment1 person in discussion
Latesttech 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 ofa 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 includethe rest of the Wikipedias in this project.[1]
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.[2]
Later this week, the Editing team will releaseMulti Check to all Wikipedias (except English Wikipedia). This feature shows multipleReference 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%).[3]
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 inthe 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 wereresolved last week. For example, a bug was fixed that had caused pages to scroll upwards when text near the top was selected.[4]
Updates for technical contributors
Editors can now use Lua modules to filter and transform tabular data for use withExtension: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.[5]
Theall_links variable inAbuseFilter is now renamed tonew_links for consistency with other variables. Old usages will still continue to work.[6]
The latest quarterlyGrowth newsletter is available. It includes: the recent updates for the "Add a Link" Task, two new Newcomer Engagement Features, and updates to Community Configuration.
A vision of relevant, accessible, and impactful free knowledge has always guided the Wikimedia Movement. As the ecosystem of Wikimedia projects continues to evolve, it is crucial that we periodically review existing projects to ensure they still align with our goals and community capacity.
Despite their noble intent, some projects may no longer effectively serve their original purpose.Reviewing such projects is not about giving up – it's about responsible stewardship of shared resources. Volunteer time, staff support, infrastructure, and community attention are finite, and the non-technical costs tend to grow significantly as our ecosystem has entered a different age of the internet than the one we were founded in. Supporting inactive projects or projects that didn't meet our ambitions can unintentionally divert these resources from areas with more potential impact.
Moreover, maintaining projects that no longer reflect the quality and reliability of the Wikimedia name stands for, involves a reputational risk. An abandoned or less reliable project affects trust in the Wikimedia movement.
Lastly,failing to sunset or reimagine projects that are no longer working can make it much harder to start new ones. When the community feels bound to every past decision – no matter how outdated – we risk stagnation. A healthy ecosystem must allow for evolution, adaptation, and, when necessary, letting go. If we create the expectation that every project must exist indefinitely, we limit our ability to experiment and innovate.
Because of this, SPTF reviewed two requests concerning the lifecycle of the Sister Projects to work through and demonstrate the review process. We chose Wikispore as a case study for a possible new Sister Project opening and Wikinews as a case study for a review of an existing project. Preliminary findings were discussed with the CAC, and a community consultation on both proposals was recommended.
Theapplication to consider Wikispore was submitted in 2019. SPTF decided to review this request in more depth because rather than being concentrated on a specific topic, as most of the proposals for the new Sister Projects are, Wikispore has the potential to nurture multiple start-up Sister Projects.
After careful consideration, the SPTF has decidednot to recommend Wikispore as a Wikimedia Sister Project. Considering the current activity level, the current arrangement allowsbetter flexibility and experimentation while WMF provides core infrastructural support.
We acknowledge the initiative's potential and seek community input on what would constitute a sufficient level of activity and engagement to reconsider its status in the future.
As part of the process, we shared the decision with the Wikispore community and invited one of its leaders, Pharos, to an SPTF meeting.
Currently, we especially invite feedback on measurable criteria indicating the project's readiness, such as contributor numbers, content volume, and sustained community support. This would clarify the criteria sufficient for opening a new Sister Project, including possible future Wikispore re-application. However, the numbers will always be a guide because any number can be gamed.
We chose to review Wikinews among existing Sister Projects because it is the one for which we have observed the highest level of concern in multiple ways.
Since the SPTF was convened in 2023, its members have asked for the community's opinions during conferences and community calls about Sister Projects that did not fulfil their promise in the Wikimedia movement.[1][2][3] Wikinews was the leading candidate for an evaluation because people from multiple language communities proposed it. Additionally, by most measures, it is the least active Sister Project, with the greatest drop in activity over the years.
While the Language Committee routinely opens and closes language versions of the Sister Projects in small languages, there has never been a valid proposal to close Wikipedia in major languages or any project in English. This is not true for Wikinews, where there was a proposal to close English Wikinews, which gained some traction but did not result in any action[4][5], see section 5 as well as a draft proposal to close all languages of Wikinews[6].
Initial metrics compiled by WMF staff also support the community's concerns about Wikinews.
Based on this report, SPTF recommends a community reevaluation of Wikinews. We conclude that its current structure and activity levels are the lowest among the existing sister projects. SPTF also recommends pausing the opening of new language editions while the consultation runs.
SPTF brings this analysis to a discussion and welcomes discussions of alternative outcomes, including potential restructuring efforts or integration with other Wikimedia initiatives.
Options mentioned so far (which might be applied to just low-activity languages or all languages) include but are not limited to:
Restructure how Wikinews works and is linked to other current events efforts on the projects,
Merge the content of Wikinews into the relevant language Wikipedias, possibly in a new namespace,
Merge content into compatibly licensed external projects,
Archive Wikinews projects.
Your insights and perspectives are invaluable in shaping the future of these projects. We encourage all interested community members to share their thoughts on the relevant discussion pages or through other designated feedback channels.
We'd be grateful if you want to take part in a conversation on the future of these projects and the review process. We are setting up two different project pages:Public consultation about Wikispore andPublic consultation about Wikinews. Please participate between 27 June 2025 and 27 July 2025, after which we will summarize the discussion to move forward. You can write in your own language.
I will also host a community conversation 16th July Wednesday 11.00 UTC and 17th July Thursday 17.00 UTC (call links to follow shortly) and will be around at Wikimania for more discussions.
Latest comment:30 Hunyo1 comment1 person in discussion
Latesttech 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 nowmatch against IP reputation data inAbuseFilters. 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.[7]
Hidden content that is withincollapsible 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.[8][9]
A new feature, calledFavourite 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 acommunity wishlist focus area.
View all 31 community-submitted tasks that wereresolved last week. For example, a bug was fixed that had caused some Notifications to be sent multiple times.[10]
Latest comment:8 Hulyo1 comment1 person in discussion
Latesttech 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, andRepository 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 thinkon the talk page.
Users of the Wikipedia Android app in some languages can now play the newtrivia 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.[11]
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 theTabbed Browsing project page.
A new feature related toTemplate Recall and Discovery will be deployed later this week to all Wikimedia projects: atemplate 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 communitythrough 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.[13]
As part ofMediaWiki 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 atManual:Notifications, information about migration inT388663 and details on deprecated hooks inT389624.
WikidataCon 2025, the conference dedicated to Wikidata is now open forsession proposals and forregistration. 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".
Latest comment:14 Hulyo1 comment1 person in discussion
(Apologies for posting in English, you can help by translating into your language)
Hello everyone, theWikidata For Wikimedia Projects team is excited to announce an upcoming change in how Wikidata edit changelogs are displayed in yourWatchlists andRecent Changes lists. If an edit is made on Wikidata that affects a page in another Wikimedia Project, the changelog will contain some information about the nature of the edit. This can include a QID (or Q-number), a PID (or P-number) and a value (which can be text, numbers, dates, or also QID or PID’s). Confused by these terms? See theWikidata:Glossary for further explanations.
The upcoming change is scheduled for17.07.2025, between1300 - 1500 UTC.The change will display the label (item name) alongside any QID or PIDs, as seen in the image below:
These changes will only be visible if you have Wikidata edits enabled in your User Preferences for Watchlists and Recent Changes, or have the active filter ‘Wikidata edits’ checkbox toggled on, directly on the Watchlist and Recent Changes pages.
Your bot and gadget may be affected! There are thousands of bots, gadgets and user-scripts and whilst we have researched potential effects to many of them, we cannot guarantee there won’t be some that are broken or affected by this change.
Further information and context about this change, including how your bot may be affected can be found on thisproject task page. We welcome your questions and feedback, please write to us on this dedicatedTalk page.
Latest comment:14 Hulyo1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Featured templates, a new feature related toTemplate 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 communitythrough the Community Wishlist.[14][15]
View all 31 community-submitted tasks that wereresolved last week. For example, the request to add Malayalam fonts in theWikisource Book Export Tool was resolved and now, the rendering of Malayalam letters in exported Wikisource books are accurate.[16]
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. Submityour scholarship application andprogram 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!
Latest comment:21 Hulyo1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
The Translation Suggestions feature in theContent 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.[17]
Administrators can now limit "Add a Link" to newcomers. The"Add a Link" Structured Taskhelps 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 theCommunity Configuration feature.
For AbuseFilter editors onsome 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 theORES/AbuseFilter variables documentation.
TheBeta Cluster wikis havebeen moved frombeta.wmflabs.org tobeta.wmcloud.org. Users may need to update URLs in any tools, or in their password managers. Any related issues can bereported 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.[18]
Latest comment:29 Hulyo1 comment1 person in discussion
Latesttech 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. Pleaseread the latest update, and if you have ideas, pleasesubmit a wish on the topic.
Updates for editors
The Wikimedia Commons community has decided to blockcross-wiki uploads to Wikimedia Commons, for all users without autoconfirmed rights on that wiki, starting on August 16. This is because ofwidespread 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 themessage or give feedback on the message text. Please also update your local help pages to explain this restriction.[19]
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 namedMediaWiki:Sp-contributions-footer-temp.[20]
Wikimania 2025 will run from August 6–9. Theprogram 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, pleaseregister for a free virtual ticket. For example, you may be interested in technical sessions such as:
TheMediaWiki 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:5 Agosto1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Editors can now enable theUser 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 inyour global preferences, and later this week it will be available in local preferences.[21]
Everybody is invited to share comments onCollaborative Contributions, a project recently launched by theConnection 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 theproject talk page.[22]
Administrators can now define the default block duration for temporary accounts. To do that, they need to create a page namedMediaWiki:Ipb-default-expiry-temporary-account and use a value defined inMediaWiki: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.[23]
Gadgets can now include.vue files. This makes it easier to develop modern user interfaces usingVue.js, in particular usingCodex, 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, anAPI module now exists to load Codex icons.[24][25]
Module developers can now use aLua 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 towatch the demo video, read more abouttranslatable modules to understand how it works, refer to Meta-Wiki'sModule:User Wikimedia project for example usage, andshare 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.[26]
Developers of external tools that connect to Wikimedia pages must set a user-agent that complies withthe user-agent policy. This policy will start to be more strongly enforced in August because of external crawlers that areoverusing 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 theParsoid/Parser Unification project page.[27]
Wikimania 2025 will run from August 6–9. Theprogram 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, pleaseregister for a free virtual ticket. For example, you may be interested in technical sessions such as:
Latest comment:11 Agosto1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
The WikiEditor toolbar now includesits keyboard shortcuts in the tooltips for its buttons. This will help to improve the discoverability of this feature.[28]
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.[29]
Editors on some wikis will see a new toggle for "Group results by page" on watchlist, related changes, and recent changes pages. This isan 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.[30]
The multiwiki datasets ofUnicode data have been moved toCategory: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 atthe talkpage.[31]
Lua code can add warnings when something is wrong, by using themw.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.[32]
Latest comment:19 Agosto1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
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.[33]
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.[34]
An A/A test to measure the baseline for reader retention was launched 12 August usingExperimentation 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.[35]
Latest comment:26 Agosto1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Template authors can now use additional CSS properties, since the CSS sanitizer used byTemplateStyles was updated. For example:width: fit-content;ruby-align; relative units such aslh; and custom strings inlist-style-type. These improvements are aCommunity Wishlist wish.[41][42][43][44][45][46][47][48][49][50]
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.[51]
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.[53][54]
Two fields of therecentchanges database table are being removed.rc_new andrc_type are being removed in favor ofrc_source. Queries to these older fields will start to fail starting this week and developers should userc_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.[56]
The latest quarterlyLanguage 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 nextLanguage Community Meeting is happening soon, August 29th at15: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.
Temporary accounts are successfully live on 30 wikis, including many large ones like German, Japanese, and French. The change they bring is especially relevant to logged-out editors, who this feature is designed to protect. But it is also relevant to community members like mentors, patrollers, and admins – anyone who reverts edits, blocks users, or otherwise interacts with logged-out editors as part of keeping the wikis safe and accurate.
Why we are building temporary accounts
Our wikis should be safer to edit by default for logged-out editors. Temporary accounts allow people to continue editing the wikis without creating an account, while avoiding publicly tying their edits to their IP address. We believe this is in the best interest of our logged-out editors, who make valuable contributions to the wikis and who may later create accounts and grow our community of editors, admins, and other roles. Even though the wikis do warn logged-out editors that their IP address will be associated with their edit, many people may not understand what an IP address is, or that it could be used to connect them to other information about them in ways they might not expect.
Additionally, our moderation software and tools rely too heavily on network origin (IP addresses) to identify users and patterns of activity, especially as IP addresses themselves are becoming less stable as identifiers. Temporary accounts allow for more precise interactions with logged-out editors, including more precise blocks, and can help limit how often we unintentionally end up blocking good-faith users who use the same IP addresses as bad-faith users.
How temporary accounts work
Any time a logged-out user publishes an edit on this wiki, a cookie will be set in this user's browser, and a temporary account tied with this cookie will be automatically created. This account's name will follow the pattern:~2025-12345-67 (a tilde, current year, a number). On pages like Recent Changes or page history, this name will be displayed. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser. A record of the IP address used at the time of each edit will be stored for 90 days after the edit. However, only some logged-in users will be able to see it.
What does this mean for different groups of users?
For logged-out editors
This increases privacy: currently, if you do not use a registered account to edit, then everybody can see the IP address for the edits you made, even after 90 days. That will no longer be possible on this wiki.
If you use a temporary account to edit from different locations in the last 90 days (for example at home and at a coffee shop), the edit history and the IP addresses for all those locations will now be recorded together, for the same temporary account. Users whomeet the relevant requirements will be able to view this data. If this creates any personal security concerns for you, please contact talktohumanrights at wikimedia.org for advice.
For community members interacting with logged-out editors
A temporary account is uniquely linked to a device. In comparison, an IP address can be shared with different devices and people (for example, different people at school or at work might have the same IP address).
Compared to the current situation, it will be safer to assume that a temporary user's talk page belongs to only one person, and messages left there will be read by them. As you can see in the screenshot, temporary account users will receive notifications. It will also be possible to thank them for their edits, ping them in discussions, and invite them to get more involved in the community.
For users who use IP address data to moderate and maintain the wiki
For patrollers who track persistent abusers, investigate violations of policies, etc.: Users whomeet the requirements will be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range (Special:IPContributions). They will also have access to useful information about the IP addresses thanks to theIP Info feature. Many other pieces of software have been built or adjusted to work with temporary accounts, including AbuseFilter, global blocks, Global User Contributions, and more. (For information for volunteer developers on how to update the code of your tools – see the last part of the message.)
For admins blocking logged-out editors:
It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects theautoblock option.
It will still be possible to block an IP address or IP range.
Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this.
If you want to test the temporary account experience, for example just to check what it feels like, go to testwiki or test2wiki and edit without logging in.
Tell us if you know of any difficulties that need to be addressed. We will try to help, and if we are not able, we will consider the available options.
Look at ourprevious message about requirements for users without extended rights who may need access to IP addresses.
To learn more about the project, check outour FAQ – you will find many useful answers there. You may alsolook at the updates (we have just posted one) andsubscribe to our new newsletter. If you'd like to talk to me (Szymon) off-wiki, you will find me on Discord and Telegram. Thank you!
Latest comment:1 Septiyembre1 comment1 person in discussion
Latesttech 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 inT402601, or to share their list withTrizek_(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
TheCampaignEvents 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, andInvitation List. To request the extension for your wiki, visit the Deployment information page.[57]
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.[58]
On September 3rd, 2025 we will increase the sampling percentages of ourgroup by toggle experiment of theSpecial:RecentChanges,Special:Watchlist, andSpecial: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.[59][60]
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 isa newsletter to learn more.
The latestReaders 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.
Latest comment:9 Septiyembre1 comment1 person in discussion
Latesttech 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, pleasetell us in this task, orcontact the team.
When browsing a wiki (likeen.wikipedia.org), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an "m" domain (likeen.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.[62]
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.[63]
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.[64][65]
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.[66]
Latest comment:15 Septiyembre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
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.[67]
Starting in the week of October 6, onsmall wikis andmedium wikis that have theCampaignEvents extension enabled, all autoconfirmed users will be able to useEvent Registration as an organizer. No changes will be made forlarge 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 theintitle: keyword:metacharacters for start-of-line (^) and end-of-line ($) anchors[68]
for bothintitle: andinsource: keywords: shorthandcharacter classes for digits (\d), whitespace (\s), and word characters (\w); andescape codes for line feed (\r), newline (\n), tab (\t), and unicode (e.g.\uHHHH).[69]
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.[70]
View all 24 community-submitted tasks that wereresolved 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.[71]
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 tojoin an upcoming discovery interview, orleave 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.[72]
The newUnicode 17.0 version has been released. Thedatasets on Commons for theModule: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 theWikimedia Enterprise Structured Contents endpoints can now accessParsed Tables. The new Parsed Tables feature extracts and represents Wikipedia tables in structured JSON. This improves machine accessibility as part of theStructured Contents initiative. Structured Contents output is freely available through theOn-demand API, or through Wikimedia Cloud Services.
Adataset of English Wikipedia biographical information fromWikimedia 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).
TheWikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
All traffic will switch on24 September. The switch will start at15:00 UTC.
Unfortunately, because of some limitations inMediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
A banner will be displayed on all wikis 30 minutes before this operation happens. This banner will remain visible until the end of the operation. You can contribute to thetranslation or proofreading of this banner text.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for up to an hour on Wednesday 24 September 2025.
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
Latest comment:22 Septiyembre1 comment1 person in discussion
Latesttech 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 scheduleddatacenter 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 canread more about the process on the Diff blog.
Updates for editors
Editors of60 more Wiktionaries will soon be able to callfunctions 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 other65 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 newparser function has been added:{{#contentmodel}}. Template editors and admins can use it to get the localized or canonical name of thecontent model of a specific page. The function makes it easier to create and edit system messages, such asMediaWiki:editinginterface, even when you switch types of pages, like wiki, JavaScript, CSS or JSON page.[73]
Adding or editing aDISPLAYTITLE 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 inthis ticket.
Beta users of the Wikipedia Android app can now try the redesignedActivity 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 involvinggeo-coordinates,quantities andtime 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 inthis video and Wikifunctions'August 1 newsletter (for quantities) andAugust 22 newsletter (for geo-coordinates).
Latest comment:29 Septiyembre1 comment1 person in discussion
Latesttech 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 toPhabricator. 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.[74]
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 thisin the latest update or you can consult thecurrent documentation on MediaWiki.
As announcedon Diff blog, the production trial of thehCaptcha 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 existingCAPTCHA (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges.
TheCampaignEvents extension has beendeployed 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 theevent organizer right.
On wikis using theMentorship system, communities can now opt experienced editors out of Mentorship throughEspesyal: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.[75]
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 areinvited 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 ofmultiblocks had the side effect that non-active block logs may have been shown on Espesyal:Mga Tampo 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 withsp-contributions-blocked-notice will be removed and replaced withthose prefixed withblocked-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.[76]
One new wiki has been created: a Wikiquote inMalay (q:ms:)[77]
View all 21 community-submitted tasks that wereresolved last week. For example, theUser Info Card now displays currently active global lock/blocks.[78]
Updates for technical contributors
Later this week, editors using Lua modules will be able to use themw.title.newBatch function to look up the existence of up to 25 pages at once, in a way that only increases theexpensive function count once.
A newUnsupported Tools Working Group has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to theProduct & 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:30 Septiyembre1 comment1 person in discussion
Hello Wikimedians,
Apologies if this message is not in your language. Please help translate to your language.
TheReader Experience team will launch the Dark mode feature for anonymous users on all Wikimedia sites, including yours, on October 29, 2025.
Dark mode is an option that allows users to view pages in light-coloured text, and icons on a dark background. Once it is available for anonymous users, they can enable it when using various devices. More information on ways to enable it can be found onthis page.Given many pages are still not compatible with dark mode this will be an opt-in feature and not automatically apply to pages.
Dark mode requires modifications to content pages and templates, and since our initial launchin July 2024, we have been working with communities and helping them prepare for dark mode. Before the rollout, it is essential that template authors and technical contributors test dark mode and readthis page to learn how to make pages Dark mode-ready and address any compatibility issues found in templates.
We will fix most color compatibility issues only on the most-viewed pages on projects with over 5 million monthly page views. Technical contributors with an account should opt into dark mode currently using preferences or settings and test pages and seek help before the release to ensure everything complies before the enablement.
Latest comment:6 Oktubre1 comment1 person in discussion
Latesttech 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 (likeen.wikipedia.org), instead of via a redirect to an "m" domain (likeen.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.[79]
Newdate filters,creationdate: andlasteditdate:, 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.[80]
Wikifunctions now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created aLatin declination table that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see anexample output. If you need any help or have any feedback, pleasecontact the Wikifunctions Team.[81]
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.[82]
View all 34 community-submitted tasks that wereresolved last week. For example, there was a problem downloading pdf files last week and that has been resolved.[83]
Updates for technical contributors
The fieldrev_sha1 in the revision database table is being removed in favor ofcontent_sha1 in the content database table. Seethe announcement for more information.
TheReader Experience team will roll outDark 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 tolearn 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 onthis talk page before the enablement.[84]
Starting on Monday, October 6, API endpoints under therest.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 theService Ops team board.[85]
Latest comment:13 Oktubre1 comment1 person in discussion
Latesttech 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 forSpecial: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 theAccount 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 atSpecial: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.[86]
This week, users at wikis where talk pageUsability Improvements are already available by default (everywhereexcept the 12 wikis listed inT379264) 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 canlearn more about this change.[87]
Users who have notverified 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.[88][89]
View all 21 community-submitted tasks that wereresolved 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.[90]
Updates for technical contributors
The Unsupported Tools Working Group has chosenVideo2Commons 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:20 Oktubre1 comment1 person in discussion
Hello. Please help pick a name for the new Abstract Wikipedia wiki project. This project will be a wiki that will enable users to combine functions fromWikifunctions and data from Wikidata in order to generate natural language sentences in any supported languages. These sentences can then be used by any Wikipedia (or elsewhere).
There will be two rounds of voting, each followed by legal review of candidates, with votes beginning on 20 October and 17 November 2025. Our goal is to have a final project name selected on mid-December 2025. If you would like to participate, thenplease learn more and vote now at meta-wiki.Thank you!
Latest comment:20 Oktubre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
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.[91]
View all 20 community-submitted tasks that wereresolved last week. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed.[92]
Updates for technical contributors
The work to reroute all traffic to API endpoints under therest.php route through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to theService 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.[93]
Wereleased the"Add a Link" Structured Task to 100% of accounts at English Wikipedia on Tuesday, September 2nd (before then it was available to 20% of accounts).
After examining if the Growth features and Mentorship could be adapted to Wikidata, we activated the Growth features onBeta Wikidata to allow for testing and discussion (T400937).Although some features, like Suggested Edits, are Wikipedia-specific, the Growth team designed most features to be more wiki-agnostic.
The machine learning team has been working on a new model that can suggest links to more languages, including Urdu, Chinese, and Japanese Wikipedias.We are starting to release the “Add a Link” feature to Wikipedias that weren’t supported by the previous model.
The Growth team is involved in several research initiatives to help guide our future work:
Progression System – We havepublished initial findings from interviews with 10 English and French Wikipedia newcomers.The research examined motivations, challenges, and feedback on a prototype system intended to help editors build confidence, develop skills, and contribute more constructively over time.
Mobile Web Editing Research – This project combines quantitative and qualitative data, community feedback, and user journey analysis to identify possible ways to enhance the mobile editing experience.
Newcomers Survey – This project surveys successful newcomers on English Wikipedia to understand their early editing experiences, tool use, and community interactions.
The Growth team participated in several community events to listen, share, and collaborate on improving newcomer experiences across Wikimedia projects.
This session invited organizers to share how they introduce newcomers to Growth features and the challenges they encounter. The discussion focused on common newcomer questions and opportunities to strengthen collaboration in supporting new editors.
This talk demonstrated how Structured Tasks help newcomers take their first successful steps on Wikipedia. It shared impact data, community configurations, and a demo of “Add a Link,” illustrating how these tasks make editing more accessible and sustainable, particularly for mobile contributors.
With active editor numbers declining, theContributors Strategy aims to create a clearer, more engaging path for participation. This session, led by the WMF Contributors group with involvement from the Editing, Growth, Moderator Tools, and Connection (formerly Campaigns) teams, highlighted efforts to streamline contributor experiences, offer structured and mobile-friendly workflows, and foster meaningful engagement. Participants learned about ongoing initiatives and shared feedback to help shape a more inclusive and sustainable future for Wikimedia contributors.
Many communities face a decline in volunteer engagement. Newcomers often leave soon after joining, while experienced editors struggle to manage increasingly complex workflows and overwhelming backlogs. We presented theContributors Strategy and the different features and workflows that can help communities to address these challenges. We listened to the specific needs of the CEE communities to help guide the Contributors teams' work.
Latest comment:27 Oktubre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
The Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You canread more on the project page.
Autoconfirmed users onsmall andmedium wikis with the CampaignEvents extension can now useEvent Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
View all 31 community-submitted tasks that wereresolved last week. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed.[94]
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 theEspesyal:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on theproject launch page.[95]
Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using theREST Sandbox. See theMediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
A dedicatedchangelog now exists for the MediaWiki REST API. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, pleasejoin the discussion.
Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked fromQ130635582. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited.[96]
Applications for the committees open on October 30, 2025. Applications for the Affiliations Committee, Ombuds commission and the Case Review Committee close on December 11, 2025. Learn how to apply byvisiting the appointment page on Meta-wiki. Post to the talk page or email cstwikimedia.org with any questions you may have.
Latest comment:3 Nobiyembre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Administrators will now find thatEspesyal: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).[97]
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 "Pagdugang og topiko" 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.[98]
Scribunto modules can now be used togenerate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files.[99]
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.[100]
Users with large watchlists have long faced timeouts when editingSpecial:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. Acommunity wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish![101]
View all 31 community-submitted tasks that wereresolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query.[102]
Updates for technical contributors
Since 2019 theWikimedia URL Shortener athttps://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means/s/ URLs will not be advertised under article titles via HTMLclass="title-shortlink". The/s/ URLs will keep working.[103]
On Thursday, October 30, theMediaWiki Interfaces andSRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to theService Ops team board.
MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025.[104]
In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia ina Diff blog post.
Latest comment:10 Nobiyembre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Example of a talk page with the new design, in French.
MediaWiki can now display apage indicator automatically while a page is protected. This feature is disabled by default. It can be enabled bycommunity request.[106]
Using the "Paunang tan-aw" or "Ipakita ang kalainan" 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.[107][108][109]
Wikivoyage wikis can usecolored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed.[110]
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.[111]
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.[112]
View all 27 community-submitted tasks that wereresolved last week. For example the inability to lock accounts on mobile sites has been fixed.[113]
TheJWT subject field inOAuth 2 access tokens will soon change from<user id> tomw:<identity type>:<user id>, where<identity type> is typicallyCentralAuth: (forSUL wikis) orlocal:<wiki id> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and thesessionJwt cookie more similar. Old access tokens will still work.[115]
AREL1_45 branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change.[117]
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.[118][119]
Latest comment:17 Nobiyembre1 comment1 person in discussion
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
TheReader Experience team is experimenting withreading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of theAccount Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
As part of theParser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in theExtension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the"Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag theContent Transform Team in Phabricator.
Unsupported Tools: Several issues withVideo2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check thePhabricator board.
Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026.Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please emailhackathon@wikimedia.org.
Hello. Reminder: Please help to choose name for the new Abstract Wikipedia wiki project. The finalist vote starts today. The finalists for the name are:Abstract Wikipedia, Multilingual Wikipedia, Wikiabstracts, Wikigenerator, Proto-Wiki. If you would like to participate, thenplease learn more and vote now at meta-wiki.Thank you!
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Last week, theWikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching forcxfcnmt on Russian Wikipedia will now add suggestions forсчастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week.[121]
Later this week, users of the "Improved Syntax Highlighting"beta feature will have syntax highlighting available inDiscussionTools. This requires that the "Enable editing tools in source mode" preference be set.[122]
Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known asCollaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcominglearning session to see the new feature in action and share your feedback.
View all 24 community-submitted tasks that wereresolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed.[123]
Updates for technical contributors
Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill therecruitment survey.[124]
The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support forformat=xml&xlst={stylesheet} will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026).[125]
The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph orhttps://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review theData Access andRequest a Query pages for details and assistance on alternative access methods.
.jpg)