Meta:Administrators' noticeboard/Archive 4

__NOINDEX__

Request for Rollback (Universal Omega)
Hello, I know I have not done much counter-vandalism here on meta, although I do feel I should have rollbacker, so that if necessary I am able to quickly rollback the edits of vandals. I am active here on meta and quite frequently check the wiki requests, and already patrol many edits on meta, marking then as patrolled, so it makes sense for me to have rollback so that I can use it if needed. I can live without it by just going back and publishing the last good edit, but the rollback would provide a better record, and make it easier to do it. Thank you for the consideration! 15:20, 13 August 2020 (UTC) ］ |
 * I'm not opposed to this, but I personally haven't even requested it as Twinkle's pseudo-rollback via "undo" and "restore to revision" has served me well (though, there has been one, maybe two, instances where  might've helped, mainly relating to another user's refactoring of other users' comments). Dmehus (talk) 15:26, 13 August 2020 (UTC)
 * Thanks. I actually think I have twinkle off, thanks for reminding me. In that case I do suppose this request is somewhat unnecessary. Thanks! 15:33, 13 August 2020 (UTC) ］ |
 * I also would see no reason to oppose this, though I personally feel that there is very little vandalism on Meta currently and that as Dmehus said, Twinkle would probably work. Reception123 (talk) ( C ) 15:52, 13 August 2020 (UTC)
 * Thank you for reminding me about Twinkle, and while you may be right about there being very little vandalism on meta, I do not need Rollbacker with Twinkle existing. However, I do think I should mention that twinkle seems unreliable, and does not work on all my devices for some unknown reason. But for now I suppose I do not need Rollback. Thanks for the replies! 04:01, 14 August 2020 (UTC) ］ |
 * Although  is rarely needed due to the pseudo-rollback feature included within the Twinkle (which uses  ), you've articulated a clear purpose and use case (i.e., the Twinkle compatibility issue when mobile), and you are trusted, so I'm inclined to grant this request, provided that you only use   when on mobile for obvious vandalism or for reverting Discord/auth. So, ✅. Dmehus (talk) 18:59, 21 August 2020 (UTC)

Request for Patroller (Universal Omega)
Hello, I would like to request the patroller group. I was active patrolling edits in the past when it was the autopatrolled group and would like to continue that. Thanks! 16:05, 30 August 2020 (UTC) ］ |
 * On hold for a few days to a week while we finalize the guidelines. Generally, I'm hoping that all patrollers will add things like unsigned, including timestamps (adjusted back to UTC time, as applicable), to talk page and noticeboards without signatures and/or timestamps, but yes, you are among the first patrollers I would like to see onboarded. Dmehus (talk) 18:51, 30 August 2020 (UTC)
 * ✅. Please ensure you that you follow the main  guidelines that will follow on your user talk page. If you have any questions, please don't hesitate to ask. Dmehus (talk) 03:49, 31 August 2020 (UTC)

Request for Patroller (CircleyDoesExtracter)
Hi. I am CircleyDoesExtracter. I can nicely request the patroller right. I had experience adding unsigned signatures and patrolling edits. Since I supported the idea of the patroller group on Meta, I'd like to request it and continue with the autopatrolled right. Thanks! Circley Does Extracter    ( Circley Talk  |  Global   |  Email the Cloud ) 01:27, 31 August 2020 (UTC)
 * ✅. Please ensure you that you follow the main  guidelines that will follow on your user talk page. If you have any questions, please don't hesitate to ask. Dmehus (talk) 03:49, 31 August 2020 (UTC)

Request for patrollers (松・Matsu)
Hi,there.Since the Japanese character code is minor and often has garbled characters, I would like to go around editing written in Japanese and help meta.thanks.--松•Matsu (talk) 14:50, 30 August 2020 (UTC)
 * On hold for a few days to a week while we finalize the guidelines. Generally, I'm hoping that all patrollers will add things like unsigned, including timestamps (adjusted back to UTC time, as applicable), to talk page and noticeboards without signatures and/or timestamps, but yes, you are among the first patrollers I would like to see onboarded. Dmehus (talk) 18:51, 30 August 2020 (UTC)
 * ✅. Please ensure you that you follow the main  guidelines that will follow on your user talk page. If you have any questions, please don't hesitate to ask. Dmehus (talk) 03:49, 31 August 2020 (UTC)
 * Thank you.:)--松•Matsu (talk) 08:12, 31 August 2020 (UTC)

Request for Patroller (Bonnedav)
Hello, I am Bonnedav. I may not be around all the time but do pop up occasionally. I have done patrolling on Meta before and wish to continue to do so. Thus i wish to request the new  group for this reason. Thank you. Bonnedav (talk) 22:09, 31 August 2020 (UTC)
 * ✅; I was hoping you'd request this. Please ensure you that you follow the main  guidelines that will follow on your user talk page. If you have any questions, please don't hesitate to ask. Dmehus (talk) 22:32, 31 August 2020 (UTC)

Request for Patroller (Hypercane)
Hello, I would like to request the  user group as I believe it would be a great way for me to start helping out here on Meta. I'll look at any relevant guidelines you give me, thank you. Hypercane (  talk ) 00:28, 5 September 2020 (UTC)
 * ✅. Thanks for volunteering. Dmehus (talk) 00:29, 5 September 2020 (UTC)

Request for to be added to the   user group

 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
 * Consensus for. John (talk) 16:41, 12 September 2020 (UTC)

The following is a brief proposal for discussion, primarily, among administrators and interested Meta community members who follow this page to add the  user right to the   user group. Using the Special:MergeHistory special page,  is a user right that allows the revisions from one page to be moved, or merged, rather, into another page. It is primarily used for fixing things like improper cut and paste page moves, so in that way, is sometimes seen as a counter-vandalism tool. Nevertheless, it also secondarily used to history merge in the revisions from one older page into the revisions of a newer page, with the primary reason being for CreativeCommons copyright licensing compliance (see also this English Wikipedia guideline page for more on that). Commonly established guidelines on the English Wikipedia recommend that it be avoided where there are significant concerns with regard to parallel page histories.

Background: In somewhat of a curious anomaly, likely the result of a clerical oversight when Meta was established (since there are no merge log entries),  was never assigned to the   user group (see this special page in ManageWiki).

Rationale: I personally have a least a couple pages requiring history merging, mainly per attribution reasons and also for housekeeping reasons so redundant trailing redirects left behind by what would be the resulting merge can be safely deleted; however, and I have also been discussing the need to establish a Meta-only community discussion noticeboard (likely at Community portal, which, in turn, would see that historical page's revisions history merged into Community noticeboard/Archive 1 and made extant to the current revision on that archive page), to eliminate or reduce certain confusion if using Community noticeboard that would almost certainly be confused with community noticeboard, since he isn't keen on co-mingling Meta-only discussions with global or Miraheze community/customer discussions on community noticeboard, and, frankly, neither am I. We also briefly toyed around with my alternate idea of having a Bureaucrats' noticeboard, but seeing as bureaucrats on Meta only really grant interface administrator requests and close local RfCs (other than things like approving bots and closing administrator discussions at Requests for permissions), there's little need for them to have a separate noticeboard of their own, and, with   in the name, users may incorrectly perceive they aren't allowed to participate on that potential noticeboard. Now, if the community still preferred a Bureaucrats' noticeboard as an alternative to Community portal, we would certainly support that, but there is still such a potential use case for  that it should be added to the   user group.

Proposal: To add the  user right to the   user group.

Note: This proposal should remain open for at least seven (7) calendar days, but given how minor of a user right addition this is, it can likely be closed early (by a bureaucrat on Meta who also holds steward rights, for technical reasons) if at least five people, having valid arguments, have expressed a supportive view with overwhelming consensus of at least 80% or greater.

Proposed by: Dmehus (talk) 21:43, 5 September 2020 (UTC)

Support

 * 1)  As proposer. Dmehus (talk) 21:49, 5 September 2020 (UTC)
 * 2)  I do see how this could be useful for the administrators to have.  21:53, 5 September 2020 (UTC) ］ |
 * 3)  Might be useful for sysops.   Circley  Does Extracter    ( Circley Talk  |  Global   |  Email the Cloud )  22:52, 5 September 2020 (UTC)
 * 4)  Would be useful for Meta admins to have. Reception123 (talk) ( C ) 05:15, 6 September 2020 (UTC)
 * 5)  Can be useful for administrators HeartsDo (Talk || Global || Wiki Creator) 12:51, 6 September 2020 (UTC)

Discussion

 * The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Autopatrolled request
First, I moved accounts from Tom191 to this account, which the former is autopatrolled. Second, I know how to use meta, vote in requests, I sign my posts, and add unsigned for others too. AppleCrunchy (talk) 23:56, 14 September 2020 (UTC)
 * Are you able to sign in to your account and have it reply to this thread, confirming that Tom191 and AppleCrunchy are the same person? If you had created AppleCrunchy while signed in as Tom191, it would show up in the user creation log that Tom191 had created the user account AppleCrunchy. Nevertheless, once you've done this, this LGTM, and I'm inclined to approve. Thanks. Dmehus (talk) 00:40, 15 September 2020 (UTC)
 * Yes, I'm AppleCrunchy Tom191 (talk) 13:05, 15 September 2020 (UTC)
 * ✅. Thanks for confirming from your, which you can now shelve, if you wish. You may want to add a notice on Tom191's global user page that it is a retired/former account. On your global user page (or Meta user page), you may, optionally, wish to disclose your prior Tom191 account, but that part is up to you as well. Here's the diff link for your confirmation edit from Tom191 for AppleCrunchy. Dmehus (talk) 13:49, 15 September 2020 (UTC)

Special:MyLanguage and "tvar" tags on FAQ
Hi, Raltseye has left a message on my talk page for ask to "implement Special:MyLanguage in tvar tags on FAQ" but I can not do this because the page is sysop protected. If a admin can take care this task, it would be good :). HeartsDo (Talk || Global || Wiki Creator) 06:00, 13 September 2020 (UTC)
 * Hrm, this should already be enabled, as I have seen  used on pages on Meta, quite frequently in fact. Maybe  just means to update the source pages with this tag? If so, I'd recommend reaching out to either (a) any translation administrator (for non-administrator-protected pages) or (b) any administrator (for any administrator-protected pages). Hope this is of some assistance. Dmehus (talk) 15:04, 13 September 2020 (UTC)
 * Yes, that's what I meant with "implementing", as in putting the actual tags in the source code on the page itself. I appologize if I used the wrong wording. --Raltseye (talk) 22:29, 13 September 2020 (UTC)
 * I'm going to temporarily lower the page protection on that page temporarily, so you or can undertake this. When it is complete, please reply back to this thread, and we'll (a) re-protect the page and (b) re-mark the page for translation. How does that sound? Dmehus (talk) 01:08, 14 September 2020 (UTC)
 * Sounds good to me. --Raltseye (talk) 22:10, 14 September 2020 (UTC)
 * I think I'm done, I don't see anything more to do on FAQ., you're more than welcome to inspect of course. I also took care of some redirects and some dubble spaces that were scattered around.
 * Also, maybe Board should be translated, I don't know, maybe. --Raltseye (talk) 23:01, 14 September 2020 (UTC)
 * Thanks for letting me know that you seem to be done with updating FAQ. I'll leave the protection lowered for another day or so, in case you have anymore updates to do, then will mark it for translation. Regarding Board, since it's a global page, I checked Miraheze's board secretary, who had no issues with it being a translated page. So, I will take care of that now. Dmehus (talk) 23:14, 14 September 2020 (UTC)
 * Great, thanks! --Raltseye (talk) 23:20, 14 September 2020 (UTC)
 * Board is all ✅, and is ready to be translated now. Let me know if you would like to translate the two subpages of that page. Dmehus (talk) 23:30, 14 September 2020 (UTC)
 * Thanks! I'm not so sure about the other two sub pages but yeah, maybe if you think it's appropriate. Also, next time, don't forget to add the Special:MyLanguage only on pages that can be translated and not on the likes of talk and user pages, since those (typically) can't be translated and in tvar tags so they can easily be translated without having to write the whole link. --Raltseye (talk) 21:02, 15 September 2020 (UTC)
 * Thanks for the tip on the  tags. I'll definitely try and do that in the future, and it was chiefly from your sample code that I am now much more confident in using them! As to the Special:MyLanguage links, yeah, I guess that's probably true, but the thinking was that the subpages would likely be translated, so couldn't hurt. Anyway, I will mark those subpages now. Dmehus (talk) 21:13, 15 September 2020 (UTC)

That's great! Also, could you add tvar tags to the main page? --Raltseye (talk) 16:54, 16 September 2020 (UTC)

Merge User:FireBarrier101/signature into User:FireBarrier101/sig
I want to merge User:FireBarrier101/signature into User:FireBarrier101/sig on this revision. 17:48, 18 September 2020 (UTC)
 * ✅. Dmehus (talk) 18:15, 18 September 2020 (UTC)

The section of the translation page is broken
Since the section of the translation source page has been changed significantly, the section is broken on some translation pages.I propose to delete pages that are not modified.thanks.--松•Matsu (talk) 00:58, 3 October 2020 (UTC)
 * Yeah, this page was broken for the longest time until HeartsDo did excellent work repairing the broken translation. Is there a problem with specific sections, or just long outdated translated sections? Dmehus (talk) 01:34, 3 October 2020 (UTC)
 * 8th is especially.It has a big impact because it inserts the rejected extension in the global extension part.However, this may help translate rejected extensions.But, the translation of the rejected extension has been subdivided and may not be very useful.--松•Matsu (talk) 01:45, 3 October 2020 (UTC)
 * Hrm, at first I wondered if by "8th" if the issue was maybe HeartsDo had reused a translation unit ID number that had been used previously for another extension. Now, I am not so certain what you are meaning. Are you just saying you don't find the rejected extensions particularly useful, or you think we should change the order of the sections on the source page? Dmehus (talk) 01:56, 3 October 2020 (UTC)
 * Translations:Extensions/8/XX part.This is the explanation part of CentralAuth.It looks like we're inserting a list of rejected extensions into the CentralAuth description.This affects unmodified, translated pages.--松•Matsu (talk) 02:09, 3 October 2020 (UTC)
 * Ah, thanks for the helpful clarification. I will look into seeing if we can modify that translation unit somehow without having to invalidate it in some way. Separately, I have deleted seven (7) unmaintained translations (unmaintained since 2018 to early 2020), namely three variants of Chinese, Polish, Russian, Bangladesh, and Korean. All were approximately 1% (or less) translated, so that should help as well. Dmehus (talk) 03:29, 3 October 2020 (UTC)

Thank you for your confirmation and response:)--松•Matsu (talk) 03:53, 3 October 2020 (UTC)

Removal of the flags for Proxybot and Void-bot
Looking at the Meta contributions and log actions for Proxybot and contributions and log actions for Void-bot, it looks like the former has not made an edit or log action on Meta since March 2018 and the latter has not done the same since October 2018 (not counting a February 2019 OAuth consumer token update). I previously confirmed with, the bot operator of the former, that Proxybot is longer blocking open proxies, and I haven't yet spoken to , so am pinging him if he can confirm whether Void-bot is still operating on Meta or whether it just operates on other wikis (i.e., CVT and/or MirahezeBots wikis). So, I'm just wondering if any Meta bureaucrat could remove the  flag from these two bots on Meta, assuming there are no imminent plans for them to resume their functions? Thanks. Dmehus (talk) 17:31, 8 October 2020 (UTC)
 * I believe when we get the proxy stuff going again we'll be using the MirahezeBots account. ~ RhinosF1 - (chat)· acc· c -  15:50, 12 October 2020 (UTC)
 * Void-bot could probably lose the sysop flag right now, but still actively uses the bot login. I can't recall the source code off the top of my head, but I think it might not function properly if the bot flag is removed from the account. I intend to continue working on it, but recently many things have gotten in the way. -- Void  Whispers 23:23, 12 October 2020 (UTC)
 * I've removed the sysop flag from Void-bot and the bot flag from Proxybot per above. If these are needed again in the future, they can be re-requested naturally. Reception123 (talk) ( C ) 17:54, 13 October 2020 (UTC)

Please block 2600:1700:50D0:ECC0:351F:B9E0:6C70:8A21
Vandalism. Gomdoli4696 (talk) 04:57, 13 October 2020 (UTC)
 * Special:Contribs/2600:1700:50D0:ECC0:351F:B9E0:6C70:8A21
 * , with a Cc: to, ✅ for one month, preventing logged in users from that IP address from editing on Meta for the duration and also from accounts being created at that IP address. As well, should the IP user change IPs, I've temporarily ✅ community noticeboard for two weeks to logged in, registered users. Thank you for your report, and to you both for your reversions. Dmehus (talk) 05:18, 13 October 2020 (UTC)
 * and hard blocked as they moved to their talk page. ~ RhinosF1 - (chat)· acc· c -  08:00, 13 October 2020 (UTC)

Moving a wiki to Miraheze is up for translation?
I recently got around to polish the page Moving a wiki to Miraheze for translation, is this something that we can mark for translation, or is there something more to do? And if so, how do one group it with other pages in the same category in Special:LanguageStats? Is that done by categories or do one have to manually do that in some special page? --Raltseye (talk) 16:10, 23 October 2020 (UTC)
 * Yeah, that page can be marked, but I would check with first as they were working on that, mainly related to its translation units. Otherwise, I have no issues with it. To your latter question, I believe that's where the "aggregate groups" comes in in that you have to aggregate the page with a similar established translation group (i.e., probably "documentation"). Dmehus (talk) 16:23, 23 October 2020 (UTC)
 * For explain rapidly the problem, this page was already marked as translation but just removed on the translation wihout removing old units.
 * I have maybe a idea, but I not sure there will work. I will mark the page for translation and see if Fuzzybot do somethings. If it doing nothing, I will try to manual edit the old units (if possible) and create the new one and see if it modify the main page.
 * In other word, don't touch the page and I will say if a success or fail HeartsDo (Talk || Global || Wiki Creator) 16:37, 23 October 2020 (UTC)
 * OK, never trust on the green box, Fuzzybot is doing his job, this request is ✅ HeartsDo (Talk || Global || Wiki Creator) 16:44, 23 October 2020 (UTC)

Archiving
Not sure if this is a great idea, but maybe add the autoarchive to this page since some things are literally 5 years old.

For your consideration. 20:27, 29 October 2020 (UTC)
 * Thank you for your good-faith suggestion. Community portal is the former community noticeboard, and, incidentally, I didn't realize that page's sysop protection had expired. This has now been corrected. We're currently developing plans to repurpose that noticeboard into a Meta-only community discussion portal, but what do with its archives is challenging. So, in the interim, it is sysop protected. Hope that helps. Dmehus (talk) 00:43, 30 October 2020 (UTC)
 * It does. Thanks! 00:44, 30 October 2020 (UTC)
 * Okay, great, and no problem. Thanks. Dmehus (talk) 00:49, 30 October 2020 (UTC)

Does Miraheze need translate rules?
Lots of English words are polysememes. And in other languages, they also have lots of different expression.

For example, "Miraheze" in Chinese can be "Miraheze", "米拉和泽" (transliteration), "菏泽的米拉铜合金" (literally) and so on.

I think Miraheze needs translate rules what has the translation of special words on gauge to make translations standard.

--开炸弹车 (talk) 03:26, 1 November 2020 (UTC)

Special:GlobalRenameRequest
I recently made a request to change my name on Miraheze the for why is entailed in the request, anyway, the message on said Special page shows this message:


 * Begäran om globalt namnbyte av användarkonto


 * Begär ett nytt användarnamn som kommer att används på alla projekt.


 * Alla dina tidigare bidrag kommer att knytas till detta nya användarnamn.


 * När du har begärt ett nytt användarnamn, kommer en anmälan att skickas till Wikimedias stewarder för utföra ett namnbyte. Du kommer att meddelas via email när denna process är klar.


 * Om din förfrågan är relaterad till en önskan om anonymitet/integritet, var vänlig notera att en permanent loggpost kommer att skapas med notering av ditt tidigare namn. Du kanske bör överväga att skapa ett nytt separat och oberoende konto och byta namn på ditt nuvarande konto till något slumpmässigt och sedan överge det.


 * Nuvarande användarnamn:
 * Raltseye

Now, correct me if I'm wrong but shouldn't it say Miraheze and not MediaWiki? Or is the system sending back a global name change request to MediaWiki? Isn't that handled locally? In which case it should be Miraheze. Or am I missing something here, could it a problem with localisation? --Raltseye (talk) 23:36, 31 October 2020 (UTC)
 * Seems to be an error in translation, as all renames are handled by Miraheze Stewards. Zppix (Meta &#124; CVT Member &#124; talk to me) 01:05, 1 November 2020 (UTC)
 * I assume it has to do with this unit on translatewiki. Alright, I seen to have fixed it. This thread was unnecessary.. --Raltseye (talk) 02:48, 1 November 2020 (UTC)
 * Thanks anyway. — Preceding unsigned comment added by Raltseye (talk • contribs) 02:52, 31 October 2020 (UTC)
 * I was just going to suggest that this should be translated through translatewiki.net. It sounds like you found the correct interface message to translate. We have a bot on GitHub that automatically imports translatewiki.net translations on a regular basis. would probably know the frequency by which the translations are imported into our GitHub repository. Hope that helps. Dmehus (talk) 03:28, 1 November 2020 (UTC)
 * I am not sure how often this happens as the bot nor translatewiki is controlled by us AFAIK. Zppix (Meta &#124; CVT Member &#124; talk to me) 05:21, 1 November 2020 (UTC)
 * I fixed the translation anyway. --Raltseye (talk) 13:38, 1 November 2020 (UTC)

Please can you delete my userpage at Meta
Please may you delete this page here: https://meta.miraheze.org/wiki/User:TheBurningPrincess as I wish to change my name (at some point), and for that page to show up as deleted on Google TheBurningPrincess (talk) 21:50, 1 November 2020 (UTC)
 * ✅. Please note, though, for Meta-only requests, you should either (a) use Administrators' noticeboard or (b) add admin help in a new section on your user talk page. Dmehus (talk) 22:07, 1 November 2020 (UTC)
 * Should you wish to reply to this thread, please note that I have moved it from stewards' noticeboard to Administrators' noticeboard, where it is now in scope. Dmehus (talk) 22:15, 1 November 2020 (UTC)

MediaWiki:Common.css
.infobox { border: 1px solid #a2a9b1; border-spacing: 3px; background-color: #f8f9fa; color: black; /* @noflip */ margin: 0.5em 0 0.5em 1em; padding: 0.2em; /* @noflip */ float: right; /* @noflip */ clear: right; font-size: 88%; line-height: 1.5em; width: 25em; } .infobox caption { font-size: 125%; font-weight: bold; padding: 0.2em; text-align: center; } .infobox td, .infobox th { vertical-align: top; /* @noflip */ text-align: left; }

.infobox th { white-space: nowrap; }

.infobox.bordered { border-collapse: collapse; } .infobox.bordered td, .infobox.bordered th { border: 1px solid #a2a9b1; } .infobox.bordered .borderless td, .infobox.bordered .borderless th { border: 0; }

.infobox.sisterproject { width: 20em; font-size: 90%; }

.infobox.standard-talk { border: 1px solid #c0c090; background-color: #f8eaba; } .infobox.standard-talk.bordered td, .infobox.standard-talk.bordered th { border: 1px solid #c0c090; }

/* styles for bordered infobox with merged rows */ .infobox.bordered .mergedtoprow td, .infobox.bordered .mergedtoprow th { border: 0; border-top: 1px solid #a2a9b1; /* @noflip */ border-right: 1px solid #a2a9b1; }

.infobox.bordered .mergedrow td, .infobox.bordered .mergedrow th { border: 0; /* @noflip */ border-right: 1px solid #a2a9b1; }

/* Styles for geography infoboxes, eg countries, country subdivisions, cities, etc.           */ .infobox.geography { border-collapse: collapse; line-height: 1.2em; font-size: 90%; }

.infobox.geography td, .infobox.geography th { border-top: 1px solid #a2a9b1; padding: 0.4em 0.6em 0.4em 0.6em; } .infobox.geography .mergedtoprow td, .infobox.geography .mergedtoprow th { border-top: 1px solid #a2a9b1; padding: 0.4em 0.6em 0.2em 0.6em; }

.infobox.geography .mergedrow td, .infobox.geography .mergedrow th { border: 0; padding: 0 0.6em 0.2em 0.6em; }

.infobox.geography .mergedbottomrow td, .infobox.geography .mergedbottomrow th { border-top: 0; border-bottom: 1px solid #a2a9b1; padding: 0 0.6em 0.4em 0.6em; }

.infobox.geography .maptable td, .infobox.geography .maptable th { border: 0; padding: 0; } (from Korean Wikipedia) This is infobox class. can add MediaWiki:Common.css? Gomdoli (talk) 12:21, 28 October 2020 (UTC)
 * It's not clear to me how adding this to Meta's common.css file would be helpful. As far as I'm aware, that file only controls Meta, and has no impacts on other wikis. So, essentially, you would need to suggest to every wiki to update their common.css files where they use that infobox. Hope that helps. Dmehus (talk) 12:47, 28 October 2020 (UTC)
 * Yes, I'm only talking about metawiki. ※Infobox -- Gomdoli (talk) 12:51, 28 October 2020 (UTC)
 * -- Gomdoli (talk) 12:53, 28 October 2020 (UTC)
 * Okay, thanks. It's still not clear to me, though, what these CSS classes would solve? What would they change? Also, if you forget to ping someone, you can still go back into your message and insert a ping since no one has replied. You can optionally update the timestamp of your signature. There's no need to start a new paragraph and sign again just for the ping. I mean, it's fine the way you did it, but just letting you know another way that is perfectly acceptable. Dmehus (talk) 12:58, 28 October 2020 (UTC)
 * They define infobox's style; We can use class, then load styles. --Gomdoli (talk) 13:20, 28 October 2020 (UTC)
 * and, you said, I edited that's because pings won't be sent. Wikipedia:ko:Template:Ping -- Gomdoli (talk) 13:22, 28 October 2020 (UTC)
 * There's infobox template. Yes. But what does this CSS class do? What value does it add to the template? Why should everyone loading Meta get these chunks of code? No, "because there's a template, there should be this CSS code" does NOT count. &mdash; revi  14:11, 28 October 2020 (UTC)
 * ❌ as no real need. Dmehus (talk) 17:53, 10 November 2020 (UTC)

Double tags
The training module Training modules/Dealing with online harassment/slides/on-wiki-steps-they-can-take feature double tags. I don't have the permission to edit the page (even though the edit button says I can), so if anyone with said permission could remove one of them, that'd be nice. --Sabelöga (talk) 13:43, 10 November 2020 (UTC)


 * ✅, but that page wasn't protected, so I'm not sure why you weren't able to remove it. Dmehus (talk) 14:47, 10 November 2020 (UTC)
 * Strange, it works now :/ Thanks anyway :) --Sabelöga (talk) 15:19, 10 November 2020 (UTC)
 * Yeah, strange. Oh well, it works now. Anyway, I noticed that you added the  tag around the   tag in this edit. It's been my experience that the   and   tags are impervious to the   tag. So, while that edit is harmless, it's also useless. Not a big deal, and I wouldn't bother correcting it, but just a point for the future. Dmehus (talk) 15:49, 10 November 2020 (UTC)
 * Well, if you mean that the  tags are automatically treated as   I think you're misinformed, because the only reason I noticed that it was doubled and thought it was a problem is because it was transcluded on Training modules/Online harassment due to the missing  . Since I removed them they aren't transcluded on that page just like the other ones. --Sabelöga (talk) 17:14, 10 November 2020 (UTC)
 * Well, hrm, that's possible, I guess, but I have noticed that when transcluding translated pages, the  tag seemed to ignore the   tag. To be honest, though, I'm not sure why we've even prepared the training modules for translation, as they're not used by community members. They're used exclusively by system administrators in the course of dealing with Terms of Use enforcement (mainly serious online harassment). We have several administrators that speak languages other than English, but all are fluent in English, so there's not really a massive need to be translating these pages. What are your thoughts to potentially deleting the translated subpages (and translation units) for the training modules, and moving these pages from main namespace to Tech: namespace? This would certainly reduce the workload for translators. Dmehus (talk) 17:24, 10 November 2020 (UTC)
 * I'm all for that, as it would take a very long time to translate them and wouldn't really be that worth it, plus it might distract translators into translating those when they're aren't really the most needed, or not needed at all. I would never for instance translate them as it's too much work and hassle, and even if I were to do it, it would take like a week or so. So deleting them from the translation system seems fair. --Sabelöga (talk) 17:30, 10 November 2020 (UTC)
 * Oh, great. I was worried you'd already put a lot of work into translating those modules. I'll try and tackle this project in the next week or so. Dmehus (talk) 17:38, 10 November 2020 (UTC)
 * Excellent, no only Spanish had been translated, partially. --Sabelöga (talk) 17:48, 10 November 2020 (UTC)

Request for for Naleksuh
Following my discussion on IRC with Naleksuh regarding Twinkle no longer functioning following Miraheze's upgrade to MediaWiki version 1.35, and because we no longer have an active Twinkle maintainer to continue the de-Wikipedia-ification started by Amanda Catherine, he has accepted my invitation to join the Meta team as an. Additionally, he has a separate application in to volunteer as a Miraheze MediaWiki extension security reviewer, given his php coding expertise. I have no doubt he will also be keen to install useful gadgets on Meta.

With that, I will now turn it over to Naleksuh to provide the necessary acceptance of this nomination and any bureaucrat can see fit to close this discretionary appointment request when their time permits. Thanks. Dmehus (talk) 03:04, 12 November 2020 (UTC)
 * Thank you for the request. I accept the nomination. Naleksuh (talk) 03:08, 12 November 2020 (UTC)
 * My password is set to take over 500 quadrillion years to crack and is not used anywhere other than Miraheze. Naleksuh (talk) 03:10, 12 November 2020 (UTC)
 * ✅ Reception123 (talk) ( C ) 06:10, 12 November 2020 (UTC)

Request for Marking Discord/Ops for Translation
Hello, could a translation administrator (or administrator) please mark Discord/Ops for translation? Thank you very much. R4356th (talk) 11:38, 13 November 2020 (UTC)


 * HeartsDo (Talk || Global || Wiki Creator) 11:47, 13 November 2020 (UTC)
 * ✅ HeartsDo (Talk || Global || Wiki Creator) 11:50, 13 November 2020 (UTC)
 * Thank you very much, . R4356th (talk) 12:11, 13 November 2020 (UTC)

Request for interface messages MediaWiki:nstab-tech and MediaWiki:nstab-tech/ja
Request...create this pages:

MediaWiki:nstab-tech:Tech

MediaWiki:nstab-tech/ja:ワザ

--Waki285 (talk) 00:33, 12 November 2020 (UTC)


 * Firstly, please note that I have procedurally moved this discussion and question from MediaWiki talk:Nstab-tech for a couple reasons. One, that is an orphaned talk page. Two, since talk pages aren't monitored regularly, the noticeboards are where most discussions should occur. Secondly, I'm not familiar with these interface messages. What would be the purpose of these? Dmehus (talk) 00:40, 12 November 2020 (UTC)
 * After looking into this a bit further, I realized that the Tech: namespace already displays "Tech" in the subject page's tab name, so I'm going to say that MediaWiki:nstab-tech is ❌. Regarding MediaWiki:nstab-tech/ja, that can be done. Normally, interface message translations are done through translatewiki.net; however, in this case, it does seem to make sense to translate this locally. When I double-checked the translation of ワザ using Google Translate, it returned "Waza". So, I am going to reach out to (Pine/Matsu), a Meta patroller, to confirm that this is the correct Japanese translation for the English word "Tech"., can you confirm and/or comment? Dmehus (talk) 01:20, 12 November 2020 (UTC)
 * It can also be translated as technical information.--松•Matsu (talk) 05:58, 18 November 2020 (UTC)
 * Okay, thank you. What do you think would be the best Japanese character to use for  to appear in the page name for Tech: namespace? Dmehus (talk) 06:14, 18 November 2020 (UTC)

Request for Marking Discord/Verification/Intro for Translation
Hello, could a translation administrator (or administrator) please mark Discord/Verification/Intro for translation? Thank you very much.(The text is the same as the previous person, but I'm sorry.) --Waki285 (talk) 05:42, 17 November 2020 (UTC)
 * Okay, but then why not just put the text on Discord/Verification anyway? The way it is now, people can't read the translated pages from the first page. Then what's the point of that page? --Sabelöga (talk) 14:25, 17 November 2020 (UTC)
 * ✅ I did not notice the Discord/Verification page before., I think that page's content could be replaced with a redirect to Discord/Verification/Intro. R4356th (talk) 14:30, 17 November 2020 (UTC)
 * Okay, but why then not move Discord/Verification/Intro to Discord/Verification? --Sabelöga (talk) 14:39, 17 November 2020 (UTC)
 * Yes, that could be done, too. But it is worth noting that the page cannot be translated while the move is in progress. R4356th (talk) 15:11, 17 November 2020 (UTC)
 * Well, no-one has started any translation, yet have they? --Sabelöga (talk) 15:25, 17 November 2020 (UTC)
 * Nope, I was just saying that no one can translate while this is being moved. So, yeah, it looks like there is no harm in moving it now. R4356th (talk) 15:28, 17 November 2020 (UTC)
 * I've had a look at both pages and, because Discord/Verification is  protected, moving Discord/Verification/Intro isn't possible. Since the former is a duplication of the latter, what I will do is remove the protection on the former, and either (a) delete the former and move the latter to the deleted former's title (if the latter is an older page than the former page) or (b) delete the latter and remove it from the translate system, allowing any translation administrator to prepare the former page for translation. Dmehus (talk) 16:03, 17 November 2020 (UTC)
 * This is ✅. Discord/Verification can now be translated as it is no longer transcluding Discord/Verification/Intro. Dmehus (talk) 16:24, 17 November 2020 (UTC)
 * Great. Thank you very much. R4356th (talk) 16:28, 17 November 2020 (UTC)

Requesting edit on General disclaimer
Specifically, I request that Special:MyLanguage is added to all the present links and that Terms of Use and Privacy Policy is moved from the tvar tags so that the link text can be translated. Like so:. --Sabelöga (talk) 00:16, 21 November 2020 (UTC)


 * I'm willing to add this as it does seem like a reasonable and helpful request; however, I meant to follow up with you on my user talk page that I had to remove the Special:MyLanguage prefix from MediaWiki:Mainpage due to an upstream MediaWiki bug that prevented administrators from being able to change the visibility of log entries in Special:Log. So, that prior request you made won't be actionable, unfortunately. However, this seems reasonable, as it isn't changing anything within MediaWiki: namespace. Dmehus (talk) 00:29, 21 November 2020 (UTC)
 * ✅ Dmehus (talk) 00:36, 21 November 2020 (UTC)
 * Thank you, and to comment on the previous request I made, I understand that it didn't work the way I intend it to so that it was reverted is maybe not a big deal, but being able to direct users to a translated version of the main page is still desirable so maybe if it's possible any other way I guess. Also, maybe that page should have some a categories? --Sabelöga (talk) 00:45, 21 November 2020 (UTC)
 * Thanks for understanding. Yeah, I'll try and think of an alternate method of redirecting users to the translated Main Page. As far as adding categories to the Main Page, that's certainly possible, but I'd have to check with Reception123 and see if it's desirable, but will definitely do that and get back to you. Dmehus (talk) 00:57, 21 November 2020 (UTC)
 * Okay, I was also thinking of General disclaimer which doesn't have any categories, the Main page could just have Category:Miraheze if that isn't undesired. --Sabelöga (talk) 01:24, 21 November 2020 (UTC)

Possible new template I've been developing on the test wiki
Possible new template I've been developing on the test wiki to be used on Administrators and other similar lists. Basically, it creates a translatable template that gets transcluded on the lists that in turn gets translated onto the main articles. See User:Sabelöga/Sandlåda for details on how the acutal template looks and works in action. (Also, why don't the testwiki have its own interwiki prefix :/) --Sabelöga (talk) 12:35, 21 November 2020 (UTC)


 * Technically and aesthetically, this looks fine, and I'm not opposed to it, but I have to think about this some more as I was actually planning on using the  as cross-wiki transcluded lists, incorporated into local wikis' lists of users (i.e., for local and global interwiki administrators). Due to an upstream bug with the Translate extension's   and   tags ignoring the   tag when used with scary transclusion, this would pose problems with transclusion. So, let me think about this some more, and I'll try and get back to you on this in the next month or two. Dmehus (talk) 15:21, 21 November 2020 (UTC)
 * Okay. --Sabelöga (talk) 16:46, 21 November 2020 (UTC)

Translatewiki
I was translating mwgithub-mirahezemagic-custom on translatewiki and saw a problem with one of the translate units. Is there somewhere were I can discuss this further with someone? Specifically there is a lot of wikimarkup in a translate unit that is really unnecessary for translators to copy and steals time. --Sabelöga (talk) 01:28, 21 November 2020 (UTC)


 * What do you mean by unnecessary wiki markup? Most of our MirahezeMagic interface messages are contained within this json file, so any changes to the source messages can be requested in that way, which are then, in turn, update on translatewiki.net for translators to update. The translations are then piped back to Miraheze's GitHub repository every Monday. Dmehus (talk) 02:07, 21 November 2020 (UTC)
 * I speak specifically about translatewiki:MediaWiki:Mirahezemagic-custom-miraheze-warnmessage in which I don't think that the wikimarkup should be contained withing the translation unit. I mean, can't it be contained outside it? Minimalising the required copy-pasting from the translators and standardising the way the notice looks. The way it is now, I could have changed how it works and if one were to in the future update the source code for the notice one would have to update the translations as well. --Sabelöga (talk) 10:24, 21 November 2020 (UTC)
 * The linked Miraheze warning message doesn't exist on translatewiki.net. Did you possibly mean a different message? Dmehus (talk) 15:16, 21 November 2020 (UTC)
 * Darn it, I mean this one https://translatewiki.net/w/i.php?title=Special:Translate&showMessage=mirahezemagic-custom-miraheze-warnmessage&group=mwgithub-mirahezemagic-custom&language=sv&filter=&optional=1&action=translate --Sabelöga (talk) 16:46, 21 November 2020 (UTC)
 * Any developments? Sabelöga (talk) 01:06, 23 November 2020 (UTC)
 * Thank you for the reminder. Yes, in fact. The good news is that particular MirahezeMagic interface message is an old interface message, so it no longer needs to be translated. The bad news is that we changed the method by which sitenotices are applied to wikis (used to be done by a bot; now it's done automatically by a maintenance script on a cron) and, as a result, those sitenotices can't currently be translated. I did some checking with Nikerabbit in the channel on IRC and, unfortunately, when the source interface message is deleted, the messages on translatewiki.net aren't deleted. Nikerabbit did say that the messages should no longer be sorted into the appropriate message group. So, if for some reason they are, then there could be another issue that will have to be tracked down. Hope that helps. Dmehus (talk) 03:49, 23 November 2020 (UTC)
 * Okay, so the message is unfortunately no longer supported nor translatable. I understand. --Sabelöga (talk) 07:02, 23 November 2020 (UTC)
 * Well, sort of. That message is no longer used, but translatewiki.net doesn't delete outdated messages. The current message is at this page in our GitHub repository, which you can see doesn't offer a way to translate it currently. We'll try and investigate a way to translate it, whether on-wiki or on GitHub, though, but no timeframe for when this will be done. Dmehus (talk) 14:15, 23 November 2020 (UTC)
 * I understand. Sabelöga (talk) 14:54, 23 November 2020 (UTC)

Translate Template:Translated
I'm thinking of marking Template:Translated for translation. Do you think this is a good idea? Also, if I were to do it, I can include the English version in the translated version if the point of the template is to point users to the bottom of the page even if they don't speak the local language. I'm thinking it's beneficial to display the information in both languages. Sabelöga (talk) 01:05, 23 November 2020 (UTC)
 * While this might be a good idea, for several reasons, I'd like to postpone preparing this for several reasons. For one thing, I have to look into how the transclusion of translated templates works, which may also add complexity to our translation pages. Keep in mind we have a limited number of translation volunteers, and, while I can see the benefit to translating these templates into languages other than English, our community is nowhere near as large or as active as the Wikimedia translation community. At the same time, we already have a fair number of content, documentation, and policy pages which need translating, translation reviewing, and updating. Finally, I do not want to overburden the  servers too much with an even greater number of pages (now templates) that will require translating. So, I'd really prefer to see us focus on translating content in Main, Meta, and Category namespaces for the time being. Hope that helps. Dmehus (talk) 01:15, 23 November 2020 (UTC)
 * That's fine, it's not that urgent so if things need to be prepared then take your time. Though when it comes to transclusions I believe we can just use Template:TNT which uses the translated version of a template (or other transcludable page) if it exists or the source template (page). Basically I've noticed it actually transcludes {pagename} /en which solves the problem of including translate tags. See how Template:Global policy is used on Dormancy Policy for instance. --Sabelöga (talk) 01:29, 23 November 2020 (UTC)
 * Okay, thanks. Yeah, I will try and look into it over the next month or so, and hopefully we can prepare it for translation. Dmehus (talk) 03:43, 23 November 2020 (UTC)
 * Okay. --Sabelöga (talk) 07:35, 23 November 2020 (UTC)
 * Note that we do use translatable templates on most of the policy pages. (Using Template:TNT) MacFan4000 (Talk Contribs) 15:16, 23 November 2020 (UTC)
 * Exactly my point, so I don't see any issues wth this either. Sabelöga (talk) 15:22, 23 November 2020 (UTC)

TOC right on Tech:Server admin log
For the sake of reading the page I think that Tech:Server admin log should make use of. I tried to add it but there was a message that said only system administrators should edit the page which makes sense since it's updated by a bot. Now, I don't know how that page is used or by who, but the way it is now that one have to scroll through an enormous amount of TOC to get to the first entry is ridiculous, if the page is never read by humans this should not pose a problem though, but then again why host it here? --Sabelöga (talk) 07:38, 23 November 2020 (UTC)
 * Reasonable suggestion. ✅. Dmehus (talk) 14:08, 23 November 2020 (UTC)
 * Thanks! I only hope this won't create any troubles with the bot when it's due to update the list next. --Sabelöga (talk) 14:54, 23 November 2020 (UTC)
 * It shouldn't. Bot adds only a new log entry to the row immediately above the previous row, adding a new section header when the calendar rolls into a new month. Dmehus (talk) 14:57, 23 November 2020 (UTC)
 * Excellent! Sabelöga (talk) 15:01, 23 November 2020 (UTC)

Creating a Policy for Marking Pages for Translation
Looking through the recent changes and talk pages, I think we should have an official policy for marking pages for translation on Meta to avoid any kind of possible confusion. A template for informing users that their edit was unhelpful to translators (usually because they either reverted an edit adding s or edited something inside a tvar and did not check the "Do not invalidate translations" option while marking the page for translation) could be helpful, too. Does anybody have any opinion on this? (I am putting this here instead of CN because I believe this needs admins' attention.) R4356th (talk) 15:49, 23 November 2020 (UTC)
 * This is indeed the correct noticeboard to use for now, as it concerns a Meta specific issue/proposal. While I do agree a policy, or perhaps a guideline adopted by administrators rather than a community adopted policy, could be helpful for translations, we do have a number of more pressing things to get to at the moment, so this probably will not be done for at least a month or two. In the meantime, we do have these translation administrator guidelines that are fairly comprehensive, particularly when you add together this advice which all translation administrators should follow. Moreover, I think most of the pages that need to be prepared for translation have been, so we really just need to focus on updating those pages. Let me know if that helps, and clears that up. Dmehus (talk) 16:13, 23 November 2020 (UTC)
 * Yes, sure but that template is barely read by non-translationadmins. And it does not mention the part about not marking translations as outdated. R4356th (talk) 16:24, 23 November 2020 (UTC)
 * Perhaps a better solution could be to take the elements from the template Dmehus mentions and to make them into a separate guideline page that non-translation administrators could read or easily be linked to (however, they could always be linked to the template too if necessary). I don't think that a policy, per se is needed, simply clear non-controversial guidelines that all users can and should follow. Reception123 (talk) ( C ) 16:27, 23 November 2020 (UTC)
 * (and Cc: to ) Also, another reason why I'm not sure a formal policy is needed is that I rather like the practice of invalidating translations as then the outdated translations are marked in red. The old translations are still there, and just need to be copied, pasted, and updated. Perhaps we could do well to advise administrators and translation administrators not to invalidate translations for minor things like updating the  tags, but I think we can probably just keep doing this with gentle reminders as we see them. Dmehus (talk) 16:32, 23 November 2020 (UTC)
 * +1 for Reception123 idea HeartsDo (Talk || Global || Wiki Creator) 16:32, 23 November 2020 (UTC)
 * While I'm not opposed to the above idea, as indeed I was the one that first floated the idea of a possible guideline page, I don't see an immediate need to create it, simply because our current practice of gentle reminders is working well, and non-translation administrators cannot mark pages for translation. Dmehus (talk) 16:34, 23 November 2020 (UTC)
 * To be honest, I am suggesting creating a policy mostly just so that reminders do not need to be sent. I am not really a fan of the ones that are currently being sent. And +1 for Reception123's idea, from me, too. Additionally, I would like to note that I am not saying it should be done immediately as well. R4356th (talk) 18:24, 23 November 2020 (UTC)
 * Okay, I'll try and work on a guideline page in the next month or so. I do think we should not make it mandatory, though, to check the "do not invalidate translations" box, though, as that does have its uses (i.e., it lets translators know which sections need to be updated). That being said, perhaps for the time being could ease up on the reminders being sent? Dmehus (talk) 18:33, 23 November 2020 (UTC)
 * Yes, I agree that it should not be made mandatory since well, as you say, it is useful in several cases. But its use should be encouraged whenever possible, in my opinion, as it is very helpful for translators. When I started working on updating most of the existing Bengali translations, I found that many of them did not really need to be updated since the updates to the English version were minor wording or spelling issue fixes which were already corrected in the translation and had to make null edits to mark them as updated. R4356th (talk) 18:49, 23 November 2020 (UTC)
 * Yes, I was reckless on the second one I sent as I didn't realize my advice was being followed. I'm sorry for that one and have apologized to the person the unnecessary message was sent to. But I agree that marking the box "Do not invalidate translations" is useful, sometimes, and it would be beneficial to stake out where it is somewhere so that we can direct people there if there's any uncertainties. Sabelöga (talk) 23:00, 23 November 2020 (UTC)

Edit request on Administrators
Could someone lower the protection level on Administrators or copy the edit from Special:Diff/146477 there? Don't forget to update the Administrators/List with Special:Diff/146476. --Sabelöga (talk) 01:13, 25 November 2020 (UTC)
 * EDIT: The same request on System administrators, System administrators, and Stewards. --Sabelöga (talk) 01:22, 25 November 2020 (UTC)
 * I did notice your inclusion of  tags around the headers of the   subpages, and half expected to have to come here to say ❌, as I noted a little further up on this noticeboard that these   subpages are designed to be easily transcluded onto other wikis. However, in my testing, purging the page several times to be sure, it seems that there were no issues, so I am going to mark this is ✅. It should be done shortly, with the obvious proviso that should unexpected issues crop up with scary transclusion, it will have to be undone. Dmehus (talk) 01:37, 25 November 2020 (UTC)
 * Well, the thing here is that you have to provide your own header which then in turn can be translatable, that has to be present or else it will look like this when transcluded: . --Sabelöga (talk) 01:42, 25 November 2020 (UTC)
 * Can you clarify what you mean by this just a bit? When I looked at my test revision on TestWiki, I saw a properly formatted table with scary transclusion. When I saw your example, locally transcluded, which I've wrapped in  tags for readability, it was not properly formatted. The transclusion would probably be a bit different with scary transclusion, but I just want to confirm that you also see a properly formatted formatted table on TestWiki. Thanks. 01:51, 25 November 2020 (UTC)
 * Well, yes, the table you showed me in Test Wiki works fine. If it's supposed to ignore noinclude tags on other wikis then it's working the way it should. Locally on the other hand, one have to provide a header. --Sabelöga (talk) 01:55, 25 November 2020 (UTC)
 * Yes, in this case, the fact that  tags are ignored with scary transclusion works in our favour here, so this was was a reasonable workaround you devised. In the event the upstream bug is ever patched, we should be able to remove one of the duplicate headers, hopefully. In any event, in your request, you linked to two instances of system administrators. I assume for one of them you meant Global Sysops, but the headers don't seem to quite match up with either of those. Wiki tables can be a bit of a headache to work with, which I invariably don't have the time for, so I'm going to have to ask you to please figure out the wikitable formatting for those pages, and link me to the revisions. You may use either your sandbox on TestWiki or the Meta community sandbox. Thanks. Dmehus (talk) 02:28, 25 November 2020 (UTC)
 * That's good, and yeah, I can work that out. Sabelöga (talk) 02:32, 25 November 2020 (UTC)
 * Aand, done mh:test:User:Sabelöga/sandbox. Sabelöga (talk) 02:58, 25 November 2020 (UTC)
 * Thanks, but for Global Sysops, I'm seeing the same wikitext coding as what I used, and the new header doesn't match up with the existing columns, so that's my concern. Also, do you have a diff for the system administrators page? Dmehus (talk) 03:01, 25 November 2020 (UTC)
 * ✅ Well, they do duplicate in my sandbox in TestWiki but they don't do when I preview the copied text Meta, for some reason :/ Sabelöga (talk) 03:15, 25 November 2020 (UTC)
 * Okay, great. Thank you for preparing the updated headers in your TestWiki sandbox, which I've now separately blanked, and ✅ this request. Dmehus (talk) 08:49, 25 November 2020 (UTC)
 * Excellent, thank you! Sabelöga (talk) 09:22, 25 November 2020 (UTC)