Stewards' noticeboard

    From Miraheze Meta, Miraheze's central coordination wiki
    You're currently logged out. If you're having problems with your wiki, you need to login.

    Looking to make a report regarding a specific user? In addition to being required to provide a thorough and complete report, you should also know that reports by anonymous or logged out users are not taken very seriously for a couple reasons, namely that:
    1. We don't know who is making the report; and,
    2. Western liberal democracies enshrine in a citizen's fundamental, constitutionally-enshrined legal rights the right to know and face one's accuser, and Miraheze is no different.

    Accordingly, please kindly login. If you are unable to login, please e-mail sre(at)miraheze.org with your username and the specific error message you are receiving, and they will assist you, or direct you to other global functionaries where appropriate.
    OOjs UI icon globe.svgStewards' noticeboard

    This noticeboard is only for requests that require Stewards', or, in a limited number of circumstances, Global Sysops' intervention. If in doubt, please try the Community noticeboard first, and you will be directed here if the matter requires a Steward.

    On the Stewards' noticeboard, you can request:

    • A Steward or Global Sysop locks a spam only or vandalism only account. Note that for vandalism only accounts, the vandalism must meet the global standard definition for vandalism, and to be a vandalism only account, there must be no (or almost no) constructive editing behaviour and, additionally, this behaviour should be occurring on multiple wikis.
    • Additional permissions on your wiki(s) that can only be granted by a Steward, such as a local interwiki administrator following a successful election.
    • A page requiring the bigdelete user right (more than 1,000 revisions) be deleted on your wiki.
    • A Dormancy Policy exemption for your wiki.

    You can report:

    • A Username Policy violation (whether in good-faith or bad faith).
    • A user suspected of abusing multiple accounts per the User accounts policy. You must link to specific revisions from both the suspected master and illegitimate alternate account(s).
    • Systemic Code of Conduct problems occurring by one or more user(s) on one or more wiki(s) and/or systemic Content Policy violations on one or more wiki(s). In either case, your report must link to specific revisions and, in the latter case, your report must be both thorough and comprehensive.

    If you would like to request:


    Please remember to:

    • Sign your request using ~~~~.
    • Stay respectful.
    • Give us enough details about your problem.
    Select an option below:
    OOjs UI icon arrowNext-ltr.svg CheckUser requests
    OOjs UI icon arrowNext-ltr.svg Requests for global (un)(b)locks
    OOjs UI icon arrowNext-ltr.svg Permissions
    OOjs UI icon arrowNext-ltr.svg Wiki (un)deletions
    OOjs UI icon arrowNext-ltr.svg Restricted setting change requests
    OOjs UI icon arrowNext-ltr.svg Wiki reports
    OOjs UI icon arrowNext-ltr.svg Discussion closure
    OOjs UI icon arrowNext-ltr.svg Miscellaneous
    Archives of Stewards' noticeboard [e]   


    CheckUser[edit | edit source]

    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@<subdomain>wiki ==
{{CheckUser request
 |status          = <!-- Don't change this line -->
 |user name1      = 
 |user name2      = 
 |user name3      = 
<!-- Up to 10 users -->
 | wiki           = <!-- Put the subdomain of the wiki here -->
 |reason          = Add your reasons here, including compelling evidence ~~~~
}}

    3 Usernames@tikiwiki[edit | edit source]

    Status:  Done
    List of users
    パズドラ神ゲー (contribs · deleted · block · log · block log · CentralAuth · check · x-wiki check)
    頼りない野菜は大事なんだよね (contribs · deleted · block · log · block log · CentralAuth · check · x-wiki check)
    メタジクロロベンゼン (contribs · deleted · block · log · block log · CentralAuth · check · x-wiki check)
    • CheckUser log
    • Reason(s): I suspect these accounts were created by same user. For first two users, who registered this afternoon at tikipedia, was randomly replacing articles with the same letter "アイヒ端末". I understand the first two users are same because in several wikis out of miraheze they are called LTA:アイヒマン. What I want to know is that whether the last user, User:メタジクロロベンゼン who registered just 1 minutes after User:パズドラ神ゲー is the same user as first two or not, since he also vandalizes the wiki. あーあ (talk) 10:47, 23 May 2023 (UTC)Reply[reply]
    P.S. Please check for User:白紙化用アカウント (contribs) too since one of the blocked user mentioned that this user is the main account of the LTA. Thanks.--あーあ (talk) 13:36, 24 May 2023 (UTC)Reply[reply]
    @あーあ: the three originally reported accounts are Yes check.svg confirmed as related and dealt with. I was unable to associate them with other vandalism including on ysmwiki or with the PS report. --Raidarr (talk) 13:04, 25 May 2023 (UTC)Reply[reply]

    Gifutami2@chizunetwiki[edit | edit source]

    Status:  Done
    List of users
    Gifutami2 (contribs · deleted · block · log · block log · CentralAuth · check · x-wiki check)
    Gihutami3 (contribs · deleted · block · log · block log · CentralAuth · check · x-wiki check)
    There was inconclusive CU evidence regarding these two users but other sockpuppets have been found and the behavioral evidence combined with the UA agent being the same is enough for a lock. Therefore, all the users found will be locked for LTA. --Reception123 (talk) (C) 11:04, 26 May 2023 (UTC)Reply[reply]
    Thank you for checks and locks. 1108-Kiju/Talk 12:26, 27 May 2023 (UTC)Reply[reply]

    Requests for (un)(b)locks[edit | edit source]

    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: 

    == <Username of user being locked> ==
{{status}}
*{{LockHide|username1|hidename=1}} <!-- include hidename=1 if you want to hide the username as it's offensive -->
*:Include your reason here ~~~~

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

    == <Username of user being locked> ==
{{status}}
*{{LockHide|username1|hidename=1}} <!-- include hidename=1 if you want to hide the username as it's offensive -->
*:Include your reason here ~~~~

    Erico[edit | edit source]

    {{status|done}}
*{{LockHide|Erico}} 
:I can't.--[[User:Erico|Erico]] ([[User talk:Erico|talk]]) 14:35, 27 May 2023 (UTC)

    Permissions[edit | edit source]

    Administrator/Bureaucrat access[edit | edit source]

    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@<subdomain>wiki ===
{{Permission request
 |status    = <!-- Do not remove this! -->
 |wiki      = <!-- Replace with subdomain of wiki -->
 |user name = <!-- Replace with username -->
 |discussion= <!-- Replace with link to discussion, if any -->
}}
Include any comments here ~~~~

    Corviraptor@ultrakillwiki[edit | edit source]

    Status:  Done

    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)Reply[reply]

    Clerically noted as Yes check.svg Done by Agent. --Raidarr (talk) 21:16, 7 May 2023 (UTC)Reply[reply]

    Artubass@celestewiki[edit | edit source]

    Status:  Not done

    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)Reply[reply]

    @Artubass: 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)Reply[reply]
    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)Reply[reply]
    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 X mark.svg Not done 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)Reply[reply]

    FrensonianPresident@frensonpediawiki[edit | edit source]

    Status:  Done

    I created Frensonpedia a while ago, forgot about it, and I was going to re-open the wiki when I noticed my bureaucrat status was removed, I just need it to be returned for me to edit normally. FrensonianPresident (talk) 00:46, 23 May 2023 (UTC)FrensonianpresidentReply[reply]

    @FrensonianPresident: Yes check.svg fixed. Rights do not appear to have assigned correctly initially. --Raidarr (talk) 23:00, 23 May 2023 (UTC)Reply[reply]

    Abe@liuvisionwiki[edit | edit source]

    Status:  In progress
    I would like to become Administrator and Bureaucrat since our previous one is missing due to personal reasons

    Other access[edit | edit source]

    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 <subdomain>wiki to global if requesting an IP block exemption): 

    === Username@<subdomain>wiki ===
{{Permission request
 |status    = <!-- Do not remove this! -->
 |wiki      = <!-- Replace with subdomain of wiki -->
 |user name = <!-- Replace with username -->
 |discussion= <!-- Replace with link to discussion, if any -->
}}
Include any comments here ~~~~

    Removal[edit | edit source]

    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 <subdomain>wiki to global if requesting a Steward remove your rights on all wikis or global rights): 

    === <username@wiki> ===
{{Permission request
 |status    = <!-- Do not remove this! -->
 |wiki      = <!-- subdomain of wiki -->
 |user name = <!-- user -->
 |discussion= <!-- Replace with link to discussion, if any -->
}}
Add additional comments here.

~~~~

    Lackbfun@erawiki[edit | edit source]

    Status:  Done

    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)Reply[reply]

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

    Lackbfun@erawikisourcewiki[edit | edit source]

    Status:  Done

    Per same reasons. Howard (talk) 14:26, 10 May 2023 (UTC)Reply[reply]

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

    Gauri@eswconrefwiki[edit | edit source]

    Status:  Done

    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)Reply[reply]

    SRuizR, can you link to your local community policy that permits this? Dmehus (talk) 03:48, 20 May 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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 Yes check.svg Done. --Raidarr (talk) 12:30, 20 May 2023 (UTC)Reply[reply]

    Wiki (un)deletion[edit | edit source]

    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: 

    == <Name of wiki> ==
{{SN wiki request
|status = <!-- do not remove this! -->
|request = deletion or undeletion 
|wiki    = <!-- subdomain of wiki -->
|reason = <!-- reason --> ~~~~
|discussion= <!-- link to discussion, if any -->
}}

    gianalbertochini[edit | edit source]

    Status:  Done
    • Requesting: deletion
    @Gianalberto.chini: Yes check.svg deleted. --Raidarr (talk) 18:51, 20 May 2023 (UTC)Reply[reply]

    Feign Wiki, Feign Developers Wiki, XYZ Wiki, Turkish Sivasvoyage Wiki, English Sivasvoyage Wiki[edit | edit source]

    Feign Wiki[edit | edit source]

    Status:  Done
    • Requesting: deletion
    • Reason(s): I don't need it anymore because the wiki is on another platform. LisafBia (talk) 12:22, 17 May 2023 (UTC)Reply[reply]
    In addition: There are also 4 wikis to close, see this page for information. Hey Türkiye Message? 11:42, 19 May 2023 (UTC)Reply[reply]
    New domain, please? --Routhwick (talk) 05:17, 19 May 2023 (UTC)Reply[reply]
    https://feign-wiki.tk @Routhwick Hey Türkiye Message? 11:42, 19 May 2023 (UTC)Reply[reply]
    @LisafBia and HeyTürkiye: wikis Yes check.svg removed as requested. --Raidarr (talk) 01:01, 21 May 2023 (UTC)Reply[reply]
    Response Response Thank you very much @Raidarr :) Hey Türkiye Message? 07:19, 21 May 2023 (UTC)Reply[reply]

    XYZ Wiki[edit | edit source]

    Status:  Done
    • Requesting: deletion

    Turkish Sivasvoyage[edit | edit source]

    Status:  Done
    • Requesting: deletion

    English Sivasvoyage[edit | edit source]

    Status:  Done
    • Requesting: deletion

    Feign Developers Wiki[edit | edit source]

    Status:  Done
    • Requesting: deletion

    A Young Girls Oral Surgery Trip[edit | edit source]

    Status:  Done
    • Requesting: deletion
    • Discussion: Private wiki creators' channel
    • Reason(s): After my approval of this wiki, several wiki creators expressed serious concerns about it, so it should probably be deleted pending more information from the requestor of this wiki. Tali64³ (talk) 04:13, 20 May 2023 (UTC)Reply[reply]
    Marked as Yes check.svg Done outside of the SN. --Raidarr (talk) 18:52, 20 May 2023 (UTC)Reply[reply]

    Dan Schneider Universe Wiki[edit | edit source]

    Status:  Done
    • Requesting: deletion
    @Loves Next & Misses Sandra: Yes check.svg deleted. --Raidarr (talk) 23:07, 23 May 2023 (UTC)Reply[reply]

    Ne te laisse plus faire ![edit | edit source]

    Status:  Not done
    • Requesting: deletion
    • Discussion: Please cancel my previous request. Everything is back into order on the sidebar and main page logic. Thanks a lot and sorry again.IlZdeba (talk) 20:43, 22 May 2023 (UTC)Reply[reply]
    • Reason(s): I am new to mediawiki and I completely screwed the sidebar and the main page logic. As the wiki is only one day old and as I am the only contributor and admin at this stage, it does not hold much content. So it will be easier to just delete this wiki and I will create another one, trying not to mistakenly change the title of the Main Page next time. Thanks and sorry for the hassle. IlZdeba (talk) 14:28, 22 May 2023 (UTC)Reply[reply]
    @IlZdeba:, to confirm, this deletion request is no longer needed and should be cancelled, rather than performed, yes? --NotAracham (talk • contribs • global) 03:30, 23 May 2023 (UTC)Reply[reply]
    @NotAracham:, exactly, deletion no longer needed (for the moment). Thanks a lot IlZdeba (talk) 16:58, 23 May 2023 (UTC)Reply[reply]

    Memestionary[edit | edit source]

    Status:  Done
    • Requesting: deletion
    @Bukkit: Yes check.svg deleted. --Raidarr (talk) 13:07, 25 May 2023 (UTC)Reply[reply]

    Wiki of the Rising Spaghett (spaghettwiki)[edit | edit source]

    Status:  Done
    @JaimieRichie: Yes check.svg deleted. --Raidarr (talk) 08:38, 29 May 2023 (UTC)Reply[reply]

    Марксисты Арцаха[edit | edit source]

    Status:  Done
    @NeoclassicVII: Yes check.svg deleted. --Raidarr (talk) 08:38, 29 May 2023 (UTC)Reply[reply]

    Free Editing Wiki[edit | edit source]

    Status:  Done
    • Requesting: deletion
    • Discussion: https://freeediting.miraheze.org/wiki/User_talk:Tali64³ (archived link for convenience)
    • Reason(s): Around three months ago, a Steward had warned me that this wiki was violating the Content Policy, particularly provisions 4 and 10; afterward, I made some efforts to bring the wiki into compliance with the Content Policy. Apparently they were not enough, since I received another warning three weeks later that the wiki would be closed in a week unless I changed its scope to be compliant with the Content Policy. At the time, I only saw two options for the wiki if I left it open: 1) properly clean up the wiki's scope to be fully compliant with the Content Policy, which would effectively make the wiki a clone of the Randomness Wiki; 2) do nothing and have the wiki shut down in a week. At that point, being stuck on two hard decisions I had to make and it having a good chance of being closed no matter what I did, I chose option 3: close the wiki myself right there. For some time, I left the topic there and focused on other projects; then, the solution to the scope problem hit me. Why not create a wiki focused exclusively on nonsensical humor, as a counterpart to Decyclopedia? Instead of porting Free Editing Wiki's content to the new wiki, however, I decided to start from scratch, though there is a page on that wiki that originated from Free Editing Wiki. However, the new wiki faced a couple of issues, namely that it rules were vague and that there was no definition for "nonsensical humor". I have now fixed these issues, adding a definition for nonsensical humor and copying most of the revised ruleset from Free Editing Wiki's rules. Therefore, I am asking for the deletion of Free Editing Wiki in favor of the new wiki, which is The Wiki for Nonsense and Absurdity. Tali64³ (talk) 20:00, 28 May 2023 (UTC)Reply[reply]
    @Tali64³: Yes check.svg deleted. --Raidarr (talk) 08:39, 29 May 2023 (UTC)Reply[reply]

    The Beagle Boys Wiki[edit | edit source]

    Status:  In progress

    Restricted setting change requests[edit | edit source]

    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: 

    == <Name of wiki> ==
{{SN wiki request
|status = <!-- Do not remove this! -->
|request = Enable <extension> or Change <restricted setting> 
|wiki    = <!-- subdomain of wiki -->
|reason = <!-- reason --> ~~~~
|discussion= <!-- link to discussion, if any -->
}}

    The Lion King Wiki[edit | edit source]

    Status:  Not done
    • Requesting: Dormancy Policy Exemption
    • Reason(s): Hi, can we please have our exemption back for our The Lion King Wiki? We've added three substantial pages (excluding a temporary to-do-list) and several templates for these pages and for future pages. It is a private wiki meant to be read so it won't ever have any editors besides the three of us (Keznen). Keznen (talk) 01:00, 17 May 2023 (UTC)Reply[reply]
    Pictogram voting comment.svg Comment: 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)Reply[reply]
    @Kenzen: 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.
    @Dmehus: 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)Reply[reply]

    Bapham123 Wiki - Việt Nam (lần 2)[edit | edit source]

    Status:  Done
    • Requesting: Enable Cargo
    • Reason(s): The Cargo extension allows you to manage structured data in your wiki and query that data to create dynamic representations: tables, timelines, maps, lists, and more. I find this utility very good for managing structured data and having a clear, coherent plan on the wiki. It will help with quick and planned data management for the admin, and also I plan to use another similar extension called Semantic MediaWiki but the wiki is enabling the Wikibase extensions, which Wikibase has a conflict with SMW that makes it impossible for me to enable the SMW extension, I will use the Cargo widget as an alternative to SMW. Please Miraheze help me enable this extension on my wiki. sincerely thank Bapham123 (talk) 12:33, 20 May 2023 (UTC)Reply[reply]
    @Bapham123: Yes check.svg enabled. --Raidarr (talk) 18:58, 20 May 2023 (UTC)Reply[reply]


    Looney Pyramids[edit | edit source]

    Status:  Done
    • Requesting: Enable Symantic MediaWiki
    • Reason(s): Our wiki uses Symantic MediaWiki for various data and searching. Several pages have content mostly generated by Semntic MediaWiki Ask queries. Do we need to enable Sematic before we import the old wiki? Dazeysan (talk) 15:10, 21 May 2023 (UTC)Reply[reply]
    Yes check.svg Done Agent Isai Talk to me! 14:37, 24 May 2023 (UTC)Reply[reply]

    Looks like it's working! Can you purge the cache on all of our pages so Semantic's data gets refreshed? If not, we can manually purge individual pages. Thank you! Dazeysan (talk) 16:35, 24 May 2023 (UTC)Reply[reply]

    heorotsdescent[edit | edit source]

    Status:  Done
    • Requesting: Enable Cargo
    • Reason(s): requires restricted approval
    @Ruchirshah: could you elaborate on why you need this extension enabled? --Raidarr (talk) 14:26, 25 May 2023 (UTC)Reply[reply]
    Sure. I’m trying to develop an open and collaborative story development tool, and would like to dynamically handle a subset of the pages as a developing knowledge base that can be queried and dynamically appended into the existing chapters based on Cargo queries. Can I check why there is a more stringent approach to Cargo here? I already have two active wikis on Miraheze with Cargo enabled and can’t see a security issue here?
    Yes check.svg Cargo is enabled. Regarding stringency: Overall, the use of Cargo is a potential performance risk and there are rare cases where it must be reviewed by SRE and if issues come up, refused or later disabled, so manual input/scrutiny for extensions in this category is desired. Outside those cases ("smaller wikis" in general which wouldn't be a performance risk) it is generally desired to have on record a) the request and b) a concise summary of use case for logging, something we try to have for all requests on the SN and related areas like RfRW. I apologize for the bureaucracy, it would have been simpler to go ahead given you've had successful requests and there were no red flags and just asked for a use summary rather than making it two-step this way. --Raidarr (talk) 17:38, 25 May 2023 (UTC)Reply[reply]
    No probs. Thanks for the clarification. Ruchirshah (talk) 18:45, 25 May 2023 (UTC)Reply[reply]

    offenelegende[edit | edit source]

    Status:  Done
    • Requesting: Enable Cargo
    • Reason(s): Being able to use dynamic queries would be extremely helpful for linking abilities to the attributes they depend on and similar use cases. Kempeth (talk) 19:21, 23 May 2023 (UTC)Reply[reply]
    @Kempeth: Yes check.svg enabled. --Raidarr (talk) 14:22, 25 May 2023 (UTC)Reply[reply]

    2EM[edit | edit source]

    Status:  In progress
    • Requesting: Enable Cargo
    • Reason(s): This is a restoration of an older wiki which had become inactive. The original wiki had cargo, so I need to activate it before I import the archive from waybackmachine. Cargo was used to database and facilitate management of knowledge resources.

    Wiki reports[edit | edit source]

    Instructions/Read before making a request 

    Use this section to report wikis which are in violation of our global policies, such as the Content Policy. When reporting a wiki, please make sure to include lots of details, links to infringing pages, and more. If the matter is sensitive, please report this via email to stewards(at)miraheze.org

    You may edit this section and place your report at the bottom of it.

    Cloned wiki[edit | edit source]

    It has come to my attention that tokyomewmewpower is a direct copy of a fandom wiki with the same name. The user who created the Miraheze wiki has been copy-pasting information directly from the fandom wiki with some minor changes and no attribution. This person has previously gotten in trouble for the exact same thing, having opened multiple cloned wikis on Fandom, all of which were closed due to flagrant copying.--RoyalMinty (talk) 08:20, 24 May 2023 (UTC)Reply[reply]

    Discussion closure[edit | edit source]

    Instructions/Read before making a request 

    Please use this section to request a Steward close a local discussion. This may be in cases of local elections on wikis without bureaucrats, on wikis where local bureaucrats also voted thus needing a third-party to close, on wikis where the bureaucrat is inactive or unwilling to close a discussion, etc.

    Miscellaneous[edit | edit source]

    Instructions/Read before making a request 

    If your request doesn't fall under any of these categories, you can add your request or question here.

    I deleted the “everyone” group and now I can’t access certain things.[edit | edit source]

    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)Reply[reply]

    @Bauerbach: Would you like us to reset all usergroups to their default version? Reception123 (talk) (C) 18:30, 18 May 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    All groups reset to default settings. Reception123 (talk) (C) 16:46, 19 May 2023 (UTC)Reply[reply]
    Retrieved from "https://meta.miraheze.org/w/index.php?title=Stewards%27_noticeboard&oldid=336933"