Re: Why we really can't use Facebook for technical discussion.

Keith Moore <moore@network-heretics.com> Mon, 07 June 2021 20:13 UTC

Return-Path: <moore@network-heretics.com>
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 38ECB3A0CB4 for <ietf@ietfa.amsl.com>; Mon, 7 Jun 2021 13:13:39 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 9i5fjQ7HXdP8 for <ietf@ietfa.amsl.com>; Mon, 7 Jun 2021 13:13:34 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24173A0CB3 for <ietf@ietf.org>; Mon, 7 Jun 2021 13:13:32 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id B2A3A16E5 for <ietf@ietf.org>; Mon, 7 Jun 2021 16:13:27 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 07 Jun 2021 16:13:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=+TmMTV 982wmxVljIu32b/yAp/Enj1uVN3pTrH/+Z0NQ=; b=dHuLWYLDsO6FuC57T2wIIc YM0RnDuxKgA58j1ryXHHDi7kj3v6H7UubwDUGWmBRX8gBINCrhW5GE4A7o8zKPQ1 LVZO0ny7quxZuRCuUyFl4P4lrRvwV0NxEfQD7bkL7asdWOkEY2FnIFsDov+6fEAe ttXsYA1cJCO1OHWbQUhiUnqASd4WBJuILRpE0Kj5opJflfRHWBVtgUJT+5XMMLz3 F6auQY3hMU44Qyhyg5uX8XIz/ZjMubmFmuZFBexuAQb/iXxnXKC/XWNDa9S8mKhs 6ec+n5hBpTElZkPQFMyUxZynMuUSiDIqiXrZcryCQB+HAYYZQ+hwrKGaeL51iF2Q ==
X-ME-Sender: <xms:5n2-YK8vOc5-9M6GpvSPTAyLyvQFxTsKJzh49Co5oRcOV3JW9epeBA> <xme:5n2-YKujei5OlEkmkIZxFVZoHfnXsvycPUN8PYvFEKw19nFhx4r-QN4wm6RQp3wZv f_z9bCDeDtCBQ>
X-ME-Received: <xmr:5n2-YACqRxy8XhuQe-BNhJ-F4JoroL7oFB6CcZ5Y-YHzy2Hd41YX6-xy9MbWWY0Wg6UEQv4ffjFIKh-fBlo3K47MtqIFnA4NkgFutdJWVw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtjedgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtd erredtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeevfeetudeige dtledvvddtudefjeejffdvfeetjeeiueelgfdtgfegtdffkeetudenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorh hkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:5n2-YCfOImpFv-lIeHT5Me3me02EvQZeeKktGXv-6Tgz6Ew0eLRqUw> <xmx:5n2-YPOUQJDHWly-fDqRdjLEGGGE4WBizkDTLpZdZ6fb7mYSyVf0vw> <xmx:5n2-YMlZPPwJ36bGabXMtnt81SrhJM_fkSZ0U1DdVvHRnyzE0YROWw> <xmx:532-YFZBmDs_PQjPAzBe_y4zu4z18gz3s8klO7ukt06-1I05yu5Lsg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Mon, 7 Jun 2021 16:13:26 -0400 (EDT)
Subject: Re: Why we really can't use Facebook for technical discussion.
To: ietf@ietf.org
References: <HJCFnRF4-BhmmY94naAXr7OwaHttkaKO4_PJx6u2V8ZyHKfo91h0wX96saMVs0sI6KM2vx-h6B-j1dGqj6XqneGrdw-smKRSp9LYfmYZGsg=@softarmor.com> <CALZ3u+a+ry4pd5eAB3QiboA2pwiVhTgc0D4Zte5_u+bj-GsonA@mail.gmail.com> <-Jo05E3w-YIEezoXLI6MpB83ZYosN9BemjreW0cpF-DKiwGfD1pdvjQNWNIRYKnfiqfQR46Ny1e5Ee2ppuMlGTLU1Jei_S4gcB1V9tc6YFI=@softarmor.com> <CAMm+LwgeZ787ae00+=fw8BP=n5OQ_TMsbtEeG16Zau=5O2Gxrg@mail.gmail.com> <4a05b42a-3ca5-0d13-0956-a66545906fe3@gih.com> <CAMm+Lwj1fB088mOULXOSDKf8LoCsUGbOSHNxfgoCws+VjfcO2A@mail.gmail.com> <1127625088.5911125.1623040315510@mail.yahoo.com> <d68ec897-1506-86e5-578d-41672bdffaef@network-heretics.com> <d2dec2e3-b9f3-2530-f143-67bb01f35269@alumni.stanford.edu>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <c2633234-9c3b-f09d-3ea8-9b052eb2b7c7@network-heretics.com>
Date: Mon, 07 Jun 2021 16:13:26 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <d2dec2e3-b9f3-2530-f143-67bb01f35269@alumni.stanford.edu>
Content-Type: multipart/alternative; boundary="------------ABEB24B65A770994F8348350"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YBq8dxVgtX752CVLKgMIRVf_7vM>
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: Mon, 07 Jun 2021 20:13:40 -0000

On 6/7/21 12:42 PM, Randy Presuhn wrote:

>> Because misandry in the service of inclusion is no vice?
>
> When (male) privilege is threatened, the reactions often look
> like (male) fragility.  One would hope to avoid zero-sum games,
> but I think one must admit the possibility that some stereotypical
> (but hardly inherent!) behaviors are at odds with inclusiveness.
> Having a particular genital configuration is not an issue.
> Interrupting and talking over others (for example) can be.

IMO the argument would be much more convincing without the cheap (and 
almost obligatory) shot of insulting people for their gender.  The 
hypocrisy of such arguments completely rids them of any credibility and 
also often distracts from the real nature of the problem.   (And it's 
certainly a violation of the IETF Guidelines for Conduct.)

Why do people sometimes talk loudly in IETF discussions?  Because 
they're frustrated, probably because they're not being heard!   At least 
half of the time this is because of other participants who are having a 
hard time seeing past their own preconceptions.   But the popular 
fashion is to blame the speaker nearly 100% of the time, even when the 
speaker is speaking clearly.   This tactic is especially common among 
those for whom the speaker's input is inconvenient.

It follows that if we want less talking loudly in IETF discussions, we 
might do well to improve the ability of IETF participants to listen.  Or 
at least we could realize that communication is a cooperative endeavor 
that requires investment on the part of both the speaker and the listeners.

Keith