Meta:Babel/Archives/2025-08

Ready for translation: Education Newsletter July 2025

July 2025 education newsletter released for translation. Please help our readers to read education newsletter in their native language. The latest education newsletter is ready for translation: here Newsletter headlines link for translation: here, to read individual articles check out: Category:Education/Newsletter/July 2025. Regards, ZI Jony ^(Talk) 02:56, 1 August 2025 (UTC)

@ZI Jony, please also include link to Template:Education Navigation into your invitations. Kaganer (talk) 09:57, 6 August 2025 (UTC)

Noted. Regards, ZI Jony ^(Talk) 16:34, 7 August 2025 (UTC)

☁ Ray Butcher (talk) 09:22, 12 August 2025 (UTC)

hridoy.khan57327@ 103.242.8.180 09:49, 12 August 2025 (UTC)

Display problem

When I successfully mark pages for translation, the check icon on the left side of the notice squeezed. Probably not the only instance. I don't know where to post it, so I'll leave it here. —— Eric Liu_（Talk） 15:47, 14 August 2025 (UTC)

@Ericliu1912 does it appear similar to phab:T398529#11048062? Johannnes89 (talk) 13:52, 15 August 2025 (UTC)

Yes! Glad to see there was already a Phab task filed. —— Eric Liu_（Talk） 14:22, 15 August 2025 (UTC)

site name changed from Meta to Meta-Wiki

Per the prior discussion and phab:T399843, our sitename has been changed. The database name has not been changed. If you see any problems, please let us know. — xaosflux ^Talk 13:34, 18 August 2025 (UTC)

Need help from bot

Hi!

I need the help from a bot to apply the following algorithm:

const listOfPages = mw.getListOfPagesStartingWith( "Wiki Loves Living Heritage/" );

const replaceRegex = new RegExp(`<!--BEGINREPLACE.+<!--ENDREPLACE-->`, "s");
const backupRegex = new RegExp(`{{Wikidata list.+{{Wikidata list end}}`, "s");

for( page in listOfPages ) {
	let matchingContent = page.wikitext.match( replaceRegex );
	if( ! matchingContent ) matchingContent = page.wikitext.match( backupRegex );
	if( ! matchingContent ) continue;

	let contentToMove = matchingContent[0];
	let newSubPageName = page.pageName + '/list';
	page.wikitext.replace( contentToMove, '{{:' + newSubPageName + '}}' ); //must be absolute path (for translation pages)
	page.save();

	mw.createPage(
		pageName: newSubPageName,
		pageWikitext: contentToMove
	);
}

Aim: moving Wikidata List to their own subpage, then transcluding the subpage, so what you see do not change.

Point: many of those pages are translatable. Each time the bot update the Wikidata list, a translation admin must mark the page for translation, which is uselessly time-consuming.

Unfortunately, I have never set a bot up, and I have not enough time to learn. Can someone help?

Pinging Susannaanas for information.

-- Pols12 (talk) 14:49, 12 August 2025 (UTC)

@Pols12: What wanna you? As human, simple? What is problem? You write (in Aim) how wanna you implement, but i dont know what is the problem (example, if i would be a user, a none-technical user). Dušan Kreheľ (talk) 10:46, 13 August 2025 (UTC)

I explained it in the “point” item: each time a translatable page is updated, a translation admin has to “mark the page for translation” to validate the changes so they are applied to translation pages. Since those are Wikidata lists, the bot update the pages every day. This is really time-consuming for translation admins to review all of those bot changes!

Benefits:

• As a translation admin, this change would reduce my workload.
• As a final user, I see the page up-to-date in my language as soon as ListeriaBot updates the page, I don’t need to wait for translation admin work.

-- Pols12 (talk) 12:14, 13 August 2025 (UTC)

@Pols12:

Solution No. 1.:

How about getting pagetranslation rights for a bot?

Solution No. 2.:

I see that the page is a bunch of mini-pages. So I would put the translation into Lua modules (the module would load the translation according to the wikis and have some constant UI for the languages).

The page would be for example: {{Page widget box|en|dog;cat;rabbit}}

The modules would be:

• Page widget box
• Page widget box – item (description pulls according to wikidata and language)
• Page widget box – UI translate

Dušan Kreheľ (talk) 13:15, 15 August 2025 (UTC)

Your solution 1 is not conceivable. That action needs a special right because it needs a human review given the risks of making something wrong and for performance reasons. Besides, my solution only needs 1 bot passage ever for each page; whereas your solution 1 would need a daily passage (each time ListeriaBot edits the page) which would be uselessly resource-consuming.

I don’t understand your solution 2. I agree several unit would benefit to be included through a template since they are common to many pages. They are already some templates for that purpose, including Template:Wiki Loves Living Heritage/Placeholders. In any case, we want the page to be localizable, and the best way is to use Translate extension features, mainly for Meta-Wiki consistency. In most cases, only the page title will be manually translatable (no unit on the page), but that would enable Languages bar to change the page language.

Also, I don’t understand why you seem to want to avoid the solution I proposed.

Unfortunately, I will probably not find any more time to work more on this in the coming weeks, sorry if I can’t follow your next answers here.

--Pols12 (talk) 23:47, 16 August 2025 (UTC)

@Pols12: I can help with this. Please let me know what the name of that subpage should be. For example, for Wiki Loves Living Heritage/Albanian iso-polyphony, should the list be at Wiki Loves Living Heritage/Albanian iso-polyphony/list? Also, can you confirm that the regex you provided are the ones you want to target? For instance, Wiki Loves Living Heritage/Albanian iso-polyphony has <!--BEGINREPLACE--> but does not have <!--ENDREPLACE-->, instead it has <!--Elementquery end-->. Although it has the backup regex {{Wikidata list}}, I just want to confirm because it may leave some instructions behind on the main page. – DreamRimmer ■ 11:28, 27 August 2025 (UTC)

Sorry to see this only now, I have not been actively following messages onwiki. I am very grateful for you looking into this, as I have been very excited about the possibility of creating such visual lists, but the biggest (but not only) hurdle is this – that the translations are switched off every time there is a minor change on the page.

I will need some more time to familiarize with what you have discussed, and I am inviting some more people to the discussion.

Thank you again! – Susanna Ånäs (Susannaanas) 🦜 07:26, 10 September 2025 (UTC)

Done Hopefully this has been resolved with Meta:Requests for bot status/DreamRimmer bot 2, but let me know if you would prefer the lists to be moved to separate subpages and I can take care of it. That said, since a bot will now mark these pages for translation daily, there should not really be any need to move them to subpages. – DreamRimmer ■ 14:00, 22 September 2025 (UTC)

This section was archived on a request by: – DreamRimmer ■ 14:00, 22 September 2025 (UTC)

MediaWiki:Globalrenamequeue-view does not support reject/accept reasons with line feeds

Tracked in Phabricator:
Task T405320

See for exmaple request #153819 (renamers only). The existence of line feeds in this request's reject notes caused the second paragraph to escape from the description list and created its own paragraph element. Example:

From

Example

To

Example-targetUsername

Reason

I just want to change it lol

Status

rejected

Requested

02:30, 20 August 2025

Completed

00:29, 26 August 2025

Done by

1F616EMO

Notes

Please carefully choose your new username.

Check w:en:WP:USERNAME for more details.
(This is a new paragraph, and you can see how it escapes from the description list and ruins aesthetics.)

Changes to MediaWiki:Globalrenamequeue-view may be needed to prevent this from happening. 1F616EMO (on zhwiki) 05:37, 27 August 2025 (UTC)

@1F616EMO: Given that the globalrenamequeue-view system message isn't overridden on meta-wiki, this seems like it should probably be reported as a software bug on Phabricator if you get a chance :) Best, ‍—‍a smart kitten_[meow] 12:46, 11 September 2025 (UTC)

@A smart kitten: Why do you think this system message is not being overridden? I tested it and it was overridden immediately. – DreamRimmer ■ 15:21, 22 September 2025 (UTC)

@DreamRimmer I feel like we might be inadvertently crossing wires -- I meant that, since the page MediaWiki:Globalrenamequeue-view had not been locally created on Meta-Wiki (and was therefore inheriting its default value from the CentralAuth extension), a bug with its implementation should probably be reported to Phabricator to be fixed within CentralAuth itself (rather than being fixed locally on Meta-Wiki). [Unless I'm misunderstanding you? Apologies if so!] Best, ‍—‍a smart kitten_[meow] 15:30, 22 September 2025 (UTC)

Ah, now I understand. I misunderstood you. – DreamRimmer ■ 15:39, 22 September 2025 (UTC)

This section was archived on a request by: — xaosflux ^Talk 15:59, 22 September 2025 (UTC)

Translatewiki interference

Hello folks, the Spanish-language translation of MediaWiki is currently broken. For example:

• The main tab of a category (such as Categoría:Uruguay says "noj ba'alo'ob" instead of "Categoría".
• The main tab of a help page (such as Ayuda:Contenidos says "ju'un ántaj" instead of "Ayuda".
• The main tab of a file page (such as Archivo:Argentina location map.svg says "Archivo'" instead of "Archivo".

It turns out that translations don't came from WMF or MediaWiki services, but from Translatewiki. In fact I can't even load that website...

Here's the current discussion at the Spanish-language Wikipedia.

Please, we need help. NaBUru38 (talk) 16:05, 31 August 2025 (UTC)

@NaBUru38: All three messages MediaWiki:Nstab-category/es, MediaWiki:Nstab-help/es and MediaWiki:Nstab-image/es were vandalised on translatewiki.net but have since been reverted to the correct version. These messages are normally updated automatically every day, but for some reason they were not localised even after being reverted on 26 August, which is why the eswiki still shows this version. You can create local versions at es:MediaWiki:Nstab-category, es:MediaWiki:Nstab-help and es:MediaWiki:Nstab-image to override the ones from translatewiki, giving you full control and allowing only trusted users to edit them. When you create them locally, you will see placeholders from translatewiki, so please replace them with your own version and save the page. – DreamRimmer ■ 16:46, 31 August 2025 (UTC)

@NaBUru38: Just a remark: those pages were probably not vandalised but rather mishandled during a translation campaign to the Mayan language; all of which created on August 22nd, day of said campaign. Anyway, we reverted most changes, some needed to be re-translated (new pages), although we would have liked most text to depend on the fall-back language, and I am also handling it on TW level. Cheers. Virum Mundi (talk) 17:03, 31 August 2025 (UTC)

This section was archived on a request by: – DreamRimmer ■ 16:49, 22 September 2025 (UTC)

Missing ⧼communitywishlist-support⧽

Missing message in ⧼⧼communitywishlist-support⧽⧽. Go to Community Wishlist/Focus areas/Media formats, editing, and display for example, scroll to blue button and push "Support focus area", the popup's main blue button that appears has this {{int:}} in it. Waddie96 (talk) 06:49, 17 August 2025 (UTC)

• Ping to @MusikAnimal (WMF): who I think is the staffer coordinating that. MA, looks like there are 2 problems:

1. Missing label at MediaWiki:communitywishlist-support as reported above.
2. This button loads a custom pop-out editor, which is missing licensing agreement verbiage (which should be, or be functionally similar to MediaWiki:wikimedia-copyrightwarning)

• Would you look in to both of these? Thank you, — xaosflux ^Talk 12:34, 17 August 2025 (UTC)

  The missing message is now fixed. Adding the copyright warning is a bit more involved, I'm afraid. We have a new MediaWiki extension that is going to replace the gadget version relatively soon, and we'll get the copyright warning added there.

  Thanks for letting us know about these issues! :) MusikAnimal (WMF) (talk) 19:22, 20 August 2025 (UTC)

  @MusikAnimal (WMF) Thanks! Waddie96 (talk) 23:28, 21 August 2025 (UTC)

There was also communityrequests-wishes-projects-header (because in the extension we've changed 'projects' into the more general 'tags'), which is now fixed in Special:Diff/29293077. SWilson (WMF) (talk) 10:54, 18 September 2025 (UTC)

Temporary accounts will be rolled out soon

Hello, we are the Wikimedia Foundation Product Safety and Integrity team. We would like to announce that we plan to enable temporary accounts for this wiki in the week of September 1.

Temporary accounts are successfully live on 30 wikis, including many large ones like German, Japanese, and French. The change they bring is especially relevant to logged-out editors, who this feature is designed to protect. But it is also relevant to community members like mentors, patrollers, and admins – anyone who reverts edits, blocks users, or otherwise interacts with logged-out editors as part of keeping the wikis safe and accurate.

Why we are building temporary accounts

Our wikis should be safer to edit by default for logged-out editors. Temporary accounts allow people to continue editing the wikis without creating an account, while avoiding publicly tying their edits to their IP address. We believe this is in the best interest of our logged-out editors, who make valuable contributions to the wikis and who may later create accounts and grow our community of editors, admins, and other roles. Even though the wikis do warn logged-out editors that their IP address will be associated with their edit, many people may not understand what an IP address is, or that it could be used to connect them to other information about them in ways they might not expect.

Additionally, our moderation software and tools rely too heavily on network origin (IP addresses) to identify users and patterns of activity, especially as IP addresses themselves are becoming less stable as identifiers. Temporary accounts allow for more precise interactions with logged-out editors, including more precise blocks, and can help limit how often we unintentionally end up blocking good-faith users who use the same IP addresses as bad-faith users.

How temporary accounts work

Any time a logged-out user publishes an edit on this wiki, a cookie will be set in this user's browser, and a temporary account tied with this cookie will be automatically created. This account's name will follow the pattern: ~2025-12345-67 (a tilde, current year, a number). On pages like Recent Changes or page history, this name will be displayed. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser. A record of the IP address used at the time of each edit will be stored for 90 days after the edit. However, only some logged-in users will be able to see it.

What does this mean for different groups of users?

For logged-out editors

• This increases privacy: currently, if you do not use a registered account to edit, then everybody can see the IP address for the edits you made, even after 90 days. That will no longer be possible on this wiki.
• If you use a temporary account to edit from different locations in the last 90 days (for example at home and at a coffee shop), the edit history and the IP addresses for all those locations will now be recorded together, for the same temporary account. Users who meet the relevant requirements will be able to view this data. If this creates any personal security concerns for you, please contact talktohumanrights at wikimedia.org for advice.

For community members interacting with logged-out editors

• A temporary account is uniquely linked to a device. In comparison, an IP address can be shared with different devices and people (for example, different people at school or at work might have the same IP address).
• Compared to the current situation, it will be safer to assume that a temporary user's talk page belongs to only one person, and messages left there will be read by them. As you can see in the screenshot, temporary account users will receive notifications. It will also be possible to thank them for their edits, ping them in discussions, and invite them to get more involved in the community.

For users who use IP address data to moderate and maintain the wiki

• For patrollers who track persistent abusers, investigate violations of policies, etc.: Users who meet the requirements will be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range (Special:IPContributions). They will also have access to useful information about the IP addresses thanks to the IP Info feature. Many other pieces of software have been built or adjusted to work with temporary accounts, including AbuseFilter, global blocks, Global User Contributions, and more. (For information for volunteer developers on how to update the code of your tools – see the last part of the message.)
• For admins blocking logged-out editors:
  • It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
  • It will still be possible to block an IP address or IP range.
• Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this.

Our requests for you, and next steps

• If you know of any tools, bots, gadgets etc. using data about IP addresses or being available for logged-out users, you may want to test if they work on testwiki or test2wiki. If you are a volunteer developer, read our documentation for developers, and in particular, the section on how your code might need to be updated.
• If you want to test the temporary account experience, for example just to check what it feels like, go to testwiki or test2wiki and edit without logging in.
• Tell us if you know of any difficulties that need to be addressed. We will try to help, and if we are not able, we will consider the available options.
• Look at our previous message about requirements for users without extended rights who may need access to IP addresses.

To learn more about the project, check out our FAQ – you will find many useful answers there. You may also look at the updates (we have just posted one) and subscribe to our new newsletter. If you'd like to talk to me (Szymon) off-wiki, you will find me on Discord and Telegram. Thank you!

NKohli (WMF), SGrabarczuk (WMF) 21:35, 26 August 2025 (UTC)

This looks like a solid step toward balancing privacy and moderation. I like that logged-out editors get more protection without losing accountability, and tools like IP Info still give patrollers what they need. Curious to see how the community adapts once it rolls out here. Michael Jobel (talk) 18:24, 20 September 2025 (UTC)