User talk:Pine - Meta-Wiki

Hello, I am happy to share that script draft 1 is complete and ready for public comment.

The script (link to the Google doc) is much longer than I anticipated, at almost 21 pages!

Although I think that the 21 page script would be a very good introduction to referencing policies and workflows, I am considering dividing it into two or more smaller scripts that would be produced as separate videos. For example, one script could focus on policies and a different script could focus on how to use the citation tool. I am considering this for three reasons:

• People may be more willing to watch shorter videos that have more specific focus.
• Shorter videos may be easier to search for an answer for a single specific question.
• There is a possibility that if I attempt to produce a single video from almost 21 pages of script that I might exceed the budget for this mini-project. I would like for both WMF and the community to be satisfied with the results from this mini-project, and I think that dividing the script into smaller scripts which could be produced separately would be a good way to ensure that the budget for the current grant is not exceeded. While there is a reasonable possibility that I could finish production of the entire 21 pages of script within the current grant, I think that dividing the script would be prudent. After one of the smaller scripts is fully produced within the currently available funding, remaining script could be considered for production within the current grant if there seems to be adequate remaining funds, or could be saved for possible production with a future grant.

I would very much appreciate constructive criticism and comments regarding the script, preferably by March 10 at 11:59 PM UTC. This is a shorter time window than I would like to provide, but the planned end date for this project is March 14 and I would like to finish video production by the end of March 13 so that I have 24 hours for communications before the grant period ends. If you would like to review the script or make other comments but the end of March 10 is too soon for you, please let me know that you need more time, and I will take that into consideration as I plan for final production and consider whether to request a date extension from WMF. (Extending the finish date for the project would not involve requesting additional funding for the current grant.) I would prefer that the video be done perfectly a few days late than that the video be done on March 14 but have an important error that was not caught during a rush to the finish.

I have three specific requests for feedback:

1. Please find errors in the script. This is a great time to find problems with my work, before the script goes into production and problems become more expensive to fix. Please go to this link in Google Docs and use the Comment feature in the Google Doc.

2. Do you have comments regarding whether the script should be divided, and if so, how it should be divided? Please let me know on the project talk page.

3. How do you feel about the name for the video? Do you prefer "Referencing with VisualEditor" or "Citing sources with VisualEditor", or a third option? Again, please comment on the project talk page. However, if I divide the script then I will create new names for the smaller videos.

Thank you for your interest in this mini-project. I am grateful to be working on a project which I hope will help Wikipedia contributors to be more efficient and effective, and indirectly help to improve Wikipedia's quality by teaching contributors how to identify and to cite reliable sources. I believe that the finished video will be good, and I hope that the community and novice contributors will find the video to be very useful.

Yours in service,

--Pine✉ 07:55, 7 March 2019 (UTC)Reply

Hi! The full version of this newsletter issue has a lot of information. I am sending a short version to talk pages.

The most important information to know is that draft 2 is finished, that the single long script has been divided into many smaller scripts, and that portions of the script have been prioritized for production.

Due to budget constraints, not all scripts can be produced within the scope of the current pilot grant, but the other scripts will remain available for potential future production. (This project feels somewhat like doing a vehicle repair when the mechanic starts to work on the engine, and once the mechanic gets under the engine and starts to work, they discover that accomplishing their objective requires twice as much time as they first had estimated.) However, nothing is lost, so do not fear. Overall, my assessment (me being User:Pine) is that this project is producing a lot of good output and is generally a valuable pilot project.

For more information, including my requests for your feedback, please see the full version of the newsletter.

Thanks very much. --Pine(✉) 22:38, 22 March 2019 (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

• Reference Check has been deployed to English Wikipedia, completing its rollout across all Wikipedias. The feature prompts newcomers to add a citation before publishing new content, helping reduce common citation-related reverts and improve verifiability. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop and about 17.5 times more likely on mobile web. [1]

Updates for editors

• The InterwikiSorting extension, which allowed for the sorting of interwiki links, has been undeployed from Wikipedia. As a result, editors who had enabled interwiki link sorting in non-compact mode (full list format) will now see links reordered. The links moving forward will be listed in the alphabetical order of language code. [2]
• Later this week, people who are editing a page-section using the mobile visual editor, will notice a new "Edit full page" button. When tapped, you will be able to edit the entire article. This helps when the change you want to make is outside the section you initially opened. [3][4]
• The Reader Experience team is inviting editors to assess whether dark mode should still be considered "beta" on their wiki, based on their experience of how well it functions on desktop and mobile. If the feature is deemed mature, editors can update the interface messages in MediaWiki:skin-theme-description and MediaWiki:Vector-night-mode-beta-tag to indicate that dark mode is ready and no longer considered beta.
• The improved Activity tab which displays user-insights is now available to all users of the Wikipedia iOS app (version 7.9.0 and later). Following earlier A/B testing that showed higher account creation among users with access to the feature, it has been rolled out to 100% of users along with some updates. The Activity tab now shows your edited articles in the timeline, offers editing impact insights like contribution counts and article view trends, and customization options to improve in-app experience for users.
• View all 21 community-submitted tasks that were resolved last week. For example, a bug that prevented DiscussionTools from working on mobile has now been fixed, restoring full functionality. [5]

Updates for technical contributors

• The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension that makes this possible continues to improve. The latest upgrade is the inclusion of a new hook, ext.globalwatchlist.rebuild, which fires after each watchlist rebuild. This allows you to run gadgets and user scripts for the Special page. [6]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Wikipedia 25 Birthday mode is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via community configuration on the local wiki.

Updates for editors

• Sub-referencing, a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and a couple of other wikis. You can try the feature on these projects or on testwiki and betawiki. Learnings from the first pilot wiki German Wikipedia have been published in a report. Reach out to the Wikimedia Deutschland team if you are interested in becoming a pilot wiki.
• Paste Check will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check tags all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via Special:EditChecks. Research across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can help to localize this and related features.
• The Reader Experience team will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface. [7]
• Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one. [8]
• Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon. [9]
• The Global Watchlist which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The extension now allows activating the language fallback system for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no uselang= URL parameter is provided. [10][11]
• The Wikipedia Android team has started a beta test of hybrid search on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily.
• For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will gradually change in March. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule. [12]
• View all 27 community-submitted tasks that were resolved last week. For example, the issue preventing users from creating an instance in Wikibase.cloud has now been fixed. [13]

Updates for technical contributors

• To help ensure fair use of infrastructure, over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
• The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts. [14]
• The new Parsoid parser continues to be deployed to additional wikis, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.
• The process and criteria for requesting exceptional access to the high volume feed of the Wikimedia Enterprise APIs (at no cost for mission-aligned usecases), have now been published. This is to provide more thorough and clearer documentation for users.
• Tech Blog, the blog dedicated to the Wikimedia technical community will be migrating to Diff, the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Highlights
Let's Talk continues

• Birthday mode: This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. The feature is available for all Wikipedias to customise through Community Configuration until 6 April 2026. So far 17 Wikipedias have joined in the fun.
• Wikipedia's 25th birthday party celebrated on Commons: Content from the January 15th global birthday party selected as Media of the day.

Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org

• Etherpad cleanup: For security and performance reasons, all current pads on Wikimedia’s Etherpad instance, the web-based "ephemeral" editor for real-time collaborative document editing, will be permanently deleted after 30 April. We will continue running this Etherpad instance to support events and other short-term collaboration, but will be periodically deleting data going forward. If you have content in Etherpad you want to keep, please create local backups, as data will be permanently deleted and will not be able to be recovered.
• Activity tab: Wikipedia iOS app has rolled out the improved Activity tab to all users in version 7.9.0. A/B test results showed increased account creation among users with access to the feature. Updates include enhanced editing impact insights, module customization, and relocation of History into the Search tab.
• Reference Check: The feature Reference Check has been deployed to all Wikipedias. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop (or acknowledge/explain why they did not) and about 17.5 times more likely on mobile web.
• Semantic search: The Foundation has launched a limited Android mobile app experiment that tests hybrid search capabilities which can handle both semantic and keyword queries. The Phase 1 beta is now live on Greek Wikipedia. The goal is to understand whether combining meaning-based retrieval with keyword search helps readers find information more effectively. Testing will expand to English, French, and Portuguese Wikipedias in March.
• Navigation experience: The Foundation will run an experiment for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias.

• Site notices: Site notices (MediaWiki:Sitenotice and MediaWiki:Anonnotice) now will render on all platforms, not just on the desktop site. Users on mobile web will now see these notices and be informed.
• Tech News: Latest updates from Tech News week 08 and 09 include the new “Edit full page” button for people who are editing a page-section using the mobile visual editor. They also link to the 40 community submitted tasks that were resolved over the last two weeks.
• Wikifunctions: Abstract Wikipedia is going to have its public preview within the next few weeks, here is the preview.

Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · The Wikipedia Library · list of movement events

Annual Goals Progress on Effectiveness
See also: Progress on the annual plan

Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · Milestones · Wikidata · Central and Eastern Europe · other newsletters

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
• Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the post on the Stewards' noticeboard (translations).

Updates for editors

• Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as iCloud Private Relay) will receive clearer guidance on what they need to do to start editing again. [15]
• Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [16]
• View all 23 community-submitted tasks that were resolved last week. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools. [17]

Updates for technical contributors

• API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
• The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and give feedback. You can also sign up for usability tests.
• The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read this update to learn more.
• Detailed code updates later this week: MediaWiki

In depth

• The Article Guidance team invites experienced Wikipedia editors from selected pilot wikis and interested contributors from other Wikipedias to fill out this questionnaire which is available in English, Arabic, Bengali, Japanese, Portuguese, Persian, and Turkish. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more on the project page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The ⧼codemirror-beta-feature-title⧽ beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share. [18]
• Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks. [19]
• On wikis using Flagged Revisions, the number of pending changes shown on Special:PendingChanges previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself. [20]
• Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about the changes.
• Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [21]
• View all 28 community-submitted tasks that were resolved last week. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed. [22]

Updates for technical contributors

• A new special page, Special:LintTemplateErrors, has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: Special:LintTemplateErrors/night-mode-unaware-background-color. [23]
• Users of the ⧼codemirror-beta-feature-title⧽ beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome. [24]
• The CodeMirror JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the ext.CodeMirror or ext.CodeMirror.lib modules from gadgets and user scripts was deprecated in July 2025. The use of the ext.CodeMirror.switch hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the migration guide for more information. [25]
• The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include extension APIs. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for GrowthExperiments and Wikifunctions APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the REST Sandbox (i.e., Special:RestSandbox, available on all wiki projects).
• The Scribunto extension provides different pieces of information about the wiki where the module is being used via the mw.site library. Starting last week, the library also provides a way of accessing the wiki ID that can be used to facilitate cross-wiki module maintenance. [26]
• Detailed code updates later this week: MediaWiki

In depth

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Highlights

• Supporting readers: For most of its history, Wikipedia did not have to worry about attracting readers. But with the way people search for information changing, there is a drop in the number of readers which is impacting the number of accounts created and contributions to our sites. Have a look at some of the ongoing and planned work to support reader experience.
• Server switch: All wikis will be read-only for a few minutes on March 25 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year.
• Tools improvement: The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads.
• Wikipedia 25 Grants: The celebration continues! The Wikimedia Foundation offers Wikipedia 25 Birthday Funds to communities planning Wikipedia’s 25th birthday events with funding between USD 1,000–2,000. Apply before March 31.

Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org

• Experiments: The Foundation is frequently conducting experiments to help learn what features will be most effective and valuable to the projects. The list of experiments in Product and Technology, tracks upcoming, live, in-analysis, and completed experiments as well as their rationale. For example, the tracker shares that one upcoming experiment, Reader to Contributor Baseline, will measure how many readers create contributor accounts and whether the rate differs depending on how people arrived to the site.
• Article guidance: Help less experienced editors by filling out a questionnaire on this page (available in 7 languages). The Foundation are looking particularly for experienced Wikipedia editors from these pilot wikis. Your answers will help customize guidance for less experienced editors while creating an article.
• Wikifunctions: You can now create Functions that will show a citation in their output.
• Editing feature: Suggestion Mode is available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines.
• Paste Check: Paste Check is now available at all Wikipedias. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation.
• Mobile experience: The user menu in the top corner for all mobile users is standardized so that it is closer to the desktop experience to improve the user interface for readers.
• Two-factor authentication: For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will gradually change in March.
• Tech News: Latest updates from Tech News week 10 and 11 include the new GraphQL API has been released as a flexible alternative to select features of the Wikidata Query Service (WDQS). They also link to the 50 community submitted tasks that were resolved over the last two weeks.

Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · The Wikipedia Library · list of movement events

Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · Milestones · Wikidata · Central and Eastern Europe · other newsletters

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
• All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.

Updates for editors

• Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced. [27]
• Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project. [28]
• The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown. [29]
• Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation. [30]
• View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.

Updates for technical contributors

• Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible. [31][32]

• The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
• Detailed code updates later this week: MediaWiki

In depth

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Beta version of Abstract Wikipedia a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. Read more.

Updates for editors

• The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. Read more.
• The Wikimedia Apps team is inviting feedback on how editing should work on the Wikipedia mobile apps. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
• View all 45 community-submitted tasks that were resolved last week. For example, an issue where citation fetching from the large newspaper archive Newspapers.com was no longer working, due to a block in Citoid requests, has now been fixed. [33]

Updates for technical contributors

• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Highlights

• Supporting the mobile experience: The Foundation is starting conversations with communities to explore how editing should work on the Wikipedia mobile apps. The goal is to understand how to better support both new and experienced editors, and how the app can guide users to the right editing tools. Your input is welcome. Join the discussion!
• Wikimania 2026: Registration for Wikimania 2026 is opening soon from the end of March to May 1. Like other Wikimedia events this year, we are introducing a "request for invitation" process, with trust and safety checks conducted prior to confirming in-person attendance. Our priority is to create a safe environment for connection, collaboration, and shared learning.
• Around the Puzzle Globe in the CEE region: On March 23 almost 60 Wikimedians took part in the CEE-Catch up- a meeting for Wikimedians from Central and Eastern Europe and Central Asia. As a part of continuous conversations we have with the communities around the Foundation's annual plan, participants discussed the global trends related to Readers and Contributors in their regional context. The meeting was also an opportunity to connect with the new Foundation CEO, Bernadette Meehan, who is meeting communities around the puzzle globe to listen, learn and engage with the communities.

Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org

• Crawlers: The Foundation is now detecting and blocking billions of bot requests that don’t follow our robot policy, such as aggressive scrapers, to make sure our resources go towards serving human readers. In the coming months we’ll be working on better detection of rapidly changing bot behavior and better API infrastructure.
• Moderator tools for newer editors: Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to an early version of Special:PersonalDashboard. It introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
• Account creation on mobile: Mobile editors at several wikis are now presented with a simplified logged-out warning message, which encourages them to create an account or log in. This test is part of our ongoing effort to enhance the account creation experience on mobile and increase participation.
• Verification email redesign: The verification email sent to new accounts that add an email address during signup has been redesigned. When tested on English Wikipedia, Wikimedia Commons, and Wikidata, the same-week email verification rate increased from 41.6% to 45.9%.
• Retaining notification history: Wikimedia site users can export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain important notifications and avoid losing them based on the planned change to delete notifications older than 5 years, as previously announced.
• Tech News: Latest highlights from Tech News weeks 12 and 13 include the update that Wikimedia site users can now log in without a password using passkeys as a secure method supported by fingerprint, facial recognition, or PIN. See also the 64 community submitted tasks that were resolved over the last two weeks.
• Experiments: Check out the list of experiments in Product and Technology to see all upcoming, live, in-analysis, and completed experiments. One new experiment that just went live is the "Improve the logged-out warning message on mobile web," which aims to reduce the sense of friction or alarm when users encounter the logged-out warning upon editing.

Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · The Wikipedia Library · list of movement events

Annual Goals Progress on Effectiveness
See also: Progress on the annual plan

Board and Board committee updates
See Wikimedia Foundation Board noticeboard · Affiliations Committee Newsletter

Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · Milestones · Wikidata · Central and Eastern Europe · other newsletters

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
• The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
• View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [34]

Updates for technical contributors

• The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected. [35]
• All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
• The Action API has had several formats for requested output. One of them, format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots. [36]
• The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [37]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Experienced editors are invited to test the Article guidance feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are available. Also, after reviewing the outlines, please provide feedback on the project talk page. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out the video explaining the feature.

Updates for editors

• On most wikis, all autoconfirmed users can now use Special:ChangeContentModel page to create new pages with custom content models, such as mass message lists, making custom page formats more accessible. Check Special:ListGroupRights for the status of your wiki. [38]
• The Growth team has launched an account creation experiment to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
• View all 30 community-submitted tasks that were resolved last week. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [39]

Updates for technical contributors

• Starting later this week, Abuse filter editors who have the ⧼codemirror-beta-feature-title⧽ beta feature enabled will have CodeMirror instead of CodeEditor as the editor at Special:AbuseFilter. This is part of the broader effort to make the user experience more consistent across all editors. [40][41]
• Tools and bots that access the Notifications API (action=query&meta=notifications) will need to update their OAuth or BotPassword grants to also include access to private notifications. [42]
• Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [43]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Highlights

Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org

• Navigating articles on mobile: The Foundation is launching an experiment to test how to make it easier and more intuitive for readers to navigate through articles on mobile. To do this, we want to test Mobile Page Previews. This experiment will go live the week of April 20 and will run for four weeks.
• Editing tools for new editors: Tone Check was deployed on French, Japanese, and Portuguese Wikipedia as a default-on feature for editors who have published 100 or fewer edits locally. When promotional or subjective language is added, users are prompted to consider "neutralizing" the tone of the edit.
• Managing watchlist labels: The new watchlist labels feature is now available via VisualEditor, the source editor, and the "watchstar" (or watch link, for skins that don’t have a star icon). Previously it was only possible to assign labels via EditWatchlist.
• Latest experiments: See all upcoming, live, in-analysis, and completed experiments in Product & Technology. A new experiment that just went live is one which aims to establish a baseline retention rate for logged-in readers.
• Latest Wikifunctions: Check out the partial list of the 102 new functions created last week – likely the first week we have exceeded 100.
• Tech News: The latest highlights from Tech News weeks 14 and 15 include an ongoing A/B test running on 10 Wikipedias to evaluate a clearer, more user-friendly message that promotes account creation on wikis. See also the 68 community submitted tasks that were resolved over the last two weeks.
• Community discussions on Semantic Search: The Wikimedia Foundation, in collaboration with the CEE Hub, hosted a discussion session on Semantic Search for members of the CEE Youth Group.

Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · The Wikipedia Library · list of movement events

• Don't Blink!: This month's highlights from the Global Advocacy team include how the Wikimedia Foundation co-presented alongside the Internet Archive at the State of the Net conference.
• Digital rights and inclusion: Take a look at the sessions that Wikimedians and allied partners will lead during Digital Rights and Inclusion Forum (DRIF) 2026.
• Manuscript preservation: The Wikimedia Foundation supported volunteer-lead workshops to write Balinese Wikipedia articles about palm-leaf manuscripts (lontar) from the Leiden University Library collection.
• Youth content creators: Wikimedia Indonesia, together with the Wikimedia Foundation, delivered an introductory session on Wikipedia for young content creators representing all 11 ASEAN member states.
• Legal and Safety Contacts: The Wikimedia Foundation has created a single "Legal and Safety Contacts" page, to be linked in the footer of each wiki page. This will ensure that everyone has access to accurate and up to date Legal contact information. Insertion of the new links on different wikis will be done in stages, based on assessment of legal risk and necessity.
• Building shared principals for the internet as a public good: The Global Advocacy team published a blog with the Center for Studies on Freedom of Expression and Access to Information (CELE) and the Electronic Frontier Foundation (EFF) summarizing a workshop that brought together digital rights advocates from Latin America to dream of a "digital utopia."

Annual Goals Progress on Effectiveness
See also: Progress on the annual plan

• Wikidata API: Wikidata’s structured knowledge is now available through Wikimedia Enterprise.
• Annual Planning and global trends: Join the America APP call on April 21 at 18:00 UTC. This meeting is an opportunity for the Latin American community to ensure that the region's voice helps shape the Wikimedia Foundation's work and priorities for the next fiscal year. The call will be in Spanish with interpretation into Portuguese and English. The last meeting between Wikimedia EDs and Foundation staff was dedicated to discuss global trends too. More discussions are happening on-wiki and in community spaces around different regions and projects.
• Futures Lab: The world is changing around us. As the Wikimedia movement navigates this moment over a hundred Wikimedians from different Wikimedia projects came together to deepen our understanding of how these trends are impacting our people and projects at the Wikimedia Futures Lab.
• Fundraising Hub: The Wikimedia Foundation has launched Fundraising Hub on English Wikipedia. The first discussion you can participate in is about distributing fundraising banner on English Wikipedia throughout the year.

Board and Board committee updates
See Wikimedia Foundation Board noticeboard · Affiliations Committee Newsletter

• Ombuds Commission: Announcement of the 2026 Ombuds Commission, the small group of volunteers who investigate complaints about violations of the Privacy Policy, the Access to Nonpublic Personal Data Policy, the CheckUser Policy and the Oversight Policy.
• Wikinews closure: All Wikinews editions will be closed and switched to read-only mode on May 4. Content will remain accessible, but no new edits or articles will be able to be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions.

Other Movement-curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · Milestones · Wikidata · Central and Eastern Europe · other newsletters

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• After two years of development, ⧼codemirror-beta-feature-title⧽, also known as CodeMirror 6, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other benefits to all users of the standard syntax highlighter. A huge thank you to volunteer Bhsd who developed many of the new features, including code folding, autocompletion, and linting. [44]
• A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. Download the latest version and explore the update.

Updates for editors

• Reading lists is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
• An experiment which explores extending Page Previews to mobile web will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. Read more about this experiment and others.
• On several wikis, logged-in editors who haven't confirmed their email addresses can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. Learn more. [45]
• View all 15 community-submitted tasks that were resolved last week. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed. [46]

Updates for technical contributors

• As part of the promotion of CodeMirror from a beta feature, all users will use CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages. [47]
• The mirrors.wikimedia.org service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. You can read more. [48]
• The image and oldimage table will be removed from wikireplicas. If your tools or queries access image or oldimage directly, please update them to use the file and filerevision table before 28 May. [49]
• Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure fair use of infrastructure by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
• The Attribution API is now available as a beta. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the REST sandbox on English Wikipedia). Share your feedback on the project talk page.
• There is no new MediaWiki version this week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.