Steward requests/Global
Add topic
This page can be used to request Account Vanishes, global locks (including self-locks), global IP blocks, or for either of these to be removed. If reporting vandalism-only accounts, make sure they fit the global standard definition for vandalism-only accounts: there must be no or almost no constructive editing behavior, and the disruptive behavior should be occurring on multiple wikis. Please note that accounts on Miraheze cannot be fully deleted! The closest to this is to submit a GDPR request to Trust and Safety. This will lock the account, strip all attached personal data, and anonymize the username. This will not remove edit history. To make a vanish request, global lock or unlock request, copy the following code, and place it at the very bottom of this page. Replace every section as needed: == <Username of user being locked> == {{status}} *{{LockHide|username1|hidename=1}} <!-- include hidename=1 if you want to hide the username as it's offensive --> *:Include your reason here ~~~~ If you're including multiple accounts in your report, format it as follows: == <Username of user being locked> == {{status}} *{{LockHide|username1|hidename=1}} <!-- include hidename=1 if you want to hide the username as it's offensive --> *:Include your reason here ~~~~ |
|
Archives of Steward Global requests [e] |
---|
Requests[edit | edit source]
Vanish for me and my alts[edit | edit source]
- Person16384 (talk • contribs • block • CA • lwcheckuser), Person32768 (talk • contribs • block • CA • lwcheckuser), Person65536 (talk • contribs • block • CA • lwcheckuser), Object16384 (talk • contribs • block • CA • lwcheckuser), La Personne Anonyme (talk • contribs • block • CA • lwcheckuser)
- I will be ditching Miraheze and my 16384 label behind. Person16384 (talk) 12:25, 2 October 2024 (UTC)
- Given repeat vanish and unvanish requests, we will not action this until 9 October. Please let us know if you'd like to proceed at that time. --NotAracham (talk • contribs • global) 19:53, 4 October 2024 (UTC)
- Yes, proceed with the operation. Person16384 (talk) 06:30, 9 October 2024 (UTC)
- Proceeding now. Please note that you will not be eligible for an unvanish for 30 day from action. --NotAracham (talk • contribs • global) 16:00, 9 October 2024 (UTC)
- This is now Done. --NotAracham (talk • contribs • global) 16:05, 9 October 2024 (UTC)
- Proceeding now. Please note that you will not be eligible for an unvanish for 30 day from action. --NotAracham (talk • contribs • global) 16:00, 9 October 2024 (UTC)
- Yes, proceed with the operation. Person16384 (talk) 06:30, 9 October 2024 (UTC)
Global lock for TristanStoddard[edit | edit source]
- TristanStoddard (talk • contribs • block • CA • lwcheckuser)
Spambot. Justarandomamerican (talk) 22:14, 5 October 2024 (UTC)
La rivbi controversy[edit | edit source]
- name hidden (talk • contribs • block • CA • lwcheckuser)
- I want this account to be gone because, I went too far with something and made a controversy. I don't really want to talk about it. La rivbi (talk) 03:22, 6 October 2024 (UTC)
- @La rivbi: to be clear, are you requesting a reverible vanish, or a permentant vanish including removal of all assosiated personal information on your account(GDPR)? --╚PixDeVl╝ (Talk ✦ Contributions ✦ CentralAuth) 14:37, 6 October 2024 (UTC)
- Reversible is fine. La rivbi (talk) 19:26, 7 October 2024 (UTC)
- @La rivbi: to be clear, are you requesting a reverible vanish, or a permentant vanish including removal of all assosiated personal information on your account(GDPR)? --╚PixDeVl╝ (Talk ✦ Contributions ✦ CentralAuth) 14:37, 6 October 2024 (UTC)
- I want this account to be gone because, I went too far with something and made a controversy. I don't really want to talk about it. La rivbi (talk) 03:22, 6 October 2024 (UTC)
- Account locked, vanish initiated. Marking as Done. --NotAracham (talk • contribs • global) 01:18, 8 October 2024 (UTC)
Vanish for this account[edit | edit source]
- name hidden (talk • contribs • block • CA • lwcheckuser)
Done with this community can't continue further. Xaloria (talk) 04:12, 6 October 2024 (UTC)
- This request will be actioned in 7 days, please update us on this request if you decide to cancel it. Once actioned, this account will not be eligible for an unvanish until at least 30 days have elapsed. --NotAracham (talk • contribs • global) 04:24, 6 October 2024 (UTC)
- @NotAracham I see the result of this in and change in my decision not interested in vanishing. Xaloria (talk) 08:46, 8 October 2024 (UTC)
- Closing per change of decision. --NotAracham (talk • contribs • global) 15:59, 9 October 2024 (UTC)
- @NotAracham I see the result of this in and change in my decision not interested in vanishing. Xaloria (talk) 08:46, 8 October 2024 (UTC)
Global lock for User:システム's sock[edit | edit source]
- name hidden (talk • contribs • block • CA • lwcheckuser)
This account's name is the same as jawiki user. he already founded システム's sockThis user is confirmed as システム's sock in local and システム is different from that jawiki user.so,I think It violates Username Policy.--Ama-ryu (talk) 12:52, 6 October 2024 (UTC)change sentence.--Ama-ryu (talk) 12:49, 7 October 2024 (UTC)
- Confirmed and this is now Done --NotAracham (talk • contribs • global) 01:21, 8 October 2024 (UTC)
Global Lock request for LKKK[edit | edit source]
He repeatedly committed vandalism on rswiki and continued to do so after being warned three times by sysop Honglan233 (talk) 13:55, 6 October 2024 (UTC)
- Considering this has been effectiely dealt with via local block(not entirely sure why not an indef but) and there is no sign of cross-wiki abuse I don't really see much use in a lock. If one of my fellow GAs or a Steward thinks it's worth it, I have no objections, I just don't see a need. --╚PixDeVl╝ (Talk ✦ Contributions ✦ CentralAuth) 14:32, 6 October 2024 (UTC)
- The lock here is to prevent cross-wiki vandalism, I always think that locks should be used to prevent someone from vandalizing other wikis, not locking after they've already vandalized multiple wikis, that's my personal opinion : ) Honglan233 (talk) 15:06, 6 October 2024 (UTC)
- Already dealt with via the other report provided, leaving as not-done. --NotAracham (talk • contribs • global) 01:26, 8 October 2024 (UTC)
- The lock here is to prevent cross-wiki vandalism, I always think that locks should be used to prevent someone from vandalizing other wikis, not locking after they've already vandalized multiple wikis, that's my personal opinion : ) Honglan233 (talk) 15:06, 6 October 2024 (UTC)
Global Blocks for 87.120.102.42[edit | edit source]
- Status: Done
This is NordVPN and it's not blocked.by Buehl106·Talk·e-mail 12:19, 7 October 2024 (UTC)
Global Block for 153.92.40.162[edit | edit source]
- Status: Done
This is NordVPN. by Buehl106·Talk·e-mail 04:26, 9 October 2024 (UTC)
TauDudeBlobber[edit | edit source]
- TauDudeBlobber (talk • contribs • block • CA • lwcheckuser)
- I am making a reversable vanish request. TauDudeBlobber (talk) 23:02, 10 October 2024 (UTC)
- Done If you want to unlock, please contact us at [email protected] or via Discord. --1108-Kiju/Talk 23:21, 10 October 2024 (UTC)
Global lock for 昨日褪色[edit | edit source]
VO on rswiki:
continued to destroy rswiki after being repeatedly banned by the administrator Honglan233 (talk) 02:33, 13 October 2024 (UTC)
- There is no basis for a global lock; the user in question is likely a well-meaning but unintentionally destructive (i.e. CIR user), and any action against them should be left to local administrators. Tali64³ (talk | contributions) 03:16, 13 October 2024 (UTC)
Electric Fan 1[edit | edit source]
- Electric Fan 1 (talk • contribs • block • CA • lwcheckuser)
The user vandalised and misgendered the webcomic author of which our entire wiki is about under 12 hours of account registration, which I can only assume is intentional disruption.
- 00:36: Account registered (Special:CentralAuth/Electric Fan 1)
- 08:48: Constructive edit: Add some parameters to a template (mh:rainverse:Special:Diff/34869)
- 08:49: Constructive edit: Fix text in previous edit (mh:rainverse:Special:Diff/34870)
- 09:19: Misgendering edit (mh:rainverse:Special:Diff/34871)
- BlankEclair (talk, contribs, CA) 09:40, 14 October 2024 (UTC)
- There is no basis for CVT action - in fact, looking at the suppressed revision, I don't think said user is even unintentionally disruptive. Adding a transgender person's birth name, as long as it's handled tastefully and respects their currently gender identity, is not inherently problematic; however, adding said birthname as one of their nicknames is iffy and probably warrants removal, but I disagree with an indefinite block with no warning. Tali64³ (talk | contributions) 13:27, 14 October 2024 (UTC)
- What constitutes "tasteful" deadnaming? 183231bcb (talk) 14:17, 14 October 2024 (UTC)
- Note: This is my personal opinion and does not reflect the opinions of the CVT team as a whole.
- If a trans person's birth name (or "deadname") is brought up as a part of their backstory, it is fine - a trans person changing their name as part of their transition does not change the fact that they were once known by another name. (using my name as an example, "Tara, formerly known as Tali, is a transgender woman who is 16 years old.")
- If a trans person's birth name is portrayed as their "correct" name or only name or is otherwise used to disparage the person, it is not fine. (e.g. "Tali, who calls himself 'Tara', is a 16-year-old boy who believes that he is a woman.")
- There are people who may disagree with this stance; that is fine, since they are just expressing their opinion. In any case, while I don't believe that CVT action is necessary for this case, the local administration of the Rainverse Wiki is free to govern however they want as long as they respect the wiki governance policy. Tali64³ (talk | contributions) 14:40, 14 October 2024 (UTC)
- Tali, I need to disagree with you here in part - different communities have different handling around deadnaming, and deadnaming can be a harassing action in violation of Global Conduct policy in situations of clear malicious intent. For now, this is a matter that can be handled locally, and has been in a way which is within their rights as wiki admins.
- @BlankEclair: please do let us know if this becomes a 'repeat customer' situation in which global CVT action is warranted. If a local policy clarification on deadnaming of subjects doesn't already exist, I would also encourage one to be crafted and made available on your wiki. --NotAracham (talk • contribs • global) 19:25, 16 October 2024 (UTC)
- Thanks, we'll keep you updated. We are also in the process of creating a local policy on deadnaming.183231bcb (talk) 01:47, 17 October 2024 (UTC)
- What constitutes "tasteful" deadnaming? 183231bcb (talk) 14:17, 14 October 2024 (UTC)
- "Note I am not CVT so do not think I am one" While they do kinda fit this requirement "there must be no or almost no constructive editing behavior" they don't fit "and the disruptive behavior should be occurring on multiple wikis" as Rainverse is one wiki and all that is needed is a local block and nothing more unless the user starts causing more damage to other wikis he is on, impersonates other important users, and more global lock worthy offenses. IMO the Rainverse local block case is way too overkill like give them a warning or a chance while yes I do tend to also go a little overkill on my CW blocks. I would go with on most offenses just giving them a warning or reminder that their editing isn't helpful or unneeded and if they chose to disregard it then I give them the foot for some time depending on their severity of their disruption not saying you have do this as not everyone mods the same way. I understand that some are strict, go with the flow, lenient, or whatever their administration style is so take this with some thought and if you don't agree that's ok not everyone agrees on the same thing. TheFunny339YoshiPlushGuy (talk) 16:04, 14 October 2024 (UTC)
Global lock for UPV[edit | edit source]
UPV on rswiki,and refused to change the user name after being warned by the administrator Honglan233 (talk) 11:28, 19 October 2024 (UTC)
- Mocking a politician does not necessarily rise to the level of global lock. Already dealt with locally, closing as not done. --NotAracham (talk • contribs • global) 17:04, 19 October 2024 (UTC)
Global lock for UPV[edit | edit source]
- Cumstain324 (talk • contribs • block • CA • lwcheckuser)
Troll username. Justarandomamerican (talk) 19:31, 24 October 2024 (UTC)
- Robot clerk: Done by PixDeVl. Waki285-Bot (talk) 21:19, 24 October 2024 (UTC)
User N*GGA[edit | edit source]
Cross-wiki vandalism BZPN (talk) 11:34, 4 November 2024 (UTC)
- + all their edits should be hidden because they contain offensive content. BZPN (talk) 11:44, 4 November 2024 (UTC)
Global lock for RobertCoomer22[edit | edit source]
- RobertCoomer22 (talk • contribs • block • CA • lwcheckuser)
Cross-wiki spam/self-promo. —k6ka 🍁 (Talk · Contributions) 17:38, 5 November 2024 (UTC)
Global lock for Andre Hicks and MadMan Hicks[edit | edit source]
- Andre Hicks (talk • contribs • block • CA • lwcheckuser)
- MadMan Hicks (talk • contribs • block • CA • lwcheckuser)
- Vandalism only accounts and sock puppet of locked user called Gordon Hicks which was locked for MAA. TheFunny339YoshiPlushGuy (talk) 15:03, 8 November 2024 (UTC)
- Locked and blocked. Done --NotAracham (talk • contribs • global) 16:16, 8 November 2024 (UTC)
- Vandalism only accounts and sock puppet of locked user called Gordon Hicks which was locked for MAA. TheFunny339YoshiPlushGuy (talk) 15:03, 8 November 2024 (UTC)