Re: Old directions in social media.

Kyle Rose <krose@krose.org> Thu, 07 January 2021 17:53 UTC

Return-Path: <krose@krose.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 34D453A03FC for <ietf@ietfa.amsl.com>; Thu, 7 Jan 2021 09:53:08 -0800 (PST)
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, HTML_MESSAGE=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 (1024-bit key) header.d=krose.org
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 0edyTkN9L4H9 for <ietf@ietfa.amsl.com>; Thu, 7 Jan 2021 09:53:06 -0800 (PST)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 895943A03FB for <ietf@ietf.org>; Thu, 7 Jan 2021 09:53:06 -0800 (PST)
Received: by mail-yb1-xb2e.google.com with SMTP id j17so6862447ybt.9 for <ietf@ietf.org>; Thu, 07 Jan 2021 09:53:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HTY6y1kQeQihUgebOBwG9WLvdjS570dXJmGi4pgvVGQ=; b=Rle8NFoQ/mAdy4r/yWVXeuAkm2977Y7FtanyCeokWrl97op0AzOdx47d6J/f210He0 BcCkJ4lpMzirXVUkNhB8u+fZrBDj6bseVizdeQqch6uTzz+o/dBIIeEOwy3+G1vCKlqk 8wB2XV8BhbWEwf2hQWzpODIHpK/8kmm/MkJ+M=
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=HTY6y1kQeQihUgebOBwG9WLvdjS570dXJmGi4pgvVGQ=; b=Sija89tCaJT48e5YK4OsdLnu3KAQL6SzoJqYPqxQ/o+ho+Qq62IEn+R/FFp4+zpqUj 1bU/JThxbcB87SMmwGcCofp3tmeZJHKiZ6zk3lhFa5YAaTdgIYkKaX1KTQxeBzkLam+W V19w+Ljq2ktcoeWdvZ2F3SVn7Eprjox+LgF3A7j/Udx+eHaIfG/AK1//OHXcucYyQQND 0rPAX8bbm0+LC8+LquAZdsmC6Zp1fEQIcLIe1ZQgRPFiR/dBsjE+bXdXzeQ98mDRVyRA KejZgiP83mrrCZIsbfrnYe7MTDQyO7Piv2J1OO1lZ/hgl9hRdbBtriZfPp+iGxzLfl8P 7wHA==
X-Gm-Message-State: AOAM532pCwE71JM/R4MbGA/yqAZxE2gjfcqdR7mPBYZgmKgt2DxSMWJe zyGC4RLIXOFHFwdbRGiPmqT/5t9yCRp7IqB2irMkPLACnLo=
X-Google-Smtp-Source: ABdhPJyzDTW9+iBIZW+YUv6gXdF8c7GpoH5Bl/fpWZPBehj+5nmV1renvOGezeMEHW1hGbTinPrDxMFEg9SqJDo/Wwo=
X-Received: by 2002:a5b:b0f:: with SMTP id z15mr14784600ybp.296.1610041985496; Thu, 07 Jan 2021 09:53:05 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <CAJU8_nWD3MwLs5aVNMi_3LqZysrfjv0N7N3ujV-zhqxiFh3tsA@mail.gmail.com> <788651ca-0c84-7a54-9c48-b962faed635f@network-heretics.com> <CAJU8_nXSE-E2AVrJnqe5ZifR+qGhXscNCFXQRDj_GU1r=hNOyw@mail.gmail.com> <70416f47-7c31-8571-02ce-f95ff386d54f@network-heretics.com> <X/TtgTtl02AMyns8@mit.edu> <AM0PR08MB371623409DE8AB03CC667234FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <866b1357-ec50-7765-4277-fd4fba8d793e@network-heretics.com> <AM0PR08MB37166B8E57C293917737D9D6FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <d8454121-f6fb-3cbb-3149-656e20efce96@joelhalpern.com> <AM0PR08MB3716C960817BCCFEE4F9F911FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com> <edf8225b-d005-4f99-b96f-41bc49633da3@joelhalpern.com> <AM0PR08MB37169778B08F3F83413194B0FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com> <1dc686a0-6810-a006-5e54-72268b0b55f2@mtcc.com> <CAJU8_nWHwN3tTVyMOf1ZW_ZrKyLnBR_mNbwpzDuoPuZZ3JHNxQ@mail.gmail.com> <6268f836-8f78-3b72-6b61-c4dc3197ab14@mtcc.com>
In-Reply-To: <6268f836-8f78-3b72-6b61-c4dc3197ab14@mtcc.com>
From: Kyle Rose <krose@krose.org>
Date: Thu, 07 Jan 2021 12:52:54 -0500
Message-ID: <CAJU8_nXXS-qHM8wxEQw-HudKvxgDE3Qbj1yONZUZOX3xQNfrEA@mail.gmail.com>
Subject: Re: Old directions in social media.
To: Michael Thomas <mike@mtcc.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009e8e6605b8531cb9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9hV5ox-7C4t9sSOQ83u3xH2-lG4>
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: Thu, 07 Jan 2021 17:53:08 -0000

On Thu, Jan 7, 2021 at 12:32 PM Michael Thomas <mike@mtcc.com> wrote:

> If anybody can send a pull request of whatever magnitude and it is pulled
> by the editors, that's a process problem. That's allowing a backdoor to the
> process of achieving consensus. Yes it happens now regardless of git, but
> that doesn't make it a good thing.


But that is also not how it works. First of all, I assume authors are
acting in good faith: if there is a major change proposed, they're not
going to apply it without understanding how the WG feels about it. But even
if they're not acting in good faith, a bad change will eventually be
discovered by someone doing a diff or a review. While the "rough" in "rough
consensus" refers to the inability to get unanimity on anything, it seems
like it also permits a bit of leeway in terms of determining consensus for
purposes of efficiency and making progress: based on prior discussions in a
WG and the deep knowledge authors have about both the material and the
views of others in the WG, some changes are obviously going to be
non-controversial, so authors often use their judgment to apply them
without actually asking on the list. Bad faith actors and misjudgments will
still be discovered.

Note that this is a separate issue from fragmentation/participants not
knowing about all the work going on that they might have opinions about. I
don't see that as a GitHub workflow or minor change issue so much as an
issue of there being so much work that no one can keep track of it all.

Kyle