<?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>Backseat Modding in 17</title>
		<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17</link>
		<description>Posts in the discussion thread &quot;Backseat Modding in 17&quot; - It&#039;s a problem.</description>
				<copyright></copyright>
		<lastBuildDate>Thu, 16 Apr 2026 04:47:55 +0000</lastBuildDate>
		
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561590</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561590</link>
				<description></description>
				<pubDate>Mon, 31 Jul 2017 06:37:04 +0000</pubDate>
				<wikidot:authorName>ChaoSera</wikidot:authorName>				<wikidot:authorUserId>2227264</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Echoing the earlier sentiments, I don't think either a new channel or muting 17 during appeals is necessary. We already have policies in place that let us deal with repeated backseat modding, the difference is, we have to actually /use/ these policies. I honestly don't remember the last time someone was kicked for this and a lot of times they were just told off - which should be the first step, obviously, but I can think of a couple repeat offenders who are, IMO, way past that point. So I think the issue here is less that we need a policy change but rather that we as ops need to actually act on these issues, which we have not done as much as we can and should.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561484</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561484</link>
				<description></description>
				<pubDate>Mon, 31 Jul 2017 02:51:16 +0000</pubDate>
				<wikidot:authorName>AdminBright</wikidot:authorName>				<wikidot:authorUserId>224440</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Yeh,agreeing with these thoughts.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561400</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561400</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 21:40:29 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>We do. This entire thread is created to solve a non-existent problem.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561399</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561399</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 21:38:22 +0000</pubDate>
				<wikidot:authorName>MrAnakinSpecter</wikidot:authorName>				<wikidot:authorUserId>1477805</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>why we don't just kick and ban people for repeated disruptive backseat modding the same as anything else</p> </blockquote> <p>We <em>do</em>, don't we?</p> <p>I don't really see what the issue is, here. If it ain't broke, don't fix it.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561392</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561392</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 21:28:14 +0000</pubDate>
				<wikidot:authorName>Doctor Cimmerian</wikidot:authorName>				<wikidot:authorUserId>1414765</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>On some days, yeah. On most days no. I'd imagine our peaks to become more common as time progresses though.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561375</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561375</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 20:35:58 +0000</pubDate>
				<wikidot:authorName>SoullessSingularity</wikidot:authorName>				<wikidot:authorUserId>637830</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I am confused, heavily confused, why we don't just kick and ban people for repeated disruptive backseat modding the same as anything else, instead of needing to mute the channel or whatever. I do not want to mute the channel because it doesn't prevent things like people changing their nicks or whatever. If need be I would approve an appeals-only side chat before we silence newbirs or anyone who might have an emergency.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561310</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561310</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 18:29:48 +0000</pubDate>
				<wikidot:authorName>RJB_R</wikidot:authorName>				<wikidot:authorUserId>1229263</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This. Muting the channel both requires the least amount of work and doesn't require any major policy changes.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561308</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561308</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 18:28:31 +0000</pubDate>
				<wikidot:authorName>RJB_R</wikidot:authorName>				<wikidot:authorUserId>1229263</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Agreeing with this sentiment, I think putting 17 on +m is a lot easier and more functional than another channel we'd have to moderate just for appeals. The few instances of someone coming in during an appeal would be easier to deal with than the struggle that comes with making sure a cadre of appropriate staff hang out in the appeals room. Plus we'd have to probably mute the room anyways unless we completed discounted non staff and non appears in. Otherwise you're just moving the problem instead of really solving it.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561262</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561262</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 16:55:47 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Are there really enough appeals for this to have any utility?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3561102</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3561102</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 11:59:56 +0000</pubDate>
				<wikidot:authorName>LilyFlower</wikidot:authorName>				<wikidot:authorUserId>1876818</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Whilst, &quot;oh no, more channels and bureaucracy!&quot; is the first thought that springs to mind, a dedicated appeals channel would solve the problems of peanut gallery comments and having to mute 17. If we had it as staff and appealing parties only, it would cut out unnecessary comments entirely (aside from staff dogpiling which is always easy to deal with), as well as ensuring 17 is kept open to help at all times. I imagine it'd be open to all chat and site disc staff (including the admins) but there'd be no real harm in opening it up to all staff.</p> <p>It'd be easy to redirect banned users to it, i.e. telling them to join it in kick messages or simply informing them once they join 17.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560821</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560821</link>
				<description></description>
				<pubDate>Sun, 30 Jul 2017 00:40:59 +0000</pubDate>
				<wikidot:authorName>Doctor Cimmerian</wikidot:authorName>				<wikidot:authorUserId>1414765</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Honestly, I'm starting to think that the idea of a channel devoted to appeals wouldn't be the worst thing in the world. We've split off crit already, and I think as we grow our user base the collision of appeals with help requests is going to be just as bad, if it isn't already (I've seen this on more than one occasion).</p> <p>An appeals channel being +m all the time would be simple, and we could deal with user appeals as they come . And when spammers/trolls try to choke up 17 with appeals or whatever (as has happened once or twice recently), it won't be in view of literally anyone but staff. Without an audience (and the occasional person chiming in when they shouldn't), that'll certainly be less of a problem (though of course it won't eliminate it).</p> <p>I'd offer up #site88 if we decide that's a solution with merit, I've kept it registered for a while now but I don't use it for anything.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560790</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560790</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 23:23:51 +0000</pubDate>
				<wikidot:authorName>thedeadlymoose</wikidot:authorName>				<wikidot:authorUserId>732274</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Using +m favors the convenience of banned users and operators over the convenience of new users (who will be much more confused by not being able to speak). Why not take appeals to a side &quot;disciplinary&quot; chat if it becomes necessary on a case-by-case basis?</p> <p>Operators have always been able to temporarily ban people who cause problems in 17, and to permanently ban them if it's an ongoing problem. It's just not standardized, and takes place at operator discretion. What's the specific benefit to standardizing this? If it's to encourage operators to do it more, does that outweigh the possibility of encouraging operators to overuse it?</p> <p>(While I confirmed on chat that I didn't miss any policy changes preventing operators from banning people from 17 for disruption, the opening post implies that kicking is the only option available to operators here.)</p> <p>Similarly, operators have always been able to use +m during an appeal (or other 17 discussion) if they wish. What's the specific benefit to requiring +m? Does it really outweigh problems created for new users?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560734</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560734</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 21:20:12 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>The +m during appeals is handled simply by a &quot;Sorry, [user], please wait for this to be over,&quot; <em>which we already do</em>.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560728</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560728</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 21:15:07 +0000</pubDate>
				<wikidot:authorName>LilyFlower</wikidot:authorName>				<wikidot:authorUserId>1876818</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>We wouldn't be putting +m on #site17 in a permanent basis, just during ban appeals or pther disciplinary discussions where input is not at all needed from outside users (I think). +m would only be disruptive if new users joined during an appeal, seeking help.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560723</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560723</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 21:07:24 +0000</pubDate>
				<wikidot:authorName>Silberescher</wikidot:authorName>				<wikidot:authorUserId>304355</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This is definitely worth considering over a stricter policy on backseat opping added to the existing structure. There's a significant gray area between helpful comments from users and disruptive ones that involves a number of factors: intent, subject, topic, any other discussions which are happening at the time&#8230; and it should get better results for ops to be able to simply curate the number of voices which can speak in 17 at a given time rather than trying to police their behavior after the fact and case by case.</p> <p>The downside is that this change will increase the barrier to entry for new and returning users. It means that we will want to append the Chat Guide to explain +m in 17 and that anyone who joins will have to PM an op for voice. This will affect everyone's user experience, while it will have a much lighter impact on 17's daily function if the operators in 17 just remove users who continually disrupt the process. (And those who are disruptive, rather than merely unhelpful, tend to repeat the behavior.)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560702</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560702</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 20:36:23 +0000</pubDate>
				<wikidot:authorName>Bouncl</wikidot:authorName>				<wikidot:authorUserId>302928</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Procyon's right. This is an overreaction. Handling backseat modding is also part and parcel of being a chatop- there's no reason to standardize this because you're already entitled to handle disruptive users.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560684</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560684</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 20:08:49 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Better that than this absurd overreaction.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560683</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560683</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 20:08:08 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm in favor of this. Let us not forget that a lot of current staff (myself included) cut their teeth helping out in 17 as users.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560647</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560647</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 19:09:32 +0000</pubDate>
				<wikidot:authorName>LilyFlower</wikidot:authorName>				<wikidot:authorUserId>1876818</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Whilst that could work I dislike shutting off 17 to new users who happen to join at a bad time- it's easy to tell them to wait a moment if we know they need help, since they may not know how to PM or such.</p> <p>(Also, yes, half-ops can speak during +m, everyone with voice or above can).</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560644</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560644</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 18:58:54 +0000</pubDate>
				<wikidot:authorName>RJB_R</wikidot:authorName>				<wikidot:authorUserId>1229263</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This seems like the best solution to me. I'd rather remove the ability to make comments than punish people for it.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560634</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560634</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 18:34:54 +0000</pubDate>
				<wikidot:authorName>salvagebar</wikidot:authorName>				<wikidot:authorUserId>1479603</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I suggest that 17 should be put in +m (moderated) mode during appeals and other sensitive arbitrations. You can voice the appellant (giving them +v) and anyone with op will be able to speak (I'll have to check about half-ops), and you can disable +m once everything is taken care of. There's a small chance that someone who is new who enters the channel will be confused by the &quot;You cannot speak while the channel is in&#8230;&quot; messages, but on the plus side:</p> <ul> <li>Anyone who wants to observe can do so</li> <li>Only people directly involved can comment while shit is going down</li> <li>Increasing the speediness of appeals and other proceedings</li> <li>The appellant is assured that they are the focus</li> <li>Upset parties can't make comments which are unhelpful or useless</li> </ul> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560600</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560600</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 17:24:36 +0000</pubDate>
				<wikidot:authorName>Silberescher</wikidot:authorName>				<wikidot:authorUserId>304355</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I approve of this measure, especially as backseat modding in the help channel tends to be performed by the same handful of recurring users (along with isolated, well-intentioned single incidents).</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560578</guid>
				<title>Re: Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560578</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 16:43:51 +0000</pubDate>
				<wikidot:authorName>Dexanote</wikidot:authorName>				<wikidot:authorUserId>481882</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I support quickbans for peanut gallery and incorrect/unqialified help after the first warning.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-3172178#post-3560576</guid>
				<title>Backseat Modding in 17</title>
				<link>http://05command.wikidot.com/forum/t-3172178/backseat-modding-in-17#post-3560576</link>
				<description></description>
				<pubDate>Sat, 29 Jul 2017 16:41:36 +0000</pubDate>
				<wikidot:authorName>LilyFlower</wikidot:authorName>				<wikidot:authorUserId>1876818</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>So, as everyone's no doubt aware, backseat modding can be a problem in 17, as can peanut gallery comments during staff action such as ban appeals. This was brought up in the recent thread about 17 as a help only room, but was never taken forward or formalised.</p> <p>Backseat modding consists of actions such as non-staff acting as staff or ops in 17, offering incorrect or false help, or interrupting staff when they're busy helping or dealing with a problem. Peanut gallery comments involve non-staff users butting in during disc action and ban appeals with unnecessary or unhelpful comments.</p> <p>Both have been dealt with by kicks or such in the past but the purpose of this thread is to formalise the procedure. After discussion in opchat and SSSC there is apparently consensus to start handing out 24-hour bans for the offenses. Discussion and suggestions can be had in here and if no other proposals are offered within a week it'll become standardised.</p> <p><iframe src="http://home.helenbot.com/tools/timer.html?time=1501951211768&amp;type=This%20timer%20expires%20in" align="" frameborder="" height="" scrolling="" width="" class="" style="width: 500px; height: 250px; border: 0;"></iframe></p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>