This user's talk page is monitored by talk page watchers. Some of them even talk back. Their input is welcome, and their help with messages that I cannot reply to quickly is appreciated.
Frostly is taking a short wikibreak and will be back on Wikipedia soon.
Frostly is currently busy with personal commitments. Your patience with delays in message replies is appreciated.
My talk page archives are in disorder, and I'd love any help in fixing them! Otherwise, I'll get to them eventually.
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the post on the Stewards' noticeboard (translations).
Updates for editors
Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as iCloud Private Relay) will receive clearer guidance on what they need to do to start editing again.
Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools.
Updates for technical contributors
API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.
The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and give feedback. You can also sign up for usability tests.
The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read this update to learn more.
The Article Guidance team invites experienced Wikipedia editors from selected pilot wikis and interested contributors from other Wikipedias to fill out this questionnaire which is available in English, Arabic, Bengali, Japanese, Portuguese, Persian, and Turkish. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more on the project page.
Special report: What actually happened during the Wikimedia security incident? A horrifying exploit took place, which could have had catastrophic and far-reaching consequences if used maliciously; instead, it seems to have happened by accident and was used for childish vandalism. How did this happen, and what did the script actually do?
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The ⧼codemirror-beta-feature-title⧽ beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share.
Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks.
On wikis using Flagged Revisions, the number of pending changes shown on Special:PendingChanges previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself.
Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about the changes.
Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'.
View all 28 community-submitted tasks that were resolved last week. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed.
Users of the ⧼codemirror-beta-feature-title⧽ beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome.
The CodeMirror JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the ext.CodeMirror or ext.CodeMirror.lib modules from gadgets and user scripts was deprecated in July 2025. The use of the ext.CodeMirror.switch hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the migration guide for more information.
The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include extension APIs. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for GrowthExperiments and Wikifunctions APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the REST Sandbox (i.e., Special:RestSandbox, available on all wiki projects).
The Scribunto extension provides different pieces of information about the wiki where the module is being used via the mw.site library. Starting last week, the library also provides a way of accessing the wiki ID that can be used to facilitate cross-wiki module maintenance.
The 2026 Coolest Tool Award celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the nomination survey form by 23 March 2026. For more information on privacy and data handling, please see the survey privacy statement.
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Updates for editors
Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced.
Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown.
Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation.
View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.
Updates for technical contributors
Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible.
The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Beta version of Abstract Wikipedia a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. Read more.
Updates for editors
The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. Read more.
The Wikimedia Apps team is inviting feedback on how editing should work on the Wikipedia mobile apps. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
View all 45 community-submitted tasks that were resolved last week. For example, an issue where citation fetching from the large newspaper archive Newspapers.com was no longer working, due to a block in Citoid requests, has now been fixed.
Following a motion, the GSCASTE extended-confirmed restriction in the Indian military history case has been narrowed. It now applies to caste-related topics in South Asia, and the preemptive protection remedy has been amended accordingly.
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed.
Updates for technical contributors
The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected.
All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
The Action API has had several formats for requested output. One of them, format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots.
The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia.
Hello and welcome to the April 2026 newsletter, a quarterly digest of Guild activities since December. We extend a warm welcome to all of our new members. We wish you all happy copy-editing.
Election results: In our December 2025 coordinator election, incumbents Dhtwiki, GoldRomean, Miniapolis, and Mox Eden were reelected coordinators, and Wikieditor662 was newly elected coordinator, to serve through 30 June. Nominations for our mid-year Election of Coordinators will open on 1 June (UTC).
December 2025 Blitz: 16 of the 31 editors who signed up for the December 2025 Copy Editing Blitz edited 116,064 words in 47 articles. Barnstars awarded are here.
January Drive: 35 of the 55 editors who signed up for the January Backlog Elimination Drive edited 498,397 words in 183 articles. Barnstars awarded are here.
February Blitz: 19 of the 23 editors who signed up for the February Copy Editing Blitz edited 83,969 words in 43 articles. Barnstars awarded are here.
March Drive: 28 of the 48 editors who signed up for the March Backlog Elimination Drive edited 210,064 words in 87 articles. Barnstars awarded are here.
April Blitz: Sign up for our April Copy Editing Blitz, which runs from 12 to 18 April. Barnstars will be awarded here.
Progress report: As of 09:10, 10 April 2026 (UTC), GOCE copyeditors have processed 81 copyediting requests since 1 January 2026. The backlog of articles needing copyediting stands at 1,794 articles.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Dhtwiki, GoldRomean, Miniapolis, Mox Eden and Wikieditor662.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Experienced editors are invited to test the Article guidance feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are available. Also, after reviewing the outlines, please provide feedback on the project talk page. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out the video explaining the feature.
The Growth team has launched an account creation experiment to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed.
Updates for technical contributors
Starting later this week, Edit filter managers who have the ⧼codemirror-beta-feature-title⧽ beta feature enabled will have CodeMirror instead of CodeEditor as the editor at Special:AbuseFilter. This is part of the broader effort to make the user experience more consistent across all editors.
Tools and bots that access the Notifications API (action=query&meta=notifications) will need to update their OAuth or BotPassword grants to also include access to private notifications.
Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia).
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
After two years of development, ⧼codemirror-beta-feature-title⧽, also known as CodeMirror 6, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other benefits to all users of the standard syntax highlighter. A huge thank you to volunteer Bhsd who developed many of the new features, including code folding, autocompletion, and linting.
A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. Download the latest version and explore the update.
Updates for editors
Reading lists is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
An experiment which explores extending Page Previews to mobile web will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. Read more about this experiment and others.
On several wikis, logged-in editors who haven't confirmed their email addresses can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. Learn more.
View all 15 community-submitted tasks that were resolved last week. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed.
Updates for technical contributors
As part of the promotion of CodeMirror from a beta feature, all users will use CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages.
The mirrors.wikimedia.org service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. You can read more.
The image and oldimage table will be removed from wikireplicas. If your tools or queries access image or oldimage directly, please update them to use the file and filerevision table before 28 May.
Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure fair use of infrastructure by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
The Attribution API is now available as a beta. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the REST sandbox on English Wikipedia). Share your feedback on the project talk page.
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the Autoconfirmed users group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions.
All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the reading lists beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access.
View all 30 community-submitted tasks that were resolved last week. For example, the issue where infobox images have huge padding in Firefox, has been fixed.
Updates for technical contributors
As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure fair use of infrastructure. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
Latest comment: 1 month ago1 comment1 person in discussion
The administrator elections process has officially started! Interested editors are encouraged to self-nominate or arrange to be nominated by reviewing the instructions at Wikipedia:Administrator elections/May 2026/Candidates.
Here is the schedule:
April 29 – May 5: Call for candidates
May 8–12: Discussion phase
May 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 1 month ago1 comment1 person in discussion
The second round of the 2026 WikiCup ended on 28 April. As a reminder for contestants who just joined or are unaware of recent changes to our round-points system, good article nomination reviews now receive 10 points, an increase from 5 points in the previous year, as per a consensus at WT:CUP. Peer reviews, which continue to be worth 5 points, are now listed in the same section as featured article candidate reviews, rather than with good article reviews. Everyone who competed in round 2 will advance to round 3 unless they have withdrawn or been banned. No other changes to the round-point system have been made for this year.
Round 2 was competitive. Three contestants scored more than 1,000 round points; nine scored over 500; and fourteen scored over 300. The top seven contestants had at least one featured article (two of them with two apiece). The following competitors scored more than 800 round points:
MCE89(submissions) with 1,333 points, mainly from good and featured articles about Australian people and geography
Bgsu98(submissions) with 1,149 points, mainly from good articles, featured articles, and featured lists about figure skating, along with many article reviews and two good topics
Olliefant(submissions) with 830 points, mainly from good and featured articles about television shows, episodes and media, along with nearly four dozen good and featured article reviews
The full scores for round 2 can be seen here. During this round, contestants have claimed 12 featured articles, 13 featured lists, 2 featured-topic articles, 106 good articles, 22 good-topic articles and more than 40 Did You Know articles. In addition, competitors have worked on 3 In the News articles, and they have conducted over 200 reviews. The tournament points table has been updated.
Remember that any content promoted after 28 April but before the start of Round 3 can be claimed in Round 3. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points. If you are concerned that your nomination—whether it is at good article candidates, a featured process, or anywhere else—will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews Needed. If you want to help out with the WikiCup, feel free to review one of the nominations listed on Wikipedia:WikiCup/Reviews Needed. Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 14:49, 29 April 2026 (UTC)Reply
Struggling to find scientific works to write about? Start with review articles or textbooks, which may highlight influential studies, theories or methods by women.
Changes to user permissions made from Meta are now included in the local user permissions log (T6055).
The autoconfirmed user group will soon be modified such that the four-day account age requirement begins when an account makes its first edit (T418484).
Arbitration
The arbitration case SchroCat has been opened. Evidence submissions in this case closed on 15 April.
Per a recent motion, appeals of blocks from the conflict-of-interest VRT queue are, by default, appealed on-wiki through the normal unblock process. However, they may be heard by the Committee if COIVRTers disagree on the interpretation of the evidence or believe ArbCom would be better suited to hear the appeal. Administrators are also advised that loosening or lifting such blocks without the consent of someone with access to the queue or ArbCom can be grounds for desysopping.
Per a recent motion, restrictions issued directly by the Committee may now be enforced with blocks which work exactly like contentious topic blocks.
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.
The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so.
From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages.
The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed.
Updates for technical contributors
The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
On 13 May, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 25 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.
Updates for editors
The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed.
In the voting phase, the candidate subpages close to public questions and discussion, and everyone who qualifies to vote has a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's vote total during the election. The suffrage requirements are similar to those at RFA.
Once voting concludes, we will begin the scrutineering phase, which will last for a few days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a non-recall candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Recall candidates must achieve 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 22 days ago1 comment1 person in discussion
Hello Frostly,
New Page Review queue November 2025 - May 2026
Backlog update
At the time of this message, there are 15,282 articles and 32,951 redirects awaiting review.
After the January–February drive the article backlog was reduced to 15,179 articles and the redirect backlog to 19,053 respectively. Great job! However, both queues are growing rapidly and any additional reviews are highly appreciated.
2024 and 2025 NPP Awards
JTtheOG was selected as the NPP reviewer of the year for both 2024 and 2025, for reviewing the most articles amongst all reviewers.
Hey man im josh and MPGuy2824 won the Redirect Ninja Master Award for 2024 and 2025 respectively, for reviewing the most redirects.
Overall in 2024, one Platinum, two Gold, eight Silver, 12 Bronze and 45 Iron Barnstars were awarded. Additionally, 66 reviewers got the NPP barnstar for doing more than 100 reviews through the year. In 2025, one Platinum, ten Silver, 13 Bronze and 38 Iron Barnstars were awarded. Additionally, 38 reviewers got the NPP barnstar for doing more than 100 reviews through the year.
The experimental two-month long backlog drive concluded with 183 reviewers patrolling over 27,761 articles and 35,309 redirects, earning over 36,836 points. Congratulations to JTtheOG, who achieved first place with 6,484.6 points in this drive.
An attempt was made to get the New Pages Feed to sort by date marked as reviewed instead of date created. However we had to revert it due to bugs. We may try again in the future. You can subscribe to the Phabricator ticket if you're interested in following along.
Latest comment: 18 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.
Updates for editors
An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights.
Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed.
Updates for technical contributors
The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.
Latest comment: 16 days ago1 comment1 person in discussion
I am contacting you because you previously voted in elections related to the Universal Code of Conduct Coordinating Committee (U4C). You may be eligible to vote in the current U4C election, which is open now and closes on 2 June 2026. You can find out more about the candidates and the election on the election page on Meta, and from there you can access the vote itself. Your participation in these elections is important to the governance of Wikimedia communities, and your time spent learning about the candidates and voting is appreciated.
Latest comment: 14 days ago1 comment1 person in discussion
News and notes: Offline: Osama Khalid still in prison He has been imprisoned since 2020 for his Wikipedia edits. A fresh campaign is calling for his release.
Recent research: WikiLambda the Ultimate Does Abstract Wikipedia help fight "One ring to rule them all" solutions for knowledge access - or does it implement one itself?
Latest comment: 11 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics.
Updates for editors
For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules.
After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed.
Updates for technical contributors
The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read more.
Mandatory 2FA for bureaucrats: Bureaucrats without two-factor authentication (2FA) enabled have already lost access to their advanced rights on 26 May. Those who do not enable 2FA may be automatically removed from the groups in mid-June 2026, and from that point onward, new members must have 2FA enabled before they can be added. (T423119, T423120)
Latest comment: 4 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The Reader Experience team is conducting an experiment to show the reading lists feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The experiment was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
The Wikimedia Apps team released Phase 1 of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
View all 18 community-submitted tasks that were resolved last week. For example, an issue where images could fail to load for some suggested edits on Special:Homepage, leaving the thumbnail stuck in a loading state, has now been fixed.
Latest comment: 2 days ago1 comment1 person in discussion
The Developing Countries WikiContest Gold Belt Buckle
Hey Frostly, it's almost that time again! The Developing Countries WikiContest will be returning for its third year, and the coordinator team is looking for experienced content contributors willing to volunteer. The coordinators are responsible for keeping the contest running and its pages—including participants' submissions, the points leaderboard, and the list of eligible articles—updated.