User talk:Matma Rex

Help test better mass message delivery

Hi. You're being contacted as you've previously used global message delivery (or its English Wikipedia counterpart). It doesn't feel so great to be spammed, does it? ;-)

For the past few months, Legoktm has built a replacement to the current message delivery system called MassMessage. MassMessage uses a proper user interface form (no more editing a /Spam subpage), works faster (it can complete a large delivery in minutes), and no longer requires being on an access list (any local administrator can use it). In addition, many tiny annoyances with the old system have been addressed. It's a real improvement! :-)

You can test out MassMessage here: testwiki:Special:MassMessage. The biggest difference you'll likely notice is that any input list must use a new {{#target:}} parser function. For example, {{#target:User talk:Jimbo Wales}} or {{#target:User talk:Jimbo Wales|test2.wikipedia.org}}. For detailed instructions, check out mw:Help:Extension:MassMessage.

If you find any bugs, have suggestions for additional features, or have any other feedback, drop a note at m:Talk:MassMessage. Thanks for spamming! --MZMcBride (talk) 05:25, 1 October 2013 (UTC)

Beginning of MassMessage, end of EdwardsBot

Hi. You're being contacted as you're listed as an EdwardsBot user.

MassMessage has been deployed to all Wikimedia wikis. For help using the new tool, please check out its help page or drop a note on Meta-Wiki.

With over 400,000 edits to Wikimedia wikis, EdwardsBot has served us well; however EdwardsBot will no longer perform local or global message delivery after December 31, 2013.

A huge thanks to Legoktm, Reedy, Aaron Schulz and everyone else who helped to get MassMessage deployed. --MZMcBride (talk) 02:36, 22 November 2013 (UTC)

Translation of Module namespace name

Hello, Matma Rex! I'm an administrator at ro.wiki and I would like to localize the name of the Module namespace. The page https://www.mediawiki.org/wiki/Help:Namespaces#Localisation directs me at https://translatewiki.net/w/i.php?language=ro&module=namespace&title=Special%3AAdvancedTranslate, but I can't find the Module namespace there. I also found the page Lua deployments/Localization of Module, but I see you closed it because the issue https://bugzilla.wikimedia.org/show_bug.cgi?id=46082 is resolved. How should we translate the name of the Module namespace now? Have a happy new year, Rsocol (talk) 18:26, 31 December 2013 (UTC)

The translations should be "Modul" and "Discuție Modul". Thanks, Rsocol (talk) 05:31, 3 January 2014 (UTC)

See also Stewards' noticeboard#Renaming namespaces and https://translatewiki.net/wiki/Support#Rename_module_namespace_40423. Rsocol (talk) 05:37, 3 January 2014 (UTC)

Letter petitioning WMF to reverse recent decitions

The Wikimedia Foundation recently created a new feature, "superprotect" status. The purpose is to prevent pages from being edited by elected administrators -- but permitting WMF staff to edit them. It has been put to use in only one case: to protect the deployment of the Media Viewer software on German Wikipedia, in defiance of a clear decision of that community to disable the feature by default, unless users decide to enable it.

If you oppose these actions, please add your name to this letter. If you know non-Wikimedians who support our vision for the free sharing of knowledge, and would like to add their names to the list, please ask them to sign an identical version of the letter on change.org.

• Letter to Wikimedia Foundation: Superprotect and Media Viewer
• Letter on change.org

I'm notifying you because you participated in one of several relevant discussions. -Pete F (talk) 22:13, 20 August 2014 (UTC)

Global user page migration

Hello Matma Rex. Synchbot deleted your local user pages on all wikis as requested. You can see the full log on your archive page. :) —Pathoschild 03:34, 22 February 2015 (UTC)

Editinterface rights expired

Hello, your editinterface rights have expired. Please start a new request on SRGP to refresh them. Thanks for the work you've done over the past year with them! Ajraddatz (talk) 04:48, 2 June 2015 (UTC)

@Ajraddatz: Thanks for the reminder, did it now. Matma Rex (talk) 17:59, 3 June 2015 (UTC)

When next week's Tech News issue doesn't exist

Hey, thanks for adding something for next week's issue. Feel free to initiate the next issue if you need it for some reason – less risk of me (or someone else) missing the hidden item and leaving it there for the translators in the wrong week. (: You could also add it to the talk page, either of the issue being prepared or just the general Tech News talk page. /Johan (WMF) (talk) 14:31, 28 June 2018 (UTC)

The Community Wishlist Survey

Hi,

You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.

You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:24, 30 October 2018 (UTC)

Your temporary access has expired

Hello, the temporary global access you requested has expired. Just to let you know that If you want it back, feel free to open a new request on stewards' global permission request page on Meta-Wiki later. Please ask me or any other steward if you have any questions. Thank you! — regards, Revi 18:59, 28 February 2019 (UTC)

Your temporary access is going to expire soon

Hello Matma Rex. You were granted temporary global permissions which is going to expire in a few days (17 March 2020). Just to let you know that if you want to continue with the access, you need to request an extension on stewards' global permission request page on Meta-Wiki. Please ask me or any other steward if you have any questions. Thank you! —MarcoAurelio (talk) 11:52, 1 March 2020 (UTC)

Your temporary access has expired

Hello, the temporary global access you requested has expired. Just to let you know that If you want it back, feel free to open a new request on stewards' global permission request page on Meta-Wiki later. Please ask me or any other steward if you have any questions. Thank you! --—Thanks for the fish! ^{talk•contribs} 20:33, 30 March 2020 (UTC)

A barnstar for you!

		The Community Wishlist Survey Barnstar
		For completing the wish proposal: Improve plain-text change tag selector! NRodriguez (WMF) (talk) 21:30, 3 March 2022 (UTC)

NRodriguez (WMF) (talk) 21:31, 3 March 2022 (UTC)

Reminder to vote now to ratify the Wikimedia Movement Charter

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Dear Wikimedian,

You are receiving this message because you previously voted in the 2021 Movement Charter Drafting Committee (MCDC) election.

This is a reminder that if you have not voted yet on the ratification of the final Wikimedia Movement Charter draft, please do so by July 9, 2024 at 23:59 UTC.

You can read the final text of the Wikimedia Movement Charter in your language. Following that, check on whether you are eligible to vote. If you are eligible, cast your vote on SecurePoll.

On behalf of the Charter Electoral Commission,

RamzyM (WMF) 15:24, 5 July 2024 (UTC)

Notice of Patch Demo Wikis Cleanup

You are receiving this message because there is/are wiki(s) on Patch Demo associated with your account. Per our records, the patches associated with them have been merged or abandoned. In an effort to manage space and ensure our systems have the capacity to continue providing the best service and experience for our users, we will be auditing and deleting wikis with merged or abandoned patches on Friday, March 14 2025.

Please refer to the list of wikis we will be deleting [1] and if you wish to keep any of the ones that belong to you, edit the table accordingly before Thursday, March 13 2025 11:59PM UTC. If we do not hear from you by then we will assume you are not opposed to this action and will proceed as planned. EBomani-WMF (talk) 22:20, 6 March 2025 (UTC)

Notice of expiration of your global-interface-editor right

Hi, as part of Global reminder bot, this is an automated reminder to let you know that your global permission "global-interface-editor" will expire on 2025-07-13 13:11:53. If you want to renew this right, please file a request at SRGP. In other languages: click here Leaderbot (talk) 19:41, 6 July 2025 (UTC)

Join us for “Many Tongues, One Movement: Voices Across Languages”!

Hello Matma Rex,

We’re excited to invite you to an inspiring global virtual gathering: the first Capacity Exchange Translat-a-thon.

Together with Language Diversity Hub, the Capacity Exchange (CapX) team will host its first Translation Marathon dedicated to ensuring linguistic equity in access to this amazing tool aimed to connect Wikimedians.
If you enjoy contributing to Wikimedia projects through translating and adapting content into different languages, this event is for you! Join us in the celebration of the multilingual spirit of the Wikimedia Movement at an event where communities that contribute in diverse languages will be able to share local knowledge and collaborate across borders.
Many Tongues, One Movement: Voices Across Languages

• Date: December 6, 2025
• Time: 12 PM (UTC) - Check the event page for your local timezone
• Location: Online (Meta-Wiki + live session links)

Register for the Event here

If you can’t join the live event, you can still contribute to the translations! Edits will be counted for two weeks, until December 20th. And everyone who participates will receive a special badge to display on their CapX profiles.

Strengthen your collaboration through CapX

We invite you and your community to join the Capacity Exchange (CapX), a Wikimedia community-built platform for connecting, collaborating, and exchanging skills with peers across the movement.

CapX helps Wikimedians and organizations find each other, share expertise, and build stronger, more connected communities.

Whether you’re an individual contributor, a user group, a community initiative or an affiliate, CapX helps you grow through knowledge exchange.

Sign up to CapX

More information

→ Explore the CapX platform: capx.toolforge.org
→ Read: User Guide & FAQ
→ Watch: Meet the Capacity Exchange video
→ Join our Telegram community chat: CapX Telegram Group

If your community, usergroup or affiliate would like to have a CapX organization profile, please reach out at capx@wmnobrasil.org, and we’d be delighted to support you.

With warm regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil

MediaWiki message delivery (talk) 14:55, 13 November 2025 (UTC)

Gerrit

Hello! I'd like to ask if you're interested in continuing to be added as a reviewer on my Gerrit changes. Most of the code is in JavaScript, since I have more experience with it, and the rest is in PHP. Thank you. IKhitron (talk) 18:30, 21 December 2025 (UTC)

@IKhitron Hi, I don't mind it :) I was happy to see your name on Gerrit. I didn't have time to review it yet, since I had a busy week or two, but I'm having a look now. Matma Rex (talk) 21:27, 22 December 2025 (UTC)

Thanks a lot. IKhitron (talk) 21:28, 22 December 2025 (UTC)

Thank you very much for the patch approval. There are three more patches ready, for extremely small patches, it took five minutes to write them. When two more people answer to this gerrit question in the section topic, I will be able to add everybody that agreed to the reviewers list. IKhitron (talk) 21:56, 22 December 2025 (UTC)

Wow. Thanks again a lot. But I'm curios, how did you know what to do in the patch demos, I did not publish the instructions yet? IKhitron (talk) 22:11, 22 December 2025 (UTC)

@IKhitron Well, all I had to do was to make some edits, watchlist a page, and have a look at Special:GlobalWatchlist, right? It was easy enough to figure out from your commit messages and the linked tasks, and the patches were indeed simple. Matma Rex (talk) 22:43, 22 December 2025 (UTC)

I see. Yes, it's easy. But no, all this was already done on Alice's account, with possible cases. IKhitron (talk) 22:50, 22 December 2025 (UTC)

Oh… I don't think I looked at your demos for them, I just tested them myself. I'll keep that in mind to save some time in the future! Matma Rex (talk) 23:00, 22 December 2025 (UTC)

Wikimedia Hackathon Northwestern Europe 2026

Hello! I came across your name on a previous Wikimedia hackathon participant page, so I thought you might be interested in this.

We're organizing the Wikimedia Hackathon Northwestern Europe 2026, taking place on 13–14 March 2026 in Arnhem, the Netherlands. It's a two-day, in-person hackathon for technical Wikimedians from the region.

Since you've attended a hackathon before, you already know how valuable these events can be for collaboration, learning, and getting things done together. We'd love to have you join us!

Apply here – registration closes mid-January or when full.

Feel free to reach out if you have any questions. Hope to see you in Arnhem! Daanvr (talk) 17:49, 12 January 2026 (UTC)

Beta Cluster

Hello. First thing, let me thank you again for all you're doing for Global Watchlist on Gerrit in last weeks, I'm very grateful. I'm here to ask for your advice. There is one patch in WIP, entry structure rebuild, you still had no time to answer in the Phab task, that I do not want to merge to master when it will be ready. I just do not know what will happen with it in real, big wikifarm, with different kinds of wikis. And as we could see yesterday, Testwiki is too late. What do you thing about the possibility to merge this specific change to Beta Cluster, when and only when it will be completely ready? If there are mistakes, we could see them before the deployment and fix in time. For example, I expect uncertainty on Wikidata in this new change, and there is no way to test it in Patch Demo, but Beta Cluster has its own Wikidata. I consider even to add to this change a couple of lines for another small Wikidata-directed task, it fits the theme, so it will be tested together. And yes, Beta Cluster Meta has Global Watchlist, connected to the rest of the cluster by its own CentralAuth. What do you think? Thank you in advance. IKhitron (talk) 08:38, 21 January 2026 (UTC)

@IKhitron That sounds alright to me, however, note that deployment to the Beta Cluster is normally automatic – if I approve a patch on Gerrit, and it gets merged into the Git repository, then a few minutes later is gets deployed to the Beta Cluster by an automated job (https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/How_code_is_updated). This job can be stopped, and the code can be deployed manually, but this will prevent other changes from being automatically deployed.

Given the above, I think the easiest way to test on Beta Cluster is to just approve the patch on Gerrit, so it will be deployed there automatically. You'll have a few days to test and submit any additional patches before the production deployment starts on the next Tuesday (https://wikitech.wikimedia.org/wiki/Deployments/Train). Does that sound okay? Matma Rex (talk) 18:54, 21 January 2026 (UTC)

Thank you.
a few minutes later is gets deployed to the Beta Cluster by an automated job
Didn't know that, it's great.
Does that sound okay?
If I would work alone I would say yes, but I don't know when anyone (probably you) approves the change, it can be hours before Tuesday morning branch cut. I can't tell you "check it in specific day", it's just rude. And also, if I find a problem, and since the moment I wrote fix until Tuesday morning there is nobody to approve the fix, because I can't tell "check it in specific day" again, it's another problem. Especially taking into account that it will be a big change, and it will take time to approve it. So, I don't know what to say. IKhitron (talk) 19:01, 21 January 2026 (UTC)

I can still review it whenever I want, and only click the big button later. Just make a note on the patch that it should be merged after a branch has been cut to give more time for testing, nothing rude about it, it's a fairly common practice for patches that are risky or require a complex setup to test. I'll make sure to be available to review any follow-up patches if they are needed (or, in the worst case, we can always revert the patch and try again next week). Matma Rex (talk) 22:02, 21 January 2026 (UTC)

Great. Thanks a lot! IKhitron (talk) 22:05, 21 January 2026 (UTC)

In this case, is there a chance for me to make the other Wikidata task in a new change, or it's too much to ask? Thank you. Because I just thought about it, it looks very simple, but I can't test it even a little before the review, Wikibase is needed for just to see how it runs. IKhitron (talk) 22:42, 21 January 2026 (UTC)

Yeah, sure. Matma Rex (talk) 13:48, 22 January 2026 (UTC)

Great, thanks. IKhitron (talk) 13:54, 22 January 2026 (UTC)

thanks for passkeys & webauthn work phab:T358771

I saw that Passkeys were announced Tech News #5 (2026) . Thanks for all the help and effort working on webauthn & Passkeys phab:T358771 Tonymetz (talk) 23:14, 27 January 2026 (UTC)

Script Publisher - Community Wishlist 2022 implementation update

Hello Matma Rex,

I hope you are doing well. I am reaching out regarding the Community Wishlist Survey 2022 proposal you supported: “A bot or gadget to publish public Git repo to a gadget or user script”

Over the past few months, I have been working on implementing this as a Toolforge-based OAuth application called Script Publisher. The goal is to provide a web-based interface that allows users to publish JS/CSS files from a public Git repository (e.g., GitHub) directly to user scripts or gadget pages, with explicit preview and confirmation before publishing.

Current project links:

1. Toolforge deployment (work-in-progress MVP): https://script-publisher.toolforge.org/
2. Source code (public repository): https://gitlab.wikimedia.org/toolforge-repos/script-publisher/
3. Initial demo prototype: https://wikipublisher.vercel.app/

The tool currently supports:

• Public repository fetching
• File selection (JS/CSS)
• Mapping files to target wiki pages
• Preview before publish
• Manual publish flow (no background automation)

The main blocker now is OAuth approval for JS-editing permissions. WMF security has raised valid concerns around applications that can edit JavaScript pages, especially site-wide JS. The discussion is ongoing here:

1. User_talk:Dev_Jadiya#Script_Publisher
2. https://meta.wikimedia.org/wiki/Steward_requests/Miscellaneous#OAuth_permissions

Since you originally supported this wishlist proposal, your technical input and perspective would be extremely valuable. In particular:

• Does the current MVP align with what you expected from this wishlist?
• Are there safeguards you believe are necessary for responsible deployment?
• Would you be willing to share your view in the ongoing Meta discussion?

My intention is not to bypass any security expectations, but to implement this in a way that is aligned with community review standards (similar to bots or interface editors), while keeping the tool transparent, auditable, and limited to user-authorized edits.

Thank you again for supporting the original idea. I would truly appreciate your feedback. Regards, Dev Jadiya (talk) 14:38, 7 February 2026 (UTC)

More work

Hello again. First of all, thank you again for everything you are doing for the Global Watchlist extension. I'm here to report you that yesterday in the evening I finished everything I can do there for now. There is a big job that is waiting for me, that can easily take months, but I can't start until I get an answer on a theoretical question I asked a week ago in some place, I'm stuck without it. Of course, there is nothing that I could do that depends on you specifically, otherwise I would not open this topic at all, it would be rude. So, the question is: is there something you want me to do, for now, in this time I suddenly have, for the extension? Thank you. IKhitron (talk) 08:15, 10 February 2026 (UTC)

@IKhitron Hey. Sorry, I've been really busy over the last week or two. I'll look through your recent work eventually, but if there's anything you want me to look at first, please share a link here – I'm not sure what is the question that you're waiting for. I don't have any requests for you. Matma Rex (talk) 17:44, 10 February 2026 (UTC)

Please don't be. I can expect from people to answer a question quickly and surprised when they don't because it takes seconds. I definitely don't think this about checking code, or writing code, or any other thing that takes time, because people have a lot of other things to do. I do not think I have something above others in particular. But if you want me to, I can collect all the things I'm waiting and give you all the links in the order I need them, so if you have time and want to you can go through this order. And not looking for them between all the mails too. Thank you. IKhitron (talk) 17:51, 10 February 2026 (UTC)

Sorry, totally forgot to answer on this one. I asked there about how to change a system variable on Patch Demo. If and when they answer I will know if I can debug the big work. IKhitron (talk) 18:26, 10 February 2026 (UTC)

@IKhitron If you want to change it for all wikis, you'll want to propose a patch for Patch Demo here: [2] (this is in GitLab, not Gerrit). There isn't much documentation, but you can have a look at existing merge requests for examples. The configuration for GlobalWatchlist is here: [3]

If you want to change a config setting on just one wiki to test something, you can create a Gerrit patch that would change that config setting, mark it as WIP so it doesn't get merged by accident, and create a new Patch Demo using that patch (in addition to the code changes you want to test). There is no way to do this nicely in the interface at the moment. Here's an random example patch like this: [4]

Hope this helps! Matma Rex (talk) 19:40, 10 February 2026 (UTC)

I very appreciate that you wanted to help and answered, even I didn't ask you. I considered to ask, but decided not to waste your time, when you're doing already so much for the extension. I tryed your suggestion, and it did not work. The problem is that I need to change a mediawiki/core variable, such that it will work on every page in the wiki before it loads. I knew about DNM patch, and tryed some, but couldn't find the right place to edit. What I need is to make the Watchlist Labels work on Patch Demo, such that the page Special:WatchlistLabels, for example, will actually work instead of a red message "Watchlist labels do not work on this wiki".

And also, you didn't answer about the links list, so I see it as a no. If I'm wrong or if you change your mind, just say. Thank you. IKhitron (talk) 20:11, 10 February 2026 (UTC)

I had a look at a few patches just now, but I mostly picked the ones that seemed easy to review :) I just missed that question, feel free to send me a list of which ones are most important for you. I'll have a look at them next time.

Regarding WatchlistLabels on Patch Demo, I see your attempt: [5]. I guess the problem is that config changes to core have to be made in several places – for example, like this: [6] (yes, this is stupid and annoying). For a Patch-Demo-only patch, you can instead put the override at the end of includes/Setup.php, like this: [7]. Matma Rex (talk) 22:19, 10 February 2026 (UTC)

Thanks a lot. I'll check the comments in one of the changes, and try the Setup.php tomorrow. Also, will make the rebases. About the list, in "send" I believe you mean send in mail. Very well, will do.

UPD: Done, one phabricator comment and two changes. Thank you.

UPD UPD: The system variable works. Thanks a lot! IKhitron (talk) 22:29, 10 February 2026 (UTC)