Re: tone policing

Dirk-Willem van Gulik <dirkx@webweaving.org> Tue, 03 September 2019 15:25 UTC

Return-Path: <dirkx@webweaving.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2ECA120046 for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 08:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ce2fgDJczbJo for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 08:24:58 -0700 (PDT)
Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F65A120119 for <ietf@ietf.org>; Tue, 3 Sep 2019 08:24:57 -0700 (PDT)
Received: from [10.11.0.158] (94-210-134-94.cable.dynamic.v4.ziggo.nl [94.210.134.94]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id x83FHtvZ097146 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Sep 2019 17:17:56 +0200 (CEST) (envelope-from dirkx@webweaving.org)
X-Authentication-Warning: weser.webweaving.org: Host 94-210-134-94.cable.dynamic.v4.ziggo.nl [94.210.134.94] claimed to be [10.11.0.158]
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
Message-Id: <A234DA88-6088-44B3-B8C9-6221429882EA@webweaving.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0600FA94-ED39-423C-9A67-5C7F3B6E8B1D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: tone policing
Date: Tue, 03 Sep 2019 17:22:22 +0200
In-Reply-To: <381923E6-597B-4208-A959-0E19BA405B49@fugue.com>
Cc: Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.org>
To: Ted Lemon <mellon@fugue.com>
References: <F2D6FBAB-7DED-41AE-9560-4D0D13B15107@ericsson.com> <1BF349D9-8ABB-4844-965A-A43964E18A41@fugue.com> <29c10b3d-8f48-8888-68c9-7390b1e4df5d@network-heretics.com> <ae8353f1-adf9-c615-a721-9fba85b40d5c@foobar.org> <059707fd-afea-e4b4-fa77-967e38206c52@network-heretics.com> <381923E6-597B-4208-A959-0E19BA405B49@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (weser.webweaving.org [148.251.234.232]); Tue, 03 Sep 2019 17:17:57 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4Se8jCpRmPHpx8fFHyE_Un95BnE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 15:25:01 -0000

On 3 Sep 2019, at 16:23, Ted Lemon <mellon@fugue.com> wrote:
> On Sep 3, 2019, at 10:04 AM, Keith Moore <moore@network-heretics.com <mailto:moore@network-heretics.com>> wrote:
>> I'm just sending replies to people arguing for censorship.   What I wonder is, why aren't more people objecting?
> 
> I suspect the reason is that I am not the only one who sees excessively frequent posting of the same message as a form of censorship.
> Rather than responding again, perhaps you should listen for a while?


So going back to the issue at hand, rather than people and what they should do or thing; on technical mailing lists I find it common to see pro/con arguments near the core of a design of principle repeated. Often. 

Sometimes I feel i can attribute that simply to people relatively new to the matter - and who have not had the time to read up on the design; or the design being so specific that it is hard to relate to from an adjacent field. Or because technical designs often need a a fairly black and white take on things in order to be implemented on a computer.

But equally often - it simply is because the structure of a lot of issues is that desire or plan for feature N+1 gets stuck/hits some crucial bit deep down - and the same argument `why that cannot be done’ bubbles up again. Just like the speed of light or conservation of mass often blocks a fun addition to physics.  Or that you need UTF8 for XXX, or a type of `escaping’ of the next character, etc. Or a `get out of jail card’ into the land of MIME. Or ‘order’ on something like a struct.

And although some percentage of that is, or becomes, a natural reaction of jaded people; and arguably the `reject’ may come too soon or without careful study - I find more of then than not that a path I embark on to fiddle/improve a protocol; hits such a technical 1+1 needs to be 3 sort of snag.

So designing a set of social rules that is overly sensitive to such repeat-a(core)-argument seems a bit out of place for such a technical space.

Dw