Requests for Comment/ApexAgunomu global ban appeal

Following an appeal sent to Stewards, this appeal for ApexAgunomu's global ban is now forwarded to the community. The following is her appeal:

"I am writing to request that my account ApexAgunomu be unlocked globally so I can edit on Miraheze again. I realize that I have had multiple issues with my behavior in terms of spamming, saying bad words, and creating extra accounts to get around local blocks on some wikis. I realize that none of that behavior was acceptable in any way, especially after receiving multiple warnings, and I apologize for disregarding the warnings and advice I received. I understand that if this appeal is granted it will be my last chance to be a part of the Miraheze community, and I am willing to adhere to any unlock conditions that may be given. I also promise to obey all the rules on all wikis from now on and will not make any extra accounts for any reason.Thank you for your consideration."

Now before the community is the chance to either support or oppose this appeal. For reference, ApexAgunomu was globally banned by the community following this Request for Comments. She was upgraded to long-term abuser status by Raidarr for evading her lock plus abusive behavior after her ban so should this proposal succeed, she would also need to appeal her LTA lock to Stewards. Agent Isai Talk to me! 02:41, 29 September 2022 (UTC)

Proposal 1 (Accept appeal)
The appeal sent by ApexAgunomu is accepted and her account is unlocked and her global ban rescinded.

Support

 * 1) There's a good chance I'll be alone here. I admit that ApexAgunomu made me do some hard work to proverbially stand here. I did not participate in the original RfC imposing the ban, and I cannot say how I would have argued if I had. The first thing that became apparent to me about this user was the presentation of several conflicts among various Miraheze communities. Namely Test Wiki, Qualitipedia, Miraheze Developers, and Polandball Wiki. I want to note the vast contrast in the behaviors on these projects to others where Apex was acting apparently as a distinguished WikiGnome as is the case on Pokémon Wiki, PolCompBall Wiki, and even the Polandball Wiki outside of discussion threads. It would appear that this user is specifically influenced by communities with demonstrable levels of toxicity or "memeity", especially considering that the more formalized and process oriented projects receive her most constructive contributions. It appears that the blocks from Miraheze projects which have been imposed upon Apex are not all entirely due to actions on a relevant project. I would safely disregard the blocks on Awesome Games Wiki, Terrible TV Shows Wiki, Crappy Games Wiki, and Qualitipedia central as largely unjustified and apparently borne either of the actions of others (blocks on other Miraheze projects) or impatience, and I question how much a Miraheze project may be allowed to police a user's own userspace. Miraheze Developers Wiki and Test Wiki were the most appropriately administered blocks, with clear reasoning, consensus, and a reasonable expiry. The remaining blocks, including Meta and Polandball Wiki can be partially justified, and should probably be applied specifically to the user's problem areas until she can be guided into proper contribution patterns. I also believe that there is a good chance that the departure of Qualitipedia will mean improvement for many of the users who struggle to positively contribute on Miraheze. Ultimately, I would like to see every community ban appealed. Simply, I do not believe that we are a community to exile members, nor do I believe that is the most constructive and growth oriented experience for problem users. In addition to this, off-Miraheze activity is important information to alert the community of potential problems with particular users, though is not a very strong argument for restricting participation. So, here I will  the acceptance of the appeal of ApexAgunomu, only with local autonomy. I would advise that local action be reevaluated and specified—projects where the problem area was discussions should block discussions and try to make ApexAgunomu a constructive contributor in other areas. The repeal of this community ban should not result in the automatic removal of individual local sanctions, which should be left to local process. This includes IRC, Discord servers, and local Miraheze projects. I believe it is best to guide problem users to the proper outlet and skills for being a proper community member.  dross  (t • c • g) 10:29, 29 September 2022 (UTC)
 * Some notes. The final breaking point in the stewardship of Dmehus was attempting to maintain chance after chance for Apex, which was successively blown on Meta without the help of any other community including the reception wikis (though Apex mucked about on them independent of any other posting that took place which may have encouraged her). Most of the record actually exists on communities outside of QP, which is a false positive given blocks on there were unnecessarily extended to other wikis (although I argue the block was sincerely valid on QP central, and was accompanied by multiple chances and warnings on the wiki itself and the attached discord at the time). This would be more persuasive to the unlock of users who were negative specifically because of QP, while Apex's record is born and raised on Wikipedia and then Miraheze central communities with only tangential intervention on QP itself. I'm skeptical that Apex was a particularly successful Gnome of any sort in her time, but I may concede a bias after having been on the front line of reports and cleanup from a diverse array of communities. Off platform wise the spam, nonsense and insincerity was continuous in any discord, irc or email she was involved in. Miraheze should not be a place to exile without good reason but it should not subject itself to violation time and again out of a sense of misguided mercy for one who systemically exploits the mercy. I hope voters will recall just how nasty and frequent this was, and not be so quick to forget. --Raidarr (talk) 10:37, 29 September 2022 (UTC)

Abstain

 * 1)  I am willing to give them a second chance, however, considering their actions on QP and Polandball wiki, plus the usage of LTA's, has made me hesitant. LovingHaydeL (talk to me uwu!)
 * 2)  Per above ZeusDeeGoose (talk) 10:52, 29 September 2022 (UTC)

Oppose

 * 1)  I have had personal experience with Apex and have found them to be increasingly disruptive to Miraheze and its projects. The fact that Apex is appealing this global ban after such a short period of time is concerning to me, and as such I have no intention of supporting this appeal at this time. Thanks - BrandonWM (talk • contribs • global • rights) 04:22, 29 September 2022 (UTC)
 * 2)  I probably would've supported this if requested in a few more months and/or they had not been trying to evade the lock with LTA behavior, but because of that behavior I can not support this at this time. I believe in second chances, which is why I am weak opposing, but such a behavior as demonstrated by them, and the fact that they request an unlock so soon, makes me think they have not actually learned anything from this. Universal Omega (talk) 04:29, 29 September 2022 (UTC)
 * The essential piece to understand is that this is so far beyond a second chance in the broader picture of the user in question. --Raidarr (talk) 10:11, 29 September 2022 (UTC)
 * 1) I am unable to support due to the minimal amount of time between ban and appeal, and the usage of sockpuppets to evade said block. I suggest that Apex appeals again in a few more months, preferably next year (not necessarily mid/late 2023) in order for me to support (albeit weakly) an appeal. I’d also like to note behavior off-wiki (Fortestwiki, to be exact) she has made a category (forgot exact name) along the lines of “Hi r****ds” a few months ago, which is the same behavior that Apex had here, which makes me believe that she hasn’t learned anything from the past (although, again, it’s off-wiki); but I mostly agree with UO, mainly on the last part. TL;DR: Wait a few months. --  Bukkit  [ cetacean needed ] 07:36, 29 September 2022 (UTC)
 * 2)  I'm sorry, but I absolutely cannot support this under any circumstances. She's been given too many chances by a former Steward, but she constantly kept breaking her promises, making her statements absolutely worthless. If she was ACTUALLY sorry for what she has done, then she needs to prove that, without a doubt in my mind. --DarkMatterMan4500 (talk) (contribs) 11:22, 29 September 2022 (UTC)

Comments

 * 1)  I'd like to add that if indeed this resolution passes, even though I've voted against it, there should be severe, community-imposed restrictions upon ApexAgunomu's reentry to the community. I'm strongly opposed to the idea of Apex back on Miraheze, let alone without any restrictions. Thanks - BrandonWM (talk • contribs • global • rights) 04:37, 29 September 2022 (UTC)

Proposal 2 (Decline appeal)
The appeal sent by ApexAgunomu is declined and her global ban remains.

Support

 * 1)  Per rationale above. I wouldn't consider an unlock appeal for at least another 6 months. Thanks - BrandonWM (talk • contribs • global • rights) 04:23, 29 September 2022 (UTC)
 * 2)  Per what I said above in proposal one. Universal Omega (talk) 04:31, 29 September 2022 (UTC)
 * 3)  Apex has sockpuppeted consistently every month or so in the time I was Steward - as far as I'm concerned the timer has hardly even begun. Apex has sent absolutely vile emails in that time and then followed up with bullshit sincere emails pretending nothing happened. Apex asked countless stupid questions that Apex already knew about the appeal process and the consequences of doing stupid things just after doing them. Apex hasn't changed a bit and while I understand the comedy in putting this out to vote to see it snowballed to death I still find it somewhat absurd to even put this to vote when the Steward context alone has volumes of evidence that Apex is a bad-faith actor who hasn't changed a bit since the day of the initial ban. I can quote some gems if necessary. For efficiency's sake it was odd to split this RfC in such a way that people would be making functionally the same vote twice (oppose one and support the other) but I digress. Apex realizes nothing, apologizes for nothing, makes up last chances like the US government prints money and is wasting our time even now. Unless you see a link with a concrete background on something credible like wikipedia 100% approving an about-face, it would be irresponsible for the Miraheze community to ever appeal an unblock. In 22, 23, or indeed 24. Some things never change. Get evidence to fine comb through before you ever consider supporting this. Apex has been trolling the time of Miraheze for years and of other platforms for years before. In this respect Apex is one of the best trolls Miraheze has ever seen. Don't be fooled. --Raidarr (talk) 09:09, 29 September 2022 (UTC)
 * I would certainly like to know some of these quotes. I think that is important information for this process. dross  (t • c • g) 10:30, 29 September 2022 (UTC)
 * This is unfortunately the last minute before a two-day downtime; afterwards I can sift through the emails. If they desire, current stewards will also have forwarded copies of some of these emails available (with digging). --Raidarr (talk)
 * 1)  Considering she's recently been evading her global locks numerous times, she needs to be away from the wikis for a while, and maybe reflect on her horrible behavior. Consider this a warning, . If you are truly sorry for what you did, then I would've gladly given you another chance. Unfortunately, you've been giving us nothing but empty promises to stop the repeated disruption ever since you've been unlocked 6 months ago. This is like explaining physics to a toddler. --DarkMatterMan4500 (talk) (contribs) 11:30, 29 September 2022 (UTC)
 * 2)  Per everyone above. It's clear that this is her being insincere yet again, and taking into account her frequent sockpuppetry I don't see any reason to trust this appeal. Marxo Grouch  (talk) 12:48, 29 September 2022 (UTC)