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

Emil Ivov <emil@jitsi.org> Sun, 06 June 2021 07:13 UTC

Return-Path: <emcho@sip-communicator.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 472743A0BFC for <ietf@ietfa.amsl.com>; Sun, 6 Jun 2021 00:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.037
X-Spam-Level:
X-Spam-Status: No, score=-1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jitsi-org.20150623.gappssmtp.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 WeVm-JVloHvA for <ietf@ietfa.amsl.com>; Sun, 6 Jun 2021 00:13:34 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 F1D583A0BFA for <ietf@ietf.org>; Sun, 6 Jun 2021 00:13:33 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id n17so425155ljg.2 for <ietf@ietf.org>; Sun, 06 Jun 2021 00:13:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jitsi-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8EYsCGWC7H9cWlXoF3MRb2/cdskJZjXAdRDUtL9Oz9M=; b=FsqAzD+sJyweoAdLYHGyaGFceoxTQFZnPyUoo762Uj6YrOY1m2/AtuPbVX+DovlGqN iXJ777rhMe/fv4mF84O7LVy1MvzifJJUfGPb9EP8XwDji7jDdHYopYb/nppVi0hOpS5N A/h52WFy/HWyRvgVcDEMRmLgZmyE6vrXjWb6NdMliwt8SEHVaMk53jOphvcvXMTeAbvH SaEU+t3nb8ZqwRBkdOaAAbL1RgGjRl8HDgPCJFbIz4BGoBGeEvYFbPWkYa5T82inVSLS l2/5vA5OQw7CPmBamY9eCXEk5o3WEnDKAQIkfes9Mn3Bp9rfOTzCAk2YtcN2/JIUgB2u zyYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8EYsCGWC7H9cWlXoF3MRb2/cdskJZjXAdRDUtL9Oz9M=; b=jPuDestmyySo1UoE+qFVFZ1C1AS1X8xS259n4XvRqPSwC0dkLLkxxNlVsECfyFgpb4 KxEdPRUI/eIv146sqFKC/yTzHOtDRS67xEkUktYdaauMvgywHsRsF/YaGu1NSPCQqErg Kvh1bor9vLLucSnVZyJvjJ8+Z3E7/2Bna0D2WKHUDj9lBU6s1G0LnLCogdOO7eHDis42 S01yQXh+/bUqcrSi4tr7v/0T1/Ax4xumprp5cw6QzH2xrfKuiNQcYaiNkrLvtgcU/4D4 ZbZgmeueXsCz1hmkwt8R2qnSRdEyqsJRGXk0sv52fjfn71KP9QGcr6dMXzDZn17Uhr1Q GRfA==
X-Gm-Message-State: AOAM533mBSf5Z8RgDif0Ps3QluLIu/kW9SBkJSKlYIfCwlYGpMFuc09m BUKRLijOZqFev/kMKZIfBUA+HDmNctpUlz8NqCF27Q==
X-Google-Smtp-Source: ABdhPJx7Ta/DknFez6NaRt+V+HhacBZzOCwfTal+OIySzq4wNEAOMHLnzbAZj9lUbIF8FJm86q4/pB54k02IImqbSm8=
X-Received: by 2002:a2e:81cb:: with SMTP id s11mr8655412ljg.466.1622963606052; Sun, 06 Jun 2021 00:13:26 -0700 (PDT)
MIME-Version: 1.0
References: <HJCFnRF4-BhmmY94naAXr7OwaHttkaKO4_PJx6u2V8ZyHKfo91h0wX96saMVs0sI6KM2vx-h6B-j1dGqj6XqneGrdw-smKRSp9LYfmYZGsg=@softarmor.com> <E1920BE6-34CA-4246-8424-928EC0BA77B7@puck.nether.net> <010801d75a97$04e30f70$0ea92e50$@acm.org>
In-Reply-To: <010801d75a97$04e30f70$0ea92e50$@acm.org>
From: Emil Ivov <emil@jitsi.org>
Date: Sun, 06 Jun 2021 02:13:14 -0500
Message-ID: <CAPvvaaLXo8G8HrHuiU77HtrbR43ZCnprAPCOPGdC8SL2Yi1e5g@mail.gmail.com>
Subject: Re: Why we really can't use Facebook for technical discussion.
To: Larry Masinter <LMM@acm.org>
Cc: Dean Willis <dean.willis@softarmor.com>, Jared Mauch <jared@puck.nether.net>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="00000000000038f29f05c413a902"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eISCPtxEp9_C-CUpoOWuhO9vmVA>
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: Sun, 06 Jun 2021 07:13:39 -0000

Ironically, advising *others* how *they* should follow Postel’s principle
is exactly the opposite of the principle.

On Sun, Jun 6, 2021 at 00:44 Larry Masinter <LMM@acm.org> wrote:

> This is the argument about Postel's principle (conservative in what you
> send, liberal in what you accept) in layer 9.
> It seems to me that Facebook is doing just fine slowing down (24 hours)
> the possible propagation of violence incitement without requiring a lot of
> judgement on what does or does not constitute thoughtful vs. inciteful
> speech.
>
> "Kill them all and let TCP sort it out" can readily be expressed in other
> terms. A content moderation policy that slowed down frequent postings (by
> 24 hours) might temper heated conversations and lead to calmer
> considerations of the actual requirements.
>
> > I hereby propose we censor Facebook engineers in IETF meetings for
> promoting stupidity.
>
> Can public forums improve the quality of discussion by delaying frequent,
> divisive posters?
> Is trying to do so really  "promoting stupidity"? (Obligatory 😊)
>
> --
> https://LarryMasinter.net https://interlisp.org
>
> --
sent from my mobile