Meta:Administrators' noticeboard

Request for variable
Hi! As the Meta-Wiki here on Miraheze doesn't need to change the interwiki table, concluding that everything here is translated through the translation extension: mw:Extension:Translate, I ask you to disable this function, $wgMinervaAlwaysShowLanguageButton (In Special:ManageWiki/settings#mw-section-localization ManageWiki). This will remove that language icon in the MinervaNeue theme (the current mobile theme here), and will of course avoid confusion, as we don't need another site to be multilingual, as stated above. Sites like MediaWiki already do this, maybe doing it here is good and won't hurt either. The tag will show the page in other languages. --YellowFrogger (Talk — ✐) 18:13, 11 January 2022 (UTC)
 * After a conversation on the Discord server nothing happened here. I ❌,admitting my indignation, because the same thing will happen with the SandBox that nobody replied, neither refuses nor approves, it is for this and other reasons that, in my opinion, there should not be administrators noticeboard or include in the Meta namespace. I didn't like the posture of users over there, playing with my request while I was being serious. This here is very simple to solve, until the analysis, regarding the addition of this function using only ManageWiki. Definitely, in a few months, some more respected user will place an order and it will be accepted, or else activated on its own, but remember that I was the first to request this here. --YellowFrogger (Talk — ✐) 06:39, 12 January 2022 (UTC)
 * I reopened this here. --YellowFrogger (Talk — ✐) 17:57, 12 January 2022 (UTC)
 * In response to Doug on Disc, yes, I still believe (hopefully) that the next admin who requests this will have the same delay. The scope is clear here, this includes something that probably sites that don't need others disable the language icon in MinervaNeue, and it even shows "This page doesn't exist in other languages", of course it exists, it's translated locally with Extension: Translate. Also, I would recommend that you reply me that you are busy, not following what users were doing (does not include the joking part as you are respectful, more ignoring). You could have asked me to wait, if you said that, I probably lost --YellowFrogger (Talk — ✐) 06:56, 12 January 2022 (UTC)
 * If there's no meaningful objections to this after a week or so, I think we can consider disabling it. Dmehus (talk) 07:04, 12 January 2022 (UTC)
 * I reopened. I'm not expecting an immediate response (decline/approval). But this is technical here at Meta, but it's still low priority. --YellowFrogger (Talk — ✐) 17:55, 12 January 2022 (UTC)
 * Cats478.jpg

--YellowFrogger (Talk — ✐) 18:06, 12 January 2022 (UTC)


 * I'm not very technically proficient with this topic and I'm not in the best position to research, but I would like to see input on the merit here since at face value, it's at least worth considering. --Raidarr (talk) 22:32, 12 January 2022 (UTC)
 * Dmehus won't be back for a few days now. This here is not of extreme urgency, but I guarantee, it will help not to confuse mobile users. This icon in Minerva says that there are no pages in the other language, while in fact the page is internally translated and the tag does this service by showing the expected languages. --YellowFrogger  (Talk — ✐) 22:39, 12 January 2022 (UTC)

Extensions
Is there currently a translation administrator available to mark the recent change on the Extensions page for translation? Thanks --YellowFrogger (Talk — ✐) 20:03, 13 January 2022 (UTC)
 * ✅. Agent Isai  Talk to me! 21:18, 13 January 2022 (UTC)
 * Thank you. I also expected an extension like this in Miraheze, however, PageViewInfo is WMF specific and HitCounters doesn't work. PageViewinfo shows views in the last thirty days in &action=info with API modules, like Wikipedia, including a very interesting graph showing the drops/rises of page views . I'm sure this is better than Matomo (because it shows on each page) then we would see the engagement of a wiki, and the best, each page. HitCounters is more limited and previously (in older versions of MW, including Monobook) they were automatically displayed in the footers of wikis, the functionality was removed, but it is still possible to install, I don't understand why it is not possible in Miraheze, PageViewInfo is perhaps more real/less liar because HitCounters changes page views with each update. I hope that one day, PageViewInfo will be set for all wikis besides WMF and also Miraheze, even if a MediaWiki page shows the installation tutorial. --YellowFrogger (Talk — ✐) 21:36, 13 January 2022 (UTC)
 * The second part of this seems better suited to perhaps the Community Noticeboard for its broad nature, or perhaps inquiry via discord to SRE for faster response.--Raidarr (talk) 22:06, 13 January 2022 (UTC)
 * This was another statement of mine. --YellowFrogger (Talk — ✐) 22:59, 13 January 2022 (UTC)
 * I don't understand your point, you seem to have gone from asking to mark a page for translation to talking about 2 previously declined extensions. As previously discussed, PageViewInfo is very Wikimedia-specific (as you noted) and HitCounters has a horrible performance issue and was previously broken. I've used Matomo through it's dashboard and it is a very, very powerful and detailed tool but there is currently no way to show public, detailed statistics per T7512. Agent Isai  Talk to me! 23:51, 13 January 2022 (UTC)
 * That statement of yours at the end made me curious. There is a way to access Matomo besides that normal page (your dashboard, according to you)? Where do I get access? --YellowFrogger (Talk — ✐) 00:03, 14 January 2022 (UTC)
 * The tool is only available for those with an LDAP account (SRE, Board and T&S). It is not available to normal users due to the amount of personal data that is available on it. Agent Isai  Talk to me! 00:32, 14 January 2022 (UTC)
 * Strange. What personal data does this have? --YellowFrogger (Talk — ✐) 00:54, 14 January 2022 (UTC)

Autopatrol Fan Formuły 1
I've seen your translations a bit, and maybe this user has good intentions. He's been editing since last month (joins Discord) and maybe his edits don't need to be patrolled. --YellowFrogger (Talk — ✐) 16:31, 15 January 2022 (UTC)


 * ✅. Dmehus (talk) 06:48, 18 January 2022 (UTC)

Merge Template:· into Template:Bullet
Template:· inserts a middot which looks extremely similar to bullets (Template:Bullet inserts bullets), so I suggest merging Template:· into Template:Bullet (Template:Bullet is a few days older).  Anpang 📨 03:11, 16 January 2022 (UTC)
 * I don't support it. Instead, it's better to delete a page. I use  in my signature and it can get in my way. --YellowFrogger  (Talk — ✐) 03:15, 16 January 2022 (UTC)
 * I said, "so I suggest merging Template:· into Template:Bullet" That means Template:· will be turned into a redirect to Template:Bullet and Template:Bullet will be the same, no changes.  Anpang 📨 03:20, 16 January 2022 (UTC)
 * Okay, good for explaining. Let's see if something doesn't happen. --YellowFrogger (Talk — ✐) 03:33, 16 January 2022 (UTC)
 * Done. See? Nothing happended, your siggy is still fine.  Anpang 📨 03:34, 16 January 2022 (UTC)
 * What do you mean by that? --YellowFrogger (Talk — ✐) 03:40, 16 January 2022 (UTC)
 * You first thought your signature was going to break because Template:Bullet would merge into another template (NOT the middot template into the bullet template) so I said it's fine, nothing happended to the bullet template which also means your signature/siggy  Anpang 📨 03:51, 16 January 2022 (UTC)
 * Anpang, with an acknowledgement to YellowFrogger's response, I've ✅ this, per your request. However, I've not done it as a history merge; I've deleted the two redirect templates as simply unused, or with little use, and because it's better to consolidate transclusions against a single template in order to track and maintain usage. Dmehus (talk) 04:14, 16 January 2022 (UTC)

Request for delete this page
Hello. Please delete the following page: Thank you --YellowFrogger (Talk — ✐) 02:20, 17 January 2022 (UTC)
 * User:YellowFrogger/SEO


 * ✅. Dmehus (talk) 03:25, 17 January 2022 (UTC)

Sitenotice
Hello. It seems that the only user who maintains sitenotice global is Agent. There was supposed to be a warning about involuntarily closed wikis/errors caused by migration, this might help desperate users. If this were to be done today, unfortunately it would be late, as it was supposed to be done earlier. I was even surprised that Miraheze didn't make any post-migration website notices. But now, it seems unnecessary. --YellowFrogger (Talk — ✐) 03:14, 17 January 2022 (UTC)


 * YellowFrogger, So there are local sitenotices, for Meta Wiki-specific announcements, in this case, global central notices, which primarily Stewards administrator, and GitHub repository sitenotices, which Agent takes care of, for SRE-related maintenance or notices (i.e., extension removals), the latter of which can be applied to specific wikis or to all wikis. It's not what clear you're asking for, but this seems to be GitHub repository-related, so closing as ❌. Dmehus (talk) 03:23, 17 January 2022 (UTC)
 * I asked my fellow SRE collogues if we could add a sitenotice for the closed wikis/SVG image issues but they said that it wouldn't be necessary which is why they're not on. Either way, most outstanding issues have thankfully been fixed. Agent Isai  Talk to me! 05:19, 17 January 2022 (UTC)

Autopatrol
May I please be considered for autopatrolled rights? I'd like to create some redirect pages for common search terms (as discussed in Discord, and within reasonable limits of course) to help users better find sections within articles commonly asked about on Discord. Later, if appropriate, I may be able to help out on some other stuff occasionally as well. Thanks! | -- FrozenPlum  (Talk / Email) 01:03, 18 January 2022 (UTC)


 * I with this.  Anpang 📨  01:11, 18 January 2022 (UTC)
 * Reliable and unproblematic editor. I see no apparent need to continue patrolling. dross  (t • c • g) 06:39, 18 January 2022 (UTC)
 * ✅. Dmehus (talk) 06:44, 18 January 2022 (UTC)

Closed wikis

 * Page: Closed wikis

Any translation administrator to mark recent changes for translation? I made some changes talking about the need for local election after an RfC, the content on this page was out of date and I've updated it now with this information.

Soon I will remove the warning  if necessary

Thanks, --YellowFrogger (Talk — ✐) 00:22, 19 January 2022 (UTC)


 * ✅ ~ RhinosF1 - (chat)· acc· c -  07:48, 19 January 2022 (UTC)

Request to delete
Please delete the following pages: These are all the deleted translation units and there is no point to keep them. Thanks, Magogre (talk) 08:29, 19 January 2022 (UTC)
 * Translations:Staff/12/en
 * Translations:Staff/12/hi
 * Translations:Staff/12/pt-br
 * Translations:Staff/10/en
 * Translations:Staff/10/hi
 * Translations:Staff/10/pt-br
 * Translations:Staff/11/en
 * Translations:Staff/11/hi
 * Translations:Staff/11/pt-br
 * Translations:Staff/3/en
 * Translations:Staff/3/hi
 * Translations:Staff/3/pt-br
 * Translations:Staff/4/en
 * Translations:Staff/4/hi
 * Translations:Staff/4/pt-br
 * Translations:Staff/5/en
 * Translations:Staff/5/hi
 * Translations:Staff/5/pt-br
 * Translations:Staff/6/en
 * Translations:Staff/6/hi
 * Translations:Staff/6/pt-br
 * Translations:Staff/7/en
 * Translations:Staff/7/hi
 * Translations:Staff/7/pt-br
 * Translations:Staff/8/en
 * Translations:Staff/8/hi
 * Translations:Staff/8/pt-br
 * Translations:Staff/9/en
 * Translations:Staff/9/hi
 * Translations:Staff/9/pt-br
 * Hm, so it was this request that led to the deletion of the page (translated through) (although that page doesn't even have much content). I will recreate. --YellowFrogger ( talk ) ( ✔ ) 05:09, 20 January 2022 (UTC)
 * ✅ Dmehus (talk) 05:22, 20 January 2022 (UTC)
 * , you deleted the entire translated pages of Staff/hi and Staff/pt-br. I only requested to delete the above pages; others were fine. Magogre (talk) 05:29, 20 January 2022 (UTC)
 * Magogre, yeah, but that would've been problematic to try and delete all those pages individually. Since the  translation was less than 20% complete, with only the page title translated, this left only the   translation. As it was only a few short sentences, it was simpler just to delete the page and have it be retranslated. Thanks. Dmehus (talk) 06:06, 20 January 2022 (UTC)
 * , that's fine and it was no big harm but I believe user contributions and their time should be respected. That was my main point and that is why I took my half an hour to filter the above pages instead of just requesting the deletion of Staff/hi, Staff/en and Staff/pt-br. Indeed, it can be translated again. YF has already translated it to pt-br. --Magogre (talk) 07:59, 20 January 2022 (UTC)
 * Magogre, they are. That's why I thanked ThisIsACreeper1101 explicitly in my log summary. Dmehus (talk) 08:28, 20 January 2022 (UTC)

New noticeboard only for blocks/global locks
Hi! What Mirahezians think about a page creation for requesting global locks/local blocks (or rather incidents). We already have SN or AN, I know, but most threads are not about locks (rarely, it's too messy and late to handle locks). We will rely on this Wikipedia page, or work in a similar way, where the requestor(s) state the reason, the username, and an administrator/bureaucrat/steward/GS will evaluate: Not done or Done. The structure would be similar to the common noticeboards, with a form similar to RfA (automatic). I'm sure creating a page just to resolve blocks would help a lot. Even to the point where I consult you guys to see if I open one (RfC), and avoid snow or out-of-scope. Leave here what you think. Thanks! --YellowFrogger ( talk ) ( ✔ ) 05:21, 22 January 2022 (UTC)


 * There are ideas in the works to divide the noticeboards by function in general (a help desk, maybe a task system, maybe an experimental system to be tried by T&S). I like the spirit of the idea, but I think it would just muddy the waters at the time for something that can be a pretty simply addressed message here, or as often is the case, through discord. The suggestion as described feels just a bit too bureaucratic in light of future changes and the raw specifically of the suggestion. --Raidarr (talk) 09:28, 22 January 2022 (UTC)
 * My main goal is to cut down on bureaucracy around response times! It might not be nice to have an extra noticeboard (more complicated to look for), but think about the administrators response time. --YellowFrogger ( talk ) ( ✔ ) 04:26, 23 January 2022 (UTC)
 * It's a noble goal, but I don't see how adding another function split from the official one is really going to do it. I think the only real path on this is to actually re-design how the system works, so users can coherently find the areas they want sooner than later instead of being bounced between various pages. That may be inevitable to a point, but we can do better especially since blocks/global locks are a rare enough appearance on either noticeboard and tend to be resolved promptly enough. What this does is add a bureaucratic element to completing locks where on Meta, the given administrator is probably already made aware either here or IRC/Discord, or with CVT, CVT gets to it when they do and resolve it fine as it is. There is simply not a niche for having this. It's an extra noticeboard for its own sake and I don't believe it sells. You think it would help a lot, I think it offers absolutely nil towards any actual problems. --Raidarr (talk) 11:26, 23 January 2022 (UTC)

User:YellowFrogger/Patrolling the edits to main namespace
Hi! Can I move this page: User:YellowFrogger/Patrolling the edits to namespace (main)? Do you agree with this? Thanks! --YellowFrogger ( talk ) ( ✔ ) 03:56, 23 January 2022 (UTC)
 * The way it's written, especially with focus to you and your advice is better suited to the userspace. Personally I think there should be collaboration between multiple meta regulars to make a page written to be suited for the mainspace. --Raidarr (talk) 11:28, 23 January 2022 (UTC)
 * I will decide to keep it in my namespace. I had even put my signature on the page. --YellowFrogger ( talk ) ( ✔ ) 17:49, 23 January 2022 (UTC)
 * YellowFrogger, I believe this duplicates the guidelines of patroller granted and the  documentation page. I would, therefore, entertain a history merge to Patrollers, so you can adapt and merge in the non-redundant text there, if desired. Dmehus (talk) 21:54, 23 January 2022 (UTC)
 * I created it thinking about these two pages quoted by you, it doesn't talk exactly how to mark a patrolled as patrolled. Also, what is "merge history". Even so, thanks for the reply. --YellowFrogger ( talk ) ( ✔ ) 00:00, 24 January 2022 (UTC)

Patroller request (Hypercane)
Hello, I would like to be considered for the patroller user group. I have been attempting to increase my activity as of recently, and I would like to help out even more (even if it is just one user right added). I have recently helped another user on the community noticeboard. Still in the process of helping them, but I am pretty sure with my prior experience as an administrator elsewhere I would be fit for the position. Thanks for your time. Hypercane (  talk ) 21:49, 24 January 2022 (UTC)
 * You can help more with some pages (translations, for example, if you know other languages). I don't see any problem supporting you, even though, the patroller group doesn't have much more than doing the simple thing of marking edits as patrolled. --YellowFrogger ( talk ) ( ✔ ) 21:58, 24 January 2022 (UTC)
 * And participate in RfXs too --YellowFrogger ( talk ) ( ✔ ) 21:59, 24 January 2022 (UTC)
 * I already plan on helping out elsewhere here too, thank you though. Hypercane  (  talk <font color="#8152C6">) 22:02, 24 January 2022 (UTC)
 * Yes, if you continue at this pace, you can probably be a Wiki creator in 3 months :) --<span style="background:linear-gradient(90deg,#89005E,#89005E, #FF00AF); -webkit-background-clip:text !important; -webkit-text-fill-color:transparent;">YellowFrogger ( talk ) ( ✔ ) 02:05, 25 January 2022 (UTC)
 * ✅ ~ RhinosF1 - (chat)· acc· c -  22:05, 24 January 2022 (UTC)