<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>[Discussion] Joint Statement re: Miscommunication and On Censure</title>
		<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur</link>
		<description>Posts in the discussion thread &quot;[Discussion] Joint Statement re: Miscommunication and On Censure&quot; - Posted Oct 17.</description>
				<copyright></copyright>
		<lastBuildDate>Mon, 20 Jul 2026 06:37:21 +0000</lastBuildDate>
		
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5128035</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5128035</link>
				<description></description>
				<pubDate>Tue, 09 Nov 2021 02:47:51 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><strong>Fiat Update</strong></p> <p>Administrators are currently reviewing Fiat policy to help assess this disciplinary case. The purpose of this is to determine the grounds of disciplinary action and how administrators are obligated to approach the situation.</p> <p>N.B.: Administrators (including the accused) informally agree universally that censure votes are necessary. However, if administrators were to shortcut the process and immediately post the threads, ironically, they would be in danger of committing some of the same errors that resulted in the incidents under disciplinary review. This will hopefully become clear over the coming days.</p> <p>During the course of this review of Fiat policy, administrators will be suggesting reforms to the Fiat process. We welcome the feedback of any user as well.</p> <p>This discussion thread is here: <a href="http://05command.wikidot.com/forum/t-14271028/administrative-fiat#post-5128031">http://05command.wikidot.com/forum/t-14271028/administrative-fiat#post-5128031</a></p> <p>PLEASE NOTE: This phase of the discussion only addresses the charge that Dexanote engaged in &quot;abuse of admin Fiat by declaration of Disc Team possessing unilateral power to determine final punishment (or lack thereof) for a staff member,&quot; which occured in the second Disciplinary thread for Cerastes.</p> <p>Admins must also consider the charge that Dexanote engaged in &quot;abuse of position by poor judgment&quot; (whether intentionally or not) by posting the first thread: <a href="http://05command.wikidot.com/forum/t-13868187/disciplinary-cerastes#post-4823379">http://05command.wikidot.com/forum/t-13868187/disciplinary-cerastes#post-4823379</a> and presenting &quot;pretty much just Magnus' argument w/o doing his due diligence,&quot; especially in the first draft of the post.</p> <p>Again, I believe it's obvious to everyone that some form of censure is merited. However, we owe it to both Dex AND all staff AND the community at large to seriously investigate all this.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5128026</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5128026</link>
				<description></description>
				<pubDate>Tue, 09 Nov 2021 02:24:40 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><strong>Update.</strong></p> <p>Here is the agenda being followed by administrators presently to address this case. Older versions of this have been posted in several places, including staff chat.</p> <p><strong>We are focusing on necessary aspects for the censure to proceed.</strong> Anything tangential to the censure was added as a side effect. Notably, I wrote up a full post on all aspects of Fiat, even though only a specific part of Fiat was necessary to discuss, but that's because of other administrators weighing in as well.</p> <p><strong>Agenda</strong></p> <p>1. <strong>Today:</strong> Finish internal Fiat discussion so we can identify the grounds of the censure (with reforms to be proposed as a side effect). Post an initial assessment of Fiat to O5 for discussion, including a few proposed reforms. This was perhaps the hardest stage of this investigation (to my surprise) and I'm glad it's about to be over. I will post a separate reply to this post once it's ready.<br /> 2. <strong>By next Monday:</strong> Post all other relevant material to O5 that has been shared in rough draft form on Staff Discord over the past weeks, except as specified.<br /> 3. <strong>ASAP:</strong> Finish remaining discussion of the staff disciplinary process with admins &amp; Disc, to verify we aren't messing up.<br /> 4. <strong>ASAP:</strong> Finish reviews of all actions of people involved as relevant to Dex's actions and Mann's actions.<br /> 5. <strong>ASAP:</strong> Post the results of the investigation of the November 2020 incident and post an explanation on O5. (I already shared a rough draft of part of the investigation on Staff Discord, but I later discovered it contained serious inaccuracies, so it will take longer to post this explanation.)<br /> 6. <strong>ASAP:</strong> Make the decisions necessary for admins to post censure votes on O5. (As I've said before, there's basically a 99.9% chance there will be two disciplinary vote threads posted with a recommendation to censure Dexanote and an undetermined recommendation for Mann, but the content of the thread is very likely to change based on our actual discussion.)<br /> 7. <strong>ASAP:</strong> Ensure all remaining questions and concerns are responded to in this thread, including ensuring other admins weigh in who haven't (many of them are waiting for assessments from myself and Aismallard).<br /> 8. <strong>ASAP:</strong> Post the Disciplinary Vote Threads.</p> <p>We intend to finish this as fast as humanly possible. Speaking for at least myself, Aismallard, and especially Dexanote, the fact that this isn't done yet is painful.</p> <p>I mentioned this above:</p> <blockquote> <p>If admins need to take more than a few days, then I have recommended (along with Dex) that we ask all of staff for permission to sidestep the full charter process and speed things up with specific steps that will be laid out then.</p> </blockquote> <p>I have currently (temporarily) withdrawn this recommendation because of accidentally discovering some very severe damage that has been done to staff accountability structures resulting from misuse of Administrative Fiat and ignoring the Disciplinary process.</p> <p>I will reinstate this recommendation if necessary. I welcome advice from other staff members and site members here.</p> <p>Due to time constraints, I haven't caught up with comments in this thread or on-site. I'm not the only admin who can do this. But at this point, due to the immensity of the policy issues involved, most admins are choosing to wait on me <em>temporarily</em> before weighing in on certain aspects.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5121257</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5121257</link>
				<description></description>
				<pubDate>Sun, 31 Oct 2021 01:06:47 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>You can't rob staff of an ability they never have.</p> </blockquote> <p>Are staff not the ones who would've been voting on a potential censure vote against Magnus had he not resigned? Who, then?</p> <blockquote> <p>Magnus was still subject to a site ban if determined necessary.</p> </blockquote> <p>Sure, no site rules were broken (debatable, but for the sake of argument&#8230;). But that's not what I mean &#8212; 'such an action' referring explicitly to when people 'abuse their [staff] power'. So as it stands, you can do something that is an abuse of staff power but breaks no site rules, &amp; resign before facing consequences. Is this a good state of affairs?</p> <blockquote> <p>Are you planning to propose one?</p> </blockquote> <p>I don't need to. Disc releasing a statement about the incident that condemned the action would've been more than enough.</p> <blockquote> <p>I'm not familiar with this total silence.</p> </blockquote> <p>The incident occurred in November of 2020; Dex's statement on it was in June of 2021, and the Censure statement was like 2 weeks ago. Those are multiple month gaps in which nothing was communicated to the userbase or staff-at-large on the matter.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5120688</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5120688</link>
				<description></description>
				<pubDate>Sat, 30 Oct 2021 07:48:03 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Despite that, I feel that dismissing comments made by said group as just &quot;they're the guys who complain all day&quot; is not good faith engagement, since you're preemptively stating you do not want to hear what the other party wants to say.</p> </blockquote> <p>Sure, but I didn't see that happening, and you weren't talking about this.</p> <blockquote> <p>Additionally, even assuming that none of the admins/disc checked SCPD, (which would be false as we had multiple of both teams engage in the chat,) almost all comments brought up there were eventually brought forward to staffchat at some point or another, either due to unrelated discussion or through the channel we created exclusively to discuss SCPD's town hall channel.</p> </blockquote> <p>Agreed, but you weren't talking about this.</p> <p>Again, all I'm saying here is that admins had a valid, solid reason to (however incorrectly) assume that that specific group didn't represent the wider community or staff &#8212; and weren't lying to you about this, or speaking to you in bad faith. Wrong doesn't mean lying.</p> <blockquote> <p>Firstly, that &quot;this event was not made public at the time,&quot; since were the issue a breach of trust… wouldn't refusing to alert the rest of staff to a breach also constitute a breach of trust?</p> </blockquote> <p>No, not remotely. At the time, it was quite unclear how bad the breach was, or if it could be duplicated, etc. That's just staff being smart about what they bring to the public. I don't agree with this argument &#8212; there is no double standard, merely different circumstances.</p> <p>And then ultimately it wasn't brought up to (ironically) protect Cerastes (I'll explain this in another post, but you can see the advance screening preview in staff chat).</p> <p>(Also, FYI I think it was also totally unreasonable to expect Cerastes to immediately let people know. At the time, more people disagreed with me.)</p> <p>All that said, thank you for explaining.</p> <p>RE: staff agency to change minds &#8212; I'm a bit confused on this, but I think I may have misunderstood you and I'm okay letting this one drop.</p> <blockquote> <p>You're correct that showing a pattern of Bad Shit is required to demonstrate bad faith, but if the issue wasn't considered Bad enough, why suddenly switch it?</p> </blockquote> <p>I think I've now explained this in staff chat, and the same explanation will be coming to O5 too once I can fact-check it at least a little bit more.</p> <blockquote> <p>Or, better yet, why make a whole thread for it?</p> </blockquote> <p>Can you explain why this is a point of confusion? People keep mentioning it, but in a way that feels like&#8230; some kind of political talking point? It never comes with an explanation, lol. What's weird about creating a new thread once the first one has spun out of control? It's just a method of trying to &quot;reset&quot; discussion.</p> <blockquote> <p>As with last time, I am beat to the punch by a few months, so I point to UE, Weizhong, and Stormbreath's comments on the issue.</p> </blockquote> <p>I'm a bit confused, because while all these posts are very good ones, they do not touch on any of the questions I have and don't support the points you've been bringing up.</p> <p>As far as I can tell, unless I've gotten lost, this is about the charge that Dexanote approached the Cerastes situation with malice. Your posts have implied this, or at least that staff reasonably believed this. However, the posts you linked don't demonstrate this at all.</p> <p>Can you clarify why you linked me those posts?</p> <p>Also, ty for clarifying your POV. The accusation of &quot;following the leader (with any disc members who assumed the summary was enough)&quot; does seem compelling to me, now that I understand what you mean.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5120666</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5120666</link>
				<description></description>
				<pubDate>Sat, 30 Oct 2021 07:13:49 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>To be clear, Magnus resigning was not a self-punishment. I got sloppy later in my post.</p> <blockquote> <p>it served to rob staff-in-general of the ability to vote on a just penalty.</p> </blockquote> <p>You can't rob staff of an ability they never have. And could grant themselves still, but haven't.</p> <blockquote> <p>they could resign and have to face no substantial consequences for such an action.</p> </blockquote> <p>Magnus was still subject to a site ban if determined necessary. However, not a single person assessed (at least at the time) that Magnus' actions were worthy of banning.</p> <blockquote> <p>It failed to send the initial signal that staff at large agreed the behaviour to be unacceptable.</p> </blockquote> <p>Indeed, but that's because no such mechanism exists for ex-staff. Are you planning to propose one?</p> <blockquote> <p>I do not know whether admins+disc would've voted to censure, but not even allowing them the option as, while I do not think an abuse of power, deeply antithetical to the idea of staff accountability.</p> </blockquote> <p>No clue on Disc (though I'm going to find out if I can). Admins would have voted to censure. At the time, Magnus' censure was a certainty, Dex's was a likelihood, and Mann's was uncertain.</p> <p>I agree with you that it's deeply antithetical to the idea of staff accountability, but there were strong mitigating circumstances in Magnus' personal life which I believe you're well aware of, and more importantly, almost all my argument was &quot;it's not an abuse of power to resign, ever&quot;.</p> <blockquote> <p>The silence for several months after what was broadly considered to be a total fiasco served to let that idea sink in.</p> </blockquote> <p>I'm not familiar with this total silence. Can you elaborate? It may be relevant to this discussion.</p> <blockquote> <p>All this to say that I agree a self-censure would be out of line. But I'm not going to sit here and pretend that a resignation is equivalent to an official removal even if they result in the same end state — the context of the situation is something that must always be taken into account.</p> </blockquote> <p>I'm not asking for that, so it sounds like we're in agreement.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5120659</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5120659</link>
				<description></description>
				<pubDate>Sat, 30 Oct 2021 06:59:56 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>somewhat intimidating and was largely unheard of during my admittedly quite short time on staff before the great seal situation</p> </blockquote> <p>Yes, this is true. But it's not the world we're living in now, and ideally never will be living in again. And this example also doesn't support your original point &#8212; in fact, it contradicts it, because apparently people weren't too intimidated to go against everyone and side with Cerastes, and Disc was pressured really easily into going along (as they should be).</p> <blockquote> <p>my point would have been phrased better if i'd focused more on them having ultimate authority on whether or not a case is even judged - i've made a disc report about other staff members and i know of four of five others that have been made with zero 05 thread or even semi-public acknowledgement of the report. the team can use these poorly defined and vague guidelines (&quot;conduct unbecoming of a staff member&quot;) to entirely arbitrarily decide what gets judged by staff as a whole or not.</p> </blockquote> <p>I agree with all of this. I'm willing to investigate these reports if you send me a PM (not on Wikidot).</p> <blockquote> <p>you also acknowledge this is an issue (which is good) - do you have any solutions which don't involve every single report about a staff member going to 05 instantly? because that's the only fix i can think of, but it's not a particularly good one imo</p> </blockquote> <p>Yes &#8212; I'm considering solutions that involve an official review process that Disc can't skip. An obligation to tell the complainer about the decision on their complaint, at minimum. No &quot;memory holing&quot;, intentional or not.</p> <p>Also, IMO even if it can't be on O5, it CAN be in staff chat. This is similar to what I'm developing to solve the &quot;admin fiats don't get reviewed&quot; issue.</p> <p>(And yes that's a discussion for another thread. And it will happen, and soon.)</p> <blockquote> <p>if this happens, make it a discussion thread, so there's an obvious place to staff to object and a mainsite mirror for the community to object</p> </blockquote> <p>Sounds good. I've had to put a pin in this because I'm needing to put so much work into speeding up <em>this</em> censure, lol. Please feel free to remind later, as I said.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5120648</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5120648</link>
				<description></description>
				<pubDate>Sat, 30 Oct 2021 06:49:31 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Delayed response&#8230;</p> <p>I agree with everything you're saying re: Mann, but we've gotten off point. You said:</p> <blockquote> <p>It's pretty implicit that nobody is going to start censure proceedings against the de facto head admin and de jure Disciplinary Captain unless he acknowledges that he's okay with it.</p> </blockquote> <p>I want to make it as clear as I possibly can that this is false for Administrators at least.</p> <p>Mann is regularly held acountable by admins with zero fear, because he makes it clear with his approach to other admins that he welcomes criticism and is eternally open to change.</p> <p>I know who admins are afraid of calling out and why (and you may know some of the names &amp; reasons yourself), but Mann isn't one of them.</p> <blockquote> <p>I said it many times in SCPD's meta, both when senior staff had engaged there and when senior staff had decided not to anymore. I know I specifically pinged Dex with it and asked someone to port over the concern.</p> </blockquote> <p>I should clarify, in case it's not obvious, that saying something SCPD's meta isn't a report to admins or a report to staff. We were discussing staff chat.</p> <p>Have been investigating this anyway.</p> <blockquote> <p>What I just learned: we apparently don't remove people's permissions when they're censured.</p> </blockquote> <p>Censured staff &quot;may still participate in policy discussions in which their knowledge or experiences are relevant.&quot;</p> <p>Censured staff may use only the permissions necessary to participate in the policy discussions where their knowledge or experiences are relevant.</p> <p>If there are no such policy discussions (a very real possibility, currently), their permissions to access these discussion spaces are removed.</p> <p>That said, this was a pre-Discord policy, so we'll have to figure this out real quick. (The only recent censure was essentially for <em>disrupting</em> policy discussions, so this didn't apply.)</p> <p>Typically, censured staff also keep their Wikidot permissions. This was my own proposal, because Wikidot is an absolute disaster, and even when we created censure in 2016, it could take hours to demote and later re-promote a person.</p> <p>I don't see this as an issue, because <strong>using any power granted by rank while censured is inherently an abuse of power</strong> unless it's an absolute emergency confirmed by staff.</p> <p>This is the same power granted to Reserve Staff and Inactive Staff who somehow still have site permissions.</p> <p>(I think my prior post edit was me being confused and forgetting that censured people who have permissions intact can still use them in emergencies declared by other staff members.)</p> <p>If this is violated by an admin, other admins have grounds to immediately strip the admin of their rank and optionally ban them from the site. If admins do not, demotion and VoNC are also options.</p> <p>So, I strongly disagree that we need to be worried about &quot;watering down&quot; censure. I strongly advise that censure is kept as-is with respect to Wikidot permissions.</p> <p>I don't have much interest in this focus on making sure punishment hurts the punished sufficiently.</p> <p>TBH, it truly seems that people think censure is so dreadful that staff will do anything to avoid it while simultaneously being just a weaksauce slap on the wrist, with one or the other being emphasized depending on where we're at in an argument.</p> <hr /> <p>Whether Mann should be censured: Unlike with Dex, admins are still determining grounds with Mann. It's a thorny, complex issue. I personally share your uncertainty, but I would be shocked at this point if Mann doesn't at least get a Disc Vote up.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5115228</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5115228</link>
				<description></description>
				<pubDate>Sat, 23 Oct 2021 14:30:45 +0000</pubDate>
				<wikidot:authorName>DrBleep</wikidot:authorName>				<wikidot:authorUserId>2887044</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I care deeply about the policy and implications for the future, and I see the discussion here as productive and elucidating out the issues that have been plaguing us for the past year or so. It wasn't my intent to cede or step away from this discussion, but to a large extent I believe what happened here extends far deeper than just an issue with how disc handled this and comes down to the writing, organization, and presentation of our policies. As Lucio said upthread, and as Moose agreed with, the charter is outdated, poorly written, and poorly organized. Supplementary documentation, policy, guidelines, and precedent are <em>not even linked</em> on the charter page, but are placed on their own &quot;policy guide hub&quot; that is entirely separted and consists explicitly of nothing but a bunch of links.</p> <p>This is the most nonsensical, inefficient, and unsettling handling of policy organization I've had the misfortune of being exposed to. <em>It's no wonder this issue happened</em> because along with the lack of a proper system to track major projects/policy initiatives/investigations and administrator level tasks and/or the often hamstrung nature of our administration, our core governing document is so poorly written it leads to major misinterpretations, hour long debates, and both staffers and administrators wholesale throwing out or ignoring entire sections of it. This is not good policy, this is not sustainable, and this is not even remotely a good thing for a major governing document to have happen.</p> <p>This is why when I return from dealing with familial issues, I will be taking a sledgehammer to our policy hubs, condensing policy, and improving our presentation and accessibility so that we avoid further issues like this in the future. The Charter rewrite is in Meat's hands, but I have no qualms of undertaking and executing a complete rework of how and where we present our policy guidelines.</p> <p>I wasn't part of disc at the time, but I have since apologized for my role in the November 2020 incident. I feel like and have felt like I was responsible for some of the pressure, I have personally apologized to Cerastes several times for my role.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5113954</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5113954</link>
				<description></description>
				<pubDate>Fri, 22 Oct 2021 06:38:46 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Rounderhouse generously pointed out that Wikidot ate my response here. It's accessible via my Wikidot profile only. I appreciate this very much, lolsob.</p> <p>Copying some of it here.</p> <blockquote> <p>The difference is utterly nominal because there are no actual mechanisms for wider stuff to ensure accountability on Disc.</p> </blockquote> <p>We're working on this actively. Some of this is now public &#8212; as in, Disc access is being rolled out to general staff. Also, all votes and decisions are being moved to O5.</p> <blockquote> <p>because there is no mechanism for wider staff to call out this nonsense</p> </blockquote> <p>There have been several mechanisms this whole time: posts in open staff chat on Discord, discussion on O5, and reports privately to admins. 1 and 3 led me here.</p> <p>It's also relevant that they were mostly (not entirely! or we wouldn't be here!) to push claims of active malice that had no evidence, as well as a whole lot of policy misunderstandings. That is true in this thread also.</p> <p>Obviously I don't really hold this against anyone, since&#8230; well, this thing stemmed from <em>Disc</em> having policy misunderstandings and inappropriately assuming malice.</p> <p>But, yeah. You've told me before why you didn't use the second two mechanisms, and you made fair points. But that's not the same as <em>no</em> mechanism.</p> <blockquote> <p>and there will never be one until Disciplinary loses the cladding of sensitivity and secrecy which it never originally had and evolved somewhere along the line.</p> </blockquote> <p>Agreed. WIP.</p> <blockquote> <p>It is profoundly fucked up that Disc and Admins will be the ones voting on whether to censure an administrator who is the captain of Disc.</p> </blockquote> <p>I don't like this either. At minimum, we should have the ability to open this up. This is possible to achieve and I am recommending we do so.</p> <blockquote> <p>But I'd like to clarify whether the last bit, about the censure, means that censure proceedings will begin by then or that discussion of whether or not you want to begin censure proceedings will begin by then.</p> </blockquote> <p>Admins have already decided we want to begin censure proceedings, and ASAP. This time is being used to draft documents, collect all charges, make sure there are no new errors, etc. (And also opening up Disc because we felt that to be just as urgent. And addressing related policy fuckery.)</p> <p>Disc has not yet officially been consulted, but will be. This is subject to Aismallard's availability as acting Disc Captain for this issue. I can confirm I'm helping her so that things move faster and she's working as fast as she can.</p> <p>The amount of writing work necessary to do this right is extremely high, but we've made a lot of rapid headway. We are working on this daily, significantly.</p> <p>Quoting directly from my previous post now&#8230;</p> <p>It is paramount that admins try to avoid messing this up even further. We're not taking our time, but we can't just throw up an O5 thread besides … well, this one. I personally don't think Dex should've even &quot;rushed&quot; his statement to the extent he did, because he mis-phrased some things, all of which have been thoroughly raked over in this thread. :)</p> <p>Please also note that discussion of censure proceedings is supposed to be informed by this discussion thread. And it will be, even if it's just the same few people posting on it, which right now is the case. But I hope more people will weigh in, too. Right now, we really do have an obligation to wait to ensure staff feel comfortable chiming in, at least until we can physically compose more of our statements.</p> <p>Thank you again for letting me know that Wikidot ate my post!</p> <p>EDIT: WELL&#8230; now I think both posts have appeared&#8230;</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112548</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112548</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 09:13:19 +0000</pubDate>
				<wikidot:authorName>EstrellaYoshte</wikidot:authorName>				<wikidot:authorUserId>3781861</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Alright, because my brain is small and I am terrible at addressing multiple points at once, forgive me if I missed some critical context or information.</p> <p>(In the interest of transparency, I have not fully read the Alchemy Department series, but have read Cerastes's 001 in full <em>in its final form</em> on the wiki.)</p> <p>Here is the four context points at the time that I, a then mostly uninvolved observer, was aware of:</p> <p>1. Magnus had not published any Great Seal 001 for his canon.</p> <p>2. Magnus had no public or known draft of his supposed 001 proposal about the Great Seal.</p> <p>3. No plans for an Alchemy Great Seal 001 was ever made public to my knowledge.</p> <p>4. Ceraste's 001, when on the wiki, did not contain any direct, involved reference to the Alchemy Department, and the aforementioned Great Seal was not about Alchemy, it is about the Adytum canon.</p> <p>So I do not know how (assuming <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/dexanote" ><img class="small" src="https://www.wikidot.com/avatar.php?userid=481882&amp;amp;size=small&amp;amp;timestamp=1696953891" alt="Dexanote" style="background-image:url(https://www.wikidot.com/userkarma.php?u=481882)" /></a><a href="http://www.wikidot.com/user:info/dexanote" >Dexanote</a></span> had discussed it with Disc team beforehand) no one realized plagiarism would've been flat-out impossible as we judge it currently. By creating an entire thread to address it, which was then extended to cover an unrelated issue, it would've been crossing several continuous blind spots at best, and a gross misstep in Disciplinary process by the entire Team at worst.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112521</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112521</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 08:18:26 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm not gonna respond to most of the stuff, because it's Cyv's argument to make and defend.</p> <blockquote> <p>It literally is impossible, then or now, for Magnus to receive a punishment that could outdo what he did himself…</p> </blockquote> <blockquote> <p>I don't personally like Magnus' decision to resign, but: Magnus enacted upon himself (at minimum) the worst punishment that Staff can enact without a Site Rules violation, which is Removal from Staff.</p> </blockquote> <blockquote> <p>Why does it matter that it wasn't a punishment officially enacted by Staff?</p> </blockquote> <p>But regarding everything related to Magnus' resignation being a maximal punishment: all of your statements rest on the idea that Resignation == Removal. I don't think that's true. Sure, it results in the same end state (user is no longer on staff) but the connotation and context is inarguably different, so different that I'd say resignation is not always a punishment, if ever.</p> <p>Resignation &#8212; for the purposes of the argument we'll look to controversial resignation rather than &quot;I don't really have time anymore bye&quot; which I doubt anyone has a problem with &#8212; can come from two places. One is a generous assumption - user knows what they did was wrong, user wants to own up to it, make things right in their capacity, steps down. Okay, sure, whatever. Other one is less generous &#8212; user realizes they fucked up, but the resignation is motivated more by a desire to avoid institutional punishment for that fuck-up. Pretty bad. We can't read minds, but we have complex reasoning capacity to discern which situation is which, I think. Personally, I've stated my reasons for believing Magnus was the latter in the mainsite mirror thread. Anyway - respectively, they have Good and Bad social connotations.</p> <p>Removal from staff, on the other hand (again, under controversy - not counting someone getting boosted for inactivity), sends an extremely clear and obvious signal: staff disapprove of the actions taken by this user in an official capacity, and has deemed them Unfit For The Job. No ambiguity for this one.</p> <p>Based on that, you can imagine why I - and I would venture a guess that most people agreeing that Dex should be censured - view Magnus' resignation from staff as not a punishment at all but the <em>lack</em> of a punishment. &quot;The infliction or imposition of a penalty as retribution for an offense&quot; &#8212; rather than a penalty, it served to rob staff-in-general of the ability to vote on a just penalty.</p> <p>The idea that it wasn't a punishment officially enacted by staff set the idea that if someone did abuse their power &#8212; not by resignation, but by a plagiarism accusation done without due diligence, without evidence, and with an exceedingly suspiciously-timed follow-up thread &#8212; they could resign and have to face no substantial consequences for such an action. It failed to send the initial signal that staff at large agreed the behaviour to be unacceptable. I do not know whether admins+disc would've voted to censure, but not even allowing them the option as, while I do not think an abuse of power, deeply antithetical to the idea of staff accountability. The silence for several months after what was broadly considered to be a total fiasco served to let that idea sink in. And then a statement saying that censure was considered but couldn't be enacted on any of the individuals served to hammer it in over another several months of silence.</p> <p>All this to say that I agree a self-censure would be out of line. But I'm not going to sit here and pretend that a resignation is equivalent to an official removal even if they result in the same end state &#8212; the context of the situation is something that must always be taken into account.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112511</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112511</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 07:59:31 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'll preface aswell that I'm enjoying that you're also taking the time to properly respond. Just want to make sure that my <em>lack</em> of prefacing doesn't make it seem like I'm disliking it or anything.</p> <div class="collapsible-block"> <div class="collapsible-block-folded"><a class="collapsible-block-link" href="javascript:;">[here&nbsp;we&nbsp;go]</a></div> <div class="collapsible-block-unfolded" style="display:none"> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">–&nbsp;hide&nbsp;block</a></div> <div class="collapsible-block-content"> <blockquote> <p>You quoted my post and said that my post came off that way lol. Wouldn't that be… me pulling this trick?</p> </blockquote> <p>I was referring to the generalized statements, which I assumed to also be speaking for the rest of the admins. As I said in the other response, &quot;if those were meant merely as your interpretations of what happened, then I take back my case here.&quot;</p> <blockquote> <p>You know this to be the case, because you know who has made almost every single post in this thread besides me, and brought almost every accusation.</p> </blockquote> <p>That's fair. On the other hand, this group of people is also notoriously the most vocal about issues in staff as a whole, so it does make sense that they'd be the ones to most often bring points of contention up.</p> <blockquote> <p>and saying your opinion is held by essentially ALL of SCPD</p> </blockquote> <p>I didn't mean to say that, and apologies if it came off that way.</p> <blockquote> <p>With this new context, can you please elaborate and give evidence?</p> </blockquote> <p>Certainly. I will concede on how most of these comments were brought forward by the same group of people, and typically came from the exact same source. I will also concede that having only a specific group of people speak up while others who also share said opinion refuse to comment on the matter may end up making said group seem like the only people who take issue with these actions.</p> <p>Despite that, I feel that dismissing comments made by said group as just &quot;they're the guys who complain all day&quot; is not good faith engagement, since you're preemptively stating you do not want to hear what the other party wants to say. Additionally, even assuming that none of the admins/disc checked SCPD, (which would be false as we had multiple of both teams engage in the chat,) almost all comments brought up there were eventually brought forward to staffchat at some point or another, either due to unrelated discussion or through <em>the channel we created exclusively to discuss SCPD's town hall channel.</em></p> <blockquote> <p>Perhaps staff gravitated towards the abusive shit. IDK!</p> </blockquote> <p>Entirely fair; most of it <em>did</em> end up abusive. I just brought up twitter as an example of another social media platform I knew which discussed the topic extensively.</p> <blockquote> <p>I'm not aware of an IRC breach? I thought this was a Discord breach.</p> </blockquote> <p>It was a discord breach? I was sure until now it was an IRC breach. Then again I did read the original thread under the impression that SSSC was an IRC thing, so that may just be due to that.</p> <blockquote> <p>I saw zero merit in them, then and now.</p> </blockquote> <p>So: The initial post on [2] states that &quot;Cerastes’ brother was able to access SSSC&quot; and additionally that he &quot;did not volunteer this information on his own, but explained what happened only after being pressed by other users. He knew very early on[.]&quot; It's explicitly stated that &quot;the failure of Cerastes [was] to report that a non-staff person was let into a staff-only chat for several hours.&quot; Having other people's private conversations be exposed to strangers &quot;without their knowledge or consent&quot; was an issue.</p> <p>However, a few things come up aswell. Firstly, that &quot;this event was not made public at the time,&quot; since were the issue a breach of trust&#8230; wouldn't refusing to alert the rest of staff to a breach also constitute a breach of trust? As stated by CaptKirby: &quot;If this trust is something that is so important that losing it is grounds for demotion, then it feels like we are using a double standard. Upthread, it is cited that staff are meant to be held to a higher standard, and by virtue of that, should our moderators, admins, etc be held to a higher standard than our operational and junior staff?&quot;</p> <p><a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2#post-4828025">Kirby said everything I think about this situation much better than I could</a>, so I recommend just looking through that.</p> <blockquote> <p>This implies a lack of staff agency to change minds, doesn't it?</p> </blockquote> <p>Not quite. My point was that while they all had the agency to change their mind (and many of them indeed did), the issue came to be with the total trust that whatever the initial post said was unbiased and fully factual, especially with a case that was as large as that. Many of them just assumed Dex had it all under control, which is understandable of course, but when part of your job is to make sure that no one else dropped the ball you can't quite afford to go &quot;eh, I'm sure someone else made sure of it.&quot;</p> <p>I wasn't saying they were mindless sheep or anything of the sort, I meant that they had a little too much confidence to assume that the initial post was peachy clean.</p> <p>(I'm assuming this was the situation mostly due to how divided the opinions of disc and non-disc at the start of each thread, which I can only attribute to that sort of &quot;i'm sure it's fine&quot; attitude.)</p> <blockquote> <p>Is this not standard procedure for disciplinary issues in general?</p> </blockquote> <p>Not exactly. Most disciplinary threads list stuff that was either considered an issue beforehand, or stuff that's already been made public. For example - let's say user X acts like a dick for the bazillionth time. Their thread would discuss stuff written in their non-disc/disc threads, and other instances which were at the time considered &quot;dick moves.&quot; In this case, the issue brought up was both never made public, apparently not even to some disc members (&quot;I [..] was not aware of the event until partway through initial conversation, nor were several other Disciplinary Team members aware&quot;), and even so the instance was considered at the time to not be an issue worth bringing up (&quot;A majority of those present saw it as ‘dealt with’ [&#8230;]&quot;).</p> <p>Bringing up something that wasn't a problem and seemed to not even be worth bringing up was the point of contention.</p> <p>You're correct that showing a pattern of Bad Shit is required to demonstrate bad faith, but if the issue wasn't considered Bad enough, why suddenly switch it? Or, better yet, why make a whole thread for it? As with last time, I am beat to the punch by a few months, so I point to <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2#post-4827341">UE</a>, <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2#post-4828190">Weizhong</a>, and <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2#post-4828843">Stormbreath</a>'s comments on the issue.</p> <blockquote> <p>May I ask that you do so?</p> </blockquote> <p>Sure thing. I do agree with the counts of hypocrisy (towards those who were aware of the breach and didn't bring it to anyone else's attention) and following the leader (with any disc members who assumed the summary was enough). On the count of &quot;having it out for Cerastes&#8230;&quot; I dunno, Hanlon's Razor and all. I feel like there may have been <em>some</em> malicious actors involved, but seems that most people just honestly thought they were doing the right call.</p> </div> </div> </div> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112469</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112469</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 07:21:11 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Correct, but calling him Head Admin and giving that as evidence for why Disc/Admins will defer to him is not correct.</p> </blockquote> <p>To me, saying someone is the head admin and saying someone is the <em>de facto</em> head admin are different things. One is an objective statement of rank, and one is a subjective claim of someone's seniority affecting their position in an informal, unquantifiable way. Which I think Mann's does. Not necessarily badly, but it does. I've said this a lot to you, but I think it's one of those things we're not gonna change each other's minds on lol</p> <blockquote> <p>he has endeavored to not enable any corruption [&#8230;] You may not believe this [&#8230;]</p> </blockquote> <p>If you mean Mann's character &#8212; I don't just believe it, I can attest to it. He's a stand-up guy, and I think you'd actually be hard-pressed to find someone around here who disagrees. Generally the worst that people can say about him is that they don't really know him, and there are far worse problems someone can have than that.</p> <p>All that said, Mann's strong moral fibre is irrelevant to my point &#8212; which isn't so much about Mann as it is about the other admins. About how I think the social dynamic works in any situation where you have to suggest punishment for the guy who <em>technically</em> owns the community, captains one of the most important teams, and has been an admin since before you caught your first whiff of SCP. It's not as simple as it is when you're suggesting it to a direct peer, or as close as you can get to one all the way up there.</p> <blockquote> <p>If it's not too much trouble, may I ask you to provide me these requests? Text + chatroom name would be sufficient.</p> </blockquote> <p>I said it <em>many times</em> in SCPD's meta, both when senior staff had engaged there and when senior staff had decided not to anymore. I know I specifically pinged Dex with it and asked someone to port over the concern. I know I've also brought it up in staffcord at least once, as have other JS &#8212; I specifically remember during the DISC-J incident someone asked Dex during the conversation why he hadn't taken it. I don't remember an answer being given but I could just have missed it.</p> <blockquote> <p>The emergency ban issue would also be solvable by consensus of OS+ staff declaring that these particular censures can allow for emergency bans only.</p> </blockquote> <p>What I was going to say: I would be resistant to this on the basis that a month of censure is already a slap-on-the-wrist punishment and doing that with the added caveat that they retain their technical permissions further waters down the symbolism of an already-symbolic (but still important!) punishment.</p> <p>What I just learned: we apparently don't remove people's permissions when they're censured.</p> <p>I think this is dumb. I don't know if this is the censure we should pick to begin this but I think removing perms for the duration of the censure is a good policy to keep, going forward, for the reason above.</p> <hr /> <p>All this is kind of moot anyway because I'm not even sure I think Mann should be censured. I am much more steadfast in my opinion Dex should be and Magnus should have been, but I'm not so sure about Mann. Without actual logs, I am left to the positions at play - Magnus was at the center of the incident, Dex was the captain of the team and began the second Disc thread, but Mann's involvement was limited to any posts he made in the threads, same as anyone else. Greatest sin being that he shouldn't have let it happen &#8212; which, if we're going there, is something that extends to all members of Disc. Conclusion being that Mann's actions were the same as anyone else on Disc or staff but he would be punished harsher because of his seniority despite not being Cap or VC of Disc. Ugly precedent to set, but then it's a complicated situation.</p> <p>I think all of Disc needs to take a public L for that incident, but only Dex (and Magnus, if he was still around and in this hypothetical presuming he hadn't been punished harsher) really needs to take a censure.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112467</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112467</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 07:16:50 +0000</pubDate>
				<wikidot:authorName>gee0765</wikidot:authorName>				<wikidot:authorUserId>5376871</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>This is non-optional, means Disc can't decide to arbitrarily demote or censure</p> </blockquote> <p>i'll concede that yes, disc can't arbitrarily demote/censure people alone. they can, however, put up a thread calling for demotion or censure for these extremely vaguely defined reasons, at which point you have to have large numbers of staff Going Against Disc (somewhat intimidating and was largely unheard of during my admittedly quite short time on staff before the great seal situation) to avoid the staff member being punished.</p> <p>my point would have been phrased better if i'd focused more on them having ultimate authority on whether or not a case is even judged - i've made a disc report about other staff members and i know of four of five others that have been made with zero 05 thread or even semi-public acknowledgement of the report. the team can use these poorly defined and vague guidelines (&quot;conduct unbecoming of a staff member&quot;) to entirely arbitrarily decide what gets judged by staff as a whole or not. and since so much is thrown out (from the perspective of an outside observer), there's a feeling that things which aren't 'thrown out' are particularly serious</p> <p>you also acknowledge this is an issue (which is good) - do you have any solutions which don't involve every single report about a staff member going to 05 instantly? because that's the only fix i can think of, but it's not a particularly good one imo</p> <blockquote> <p>If this power is used for something else, something has gone wrong, and accountability must be had. (I think this may have occured recently followed by an apology but I'm foggy on this.)</p> </blockquote> <p>assuming we're talking about the recent-ish misuse of fiat here, you're correct(ish). i'm not going to go super in-depth (as strong as my feelings on the admin fiat are, this isn't a thread for discussion of it), but i wouldn't say that there was <em>accountability</em> (i have issues with relying on loud staff members who are fine with calling out admins being around in staffchat at the exact correct time to call out admins for misuse of fiat) or a particularly defined apology (have just reread the logs to check this. i can't see anything myself, but may be missing something). that being said, you're right that the fiat <em>was</em> withdrawn</p> <blockquote> <p>Right now I'm going to err on the side of asking admins to agree to not ever do this again and say so on O5.</p> </blockquote> <p>if this happens, make it a discussion thread, so there's an obvious place to staff to object and a mainsite mirror for the community to object</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112461</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112461</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 07:07:41 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>More questions, answered in a separate post. (Please note I forgot to post this before responding to two people above. Refer here for context.)</p> <h2><span>Why Follow the Charter?</span></h2> <p>Yes, it's hard to deal with, but that's mostly because it's just badly written and badly edited and doesn't correctly link to policy.</p> <p>Mostly the actual policy is either solid, or already sidestepped with universal staff consensus (such as the absurdly short deadlines). Admins have the power to do this <em>if and only if</em> they are met with essentially universal agreement (again, as with the absurdly short deadlines).</p> <p>But admins cannot do this for ANY other reason!</p> <p>Have they? Yes. As far as I know, without malice, but it must change, and it must change now. We are working on rectifying this now.</p> <p>We are also working on improving the writing and bringing together staff suggestions for change.</p> <p>Most importantly, the Charter has built-in accountability processes and requirements to do certain things <strong>that are there for a reason.</strong> Which have not always been followed. <em>Many</em> of the things staff have recently been complaining about can be fixed by following the parts of the Charter that no one had any permission to ignore! Including admins.</p> <p>&quot;Just doing what staff pressure you to do, and fuck the Charter&quot; is <em>how we got here</em> in the first place.</p> <p><strong>@Limeyy:</strong> (&amp; others)</p> <blockquote> <p>The obvious answer is to take the path of least resistance instead of adding weeks of bureaucracy and newly invented rules to a process that's already 11 month's overdue.</p> </blockquote> <p>If admins need to take more than a few days, then I have recommended (along with Dex) that we ask all of staff for permission to sidestep the full charter process and speed things up with specific steps that will be laid out then.</p> <p>Due to the circumstances, I strongly recommend that admins do not use their power to sidestep the charter process in any other way. That may help with social pressure from (so far!) a few specific staff members, but it risks making serious mistake even worse.</p> <h2><span>Addressing Dexanote</span></h2> <p>In the interest of speeding up this discussion: I can confirm that Dex intended to apologize again here and believes he owes another apology. I am writing this part of this post (and only this part) because Dex is unavailable presently for personal reasons.</p> <p>Admins prepared multiple statements; this one, in my opinion, was a bit rushed (though not unduly so). Pretty sure Dex messed up here, thinking he included the apology part when he didn't yet. So while this is embarrassing, I would encourage everyone not to read this as malice.</p> <p>Also, further apologies &amp; explanations are forthcoming.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112444</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112444</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 06:51:18 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Preface: Again, I appreciate the engagement.</p> <blockquote> <p>My concern was moreso that it came off as if the admin team was pulling this trick.</p> </blockquote> <p>How? You quoted my post and said that my post came off that way lol. Wouldn't that be&#8230; me pulling this trick?</p> <p>Appreciated re: post edits &amp; clarifications.</p> <blockquote> <p>but rather the admins who were both active in the discussions and claimed to have no idea how the disciplinary thread was taken by the wider community.</p> </blockquote> <p>I felt they gave a very good explanation of this: the same group of people is the source of almost all this feedback.</p> <p>You know this to be the case, because you know who has made almost every single post in this thread besides me, and brought almost every accusation.</p> <p>I've also seen it verified by SCPD mods to admins &#8212; one personally to me &#8212; that the vast majority of the rhetoric is localized to specific friend group in SCPD. <strong>This group's opinions are still 100% valid, and now admins understand that the problem does not lie with one vocal group.</strong></p> <p>However, no one who's part of this friend group has openly acknowledged or debunked this apparent fact, including you, here, now. Claims are only made that you do in fact reasonably represent all the community, but no evidence is given&#8230; besides referencing SCPD as synonymous with all the community (and saying your opinion is held by essentially ALL of SCPD, which has been contradicted to admins (and personally to me!) by quite a few SCPD users).</p> <p>Others may <em>silently agree</em>, but admins cannot be mind-readers. (This is also why I've asked other staff to collect evidence that Disc/Admins were shown evidence that was ignored.)</p> <p>Either way, well&#8230; I hope everyone reading this thread can see how this <em>might cause some good-faith confusion.</em></p> <p>Especially looking at this thread. All the confusion, accusations, etc. And this is WITH admins specifically calling out unacceptable behavior openly.</p> <p>So, you claim admins to have spoken in bad faith, not good faith. With this new context, can you please elaborate and give evidence?</p> <p>Also, I did participate briefly in the post-discussion of the Nov 2020 incident. IIRC I said that Magnus and Dexanote should be considered potentially subject to censure, at almost the same time that Magnus quit, and then I discussed the aftermath, including recommending that Dex &amp; Mann could not and should not self-censure. After this, I believe I was absent from these discussions for some time up until a few months ago (ish? post-Harmony).</p> <blockquote> <p>but this went down in twitter and multiple other servers aswell (and I assume some other locations I'm not even aware of at the moment).</p> </blockquote> <p>Twitter has been a source of real-world harassment for people, and outright abuse towards staff, sometimes severe. That said, admins were well aware of the discussion on Twitter, and that's where some of my statement of &quot;most of them were purely personal attacks, false statements about occurences, claims of malice with no evidence, or false statements about how policy and/or Disc work&quot; came from.</p> <p>Please also note that staff could have easily missed some discussion on Twitter. Perhaps staff gravitated towards the abusive shit. IDK! Can you point me to any discussion that doesn't fall under the categories I mentioned above? (I acknowledge I could've VERY easily missed some &#8212; I don't really participate excessively in SCP twitterspheres.)</p> <p>Also, Twitter is <em>literally known for</em> having algorithmic &quot;bubbles&quot; and encouraging a &quot;parrot the leader&quot; mentality.</p> <p>With this in mind, do you think admins must be held accountable for not seeing the discussions you reference?</p> <p>As for Discord servers, I don't know which ones you might mean. This could be a failing on my part. However, I lurk a lot of SCP discussion online and I don't know if I agree with the implication that I must be in specific servers to carry out my job as admin, nor would I apply this to anyone else.</p> <blockquote> <p>Many of the issues which made the disciplinary thread to be as infamous as it is now were either worsened or were formed in the second thread, regarding the IRC breach.</p> </blockquote> <p>I'm not aware of an IRC breach? I thought this was a Discord breach.</p> <blockquote> <p>with how Cerastes was accused of hiding something for less than two days, when the admins (iirc) did so for over a month</p> </blockquote> <p>I saw these accusations, but I have to say, I saw zero merit in them, then and now. Open to hearing otherwise.</p> <blockquote> <p>blindly following the leader (with the split between opinions held by the initial Disc posts to the posts made by the rest of staff)</p> </blockquote> <p>Huh. This implies a lack of staff agency to change minds, doesn't it?</p> <blockquote> <p>having something out for Cerastes (with how the two topics seemed weirdly unrelated, with the only connection being 'cerastes did something wrong')</p> </blockquote> <p>Is this not standard procedure for disciplinary issues in general? I understand that &quot;demonstration of bad faith&quot; is pretty much based on &quot;look at several things this person did wrong. together, they show a pattern of Bad Shit.&quot;</p> <p>(The issue, obviously, is that both instances were grossly blown out of proportion, were not Bad Shit, and were undeserving of any punishment, and Disc should have seen that. But I'm asking about your impression of this specific point.)</p> <blockquote> <p>I'm not claiming all of these points are valid or invalid, I'm merely stating this is where they formed.</p> </blockquote> <p>Well, this thread is very much for claiming that these points are valid or invalid. May I ask that you do so?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112429</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112429</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 06:20:25 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Okay, response time (acknowledging we discused a few things beforehand because I was a little confused &#8212; I appreciate this! and, believe it or not, that made this message far shorter).</p> <blockquote> <p>At this point, it has become more than evident that Disc was never going to be able to censure Dex nor Mann, whether this comes as a result of internal politics or a failure to perform their due diligence is irrelevant.</p> </blockquote> <p>Admins make up a whole lot of Disc. Admins created this thread, with heavy Disc involvement. &quot;Never&quot; is demonstrably not the case!</p> <p>If you believe I'm wrong, please bring evidence to the table for &quot;never&quot;. You say it's evident, despite everything I said before you posted in this thread &#8212; evident implies evidence.</p> <p>Regarding Disc itself, as you likely now know, this is being addressed. Accountability and transparency structures have already been announced publicly, and more will follow.</p> <blockquote> <p>with the issue of plagiarism being addressed by users unversed in the rigours of plagiarism</p> </blockquote> <p>That's almost everyone on wiki staff, and at the time it was worse.</p> <blockquote> <p>Frankly, I disagree, this was not a harsher punishment. He voluntarily chose to resign his authority, freeing himself from the burden of punishment.</p> </blockquote> <p>I meant that demotion represents a harsher punishment than censure.</p> <p>I wrote this in response to someone saying self-censure would be considered fine by everyone. This is, as we've discussed, vastly incorrect.</p> <p>Actually, you and I here agree: <strong>We both think self-censure is an abuse of power, because it grants the ability to determine one's own censure length and remove the option for other forms of discipline.</strong></p> <p>We disagree only in that I think resignation is not and definitionally cannot be an abuse of power.</p> <p>I will explain, using Magnus as an example, per discussion:</p> <p>There are only a few possible punishments without breaking a Site Rule that can be enacted by Admins &amp; Disc without using a VoNC. In ascending order of seriousness:<br /> - Censure, which always ends with full restoration of privileges: even under extreme circumstances, Magnus would now be an Admin (unless he got removed for another reason). This is the least serious.<br /> - Demotion: Magnus would lose rank, being demoted to Mod or OS. (I'm unsure anyone ever suggested this.)<br /> - Removal from Staff, which is what Magnus did to himself. If Staff removed him, it would be easier for him to come back. But he removed himself, which caused a lot of chaos. So&#8230; well, you do the math.</p> <p>It literally is impossible, then or now, for Magnus to receive a punishment that could outdo what he did himself&#8230;</p> <p>&#8230;Unless you think he should've been banned. Which&#8230; well, why would we do that? He didn't violate site rules, and it's circular to say &quot;Magnus should be banned for avoiding censure/demotion/removal&#8230; by enacting the harshest forms of these on himself.&quot;</p> <p>And I don't think you want this to have the consequence of a ban anyway. If that's true, what would you suggest?</p> <p>Also, more below.</p> <blockquote> <p>Staff were left unable to account for his actions because he had already stepped away and excused himself of the issue. This, by any stretch of the definition, would be considered a direct abuse of authority.</p> </blockquote> <p>When you say &quot;by any stretch of the definition&quot; for an opinion that you know you are in the minority for, can you please give evidence and a more detailed argument?</p> <p>I don't personally like Magnus' decision to resign, but: Magnus enacted upon himself (at minimum) the worst punishment that Staff can enact without a Site Rules violation, which is Removal from Staff. How can this be an abuse of authority?</p> <p>Why does it matter that it wasn't a punishment officially enacted by Staff?</p> <p>Additionally, how can it be an abuse of authority if literally any staff member can do this and they always have been able to?</p> <p>How can it be an abuse of authority to <em>have personal boundaries and need to leave an online writing community?</em></p> <p>What exactly would you recommend we do to staff who resign without &quot;permission&quot; in such cases?</p> <p>Do you think they should be forced to stay in a staff position?</p> <p>How do you propose enforcing this?</p> <p>Finally, can you give any other evidence or further explanation why resignation is a direct abuse of authority?</p> <blockquote> <p>The argument being made here by users is that Disc has the power and authority to read above and beyond the Charter and/or Disciplinary policy due to its inherent vagueness, thus allowing them to arbitrarily determine whether or not to deliver action.</p> </blockquote> <p>How is this the argument being made here? Did you misread, or have I?</p> <blockquote> <p>something they are perpetuating to this day by choosing to deliberate further on the punishment.</p> </blockquote> <p>1. Admins are currently handling this process stage, not Disc.<br /> 2. Disc &amp; Admins are required to allow time for a discussion thread by the Charter, as well as to prepare statements and post threads. Do you think we have allowed too much time for this discussion thread? If so, can you elaborate?<br /> 3. Do you think admins are delaying statements and delaying posting of threads, currently &#8212; including by taking extensive time to respond to you? If so, can you elaborate?</p> <blockquote> <p>Either reform must occur internally amongst yourselves, which can then be brought before the rest of Staff to be voted upon as with all proposals</p> </blockquote> <p>1. All proposals are not required to be voted on by all staff. Have I misunderstood? If not, can you provide evidence?<br /> 2. I know you dislike red tape. Why do you consider this an exception?<br /> 3. Since you posted this, Aismallard and Dexanote began the process of enacting transparency and accountability measures for Disc. Do you think this was a mistake, and should have been voted on by all staff? If so, why?</p> <p>(Going to stop here due to time limitation, but others can respond.)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112372</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112372</link>
				<description></description>
				<pubDate>Wed, 20 Oct 2021 04:56:19 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Since our responses are all extremely long now, I'll start collapsing them, so people don't have to scroll past multiple textboxes whenever they open the thread.</p> <div class="collapsible-block"> <div class="collapsible-block-folded"><a class="collapsible-block-link" href="javascript:;">[insert&nbsp;word&nbsp;vomit&nbsp;here]</a></div> <div class="collapsible-block-unfolded" style="display:none"> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">–&nbsp;hide&nbsp;block</a></div> <div class="collapsible-block-content"> <blockquote> <p>If you believe Disc &amp; admins were right to ignore this aspect of the charter, then you're free to say so.</p> </blockquote> <p>I wasn't trying to comment on whether this choice was good or bad, merely how the situation came to be. Personally I don't think they should have, but I don't think that opinion will surprise anyone.</p> <blockquote> <p>I hope it's clear to everyone, including you, that I am not doing this.</p> </blockquote> <p>Clearly not; you wrote up a massive post here explaining your every reasoning. My concern was moreso that it came off as if the admin team was pulling this trick.</p> <blockquote> <p>You have omitted my &quot;most of&quot; clarification.</p> </blockquote> <p>Yes, yes I did. That was a legitimate accident, adding &quot;only&quot; there changed the original meaning of the quoting. I'll edit my original response in a second.</p> <blockquote> <p>I did not and do not make this claim for Disc, but ONLY complaints sent to admins, myself personally, or AHT, plus a few others I sought out myself.</p> </blockquote> <p>Ditto on the last response - I legit was confused for a second which one of the two received the complaints. Will change the comment appropriately, but I feel that even with these two edits much of the point still stands.</p> <blockquote> <p>you have strongly implied that I have spoken in bad faith, which I believe to be intentional. Can you please clarify?</p> </blockquote> <p>Not <em>you</em>, specifically, but rather the admins who were both active in the discussions and claimed to have no idea how the disciplinary thread was taken by the wider community. I was taking your comments which mentioned &quot;admins&quot;/&quot;we&quot; as generalizations. If those were meant merely as your interpretations of what happened, then I take back my case here. (I said that it's either that or that the admins didn't really participate in any of the post-discussions about the Great Seal - which you didn't, so that solves that mystery.)</p> <blockquote> <p>well, not participating in SCPD doesn't mean the same as what you just said it means. So did I misunderstand?</p> </blockquote> <p>SCPD was not the only location where such discussion was going down. SCPD was the most vocal, due to it being a fast-paced, well known chat server with numerous members of the community, but this went down in twitter and multiple other servers aswell (and I assume some other locations I'm not even aware of at the moment).</p> <blockquote> <p>May I request that you clarify this point?</p> </blockquote> <p>Many of the issues which made the disciplinary thread to be as infamous as it is now were either worsened or were formed in the second thread, regarding the IRC breach. Accusations of hypocrisy (with how Cerastes was accused of hiding something for less than two days, when the admins (iirc) did so for over a month), blindly following the leader (with the split between opinions held by the initial Disc posts to the posts made by the rest of staff), having something out for Cerastes (with how the two topics seemed weirdly unrelated, with the only connection being 'cerastes did something wrong'), etc.</p> <p>I'm not claiming all of these points are valid or invalid, I'm merely stating this is where they formed.</p> <blockquote> <p>I intend to continue this approach as much as I can.</p> </blockquote> <p>I do believe you, and I <em>want</em> to believe all the admins aswell. The recent disciplinary update does give me a bit more faith, I will say.</p> </div> </div> </div> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112199</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112199</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 23:44:53 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>exactly! this is vague to the point where there is functionally no difference between following the charter and arbitrarily deciding on punishments, which is why i objected to the statement that they're different things.</p> </blockquote> <p>Huh? I'm not sure I understand. How is there no difference? Please refer to the fact that Gee was censured by a vote of all staff, unless my brain fell out. This is <em>non-optional</em>, means Disc can't decide to arbitrarily demote or censure. (Annoyingly, they can decide NOT to offer staff a chance to punish someone, and we need to change that. But, once it's on O5, no one can stop it.)</p> <p>Through this vote, staff have to agree that the conduct is actually unbecoming. Because for staff conduct, Disc can't say &quot;this is Bad Actually even though most staff think it's Fine.&quot;</p> <blockquote> <p>- extremely poor judgement on disc's part but poor judgement made entirely in good faith.</p> </blockquote> <p>Understood &#8212; thank you for clarifying. I agree with this assessment, though no one else has to.</p> <blockquote> <p>you know how i feel about admins being able to just. do stuff :p</p> </blockquote> <p>This power is only supposed to be used to cut through red tape reflecting staff consensus and/or improvement in taff operation that does not enable or consistute a misuse/abuse of power.</p> <p>If this power is used for <em>something else</em>, something has gone wrong, and accountability must be had. (I think this may have occured recently followed by an apology but I'm foggy on this.)</p> <p>Why admins? Admins have the unique if iffy qualification of &quot;we trust this person won't fuck up the site, even if we're wrong.&quot; And admins have the wikidot-induced power to back it up.</p> <p>Admins can't &quot;just do&quot; anything else. They also need to take staff feedback into account even for what they CAN &quot;just do.&quot; Accordingly, see below&#8230;</p> <blockquote> <p>more seriously, i'd be happier with this if staff were notified in advance and could object to this change before it's made if they want to, in which case it would go to the standard discussion and vote. i definitely wouldn't be objecting to the change, but the option should remain available to those who want to.</p> </blockquote> <p>It's still available even if admins do this, because staff can go ahead and just <em>revert that process</em> if a quorum agrees. That said, your preference is noted. Right now I'm going to err on the side of asking admins to agree to not ever do this again and say so on O5. (If this doesn't happen or be taken off the table within 2-4 weeks, please remind me.)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112195</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112195</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 23:29:12 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>That'd be a failing on both of their parts, I believe.</p> </blockquote> <p>Yes, I agree &#8212; if I didn't say so below, I meant to.</p> <p>I am included in this failure, for ignoring it (up until I didn't).</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112194</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112194</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 23:26:51 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Elaborating due to wishing to help this discussion along.</p> <blockquote> <p>The difference is utterly nominal because there are no actual mechanisms for wider stuff to ensure accountability on Disc.</p> </blockquote> <p>This was partially a mistake and partially an accident, and is being actively worked on. Co-signing Dex's statement here.</p> <blockquote> <p>We saw a baseless plagiarism accusation morph into a security breach (that revealed other staff had kept the secret far longer than Cerastes had) and then into a &quot;pattern of behavior&quot;. Despite this two-step shuffle, no one involved in the incident was ever punished, and remains unpunished, because there is no mechanism for wider staff to call out this nonsense</p> </blockquote> <p>There is indeed a mechanism, but it has been largely used to proclaim or imply &#8212; as you do here &#8212; that the reason for punishment is active malice.</p> <p>However, I've been informed &#8212; by you &#8212; that many calls to address this have been ignored. I assume some of these could have included evidence besides instistence that everyone agree that this was clear evidence of malice.</p> <p>Therefore, I'm withholding judgment on this until I see calls (whether because I find them or someone hands them to me).</p> <p>For the rest of the paragraph, see Dex's post.</p> <blockquote> <p>It is profoundly fucked up that Disc and Admins will be the ones voting on whether to censure an administrator who is the captain of Disc.</p> </blockquote> <p>Yes, I agree, and to be honest, I cannot help but wonder if this was somehow intentional, but I promise, it wasn't the intention of any current staff.</p> <p>That said, we will do our best to earn back some of the faith of the community here with our actions in this situation. And, we will address this serious flaw in Charter policy.</p> <blockquote> <p>But I'd like to clarify whether the last bit, about the censure, means that censure proceedings will begin by then or that discussion of whether or not you want to begin censure proceedings will begin by then.</p> </blockquote> <p>Discussion of whether or not Admins (or admins+Disc) want to begin censure proceedings (followed by Disc if it hasn't been done already) has already begun, and has been ongoing for a while.</p> <p>Admin consensus is in favor of beginning censure proceedings, and doing so as fast as humanly possible.</p> <p>Non-Admin Disc members have not yet been consulted, but will be, again as fast as Aismallard (Acting Disc Captain in this situation) can write this all up. I doubt that will change the result, but if so&#8230; well, I can't speak for anyone else but me, but I will try to ensure accountability standards are held here to the very best of my ability.</p> <p>I don't know if a deadline has been set for announcing this result because I'm confused about that. Apologies. Presently the timeline is &quot;as fast as humanly possible.&quot;</p> <p>To be totally clear: the &quot;real&quot; reason is not that admins are unsure about suggesting censure. <em>We are sure.</em> It's not even the Charter, though I do care about that Charter very much and wish us to follow it here.</p> <p>The &quot;real&quot; reason is that Asimallard (with myself helping) has not yet been able to finish a statement, even with help of other admins. (The statement has been fully rewritten twice so far, and I mean <em>from scratch</em> and it's <em>extremely long</em> in draft form.)</p> <p>It is paramount that admins try to avoid messing this up even further. We're not taking our time, but we can't just throw up an O5 thread besides &#8230; well, this one. I personally don't think Dex should've even &quot;rushed&quot; his statement to the extent he did, because he mis-phrased some things, all of which have been thoroughly raked over in this thread. :)</p> <p>Please also note that discussion of censure proceedings is supposed to be informed by this discussion thread. And it will be, even if it's just the same few people posting on it, which right now is the case. <strong>But I hope more people will weigh in, too.</strong> Right now, we really do have an obligation to wait to ensure staff feel comfortable chiming in, at least until we can physically compose more of our statements.</p> <p>(BTW I had to rush this statement, ironically, so please call out + forgive any errors)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112183</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112183</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 23:01:13 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I think I already covered most of this, but:</p> <blockquote> <p>Rather than build a temporary system where you've gotta wait a week for admins and Disc and everyone else who wants in to make a call, just do it and build a permanent system later. Sure, it's not been done before, but neither's any of this.</p> </blockquote> <p>We have a system, detailed below. And, much of this <em>has</em> been done before. I should know: I was a subject.</p> <p>Will respond to the rest in a new post.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112161</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112161</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 22:30:34 +0000</pubDate>
				<wikidot:authorName>Cyvstvi</wikidot:authorName>				<wikidot:authorUserId>6004508</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><strong>Disclaimer:</strong> These are my thoughts and position on Disc and the three major incidents that led to the issues raised in the Joint Statement.</p> <p>At this point, it has become more than evident that Disc was never going to be able to censure Dex nor Mann, whether this comes as a result of internal politics or a failure to perform their due diligence is irrelevant. Regardless of this previous point, censuring both or either of them at this time is not going to resolve any issues held by the community at large.</p> <p>The primary issue with Disc is their sweeping, broad powers and authority, which lacking accountability, transparency, or oversight by the wider staff body and the general community allows it to function as an extrajudicial wing of Staff, operating beyond the accountability expected of Staff members and their teams. It has been shown that Disc, on <a href="http://05command.wikidot.com/forum/t-13868187/non-disc-record-cerastes">two</a> <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2">occasions</a>, has abused its own authority; failing to perform due diligence and stifling disciplinary actions upon its own members.</p> <p>My position on the Cerastes' Incident is rather simple. It should simply never have been allowed to happen. Disc displayed a continuous failure to adequately consider the charges placed before them. This partially emerged from the lack of a second opinion, with the issue of plagiarism being addressed by users unversed in the rigours of plagiarism, and ignoring the most important factor of the Wiki; it is collaborative - users are well within their own right to write around existing concepts and objects.</p> <p>On the topic of Magnus' failure to receive an adequate punishment, Moose raises the following point in the <a href="https://scp-wiki.wikidot.com/forum/t-14230086/discussion-discussion-joint-statement-re:miscommunication-an">main site mirror</a> regarding Magnus' reaction to learning that he would receive a censure:</p> <blockquote> <p>Magnus resigned, demoting himself permanently, which is a much harsher punishment than censure.</p> </blockquote> <p>Frankly, I disagree, this was not a harsher <em>punishment</em>. He <em>voluntarily</em> chose to resign his authority, freeing himself from the burden of punishment. Staff were left unable to account for his actions because he had already stepped away and excused himself of the issue. This, by any stretch of the definition, would be considered a direct abuse of authority.</p> <p>In effect, Magnus' resignation runs into the precise issues that Moose raises further in their comment on the main site mirror, namely:</p> <blockquote> <p>Dex &amp; Mann self-censuring would actually dodge the ability for Disc/Admins to demote them, and would also remove other abilities that staff have (which are under discussion and I or another admin will update ASAP).</p> </blockquote> <p>This is precisely what Magnus actively did by resigning. This is an abuse of position. Now, should Magnus be dragged back before Disc to be held accountable for this? No, he should not. The issue has since passed and I honestly think that Magnus believed his actions were correct and that therefore the case of plagiarism was accurate in his eyes. However, the consequences of the event continue to be raised to this day, which is why I suggest the alternative approach of reform.</p> <blockquote> <p>This is just not correct: Disciplinary team has the power to deliver appropriate disciplinary action as per the outline provided by the Charter and/or Disciplinary policy. It does not have the ability to arbitrarily determine whether or not to deliver action.</p> </blockquote> <p>The argument being made here by users is that Disc has the power and authority to read above and beyond the Charter and/or Disciplinary policy due to its inherent vagueness, thus allowing them to arbitrarily determine whether or not to deliver action. Beyond this, due to the lack of accountability and oversight, it is unknown when, how, or why Disc chooses to respond to an Incident. This was exacerbated by Disc’s continuous delaying of Dex's, Mann's, and at the time, Magnus' censures, something they are perpetuating to this day by choosing to deliberate further on the punishment.</p> <p>Overall, both the Disciplinary Team and Administration have evidenced that their own internal structures are no longer fit for purpose. Unlike the recent reforms and changes made to AHT, Disciplinary has been a failure. Either reform must occur internally amongst yourselves, which can then be brought before the rest of Staff to be voted upon as with all proposals, or there should be external reform, primarily the creation of a body through which wider transparency, accountability, and oversight over Disciplinary and the Administration can be achieved. Until we solve the divide between Administration/Disciplinary and the rest of Staff, these questions will continue to be raised concerning the conduct and operation of Disciplinary.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112136</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112136</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 21:50:13 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Maybe. He's still by a massive margin the most senior active administrator (promoted in 2010 against the next-oldest two 2017 admins) and if someone tells me that doesn't come with a certain degree of respect and deference I straight-up don't believe them.</p> </blockquote> <p>Correct, but calling him Head Admin and giving that as evidence for why Disc/Admins will defer to him is not correct. The specific reason Mann was chosen to have Site Owner back when he was NOT the most senior admin is because since the time he joined administration, he has endeavored to not enable any corruption to the best of his ability, and he has endeavored to be as open to critique as humanly posible.</p> <p>You may not believe this, and that is your right, but I am speaking from working with Mann for many years and observing this particular incident and extensively discussing it with him. And that's worthwhile hearsay evidence to at least some people.</p> <blockquote> <p>Mann did suggest there were grounds for censure — it represents an understand that he, if no one else, thinks he did something worthy of censure.</p> </blockquote> <p>This is correct and was an error from rushing on my part. You are good at catching these in my messages, which I genuinely appreciate. I think I addressed this better in other posts, notably to Lucio. I apologize for this error, and thank you for catching it.</p> <blockquote> <p>Then the admin team doubled and any requests to revisit it, by me and others, were met with silence in staffchat until last week.</p> </blockquote> <p>If it's not too much trouble, may I ask you to provide me these requests? Text + chatroom name would be sufficient. I'll copy this to staff chat also.</p> <blockquote> <p>I also find the idea that we should delay punishment until it is convenient because we're dependent on people's technical staff powers (the inherently admin-only ability to enact emergency bans/revokes) bizarre because it rests on the assumption that we couldn't have done fine with 3-4 (depending on whether Mann was censured) active admins to handle the odd revokes and such for a month. If the argument is that we legitimately couldn't have — we hadn't had more than 6 active admins total from December 2020 until the most recent round of promos. Running with a skeleton crew is not a good enough justification for delaying punishment when you could have added more to the fold at any time. I'm not saying we should've promoted Joe Schmoe just so there were more hands on deck but there were options.</p> </blockquote> <p>I am quoting this simply to say that while I do not feel as harshly as you do, I hear you and largely agree with your point.</p> <p>EDIT: The emergency ban issue would also be solvable by consensus of OS+ staff declaring that these particular censures can allow for emergency bans <strong>only</strong>.</p> <p>However, I get why no one thought of this. I'm suggesting it now at least for future reference.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112082</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112082</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 19:18:26 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>First off, I appreciate your extensive response.</p> <blockquote> <p>In practice, however, Dex did attempt to give (albeit for one vote) Disc team a power he nor the team previously had, going against these rules.</p> </blockquote> <p>Correct.</p> <blockquote> <p>This thread was supposedly passed by the rest of the Disciplinary Team, which would include multiple admins, and would include the two people who you yourself stated &quot;would know best.&quot;</p> </blockquote> <p>Correct. For the record, Mann cited this is as part of why he feels he should be censured. I would like to see other admins acknowledge the (severe) error publicly as well.</p> <blockquote> <p>The charter is notoriously outdated by this point, with multiple sections that staff as a whole are choosing to just ignore since they're either impractical or nonsensical.</p> </blockquote> <p>Ignoring the charter also involves ignoring the aspects of the charter that protect against abuse. This was a severe mistake.</p> <p>If you believe Disc &amp; admins were right to ignore this aspect of the charter, then you're free to say so.</p> <blockquote> <p>When the entire team, along with several admins, all agree on a call that goes against the charter, the rest of staff can only assume this is the new rule.</p> </blockquote> <p>Sure, I get why this has happened. When the call is &quot;policy votes need to be longer than 48 hours,&quot; this is clearly not an abuse of power, and it's the job of admins to validate things like this.</p> <p>However, when the call is &quot;grant Disc special powers by accident&quot;, then validating this is a misuse or abuse of power. In this case, it appears to be clearly unintentional, which is the only reason I'm not angrier. (I've also checked to make sure it was unintentional, to be clear, as I have admin chat access that staff in general do not.)</p> <p>That means it's the job of admins to clarify that misuse of power occured. In making this post, I am carrying out this aspect of my job.</p> <p>I hope this clarifies.</p> <blockquote> <p>Even if they technically couldn't, they did, and none of staff would have a proper leg to stand on if they tried to speak against it.</p> </blockquote> <p>Well, now they do. This is part of admins' attempt to rectify this error, channeled through me.</p> <p>I checked &amp; double-checked all policy positions with administration WELL before posting. Only the choice of timing is my own.</p> <p>RE: Cerastes &#8212; you've told me how it came off, yes. But no one has identified precisely why it came up that way.</p> <blockquote> <p>Considering how much this was discussed, both in and out of staff, this claim feels like a Missing Missing Reason. To explain, a Missing Missing Reason is when someone claims they were never given a reason for X occurrence, often claiming that X came out of the blue to them. However, later on, said individual may actually admit they were given reasons but never really elaborate on them. They'll claim the reasons were &quot;nonsensical,&quot; &quot;lies,&quot; &quot;abusive,&quot; &quot;harassment,&quot; and other adjectives which aim to demean and de-legitimize the original claim without never actually addressing it.</p> </blockquote> <p>It's true that I can only truly speak for what I've seen, and I very explicitly have ignored certain parts of staff discussion (though *not* reports made to admins, AHT, or myself personally).</p> <p>In my case, I do claim certain things came out of the blue for me. I cannot prove this. However, I hope that my efforts are at least a demonstration of good faith.</p> <p>This discussion thread is your chance to make your evidence clear, here on O5, where if I (or anyone) choose to dismiss it, anyone can see what we're doing.</p> <p>Currently the evidence is &quot;things didn't add up&quot; and &quot;vehemency&quot; and &quot;revealing previously unknown information.&quot; I hope you can understand how this, by itself, doesn't make a strong case.</p> <p>I will elaborate more in another post, and try to address specific claims, but I want to give staff a chance to, well, bring those claims. Please also note I need to read other posts in this thread. Other admins may respond as they can. Or anyone who chooses to.</p> <blockquote> <p>In reality - the individual in question cannot or will not actually respond to the reasons they were given. This type of speech aims to not-so-subtly imply that the complainer is irrational and should be ignored, while focusing on how the individual in question took the responses.</p> </blockquote> <p>I hope it's clear to everyone, including you, that I am not doing this. If you feel otherwise, please let me know. I hope I've established that I'm open to hearing such complaints.</p> <blockquote> <p>Your claims that the only reasons Disc/Admins were given were &quot;purely personal attacks, false statements about occurrences, claims of malice with no evidence, or false statements […]&quot; does not help this reading.</p> </blockquote> <p>1. You have omitted my &quot;most of&quot; clarification. If I omitted that, I would be lying. Therefore, your quotation of me does make me a liar, obviously unintentionally, but it's still distressing.</p> <p>2. <strong>I did not and do not make this claim for Disc, but ONLY complaints sent to admins, myself personally, or AHT, plus a few others I sought out myself.</strong> You added this to my claim, which also unintentionally makes me a liar. Again, very distressing.</p> <p>I have recently exercised my right to be granted access to Disc's full records, but please understand that I haven't had time to read them and &#8230; I don't know when I'll be able to, and I can only promise it's at least on my list. Other admins will need to speak for this.</p> <p>Ignoring the &quot;accidentally made Moose a liar&quot; aspect, which I believe to be unintentional &#8212; you have strongly implied that I have spoken in bad faith, which I believe to be intentional. Can you please clarify?</p> <p>Currently, your evidence for my bad faith is &quot;Considering how much this was discussed, both in and out of staff&quot;. However, this thread exists to make this case, so I request that this evidence be provided.</p> <blockquote> <p>Bluntly? Yes. Disc's job is to enact disciplinary measures on both users and staff, and this was a failing on their part to not attempt to address how to deal with this situation. On the other hand, I can't blame most of Disc's members - the accused was their boss, and his coworkers were all defending his choice, who was going to bring that conversation up?</p> </blockquote> <p>I think this is a strong and fair argument, unfortunately for everyone involved, including me, now.</p> <blockquote> <p>If none of the admins were ever aware of how people took these disciplinary threads, I truly wonder how many of them actively participate in the larger community.</p> </blockquote> <p>I do object to this. You must be aware that, as demonstrated by this thread, most of this anger has been publicly led by only a few people, including yourself, and a somewhat higher number of people localized to a specific SCPD channel, which is a significant community pillar but&#8230; well, not participating in SCPD doesn't mean the same as what you just said it means. So did I misunderstand?</p> <p>Please note this is not an attempt to diminish these very real issues which I've seen these &quot;few people&quot; bring up.</p> <p>In fact, the charges I have brought to the attention of admins <em>are more serious and require much more change</em> than anything I've ever seen suggested. I hope this demonstates to the community and to you that I don't wish to diminish or dismiss ANYTHING.</p> <blockquote> <p>Where it all went wrong was the IRC thread.</p> </blockquote> <p>May I request that you clarify this point?</p> <blockquote> <p>I hope so, but I do want you to understand that this claim has been thrown around so repeatedly regarding situations which ended up quietly dying or taking more time than necessary, that I'm finding it honestly hard to believe. Hope you all prove me wrong.</p> </blockquote> <p>I hear you and I acknowledge this. You are right, and that is why I saw it as my job as Reserve Admin to step in. It's also why I've chosen to post much of this information earlier than all admins explicitly approved (though for the record, I have received only approval from administration so far). I intend to continue this approach as much as I can.</p> <p>It is my strong belief (backed by personal discussion) that other administrators are doing the same, and are posting slower than me largely because they don't wish to shut down conversation.</p> <p>EDIT: I have also posted responses on the main site containing more information &amp; answers, notably here: <a href="https://scp-wiki.wikidot.com/forum/t-14230086/discussion-discussion-joint-statement-re:miscommunication-an#post-5112132">https://scp-wiki.wikidot.com/forum/t-14230086/discussion-discussion-joint-statement-re:miscommunication-an#post-5112132</a></p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112018</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112018</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 17:02:26 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Mann isn't the de facto Head Admin, at least not seen that way by Disc or Admins, who make this decision jointly.</p> </blockquote> <p>Maybe. He's still by a massive margin the most senior active administrator (promoted in 2010 against the next-oldest two 2017 admins) and if someone tells me that doesn't come with a certain degree of respect and deference I straight-up don't believe them. He may not have any more or less institutional power than other admins but <em>primus inter pares.</em></p> <blockquote> <p>Additionally, no one suggested that there were any grounds for censure against Mann except himself…. that I'm aware of.</p> </blockquote> <p>I can't say whether this is true, but I don't understand how it's relevant either way. Mann <em>did</em> suggest there were grounds for censure &#8212; it represents an understand that <em>he</em>, if no one else, thinks he did something worthy of censure. What does matter is how unreasonably long the charges were delayed without a clear explanation and justification to staff &#8212; something you acknowledge but is worth repeating.</p> <blockquote> <p>Was this not done yet? I will post a brief version below for visibility.</p> </blockquote> <p>An informal explanation was tendered once or twice to staff &#8212; not to the userbase in general &#8212; that the drought of admins made it inadvisable to censure. Then the admin team doubled and any requests to revisit it, by me and others, were met with silence in staffchat until last week. I also find the idea that we should delay punishment until it is convenient because we're dependent on people's technical staff powers (the inherently admin-only ability to enact emergency bans/revokes) bizarre because it rests on the assumption that we couldn't have done fine with 3-4 (depending on whether Mann was censured) active admins to handle the odd revokes and such for a month. If the argument is that we legitimately couldn't have &#8212; we hadn't had more than 6 active admins total from December 2020 until the most recent round of promos. Running with a skeleton crew is not a good enough justification for delaying punishment when you could have added more to the fold at any time. I'm not saying we should've promoted Joe Schmoe just so there were more hands on deck but there were options.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5112013</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5112013</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 16:58:36 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Alright, let's hit this one by one.</p> <blockquote> <p>The Disciplinary Team cannot ever grant itself power.</p> </blockquote> <p>This is technically correct. As you laid out, Disc does not have the ability to grant itself more power as it wishes, since this would set a dangerous precedent and create a team with unrestricted power. In practice, however, Dex did attempt to give (albeit for one vote) Disc team a power he nor the team previously had, going against these rules. This thread was supposedly passed by the rest of the Disciplinary Team, which would include multiple admins, and would include the two people who you yourself stated &quot;would know best.&quot;</p> <p>&quot;But that goes against the charter, and someone could have pointed that out.&quot; The charter is notoriously outdated by this point, with multiple sections that staff as a whole are choosing to just ignore since they're either impractical or nonsensical. (For example - the charter states policy votes will be up for 24 hours, with 48 hours at the extreme. Votes typically go on for a week nowadays.) When the entire team, along with several admins, all agree on a call that goes against the charter, the rest of staff can only assume this is the new rule.</p> <p>Even if they technically couldn't, they did, and none of staff would have a proper leg to stand on if they tried to speak against it.</p> <p>(This point is brought up a few more times in the comment, so I won't repeat it every time it pops up. Consider this my response to all further mentions of the above.)</p> <blockquote> <p>Dex (as far as I understand) felt like he'd be running away and shirking his responsibilities if he didn't try to fix this rather severe issue as Disc Captain.</p> </blockquote> <p>I really hope Dex clarifies here, because&#8230; Dex, &quot;doing what you promised to do half a year ago&quot; is not running away from responsibility. It would, infact, make staff and the community trust Disc more since they show signs of self-accountability. Prolonging this censure this far is one of the key elements why trust in the disciplinary team is eroded worse than a blacksmith's shop in Atlantis.</p> <blockquote> <p>I'm foggier on whether Extension 3 was made clear to staff.</p> </blockquote> <p>Personally, I am not aware of being told of this. It is possible that it was said in adcap or such other channels, but that is a whole different beast onto its own.</p> <blockquote> <p>Admins were provided no evidence of Disc intentionally trying to get rid of Cerastes, including in this thread (unless I missed it by skimming, in which case I apologize!).</p> </blockquote> <p>&#8230;Hoo, how do I even approach this one. I'll try to write this in the least accusatory tone that I can, despite the fact that my main argument is accusatory in nature.<br /> Due to the mishandling of the Great Seal case, the accusatory tone much of Disc took towards Cerastes, and seemingly unrelated two events which were glued together (the brother and &quot;plagiarism&quot; cases), folk were at an utter loss on how to explain what just occurred. Many things didn't add up - why did Disc make a follow-up thread on a separate issue if the first issue was generally agreed upon to be non-malicious? Why was a topic which was kept secret for so long suddenly unveiled now? Why are most of the admins and disc so vehement in the thread when the majority of non-disc staff seem to be entirely in Cerastes's defense? So many elements that, while individually could be viewed as incompetence or a mishap, began to pile on.<br /> While maybe not necessarily towards Cerastes themselves, the Disc thread seemed hellbent on delivering a &quot;guilty&quot; verdict either out of embarrassment on how the first thread went, or just a need to prove themselves right. At the very least, that's how it was viewed. It was either that, or disc suddenly became shockingly incompetent. None of these two claims can be stated without seeming accusatory, so you can see how those discussions went.</p> <blockquote> <p>This raised a red flag: &quot;We're missing something, and we need to wait to figure out what that is.&quot;</p> </blockquote> <p>Considering how much this was discussed, both in and out of staff, this claim feels like a Missing Missing Reason. To explain, a Missing Missing Reason is when someone claims they were never given a reason for X occurrence, often claiming that X came out of the blue to them. However, later on, said individual may actually admit they were given reasons but never really elaborate on them. They'll claim the reasons were &quot;nonsensical,&quot; &quot;lies,&quot; &quot;abusive,&quot; &quot;harassment,&quot; and other adjectives which aim to demean and de-legitimize the original claim without never actually addressing it.</p> <p>In reality - the individual in question cannot or will not actually respond to the reasons they were given. This type of speech aims to not-so-subtly imply that the complainer is irrational and should be ignored, while focusing on how the individual in question took the responses.</p> <p>Your claims that most of the reasons Admins were given were &quot;purely personal attacks, false statements about occurrences, claims of malice with no evidence, or false statements [&#8230;]&quot; does not help this reading.</p> <blockquote> <p>if admins weren't ready to &quot;bring charges&quot; because the situation was so strange, would it be Right to order Disc do it?</p> </blockquote> <p>Bluntly? Yes. Disc's job is to enact disciplinary measures on both users and staff, and this was a failing on their part to not attempt to address how to deal with this situation. On the other hand, I can't blame most of Disc's members - the accused was their boss, and his coworkers were all defending his choice, who was going to bring <em>that</em> conversation up?</p> <blockquote> <p>This all established grounds for admins to know without a doubt that this situation was more serious <strong>than we had ever identified or been informed.</strong></p> </blockquote> <p>If none of the admins were ever aware of how people took these disciplinary threads, I truly wonder how many of them actively participate in the larger community.</p> <p>You may notice my statements are getting more blunt and aggressive. I'm legitimately trying to be polite here, as much as many don't believe as such, but some of these later statements are&#8230; I don't know how to say it. They're so&#8230; easy to figure out, I suppose, that I'm at a genuine loss as to how to approach them. I either have to assume that none of the admins/disc have been a part of the larger community in the past 11 months (for the claim they were never aware of these issues), which is bad, or that they're feigning ignorance to act like it was someone else's responsibility to tell them, which I think might actually be worse. I honestly don't know what to say, so it just comes off as exasperating and confusion. I'll try to tone it down when possible, but it's honestly incredibly difficult.</p> <blockquote> <p>But the fact is, we cannot avoid unfair charges of plagiarism. We absolutely cannot.</p> </blockquote> <p>That's fair, honestly. The first thread was a mishap, but it was not what granted it the legendary status that it currently holds. If the first thread got an extension to discuss the first accusation, and then likely was shut down as most of staff agreed it was an unfair charge, the thread would have sparked <em>some</em> discussion regarding disc but mostly just fair claims of &quot;this should have been looked into more.&quot; Where it all went wrong was the IRC thread.</p> <blockquote> <p>I can vouch that every day since then, admins have spent many hours working on all parts of this situation.</p> </blockquote> <p>I hope so, but I do want you to understand that this claim has been thrown around so repeatedly regarding situations which ended up quietly dying or taking more time than necessary, that I'm finding it honestly hard to believe. Hope you all prove me wrong.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111993</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111993</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 16:16:23 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>However, Disc team wasn't forced to consider it, and admins didn't force ourselves or Disc to consider it in a timely fashion (see my post below).</p> </blockquote> <p>That'd be a failing on both of their parts, I believe.</p> <p>I have more to say here, but I'll read your other megapost and respond to that.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111833</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111833</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 12:51:23 +0000</pubDate>
				<wikidot:authorName>gee0765</wikidot:authorName>				<wikidot:authorUserId>5376871</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Not when it goes against the plain meaning of the words, as well as the intent of the charter itself (though intent is not needed here.)</p> </blockquote> <p>this is entirely correct, but in the line i was responding to dex wasn't talking about the censure process - it was a clarification of a line used in the initial disc threads, before censure for anyone other than cerastes was even on the table. i'm aware censures have an established process that needs to be followed - the process still doesn't take eleven months.</p> <blockquote> <p>&quot;Conduct unbecoming of staff&quot; IS broad enough to count here, and that's what Disc did.</p> </blockquote> <p>exactly! this is vague to the point where there is functionally no difference between following the charter and arbitrarily deciding on punishments, which is why i objected to the statement that they're different things.</p> <blockquote> <p>I should say, though, that I think the assumption of malicious intent on Disc's part seems uncalled for! Did Disc members say, in so many words, that Disc was trying to justify Cerastes' demotion? Because if not, then this is fairly uncool.</p> </blockquote> <p>i wouldn't say i was assuming malicious intent - extremely poor judgement on disc's part but poor judgement made entirely in good faith. evidence that i consider (and also considered at the time) extremely weak/shaky was used by people who thought it was stronger to call for disciplinary action - this was an extremely bad call imo but still not a malicious one</p> <blockquote> <p>VoNC was clearly designed as a last resort and would be extremely bad policy if it were used for all staff discipline. I strongly recommend against this.</p> </blockquote> <p>this is a reasonable point, im definitely open to hearing other ways that discipline within staff could work without belonging to a specific team</p> <blockquote> <p>I think now we should be requesting it from the community instead.</p> </blockquote> <p>this would be very cool. if delays are really necessary it shouldn't be difficult to convince the community that the action should wait a few months.</p> <blockquote> <p>Admins have the power to remove this ability from Disc immediately with no vote needed</p> </blockquote> <p>you know how i feel about admins being able to just. do stuff :p<br /> more seriously, i'd be happier with this if staff were notified in advance and could object to this change before it's made if they want to, in which case it would go to the standard discussion and vote. i definitely wouldn't be objecting to the change, but the option should remain available to those who want to. i see you suggesting this in the next paragraph, so i can say i definitely agree there</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111675</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111675</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 09:08:45 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>In this case, Mann and Dex (being two users who are peers) could have brought forward their own case to Disciplinary</p> </blockquote> <p>This is correct, yes, and they indeed did so in a valid manner. See my post below for a not-so-brief explanation on why &quot;bring these charges to light on O5&quot; was delayed.</p> <p>But, your specific quote was:</p> <blockquote> <p>Additionally, the charter says nothing regarding the self-application of censures.</p> </blockquote> <p>The Charter only allows Mann &amp; Dex to propose their own censure to others, not apply it to themselves.</p> <blockquote> <p>I meant that they could have easily begun this process whenever they wanted.</p> </blockquote> <p>Yes, certainly, and they did so.</p> <p>However, Disc team wasn't forced to consider it, and admins didn't force ourselves or Disc to consider it in a timely fashion (see my post below).</p> <p>Their alternative would've been to executive-summary a censure on themselves, which technically they do indeed have the power to do. Mann did not do so because of his own time limitation. Dex is explained elsewhere, in my post and in his own, I think.</p> <blockquote> <p>In that case, wouldn’t Mann and Dex “deciding” to take a Censure apply aswell? Even if someone else enacts it by this point, it seems to be very much their decision, especially considering how it’s been delayed for nearly 11 months.</p> </blockquote> <p>You can't decide to take a Censure, nor the time length, so none of what would've counted. Peers must vote on whether they should be censured, with the option of saying they actually deserve no punishment or various forms of demotion instead. &quot;Deciding to take a censure&quot; removes these options from their peers.</p> <p>For more, see my other posts. I can try to answer more questions also (though please forgive me if it's not in a timely fashion).</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111660</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111660</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 07:46:18 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Also, it wouldn't actually count as disciplinary action, and upon the admin's return, they could still be subject, fairly, to yet another Disciplinary Vote thread.</p> </blockquote> <p>I’ll clarify what I meant: The “demotions” section of the charter states that in the event that a staff member acts unbecomingly of their position, a staffer may discuss it with a peer of the member, and if both agree they may bring it forward to Disciplinary. Once Disciplinary discusses the case, it is “the duty of the head of disciplinary (in the case of non-administrators) or an administrator on the disciplinary team (in the case of administrators) to bring these charges to light on O5.” In this case, Mann and Dex (being two users who are peers) could have brought forward their own case to Disciplinary, which could have then been forwarded to 05 by either Dex himself (being both an admin and head of disc) or any of the other admins there.</p> <p>I did not mean that they should have executive-summaried a censure on themselves, I meant that they could have easily begun this process whenever they wanted. Hope that clears that up.</p> <blockquote> <p>Sure, an admin could self-censure, but it would be the exact same as temporarily stepping down.</p> </blockquote> <p>In that case, wouldn’t Mann and Dex “deciding” to take a Censure apply aswell? Even if someone else enacts it by this point, it seems to be very much their decision, especially considering how it’s been delayed for nearly 11 months.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111658</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111658</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 07:38:34 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>It's pretty implicit that nobody is going to start censure proceedings against the <em>de facto</em> head admin and <em>de jure</em> Disciplinary Captain unless he acknowledges that he's okay with it.</p> </blockquote> <p>Mann isn't the de facto Head Admin, at least not seen that way by Disc or Admins, who make this decision jointly.</p> <p>Additionally, no one suggested that there <em>were</em> any grounds for censure against Mann <em>except</em> himself&#8230;. that I'm aware of. (Please feel free to correct me.)</p> <blockquote> <p>now people want an explanation for why this censure never moved forward for the better part of a year despite you and Mann both agreeing to it (something that should not have had to happen). They deserve one.</p> </blockquote> <p>Was this not done yet? I will post a brief version below for visibility.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111654</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111654</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 07:22:15 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Alright, going to go ahead and try to answer some policy questions that I didn't elsewhere. I can't easily speak to all of this, so apologies for skipping some things.</p> <blockquote> <p>there are many different ways to interpret one piece of policy.</p> </blockquote> <p>Not when it goes against the plain meaning of the words, as well as the intent of the charter itself (though intent is not needed here.)</p> <p>In this case, the Charter is clear, albeit annoying to read:</p> <ul> <li>Disc Team &amp; Admins (combined) have broad unilateral power to determine <strong>not</strong> to enact Demotion or Censure against a staff member. This is because they can choose to simply not offer the option to staff. <ul> <li>Is that reasonable? I don't actually think so, but it's clear in the Charter, and I can confirm it was the intent. (See rest of my post for my suggested alternative.)</li> </ul> </li> <li>Disc Team can't demote or censure by itself (see my other posts). This was by design, and I say this as one of the designers. They were intentionally not given any mechanism with which to do so.</li> </ul> <blockquote> <p>we had a lot of disc members presumably using disciplinary policy to unsuccessfully attempt to justify cerastes' demotion</p> </blockquote> <p>&quot;Conduct unbecoming of staff&quot; IS broad enough to count here, and that's what Disc did.</p> <p>I should say that I could not disagree more with the grounds for which Cerastes was up for demotion. Disc's <em>job</em> was to see that it was blown out of proportion, to quote the charter &#8212; and Disc didn't.</p> <p>I should say, though, that I think the assumption of malicious intent on Disc's part seems uncalled for! Did Disc members say, in so many words, that Disc was trying to justify Cerastes' demotion? Because if not, then this is fairly uncool.</p> <blockquote> <p>fold all staff discipline into the existing vote of no confidence proposal - we already have a mechanism which doesn't rely on specific individuals there.</p> </blockquote> <p>VoNC was clearly designed as a last resort and would be extremely bad policy if it were used for all staff discipline. I strongly recommend against this.</p> <p>However, I agree that Disc &amp; Admins should no longer have the ability to determine to delay censure/demotion, as staff has changed enough that this is harmful now. I feel like at this point it's very hard for us to determine grounds for delay, whereas it used to be 1000% easier. I think now we should be requesting it from the community instead.</p> <p>Admins have the power to remove this ability from Disc immediately with no vote needed, and I'm going to recommend that this is done within the next couple weeks. (Disc had this power at its inception via the Charter, but admins may remove it at any time, <em>because</em> it is not explicitly listed within the Charter.)</p> <p>(I also think admins may also have the power to just&#8230; make ourselves a rule that we MUST to ask staff for permission to do this, but I'd need more time to check. Either way, I'm going to recommend that admins just DO this from now on, period.)</p> <p>(Also, a staff vote may also <strong>require</strong> admins to ask permission to delay a censure/demotion decision or vote that has been requested of them, with a modification to the Charter accordingly.)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111646</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111646</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 07:06:22 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I see a lot of misconceptions in this thread! Here we go.</p> <p>Please note I literally haven't had time to do more than skim these threads. I'm trying to help this process along because I know it's important. Please call out my errors. This goes triple for admins reading this.</p> <h2><span>Disc Team Powers</span></h2> <p>Here is something very important to understand about the Disciplinary Team, which is a point that has been somewhat lost to time. And then I'll explain why it doesn't matter.</p> <p><strong>The Disciplinary Team cannot ever grant itself power.</strong></p> <p>This is actually true for all teams, but it's most extreme for Disciplinary. To understand this, let's look at how Staff Teams gain power: <a href="http://05command.wikidot.com/staff-structure">http://05command.wikidot.com/staff-structure</a></p> <blockquote> <p>Capabilities and permissions will be added or removed if:</p> <ul> <li>The team requests a new permission or ability,</li> <li>The team is determined to have abused a permission, or</li> <li>A situation arises that requires attention, and administration determines that this team is best suited for dealing with the situation.</li> </ul> </blockquote> <p>Who can do this? When Troy and I wrote that page, &quot;everybody knew&quot; that it was the following:<br /> 1. The administrators who already possess the power to be granted or removed. This is a use of administrative power.<br /> 2. The will of all site staff, as laid out in the Charter. This is a use of staff power.</p> <p><strong>There are no other options.</strong></p> <p>With that in mind&#8230;</p> <ul> <li>The Charter grants all non-Reserve administrators the power to vote to ban (except , and all members of the Disciplinary Team the power to vote to ban in place of an administrator if no administrator is present.</li> <li>Since the power to ban rests with all non-Reserve administrators, then non-Reserve admins must grant any new uses of the power to ban, and must be accountable to staff for it.</li> </ul> <p>Here are a couple of the powers granted to Disciplinary, since its inception.</p> <p>1. Due to a recurring lack of administrators, administrators as a group long ago informally granted members of the Disciplinary Team the power to vote to ban even when sufficient administrators are present.<br /> * Accountability: This was requested by staff consensus in IRC staff chat. To my recollection, the decision at the time was perceived as &quot;the only possible right move&quot; by every staff member at the time.<br /> 2. Disc was also given the power to hide information key to resolving a ban vote. Information must be made available to OS+ upon request, and must be kept private amongst OS+ staff unless determined by Disc or Admins. Admins &amp; Disc must still take staff feedback into account for bans.<br /> * Accountability: This was requested by staff consensus in IRC staff chat. To my recollection, this decision was at best mildly controversial because it meant removing information from O5.</p> <p>Alright. So all that's done. Now&#8230; here's why all of the above doesn't matter, regarding censure.</p> <p>To the very best of my knowledge, and to the best of Dex's and Mann's knowledge (the people who would know best), as well as other admins I consulted with:</p> <ul> <li><strong>Admins, as a group, do not have the power to give themselves or the Disciplinary Team power to enact Demotion or Censure.</strong> Admins, and Disc, must follow the procedure in the Charter. BOTH admins and Disc must determine the discipline of an admin.</li> <li><strong>Further, admins, as a group, did not try to give anyone this power.</strong></li> <li><strong>Only the will of all staff, as voted on per the Charter, can grant anyone additional power to enact Demotion or Censure.</strong></li> </ul> <p>Summary: Disc can't censure anybody on its own under any circumstance unless it's an admin, and even then, they have to allow all other non-Reserve admins to vote on it too (and must follow the Charter procedure to do so).</p> <h2><span>Why the Delay?</span></h2> <p>It was the intent of administration to post this, but I think it may have gotten lost. Due to staff request, I'm going to explain. Ordinarily I would not have the power to do this, but it is understood that admins need to be accountable to the community, and therefore I hope my fellow admins will forgive me for this. I will try to rectify any errors that may occur.</p> <p>Admins granted three extensions to Disc (&amp; themselves) to make a censure decision.</p> <p>1: Formal extension granted due to the Harmony situation. Staff generally seem to agree this was merited.</p> <p>2: Formal extension granted until more admins can be promoted &amp; trained. I beleive this was also announced.</p> <p>3: <em>Informal</em> extension granted because admins were overloaded, and Disc Team felt they had lost the confidence of staff members to do anything <em>except</em> censure Dex and maybe Mann. At that point, Dex (as far as I understand) felt like he'd be running away and shirking his responsibilities if he didn't try to fix this rather severe issue as Disc Captain. (Dex may clarify this point.)</p> <p>(And Mann was asked by admins to hold off on grounds of &quot;it's unclear we can ethically even put you up for censure even though we probably will if anyone can bring a clear charge.)</p> <p>If Disc delays censuring, that meant admins had to either pick up the process ourselves, or wait. Admins elected to wait (informally granting Extension 3 here), and begin to investigate the situation due to intense confusion around it. Full disclosure: I helped with this process.</p> <p>I'm foggier on whether Extension 3 was made clear to staff. Admins will need to clarify how/if they approached telling staff in general.</p> <p>The sheer amount of time we took was very specifically because of the amount of confusion and limited time, with only admins to drive the investigation. (I've addressed admin overload being a huge problem, and it contributed here. I am preparing proposed solutions.)</p> <p>Admins received or read many reports on Dex, but most of them were purely personal attacks, false statements about occurences, claims of malice with no evidence, or false statements about how policy and/or Disc work.</p> <p>Additionally, initial investigation results pointed towards &quot;Dex did not do anything that would be unacceptable from any other staff member.&quot; Many people were led to believe that Cerastes engaged in plagiarism. Many people also were extremely concerned about the &quot;brother&quot; incident, even though it was hard to assess.</p> <p>Admins were provided no evidence of Disc intentionally <em>trying</em> to get rid of Cerastes, including in this thread (unless I missed it by skimming, in which case I apologize!).</p> <p>Additionally, the amount of abusive behavior directed at Dex had gotten fairly shocking. This raised a red flag: &quot;We're missing something, and we need to wait to figure out what that is.&quot;</p> <p>Another theme was holding Dex responsible for the censure delays. Dex bears equal responsibility for the third extension only (not 1 or 2), which might be grounds enough for censure itself.</p> <p>This <strong>is</strong> grounds for a Disc thread with a charge of power abuse, even unintentional. However, admins knew the reasoning, though we didn't tell staff (and maybe should have! I think that was a fuck-up), and&#8230; well.. if admins weren't ready to &quot;bring charges&quot; because the situation was so strange, would it be Right to order Disc do it?</p> <p>(This is why I feel in the future, as I said, admins should ask staff for permission for extensions, or some other mechanism be created.)</p> <p>Then the investigation, after months, <em>finally</em> bore fruit. Admins discovered the following:</p> <ul> <li>Admins discovered the policy error that Dex made, and the apparent severe consequences of it: people appear to believe that Disc <em>can and will</em> do literally anything. Hell, people in this thread are claiming Disc has this power! I don't know if this was caused by the Cerastes thread or not, but&#8230; well, see next point.</li> <li>Reports have been unanimous: the Cerastes thread is used as evidence across the community to demonstrate that Disc can and will do literally anything. The reasons why seemed&#8230; strange, at best, and malicious at worse. But suddenly many of the reports became starkly clear once we read the thread and compared it to the Charter and questioned all our assumptions as carefully as possible. We were trying to figure out how things could have gone horribly wrong and&#8230; we did.</li> <li>Other factors which will be discussed later, but the above two on their own were more than enough, and resulted (alone) in the end of the extensions permanently.</li> </ul> <p>This all established grounds for admins to know without a doubt that this situation was more serious than we had ever identified or been informed.</p> <p>On personal note, here: &quot;Unfair charges of plagiarism&quot; may sound just as bad as &quot;claiming Disc has the power to unilaterally censure or demote.&quot; But the fact is, we cannot avoid unfair charges of plagiarism. We absolutely cannot. I learned this the hard way. Writers seem to have their brains absolutely fucking fall out here. If you disagree, you are either too inexperienced in these communities or selling something. (I will only fault you for the latter.)</p> <p>I still think that alone <em>could</em> be grounds for censure, and definitely community damage! However, admins have still received zero evidence of a hit job on Cerastes, just demanding that a specific interpretation of Disc's actions be made.</p> <p>&#8230;But, &quot;claiming Disc has the power to unilaterally censure or demote&quot;&#8230; well, the reason Disc DOESN'T have that power is because Troy and I and other staff at the time denied this power to Disc repeatedly, and then enshrined it in the Charter.</p> <p>Most visibly, we did this Eskobar was Disc Captain and requested inquisitorial power <em>using those words,</em> because at the time Disc was popular and people wanted to use Disc as a club to get rid of people they were mad at. (Sound familiar? It should.)</p> <p>We specifically feared that it would essentially make Disc &quot;an Inquistion&quot; and make people have to live in fear of Disc. Which appears to be exactly what has happened! In combination with other things, as well, but as I said, this by itself would be enough.</p> <p>With this knowledge, admins ended the extension effective immediately and created an internal timeline to address this.</p> <p>We now consider it an emergency situation and it has been our top priority since the Akimoto situation was addressed, and was second priority before then. I can vouch that every day since then, admins have spent many hours working on all parts of this situation.</p> <p>I wish to apologize again that this hadn't been explained, and to clarify that it would have been explained ASAP in the next few days if I hadn't done so. More information is also forthcoming ASAP.</p> <p>EDIT: To be clear, I think it was a mistake for admins to take as long as we did without specifically asking permission from staff. Notably, extension 3 at least should've been granted permission by staff, and was a mistake in handling by admins, including myself. And extensions 1 and 2 probably would've been approved, so, um&#8230; I feel admins should just ask in the future, period. So many issues could have been solved this way, meaning it's the responsibility of admins to do better here.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5111622</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5111622</link>
				<description></description>
				<pubDate>Tue, 19 Oct 2021 06:26:18 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Was skimming through this thread and happened to notice:</p> <blockquote> <p>Additionally, the charter says nothing regarding the self-application of censures.</p> </blockquote> <p>Censure is a form of temporary demotion that can be enacted only as a consequence of either a Disciplinary Vote thread created per Charter standards, or a Vote of No Confidence thread.</p> <p>Sure, an admin could self-censure, but it would be the exact same as temporarily stepping down. Also, it wouldn't actually count as disciplinary action, and upon the admin's return, they could still be subject, <em>fairly</em>, to yet another Disciplinary Vote thread.</p> <p>Please note that Dexanote's statement about lacking this power was prompted by myself in my role as Reserve Admin, advising on policy interpretation. <em>And</em> as one of the staff who co-created this policy, I can confirm this was the intent.</p> <p>Staff, as always, retain the power to change this. However, I urge y'all not to: people should not have the power to enact disciplinary action on themselves. That leads to all kinds of ethical issues.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110933</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110933</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 08:18:54 +0000</pubDate>
				<wikidot:authorName>gee0765</wikidot:authorName>				<wikidot:authorUserId>5376871</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Disciplinary team has the power to deliver appropriate disciplinary action as per the outline provided by the Charter and/or Disciplinary policy. It does not have the ability to arbitrarily determine whether or not to deliver action.</p> </blockquote> <p>there are many different ways to interpret one piece of policy. we had a lot of disc members presumably using disciplinary policy to unsuccessfully attempt to justify cerastes' demotion - you can use vague and not particularly well-defined policies to justify anything if you want to. so no, there isn't a significant difference between these two things.</p> <blockquote> <p>An important point is that staff members do not have the ability to call for or enact censure on themselves</p> </blockquote> <p>even if we look past the fact that this is partially untrue (nothing in the charter or anywhere i can find says that people can't suggest their own censure to the rest of disc. yes, disc would have to make the final decision but you (or anyone, really) could have suggested it to the team at any point), it doesn't even come close to justifying an <em>eleven month</em> delay. maybe a week or two while people decided how was best to handle this, not almost a whole year.</p> <p>really the lesson here is (as i previously said in staffchat) that disc shouldn't be handling the censure and discipline of staff members. they dropped the ball with cerastes and spent the last eleven months failing to pick it up when they delayed this censure this much. fold all staff discipline into the existing vote of no confidence proposal - we already have a mechanism which doesn't rely on specific individuals there. censures are good at sending a message but they don't address the structural issues which are causing the problems.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110870</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110870</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 05:58:49 +0000</pubDate>
				<wikidot:authorName>OptimisticLucio</wikidot:authorName>				<wikidot:authorUserId>3199573</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>The way this is phrased suggests that Disciplinary team would have the sole power to determine a disciplinary outcome.</p> </blockquote> <p>It doesn't quite <em>suggest</em> it as much as it flat out states that disc have &quot;the final say&quot; in big bold letters. Semantics, I know, but this line felt like it was misrepresenting the statement.</p> <blockquote> <p>My intent was to communicate to a subgroup of readers that Disc team wasn’t being influenced by other actors</p> </blockquote> <p>I legitimately fail to see how second disc thread's phrasing conveys this sentiment. All it says is that Disc will have the final executive decision, and that OS+ may add their opinions. There is nothing there about influence.</p> <blockquote> <p>An important point is that staff members do not have the ability to call for or enact censure on themselves, but this is a matter which (per the Charter) should be decided by Administrators and/or the Disciplinary Team.</p> </blockquote> <p>You are both an admin and the captain of disciplinary. As said by some in the onsite thread, this doesn't seem like you're legitimately trying to adhere to the spirit of the Charter, and moreso trying to avoid consequence by pointing at what the Charter technically states. <strong>Additionally, the charter says nothing regarding the self-application of censures.</strong></p> <p>I have more to comment on what was said elsewhere in this thread, but Rounder and Limeyy already said all I have to say and more. I'll only comment on one more aspect which was said exclusively in this thread:</p> <blockquote> <p>At arm's length, it's an apology for a slip of a line being written during a time of perceived duress, which was intended to cover bases and ended up being totally unnecessary.</p> </blockquote> <p>This is not an apology. This statement does not contain an admittance of fault, a promise to do better, and at the most basic level <em>it does not include the word &quot;sorry.&quot;</em> This is just a statement that explains your thought processes and decisionmaking during the event; none of this can be amounted to an apology.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110714</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110714</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 01:53:49 +0000</pubDate>
				<wikidot:authorName>Limeyy</wikidot:authorName>				<wikidot:authorUserId>3533748</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This response really doesn't sit well with me.</p> <blockquote> <p>It really wasn't attached to the previous discussion, though I fully acknowledge how it looks like that.</p> </blockquote> <p>Many times, both in your original post and in the discussion forthcoming, are <a href="http://05command.wikidot.com/forum/t-13868187/disciplinary-ceraste" target="_blank">Great Seal Incident</a> and <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2|">SSSC Incident</a> (cerastes 1 and 2 respectively because using numbers always confuses me lol) used as an example as a pattern of behavior to paint them as an untrustworthy or otherwise a negative value member of staff. While the second incident happening so soon may have been coincidental, the inflammatory tone in the SSSC incident thread, using the great seal incident as a launchpad for character judgements. I highly doubt a thread about a respected Moderator's older brother joining staffchat with a bug, refusing to leave, and then leaving after 12 hours would have had a disc thread a percent as aggressive of an opening as this - there was an agenda, likely subconscious but an agenda nonetheless at play in the opening of Cerastes 2. Even if the exact cause may not have been fabricated, these threads were clearly connected in content and expectations, and a brief read through the first pages of the SSSC incident's thread (linked above) shows that's clearly the case.</p> <blockquote> <p>At arm's length, it's an apology for a slip of a line being written during a time of perceived duress, which was intended to cover bases and ended up being totally unnecessary.</p> </blockquote> <p>This was not an apology. There was no apology in the thread here. A clarification of what you meant and didn't convey? Sure, but there still has not been a public apology *to the community* for Disc's or any other party's part in the November 2020 incident. And that's what it needs to be. This isn't about any one individual or one (read: two) incidents, this has become a community issue and a systemic issue. <a href="http://05command.wikidot.com/forum/t-14129317/statement-on-events-of-november-2020">An earlier statement</a> promised a public apology at some point connected to the censure, and apologized to the members of disc who have had to deal with the aggression as a result of the November 2020 incidents, but we're still yet to see Disc or anybody else publicly buckle down and say 'hey, we fucked up. Sorry 'bout that', and as such trying to frame anything that's come out as an apology rather than an attempted justification of Disc's actions feels hollow, especially when we haven't even got a public surface level 'sorry' yet, especially when you're out here admitting (rightly so) that damage *has* been done.</p> <blockquote> <p>The censure thing… well, the point is also that we (Mann and I) can't agree on a censure. Like, that's not our choice, that's the decision of Administrators and/or Disciplinary Team, likely both in this case.</p> </blockquote> <p>This reads to me that rules to allow your censures don't exist. Cool. Mann has the power to delete the site and you're the captain of the most powerful team on said not-yet-deleted site. There's a time for building new rules and precedent and whatever, but this isn't it. You fucked up, you're clearly willing to take this censure as much as I disagree with the idea that you *can* take censures like that so just like&#8230; do. Rather than build a temporary system where you've gotta wait a week for admins and Disc and everyone else who wants in to make a call, just do it and build a permanent system later. Sure, it's not been done before, but neither's any of this. The obvious answer is to take the path of least resistance instead of adding weeks of bureaucracy and newly invented rules to a process that's already 11 month's overdue. I know it's well-intentioned, but this could easily be read like stalling.</p> <p>EDIT: Oh Rounder also replied to this one. Oops.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110708</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110708</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 01:45:30 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>It really wasn't attached to the previous discussion</p> </blockquote> <p>It absolutely was, though. Your words, directly from Cerastes [2]:</p> <div class="blockquote"> <blockquote> <p>&quot;The following event, however, is <strong>the core issue from where this conversation should have been focused on from the beginning.</strong>&quot;</p> </blockquote> <blockquote> <p>[&#8230;] will acknowledge here that this breach <strong>should have been included much more prominently in the opening thread.</strong></p> </blockquote> </div> <br /> You can't say the second thread wasn't attached to the first when you explicitly note in the second that it should have been included with the first and coupled into one discussion. <blockquote> <p>I soon dropped it as it came to that most staff didn't feel the same.</p> </blockquote> <p>The thread continued for the full 72 hours demanded by the Charter - what do you mean when you say you dropped it?</p> <blockquote> <p>At arm's length, it's an apology for a slip of a line being written during a time of perceived duress [&#8230;]</p> </blockquote> <p>It's not really an apology if you never say sorry or like, &quot;I apologize&quot;. Apology implies a degree of voiced regret -this is just an acknowledgement of missteps. <a href="http://05command.wikidot.com/forum/t-13875439/disciplinary-cerastes-2#post-4829801">This</a> <em>is</em> an apology, as is the one you later voiced to members of Disc who were uninvolved. The post this thread is about, though, is not. All it would need is &quot;I apologize&quot; to turn it into one.</p> <blockquote> <p>The censure thing… well, the point is also that we (Mann and I) can't agree on a censure. Like, that's not our choice, that's the decision of Administrators and/or Disciplinary Team, likely both in this case.</p> </blockquote> <p>You misunderstand. It's pretty implicit that nobody is going to start censure proceedings against the <em>de facto</em> head admin and <em>de jure</em> Disciplinary Captain unless he acknowledges that he's okay with it. Which you did, with Mann (and Magnus, though he resigned before anything could actually happen), which is very good! Shows a willingness to face the music &#8212; but this extension is typically not granted to censures candidates. Also, it's been 9-10 months since January. The situation has progressed - now people want an explanation for why this censure never moved forward for the better part of a year despite you and Mann both agreeing to it (something that should not have had to happen). They deserve one.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110697</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110697</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 00:54:37 +0000</pubDate>
				<wikidot:authorName>Dexanote</wikidot:authorName>				<wikidot:authorUserId>481882</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'll touch on the latter half, as the first part is an upcoming discussion (this or next week). Please have patience.</p> <p>As per the Charter, I believe the discussion will be the <em>second</em> - that is, &quot;the initial discussion will be whether admins and Disc believe it appropriate to enact censure on the admin who is the captain of Disc&quot;. If I may be honest, <strong>I'm not happy about that</strong>. But I think I have faith that they'll do the right thing.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110692</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110692</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 00:38:06 +0000</pubDate>
				<wikidot:authorName>Dexanote</wikidot:authorName>				<wikidot:authorUserId>481882</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I think there's some misunderstandings here, though I think I see where you're coming from.</p> <p>First to touch on the middling part - The second thread I made, regarding the 'leak' on staff discord, e.g. another person coming in and me and a lot of other staff having not known about it, was intended as a discussion to see if people saw it as egregious and frustrating as I did. I soon dropped it as it came to that most staff didn't feel the same. It really wasn't attached to the previous discussion, though I fully acknowledge how it <em>looks</em> like that. This actually goes arm in arm with the first half of the statement I made today, about the misspoken line.</p> <p>Now, the fact that the first half of todays statement doesn't say much isn't really untrue. At arm's length, it's an apology for a slip of a line being written during a time of perceived duress, which was intended to cover bases and ended up being totally unnecessary. But the implications of the line were an egregious slip on my part, and a misrepresentation of how Disciplinary team's systems actually work. It's implications contributed to helping set the same perception I touched on immediately above, and that you've related. Damage is done, and it needed to be addressed to here.</p> <p>The censure thing&#8230; well, the point is also that we (Mann and I) can't agree on a censure. Like, that's not our choice, that's the decision of Administrators and/or Disciplinary Team, likely both in this case. We were preemptive with the idea of it, as we intended it to be a signal of actual penance and showing we know we fucked up. But in the spirit of keeping people accountable, you can't just punish yourself. There needs to be a public recognition of things done wrong.</p> <p>I'm glad we agree it's good that it's moving forward now though.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110688</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110688</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 00:30:00 +0000</pubDate>
				<wikidot:authorName>Rounderhouse</wikidot:authorName>				<wikidot:authorUserId>4187885</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Echoing what Limeyy said. The difference is utterly nominal because there are no actual mechanisms for wider stuff to ensure accountability on Disc. We saw a baseless plagiarism accusation morph into a security breach (that revealed other staff had kept the secret far longer than Cerastes had) and then into a &quot;pattern of behavior&quot;. Despite this two-step shuffle, no one involved in the incident was ever punished, and remains unpunished, because there is no mechanism for wider staff to call out this nonsense - and there will never be one until Disciplinary loses the cladding of sensitivity and secrecy which it never originally had and evolved somewhere along the line.</p> <p>It is profoundly fucked up that Disc and Admins will be the ones voting on whether to censure an administrator who is the captain of Disc. But I'd like to clarify whether the last bit, about the censure, means that censure proceedings will begin by then or that discussion of whether or not you want to begin censure proceedings will begin by then. One indicates the problem is being taken seriously and steps are being made to amend it (though admittedly a year late) and one signifies that people are yet to even agree on whether this is a step that should be taken - though I would hope that isn't in argument anymore.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110678</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110678</link>
				<description></description>
				<pubDate>Mon, 18 Oct 2021 00:06:42 +0000</pubDate>
				<wikidot:authorName>Limeyy</wikidot:authorName>				<wikidot:authorUserId>3533748</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>This is just not correct: Disciplinary team has the power to deliver appropriate disciplinary action as per the outline provided by the Charter and/or Disciplinary policy. It does not have the ability to arbitrarily determine whether or not to deliver action.</p> </blockquote> <p>This really feels like an incredibly similar thing to me. Sure, Disc can't ban people for being annoying, but saying as such in a statement about the events of November 2020 is irrelevant at best and actively detrimental to the point at worst. Disc can't ban people for being a pain, but they can hop on a plaigirism call and, when that falls through, find another excuse to back up a decision they have already made. I can hardly blame people for not being filled with confidence at the idea that disc have to ban you for *something* after seeing that, and I really don't feel this first half of the statement says much at all at best and the fact there feels to be a need to clarify it really just makes me feel weird at worst.</p> <p>Going ahead with the censure is cool though. It's still a little fucked that y'all get to agree to go on censure when nobody else on staff has a choice, but the fact that it's happening at all is a win.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110665</guid>
				<title>Re: [Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110665</link>
				<description></description>
				<pubDate>Sun, 17 Oct 2021 23:32:05 +0000</pubDate>
				<wikidot:authorName>Dexanote</wikidot:authorName>				<wikidot:authorUserId>481882</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><a href="https://scp-wiki.wikidot.com/forum/t-14230086/discussion-discussion-joint-statement-re:miscommunication-an">Site mirror here!</a></p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-14230078#post-5110658</guid>
				<title>[Discussion] Joint Statement re: Miscommunication and On Censure</title>
				<link>http://05command.wikidot.com/forum/t-14230078/discussion-joint-statement-re:miscommunication-and-on-censur#post-5110658</link>
				<description></description>
				<pubDate>Sun, 17 Oct 2021 23:24:14 +0000</pubDate>
				<wikidot:authorName>Dexanote</wikidot:authorName>				<wikidot:authorUserId>481882</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This is a discussion for <a href="http://05command.wikidot.com/forum/t-14230046/joint-statements-regarding-miscommunication-and-on-censure">this</a> thread, and the contents within.</p> <p>The intention behind this thread is to clarify any questions people have with the contents of the statement. Please have the other thread open as well while reading or posting to this one. Thank you.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>