Wikipedia:Arbitration/Requests/Case

Requests for arbitration

Arbitration Committee proceedings

• recent changes
• purge this page
• view or discuss this template

Case requests

Request name	Motions	Initiated	Votes
Malik Shabazz		18 August 2015	{{{votes}}}

[edit]

Open cases

Case name	Links	Evidence due	Prop. Dec. due
Backlash to diversity and inclusion	(t) (ev / t) (ws / t) (pd / t)	10 Oct 2024	24 Oct 2024

[edit]

Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Clarification and Amendment requests

Request name	Motions	Case	Posted
Amendment request: Palestine-Israel articles (AE referral)	Motion	(orig. case)	17 August 2024

Arbitrator motions

No arbitrator motions are currently open.

Malik Shabazz

Initiated by Georgewilliamherbert (talk) at 01:06, 18 August 2015 (UTC) Initiated by ceradon (talk • edits) at 01:08, 18 August 2015 (UTC)

Involved parties

• Ceradon (talk · contribs · blocks · protections · deletions · page moves · rights · RfA), filing party
• Georgewilliamherbert (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Malik Shabazz (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Chillum (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Mike V (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• KTC (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Brad Dyer (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Confirmation that all parties are aware of the request

• [1]
• [2]
• [3]
• [4]
• [5]

Confirmation that other steps in dispute resolution have been tried

A case of possible administrator abuse; DR unnecessary.

(for the record - Georgewilliamherbert (talk) 01:27, 18 August 2015 (UTC))

• Malik warned [6]
• Malik blocked and reblocked [7] (Chillum, Mike V, and KTC)

Statement by Ceradon

I believe we may have a case of abuse of administrator tools. The earliest example is likely here: [8], where Malik Shabazz revdels one of his own disparaging comments. Then, here: [9], where Shabazz says "suck my dick, ass hole" while giving Brad Dyer an ANI notice. Then here, [10], where Shabazz says, "No, you can suck it, sonny boy. What'll you call me next, nigger?". Now, RevDel criterion 3 states that "grossly inappropriate threats or attacks" may be revdelled. However, Shabazz, despite (or in spite of) his block, unrevdels that particular diff with the summary: "Restoring the truth -- you people can ignore this is [sic] you want, I won't". On his talk page, he says, in reference to Chillum, "You can suck my dick, too, asshole" [11]. And here [12], Shabazz states: "Now when the fuck is somebody going to address the fact that the Jewboy is harassing me? Or is only okay to hound niggers off Wikipedia?" Our policy on administrator conduct states: "Administrators are expected to lead by example and to behave in a respectful, civil manner in their interactions with others. Administrators are expected to follow Wikipedia policies and to perform their duties to the best of their abilities. Occasional mistakes are entirely compatible with adminship; administrators are not expected to be perfect. However, sustained or serious disruption of Wikipedia is incompatible with the status of administrator, and consistently or egregiously poor judgment may result in the removal of administrator status." Shabazz, on August 8, revdeled one of his own disparaging comments. It begs the question, what else has he hidden. How much else has flown under the radar. Shabazz has been an administrator for 8 years. I hate finger-wagging, but he should know better. I think there is enough material here for a case. Thank you, --ceradon (talk • edits) 01:08, 18 August 2015 (UTC)

I should add, that Shabazz was blocked by Chillum for 2 days as a result of personal attacks., and reblocked by Mike V for misuse of talk page privileges, and then reblocked again by KTC for abuse of admin tools. --ceradon (talk • edits) 01:13, 18 August 2015 (UTC)

• @L235: Done. --ceradon (talk • edits) 01:24, 18 August 2015 (UTC)
• @Drmies: That is suggestive, and I have struck it. But I honestly hope this isn't a permanent desysop. Malik was provoked, it's easy to see, but it doesn't excuse his behavior, and his use of admin tools while blocked. Malik is angry. He should have a time to cool down. But if he is angry, it should not be at our peril. Leaving a person who is pissed off to infinity with the keys to the castle is the fucking height of stupidity. A temporary desysop was in order. But now that he no longer has his tools, I would probably want the Committee to suspend this case and allow the community to discuss it further. Maybe if there is consensus for a desysop, the desysop can stand, and if there isn't it can be removed. That's up to the Committee though. --ceradon (talk • edits) 02:41, 18 August 2015 (UTC)
• I don't know if the Committee will find enough evidence to take a case, and I don't have any comment on that. But if the only think that can be used against Malik is what I have brought here today, I believe he should be allowed his bit back. Malik works in some very contentious and difficult areas, and endures a massive amount of hate for it (the RevDel log on his talk page is evidence enough). To leave him desysopped would be an absolute and unequivocal injustice incomparable to anything I've seen on Wikipedia. For all the shit he takes, he is allowed one misstep, I think. --ceradon (talk • edits) 03:49, 18 August 2015 (UTC)
• In regards to whether this should be full case: I think the conduct of Brad Dyer should be examined. And, since there is at least the possibility that this might result in a permanent desysop, I think a full case is necessary. --ceradon (talk • edits) 04:00, 18 August 2015 (UTC)

Statement by Georgewilliamherbert

Malik and Brad Dyer entered into a content dispute which apparently turned nasty on both sides (documented here. Malik appears to have taken it far further including a number of personal attacks and eventually a block of him, him doing a page unprotect through the block [13](Chillium), and block extension (KTC). Having used admin functions in a personal dispute with other users through a block, it appears that a temporary desysop may be required, possibly by motion. Full case may or may not be required. Malik is not known to me to have had behavior issues prior to this incident, this is unlike him.

• Yeah, I had a typo that caused subst not to, and it took forever for mine to "take effect", but yes a merge is fine. I'm going to grab some header stuff out of my filing and add it here. Georgewilliamherbert (talk) 01:25, 18 August 2015 (UTC)

Additional note: Someone with some time to do so needs to closely examine the discussions leading up to the bad behavior for taunting or other behavior that might explain why a longstanding well liked admin suddenly reacted like this. I haven't yet and it needs to be done, and I don't have enough time to do so until later tonight. Georgewilliamherbert (talk) 01:36, 18 August 2015 (UTC)

Statement by Malik Shabazz

This is a copy of the e-mail message I sent ArbCom last night. "Under a cloud" my ass.

I initiated a complaint at AN/I because Brad Dyer, one of the dozens of pro-Israel single-purpose accounts that plague Wikipedia, was harassing me. You can read (what's left of) my complaint to see the details. What nobody seems to understand is that it should never be acceptable to refer to a Black man as "sonny boy". Brad Dyer has successfully hounded me off Wikipedia. You can all suck my balls, assholes, because all you did was delete my complaint.

So please take my tools. And go to hell.

Sincerely,

Malik Shabazz (sent 01:47, 18 August 2015 (UTC))

And Chillum, I was wrong to call the people at AN/I jackasses. I should have just called you a jackass. You didn't (and still don't) give a fuck that somebody was harassing me, but when I used the word Jewboy that got your attention. I'll reiterate: The Jewboy has chased the nigger off Wikipedia. Congratulations. — Malik Shabazz ^Talk/_Stalk 17:16, 18 August 2015 (UTC)

Statement by Chillum

The facts of this case are clear and not much is left but interpretation. WP:ADMIN says "Administrators are expected to lead by example and to behave in a respectful, civil manner in their interactions with others." These are not just pretty words for me, they are policy and they are a damn good idea.

In my opinion the abuse given out by Malik Shabazz is incompatible with being an administrator. We just cannot have admins calling people "Jewboy" and expect to be taken seriously.

Beyond the conduct unbecoming an admin we have at least two examples of abuse of admin tools. The revdel of his own comment which contained a personal attack in an apparent effort to hide it and the use of the revdel tool while blocked to restore his own comment which also contained a personal attack.

I feel the evidence in this case will be well documented, however if diffs are desired for anything I have claimed I will happily provide them. I think it is important that the community see that we do indeed have civility standards for at least our administrators. Chillum 01:38, 18 August 2015 (UTC)

@Zero0000: Could you show me some diff that indicates that the revdel of the personal attack was done out of a sense of regret rather than a desire to conceal that behaviour? I admit I am not familiar with the context of the post and subsequent revdel. Chillum 02:05, 18 August 2015 (UTC)

@Zero0000: I concede the possibility. It changes little in my opinion as that was the act I had the least objection too. Chillum 02:27, 18 August 2015 (UTC)

For those who wish for him to have his admin status restored based on this being an isolated incident I can certainly hold out hope for that myself. However so far all we have gotten from this user is more insults after the block, use of tools after talk page access was removed, and more insults and blaming others when talk page access was restored. I would like to see an admission that the users actions were not appropriate for an administrator and a clear plan on how this will be avoided in the future. As long as this user stands by their actions and blames others I would would call the idea of returning the tools a non-starter. Chillum 15:59, 18 August 2015 (UTC)

@Floquenbeam: I did not ask for grovelling, no need to mis-characterize what I said. I asked for a sign that he is now ready to return. He had his talk page access returned and he used it to call the folks at ANI jackasses and to blame others for his action. Surely a bad sign. It would be irresponsible to assume he is now ready to behave as expected without some level of commitment from him, and yes I do think that includes taking personal responsibility.

If this user cannot at the very least explain why this won't happen again then we cannot return the bit. I don't think the 8 years of good behaviour is proof it won't happen again because it did not stop it from happening the first time, I want to hear from his mouth that this is not going to repeat. Chillum 16:34, 18 August 2015 (UTC)

@Malik Shabazz: please do not tell me what I do and do not give a fuck about. I am heartbroken at how things have turned out. Chillum 17:39, 18 August 2015 (UTC)

Statement by KTC

Wikipedia:Civility and Wikipedia:No personal attacks applies to everyone, and that includes if someone was responding to incivility that were directed at them. The comments by Brad Dyer was totally unacceptable, but undoubtedly so were Malik Shabazz's responses, who as an administrator was held to a higher standard of civility. Having said that, this would had ended at the original 48 hours block if Malik just walked away at that point, maybe even an unblock if he recognised the comments were inappropriate and agreed to stop. Instead, Malik continued with [14][15] on his talk page, which led to his having talk page access revoked, at which time he admined through his block in a manner connected to that block.

Admining through a block, especially in relation to that block is understood by every admin to be a desysop offence. Doing so to reinstate a personal attack that one were blocked for is simply conduct unbecoming.

While I do have sympathy with Malik given the incivility that had been directed at him, and his apparent (given the many testimonies here, ANI, and his talk page) many years of dedicated unblemished service to the project up to this point, he has obviously not recognised what went wrong from his side and is continuing with the same conduct still. -- KTC (talk) 17:40, 18 August 2015 (UTC)

Statement by MrX

Arbcom should swiftly decline this case. There is no evident pattern of long-term WP:ADMIN abuse or tool misuse. Malik Shabazz seems to have reacted to perceived harassment by another user. The community has not been afforded the opportunity to address the concerns in this complaint, as is the usual process defined at WP:ADMIN#Disputes or complaints. I would also add that it's silly to redact Malik's comments on ANI, yet bare them for the world to see here.- MrX 01:36, 18 August 2015 (UTC)

As an ordinary member of this community, I'm stunned by the suggestion that Arbcom should discuss de-sysoping in private, and equally disheartened to see that some committee members have apparently already made up their minds to permanently de-sysop. The subject of this case has not even been given to opportunity to answer publicly, or to have his response examined by the community. Please help me understand under what policy Arbom derives the authority to circumvent the consensus established dispute resolution processes? - MrX 03:08, 18 August 2015 (UTC)

Guerillero: Sure, I understand the need to temporarily de-sysop an account that may have been compromised, or when we fear that someone is going berserk and might break the internets. Setting that aside, my comments about due process and transparency stand.- MrX 03:27, 18 August 2015 (UTC)

Statement by non-party Zero0000

I'm an administrator whose editing interests have overlapped with Malik Shabazz's for a long time. Malik Shabazz has been an excellent contributor to the encyclopedia for many years, so it is sad to see him lose control as he did here. I hope that he will be given the opportunity to resume editing after a break. Just one comment on the evidence: a case for misuse of administrator tools needs to be made more carefully than it has been. Ceradon's list contains examples that are not misuse (the first diff: if an administrator improperly uses an offensive edit summary, then revdelling it should be his next edit), and examples not requiring administrator tools or done by someone else. Zero^talk 02:01, 18 August 2015 (UTC)

@Chillum: I don't know his motive, but you don't either and we shouldn't assume malice without evidence. On principle, something offensive should remain in the encyclopedia for as little time as possible. Of course he shouldn't have written the edit summary in the first place, but after he did so deleting it was proper, even required. Zero^talk 02:22, 18 August 2015 (UTC)

I'm disturbed by the haste here. One hour and 14 minutes between filing and desysopping. Doesn't Malik even get an opportunity to speak in his own defence? Zero^talk 02:39, 18 August 2015 (UTC)

Further to this, I understand better after Courcelle's comments. I hope that any permanent action will be taken with much less urgency, giving Malik adequate time to make a defence. Actually he has been one of the best editors I've interacted with and I believe that a careful review of his administrative activities will show that, with the possible exception of the past day or two, he has been a good administrator. I'll also mention one matter that probably escaped the attention of a few here: Malik is Jewish (userbox). Words that are shocking in most circumstances can be unexceptional invective within the tribe (think of the 'n' word as used between African-Americans). Whether that holds here, I don't know; just give him a chance. Zero^talk 03:58, 18 August 2015 (UTC)

Statement by Writ Keeper

I'd like to note two things. First, Malik's revdel of the 8th was done at Brad Dyer's request.[16][17] Not strictly correct, perhaps, but not something I'd hold against them, either.

Second, I feel that it's important to note that there was (imo) clear provocation from Brad here. Brad accused Malik of directly copying from a source, which is a serious accusation that wasn't true (it was actually added here). I would argue that the opening shots in this exchange came from Brad, with his condescending (to say the least) "sonny boy" here. Add that with the recent history between these two, and I'd say it's pretty clear that Brad was just looking for an excuse to pounce on Malik, and this was the next thing that came along.

Not that any of this excuses or even much mitigates what Malik said, or should interrupt the level 1 procedure here (which I personally think might be hasty but that's to one side); I'd just like it on the record that this didn't happen in a vacuum. Writ Keeper ⚇♔ 02:05, 18 August 2015 (UTC)

Statement by uninvolved EvergreenFir

The use of racial and ethnic slurs in this manner should be ground for immediate removal of tools. EvergreenFir (talk) Please {{re}} 02:16, 18 August 2015 (UTC)

Statement by Drmies

Wow, sometimes ArbCom works really quickly, and in this case unnecessarily so. You can't desysop like this for an insult, and the abuse of tools is singular: one revdel, in anger of course, just one, and no suggestion of a pattern. Not even a second abusive tool usage. I'm also puzzled by the suggestive rhetoric of "what else has he hidden", a phrase used by the filer--well, that's easy: you have admin glasses, Ceradon, and you can see what he has hidden, so there can be no question here. I find it sad that Malik did what he did, and I also find this whole circus wholly unnecessary. It's like Human Resources is looking over our shoulder constantly, and we are more than happy to rat each other out with these procedures--do you all not remember we're supposed to be colleagues here? (Someone commented that racial abuse is grounds for a desysop--surely that person knows how "sonny boy" must have been intended in this case.) Malik, I'm sorry.

• After some more arbs have weighed in, I still am not convinced how we (you) extrapolated from one single clear error in judgment to the suspicion that this would be an ongoing pattern. One strike and you're out? Drmies (talk) 04:23, 18 August 2015 (UTC)

Statement by uninvolved Softlavender

I recommend not accepting this case. Malik Shabazz is the most gentle, reasonable, forgiving, and harmless editor, never mind admin, I have ever seen or come across on Wikipedia. He also endures, without complaint, a nearly daily and non-stop onslaught of racial and ethnic slurs and abuse (check the revert and also revdel list on his talk and user pages), for being black and for being Jewish, and for editing circumspectly on controversial pages on Judaism, Muslim and Arab issues (which he also has an interest in because of his stated interest in Malcolm X), other ethnic conflicts, and pages on black figures or issues, etc. Thus far, to my knowledge, he has endured all of this without a single complaint or drop in civility, until apparently just now. Obviously a breach of civility and revdel parameters occurred, but this short-term lapse in judgment after enduring years of abuse is not worthy of an ArbCom case or a de-sysopping. Merely a warning should suffice. If this were a longterm pattern, that would be another thing entirely, but this is a singularly out-of-character short-term blow-up and misjudgment. Softlavender (talk) 03:28, 18 August 2015 (UTC)

Statement by uninvolved Ivanvector

I believe I'm uninvolved although I did comment at ANI that I endorsed (as a non-administrator) Chillum's initial block of Malik. Given that Malik was abusing the tools to edit through a block and restore revdeleted personal attacks, the level I desysop was absolutely warranted, however I encourage the Committee to decline this case at this time. It seems obvious that Brad Dyer's pointy behaviour and his own use of thinly-veiled racial epithets (per Drmies) were the opening salvo in this exchange, which somehow pushed one of our most level-headed admins to completely and rapidly self destruct. Of course that doesn't excuse Malik's behaviour, which would be appalling from any user but especially from an admin, but with the temporary desysop and both users on an enforced holiday, these issues are for the moment resolved. I agree with other users who have said here and at WP:ANI that if Malik's regrettable but isolated misstep resulted in permanently losing admin rights, that would be an overreaction and a net loss to the project. Ivanvector 🍁 (talk) 03:39, 18 August 2015 (UTC)

Statement by uninvolved Beyond My Ken

Very little to say here:

• My observation of and limited experience with Malik Shabazz have been uniformly positive. This appears to be a fairly singular incident, albeit a rather serious one, and ArbCom should take his exemplary editing and administrating history into account.
• Neverthless, I endorse the temporary desysopping. Under the circumstances it was warranted and justified.
• I believe the the Committee should accept a full case to delve into the circumstances of the provocations of Brad_Dyer towards Malik Shabazz. Since the case might end up in a permanent desysopping (although I don't think it will and don't believe it should), it can't be handled by the community, or, rather, if the community handles it it will probably just wind up here anyway. BMK (talk) 03:57, 18 August 2015 (UTC)

Statement by Dave Dial

It's as if nobody on ArbCom knows Malik. I agree that his actions deserve a block, and if a continued use of the tools, a temporary desysop. But Malik has been one of the best and most level headed admins on the project. This seems to be a very hasty response with little to no thought about the individual and the character of that individual. Dave Dial (talk) 04:02, 18 August 2015 (UTC) @Seraphimblade: Uggg, so ArbCom must accept this 'case' and further deliberate to death what should be dealt with using patience and common sense? By all means, don't wait a few days for some of the heat to die down. Bahhh. There is no pattern of this type of behavior, there is no need to examine the intricacies of the whys and hows. It's obvious. Sorry, this will be my last comment here. I respect ArbCom members volunteering their time for the project, but..... Dave Dial (talk) 16:52, 18 August 2015 (UTC)

Statement by uninvolved Avraham

I try not to get involved in Arbcom discussions, but I feel compelled to speak, if only as a character reference. I have dealt with Malik for many years now—often on actuarial related topics, sometimes on Judaism or Israel related topics. We often do not agree, but he has, to the best of my recollection, always comported himself with dignity, class, and great reserve. He has done so for years, even dealing in some of the more tendentious areas of the encyclopedia. As I can best understand it, in this instance, his prodigious patience ran out. So, yes, he was actively violating the civility norms; unquestionably. For that he was blocked as a protective measure to prevent further escalation. Similarly, the talk page block was appropriate.

My concern is for the apparent rush to desysop. As noted in the original request, Malik has been an admin for 8 years, and an active one for that time. I am of the firm belief that no admin should get any special treatment just for being a member of that class. I am of the same level of belief that every editor needs to be judged in the context of his or her history, regardless of class. Malik is not a problem editor; nor is he is a problem admin. Just the opposite. This week, though, Malik lost his temper, his cool, his reserve, and his will-power, and let his frustration, anger, and emotion get the better of his common sense and good judgment. That is not desysop-worthy in my opinion. A reminder that as an admin he should act as befits an officer and a gentleman is warranted. Perhaps an outright warning as well, but a knee-jerk desysop of someone whose years of history and tens of thousands of civil and respectful edits—content and maintenance both—would be punitive and not preventative, and giving one incident out-sized weight, in my opinion. Thank you. -- Avi (talk) 04:22, 18 August 2015 (UTC)

Malik's retirement is clearly a net loss for the project. If anything positive comes out of this fiasco, it is my opinion that it should be 1) that we finally put our money where our mouths are and civility should be enforced and 2) as social construct, common sense and wisdom should temper rote bureaucracy. -- Avi (talk) 14:37, 18 August 2015 (UTC)

Also, this case is a counter-example to what I meant when I said "the formality of an Arbcom case is a feature, not a bug." A measured response was called for, not an emergency desysop. I believe even a cursory review of Malik's history would indicate that he was not going to cause any immediate disruption to Wikipedia, which is the purpose of an emergency desysop. -- Avi (talk) 15:46, 18 August 2015 (UTC)

Statement by Sean.hoyland

I wonder which banned/blocked ethno-nationalist extremist admins are facilitating this time. Given Brad Dyer's passive aggressive nature and his whiny fucker-ness, he looks a lot like NoCal100 to me. But I guess he could be any of a number of the worst kind of Israel supporters attracted to Wikipedia who obsessively return here with the community's de facto blessing. Either way, in ARBPIA, the probability that he is a sock is certainly greater than 50%, thanks to Wikipedia's pathetically weak and time wasting defense against sockpuppetry, apparently willful blindness and tolerance for day to day POV pushing and community willingness to collaborate through discussion with liars, racists, ultranationalists, people who support ethnic cleansing etc. This is what happens when there is an almost complete lack of policing of the ARBPIA topic area coupled with the profoundly foolish and counterproductive notion that it even remotely resembles a collaborative, collegiate environment, a mantra stupidly repeated by admins over and over again. I was lucky enough to go to collage. Don't remember it being infested with sociopathic piece of shit excuses for human beings. The reality is that about half of the editors active in ARBPIA, often the most active editors, are ethno-nationalist extremists or thereabouts, who the community, for the most part, pretty much allows to get away with their abusive misuse of the site. Good people, highly involved admins like Malik, could make the topic area a genuinely collaborative collegiate environment by getting rid of the many truly appalling people who come here to advocate by simply blocking them on sight - it's easy to recognize people who come to Wikipedia to advocate. But instead Malik's 'involved' hands are tied and he is subjected to Wikipedia's weak and pointless version of tar and feathers. One day admins will need to face up to the reality that they have lost control of an entire topic area and that it has consequences. Sean.hoyland - talk 07:42, 18 August 2015 (UTC)

Statement by involved Kingsindian

Some background: I actually made the edits which were at the bottom of the ANI mess. The material was not added by MShabazz, as Brad Dyer mistakenly stated. As I stated on the talk page, the revert by Brad Dyer seemed rather WP:POINTy to me. (I am not accusing Brad Dyer of anything in the following) I do want to note, however, the routine socking which goes on in this area, which MShabazz is quite familiar with. I reported two socks (sock1, sock2) of Wlglunight93 just in the past month, and another user reported a long-time sock of NoCal100 (sock), active for years. I have ran into them tag-teaming (see for example the RfC here which I started, also here). I am actually pretty sure that NoCal100 is back, and I even know who it is, but I don't have the evidence yet. Kingsindian ♝♚ 09:21, 18 August 2015 (UTC)

Statement by JzG

The Committee should take this case in order to do the following:

1. Review Malik's long history, and restore his sysop bit after this unfortunate and no doubt temporary meltdown (it is likely there is some external mitigating factor at play, this is absolutely not characteristic of Malik).
2. Review Brad Dyer's behaviour.

As the statements above show, Malik is normally known to be very level-headed and calm. I think I am not alone in preferring that Malik returns to active mop-duty as soon as his normal equanimity returns. Guy (Help!) 11:02, 18 August 2015 (UTC)

Statement by Alanscottwalker

Malik, I have only had limited interaction with you and I have been impressed. You went wrong ('fight fire with fire and all burn', as they say, I think you usually know that), but, please, hopefully you can find your way back to us (perhaps not to that subject area, even though it needs much adminning). I can only offer my best wishes to you. Alanscottwalker (talk) 11:15, 18 August 2015 (UTC) (My hope is that you are not desysopped, permanently, I think part of that depends on what you want and say. I can offer further unsolicited advice at my talk page, if you want it. Alanscottwalker (talk) 14:49, 18 August 2015 (UTC))

Statement by Non-involved user Stifle

I have had a look at the situation. The behavior, save for using admin tools whilst blocked, would get an average user blocked for a few days at most. Admins being held to a higher standard, or otherwise, Malik Shabazz has ended up with a week block as far as I can see. A single isolated instance of using the tools inappropriately and a series of incivil edits do not seem to me to be worth going through the mill of a full-blown case.

Therefore I would urge ArbCom to decline, with a motion if necessary that Malik Shabazz is sentenced to "time served" in terms of the desysop and block, in view of his otherwise long and excellent record. My second preference would be in line with JzG. Stifle (talk) 11:04, 18 August 2015 (UTC)

Statement by Collect

I greatly respect Malik. The problem is that ArbCom can not be seen to hold different standards from case to case, and there is no doubt that the language used in multiple example is quite unacceptable, and that he used sysop tools in a less than circumspect manner. Sorry - there is no way to excuse many of the comments made at all, and if a normal editor made them, they would receive more than a one week block just for that. Misuse of sysop tools has, per policy, only one result. But I still like him Malik an editor, and agree on his positions many times. Collect (talk) 11:24, 18 August 2015 (UTC)

Statement by Xeno

Roger Davies: I agree with Courcelles in that Level I procedures were appropriately invoked here; in the time it would have taken to implement Level II procedures, the user may have performed further administrative acts through the block during (what appears to be) a temporary lapse in judgment.

Has the committee been in contact with Malik yet? Perhaps talk page access could be restored or he could be unblocked so that he may prepare a statement? –xeno^talk 12:26, 18 August 2015 (UTC) Talk page access since restored

Worm That Turned: Respectfully, I disagree that Level I procedures were not made out. An administrator intentionally and actively using administrative tools through a block to initiate or further a wheelwar does cause harm, if only by blatantly disregarding the social contract to which administrators are held. –xeno^talk 12:40, 18 August 2015 (UTC)

Statement by Worm That Turned

I'm a disappointed in those who agreed to a level 1 desysopping.

• Level I procedures may be used if (a) an account appears to be obviously compromised, or is intentionally and actively using advanced permissions to cause harm in a rapid or apparently planned fashion, or (b) multiple accounts are actively wheel-warring.

Malik does not appear to be compromised or intent on causing harm in a rapid or planned fashion. 1 admin edit and it was clearly "reactive" not "planned". A simple "Don't do that" could have sorted that. I also disagree with Roger that Level 2 would be appropriate.

• Level II procedures may be used if (a) the account's behaviour is inconsistent with the level of trust required for its associated advanced permissions, and (b) no satisfactory explanation is forthcoming. (my bolding)

I'm assuming no explanation was requested. Simply, Malik should not have had his tools removed. He should have been told to stop and then a case if necessary. The administrative action was over his edit and he unhiding it. There's all sorts of arguments over whether it should be deleted or not, but it's not a simple case of him intending to cause harm.
Now that I've registered my disappointment, we should look forward. Malik, who I've not worked with but believe the testimony's to his character, was clearly provoked here. Yes, his actions were unacceptable, but that was dealt with by the community. I'd like to see Malik contact the committee, admit he was out of order there and have the tools returned. Don't put a massive amount of hoops in the way here - a simple explanation (which should be bloody obvious anyway) is all that should be needed. Worm^TT(talk) 12:35, 18 August 2015 (UTC)

Xeno, there's a different between where we are and where we should be. I'd support a temporary desysop procedure for situations like this, but Arbcom's "Level 1" procedures are not them. There are VERY strict circumstances that Level 1 desysop procedures should be used - compromised account, or intentionally and actively using advanced permissions to cause harm in a rapid or apparently planned fashion. The harm caused is debatable. The planned fashion completely out - this was completely reactive over reach of power. Like I say, there's 5 names who voted for that the desysop that... well, I'm disappointed in. I wasn't there, I'm not going to criticise too much - but I stand by my statement "it was the wrong decision". Worm^TT(talk) 12:46, 18 August 2015 (UTC)

Statement by WJBscribe

Just to note that I have restored Malik's ability to edit his own talkpage. Given that there are proceedings here, I think he should be able to post a public statement before his block is due to expire if he so chooses. Talkpage editing restrictions should be a last resort and, even the restriction was needed at the time, it hopefully isn't now. WJBscribe (talk) 12:45, 18 August 2015 (UTC)

Statement by Davey2010

Personally I don't think this should be accepted - As far as I'm aware Malik's never once gotten pissed off with anyone - Infact he's always been polite and calm with everyone, Even when trolls come to his talkpage he simply shrugs it off and gets on with it, Everyone on this project loses there shit at times (myself included) so I don't really think it's right nor fair to bring an Admin to Arbcom over his outburst which looks to have been his first in the 8 years he's been here. –Davey2010^Talk 13:14, 18 August 2015 (UTC)

Statement by DrKiernan

Black youth and artistes seem to revel in using the word nigger, and no-one says they are racist. So, is it racist for a Jewish person to use the word jewboy? Probably not, especially when it is used in a remark that is clearly satirical. DrKiernan (talk) 13:26, 18 August 2015 (UTC)

Statement by (uninvolved, but upset) StevenJ81

I would have taken the time to write my own opinion in support of Malik. But as of about 15 minutes ago, there is now a "RETIRED" template up on his talk page. So I think some of the high-and-mighty ArbCom/Bureaucrat/Steward types who are buzzing around this page better figure out now how this project can possibly continue when effective, responsible contributors and administrators can get bullied and slurred to the point where they want to leave. StevenJ81 (talk) 14:18, 18 August 2015 (UTC)

Chillum, if you and others around here are really that heartbroken, then let's figure out a way to fix some of this stuff. There are a lot of people with a lot of fancy flags who wouldn't even dream of touching some of the stuff that Malik was willing to work on. And yet those people dare to criticize?

Really, only a little bit of this is about the particular case at hand. It's a much more general problem.

I appreciate how politically contentious this topic area is. And I really appreciate that Wikipedia is open, in principle, to editing by anyone, any time, no matter what. But at this point, something's got to give.

So what's going to give? This topic area is already de facto not open to "everyone" to edit, because a lot of good, dedicated people (like me, I'd like to think) can't stand being there, and so won't edit there. Except for guys like Malik, increasingly only the nutcases (on both sides) are left. In my view, this area has got to be left to experienced editors, and even experienced editors need to have their edits vetted (à la pending changes). If you're going to complain to me that a rule like that violates "open to everyone", I will repeat: it's already not open to everyone. So in that case, we might as well concede that, and try to create an encyclopedia that is of high quality.

Frustratedly, StevenJ81 (talk) 17:55, 18 August 2015 (UTC)

Statement by uninvolved Hammersoft

There's claims here that this event, with regards to Malik Shabazz, is isolated. This is false. A cursory examination of history shows Malik to be uncivil on a number of occasions.

• "cut the bullshit; if you don't see scandals, regardless of your politics, your head is in the sand"
• "You can't just make shit up and put it in front of a footnote"
• "look at the end of the fucking paragraph, you morons"
• "Fuck off"

Everybody has bad days. But, sustained incivility is not compatible with adminship. I note that he has apparently retired. It would be problematic if this user's admin flag were restored and a case concluded this latest incident was isolated, therefore no problem. There is a problem. --Hammersoft (talk) 14:49, 18 August 2015 (UTC)

Statement by Floq

I haven't run across Malik Shabazz very often - probably because he does the hard stuff and I do the easy stuff - but the testimonials above lead me to think that the best solution to this one-off blow up is (a) allow the NPA blocks for both parties to remains in effect, or if an {{unblock}} template is used, be addressed the way typical ones are (b) return the tools with no case, contingent on an assurance from MS that this won't happen again, (c) make sure that MS realizes that this was pretty far over the line, even if there are extenuating factors, and (d) decline a case for now, let the community try to address the underlying behavioral issues with MS and BD, and accept a new case if that fails. Before I knew the background, I was originally much more upset with the epithet "Jewboy", but based on Softlavender's and DrKeirnan's comments, my understanding is that this is not evidence of actual anti-Semitic prejudice, but an attempt to hurt with words, mirroring words thrown at him. Not good, obviously, but a different kettle of fish. --Floquenbeam (talk) 15:01, 18 August 2015 (UTC)

• As I look into this more, I get more and more concerned that de-escalation would be (a) highly desirable, and (b) increasingly unlikely based on how we usually work. Any possibility that, now that the heat of the moment has passed, we could take the first step and preliminarily unblock and resysop, on the basis that it's not likely to be repeated, and that we might be able to salvage an apparently invaluable admin working in a nightmare topic area? An area that I am literally too chickenshit to touch? I've been one keystroke away from a Level 1 desysop myself, and that was without being refered to by a term that, to quote Drmies, "combined racism with utter disrespect, in a word that has centuries of history in American racist speak". Surely we can find a way to bend rules in such a way that we don't shoot ourselves in the foot? --Floquenbeam (talk) 16:21, 18 August 2015 (UTC)
  • As a first step (the only one I can take as a mere admin) I've unblocked Malik. --Floquenbeam (talk) 16:33, 18 August 2015 (UTC)
• @Chillum:, I would interpret his previous 8 years of apparently calm and upstanding admining in a toxic topic area as evidence he knows he can't do that. He was just called a racist epithet and snapped; surely he doesn't have to grovel? --Floquenbeam (talk) 16:21, 18 August 2015 (UTC)

Statement by Ritchie333

I haven't dealt with Malik much but when I have he's been a hard-working and patient administrator, one of the good guys, who is about the last person I'd expect to end up here, if I'm honest. His reaction to the message is not too different in scope to a similar incident on my talk (although I would hope it's obvious I was simply making light of the situation) and being repeatedly accused of policy violations without any proper evidence would drive anyone else up the wall. I think Malik should take a few days off to clear his head and Arbcom give him an open offer of the tools back on the condition that the next time he feels like making a personal attack, to just shout it at the monitor without pressing "Save page". It's not like he's been repeatedly disruptive all over the place; this is a one-off where things got out of hand; hence there is no reason to take a case. Ritchie333 ^{(talk) (cont)} 15:19, 18 August 2015 (UTC)

Statement by Capeo

Great job, arbs. A black American male gets called sonny boy, quite literally the most insulting thing you can say to a black American male, after being hounded by an obvious sock in the most contentious editing area of the whole wiki and rather than having his back you desysop him. Well done. And the racist troll gets what? A 48 hour timeout or some such BS?. Great job, admins, as well. Capeo (talk) 15:38, 18 August 2015 (UTC)

Statement by Hasteur

I believe I've never had any substantial involvement with respect to any of the primary parties to the case, but would like to note the following conditions are in play currently: Level 1 Desysoping was invoked on an Admnistrator (rightly or wrongly), Said administrator has elected to retire in chronological proximity to said desysoping, Said administrator retired while under scrutiny for their administrative actions. As such I assert that a "under a cloud" situation has occured. In order to prevent AN/ArbCom flu outbreaks in the future, should the committee with to curtail the gambit, to pass a simple motion confirming the desysop and indicating that should the editor wish to regain Administrator privileges, they should stand a new "Request for Administrator" campaign. Hasteur (talk) 15:40, 18 August 2015 (UTC)

@Dennis Brown: adding the under the cloud makes clear that there was cause for concern when the retiring took place and therefore a standard request for resysop would be out of order. Hasteur (talk) 16:53, 18 August 2015 (UTC)

Statement by Nishidani

This is extremely distressing . My testimonial hasn’t the authority, or neutrality one will observe in, to name the major editors who have commented whose work I admire, Avi and StevenJ81 but I agree with them, as I rue (while understanding) their decisions to withdraw from an active presence in the I/P area. It is an extremely stressful area to work, and made more so by the unending recycling of sockpuppets, and the prevalence of the sheerly incompetent with a national mission guiding their every revert,mostly ungrounded in policy. Those who work there know that half of their daily grind will consist in trying to talk reason to editors who are indifferent to the talk page, or use it in a highly desultory fashion. Brad Dyer is a disgrace to the project, but he’s not alone: at least 8 editors there, often red-linked, are destructive in their purposes. Identify laboriously one of them, and two pop up after the ban is set, hydra-like. In good part, the area has been effectively abandoned as either (a)”toxic” (b)or because the anarchic nature of editing there works out as an attritional war, where the best fall because there is simply no answer to blind attritional gamesmanship. Malik is one of the few (two or three) admins who, able to see both sides, could be relied on to enforce policy there. This is the second instance I can recall where we have lost an invaluable editor because he, on one single occasion, blew up and got tired of being polite to either an obvious sockpuppet or a nuisance provocateur. It is this fact, the success with which idle editors can achieve a massive gain – the elimination via successful provocation of an extremely good editor/admin – without having their own record or utility for the project examined, which is deeply disturbing. An encyclopedia that shows itself ready to adopt draconian measures for the rarest lapse (and the lapse was very serious) in an admin of 8 proven years of exceptional duty, while demonstrating a total insouciance to the “toxic” idiocy of editing in the area he worked in (we need, ladies and gentleman, a high bar of perhaps at least 400-500 non-I/P edits for newbies who wish to work on I/P issues), will only serve to disenchant the few masochists who put up with the nonsense, which looks as though it were being condoned by sheer negligance. How long are we to put up with this inane anarchic state of abandon, when the best admins are punished for a frailty as exceptional for his record as it is, formally, unacceptable? Nishidani (talk) 15:57, 18 August 2015 (UTC)

Statement by Opabinia regalis

Of course we all agree that the comments here were way, way over the line, and we all wish Malik well. But considering the category of things that can be described as an emergency - and let's even restrict the scope to things that are emergencies on the internet - is this really in that category? A person who is being racially harassed changed the visibility of one of his own intemperate reactions while blocked? Seems more like yet another demonstration of how difficult it can be to stop the gathering momentum of Something Must Be Done. Meanwhile, the desysop was done before anyone got around to blocking the person doing the harassing.

If this case is accepted it should be about some combination of 1) this repeated pattern of unnecessary escalation by ANI stampedes, 2) the general toxicity of the topic area (which is apparent even to the entirely uninvolved), and 3) the ineffectiveness of the community at dealing with harassment, provocation, and trolling as opposed to mere "incivility". Opabinia regalis (talk) 16:37, 18 August 2015 (UTC)

Statement by Dennis Brown

Deysopping via Level 1 seems a bit strong, but it's done so I don't see a point in laboring it. That said, deescalating the situation would be best, and it would seem rebitting him might be in order as there isn't any immediate threat. The reason for the temporary desysopping no longer holds true. Then Arb can decide if a case is really needed, or if the community can handle it. I'm torn without looking at more details, but this is a unique blowup from an admin that has a long history of good service, so desysop may very well be the wrong long term solution. And Hasteur, "under a cloud" is meaningless because he didn't voluntarily resign the bit. Dennis Brown - 2¢ 16:44, 18 August 2015 (UTC)

Statement by {Non-party}

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the case request or provide additional information.

Clerk notes

This area is used for notes by the clerks (including clerk recusals).

• @Georgewilliamherbert and Ceradon: Any objections to merging the two requests? L235 (t / c / ping in reply) 01:21, 18 August 2015 (UTC)
  • @Georgewilliamherbert and Ceradon: Thanks folks, though as this page is strictly under sectioned discussion I've moved your comments into your own sections. L235 (t / c / ping in reply) 01:31, 18 August 2015 (UTC)
• @Guerillero, Courcelles, and GorillaWarfare: Query for the arbs, are you voting for the level 1 on-wiki? Have the proper procedural requirements (arbcom-l and communication with all arbs with all mediums) been done? Should this be taken as a formal request for a bureaucrat to take action, or should the crats wait until the notices are posted to WP:ACN and WP:BN before actioning, per WP:LEVEL1? Thanks - L235 (t / c / ping in reply) 01:44, 18 August 2015 (UTC)
  • Appears I spoke too soon for the second question, but the first few probably still need a bit of clarification.. L235 (t / c / ping in reply) 01:45, 18 August 2015 (UTC)

Malik Shabazz: Arbitrators' opinion on hearing this matter <7/3/0/1>

Vote key: (Accept/decline/recuse/other)

• Decline per WP:LEVEL1 --Guerillero | Parlez Moi 01:27, 18 August 2015 (UTC)
  • Please wait for a notice to be posted by an arb. --Guerillero | Parlez Moi 01:46, 18 August 2015 (UTC)
    • @MrX: We were following the 6-year-old WP:LEVEL1 procedure for a temporary desysop. --Guerillero | Parlez Moi 03:19, 18 August 2015 (UTC)
• Decline and desysop under level 1. Courcelles (talk) 01:30, 18 August 2015 (UTC)

• Noting that several checkusers, myself and Guerillero included, have looked at this, and found no evidence of a compromised account. Courcelles (talk) 01:31, 18 August 2015 (UTC)
• With three votes, I have asked at BN for this to be enacted. Courcelles (talk) 01:47, 18 August 2015 (UTC)

• @L235:, this mess broke quickly, but, yes, there has been a thread on arbcom-l about it, and there has been no objection to a level 1. Courcelles (talk) 01:49, 18 August 2015 (UTC)

Okay. Now that the level I is in effect, let us all slow down and take a breath. The use of admin tools as they were used while blocked was the major issue here. We don't level 1 for insults, even extreme ones, that is the realm of the block and revoke talk access functions. Those are the realm of a case, or a normal desysop by motion. Level I is an extremely rare thing, I would never have considered a level 1 without the direct use of the admin tools while blocked. Now we have the time to think and reflect and let everything cool down. A Level 1 is not a final decision. A level 1 is not a decision made by a majority of the committee. Now, I think we need to slow down, to let Malik Shabazz respond. The level 1 is explicitly not a final decision, and now we need to process this like a normal case request. I think what has to happen now is one of three things. Either the tools can be restored, a permanent revocation passed by normal motion, or a case opened to look this. I'm thinking this is a complicated mess, and now that the immediate problem is over, that we might actually need a case. Courcelles (talk) 02:42, 18 August 2015 (UTC)

• I'm not sure why Roger says that Level 1 is for "situations where a (compromised or otherwise) admin account goes on the rampage inflicting damage on the encyclopedia's infrastructure." given that in any circumstance like that, a 'crat or steward would be fully justified in pulling the bit and asking questions later. And I damned well hope they would rather than waiting around for three arbs -- none of which this year have the technical ability to remove admin bits -- to sign off on something so blatant. (You could almost call that level 0, I guess) Level 1 is for things that need to be done now, and this did need to be done due to the rather obvious prohibition of a blocked admin using their tools. We use Level II for far less immediate situations, such as when an admin has been caught socking. Down to brass tacks: The presumption on a level 1 is that the tools can be restored easily in proverbial morning. What we have here is a total mess, but one that had admin tools not been used, would have been dealt with at ANI, and was being dealt with. Malik Shabazz, is, as many have said, an admin of a record of long tenure and honourable service. I'd be prepared to reverse the desysop if Malik Shabazz were to come back, and publicly commits not to ever use his tools while blocked or in a dispute again, I never, ever intended this desysop to be permanent or the final word on anything. I guess accept to look into the matter fully, including the actions of Brad Dyer and others involved. But I remain open to the idea a motion could dispose of this to most parties' satisfaction. Courcelles (talk) 08:05, 18 August 2015 (UTC)
• Comment I also support a level 1 desysop, bringing it to the required three in favor. GorillaWarfare (talk) 01:39, 18 August 2015 (UTC)
• I also agree to the desysop. Compromised or not, this is absolutely not acceptable behavior for an administrator. Seraphimblade ^{Talk to me} 01:51, 18 August 2015 (UTC)
  • @DD2K: Desysops done in this manner are a temporary measure to prevent an immediate problem. They are open to review later, and if Malik should so request, we will of course review whether the tools should be restored. Seraphimblade ^{Talk to me} 04:19, 18 August 2015 (UTC)
  • Accept to examine the entire situation. There's clearly more to this situation than this particular incident. If the ARBPIA area remains toxic despite what's already been done there, we need to revisit that. Seraphimblade ^{Talk to me} 16:19, 18 August 2015 (UTC)

• The desysop has been done, but per procedure this is temporary until the entire committee can review the matter. To make the timeline clear, and explain why at least I thought this had to be done by the level 1 process, was the timeline showing tools were used through the block. Courcelles (talk) 02:20, 18 August 2015 (UTC)

• I agreed also, but quite specifically pending some sort of explanation. I need more information to say whether we will need a case. DGG ( talk ) 04:16, 18 August 2015 (UTC)

• Accept: this isn't really a Level I situation. Level I was intended for situations where a (compromised or otherwise) admin account goes on the rampage inflicting damage on the encyclopedia's infrastructure. Level II is more appropriate to the circumstances here: a temporary desysop pending investigation. Given Malik Shabazz's seemingly exemplary record a public case is probably the best way forward. It may also be a good time to review the Level I/Level II procedures, to see whether a better system can't be put together.  Roger Davies ^talk 06:57, 18 August 2015 (UTC)
• Decline - block of both parties was necessary for personal attacks. Temporary tool removal was also necessary as a preventative measure, given they were used while blocked and still engaged in the dispute. Full case is not necessary as I don't see this as a pattern of behaviour - it seems like a one-off angry reaction. Once we're confident the disruption has ceased I would support return of the tools per "Return of Permissions." On a separate issue, suggest AN or ANI consider whether this reaction is a consequence of ongoing harassment as suggested above. Should that be unproductive, would consider a case request on this subject. -- Euryalus (talk) 07:01, 18 August 2015 (UTC)
• Accept I don't think this is level I, it was clearly very far out of line but he didn't exactly go on a rampage deleting key articles or performing pagesplit vandalism. There was some background which is important to take into account in this case which hasn't really been exanined, and we should aim to be transparent as much as possible. Hence I am voting to accept this case. This may not have been a pattern of misbehavior, but it should nonetheless be examined. NativeForeigner ^Talk 07:14, 18 August 2015 (UTC)
• Accept. I was asleep when all this happened, but I would have supported the temporary desysopping had I been aware at the time and endorse my colleagues actions. This is solely on the grounds of using admin tools while blocked. Given that a level 1 desysopping has happened there needs to be a review of the whole situation to determine whether Mike should have his tools restored and whether any action needs to be taken against other parties. A public case is the best way to have this review I believe. Note that I am recused with respect to KTC and will not be passing comment on their actions. Thryduulf (talk) 07:52, 18 August 2015 (UTC)
  • To those who have said that Mike's 8 years of good, level-headed service as an admin mean that it was obvious he was not going to go on a rampage, I disagree. This act was so clearly out of character that I do not believe his past behaviour to be a good predictor of his actions when clearly very emotional (and he certainly had good reason to be), we will never be able to know what actions this emergency desysopping did or did not prevent from happening, but in my opinion it is better to be over cautious in these matters. One principle that I think needs to be stressed in the light of Mike's statement here is that two wrongs do not make a right - racist abuse is never acceptable, but being the subject of racist abuse does not make it OK for you to racially abuse somebody else, ever. Thryduulf (talk) 17:38, 18 August 2015 (UTC)
• Accept Pretty much per Thryduulf. This all went down while I too was asleep, so I'm just getting up to speed on it this morning; on the face of it, though, there are several aspects to this case which may bear examination beyond the desysop. Yunshui ^雲_水 09:53, 18 August 2015 (UTC)
• Decline pretty much per Euryalus. Salvio ^{Let's talk about it!} 11:11, 18 August 2015 (UTC)
• Accept per Roger and NativeForeigner. Doug Weller (talk) 15:50, 18 August 2015 (UTC)