Meta:Administrators' noticeboard

From Meta
Jump to navigation Jump to search
Administrators' noticeboard
Shortcuts:
This noticeboard is for anything that requires administrator intervention on Meta wiki only (anything related to global policies, global groups, or in some way involves Miraheze customer wikis should be discussed at the Community noticeboard!)

On Meta:Administrators' noticeboard (this page), you can:

If you would like to:

To add your request, type in a title and click the "Add Topic" button below.

Archives of Administrators' noticeboard [e]   



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)

@Gomdoli: 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)
@Dmehus -- Gomdoli (talk) 12:53, 28 October 2020 (UTC)
@Gomdoli: 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)
@Dmehus: and, you said Also, if you forget to {{ping}} someone, you can still go back into your message and insert a ping since no one has replied., 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. — revi 14:11, 28 October 2020 (UTC)
X mark.svg Not done as no real need. Dmehus (talk) 17:53, 10 November 2020 (UTC)

Double </language> tags

The training module Training modules/Dealing with online harassment/slides/on-wiki-steps-they-can-take feature double </language> 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)

@Sabelöga:  Done, 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)
@Sabelöga: Yeah, strange. Oh well, it works now. Anyway, I noticed that you added the noinclude tag around the languages tag in this edit. It's been my experience that the languages and translate tags are impervious to the noinclude 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)
@Dmehus: Well, if you mean that the language tags are automatically treated as noinclude 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 noinclude. 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)
@Sabelöga: Well, hrm, that's possible, I guess, but I have noticed that when transcluding translated pages, the languages tag seemed to ignore the noinclude 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)
@Sabelöga: 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 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)

@Waki285: 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)
@Waki285: 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 X mark.svg Not done. 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 Tech to appear in the page name for Tech: namespace? Dmehus (talk) 06:14, 18 November 2020 (UTC)

Request for interface-admin 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 interface administrator. 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)
 Done 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)

 Doing… HeartsDo (Talk || Global || Wiki Creator) 11:47, 13 November 2020 (UTC)
@R4356th:  Done HeartsDo (Talk || Global || Wiki Creator) 11:50, 13 November 2020 (UTC)
Thank you very much, @HeartsDo:. R4356th (talk) 12:11, 13 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)
 Done I did not notice the Discord/Verification page before. @Sabelöga:, I think that page's content could be replaced with a redirect to Discord/Verification/Intro. R4356th (talk) 14:30, 17 November 2020 (UTC)
@R4356th: Okay, but why then not move Discord/Verification/Intro to Discord/Verification? --Sabelöga (talk) 14:39, 17 November 2020 (UTC)
@Sabelöga: 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)
@R4356th: 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 sysop 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  done. 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 Meta: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: [[<tvar|tou>Terms of Use</>|Terms of Use]]. --Sabelöga (talk) 00:16, 21 November 2020 (UTC)

@Sabelöga: 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)
 Done 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)
@Sabelöga: 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)
@Dmehus: Okay, I was also thinking of Meta: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)

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)

@Sabelöga: 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)
@Dmehus: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)
@Sabelöga: 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)
@Dmehus: 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)

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 Meta: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)

@Sabelöga: 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 [[.../List]] 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 translate and languages tags ignoring the noinclude 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)