Stewards' noticeboard

From Meta
Jump to navigation Jump to search
You are currently logged out. Please note that if you are having problems with your wiki, you need to login.

If you are 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 cannot ascertain 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 tech(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.

Stewards' 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 community noticeboard first, and you will be directed here if the matter requires a Steward

On Stewards' noticeboard, you can:

  • Request a steward or Global Sysop to lock 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
  • Report a Username Policy violation (whether in good-faith or bad faith)
  • Report a user suspected of abusing multiple accounts per user accounts policy. You must link to specific revisions from both the suspected master and illegitimate alternate account(s)
  • Request additional permissions on your wiki(s) that can only be granted by a steward, such as local interwiki administrator
  • Request a page requiring the bigdelete user right (more than 1,000 revisions) be deleted on your wiki
  • Request a Dormancy Policy exemption for your wiki
  • Report 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:


Please remember to:

  • Sign your request using ~~~~
  • Stay respectful
  • Give us enough details regarding your problem
To add your request, type in a title and click the "Add Topic" button below.

Archives of Stewards' noticeboard [e]   



Dormancy Policy exemption for a currently private wiki

I would like to apply for dormancy policy exemption for my currently private wiki.

For the following reasons:

1 - There is only so much I can take of going back and forth using wayback machine to retrieve the data, I need breaks. There was no xml dump (that I know of) and the way the publisher hosted it was extremely limiting, we editors didn't have the delete power at all nevermind administrator powers. The currently private wiki is a rebuild of a lost wiki (it was essentially deleted when the publisher lost rights to the game and failed to pass the wiki to new publisher) I am one of the original wiki editors and I absolutely despise that publisher for deleting 10+ years of work that the community put into that wiki, (I contributed about 7 years of work before I left when that publisher first took over, I knew they were bad due to disrespecting of experienced wiki editors). So I guess its essentially me taking it back and rebuilding it better.

2 - I'm an active gamer, every so often I find a slew of games that I'm interested in trying out. Recently there had been 3 in a row (one after the other, spending a few weeks in each one, which took up the time I would have otherwise spent on my wiki) this triggered the inactive warning which I then had to spend 10-15 mins searching how to get rid of it, time I rather spend editing when I'm back after playing.

3 - I have a burning hatred of the publisher that I blame for the loss of the wiki, I will eventually have it back to its former glory, once there I will most likely make it publically viewable but not editable unless by admins. I do not want to lose the wiki again. Mystic (talk) 20:58, 8 December 2021 (UTC)[reply]

Could I get a reply? If the information above is insufficient, please contact me on Discord (preferred way of contact) Thanks. Mystic (talk) 23:14, 23 December 2021 (UTC)[reply]

Hi, sorry for the delay, I assume this just wasn't seen until now. I have made your wiki exempt from the Dormancy Policy, so you shouldn't have to worry now. -- Void Whispers 00:04, 7 January 2022 (UTC)[reply]
Thank you Mystic (talk) 15:23, 8 January 2022 (UTC)[reply]

Could these pages be imported?

I created a list here of pages from the now-closed New Reception Wiki that should be imported to another wiki. As suggested by @TigerBlazer: in the comment section of this blog post I made about it on The Chill Place, the pages could possibly be imported to that wiki. Could a steward please take a look at this? FatBurn0000 (talk) 03:19, 27 December 2021 (UTC)[reply]

@FatBurn0000: This seems like a request better suited for Phabricator. Agent Isai Talk to me! 03:35, 27 December 2021 (UTC)[reply]
As I recall, Dmehus solicited the suggestion of pages to export from the wiki as a Steward when refusing a request to reopen the wiki. Therefore in this case I believe the message being placed here is appropriate unless noted otherwise, as something that I believe would require a Steward to process. --Raidarr (talk) 18:25, 9 January 2022 (UTC)[reply]

Creating a steward requests page to be used for requesting (b)locks, permissions, CU

Hi. I am proposing to create a page where users may report user account and IP's to CVT, request CU information and permissions from stewards after holding Local election or after successful reopening request. All the above mentioned things will be divided into sections for the clarity. The locks and blocks can be performed by CVT but the other requests such as CU and permissions requests will be performed only by Stewards. This noticeboard will still be used for miscellaneous requests and other things which are not mentioned above. The page will be titled CVT requests or Steward requests (preferred). --Magogre (talk) 04:53, 29 December 2021 (UTC)[reply]

Stewards noticeboard is also often cited to report users who have committed vandalism, and even request a block, and email is currently a good option, so I don't think that would be necessary --YellowFrogger (Talk) 05:02, 29 December 2021 (UTC)[reply]
Email is not used to request blocks or report users/IP's, if I am not mistaken. It is used to request oversight, appeal locks and blocks and discuss other private matters with stewards which cannot be publicly discussed.
SN is cited to report, but that's what I am proposing to change in regards to above mentioned things (blocks, CentralAuth locks, CU information and permission requests) --Magogre (talk) 05:19, 29 December 2021 (UTC)[reply]
Symbol support vote.svg Support SN has too many purposes, to me.  Anpang📨  05:06, 29 December 2021 (UTC)[reply]
How would you propose this page be structured? In a fashion like that of Wikimedia Meta-Wiki's Steward requests/Global? I was actually reviewing this topic with another volunteer today and suggested perhaps following Orain's approach to the Stewards' noticeboard as a demo perhaps. Agent Isai Talk to me! 08:00, 29 December 2021 (UTC)[reply]
Agent, Orain's page (you linked) looks similar to what I am saying. As I have said above, there will be a section for each type of request - one for CU, one for permissions, one for blocks and locks with a general header on the top and a specific header in each of these three headings properly guiding users where and how to request. Magogre (talk) 12:16, 29 December 2021 (UTC)[reply]
Magogre, I do not believe we need to replicate the Wikimedia way of doing things, with multiple noticeboards for stewards to monitor. We're just not big enough, nor are there a sufficient number of requests, to warrant multiple noticeboards for each type of requests. Global Sysops will monitor stewards' noticeboard for certain requests within their scope and mandate, and assist with those requests where they are able to do so. There's also issues with a lot of these requests are actually requested on IRC in #miraheze-cvt connect. As well, many users will post on the wrong noticeboard, with one stewards' noticeboard; let alone four or five. We could, however, create separate boilerplate templates for common steward requests (such as a local election request, local interwiki administrator request, bigdelete request, CheckUser request, or other request), but still have them be added to this noticeboard. That in and of itself, with consistent subject headings, would go a long way towards improving the organization. Dmehus (talk) 18:54, 30 December 2021 (UTC)[reply]
Not every user uses/will use IRC or Discord. Off-wiki #cvt should be only for emergencies or where CVT need to act instantly. Everything should be centred on-wiki. I have even seen users requesting to perform CheckUser on someone and a lot of similar cases, daily on Discord. I am not trying to replicate Wikimedia's way, I never said that. It is for the simpleness and separating the noticeboard. I agree that there aren't too many requests, but it is better to have one instead of monitoring spambot list userspace pages. Magogre (talk) 20:06, 30 December 2021 (UTC)[reply]
Well, for spambots, we don't necessarily need to have those retained in an archive in perpetuity. Also, locking spambots without soft blocking the IP ranges is of only marginal and very short term use, as additional spam only accounts are created on a daily basis, but upon re-reading your reply, I see that's not really what you were requesting, so that's fine. CheckUser requests for non-routine evasion are rather infrequent (i.e., AllTheTropes Wiki was the last one, as I recall), so I don't see why those can't remain on stewards' noticeboard. I do agree with maintaining simplicity, but speaking with Reception123 and others in the past, fewer noticeboards are way this achieved. Thus, if we make any changes, I would suggest a streamlining of the Steward request workflow to use common request templates, similar to the process used at requests for adoption. Hope that clarifies and is helpful. Dmehus (talk) 20:25, 30 December 2021 (UTC)[reply]
While I like the idea of a streamlined process, I believe it would first be important to consider and develop the reporting platform that has come up in odd discussion and previous Miraheze Meetings. Said platform can suppelment the current Noticeboard function without adding too much more inline structure to the way this page and the process works. I think the objective should be minimizing complications for reporting as possible, and as such we should consider the above before splintering off different noticeboards. If that is too far in the future or not feasible I encourage developing a proof of concept or collaborating for one in a dedicated space, be it Meta userspace, split to Public Test Wiki for scale or a different dedicated area so the structure can be made, reviewed, styled and implemented cleanly. Developing clarity and a comfortable interface is critical for an idea such as this to work, and to reduce what I consider WMF's flaw of having a questionably offered interface with too many divisions for people trying to solve issues, as I think is already something of an issue for how Miraheze already works. --Raidarr (talk) 14:57, 9 January 2022 (UTC)[reply]
I concur largely with Raidarr's comments above. While it's true not everyone users IRC or Discord, the vast majority of those active volunteers do, including Magogre. I also agree that we should not replicate the many imperfect aspects of Wikimedia, in terms of on-wiki reporting of what are routine or reports (i.e., requests to block open proxies, lock obvious spambots, or even lock obvious vandalism only accounts). If user does not use IRC or Discord, the on-wiki reports are not too frequent so as to be to require segmentation to a separate noticeboard. Consolidating requests on a single noticeboard means fewer noticeboards for Stewards to monitor, and it should be noted that it is not a noticeboard used exclusively by Stewards' either; Global Sysops monitor for requests within their mandate and with which they're able to handle. I think Miraheze has a unique multi-channel reporting structure, and this is the best. If at some point, a particular type of request requires a separate noticeboard, we can consider that, but I would probably be more inclined to favour a local election assessment request noticeboard, retaining CheckUser requests and global lock/block requests at stewards' noticeboard. Dmehus (talk) 16:15, 9 January 2022 (UTC)[reply]

Restoring ManageWiki permissions for Bureaucrat role

Hello. I've by accident removed the ManageWiki permission from the Bureaucrat role in my wiki, inadvertently locking myself out of the ManageWiki permissions and in turn preventing me from restoring that permission to myself. With no obvious way of fixing this issue and with this issue practically stopping me from configuring the wiki at all, I don't see any alternative other than to ask a steward's help in restoring this permission to my wiki's Bureaucrat role.

The wiki in question

My wiki's page for managing permissions Sylepieus (talk) 18:26, 30 December 2021 (UTC)[reply]

Sylepieus, Yes check.svg Done. Please ensure that you do not remove the managewiki user right, as it's essential for using ManageWiki on your wiki. Thanks. Dmehus (talk) 18:45, 30 December 2021 (UTC)[reply]

My Detective Conan Wiki adoption request

Hello. I wanted to tell you that I had made a request to adopt Detective Conan Wiki: here Could you take a look at it to see if I qualify? Thanks in advance and sorry for the inconvenience. Anass (talk) 01:30, 31 December 2021 (UTC)[reply]

@Anass: Please ask to adopt a wiki in the requests for adoption. --YellowFrogger (Talk) 01:37, 31 December 2021 (UTC)[reply]
Anass, I will aim to handle the open requests for adoption tonight and tomorrow. Dmehus (talk) 01:39, 31 December 2021 (UTC)[reply]
Yes check.svg Handled elsewhere. Dmehus (talk) 18:18, 31 December 2021 (UTC)[reply]

Detective Conan Wiki language change

Hello, I want to change the language to Detective Conan Wiki from English to Spanish, may it be possible (I requested it from the beginning but with all this change it is in English)? Anass (talk) 17:57, 31 December 2021 (UTC)[reply]

Anass, Yes check.svg Done. Dmehus (talk) 18:02, 31 December 2021 (UTC)[reply]

CheckUser request for the following accounts listed here:

While yes, DravenLoLf4n6 is indeed globally locked, I did find something pretty suspicious about how these accounts have behaved on a few wikis, which I'll be narrowing down the list of (hopefully sufficient) evidence that could be used to identify the main account (if BlitzR6SiegeMain76 is the master at all). For one thing, both Blitz and Draven have vandalized the Undertale article on the Awesome Games Wiki, with BlitzR6SiegeMain76 replacing all contents with gibberish, then about 16 days later, DravenLoLf4n6 came about and did something similar, except writing an inappropriate edit. Then we have BlitzR6SiegeMain76 replacing content with racial slurs, which is technically indistinguishable to Jack the Furry Slayer's racial slurs he put on The Dunkman's article about the Clifford movie on Awful Movies Wiki. Not sure if this is enough evidence to warrant a check, but I have noticed some similar gibberish that both Blitz and Draven have added (while DravenLoLf4n6 is indeed globally locked, I'd like that account to be checked as well). Pinging Dmehus to give this section a look. DarkMatterMan4500 (talk) (contribs) 18:48, 31 December 2021 (UTC)[reply]

Dmehus Let me guess: You didn't find much, right? --DarkMatterMan4500 (talk) (contribs) 19:10, 31 December 2021 (UTC)[reply]
DarkMatterMan4500 Thank you for your report. Please note that while you've provided evidence, I did not find the linked diffs particularly compelling. I did, however, find other evidence which suggested there was potential inappropriate abuse of multiple accounts in accordance with user accounts policy. However, I would say these two accounts X mark.svg not likely related. Nevertheless, though the vandalism is occurring on one wiki, based on a variety of evidence, I have Yes check.svg locked BlitzR6SiegeMain76 as a vandalism only account. Thanks. Dmehus (talk) 19:13, 31 December 2021 (UTC)[reply]
@Dmehus: Alright, thank you. --DarkMatterMan4500 (talk) (contribs) 19:15, 31 December 2021 (UTC)[reply]

Detective Conan Wiki permits

Hello, I wanted to request delete and move permissions for Detective Conan Wiki as the previous bureaucrat protected all categories and templates. Anass (talk) 19:39, 31 December 2021 (UTC)[reply]

Anass, for that, you will need to hold a local election somewhere on the wiki. You can advise me when it's set up, and I can add a local sitenotice for you. Nevertheless, in the interim, I can unprotect those categories and templates for you, to allow you to work on them? Dmehus (talk) 19:43, 31 December 2021 (UTC)[reply]
Dmehus Perfect, where do I have to make the local choice and how do I do it? Yes please, I need to work on them.--Anass (talk) 19:53, 31 December 2021 (UTC)[reply]
Anass, check the wiki to see if there's a "requests for permissions," "administrators' noticeboard," "bureaucrats' noticeboard," or "community portal" (usually in (Main) or Project: namespace. If none exists, then simply create a local election page in either namespace, explaining clearly the rights you're requesting, that you would be seeking to be an additional bureaucrat/sysop, not a replacement, and outline how to express views for or against your candidacy. Once set up, you can return here to request a local sitenotice. I will unprotect the templates and categories per your request now. Dmehus (talk) 15:26, 1 January 2022 (UTC)[reply]
Dmehus I already have the message and it is found here. I would like to know what would happen if no one commented or voted in the election, would it be automatically canceled?--Anass (talk) 17:13, 1 January 2022 (UTC)[reply]
Anass, thank you. I'll review this after a few days, and will add the local sitenotice per your request and per good global practice. To your question, no the election would not be cancelled. Rather, we would consider your contributions to the wiki, and assuming you'd made more than a few very minor edits and there no objections, would declare your election request successful by acclamation. Hope that helps. Dmehus (talk) 17:25, 1 January 2022 (UTC)[reply]
Hello Anass: unfortunately, I have to tell you that I have declined the idea of continuing with the Detective Conan wiki and wanted to apologize for my insistence and the inconvenience I have given you. I would also like to ask you to delete my edits and make the wiki private so that someone else can adopt it, I don't know if the latter is possible but I leave it up to you. --Anass (talk) 22:53, 1 January 2022 (UTC)[reply]
Anass, not a problem. As to deleting your edits, that's not really needed. Other users can pick up where you left off and make further changes, or roll the changes back. As to making the wiki private, that would need a local community discussion (described above for the permissions request). So if you don't go to that step, I would say, just move on and leave the wiki be. Someone will pick up where you left off, request to adopt it, or the wiki will be later deleted. Dmehus (talk) 22:57, 1 January 2022 (UTC)[reply]
Ok, thank you very much and sorry for the inconvenience. --Anass (talk) 23:13, 1 January 2022 (UTC)[reply]

Can I have my username renamed from Connall2021 to Connall2022 please?

Hello, I would like my username to be renamed from Connall2021 to Connall2022 to match up with the year weʼre currently in please. Connall2021 (talk) 06:33, 1 January 2022 (UTC)[reply]

Connall2021, Hi there. You can request a rename at Special:GlobalRenameRequest though I would advise you don't request a rename every year and instead pick a nickname which isn't so dependant on the year. Agent Isai Talk to me! 07:41, 1 January 2022 (UTC)[reply]
Though we can accept your rename request via stewards' noticeboard, I concur with Agent Isai above in that you should pick a username that is not dependent on the current year. Usernames are meant to be long-term things, lasting across multiple years. Dmehus (talk) 14:10, 1 January 2022 (UTC)[reply]

Yandex. Critical error

Yandex. Critical error (1 jan 2022)
Yandex. Critical error (1 jan 2022)

Message sent by Yandex to my email address:

Hello!

The average server response time is longer than 3 seconds. Slow page loading makes it difficult to use the site https://wikifrases.miraheze.org. Examples of pages where a slow response was detected:

/wiki/Categor%C3%ADa:Im%C3%A1genes_por_licencia 2022-01-01 00:53:01 UTC 6286ms
/wiki/Plantilla:Aviso/doc 2021-12-30 21:34:32 UTC 3499ms
/wiki/M%C3%B3dulo:Date/ejemplos/doc 2021-12-30 19:02:11 UTC 12489ms
/wiki/Plantilla:Purgar/doc 2021-12-30 16:35:01 UTC 3026ms

Check the server response and contact your hosting provider if necessary.

Go to the diagnostics section to find out about all site issues known to Yandex. Sincerely, The Yandex.Webmaster robots

Happy 2022 everyone! Hugo Ar (talk) 15:37, 2 January 2022 (UTC)[reply]

Answered here. Greetings. Hugo Ar (talk) 12:35, 3 January 2022 (UTC)[reply]

Crappy GachaTubers Wiki

Could a steward please close this wiki? @Dmehus: stated in this topic that he was going to delete this wiki and Bad Quotev Users Wiki, also BQUW was renamed and rebranded and later closed, so there's no need to worry about it. Anyway, most (if not all) pages are not actual criticism and are instead just spreading rumours about GachaTubers. If the userbase wants a wiki about bad GachaTube content, then they should probably make a new one instead, and it should have a slightly different focus. FatBurn0000 (talk) 03:17, 4 January 2022 (UTC)[reply]

And I noticed that edits there need to be approved by moderators. He's flouting the Content Policy (Miraheze does not host wikis with the sole purpose of spreading an unsubstantiated insult, hate or rumors against a person or group of people) and the stewards must have forgotten about that. --YellowFrogger (Talk) 03:29, 4 January 2022 (UTC)[reply]
FatBurn0000, as I recall, I said that this is sort of meh, given the extremely low number of pages created. More importantly, I also indicated my preference would be for you, or someone else locally, to begin a discussion on the wiki, in a prominent location, and after at least seven (7) days have elapsed, then we could close it per the local wiki's request. Thanks. Dmehus (talk) 03:37, 4 January 2022 (UTC)[reply]
@Dmehus: The problem is, as @YellowFrogger: said, the wiki has moderation, so my edit will have to be reviewed by a moderator. FatBurn0000 (talk) 04:31, 4 January 2022 (UTC)[reply]
FatBurn0000 Since the wiki has only one local bureaucrat/sysop, whose only recent log actions have been to reopen the wiki, and since the wiki does have some content issues that you've noted above, the fact that the Moderation extension is enabled and there are no local administrators available to approve legitimate community discussion requests, or worse, is contrary to the very ethos of local community-controlled discussions. I've approved the outstanding edits by you and YellowFrogger in lieu of locally available moderators, and while Stewards could've granted you the local automoderated group on this basis, since you're seeking to start a community discussion, this is problem. As such, per this reasonable request, and because additionally there does not appear to have been any local discussion to enable the extension, even among local administrators, I have Yes check.svg disabled the Moderation extension. Should you encounter attempts to subvert the democratic process on that wiki, please {{ping}} me here or another member of the Steward team. Dmehus (talk) 04:45, 4 January 2022 (UTC)[reply]

Really Bad Admin Alert

His name is WellFiredToast. His wiki is called mightythornberry.miraheze.org. He blocked me permanently for no damn reason at all. He even revoked tpa and eMail. I never abused those ever! The user should be spoken to, then banned.

I never did anything wrong, I left a message on his meta talk page yet hasn’t responded. All I did was improve on the main page, this block is super unfair and I should be unblocked. TheCoolStranger45 (talk) 08:06, 4 January 2022 (UTC)[reply]

TheCoolStranger45, that's good that you left them a message on Meta Wiki, as that would be your first step. That being said, your tone here is not helpful, nor is calling the user an "ugly prawn." I would suggest posting a second message on their user talk page, on Meta Wiki, with a {{ping}} as well, and take a conciliatory approach. If they still do not respond in a few weeks, then we can revisit this. Dmehus (talk) 08:15, 4 January 2022 (UTC)[reply]

Morbius

I posted to this user's talk page three times now. I was blocked on their wiki for no reason and just want to be unblocked. I have no plans to edit Project Saramora, but I want my CentralAuth to show I am in good standing globally. –MJLTalk 04:45, 5 January 2022 (UTC)[reply]

@MJL: Note that I am not a steward or an admin. But, CentralAuth negated might be bad, but note that it doesn't fully indicate that a user has committed malicious acts or anything like that. I've been blocked on two wikis I haven't edited on, and several experienced Meta users have already been blocked on several wikis. Often times, a block cannot be taken seriously. Relax and and don't worry about it. --YellowFrogger (Talk)
@MJL:This user and all others have been cleared from the blocked list. The blocks were due to previous difficulties on a former wiki with bots and spammers and our misunderstanding of the existence of observers and the like on Miraheze who would visit the many wikis in such fashion. We apologise for the misunderstanding and hope future interactions may be more amicable! — Preceding unsigned comment added by Morbius (talkcontribs) 14:23, 5 January 2022‎
OK understood! (: --YellowFrogger (Talk) 16:41, 5 January 2022 (UTC)[reply]
@Morbius: Awesome, thank you and happy new year! <3 –MJLTalk 18:20, 5 January 2022 (UTC)[reply]

CheckUser request on a suspected Quarrow sockpuppet:

I have a good reason to believe this is Quarrow doing his usual vandalism tricks. These following diffs here are pretty consistent, with the first diff being an obvious hint that it's a sockpuppet. Also compare this same edit by Computer2003michael to this edit made by AVXUser, and you'll see that there's a pattern going on here, especially with the comparisons between this diff (which is the same one by the way) and this deleted photo, which I believe had a picture of someone in a diaper, which was uploaded by DiaperFan. Pinging Dmehus so he can investigate this in an orderly manner. --DarkMatterMan4500 (talk) (contribs) 18:54, 6 January 2022 (UTC)[reply]

Also, compare this edit summary made by Computer2003michael and every disruptive vandalism and/or other disruptive edits in general made by this user to this edit by LOTRMaster, as that particular edit is obviously vandalism. Same hatred, same behavior, same pattern, and same about everything, which can be seen from the edits, and the behavior appears to be quite obvious here. In general, Quarrow doesn't even try hiding the fact that he's evading locks, nor does he hide any of his "Quarrow" nonsense either. Hopefully, additional evidence I've provided is enough to warrant a check, and to do a sleeper check, so we can flush out all the sockpuppets he might have created with the IP range he might've used. --DarkMatterMan4500 (talk) (contribs) 03:37, 7 January 2022 (UTC)[reply]
This same user, Computer2003michael, has already been Yes check.svg locked globally for likely abusing interwiki and vandalism by Raidarr. --YellowFrogger (Talk) 03:44, 7 January 2022 (UTC)[reply]
@YellowFrogger: Yes, but that doesn't matter. It's still pending an investigation, so by doing this, we might even find a bunch of sleepers the user might have utilized under the same IP range. Also, that comment you posted above doesn't really help much, I'd like you to refrain from making unhelpful comments in the future, if you can. :) --DarkMatterMan4500 (talk) (contribs) 04:00, 7 January 2022 (UTC)[reply]
@DarkMatterMan4500: You did not like the nature of my comment, although I agree it didn't count. So my theory is that global locks can restrict access to other accounts. Anyway, I will try to limit this by avoiding this kind of comments. Thanks. --YellowFrogger (Talk) 05:01, 7 January 2022 (UTC)[reply]
@DarkMatterMan4500: These edits are also made to mark up or remove my inactivity. I don't have to say what users say on the noticeboards, so I don't want to be inactive in the project. — Preceding unsigned comment added by YellowFrogger (talkcontribs) 05:07, 7 January 2022 (UTC)[reply]
It is true that I have locked the account for vandalism at the time, spurred as well by the compelling signs of an LTA that I highly suspect to be true, as well as no faith in good change or further benefit to Miraheze while unlocked. However, I avoided locking for LTA pending proper confirmation from Stewards, as well as the fact I still need to have a proper LTA discussion with dmehus. I think the comment is made with good intentions and does not deserve to be struck as it was, though I confirm that this SN post is an appropriate follow up for the topic. This shouldn't have to become a discussion on peanut galleries, though for that matter nor should any user feel obliged to make edits to stave off a perception of inactivity that would be in no way accurate. At times withholding comments can indeed be the wiser move, but in any case continuing that tangent is probably best for a different discussion area. My 2c here. --Raidarr (talk) 09:58, 7 January 2022 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── @YellowFrogger: Thank you, and I also noticed you didn't sign your name, so I did the rest for you using the {{unsigned}} template. In the future, it's best you sign your name using the ~~~~ code, which I'm sure a lot of users may have pointed this out to not only you, but a lot of Mirahezians that come to contribute to this project. Hope this helps. :) --DarkMatterMan4500 (talk) (contribs) 11:46, 7 January 2022 (UTC)[reply]

@DarkMatterMan4500: Thanks! But remember that I'm not new to wikis, my device bug caused me to sign it with five tildes ~~~~~, so this if looks more like an accident, and the community shouldn't care for that. --YellowFrogger (Talk) 20:42, 7 January 2022 (UTC)[reply]
@YellowFrogger: I have already Yes check.svg replied to you on Discord. --DarkMatterMan4500 (talk) (contribs) 02:17, 8 January 2022 (UTC)[reply]
@DarkMatterMan4500: Facepalm flesh tone.svg I know --YellowFrogger (Talk) 16:22, 9 January 2022 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── @Dmehus: How about I place this request Symbol wait.svg on hold for a while, to see if a new account starts cropping up and repeating the same behavior? --DarkMatterMan4500 (talk) (contribs) 02:42, 9 January 2022 (UTC)[reply]

Some things I'd like to ask about

  1. Could you possibly close Horrible Music & Songs Wiki? Someone tried to adopt it, and the election took too long, so Worst Music & Songs Wiki was created instead, therefore, we don't need the wiki.
  2. Could you please reopen Amazing Scratch Projects Wiki? It was closed with no consensus much like the website reception wikis.

FatBurn0000 (talk) 06:42, 7 January 2022 (UTC)[reply]

1 is a duplicate premise of now two wikis that exist (a wikia port also using the 'horrible' flair in its name and the mentioned Worst M&S). It's possible the content is similarly pulled from one or the other wiki, as half of WM&S is from the direct wikia port. Unless substantial violations can be found though, the Stewards may prefer leaving the matter to local vote much in the same way as Crappy GachaTubers. --Raidarr (talk) 09:39, 7 January 2022 (UTC)[reply]
@Raidarr: About the HMASW I'm talking about, it is actually the first one, however for various reasons, this does not mean it should be the one that is kept. It was originally founded by CHICHI7YT, the owner of the Fandom version at the time, on September 23, 2018, due to the fact that the Fandom version was probably going to close soon considering that was around the time when reception wikis (especially negative ones) were being shut down on Fandom. However, for whatever reason, the Fandom version didn't close until eventually, a Fandom staff member discovered the wiki on September 30, 2020 and by the time that was happening, the Miraheze version had been expanded by outcasts and ultimately looked like it was deliberately made to duplicate and defame the original wiki. This caused the new owner to believe this is what it was, and as a result tried to get the wiki closed and made a new wiki for migration. However, a user replied to them here and the owner falsely believed that they were an actual global staff member (when they were not) and as a result thought that the request to close the wikis had been denied. However, since the election took too long and has now been duplicated, it should be closed. Also, what about ASPW? FatBurn0000 (talk) 02:49, 8 January 2022 (UTC)[reply]
1 is still likely to fall under community discussion unless it provides substantial content concerns. As for 2, that is entirely Steward discretion given the wiki's private nature. If it was the same type of circumstances as the website wikis it may be reopened; but if the editing was very minimal and no local contributors objected, it may be even clearer than TNRW and remain closed. --Raidarr (talk) 09:14, 8 January 2022 (UTC)[reply]

Checkuser Request for a possible ban evader

All The Tropes requests a Checkuser of User:Iloveicecream and User:Thistroperz

User:Iloveicecream is currently on a temporary block (scheduled to end at 2022-01-11T17:51:23) for multiple violations of section 2 of att:All The Tropes:Terms of Service followed by a violation of section 1 ("abusive behavior") of the same core policy.

User:Thistroperz displays the same idiosyncrasies in the use of wiki markup (or the lack thereof) and the English language that User:Iloveicecream displays.

If User:Thistroperz is the same user as User:Iloveicecream, then this is "evidence of ban evasion" which as per att:All The Tropes:How We Do Bans Around Here we consider to be grounds for a permanent ban without warning on the first occurrence. If this is the case, then we authorize Miraheze to block both accounts indefinitely on All The Tropes.

--Robkelk (talk) 00:49, 9 January 2022 (UTC)[reply]

@Robkelk: Could you provide a few examples of Iloveicecream using another account attempting to go around a block given to the said user? That would be most helpful. --DarkMatterMan4500 (talk) (contribs) 01:00, 9 January 2022 (UTC)[reply]
@DarkMatterMan4500:, this appears to be the first attempt (at least, the first attempt that we've spotted) of Iloveicecream attempting ban evasion. we have a zero-tolerance of ban evasion on All The Tropes, which is why we're requesting the Checkuser in the first place. --Robkelk (talk) 01:09, 9 January 2022 (UTC)[reply]
DarkMatterMan4500, the edits by Thistroperz are behind the Moderation extension, so Robkelk can't provide live diffs. That being said, I do see the behavioural similarities/traits Robkelk mentioned. Dmehus (talk) 01:14, 9 January 2022 (UTC)[reply]
I've approved this edit (after checking that it wasn't in violation of section2 of our Terms of Service) so that you have something to work with. --Robkelk (talk) 01:26, 9 January 2022 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── @Dmehus: Ah, okay then. :) --DarkMatterMan4500 (talk) (contribs) 02:38, 9 January 2022 (UTC)[reply]

Robkelk, I've Yes check.svg globally locked the illegitimate sockpuppet user account, and Yes check.svg guided the user via their main account. Please advise me if you should see any future, or, conversely, pre-existing user accounts behaving in a similar manner. Dmehus (talk) 03:11, 9 January 2022 (UTC)[reply]

Concerning behavior from a Meta patroller.

Are you aware that the patroller by the name of Bukkit recently vandalized a page on Terrible Shows & Episodes Wiki in response to a page they disagreed with? To be frank, this action is very concerning to me given that the user showed no signs of behavior like this previously. What I want is for the stewards to look into this to determine what should be done. Marxo Grouch (talk) 00:24, 10 January 2022 (UTC)[reply]

Marxo Grouch I agree the blatant vandalism is concerning, and especially so since the linked page is not particularly problematic, from a Content Policy or other policy perspective, but I'm uncertain as to what you're wanting Stewards to do here? Engaging in cross-wiki vandalism could be a reason to revoke Bukkit's patroller bit, but that would be best handled by a Meta administrator at Meta:Administrators' noticeboard. Unless you have significantly more evidence of vandalism or disruptive behaviour across wikis, or have evidence of abusing multiple accounts, I don't really see a need for Steward involvement here. Dmehus (talk) 00:32, 10 January 2022 (UTC)[reply]
Surprised that such a communicative user, Bukkit, patroller on Meta, couldn't hold back the urge to vandalize (remove content) on Miraheze's own wiki. I don't think it's necessary yet, although the stewards who evaluate it, a revocation. In this case, an attention to what this user does lately is necessary. But that's sometimes just him showing what he really is. --YellowFrogger (Talk) 00:36, 10 January 2022 (UTC)[reply]

System problem

Hello. I just found a problem in the system. All usergroups from all wikis send to this page and not to the wiki page about this group. Also groups like administrators and bureaucrats write their system only in English and not in other languages. Thanks! AlPaD (talk) 20:34, 10 January 2022 (UTC)[reply]

@AlPaD: This was probably a MirahezeMagic update yesterday, it also happened to me (See about this in GitHub: [1]) --YellowFrogger (Talk) 20:41, 10 January 2022 (UTC)[reply]
Thank you! AlPaD (talk) 21:02, 10 January 2022 (UTC)[reply]
@AlPaD: The link change was done recently in a bid to aid users and wikis in understanding some of these user groups better. You can change where the page links to by changing the link in your wiki's local MediaWiki:Grouppage-<name of group> (e.g. sysop for admin, bureaucrat for bureaucrats, etc.). Agent Isai Talk to me! 20:45, 10 January 2022 (UTC)[reply]
Thank you! AlPaD (talk) 21:02, 10 January 2022 (UTC)[reply]

Delete this wiki

Hello. I am requesting the deletion of the following wiki:

  1. gtavariantswiki

The name, scope, and description are perfect for me. However, the wiki is totally messed up full of pages and inaccurate edits. I could even ask to restore it to Phabricator, but due to server migration, we can't do that until January 14th. I need this wiki deleted to soon request another one of a similar scope. --YellowFrogger (Talk) 21:54, 11 January 2022 (UTC)[reply]

YellowFrogger, though TheNino is also a bureaucrat and administrator on that wiki and is a relatively equal contributor to you, I do know that you and TheNino often work and collaborate with each other roughly in sync, so this has been Yes check.svg done. Note, though, that the wiki database still exists, it's just marked for deletion and users will see a 404-like error page. The actual database will not be dropped for at least two weeks from today, and even then, it is at SRE's discretion (though, in practice, it's usually when I nudge the SRE team member chiefly responsible). :) Dmehus (talk) 04:00, 12 January 2022 (UTC)[reply]
Hello, good to see you back, @Dmehus:, and thanks for taking the action. Universal Omega said they are no longer performing wiki restores by migration, order given by Reception123. I don't know why, but it makes me think that maybe this process takes time to complete. --YellowFrogger (Talk) 04:22, 12 January 2022 (UTC)[reply]
wikis can be deleted via ManageWiki, without the database being dropped. We are holding off on dropping databases or completely resetting wikis until after the migration, but Stewards can still mark wikis as deleted.
In addition to what Universal Omega said above, I would also just add that the reason SRE is likely holding off on import requests until after the migration is a combination of things, ostensibly owing to SRE being very busy with the migration and also to either potential strain on the servers as the migration of data takes place and/or essentially freezing manual changes to the database servers. Dmehus (talk) 04:34, 12 January 2022 (UTC)[reply]
I'm not seeing problem with maintaining 404 error page, this is normal/typical of non-existent wiki. Also, @Dmehus:, could you look at these two recent requests in the administrators noticeboard?. --YellowFrogger (Talk) 04:42, 12 January 2022 (UTC)[reply]

Requesting a Dormancy Policy exemption for Zendari

Hello! I'd like to request a dormancy policy exemption for https://zendari.miraheze.org/. We've been continuously vandalised over the past few months, so I set the wiki as private, however I've received a few requests to open up the wiki again because people are still reading the articles and still want to know some history behind everything in the contest as we've put lots of effort into it. However I'm afraid to put it as closed or inactive because we may risk deletion (and I've heard that someone can claim the wiki as their own, which would likely mean that a vandaliser would take it over - although I'm not sure if this is true or not), so I'd like to request for our wiki to be exempt from the dormancy policy rule. I think I've cleaned up all the vandalism that happened so putting it as read-only would be a great solution until further notice. We created a fantasy world and it would be a real shame if everything was lost due to inactivity. Hope it's alright! Stewen (talk) 19:00, 12 January 2022 (UTC)[reply]