Stewards' noticeboard

在worldbox.wiki中禁用matomo页面
Close Disable matomo pages in worldbox.wiki Due to the well-known political reasons in mainland China, I was worried that part of the matomo interface‘s “country”.would cause trouble, so I decided to disable it, thank you. Isutan (talk) 02:52, 6 May 2022 (UTC)


 * Maybe it is only me that unfortunately does not understand what this thread is trying to request but could you please try to rephrase so that it can be better understood? I am certain that you are using an automatic translation program but it is difficult to determine what you wish to convey here. DeeM28 (talk) 07:39, 6 May 2022 (UTC)
 * From what I understand you think Matomo's geographic tracking (seeing who comes from what country) is a problem in China for your wiki.
 * I'm not sure parts of Matomo can be shut down like that, and it will take a more technical eye/someone from SRE to see how plausible this is. --Raidarr (talk) 08:24, 6 May 2022 (UTC)
 * Hi. So far we've not disabled or excluded any wiki from Matomo. What kind of issues are being encountered with users from mainland China? Is Matomo being blocked and causing issues for users when accessing your wiki? I don't think a prospective worry about Matomo would be enough to have it disabled. Reception123 (talk) ( C ) 09:32, 6 May 2022 (UTC)
 * TW and Hongkong SAR As China laws is violate，They are not country. Isutan (talk) 03:19, 9 May 2022 (UTC)
 * Isutan, can you clarify this a bit? That being said, I believe that you can opt out of Matomo analytics tracking, by adding the  user right to either of the (a)   (all users) or   (registered users) user groups. If that doesn't work for your purposes, can you clarify what you mean? If you're concerned that Taiwan and Hong Kong Special Administrative Region could be used by Chinese government agencies to track Miraheze user information to narrowly, even in an aggregate sense, I wouldn't be opposed to asking our SRE volunteer team to group users within mainland China, Taiwan, Hong Kong SAR, Macau, etc. as simply "Asia," to provide for even greater anonymity. There's little value in us keeping country-specific visitor data anyway. Dmehus (talk) 04:20, 9 May 2022 (UTC)
 * The issue here seems to be essentially 'recognition' of Taiwan and Hong Kong as countries by the analytics, a significant political no-no in the mainland. I'm personally unwilling to make significant change to appease this policy, but if merging to a general 'asia' section especially as an opted in thing is an option then I'm in favor of seeing it done. --Raidarr (talk) 08:58, 9 May 2022 (UTC)
 * Yes, merge them into "China", don't say it's the People's Republic of China or delete the country column, which ensures Miraheze's political neutrality. Also, please do it quickly, the number of my wiki visitors is constantly increasing, if anyone finds out, I will be reported, I will “die socially”, and maybe I will be forcibly withdrawn from the world box player community in mainland China Isutan (talk) 06:46, 11 May 2022 (UTC)
 * @Dmehus@Raidarr@John@Agent Isai Isutan (talk) 06:48, 11 May 2022 (UTC)
 * Hello, although I am not a steward, I think this may take a little time for them to change this globally. In the mean time, if you want to get rid of the matomo analytics for all users, since you are bureaucrat, you can select (everyone) in here at the first column and submit by the blue button, then tick the noanalytics box from unassigned permissions. This way, no logs will be visible from Special:Analytics in your local wiki. —Matttest (talk) 13:40, 11 May 2022 (UTC)
 * @Dmehus@Raidarr@John@Agent Isai@Reception123@Universal Omega Isutan (talk) 02:09, 16 May 2022 (UTC)
 * This issue sounds quite complex. I would advise following Dmehus' advice to disable Matomo statistics. Agent Isai  Talk to me! 02:11, 16 May 2022 (UTC)
 * Then just delete it Isutan (talk) 00:04, 17 May 2022 (UTC)
 * We will not be doing that, apologies. Agent Isai  Talk to me! 05:06, 17 May 2022 (UTC)
 * As far as what I can see, he have done that managewiki change after me and Dmehus's guideline. Isutan, if you want to change it globally, it would certainly need more discussion and engagement from other users, thank you for your acknowledgement. -Matttest (talk) 05:41, 17 May 2022 (UTC)
 * @Agent Isai@Dmehus@Agent Isai@Reception123 Isutan (talk) 00:50, 29 May 2022 (UTC)
 * Hello, please do not ping several people without something attached - there's not much here to reply to, and if you want to see a platform wide change/removal of Matomo beyond the options noted above, it will at least take a successful request for comment. --Raidarr (talk) 01:21, 29 May 2022 (UTC)
 * My suggestion is to replace "country" with "country and region", and to replace the Greater China region with "Mainland China", "Hong Kong, China", "Macau, China", "Taiwan" or "Taiwan, China".And not to appear country names such as " People's Republic of China" or "Republic of China". 城市酸儒文人挖坑 (talk) 09:13, 7 June 2022 (UTC)
 * I will suggest replacing political states’ name into a common geographical name. To go into details, it will be great to make “country” into “countries and regions”, using geographical names like “Mainland China”, “Hong Kong”, “Macau”, and “Taiwan” (already set). Another proposal is to replace the countries and regions mentioned above, along with Japan and Korea, with “East Asia”. Cheers, Matttest (talk | contribs) 12:46, 9 June 2022 (UTC)
 * oh.ping @Agent Isai@Dmehus@Reception123. Isutan (talk) 01:31, 16 June 2022 (UTC)
 * As Raidarr said, please stop pinging multiple people. As for Matomo, that is up to the upstream developers and there's nothing we can do about it. Furthermore, we will not be getting into controversial political issues such as the ones you mention. Reception123 (talk) ( C ) 05:16, 16 June 2022 (UTC)

Extension request: Semantic MediaWiki
As a long-time advocate of this extension (thanks to the now-dormant Referata farm), I have finally decided to give Semantic MediaWiki a go for at least two other reasons:
 * Wiki ID: constantnoble
 * Encouragement from similar proposals by and ; and
 * Hope that this may resolve a slew of ongoing infrastructural issues/deficiencies across the Tovasala Dictionary on my creative-venture wiki, especially as far as the component (in entries for "S"- and "T"-initial Tovasala terms) is concerned; details at T8866. (Miraheze's long-time hesitancy over SMW led me to adopt The Next Best ThingTM, DPL3, days after said wiki's relaunch.)

And while you're at it, /
 * Semantic Result Formats, which Referata also used, may soon be a valuable add-on.
 * If SMW's implementation benefits well enough, then we might give RegexFunctions a second chance (provided I'm careful enough not to send the affected entry range into a loop again; RgxF is currently disabled thanks to the chaos documented at T8866). Attempts with Scribunto/Lua substitution have not gone any better, and 's Unicode support leaves a handful to be desired...

The sooner it arrives, the sooner I'll get to importing/spinning off select property pages from my Referata archives--and I know just where to start ("Unaccented headword"/"Unaccented morpheme name")...

P.S. Before you ask, I'm aware it's an experiment offered by request.

P.P.S. Extension:Score, which never really took off on Miraheze (T5863), is another must-have on my wishlist (as a fledgling composer)--but that's for another filing. Routhwick (talk) 23:30, 12 May 2022 (UTC)
 * With assistance from for the script, SMW is now locally ✅. Please report back if there are any technical issues arising from the enabling. --Raidarr (talk) 11:49, 14 May 2022 (UTC)
 * The ability to edit may not be affected, but that tricky "upgrade key" message (a familiar sight on the SMW Betaheze earlier this year) comes with the (new) territory, and a few JS bits may be loading on and off as a consequence. How soon before it settles down completely or for the most part?
 * P.S. Anyone care to tell me more about those three "humming bars" on the top right of a page? --Routhwick (talk) 15:22, 14 May 2022 (UTC)
 * cc for support in troubleshooting - I enabled SMW, Rhinos ran the script and the upgrade key issue was a result (easily duplicated for me by trying to check the log entries where I enabled SMW through recent changes). This issue is a bit out of my depth. --Raidarr (talk) 12:43, 15 May 2022 (UTC)
 * I have now fixed this. Universal Omega (talk) 20:41, 15 May 2022 (UTC)
 * Although SMW is already enabled, it's unable to detect the custom namespaces on my wiki at this writing. The official SMW site shows how to rectify this via $smwgNamespacesWithSemanticLinks; as it stands, we'll start out in the Entry, Morpheme, and Character areas. Baby steps, as they say... --Routhwick (talk) 01:50, 16 May 2022 (UTC)
 * To /// Bumping so that this issue doesn't get lost in the shuffle. (Also requesting semantics in the Template, Place, Grammar, Corpus, and Backstory namespaces on my wiki.) --Routhwick (talk) 01:43, 22 May 2022 (UTC)
 * If I dont end up getting to it within the next day or two, you could create a task on Phabricator in order to request that configuration, and someone should get to it. Which may be a bit faster for configuration requests. But regardless, I'll see if I can get to adding it to ManageWiki tomorrow. Universal Omega (talk) 01:50, 22 May 2022 (UTC)
 * If it's not been addressed per UO's message here, I do encourage making a task if you haven't already since enough time has passed. --Raidarr (talk) 12:51, 29 May 2022 (UTC)
 * Already filed. --Routhwick (talk) 14:42, 29 May 2022 (UTC)
 * With followup at T9341. --Routhwick (talk) 23:09, 11 June 2022 (UTC)
 * Unfortunately this has long dipped from my field of experience outside of just turning it on. Other than that I'm not really familiar with SMW, or its consequences interacting with other features. --Raidarr (talk) 12:20, 22 May 2022 (UTC)
 * Routhwick, thanks for ping. Unfortunately, as with Raidarr, this is not my area of expertise. I'm okay with enabling the extension, which it is, but the configuration changes are best done by Universal Omega in the next week or so. Please remember we're all volunteers here, juggling many priorities. Dmehus (talk) 04:01, 24 May 2022 (UTC)

Hoping to become an administrator in CountryHumans Wiki.
It seems like most of the administrators on the CH wiki are inactive. Ever since the wiki shutdown on FANDOM, I'am hoping to become one of the administrators on the miraheze wiki of CountryHumans. I'am planning to make the wiki a bit better, by adding a logo, changing the background color, etc, as well as restoring some images. If I cannot become an administrator, that's okay. Just wanna make the wiki more better. Thanks. ForestWolffey (talk) 17:32, 22 May 2022 (UTC)


 * In order to become an administrator (and bureaucrat it seems as you want to change ManageWiki settings like logo and such), you must hold a local election first in which users of the wiki vote for you to become an administrator and bureaucrat. If no one opposes then you can win by acclamation and become a local administrator and bureaucrat. Agent Isai  Talk to me! 17:35, 22 May 2022 (UTC)
 * For a detailed description see here, an essay written by a Steward. After the election, you can show stewards your election on your wiki at Stewards' noticeboard (here, with a new thread), and administrator and bureaucrat permissions may be added to your account at that time.--Matttest (talk) 09:10, 23 May 2022 (UTC)
 * Thank you, sorry for the late reply. I will try doing this. ForestWolffey (talk) 21:14, 5 June 2022 (UTC)

Requesting a few dormancy policy exemptions
Hi, so I edit several video game-related wikis on Miraheze, along with DarkMatterMan (many of them within the unofficial brand of Miraheze Gaming Services), kind of like how Qualitipedia has become a brand of its own on Miraheze. It says I can request a few exemptions to the Dormancy Policy, so I'll list the few that I requested via Special:RequestWiki. I do my best to keep an eye on these wikis, but I feel exemptions to the dormancy policy -- better to be on the safe side of things (from what I remember, there was a bug that caused some wikis to be closed from inactivity around the time Miraheze upgraded its data centers). Here's the wikis:
 * https://thenintendowiki.org/
 * https://smashbroswiki.com/
 * https://pokemonwiki.info/
 * https://dragonquestwiki.com/
 * https://crocwiki.com/ (Miraheze Gaming Services mascot)

If (who founded these via Special:RequestWiki) is ok with it, I could also request the following to be exempt form the dormancy policy:


 * https://kirby.miraheze.org/
 * https://metroid.miraheze.org/
 * https://squareenixwiki.com/
 * https://luigismansion.miraheze.org/
 * https://wiisports.miraheze.org/ Bawitdaba (talk) 13:32, 3 June 2022 (UTC)
 * The wikis have been very active as of lately, so unless if the wikis suddenly stopped receiving edits, it looks fine just the way it is for now. DarkMatterMan4500 (talk) (contribs) 19:12, 3 June 2022 (UTC)
 * Luigi's Mansion and Wii Sports are two of the lesser active ones as far as I know. I suppose there is a point that if they active, wouldn't have to add them in. The first five above I still have as part of the request. I think MGS could become one of the go-to's of Miraheze, hence why I've connected it to the idea of dormancy policy exemption. Perhaps not in the same capacity as Qualitipedia but still one nonetheless. Bawitdaba (talk) 19:26, 3 June 2022 (UTC)
 * The issue here I feel is that DP exemptions are for a limited set of scenarios typically including (in summary) high content, low editing traffic or need for traffic due to being complete, and a clear audience. If you keep your eye on the wikis I think you've already illustrated that a DP isn't exactly necessary, unless you'd consider the wikis more complete - they don't seem to be even if they all have something at least. If MGS becomes a go-to it will sustain its own activity in editing (or perhaps grow into a true need for exemption), while I think there may be a misunderstanding here and it's not needed. The recent changes bug was highly unusual and unlikely to occur again, and was easy to fix especially on wikis with anyone checking + did not cause any imminent data loss.
 * If you disagree with this and think they're closer to what I describe since this opinion is not backed with an in-depth review and is just a cautionary statement, I can go ahead and review the wikis individually (at least from the initial list). --Raidarr (talk) 20:00, 3 June 2022 (UTC)
 * It should be fine, thank you. You made a good point that the activity sustains itself. If you were to review any, I think Croc Wiki is the only one that comes to mind seeing as Croc has been an inactive game franchise for over 20 years yet it has some historical significance because it branched off from Yoshi during Argonaut's tenure with Nintendo in SNES days. Bawitdaba (talk) 20:09, 3 June 2022 (UTC)
 * yet I think it stands out as a nice mascot nonetheless. so i guess for an inactive game franchise (Croc Wiki, I'm saying) would make more sense to have look into the Dormancy Policy, as the other urls listed above cover stuff that is very active. Bawitdaba (talk) 20:40, 3 June 2022 (UTC)
 * Okay, restored conversation from archive + finally able to put a proper answer to this. As elaborated and agreed the exemptions aren't necessary to dive into for any case except Croc Wiki, which I've gone ahead and looked into. There are a few troubles there which make me reluctant to accept. One is that rather like the other wikis, it's been maintaining solid enough activity (minimal edits which continuously reset the expiration timer). It appears to have little traffic and the MGS coordination status doesn't really do anything to boost this. Content wise I plucked 6 pages linked from around the main page and they're all substantively imported from Fandom with the only significant changes being formatting to fit in. So I find it difficult to find a substantive reason to exempt it either, I'm afraid. --Raidarr (talk) 19:07, 18 June 2022 (UTC)

Enable Semantic MediaWiki extension on alicesoft.miraheze.org
https://alicesoft.miraheze.org/wiki/AliceSoft_Wiki:Main_Page

Hello.

The Alicesoft wiki migrated to Miraheze from its original host at Fandom. As such, several of its most staple features, such as the Game (https://alicesoft.miraheze.org/wiki/Template:Game) and Character (https://alicesoft.miraheze.org/wiki/Template:Character) templates make use of the extensions "Semantic MediaWiki" and "Semantic Drilldown" and are not completely functional if they are not enabled. To improve site functionality, we would like to request permission to use the Semantic MediaWiki extension.

Thank you for your time. Alto the Reaper (talk) 01:05, 4 June 2022 (UTC)


 * ✅ with support from . Please note that our implementation of SMW is experimental and still on a trial basis. Feel free to follow up with any inquiries including reports of unusual errors or issues through Phabricator. --Raidarr (talk) 22:15, 4 June 2022 (UTC)

Request for reopening Retro Windows Wiki
I come back wanting to edit the wiki only to find it closed, and I'm upset about it.

The admin manually closed it without giving a good reason. Closing the wiki, making it eligible to be deleted after 6 months, does not seem to be a good way of just "taking a break" (as stated on mh:retrowindows:User:Xack).

If Xack is unwilling to keep being the sysop and/or admin of the wiki, I can take over. But if I do take over I might have to request exemption from inactivity, because this wiki would mainly be read, and it would not be necessary to frequently add content to it. Jack980517 (talk) 07:47, 4 June 2022 (UTC)


 * Hi Jack980517, per this diff at his global user page, I believe that he have decided to retire from miraheze and intended to allow other users to adopt it. In my opinion, I guess you can request it at Requests for reopening wikis to adopt it since the creator will certainly not editing it again and there is nothing different from leaving it to inactivity . Pinging Dmehus (a steward) for a better judgement on this case. Cheers, Matttest (talk) 08:12, 4 June 2022 (UTC)
 * Understood. If Dmehus doesn't reply tomorrow (24h later) I'll go to Requests for reopening wikis. Jack980517 (talk) 09:26, 4 June 2022 (UTC)
 * Well, sorry if my comments make any confusion. That means, I think it would be better for steward to review this case, since Requests for reopening wikis is only for wikis that is closed due to inactivity. I do believe that you are eligible to adopt this wiki, though, since the original bureaucrat is retired. Cheers, Matttest (talk | contribs) 09:38, 4 June 2022 (UTC)
 * IMO you should have stated that you aren't a steward before offering suggestions, or "guesses". An outside observer (someone not familiar with the staff list of Miraheze) wouldn't know that from a glance. Users posting here expect authoritative answers from actual stewards, not someone who have no say on the site's policies. Jack980517 (talk) 10:20, 4 June 2022 (UTC)
 * I am helping the issue by pointing out the fact that the original bureaucrat of the wiki is retired, since other stewards isn’t here. Please note that everyone (not only stewards) can use miraheze’s site policies for reference, and suggestions are not vested only in stewards side. I do admit that I should say “although I am not a steward” before giving advice here with the fact that it is stewards’ noticeboard here, and so sorry for confusion. Cheers, Matttest (talk | contribs) 10:47, 4 June 2022 (UTC)
 * Steward's input here. Matt raised an interesting point re the main operator's global userpage making an open invitation to 'adopt' wikis. It's an unusual and inadvisable practice to just close a wiki if you're bored, especially if you leave a fairly clear out like that and provide no proper reason for closure when other users are interested and/or present. Iirc he'd already pointed a few more shut down wikis at the retro windows domain and the wiki's scope is quite broad and non-personal in nature. In light of these circumstances I have gone ahead and ✅ the wiki, treating this as a valid reopen request that is skirting the line where manual closure would usually be a dent in reopening. It's not an exception made often or lightly, but I believe it holds merit here all things considered.
 * We don't take issue with users responding to inquiries as long as they are accurate, which I can confirm has been pretty much the case so far (though some interpretation was needed here, that needs to be careful). Alas, part of this is because our team is limited in both numbers and time, and anyone who can volunteer to make things easier in the meantime is encouraged to do so. I do concur that making 'not a steward' evident from the start is best. --Raidarr (talk) 22:06, 4 June 2022 (UTC)
 * Thank you. According to the site notice that you wrote, I would need to go through the local election process to become sysop, and only then can I request exemption from inactivity. Is that correct? Jack980517 (talk) 00:12, 5 June 2022 (UTC)
 * A local election is best yes; while I used Xack's edit as a rationale to reopen, they are not clear enough to me to bypass the standard LE a Steward uses when transfer of power/wiki authority is unclear. As for exemption yes, you would need to become 'the operator' (bureaucrat/sysop) to request, but to be frank the wiki in its current state I would not approve to exempt due to limited, highly stub-like content and not clearly fitting other interpretations an exemption is used for. --Raidarr (talk) 15:21, 5 June 2022 (UTC)

The time I stated for the local election has passed and no meaningful discussion has taken place. Please make me sysop and admin, thank you. --Jack980517 (talk) 00:24, 10 June 2022 (UTC)


 * Planning to finalize this tomorrow. --Raidarr (talk) 00:47, 10 June 2022 (UTC)

Request for locking
Could you lock the account ? This is my impersonation.Thank you. by Buel ·Talk·Wikimail 23:11, 4 June 2022 (UTC)
 * Hello looking into this I see clear confirmation from your account that Rigany is  you, but Rigany's edits and CentralAuth are... confusing. To clarify, is this an account operated by you (if so an edit by Rigany to confirm here would be best), or an unknown user impersonating you? Apologies for the confusion. --Raidarr (talk) 15:18, 5 June 2022 (UTC)
 * Buel, I concur with Raidarr here. Please provide a confirmation edit from Rigany if this is indeed a self-requested lock of your alternate account. Thank you. Dmehus (talk) 05:31, 6 June 2022 (UTC)
 * @Raidarr Dmehus,Thank you for replying."Rigany" is not mine.This is an impersonation of an unknown user. by Buel ·Talk·Wikimail 07:37, 6 June 2022 (UTC)
 * Note to steward: The account Rigany seems to be the username that Buel had used before renaming, see User talk:Buel which may help as reference. Cheers, Matttest (talk | contribs) 07:55, 6 June 2022 (UTC)
 * understood. ✅ for local impersonation as a notable admin. 's observation is confirmed by the global rename queue, a fairly recent rename at that. --Raidarr (talk) 08:58, 7 June 2022 (UTC)
 * I'm sorry for the unfamiliar and incomprehensible English. Thank you very much. by Buel ·Talk·Wikimail 12:06, 7 June 2022 (UTC)
 * not an issue, I simply misunderstood the situation. Best of luck. --Raidarr (talk) 14:49, 7 June 2022 (UTC)

Hi, can you undelete wiki page: "wikimotor"? Thanks.
Hi, can you undelete wiki page: "wikimotor"? Thanks. Bondiee (talk) 14:37, 5 June 2022 (UTC)
 * ✅. --Raidarr (talk) 15:22, 5 June 2022 (UTC)

Delete dynguwiki
Requested here and here. Naleksuh (talk) 23:16, 6 June 2022 (UTC)
 * I think a better possible method to change the sitename with all the original contents there will be, request for a subdomain change at phabricator. You can ask stewards' to delete the wiki you recently requested to make room for that subdomain change. Then, you can open a new ticket at phabricator to change the sitename to the subdomain you prefer. Hope that helps. Cheers, Matttest (talk | contribs) 23:50, 6 June 2022 (UTC)
 * While I considered mentioning that in the request, the log entry and closing the wiki makes it clear that the goal is to delete it. If Yoshimidsu changes their mind they are welcome to reopen it. Naleksuh (talk) 23:54, 6 June 2022 (UTC)
 * I may have misunderstood the request in the first place. While a phabricator based rename would be more elegant, the new name is already approved and the will on the original wiki is clear. It's ✅. --Raidarr (talk) 08:53, 7 June 2022 (UTC)

Request for checkuser
Could you check long-term abuse's IP adsress out on Ysmwiki? See also block log for more information.Thank you. by Buel ·Talk·Wikimail 10:38, 8 June 2022 (UTC)
 * Due to privacy concerns per the Privacy policy, IPs cannot be fished or be linked to any accounts unless it's the other way around. I've been keeping track of how many IPs have been targeting that specific wiki, and I can re-assure you that even, , and other users are aware of this catastrophe as much as I am. DarkMatterMan4500 (talk) (contribs) 11:22, 9 June 2022 (UTC)
 * I am not opposed to checking offending IPs for account creations or accounts for IPs pertaining to other creations if they pertain to globally recognized long term abuse. The global recognition is the key. I have little context to an awfully huge range of blocks listed in your block log. It would instead be better to identify recent priority targets associated with behavior which accounts have been globally locked for either across wikis or locked due to their LTA behavior locally, which I/another steward can look into and decide if it is worth checking for connections. Suspicion of alt abuse should be accompanied with specific reasons to assume it is a 'repeat customer', and not just run of the mill vandalism. So I'm afraid just linking the block log does not qualify for me to CU here. What I can do is globally block proxies from registration if you've addressed them locally and they are not globally blocked. --Raidarr (talk) 14:55, 9 June 2022 (UTC)
 * This LTA is cross wiki abuse.special:centralauth/アラスのだいすき!1 vandalismed globally. by Buel ·Talk·Wikimail 11:58, 13 June 2022 (UTC)
 * ✅, precisely the example I needed. In addition to crosswiki abuse it directly resembled the last impersonation issue and a cursory check exposed several related accounts. It does seem to overwhelmingly prioritize local abuse, perhaps filters can be considered locally. Alas, creating filters is not my specialty, but perhaps I can point someone towards this to see what can be done. Unfortunately in this case the background was a notable telecom provider, with no apparent proxies to snub out. But this doesn't preclude a more thorough check from a colleague (Steward). Note that DarkMatterMan is just an interested volunteer and does not have the ability to check users or action accounts. --Raidarr (talk) 12:25, 13 June 2022 (UTC)
 * I've been on that particular LTA's trail for about a few months now, and I've been blocking the IP ranges on the ysmwiki. I've also attempted to modify one of the abuse filters so the disruptive account names can be stopped, causing the IPs behind it to get blocked instantly. DarkMatterMan4500 (talk) (contribs) 12:44, 13 June 2022 (UTC)
 * I understood.Thank you very much. by Buel ·Talk·Wikimail 08:35, 14 June 2022 (UTC)

Lock Request
Please lock my account. I decided I don't need it any more. Thanks. --PokeFan19 (talk) 16:57, 9 June 2022 (UTC)


 * @PokeFan19 Since you created your account less than two hours ago, I must ask whether you are sure that you no longer want it? If you change your mind a few hours later, we can't keep unlocking and locking your account. Reception123 (talk) ( C ) 17:20, 9 June 2022 (UTC)

I am sure. I don't think I'll change my mind about it either, but thanks for checking. --PokeFan19 (talk) 17:30, 9 June 2022 (UTC)


 * @PokeFan19 I understand. By chance, I wanted to ask whether you've had other Miraheze accounts in the past. Reception123 (talk) ( C ) 17:31, 9 June 2022 (UTC)

Yes. But I'm not comfortable disclosing my other account name. I had made this account to use at a local wiki where I'm blocked, but then I realized that that would only make things worse for myself. If I want to edit anything here I'll use my other account. And I won't make any more side accounts either. PokeFan19 (talk) 17:39, 9 June 2022 (UTC)
 * /, this is ✅. Please take into account my advisory regarding this issue and the wider context it pertains to. --Raidarr (talk) 18:18, 9 June 2022 (UTC)

Proxy blocking
I would like to move forward on proxy blocking both so that SRE can have their excuse to remove reCAPTCHA by stopping spam, and because proxies and VPNs are currently being used for block evasion.

This simply involves generating a list of Wikimedia blocked proxies and applying them, if it is agreed upon. I made a list back in February Special:Diff/237372 but it's gotten outdated since then, and Reception123 has asked how people can verify it is accurate.

Do any Stewards object? User:John User:Void User:Raidarr Naleksuh (talk) 23:01, 9 June 2022 (UTC)


 * I wouldn't feel comfortable with this as Wikimedia's global block list also includes other IPs that were blocked for reasons that are not within our global policies (e.g. T-Mobile IPs, etc) and would also need to be maintained constantly which may be a burden to whoever is in charge of that. If anything, I would potentially support deploying StopForumSpam globally (something being considered by WMF) and seeing if we can use that to block all open proxies and web hosts. Agent Isai  Talk to me! 23:25, 9 June 2022 (UTC)
 * I have been considering building a tool for this sort of thing. It would ideally allow for some sort of oversight when importing blocks, but would also allow for gathering other lists of ranges through other means (such as ASN lookups). I would prefer to make this tool something with a web interface, but it may be more realistic for me (with my skills) to build a standalone application. In the meantime, as building such a tool is simply not going to happen very quickly, I think I'll build a Quarry query to compile the list (this makes it easier for others to use it themselves). -- Void  Whispers 23:48, 9 June 2022 (UTC)
 * To clarify, I already built a tool, see the linked diff. Though there's no harm in multiple if you want to make your own as one of the people who can do the blocking. Naleksuh (talk) 00:10, 10 June 2022 (UTC)
 * I've seen the diff, but you don't mention there how the list was generated. In either case, I've created Query 65222 and Query 65223 for global and enwiki proxy blocks respectively. -- Void  Whispers 00:52, 10 June 2022 (UTC)
 * It looks like that list doesn't have more recent blocks. I think it's using a really old snapshot of the database. For me, I simply rapidly used the API to get a live copy. Naleksuh (talk) 07:10, 10 June 2022 (UTC)

Requests for Comment/Replace reCAPTCHA with another CAPTCHA 2
Please reopen this.
 * 1) There was an actively ongoing discussion about proxy ranges that I returned to this page to continue when I saw it had been closed.
 * 2) Dmehus closed the last reCAPTCHA RfC, if and when it is time to be closed it should be closed by someone else
 * 3) Several closures by this user have been overturned recently (for example on test.miraheze.org community ban discussion)
 * 4) Close does not accurately reflect the discussion, for example the closer said that reCAPTCHA 2.0 is one of the possible solutions even though it was never mentioned in the discussion (also doesn't solve the reCAPTCHA problem, but that would be content for discussion)
 * This is a continued pattern of supervotes by Dmehus that has been going on for a while now

Based on all of the above, I would like this RfC reopened so that discussion on proxy blocking can continue. Naleksuh (talk) 22:49, 9 June 2022 (UTC)
 * Actually this was a global RfC so it is a Steward thing, but I'm not going to move it now. Naleksuh (talk) 22:56, 9 June 2022 (UTC)
 * I have moved this to the Stewards' noticeboard where it is now in scope. Agent Isai  Talk to me! 04:26, 10 June 2022 (UTC)
 * I agree with Naleksuh, the discussion is keep going active on the issue related to proxy blocks. Please reopen the discussion. Cheers, Matttest (talk | contribs) 10:16, 10 June 2022 (UTC)
 * We should instead use SimpleCaptcha (math operation, MediaWiki default), FancyCaptcha (words in an image, used on Wikimedia wikis), MathCaptcha (math operation in an image) or QuestyCaptcha (answer to a question set in ) Cigaryno66331 (talk) 09:39, 14 June 2022 (UTC)
 * Hey, sorry for catching up a little late. I asked around a little and ultimately I would say it's best that this discussion is closed, but for a less formal discussion to be put up and stay open. This could be on its own page (perhaps the talk of the closed RfC, developing materiel that can be voted again for more conclusive results) or via Community noticeboard (the default, but it could get a bit clogged by surrounding entries).
 * The main problem is that this wasn't on its way to consensus at all (and so I do disagree strongly with the conclusiveness shown in its closure), and ideas wise it's simply not ready to go the full distance. I think we should get a few more things worked out, for example I'm partially waiting to see what Void has for dealing with proxies and presenting a more thorough proposal than what was linked. I'd like to improve how we tell people to request accounts account by email; I've received feedback that the wording of how we block proxies can be unclear in translation, so that's something I'd like to explore to assist Chinese concerns (among other regions). Chinese incentives in particular can only be helped so far by a captcha change (which SRE is already looking into to help them out). A lot of their issue is not being able to register either way because they need to come from proxies. Once we have progress there will be a stronger base to change from and get consensus for, otherwise just reopening now invites a cycle of indecisive repeats of the same arguments to little end.
 * Another issue is that this entirely falls to the discretion and availability of SRE. I've talked to several including a steward-sre member and the answer is universally 'we have this on the list but until more gets done/we have more volunteers this can't be priority'. So what we have is an RfC that is almost impossible to enact which has now repeatedly shown difficulties getting a decisive majority that could compel SRE to change this.
 * I agree the closure was abrupt, the closing statements contained inaccuracies and the discussion should continue, but I don't think it will get any farther as a proper RfC and I don't see reason to overturn the closure itself in light of the above. I'm open to additional inputs and perhaps soliciting another Steward's response if this one is inadequate, but I don't expect this will change. --Raidarr (talk) 15:40, 16 June 2022 (UTC)
 * With regard to your second point, I don't see why a Steward, having previously closed a similar RfC, should be precluded from closing a subsequent RfC. With regard to the first point, I'm open to reopening the third proposal, though I would note that we have no open proxies policy. Requests for Comment is designed to initiate clear policy amendment proposals. What Proposal 3 is a community discussion without a clear policy proposal that can be enforced, so I would rather suggest it be moved to community noticeboard to further discuss how to formulate this into a clear policy proposal, or set of alternate proposals, that are enforceable. With regard to the fourth point, that is not a supervote, as you as mention. That is me just suggesting one possible option which could explored through a subsequent RfC, community discussion, or discussion with SRE. I'm happy to clarify that. Dmehus (talk) 00:34, 20 June 2022 (UTC)
 * That is me just suggesting one possible option If you have something like that to say, comment. It is not what closures are for, especially when indicating discussion. Naleksuh (talk) 00:46, 20 June 2022 (UTC)
 * Though another steward did not believe the closure should be overturned, as I do believe there is consensus from those participating in this discussion that the current configuration for reCAPTCHA 2.0 is a problem and there was no consensus for the first two proposals, with the third proposal already being policy and not being clear how it would be enforced, I've nonetheless ✅ this discussion, with the hope that there will become clearer consensus (in either direction) for either Proposal 1 or Proposal 2 or that Proposal 3 may spawn a subsequent proposal that aims to clarify what is unclear. Dmehus (talk) 01:19, 20 June 2022 (UTC)
 * This issue was not invoked specifically but in my opinion it is not improper to close an RfC early on if the topic of the RfC was discussed very recently before and the outcome is tending towards negative. It is of course important to allow the community to express itself and have as much time as is required to discuss but if the same or similar RfC is attempted multiple times there does not seem to be much sense to rehashing the same topics and same arguments for extended periods of times. If this RfC fails to garner enough votes I suggest that a break of a few months is taken before attempting it again so as it does not become a topic ad nausem for a community which has already expressed its view before. DeeM28 (talk) 20:30, 20 June 2022 (UTC)
 * I agree with all of your comments, DeeM28. The ReCAPTCHA configuration presents some ongoing challenges, but I very much believe that the way that RfC was structured with only two proposals for alternative CAPTCHAs, so soon after a very similar RfC, was less than ideal. Since the issues persist, I believe continued discussion is reasonable, but I very much would've preferred the RfC's proponent started a discussion at community noticeboard that sought to (a) identify precisely what the problem was with the current ReCAPTCHA configuration, (b) ask SRE to try a series of alternate configurations to (c) identify whether the issue can be fixed with RECAPTCHA. If it could not, then alternatives could, of course, be considered. Dmehus (talk) 03:56, 21 June 2022 (UTC)

Dormancy policy exemption
I'd like to request an exemption to the dormancy policy for https://corpmercs.miraheze.org/

It's a wiki for a relatively popular server on a quite unpopular game engine. (see: Byond)

I don't expect edits to happen often, as the dev cycle is relatively slow, and large changes don't occur too often. And while there's been a handful of people in the past that have done quite a lot, more of the technical details of the game would have to be added by the developers themselves anyways.

If y'all have any questions, feel free to ask. Shadow Quill (talk) 16:42, 10 June 2022 (UTC)


 * there, apologies for the delay. While the wiki is fairly small it does have a well rounded selection of content, and has been around for quite some time. I see what you mean with slower edits; while they don't seem to have caused activity issues the delays in editing have gone past a month multiple times over the year so far. Paired with the fact it appears well integrated in the community it's for, I think it is reasonable to ✅ this. --Raidarr (talk) 19:24, 18 June 2022 (UTC)

Managewiki access Removed by bureaucrat Rights
I'm the founder of the 鸿蒙百科. I added a staff user group so I canceled the Bureaucrats' access permission of the ManageWiki extension. But I forgot to add myself to the user group first (QAQ). Could any of you help me to add the permission of bureaucrats' ManageWiki-access here? Thank you very much.

PS. I'm really sorry for clearing this page just now by accident.--Cocoream (talk) 11:24, 11 June 2022 (UTC)
 * ✅, naturally please be careful when it comes to managewiki changes and permissions design, including making this unusual permissions arrangement clear by some local documentation just to minimize future confusion (for example, what BC would now be for/what takes its place). No trouble regarding your edits, it was fixed quickly. --Raidarr (talk) 12:01, 11 June 2022 (UTC)
 * Thank you very much! I will be careful about that from now on. I'm sorry for editing this page at the same time and losing your edition.
 * Thank you! --Cocoream (talk) 12:16, 11 June 2022 (UTC)

The latest socks of Ngozikal

 * Nina394586353
 * Natalya394563
 * Amanda3952
 * Nina5492452

In this one, the usernames are pretty ducky, and rather obvious in terms of username similarities, and also writing style is identical to other identified socks (there's been a bunch of Ngozikal socks popping up, so if I didn't gather enough, I couldn't quite keep up so I'll try the best I can).

If we look at this history from the Public Broadcasting Service page, you might notice these edits overlap with Kimbella3452's edit, along with some more overlaps from the account(s).

Chuck Quenano's latest socks

 * Movie Logoz Time Again
 * Stella's Logo Archive
 * Jayden the Time Time
 * Chance's Another Logo Archive
 * Stella's Angry Badger

There's just too many to list here, but a CheckUser is absolutely needed here, as seen from this remarkable overlap from this article on the Closing Logos Group Wiki. I assume you might not have read the email I sent you last night, but there's just too many sock accounts from both parties to even list, so I am doing the best I can to gather some type of evidence through the page's history. Sorry if it looks a bit weak, but the usernames are obviously similar in terms of username similarities. DarkMatterMan4500 (talk) (contribs) 22:36, 11 June 2022 (UTC)


 * DarkMatterMan4500, Indeed, I'd not seen your e-mail message yet, but will aim to look at it tonight, together with this report and any direct messages you may have sent on IRC. Dmehus (talk) 22:45, 11 June 2022 (UTC)


 * There's one that still needs to be banned, because this guy's not the actual logo YouTuber itself who posts logos he captures.--Crazy Muzzarino (talk) 19:52, 12 June 2022 (UTC)
 * That's ❌ to the 2 parties I've listed above. DarkMatterMan4500 (talk) (contribs) 19:56, 12 June 2022 (UTC)
 * If you closely check the personal info on his profile on the wiki you're addressing the problem at, that is one of his socks he openly used his real name at. So yes that one needs to be banned.--Crazy Muzzarino (talk) 20:10, 12 June 2022 (UTC)
 * From what I've been hearing, ThePBSArchive2020's modus operandi is usually impersonation. It could possibly be him imitating Chuck Quenano. DarkMatterMan4500 (talk) (contribs) 12:46, 13 June 2022 (UTC)
 * And of course, another sockpuppet, which is Chance and Friends just showed up., just a heads-up. DarkMatterMan4500 (talk) (contribs) 19:12, 21 June 2022 (UTC)
 * I've issued a soft block locally that should at least somewhat stem these account creations, which I picked up while taking a glance at the 'abuse filter' accounts clearly created to circumvent blocks themselves. Everything here is superficial enough that I'm uncertain in taking stronger action and will defer to Doug before proceeding to lock/deeper sockpuppetry investigation unless the soft measures in the cases I did look at are circumvented. I may end up looking at the Pepsi case earlier if I get a better reading of who Chuck is and what they're on about. --Raidarr (talk) 22:42, 23 June 2022 (UTC)

The Girlfriends Saga Wiki
I'm the owner of this wiki and I know I haven't been editing it for a very long time, but can you make it private so that only I can edit it, so others don't without my permission to?

--XenithXenaku (talk) 18:19, 12 June 2022 (UTC), edited at 18:24, 12 June 2022 to fix errors.


 * Making a wiki private and setting it as editable only by you are two different things. If you want to make your wiki private so no one can read it apart from those you authorize, please go to Special:ManageWiki on your wiki and check the "Private" box. To simply make your wiki uneditable by non-administrators, go to Special:ManageWiki/permissions -> (everyone) and revoke the "edit" permission from the group and assign it to the "Administrators" group. Agent Isai  Talk to me! 19:02, 12 June 2022 (UTC)
 * If you want make your wiki uneditable by non-sysops, you will need to remove the "edit" permission from the "user" group also. Hope that helps. Cheers, Matttest (talk | contribs) 08:20, 13 June 2022 (UTC)

Remove bureaucrat right from User:Reiji801 on mh:nucarnival
Hi, could you remove bureaucrat right from User:Reiji801 on mh:nucarnival? It's been 3 months since he got that right, but not a single edit has been made. Thanks. William Surya Permana (talk) 03:57, 13 June 2022 (UTC)


 * It seems that he have no contributions there but was granted with rights by the founder. There is a reasonable thought that this account is an alternate account created by the founder. I will advise you to ask the founder of the wiki about why the rights is granted before asking for steward action here. Cheers, Matttest (talk | contribs) 08:36, 13 June 2022 (UTC)
 * Hi @Matttest. For the reason why the right is granted, actually it's because both Reiji and I requested it on a Reddit comment posted by the founder. So, it's not an alternate account. William Surya Permana (talk) 09:46, 13 June 2022 (UTC)
 * Just for the record, Miraheze does not recognise 'founders' as being superior to other bureaucrats, we only recognize communities. If you want bureaucrat removed, I would suggest holding a vote locally (see Local elections) to determine whether the community wants 'crat removed from Reiji801. If that is the case, a Steward will confirm the vote and remove bureaucrat. Reception123 (talk) ( C ) 11:34, 13 June 2022 (UTC)
 * Hi, I've looked over this and while Reception is typically correct and the LE process is preferred for major changes involving the bureaucrat right, there are several factors here where I believe a speedy removal is warranted. The first is the zero edits, making the affected a non-factor community wise. Second, the reddit post which I believe checks out on the nature (and general terms) of the promotion; the reasons provided there aren't met, indeed admin let alone bc wasn't necessary unless the wiki restricts editing to admins. BC in good part is the technical area that the user in question didn't really want to involve in. Third is the absence of any community that would lend merit to this process - the only substantive vote would be the founder, aka co-operator who's been away for some time, though in accounting for his background a removal request would have less ground to stand on and at the very least I would expect reaching out.
 * The circumstances in this one are fairly clear and this would merely be a clerical inactivity removal in what appears to be a healthy, if tiny ecosystem. I assume if the rights are needed in the future they can just be re-requested/regiven. Otherwise I'll pull from the Code of Conduct regarding graceful resignation, though in this case the user is 'being' resigned. I'm going to call this ✅ and circumvent bureaucratic fuss in an affair which does not need it. --Raidarr (talk) 12:01, 13 June 2022 (UTC)
 * Thanks for your help, @Raidarr. Yup, you're correct, sadly this wiki lacks active users at the moment. William Surya Permana (talk) 02:17, 14 June 2022 (UTC)

Wikilouco again
So, 2 weeks ago i requested bureaucrat at WikiLouco. They told me to create a votation, and so I did. But, since then nobody came to vote, so I now I can get the staff, thank you. The Log (talk) 14:35, 13 June 2022 (UTC)


 * this is now ✅, see the finishing text locally. You did actually get a vote from a sysop - that alone was quite persuasive, given the absence of all other operators/bureaucrats. --Raidarr (talk) 15:45, 16 June 2022 (UTC)

CheckUser request for the following accounts

 * Yonnnptk
 * Uuuuuuuuuuuuuu
 * Idependient journalist
 * Dehehhe

I am asking for a CheckUser on these particular accounts as they have been editing in a similar fashion to either Anti villain or Gigdsclasp, with similar trolling tactics or otherwise disruptive behavior.

Here's a comparison of behavioral evidence and/or similar editing styles they have been using to consider: So overall, a CheckUser might be necessary, as Anti villain/Gigdsclasp has been known for resorting to sockpuppetry or lock evasion for over a year now, and these accounts need to be checked, along with any sleepers they might be carrying around. Thank you. DarkMatterMan4500 (talk) (contribs) 19:23, 14 June 2022 (UTC)
 * Uuuuuuuuuuuuuu vs. Idependient journalist
 * Idependient journalist vs. Napalm vs. Gigdsclasp vs. Omar Bongos
 * Yonnnptk vs. Uuuuuuuuuuuuuu
 * Uuuuuuuuuuuuuu vs. Anti villain vs. Ambrosio Requena (Ambrosio Requena was confirmed to Anti villain directly)
 * Dehehhe vs. Uuuuuuuuuuuuuu (These 2 diffs especially should become very obvious especially when the latter reverted to the former's revision, which means it's very obvious that ban evasion is occurring here.)


 * I hope to hear back from a Steward as soon as they see this thread. DarkMatterMan4500 (talk) (contribs) 14:01, 19 June 2022 (UTC)

Change Server…
（抱歉懒得翻译，只用中文写了）最近QQ几个群友又抱怨worldboxwiki服务器卡了. 查了下发现服务器居然在🇨🇦博阿努瓦. 查了下，有人说你们在🇸🇬有服务器，不知道能不能换到这边，速度比较快. （当然可以用英文回复，如果是机器翻译的中文我也不介意） Isutan (talk) 01:36, 16 June 2022 (UTC)


 * Tech:Cp3 Isutan (talk) 01:45, 16 June 2022 (UTC)
 * 看起来Cp5更快 Isutan (talk) 01:49, 16 June 2022 (UTC)
 * Both servers are no longer in production as clearly indicated by the pages. Reception123 (talk) ( C ) 05:26, 16 June 2022 (UTC)
 * So what other servers are closer to China? @Reception123 Isutan (talk) 23:52, 16 June 2022 (UTC)

Request for deletion
I would like to request the deletion of two wikis: Beach Ball Wiki (https://closingthings.miraheze.org/) and Cartoon Wiki (https://cartoon.miraheze.org/), both of which were created by Caidin Johnson, a known vandal and abuser of sockpuppet accounts. The former is also a ripoff of the CLG Wiki. Buzzfan120 (talk) 18:52, 16 June 2022 (UTC)


 * Could you elaborate on how those 2 wikis are rip-offs of the CLG Wiki? The way you worded it was very vague. As for Caidin Johnson herself, some of us are quite aware of what she does, and one Steward even took notice of that, after I reported her previous socks back in November. DarkMatterMan4500 (talk) (contribs) 18:57, 16 June 2022 (UTC)
 * In most cases, we only delete wikis which most of its articles violated the Content policy or have severe copyright issues, usually with an extra question about this to the founder. You said the former one have copyright issues, can you give out the corresponding links for evidences? For the second wiki you mentioned, unless there is a clear violation of the policies I mentioned above, I doubt if the it can be deleted only due to the reason that the owner is a LTA. Cheers, Matttest (talk | contribs) 08:26, 17 June 2022 (UTC)
 * There is precedent for deleting wikis made by locked users where there are no other local contributors, in accordance with the Content Policy provision of "Miraheze may delete unused and empty wikis." Agent Isai  Talk to me! 14:47, 17 June 2022 (UTC)
 * Empty or unused wikis can indeed be closed under the Dormancy Policy which is noted by the Content policy, but from what I can see those wikis they mentioned wasn’t closed or inactive, so I doubt if stewards should delete those wikis. Cheers, Matttest (talk | contribs) 02:05, 18 June 2022 (UTC)
 * Caidin is a guy, by the way. And the Beach Ball Wiki is a ripoff of the CLG Wiki because a lot of the articles are about logos, with Caidin's signature brand of nonsense thrown in. He even went so far as to give his wiki a similar domain name (closingthings.miraheze.org) (CLG Wiki's domain name is closinglogosgroup.miraheze.org). The other wiki isn't a ripoff of the CLG Wiki, it's just a bunch of nonsense. And the only contributor to these wikis is Caidin, but he uses various sockpuppet accounts to edit the two wikis. Buzzfan120 (talk) 04:23, 18 June 2022 (UTC)
 * To add onto the evidence for Beach Ball Wiki being a carbon copy of the CLG Wiki, the Rules page for Beach Ball Wiki (closingthings.miraheze.org/wiki/Beach_Ball_Wiki:Rules) is a near-exact copy of CLG Wiki's Rules page (closinglogosgroup.miraheze.org/wiki/CLG_Wiki:Rules), even down to retaining mentions of the CLG Wiki. HibiscusCrown20 (talk) 18:34, 20 June 2022 (UTC)
 * First, I just want to say that Caidin is not globally locked, so I still doubt if the second wiki you mentioned shall be deleted, since it is still not marked as closed per the Dormancy Policy. However, having checked the Beach Ball Wiki, I agree that tons of pages are rip-offs of CLG wiki, so it should be deleted under the Content Policy which notes “A wiki must not create problems which make it difficult for other wikis”, which apparently it does. I think pinging Raidarr (a steward in miraheze) here will be useful for all parties. Also ping Caidin2009 to note that your wiki is being asked for deletion. Cheers, Matttest (talk | contribs) 10:48, 24 June 2022 (UTC)

Please add Dormancy Policy exemption for FIFA Manager Modding Wiki wiki
I'm asking to add the wiki to exemption list https://fifam.miraheze.org/wiki/Main_Page The reason is current war in Ukraine. Last time a lot of people contacted me because they saw a notification about a possible deletion. There may be a situation where I will not be able to update the wiki. Dmitri (talk) 21:13, 18 June 2022 (UTC)

Inability to log on
I created a test account named "CigarynoTest" and every single time I log in, it tells me no log in session is active. Redacted 06:46, 19 June 2022 (UTC)
 * Hi, Please disable Total Cookie Protection on Firefox. If you wish to discuss more and avoid exposing your IP, please contact sre[at]miraheze.org ~ RhinosF1 - (chat)· acc· c -  06:54, 19 June 2022 (UTC)
 * I fixed it with a VPN, also this is my main account. Cigaryno (talk) 08:15, 19 June 2022 (UTC)
 * I have met similiar problems before, and it was fixed by either (i) logging in to another miraheze wiki (ii) using incognito mode to log in. Cheers, Matttest (talk | contribs) 13:08, 19 June 2022 (UTC)

Question
Why is the URL thetoptens.com in the spam filter? FatBurn0000 (sandbox | CentralAuth) 09:10, 20 June 2022 (UTC)
 * This is just because in matches the entry thetoptens.com matches the spam blacklist. Cigaryno (talk) 14:55, 20 June 2022 (UTC)
 * Hi, TheTopTens was banned from being linked to as it is full of abuse and unmoderated. ~ RhinosF1 - (chat)· acc· c -  15:03, 20 June 2022 (UTC)
 * Specifically, it was added as a result of this discussion for hosting harassment towards Miraheze users. — Chrs (talk) 18:46, 20 June 2022 (UTC)
 * , and  But what if a page about the website's content was going to be created? FatBurn0000 (sandbox | CentralAuth) 20:53, 20 June 2022 (UTC)
 * It will not be created because thetoptens.com matches the global spam blacklist. Cigaryno (talk) 09:29, 21 June 2022 (UTC)
 * No I mean, have you considered that users might want to do that? FatBurn0000 (sandbox | CentralAuth) 13:31, 21 June 2022 (UTC)
 * See the global spam blacklist and find  here. Cigaryno (talk) 13:40, 21 June 2022 (UTC)
 * Yes, we have considered the fact that the community doesn't want wikis to be able to link to an abusive and unmoderated website. If you think this position should be changed you're free to present arguments as to why that should be done. Reception123 (talk) ( C ) 18:41, 21 June 2022 (UTC)
 * Yes, but what I mean is, I'm not talking about theTopTens being used as a source itself for information, I am talking about if users wanted to create wikis and pages about its content. FatBurn0000 (sandbox | CentralAuth) 20:45, 21 June 2022 (UTC)
 * Creating pages about TheTopTens isn't banned, only using the actual link will be prevented (if I understood what you meant correctly) Reception123 (talk) ( C ) 12:42, 22 June 2022 (UTC)
 * I would advise you strongly consider the Content Policy when doing so, while it is not banned, you run a serious risk of violating it if posts from the site are repeated on Miraheze that are inappropriate. ~ RhinosF1 - (chat)· acc· c -  12:47, 22 June 2022 (UTC)
 * A page about TheTopTens will be created but only  was banned. Cigaryno (talk) 16:30, 22 June 2022 (UTC)

Closing Trashy Celebrities wiki
This wiki be closed due to it being in severe content policy violations. It violates the policy because it is meant to slander real life people. Almost all pages have no sources, unlike something like Real Life Villans. It should be closed immediately. ZeusDeeGoose (talk) 22:23, 20 June 2022 (UTC)
 * While I would say based on a brief sample that the pages generally attempt to source and it is not as urgent as it's made out to be here, I do find the wiki is problematic enough to initiate a process that will likely lead to its closure. I've left a topic about it locally. --Raidarr (talk) 12:06, 21 June 2022 (UTC)
 * and No, it does not violate the content policy. It is not slandering people, it is criticising them, and the pages on the wiki that don't follow this are up for deletion. FatBurn0000 (sandbox | CentralAuth) 13:33, 21 June 2022 (UTC)
 * You do realize that this has been said more than 10 times in the past, right? That's not going to convince anybody, I'm afraid. DarkMatterMan4500 (talk) (contribs) 19:10, 21 June 2022 (UTC)
 * Well, regardless, it's true. FatBurn0000 (sandbox | CentralAuth) 20:39, 21 June 2022 (UTC)

Hit Counters
I recently completed the 'survey' and I did state that I would like to see statistics on a per page basis. Reception123 kindly responded with "I understand the need to see statistics on a per-page basis but for the time being unfortunately we don't have enough funds to be able to fully implement this. However, we are trying out hit counters which can be requested at https://meta.miraheze.org/wiki/SN so you could try to that to at least have minimal statistics for the time being." So inline with Reception123's recommendation I am requesting the 'hit counter' facility please. NavySparker (talk) 13:09, 21 June 2022 (UTC)


 * The WiKi in question is 'Battle of Jutland Crew Lists Project'. Sorry I missed that off on my original posting. NavySparker (talk) 10:54, 22 June 2022 (UTC)
 * What subdomain does your wiki have? ~ RhinosF1 - (chat)· acc· c -  10:58, 22 June 2022 (UTC)
 * The Wiki is battleofjutlandcrewlists.miraheze.org NavySparker (talk) 16:59, 22 June 2022 (UTC)
 * This is a request for the 'Hit Counter' facility to be installed on the above Wiki please. NavySparker (talk) 15:37, 25 June 2022 (UTC)

Request for skin change at unbookswiki
Following discussions in the community portal at, there is clear community consensus for changing the wiki’s skin from vector-2022 back to legacy vector. As a local sysop of this wiki, I request to change the skin back to legacy vector for the whole site. Thanks. Cheers, Matttest (talk | contribs) 11:08, 22 June 2022 (UTC)


 * You can contact the wiki's bureaucrat(s). Cigaryno (talk) 15:37, 23 June 2022 (UTC)
 * There are no local bureaucrats due to an ongoing local dispute which requires Steward mediation hence why Matttest asks here. Agent Isai  Talk to me! 16:05, 23 June 2022 (UTC)

Enabling External Data extension at https://runrust.miraheze.org
Hello, I noticed T9246 and our wiki would like to use this extension to query APIs for the latest versions of software, could a steward please enable it? Thanks! Fee1-dead (talk) 02:36, 23 June 2022 (UTC)


 * Ping @Universal Omega. Fee1-dead (talk) 09:26, 24 June 2022 (UTC)

Interwiki request
Could you add two interwikis on Japlantwiki,please?Here is a result of discussion.("賛成" means "surpport" in Japanese.) by Buel ·Talk·Wikimail 08:47, 23 June 2022 (UTC) Fix. by Buel ·Talk·Wikimail 09:37, 23 June 2022 (UTC)


 * Note for patrollers: The requesting wiki is private. Steward action is necessary in this case. dross  (t • c • g) 08:54, 23 June 2022 (UTC)
 * They requested earlier on Discord and later withdrew the request, the private thingy was the same reason. Interwiki administrators can not edit the Special:Interwiki of a private wiki. --  Joseph  TB  CT  CA   17:30, 23 June 2022 (UTC)
 * I am just curious why the wiki is make private while the wiki request states that it is a wiki that describe plants in Japanese, which should be a public encyclopedic wiki. Cheers, Matttest (talk | contribs) 10:25, 24 June 2022 (UTC)
 * Local bureaucrats have the right to change it from private to public whenever, maybe they just wanted to be the ones to edit it, not anyone else. Plenty of reasons to make a wiki private, even those wiki a public-sounding wiki request. Thanks - BrandonWM (talk • contribs • global • rights) 15:45, 25 June 2022 (UTC)

global block request
I have found out that the IP range 45.91.23.0/24 is an open proxy:Expressvpn. Airtransat236 (talk) 23:22, 23 June 2022 (UTC)

Talk Page Access Denied On-Wiki
Hi,

I'm filing this report as I've recently noticed that a wiki,, has been denying talk page access to any user for communication. While not explicitly disallowed, it's doesn't permit communication between editors, and as such, is an obstruction on basic editing. Thanks - BrandonWM (talk • contribs • global • rights) 02:55, 24 June 2022 (UTC)


 * This was done following the consultation of Stewards due to severe Code of Conduct violations that occur on the wiki, specifically on the former comment sections and talk pages. CVT had to intervene several times on that wiki, particularly in the comments section and thus that had to be done. Agent Isai  Talk to me! 04:07, 24 June 2022 (UTC)
 * Ah, gotcha. Got it. Thanks - BrandonWM (talk • contribs • global • rights) 15:21, 24 June 2022 (UTC)

Urgent: I accidentally deleted the Bureaucrat role. Could a steward please readd it to my wiki?
I accidentally deleted my Bureaucrat usergroup for my wiki at https://vyyrahkcity.miraheze.org/ Could someone please readd the usergroup and place my account into it? Yoshi Funny (talk) 20:20, 24 June 2022 (UTC)


 * I've restored the group with the default permissions set I believe. Either way, you should now have managewiki access back to continue customizing permissions. Just be sure to be careful that you don't remove managewiki without already being in another group that also adds it. -- Void  Whispers 20:52, 24 June 2022 (UTC)

Enable something in my wiki
Hello, I need a steward enables the expirimental features checkbox in Special:ManageWiki/core/gdwikiwiki. Cigaryno (talk) 12:44, 26 June 2022 (UTC)

None one comes to resolve the request wiki queue?
I requested to create Cloaud Village Wiki 8 hours ago but I haven't get any replies. Zes M Young (talk) 13:26, 26 June 2022 (UTC)


 * Be patient as wiki creators might be busy for now. Cigaryno (talk) 13:41, 26 June 2022 (UTC)
 * Sorry. OK. I'm actually not in such a hurry. --Zes M Young (talk) 14:06, 26 June 2022 (UTC)
 * your request is currently waiting for you to select a different subdomain. — Chrs (talk) 23:10, 26 June 2022 (UTC)