Meta:Administrators' noticeboard

Grant Local IP Block Exemption

 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
 * ✅ of Bukkit. In this case, DarkMatterMan4500's Spidey sense seems to have been correct. Dmehus (talk) 04:01, 17 February 2022 (UTC)

I averagely access the internet through TOR, as it is a great privacy protector. 29TB (talk) 17:38, 29 January 2022 (UTC)


 * You seem to know about the Local IP Block Exemption, which makes me wonder if you have actually been on this wiki with a prior account, given that your account is 8 days old at the moment. DarkMatterMan4500 (talk) (contribs) 21:24, 29 January 2022 (UTC)
 * Just because I know of that user group, does not mean I have a prior account. I merely looked at the RfCs. 29TB (talk) 22:01, 29 January 2022 (UTC)
 * Not relevant, DMM. --Raidarr (talk) 22:05, 29 January 2022 (UTC)
 * Fair point. I suppose I can just trash my own question as unrelated. DarkMatterMan4500 (talk) (contribs) 22:08, 29 January 2022 (UTC)
 * Per IRC, This is ❌. Blocks of proxies are done to prevent abuse and being allowed to bypass blocks should only be done where this is a legitimate need. I want to use TOR is not valid and Miraheze do not use any third party tracking on site that using TOR would prevent. Any client side tracking can be disabled client side and is unlikely to be helped. If there becomes a legitimate need, this can be re-evaluated. I will note that they are a wide range of reasons that would be acceptable and they can probably be met without a huge barrier. ~ RhinosF1 - (chat)· acc· c -  22:19, 29 January 2022 (UTC)


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

Community portal in Sidebar
Any system administrator or any other users who have sufficient privileges to edit the MediaWiki namespace? I propose to link the page Community portal to Noticeboards in MediaWiki:Sidebar.

For example, like this:


 * Noticeboards
 * Community noticeboard|Community noticeboard
 * Stewards' noticeboard|Stewards' noticeboard
 * Meta:Administrators' noticeboard|Meta Administrators' noticeboard
 * Meta:Community portal|Meta Community portal

I don't see great despair in putting the link, but because this page is newly created and many users are not aware of it. That said, I think this would help a lot. --YellowFrogger ( talk ) ( ✔ ) 00:36, 8 February 2022 (UTC)


 * For continuity I think it would make sense. At the same time I'd strongly encourage a look at renaming the RfA process to get that out once and for all. --Raidarr (talk) 01:26, 8 February 2022 (UTC)
 * Makes sense and will be useful for quick navigation. --Magogre (talk) 03:00, 8 February 2022 (UTC)
 * This would be quite beneficial for navigation. — Arcversin (talk) 01:19, 9 February 2022 (UTC)
 * I 100% support this action. I mean, it makes sense doing so. DarkMatterMan4500 (talk) (contribs) 02:08, 9 February 2022 (UTC)
 * Well this here a while ago and it looks like 4 unique editors (5 with me) agree with this. Even so, what will be done? --YellowFrogger ( talk ) ( ✔ ) 21:19, 12 February 2022 (UTC)
 * This has been ✅. The concern I have, though, is that the similarly named Community portal may be confusing with community noticeboard and actually increase the workload for Meta patrollers moving threads to the correct community noticeboard, but it's a reasonable request, and, I think, placing it at the bottom of the noticeboard lists should help to minimize this. We can monitor this and course correct accordingly. As an administrative note to a portion of the unaddress preamble to this request, it wouldn't be appropriate for a system administrator to make this edit to the MediaWiki:Sidebar. Administrators' noticeboard is indeed the best venue, and Meta administrators the best functionary to action this request. Dmehus (talk) 18:22, 13 February 2022 (UTC)
 * Thanks. But the only thing that intrigues me is the lowercase "Meta community portal" (C). --YellowFrogger ( talk ) ( ✔ ) 22:12, 13 February 2022 (UTC)
 * That was, in part, intentional and by design. Since Community noticeboard is capitalized, the lowercase "c" in Meta community portal may help to distinguish between the two similarly named portals. As well, grammatically speaking, it is more consistent with the practice of not capitalizing the name of the noticeboard. Dmehus (talk) 22:26, 13 February 2022 (UTC)

Deletion request(s)
Hello. Please delete the following pages:

These are all the unused/abandoned translation units. Thanks. --Magogre (talk) 08:29, 15 February 2022 (UTC)
 * ✅ Reception123 (talk) ( C ) 09:52, 15 February 2022 (UTC)
 * Thank you Reception123. --Magogre (talk) 11:09, 15 February 2022 (UTC)

Block for YellowFrogger
YellowFrogger is currently engaged in an edit war at User talk:Agent Isai. Multiple users have reverted their edits yet they continously reinstate and make more. Agent Isai is within their right to revert per w:WP:OWNTALK but YellowFrogger continuously edits and is well over the three-revert rule. Naleksuh (talk) 01:00, 16 February 2022 (UTC)


 * I have taken emergency action in light of the edit war and YellowFrogger's significantly declined behavior as well as delays in local sysop action. It is likely an unprecedented move and I apologize if it was an overstep. It is either way subject to proper local administrator review. Disruption should be ceased; any sockpuppet action to circumvent the block as retribution will be noted as well as actioned by global lock as abuse of multiple accounts. --Raidarr (talk) 01:06, 16 February 2022 (UTC)
 * If it's not too much, YellowFrogger has been too disruptive beyond any comprehensibility for quite some time now. If yesterday's incident regarding Ninox's similar behavior like voting again with a sock wasn't bad enough, wait until you see the disruption they added to my talk page, which I have reverted the moment it was set there. I am EXTREMELY disappointed in this user's behavior. I would probably ask YellowFrogger to seek some help and take a load off by taking a break from Miraheze for a while until he realizes what he has done wrong, and how he can come to terms of his recent wrongdoings. What I am essentially saying from this reply is for him to do something else for a while, and take a clean start and start all over again (that is, if he could get permission to have a fresh start). I do hope he comes back with maturity and competency. DarkMatterMan4500 (talk) (contribs) 01:22, 16 February 2022 (UTC)
 * User:Raidarr, global sysop actions are not supposed to be indefinite. It is supposed to be for a short time period, during which a local sysop can choose to extend it. Naleksuh (talk) 01:42, 16 February 2022 (UTC)
 * My impression was that this block was meant to be reviewed by a Meta sysop and the block reason would probably be amended either way so I guess this is fine for now but indeed, I would advise Raidarr to perhaps not indefinite block users on other wikis that are not Meta. Agent Isai  Talk to me! 01:48, 16 February 2022 (UTC)
 * The intention is for it to be reviewed and replaced, in which the time period is deliberately unspecified; noted for future cases however, as one of likely multiple advisories given the nature of the action. If it is not addressed when I return tomorrow I can look at a shorter time, perhaps the week duration that was issued on login wiki by Doug. --Raidarr (talk) 01:51, 16 February 2022 (UTC)
 * @Raidarr I have reviewed the block, and I approve of it, and have reblocked showing as such and have denied their unblock request. Zppix (Meta &#124; talk to me) 04:16, 16 February 2022 (UTC)
 * Support an indefinite block. I was surprised that they weren't (b)locked in the first place. Totally unacceptable behaviour. --Magogre (talk) 02:09, 16 February 2022 (UTC)
 * First off, don't use bullet points, this is a request, not a vote or public forum. Second, the user has already been blocked indefinitely but by a global sysop. I personally wouldn't have placed an indefinite block at all but it's outside of the global sysops policy to do so-it would make sense for a meta sysop to either set an expiration date or leave the parameters as is. Naleksuh (talk) 02:12, 16 February 2022 (UTC)
 * I agree with Naleksuh above that bolded bullet points aren't appropriate for requests for assistance from a Meta administrator. The community can advise Meta administrators on courses of action, and, occasionally, in the past, Meta administrators have delegated decision-making to the community on the best outcome for users, but in such cases, the authority to make that delegation to the community rests with Meta administrators and Stewards (depending on the type of conduct and outcome). I have reviewed YellowFrogger's recent conduct with Agent Isai. First of all, Agent Isai should have been clearer in his edit summaries, and ideally provided a warning on why YellowFrogger's edits were being reverted. Indicating "transparency" (one word) in an edit summary is not that helpful to someone whose native language is not English. A better option would've been to message him here, advising him how to properly edit his own comments where replies have already occurred (see also: this English Wikipedia editing guideline on the matter) by striking through his comments and adding his amended comments. Nevertheless, YellowFrogger's continuing to edit war was also highly problematic. Raidarr's action as a Global Sysop seems fine to me, and the appropriate venue to review the action is indeed Administrators' noticeboard. I do think a block on Meta Wiki is needed, but, at the same time, YellowFrogger is currently subject to an indefinite Steward-imposed global user restriction restricting him to creating any alternate accounts he requires logged in and, ideally, on Meta Wiki. Additionally, he is also subject to a Meta administrator-imposed editing restriction limiting him to using only his YellowFrogger account on Meta Wiki. Thus, an indefinite sitewide block would be at cross purposes with the aforementioned user restrictions. I am leaning towards either (a) an indefinite partial block from one or more namespaces (this is where the community's input would be helpful in helping to define the namespaces), with the option to appeal not sooner than three (3) months from the date of imposition or (b) a three (3) month partial block one or more namespaces ( namespace certainly, but likely   and   namespaces as well) Dmehus (talk) 03:43, 17 February 2022 (UTC)
 * I would support (a) where he is blocked on all namespaces indefinitely (but not sitewide blocked which would hinder him from creating user accounts, in accordance with the globally imposed restriction) and can appeal in 3 months. I think YellowFrogger should take some time off Meta to reflect on his actions, cool off, and once he's ready to appeal in 3 or more months, he can come back and will be gladly received by the community. Agent Isai  Talk to me! 05:24, 17 February 2022 (UTC)
 * If the partial block is for all namespaces simply to allow the creation of alt accounts publicly on Meta, that would be fine with me. Reception123 (talk) ( C ) 06:57, 17 February 2022 (UTC)
 * Except that wouldn't work, because a partial block on all namespaces vs. a sitewide block doesn't change anything here. Instead it's in the "block account creation" option. Naleksuh (talk) 07:00, 17 February 2022 (UTC)
 * We could block indefinitely from all namespaces, unchecking the "account creation" box. Though I agree there's not really a significant need for him to create alternate user accounts, this may invite further abuse or breaching of that restriction. I agree that it's best for YellowFrogger to not be able to edit on Meta Wiki, but since Meta Wiki is where wikis are requested, for mainly technical and transparency reasons, and because it's where certain other special page functions occur (i.e., global renames, logging in to Phabricator, modifying OAuth consumers, etc.), there is a need for him to have access to those functions, but no ability to edit on Meta Wiki, indefinitely, with the opportunity to appeal after at least three months. Dmehus (talk) 07:05, 17 February 2022 (UTC)
 * Would it be in consideration to block the bot and alternate account to avoid socking? SoyokoAnis  18:29, 17 February 2022 (UTC)
 * They are not blocked just for being other accounts unless they were created after the block or are being used to evade etc. Otherwise, there is no evidence that the block was necessary to prevent damage. Naleksuh (talk) 18:32, 17 February 2022 (UTC)

Block for Andyyeung7
As seen by their recent contributions I believe this user needs a block imposed on their account due to their disruptive behavior and editing. Hypercane (  talk ) 02:12, 16 February 2022 (UTC)


 * Hypercane, the user seems to have stopped the behaviour. In any case, given that the problems seem to have just been (repeated?) out of scope page creations, what the user needed was a clearer warning, which I've now ✅. Thanks. Dmehus (talk) 03:57, 17 February 2022 (UTC)
 * Ah okay, well that works out too. Thank you Dmehus. Hypercane  (  talk ) 12:07, 17 February 2022 (UTC)

Resignation of rights
Please remove my patroller and translationadmin flags. Thanks. --Magogre (talk) 04:19, 18 February 2022 (UTC)


 * Magogre, as with your similar request at stewards' noticeboard, ✅, with regrets and thanks for your service. I have left you with, as there should be no need to patrol your edits, but this can be removed also, if you request it. Dmehus (talk) 04:28, 18 February 2022 (UTC)

Moderation extension
I've enabled the Moderation extension.


 * Should autopatrolled or autoconfirmed users, or both, be auto-moderated?


 * Who should have the ability to moderate edits? Administrators, or administrators and patrollers? Dmehus (talk) 20:12, 20 February 2022 (UTC)