Hello everyone
If you don't use etherpad, you can ignore this message.
We will *delete all pads after 1st March 2026*! If you need any of your
pads, please make a local backup. We will not be able to recover the data
after 1st March.
The pad cleanup helps to reduce the size of the database and the footprint
on our infrastructure. After the cleanup, etherpad can still be used for
real-time collaboration but please do not expect long term storage.
Additional cleanups might happen after that unannounced.
See also https://phabricator.wikimedia.org/T415237 for more information.
Greetings and thank you
Jelto
Hey all,
User scripts and gadgets often become outdated without notice. When a .js
or .css page changes, a dependency shifts, or a repository moves forward,
things can break or remain outdated longer than expected unless someone is
actively watching.
This is a small but recurring issue in daily workflows, especially when
tracking is mostly manual and spread across multiple places.
To address this, I built a tool called *WikiScriptSync* that monitors
repositories and specific user pages such as .js and .css files, in near
real time. It surfaces updates as they happen, instead of relying on manual
checks or watchlists.
This tool may be useful for:
- Maintainers of user scripts and gadgets
- Admins and interface editors managing sitewide scripts
- Developers tracking repositories or shared code
- Anyone responsible for keeping scripts up to date
The system is currently functional with working subscriptions, event
tracking, and notifications. Documentation and setup details are available
on Meta-Wiki <https://meta.wikimedia.org/wiki/WikiScriptSync> and Wikitech
<https://wikitech.wikimedia.org/wiki/Tool:WikiScriptSync>.
You can try it out here: https://script-publisher.toolforge.org/
This is an early version and feedback would be useful, especially regarding
real use cases and improvements.
Built as part of Developer Skill Development Program India 2025
<https://meta.wikimedia.org/wiki/Developer_Skill_Development_Program_India_2…>
under IMDUG
Thanks,
Dev Jadiya
Hi
We are now ready to start rolling out the next phase of global API rate
limits. As previously announced
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>,
this will apply to all API requests, including those that we class as
identified.
The full set of limits
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits> have now been
published on wiki, along with answers to frequently asked questions
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits/FAQ> that we
received after the roll out of limits to anonymous requests. We will
gradually ramp down to the published limits, starting from next Tuesday
28th April. We expect to be at the final limits by the end of May.
As part of this change we have moved from per-hour limits to per-minute
limits, so please bear that in mind when you first look at the docs! This
is preferable, as it helps smooth aggregate request rates and also minimises
the impact on any user that inadvertently hits a limit.
These limits are based on extensive analysis of API request data, but it is
possible that some bots or gadgets may still trigger rate limits. We will
be actively monitoring all relevant spaces, so please do let us know if you
need help to work out the best way forward should this happen.
Thank you for your engagement with this. I hope from our actions it is
clear that we are not trying to limit community usage, but protect our
projects from automated usage at a scale we cannot support
<https://diff.wikimedia.org/2026/03/26/quo-vadis-crawlers-progress-and-whats…>
without ensuring it is a fair and sustainable use
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Responsible_Reuse>
of resources.
Best
Jonathan
--
Jonathan Tweed (he/him)
Senior Product Manager, Core Platform
Wikimedia Foundation
Hey all,
This is a quick note to highlight that we've created the REL1_46 branch for
MediaWiki core and each of the extensions and skins in Wikimedia git [0].
This is the first step in the release process for MediaWiki 1.46.0, which
should be out in June 2026, approximately six months after MediaWiki 1.45.0.
The branches reflect the code as of the last 'alpha' branch for the
release, 1.46.0-wmf.26, which was deployed to Wikimedia wikis on Tuesday,
28th April, for MediaWiki itself and those extensions and skins available
there.
From now on, patches that land in the main development branch of MediaWiki
and its bundled extensions and skins will be slated for the MediaWiki 1.47
release, unless specifically backported [1].
If you are working on a critical bug fix that will affect the code in the
release, once the patch has been merged into the development branch, you
should propose it for backporting by cherry-picking to the REL1_46 branch.
If you are working on a new feature, that should now not be backported. If
you have an urgent case where the work should block release for everyone
else, please file a task against the `mw 1.46-release` project on
Phabricator [2].
If you have tickets that are tagged for `mw-1.46-release`, please finish
them, untag them, or reach out to get them resolved in the next few days.
We hope to issue the first release candidate, 1.46.0-rc.0, in roughly three
weeks' time, and if all goes well, to then release MediaWiki 1.46.0 a few
weeks after that.
[0]: https://www.mediawiki.org/wiki/Bundled_extensions_and_skins
[1]: https://www.mediawiki.org/wiki/Backporting_fixes
[2]: https://phabricator.wikimedia.org/tag/mw-1.46-release/
Check out the results!
https://www.mediawiki.org/wiki/Developer_Satisfaction_Survey/2026
____
This year, 207 respondents from the Wikimedia developer community
answered questions about:
- Wikimedia Toolforge and Cloud VPS
- MediaWiki code quality
- Wikimedia API use
- Documentation
- Research
- Developer tools and processes
The Wikimedia Developer Satisfaction survey was open for 4 ½ weeks,
from Thu, 04 December 2025 through Mon, 05 January 2026[0].
The developer survey helps us decide what to work on next and review
what we worked on last.
____
Thank you to everyone who took the time to fill out our survey!
And thanks to everyone who worked hard crafting questions and making
sense of answers.
Final, big, giant thank you to Caroline Myrick for all her work on
survey design, data visualization, making sense of all the data we
collected, and for being a wonderful, tireless human being.
<3
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
>
Summary:
The Cloud Services implementation of Superset
(https://superset.wmcloud.org) is currently unsupported by WMF staff. We
would welcome a volunteer stepping up to maintain it, but without a new
home the service will be shut down at the end of March.
If you would like to take on ownership of this service, please reach out
to WMCS staffor comment on the phabricator task[1]. The day-to-day
maintenance load is minimal, but someone will need to keep track up
updates, security concerns and a potential future of defense against AI
scraping.
Background:
There has always been demand from researchers and volunteers to run
one-off queries against Wikimedia datasets. Quarry.wmcloud.org was built
and launched by the WMF more than 10 years ago. Originally a one-person
skunkworks project, it quickly caught on in popularity as one of the
most trafficked services run by Wikimedia Cloud Services.
A few years ago, we launched superset.wmcloud.org[0] as an intended
Quarry replacement. We soon learned that despite being a less polished,
home-made tool, Quarry provides many features that Superset does not,
and most users resisted migration away from it. Superset has only a
handful of active users.
At this point, Superset is essentially unsupported by WMF staff. As part
of ongoing efforts to improve our support for Toolforge and other more
popular services we will be either shutting it off or transferring
ownership of Superset in a few weeks[1].
[0] https://phabricator.wikimedia.org/T169452
[1] https://phabricator.wikimedia.org/T416373
Hey all, apologies for the previous email with incorrect dates and title.
This is a quick note to highlight that in the week of 21st of April 2026,
the REL1_46
branch will be created for MediaWiki core and each of the extensions and
skins in Wikimedia git, with some (the 'tarball') included as sub-modules
of MediaWiki itself[0]. This is the first step in the release process for
MediaWiki 1.46, which should be out in June 2026, approximately six months
after MediaWiki 1.45.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.46.0-wmf.25, which will be deployed to Wikimedia wikis in the
week beginning 21 April 2026 for MediaWiki itself and those extensions
and skins available there.
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be instead be slated
for the MediaWiki 1.47 release unless specifically backported[1].
If you are working on a new feature that you wish to land for the release,
you now have a few days to finish your work and land it in the development
branch; feature changes should not be backported except in an urgent case.
If your work might not be complete in time, and yet should block release
for everyone else, please file a task against the `mw-1.46-release` project
on Phabricator.[2]
If you have tickets that are already tagged for `mw-1.46-release`, please
finish them, untag them, or reach out to get them resolved in the next few
weeks.
We hope to issue the first release candidate, 1.46.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.46.0 a few
weeks after that in the beginning of June.
[0]: <https://www.mediawiki.org/wiki/Bundled_extensions_and_skins>
[1]: <https://www.mediawiki.org/wiki/Backporting_fixes>
[2]: <https://phabricator.wikimedia.org/tag/mw-1.46-release/>
Good news, everyone!
A new Attribution API <https://www.mediawiki.org/wiki/Attribution_API>
module is now available as a beta
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Stability_policy> on all
Wikimedia Foundation hosted wiki projects. The purpose of this API is to
make it easier to appropriately attribute Wikimedia project content when
it’s presented or referenced in off-wiki contexts. This API directly
supports the Wikimedia Attribution Framework
<https://wikimedia-attribution.toolforge.org/>, which provides specific
guidelines for how to appropriately attribute content across different
reuse scenarios and form factors.
What does it do?
The Attribution API <https://www.mediawiki.org/wiki/Attribution_API>makes
it easy to follow the guidelines outlined in the Wikimedia Attribution
Framework <https://wikimedia-attribution.toolforge.org/>. The API provides
the information required by each attribution signal in a single,
well-structured and easy-to-use endpoint. Although the recommended
attribution information was largely already available through existing
APIs, this approach significantly simplifies the process for developers,
which we believe will make it more likely that developers will follow the
recommended standards.
Who is it for?
Appropriate attribution is critical for all reuse scenarios where Wikimedia
content will be presented off-wiki, as it ensures that the content is
fairly credited and that external readers remain aware of the Wikimedia
projects and communities it came from. This means that if you make games,
offer search services, use project content for research, build alternative
reader experiences, or contribute to anything else happening off-wiki, you
probably need to properly attribute Wikimedia content!
This specific API is also primarily intended for mission-supporting users
and use cases. Wikimedia Enterprise will offer similar information in their
structured responses for scaled commercial reuse.
How do I participate?
We encourage everyone to try out the endpoints and give us your feedback on
the project discussion page
<https://www.mediawiki.org/w/index.php?title=Talk:Attribution_AP>!
Additionally, if you discover what you think might be a bug, please feel
free to file an issue directly to the MediaWiki Interfaces Phabricator board
<https://phabricator.wikimedia.org/project/view/6931/>.
Major changes will minimally be announced on the project page
<https://www.mediawiki.org/wiki/Attribution_API>. If you are interested in
this capability, we recommend that you add the page to your watchlist to
stay informed with the latest changes and calls for targeted feedback. Some
of these changes may also be announced here or through Tech News, but the
nature of a beta does not guarantee broad communication of every change.
What should I expect?
This API is available on all Wikimedia projects, and is initially being
released as a beta
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Stability_policy>. Reference
documentation can be found in the REST API sandbox
<https://www.mediawiki.org/w/index.php?title=Special:RestSandbox&api=attribu…>
on any Wikimedia wiki (such as the REST API sandbox on English Wikipedia
<https://en.wikipedia.org/w/index.php?api=attribution.v0-beta&title=Special%…>).
Although available everywhere, the Attribution API only explicitly supports
Wikipedia articles and media files hosted through either Wikipedia or
Commons. We need your help testing and shaping additional project and
content types to help inform how the information should be structured.
We are continuing to iterate and refine the API. Although we expect the
interface itself to remain relatively stable, the specific returned values
are subject to change over time. Breaking changes to adjust the interface
or response structures may also occur during the beta period as we respond
to emerging feedback and feature requests.
Following the beta period, we will elevate the API to a stable v1. This
will be done after we are satisfied with meeting user expectations and when all
high priority issues are resolved. Although there is not yet a firm date
for when we will elevate this experience, we expect it to happen around
September 2026, depending on the nature of requests that arise during the
beta period. Additional communications will happen closer to the stable
version launch date to ensure the community is aware of the upcoming change.
Please feel free to reach out directly here or post on the project
discussion page
<https://www.mediawiki.org/w/index.php?title=Talk:Attribution_AP> if you
have any questions, comments or concerns! We look forward to your feedback
and support in helping us refine this API, as well as the beta process
itself.
Thanks, and happy attribution!
Halley
*Halley Coplin* (she/her)
Sr. Product Manager, MediaWiki Interfaces
Wikimedia Foundation <https://wikimediafoundation.org/>