Re: What's the alternative to "snarling"?

Bron Gondwana <> Wed, 21 April 2021 03:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A8C5A3A0806; Tue, 20 Apr 2021 20:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=ev+4UHnh; dkim=pass (2048-bit key) header.b=iAp3V+KO
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GK9emAi6RFkO; Tue, 20 Apr 2021 20:49:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BEE393A07D6; Tue, 20 Apr 2021 20:49:32 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id E59445C013A; Tue, 20 Apr 2021 23:49:27 -0400 (EDT)
Received: from imap42 ([]) by compute2.internal (MEProxy); Tue, 20 Apr 2021 23:49:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm2; bh=sGbe /9X6lZ+THS0uCqxVHGyvaNYB4RSMoU2k0WME3sU=; b=ev+4UHnhP8hi763AG4fB a69LG3U2E2xw/Yml3xhAmr2+xySOlNOM2yetj4cSkA3+j6FcFQv8eJKLZmXQtJCO nl78pAZvXvLh90LnF/xx8FkuDyHTlsMnppakYtR1U76HED5yHOlVndMhaeeihNwP heqftypOCZNaO/W0U+RxJ78C6+kuNxUOefQfNIuQjLYuy9oQSXoD+WaNeBOjpq5i 15xEnnhe2WyxfjkaA47V5kBVM6bDIg2/ays/wXom/hFl2ycAVkrilTcOgOIonlBr oA7/2rOS10YOj738co3pseuGVGBICgCprxL96XQ1ci02Z+lgZU3XeXe401FdrOKx og==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=sGbe/9 X6lZ+THS0uCqxVHGyvaNYB4RSMoU2k0WME3sU=; b=iAp3V+KOrwLm77t01M9+U2 ja4sAz6Ct8mHkeolJSSh7u1h0wcrib5Axxe02JMjGZOuw2Mpy2tYgJGRV+b1YX9D AUkLhWPKGRYx4JKrbiw+cQHPSymn99GMxve76v6e4q+p4LWe7O30qlzk8Yd71clk dAGlGPiongCPNyUXwJrqzbguE0kSSevOewuaqP940mGY/eLZRjdnlYxL7iRIiw+r ZhRP//zQZj8TQ5YM8wA8U7ovoTXmOa8b+mnvIdscLMQCzvQJRBfu3+ugbnUr30ep WDg4XC+Rf/rxJ6BsBXfOpNbdwQjJQWIqj4YlOdUr4UYmbB15T+P9jVek2OU8TMag ==
X-ME-Sender: <xms:x6B_YAfenxyAZxRmSpQsE49BkWf61t8VDp5k5OuSV98U4bkR-ivXUA> <xme:x6B_YCPv9dmpr2KMY4ovNc2rUeZq7w8u5kkpjGfu_6NU7O4Ub30QhbFIMAK-GPBEE oFzxyApLhg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddtjedgjeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeevffefgfdvhf fhueeffeejudegieffjefftdetleeljeeigfefgefgjeduheefhfenucffohhmrghinhep fhhrrghmvghshhhifhhttghonhhsuhhlthhinhhgrdgtohhmpdgtrhgrphhhohhunhgurd gtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep sghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:x6B_YBicNIgZDO1rd2VLl8RyNjLmYqvsRlwJiOuqWsXGKNdghkLI1A> <xmx:x6B_YF9ypz2bUlWcLavco8zVdolne-BZKxrxXNiqxnONNOssj9lhKg> <xmx:x6B_YMvQ5L6QppU3g1VaJ-bRLm1mggkGpSM-HOyC0YgpztAJetECCw> <xmx:x6B_YF7DDZXX2blI4ZLOxFVwWDIZECx3mZy7BLa0KyuwF8i6DPkIxA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id EC5B4310005D; Tue, 20 Apr 2021 23:49:26 -0400 (EDT)
X-Mailer: Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-625-g0392165453-fm-ubox-20210419.003-g03921654
Mime-Version: 1.0
Message-Id: <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <433863C0CD9449636063CDE3@PSB> <> <> <> <> <> <> <> <> <> <>
Date: Wed, 21 Apr 2021 13:49:06 +1000
From: "Bron Gondwana" <>
To: "Jay Daley" <>
Subject: Re: What's the alternative to "snarling"?
Content-Type: multipart/alternative; boundary=9bc79572619341a49a0e0ca43055a05f
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 21 Apr 2021 03:49:39 -0000

On Wed, Apr 21, 2021, at 13:07, Jay Daley wrote:
>> On 21/04/2021, at 1:41 PM, Bron Gondwana <> wrote:
>> I believe there are good participants who will get out if they see a trust-and-safety secret court established which can judge them as having snarled, and tar and feather them as happened to Jeremy in that blog post above, with no recourse and no fair hearing.
> I don’t recall seeing anyone suggesting that.

Nope, but it's a persistent end-state .  The particular good thing which Jeremy called out was:

Some of these issues are discussed in an excellent presentation <> from Valerie Aurora, who explains that “a code of conduct should contain” “behaviors which many people think are acceptable but are unacceptable in your community”, and that “If you want to list good behaviors or describe the community ideal of behavior, do it in a separate document”, and in particular “Do not require politeness or other forms of ‘proper’ behavior”.

>> We had an induction for my kids' school a couple of years ago, and the principal talked to us about bullying, and about how bullies often know the rules the best - they are intimately familiar with the rules and able to weaponise them against others, poking and needling at the other person until they break and lash out back, at which point the bully proudly shouts "look, the other person aggressed me" and points to the chapter and verse of the rule that was broken.  And looking back at the bully's actions leading up, they were all within the letter of the rules, while quite clearly also goading on their victim to impale themselves.
> That’s behaviour I’ve observed too but I struggle to see the relevance here - are you suggesting that by the community trying to manage down bad behaviour all it is doing is creating opportunity for clever bullies to exploit the rules?

If the community starts enforcing "proper behaviour", then yes - that's where there's an opportunity for bullies to say "X snarled at me, CoC them".  And it's really hard to tell who's the bully in the general case - often both parties have some "instigating" blame to be apportioned.

>> But "assign tasks to old-timers" - in the re-educate all the old bad people who need showing that they're wrong sense?  That's how you drive people out - by their involvement no longer worthwhile to them.  We'd want to be really sure there's newer, better people waiting to take their place before embarking down that route!  That's where I was getting at with the "disuade existing customer base in favour of chasing a theoretical new customer base" analogy.
> Again, I read that quite differently.  To me this was someone suggesting that old-timers are the best choice for documenting all the "discussed ad nauseum" ideas, which newcomers can then read to avoid falling into the trap.  Sounds like a useful section for the new wiki being planned [1].

I found a good one over in one of the other threads, which is very not much IETF specific, and is the assumption "company X is big so they can implement my idea / test my idea easily".  For sure, documenting both "discussed ad nauseum" and "fallacies about how the standards work" (hello protocol police) is useful.

In the degenerate case, once you remove the politeness angle, what's left of snarling is "outright dismissal of input without showing cause"... which is still tricky because when the Nth person shows up proposing that we drop all other work to implement IPv100-over-QBITS, it becomes a DoS to be required to fully educate them to their satisfaction.  In the anti-spam email world it got to the point where somebody built a template for rejecting ideas:

And sometimes a list like that is necessary to allow you to quickly dismiss distractions and get back to work!


  Bron Gondwana, CEO, Fastmail Pty Ltd