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

Fred Baker <fredbaker.ietf@gmail.com> Sat, 05 June 2021 23:20 UTC

Return-Path: <fredbaker.ietf@gmail.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 2A3EF3A340B for <ietf@ietfa.amsl.com>; Sat, 5 Jun 2021 16:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 9zrZCY31kJH8 for <ietf@ietfa.amsl.com>; Sat, 5 Jun 2021 16:20:06 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5FE83A3409 for <ietf@ietf.org>; Sat, 5 Jun 2021 16:20:06 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id mp5-20020a17090b1905b029016dd057935fso1401015pjb.5 for <ietf@ietf.org>; Sat, 05 Jun 2021 16:20:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=x/MH/XzUpp9cSf7cl5U3C/ma+Tet/ropri1qWe9S9U0=; b=l7xbUgTOOhclMX0rh1zahsEBHHSsVi+Yj8ZwP9NNVh1iFvYTvnNqkrBHp+pJ0LQAOI S2tUABlGUbWXjtJAzsP2PIvs14/v5HxrlTNU58K5FiImIYHEq5cI2plTq2IBDAhNiLKm ZDkGxtblAPr1V+IaXTQnmKZkmWeX23mvWdzAzkysIkqkWi7O22U8aXUBIGH43NYVPTdi 4MDQzb+5tD9EOwHxQGae7CiYHUgWcuJPGEG0LvLsY2MtUrCG/sTabCLhFISyxtUp0rCi iLH9XMSbV3i676XoDVMj3bHSK6GWdkof02xbg4raFr7q5JLbnst2ZSvJtMNYFw0Bd5Jy uSjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=x/MH/XzUpp9cSf7cl5U3C/ma+Tet/ropri1qWe9S9U0=; b=qjDlqG83TNb2l5Tjtfnt6fJf7iK1yGNDmvMsS8kUwst+griXAcDjhxI9ptLSwu5XBg 842od7AR2cEPOM/my76onVpgE5l8sfbZhPmn5hf5iOHK5jjgwuw1ojaYJO96EL+5PHVw nQDeQ3CZUBuzAjGdEi2+5CsrWf5Wtz67ty5Ru09ZjDD25tFBHOxPMVffm24Y/sl2dxa2 yU8cu1wwXfttp0jkAd2S2hp8CXDX+MqERy4q4srRqbImAaHYurIrTC0YTbBG/6j6ry/h gN3DfPyigx2To+yUe0agxzfjNYkNN86ZigYrfVJVohEvgiYdzd/KbX2iZc/KQejjCSy4 tF7g==
X-Gm-Message-State: AOAM533QnoNKbg85EME5mosGeIQURRcc1AaT3BJhiXQNTNbog8dBI+xm 1tfbqOzUpf8jE9MZh8gc9qM=
X-Google-Smtp-Source: ABdhPJz9IPI/nCY96TjtnlcM94ijmEcf4QlkEcozqb+O/fskbgL07Hxz9ZMV605korNBTCemXzsq6Q==
X-Received: by 2002:a17:903:1c3:b029:f4:9624:2c69 with SMTP id e3-20020a17090301c3b02900f496242c69mr10980620plh.51.1622935205744; Sat, 05 Jun 2021 16:20:05 -0700 (PDT)
Received: from smtpclient.apple ([2601:648:8200:dd20:48f6:377e:6298:e14f]) by smtp.gmail.com with ESMTPSA id h12sm5247910pgn.54.2021.06.05.16.20.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 05 Jun 2021 16:20:05 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
X-Google-Original-From: Fred Baker <FredBaker.IETF@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Why we really can't use Facebook for technical discussion.
Date: Sat, 05 Jun 2021 16:20:04 -0700
Message-Id: <1C297215-667C-43C3-BF20-DB2564BC0A32@gmail.com>
References: <HJCFnRF4-BhmmY94naAXr7OwaHttkaKO4_PJx6u2V8ZyHKfo91h0wX96saMVs0sI6KM2vx-h6B-j1dGqj6XqneGrdw-smKRSp9LYfmYZGsg=@softarmor.com>
Cc: ietf@ietf.org
In-Reply-To: <HJCFnRF4-BhmmY94naAXr7OwaHttkaKO4_PJx6u2V8ZyHKfo91h0wX96saMVs0sI6KM2vx-h6B-j1dGqj6XqneGrdw-smKRSp9LYfmYZGsg=@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
X-Mailer: iPad Mail (18F72)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B9ujKzgcEIbym6UaKHe5To6JyA8>
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: Sat, 05 Jun 2021 23:20:11 -0000

I’d suggest that we do so for cause, if it happens. It’s not the engineers making the silly calls.

Sent from my iPad

> On Jun 5, 2021, at 3:35 PM, Dean Willis <dean.willis@softarmor.com> wrote:
> 
> 
> 
> 
> 
> Today, Emil Ivov posted a humorous note about how the various SIP-related network traversal RFC efforts like STUn, etc. reflect a tension between realism and pragmatism.
> 
> I responded with my usual argument, that I'm in the "kill them all and let TCP sort it out" camp.
> 
> That earned me a 24 ban from Facebook for promoting violence.
> 
> I hereby propose we censor Facebook engineers in IETF meetings for promoting stupidity.
> 
> --
> Dean
> 
> 
>