Stewards' noticeboard

= CheckUser = {{Hidden|Instructions/Read before making a request| Use this section to request that a Steward do a CheckUser on a user/group of users who are suspected of sockpuppetry. If you suspect sockpuppetry, please compile evidence for this. Include as many links to similar behavior as possible such as overlaps in editing styles, grammar, edit summaries, or even SocialProfile data. Failure to do this may result in delays or a decline.

To make a request, press "edit" next to the CheckUser section header, copy the following code and place it at the very bottom of this section. Replace every section as needed:

Username@ wiki
}}

5 usernames@Librepediawiki

 * ✅. I commend your patience in dealing with this user; UAK appears to be the origin for all reported accounts + one other. I elected to go for the maximum route because of the vandalism-only nature of contributing and credible connection to long term abuse on Wikimedia as you suggest indicate to me there is little point to escalating warnings, although reaching out to stewards@ by email for reasonable discourse is still an option. There is room for abusefilters to be tailored in this case but I honestly just don't have time or competence to do that right now: another Steward, GS or interested party is free to make suggestions/enact additional measures based on this. --Raidarr (talk) 15:59, 10 May 2023 (UTC)

= Requests for (un)(b)locks = {{Hidden|Instructions/Read before making a request| Please use this section to request global locks (including self-locks), global IP blocks, or for either of these to be removed. If reporting vandalism-only accounts, make sure they fit the global standard definition for vandalism only accounts: there must be no or almost no constructive editing behaviour and, additionally, this behaviour should be occurring on multiple wikis.

To make a global lock or unlock request, press "edit" next to the "Requests for (un)(b)locks" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed:



 * Include your reason here ~
 * Include your reason here ~

If you're including multiple accounts in your report, format it as follows:


}}
 * Include your reason here ~
 * Include your reason here ~

Various users

 * These accounts are sockpuppets of 岐阜県民 who was locked.They told me that they'll kill us.This is so big problem.I'd like stewards to lock these accounts to prevent issues from them. by Buehl106·Talk·e-mail 08:48, 8 May 2023 (UTC)
 * ✅. There are quite a few more accounts than this which I will subsequently address. --Raidarr (talk) 14:35, 11 May 2023 (UTC)
 * These accounts are sockpuppets of 岐阜県民 who was locked.They told me that they'll kill us.This is so big problem.I'd like stewards to lock these accounts to prevent issues from them. by Buehl106·Talk·e-mail 08:48, 8 May 2023 (UTC)
 * ✅. There are quite a few more accounts than this which I will subsequently address. --Raidarr (talk) 14:35, 11 May 2023 (UTC)
 * ✅. There are quite a few more accounts than this which I will subsequently address. --Raidarr (talk) 14:35, 11 May 2023 (UTC)

Mayfair

 * I couldn't figure out the template but I would like to have this account locked since I don't think I'll be active here. --Mayfair (talk) 21:44, 8 May 2023 (UTC)
 * Very well, this is ✅. --Raidarr (talk) 16:01, 10 May 2023 (UTC)
 * Very well, this is ✅. --Raidarr (talk) 16:01, 10 May 2023 (UTC)

= Permissions =

Administrator/Bureaucrat access
{{Hidden|Instructions/Read before making a request| Use this section to request Stewards grant you administrator or bureaucrat rights on a wiki without any active bureaucrats (or unwilling bureaucrats if they refuse to certify a successful vote) following a local election. We normally don't grant permissions without a local election for advanced rights like this so you'll need to make a local election unless you accidentally demoted yourself.

If you accidentally removed your own permissions, you can also use this section to request re-addition.

To make a request, press "edit" next to the "Administrator/Bureaucrat access" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed:

Username@ wiki
Include any comments here ~ }}

Corviraptor@ultrakillwiki
Hi! I ran a local election a little while back, and would like it closed so I can start working on things that require local bureaucrat and administrator rights on the wiki, and so that I can work on getting more bureaucrats to help, as I'm very busy these days!

Corviraptor (talk) 22:57, 5 May 2023 (UTC)
 * Clerically noted as ✅ by Agent. --Raidarr (talk) 21:16, 7 May 2023 (UTC)

Artubass@celestewiki
I would like a temporary appointment to sysop as the only active contributor. The reason I need this permission is to edit the protected Main Page, which is currently under construction. Artubass (talk) 11:08, 12 May 2023 (UTC)
 * Have you tried to contact Celeste first? I would recommend trying that and waiting a few days before requesting this. If it's also just for a specific page only that could potentially be unprotected temporarily rather than an appointment just for that. Reception123 (talk) ( C ) 11:20, 12 May 2023 (UTC)
 * Yes, I have tried contacting Celeste via Discord. Sure, unprotecting the Main page will be sufficient. How can I request that? Thank you. Artubass (talk) 12:15, 12 May 2023 (UTC)
 * I have reached out to the wiki operator on discord, who publicly stated there an intention to make Artubass a sysop herself. She replied to direct message rather quickly to say she was still intending to do it, just had a snag with her account making the process slower but not impossible, and still intends to do it in the next few days. I will mark this as for now because of this, but if a week passes with no progress please leave a reply and this can be addressed by Stewards.  --Raidarr (talk) 22:37, 14 May 2023 (UTC)

Other access
{{Hidden|Instructions/Read before making a request| Use this section to request Stewards grant you minor local access such as autopatrolled, confirmed, or rollbacker on wikis without any active bureaucrats.

You may also use this section to request a Steward grant you a Global IP block exemption.

To make a request, press "edit" next to the "Other access" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed (change wiki to global if requesting an IP block exemption):

Username@ wiki
Include any comments here ~ }}

Removal
{{Hidden|Instructions/Read before making a request| Use this section to request Stewards remove rights from a user (such as bureaucrat) following a local revocation or resignation, or to request they remove user rights only they may modify for any reason as defined by group revocation policy. You can also use this section to request bureaucrats remove your own rights on a wiki or on all wikis (including global rights).

To make a request, press "edit" next to the "Removal" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed (change wiki to global if requesting a Steward remove your rights on all wikis or global rights):


Add additional comments here.

~ }}

Lackbfun@erawiki
Per inactive and security concerns, the community of this wiki enacted a consensus to remove all permissions from user:Lackbfun. Howard (talk) 14:26, 10 May 2023 (UTC)


 * Agreed on removing user:Lackbfun's permissions due to inactivity and security concerns. Asck1116 (talk) 15:31, 10 May 2023 (UTC)
 * Confirm.Agreed on removing user:Lackbfun's permissions due to inactivity and security concerns. Awk-DSPR (talk) 17:13, 10 May 2023 (UTC)
 * Agree. Lackbfun has been inactive for almost 3 months. CK Rainbow (talk) 01:26, 11 May 2023 (UTC)
 * Permissions removed per consensus above. Reception123 (talk) ( C ) 11:21, 12 May 2023 (UTC)

Lackbfun@erawikisourcewiki
Per same reasons. Howard (talk) 14:26, 10 May 2023 (UTC)


 * Agreed per same reason. Asck1116 (talk) 15:35, 10 May 2023 (UTC)
 * Agreed per same reason. Awk-DSPR (talk) 17:14, 10 May 2023 (UTC)
 * Agreed per same reason. CK Rainbow (talk) 01:30, 11 May 2023 (UTC)
 * Removed per consensus. Reception123 (talk) ( C ) 11:22, 12 May 2023 (UTC)

Gauri@eswconrefwiki
Currently, I'm the only active user in this wiki. This user has been inactive since 2020. Please, for security reasons, remove her bureaucrat rights (do not remove her sysop rights).

SRuizR (talk) 03:31, 20 May 2023 (UTC)


 * SRuizR, can you link to your local community policy that permits this? Dmehus (talk) 03:48, 20 May 2023 (UTC)
 * The wiki is marked as private, so it may not be possible for SRuizR to directly link to the community policies of the wiki in a manner that is publicly accessible. They can certainly provide the relevant portion of the policy through other means, such as posting it verbatim in this thread, providing it through a screenshot, etc. However, the wiki governance and voting policy states that owners of personal wikis are solely responsible for managing them, which this wiki may be given its narrow scope as described in its request. Therefore, community policy may not be relevant here, and this request for removal can proceed regardless of whether local policy (if it exists) allows it. Tali64³ (talk) 04:02, 20 May 2023 (UTC)
 * That is true, yes, but it is still helpful, and a best practice, for requestors to link to their local policy for Stewards to assess. In terms of whether it is construed as a 'personal wiki', it's hard to say, but I would note we have quite a few community-run, non-personal private wikis. As co-drafter of that RfC that led to that wiki governance policy, or, rather, its predecessor, I intentionally made "personal wikis" narrowly construed, to ensure community consensus, or at least some form of involvement, applies to most wikis on Miraheze in keeping with the Miraheze ethos, or raison d'être. Hope that clarifies! :) Dmehus (talk) 04:06, 20 May 2023 (UTC)
 * The Rules page says "En caso de inactividad, el administrador o burócrata que concedió el acceso podrá retirarlo por motivos de seguridad. En caso de que esto ocurra, el usuario podrá solicitar al admininistrador que le vuelva a conceder el acceso y se concederá sin problema.". As I was the one to give her member, sysop and bureaucrat access, I can revoke it, but I prefer to leave removal of bureaucrat access to stewards. I don't know if this counts as a personal wiki, but I doubt it; me and Gauri decided to create it to work on some proposals for our home wiki, inviting other interested users from that wiki and working together to help improve management of conflicts there. As I mentioned it before, I am the only active user in this wiki since 2020, so there is nobody opposing the rules that I have implemented. If Gauri returns to the wiki, I will give back her bureacrat access; this removal is for security reasons.--SRuizR (talk) 04:42, 20 May 2023 (UTC)
 * Thanks, that's great. Policies can be decided by one user, in the case of small wikis with small communities, so that should be fine. Dmehus (talk) 04:47, 20 May 2023 (UTC)
 * I supplement to say that this best practice, while not explicitly codified in wiki-side policy, does have strong affirmation in the MSCoC and is a generally held/recognized reasoning in many community circuits in and out of Miraheze. It is typical that an inactive operator is simply not entitled to powers if they have no means to use them and have been given ample chance to participate. Communities like this typically rarely ever have written out procedures for governance; I wish more of them did but I must operate with the typical absence in mind. In case of a private wiki discretion applies even more as it is often impractical to operate with the same standard of community idealism that more open wiki concepts are based on.

Interesting discussion aside this request is ✅. --Raidarr (talk) 12:30, 20 May 2023 (UTC)

= Wiki (un)deletion = {{Hidden|Instructions/Read before making a request| Use this section to request Stewards undelete a wiki if it was deleted for inactivity (not if it's 'closed' [i.e. uneditable but still online] in which case you must use Requests for reopening wikis).

To request a wiki deletion, if your wiki has multiple contributors, you must hold a local discussion beforehand and consensus must be in favor of the wiki closing. If your wiki is a small/personal one where you are the sole contributor, no discussion is needed.

To make a request, press "edit" next to the "Wiki (un)deletion" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed:


}}

gianalbertochini

 * ✅. --Raidarr (talk) 18:51, 20 May 2023 (UTC)

Terrapedia

 * Wiki has been fixed so deletion is no longer necessary. Reception123 (talk) ( C ) 05:59, 12 May 2023 (UTC)

PoorMemes Wiki

 * Qualitipedia, the administrative entity was shut down - this wiki is not a part of it and so that rationale does not apply. I have reached out to your cofounder on Discord to see what he thinks of this as he is still reachable elsewhere and I'd like his 2c before proceeding. If he agrees I can do this outright. --Raidarr (talk) 16:26, 10 May 2023 (UTC)
 * Okay. Commetia/Kazakhar (talk/Contact) 20:53, 10 May 2023 (UTC)
 * Carl did not object, and so this is ✅. --Raidarr (talk) 19:16, 11 May 2023 (UTC)

Drawutha

 * The original request was a private wiki created by and  is not its requestor nor appears to have been a member. If Gool wishes to contribute to the original wiki then Drawuthia needs to be involved, or the wiki needs to be dropped and then the request can proceed as normal, or a new domain should be chosen - I'd lean this last one since Drawutha is an unusual name and it's odd that they'd overlap this way unless Gool knows the original requestor and can perhaps get in contact or elaborate here if there's a connection. If Gool does not know about this then it would be simpler to pick a different name. If we're going with a drop, I defer to a steward-sre colleague. --Raidarr (talk) 20:51, 13 May 2023 (UTC)
 * Dear all, Gool speaking, I am sorry to create such confusion. I assume that I was requesting this request through a different account few months ago that I simply forgot about. My apologies. changing the name is absolutely possible if it is the easiest solution in our hands. Regards 2A01:E0A:AAF:B2B0:5DD5:72E:2960:28E3 21:29, 13 May 2023 (UTC)
 * So I take that as meaning that Drawutha was an old account of yours that you no longer have access to? Tali64³ (talk) 22:22, 13 May 2023 (UTC)
 * If Drawutha is an old account name there are two options: 1. recover the original account and post here at which point I can undelete the original wiki for you, or 2. change the database name so the request can be completed on the spot. It would be cleaner to restore the original account if you can, but that is up to you. --Raidarr (talk) 22:14, 14 May 2023 (UTC)

Terragen Database

 * ✅. Good luck on your new horizons. --Raidarr (talk) 22:12, 14 May 2023 (UTC)
 * Didn't quite catch that in time. What's your new host? --Routhwick (talk) 21:28, 15 May 2023 (UTC)

Feign Wiki

 * New domain, please? --Routhwick (talk) 05:17, 19 May 2023 (UTC)
 * https://feign-wiki.tk @Routhwick Hey Türkiye  Message? 11:42, 19 May 2023 (UTC)
 * wikis ✅ as requested. --Raidarr (talk) 01:01, 21 May 2023 (UTC)
 * Thank you very much @Raidarr :) Hey Türkiye  Message? 07:19, 21 May 2023 (UTC)

A Young Girls Oral Surgery Trip

 * Marked as ✅ outside of the SN. --Raidarr (talk) 18:52, 20 May 2023 (UTC)

= Restricted setting change requests = {{Hidden|Instructions/Read before making a request| Use this section to request Stewards change a setting which is restricted and cannot be changed by bureaucrats, including extensions which require a Steward to enable them (such as Cargo, Semantic MediaWiki) and Dormancy Policy exemptions.

To make a request, press "edit" next to the "Restricted setting change requests" section header, copy the following code and place it at the very bottom of this section. Replace every section as needed:


}}

Wiesepedia

 * ✅ --Raidarr (talk) 16:11, 10 May 2023 (UTC)

szk.miraheze.org

 * ✅ --Raidarr (talk) 20:36, 11 May 2023 (UTC)

The Lion King Wiki

 * While it's a private wiki, which may have a lower threshold for an exemption to Dormancy Policy, there also has to be a need. My personal view is that three additional pages do not justify that need, given that it only takes one user to make a log action or an edit every sixty (60) days to prevent the wiki from closing. Once it closes, you have a further four months around which to edit on the wiki or to re-open it. Note that RecentChanges activity does count towards to preventing deletion. Even when a wiki is deleted, it's merely hidden until SRE run the deletion script. Even then, Reception123 maintains XML dumps on one of SRE's servers, around which the wiki can be re-imported. To my knowledge, he has not deleted any of those XML dumps in the past few years. Dmehus (talk) 03:54, 20 May 2023 (UTC)
 * I tend to agree with Dmehus's assessment on this. Exemptions depend on one of the following at least; a) a very substantial wiki, b) a very clear seasonal editing basis (ie something that only happens once a year or so which is outside the scope of when dormancy may fatally hit the wiki) or c) some very strong basis which falls outside these parameters but follows their vein. To be honest I don't find the case to be substantial and adding a couple pages does not make or break exemptions, especially when the page count right now is five short-to-moderate pages from what I can tell. I imagine the weak basis initially is why the exemption was removed. Unless you have a case why this can't happen I would suggest just making recurring small edits to keep the wiki alive or to flesh it out much more significantly. There isn't a minimum page count to aim for, more a general sense of completeness or, again, a strong basis for why dormancy should not apply and I don't see it in this case.
 * Thank you for the input; I note that at least from what I see, private wiki XMLs are only held on for so long and are cleared periodically. If the drop was recent it's worth getting him to take a look but if it was say, last year from now, it reasonably would not be present. I don't know of any formal practice around this and it's not something to lean on ideally, but Reception can further clarify if there's more to it. --Raidarr (talk) 19:09, 20 May 2023 (UTC)

Bapham123 Wiki - Việt Nam (lần 2)

 * ✅. --Raidarr (talk) 18:58, 20 May 2023 (UTC)

Looney Pyramids
=Wiki reports=

Copyright Violation at bngyaanipediawiki
Over 500 pages on bngyaanipediawiki have been imported from the Bengali Wikipedia without proper attribution (the page history contains only the latest revision when the import was carried out and uses the wrong interwiki prefix) by a globally locked user. The wiki has other examples of improper attribution as well were the pages were manually copied over from BN Wikipedia. Furthermore, it appears that a number of copyrighted pages copied entirely from Banglapedia (the list can be found here), which were believed to have been cleaned up nearly two years ago by Steward request following a user report appear to have survived the purge (for example, these pages) as well. The last time a Steward (Dmehus) tried to contact the wiki bureaucrat who imported these pages, he received no response. I request you to delete the pages copied from Banglapedia and decide what to do for the rest where, at least in theory, the wiki could be given a chance to either go back and correctly import the pages or add attribution templates. Personally though, I do not see what purpose the wiki serves if almost all the pages (main page included!) are just copied over from external sites but ultimately, it is obviously your decision and I am just adding my two cents. Thank you. Redmin Contributions CentralAuth (talk) 23:38, 8 April 2023 (UTC)


 * Courtesy ping: Redmin Contributions CentralAuth (talk) 23:41, 8 April 2023 (UTC)
 * Thank you for your report! This wiki is part of the Gyaanipedia network which was shutdown due to egregious copyright violations so I am equally closing this wiki too. Thanks. Agent Isai  Talk to me! 18:01, 17 April 2023 (UTC)
 * If the Gyaanipedia network was shut down then please get rid of these leftovers as well: zhgyaanipediawiki, commonsgyaanipediawiki, degyaanipediawiki, esgyaanipediawiki. Thanks. Redmin Contributions CentralAuth (talk) 08:38, 18 April 2023 (UTC)
 * Apologies for the delay. I confirmed with Agent that these were an oversight and I have taken the liberty to ✅. Courtesy cc as a functionary on multiple of these so he knows what happened if he attempts to enter them. --Raidarr (talk) 22:22, 14 May 2023 (UTC)

=Discussion closure=

= Miscellaneous=

I deleted the “everyone” group and now I can’t access certain things.
I was trying to hide pages on philosiverse.miraheze.org (my wiki) as the associated books have not even been announced yet. I tried removing the “everyone” group, but now I can’t access things such as AbuseFilter. Can you undo that change please?

Bauerbach (talk) 15:55, 18 May 2023 (UTC)


 * Would you like us to reset all usergroups to their default version? Reception123 (talk) ( C ) 18:30, 18 May 2023 (UTC)
 * Yep! Also, how can I make it so that only a few people can view pages short of saving everything to my computer and having the wiki deleted? Bauerbach (talk) 19:37, 18 May 2023 (UTC)
 * I leave the heavy hitting to Reception as he has already replied, but I have two notes. One: never delete groups without understanding the implications. In this case you deleted the system group that gives certain basic rights to all users. Done wrong this can do other things like confuse the system on what a user is or straight up remove your ability to administer the wiki were you to remove bureaucrat. Two, setting the wiki to private was already enough. Nobody except Stewards, Trust and Safety and SRE (technically) would be able to view the wiki outside of its main page except you and users you specifically assign to the Member group. --Raidarr (talk) 20:05, 18 May 2023 (UTC)
 * All groups reset to default settings. Reception123 (talk) ( C ) 16:46, 19 May 2023 (UTC)