Re: Old directions in social media.

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 06 January 2021 05:46 UTC

Return-Path: <hallam@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 F30593A109A for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 21:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 go3eyfgAlx5c for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 21:46:24 -0800 (PST)
Received: from mail-yb1-f171.google.com (mail-yb1-f171.google.com [209.85.219.171]) (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 449DF3A0F0A for <ietf@ietf.org>; Tue, 5 Jan 2021 21:46:24 -0800 (PST)
Received: by mail-yb1-f171.google.com with SMTP id f6so1761147ybq.13 for <ietf@ietf.org>; Tue, 05 Jan 2021 21:46:24 -0800 (PST)
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=cnW3A2qIKbTCNFJnqlwt8JMn8AJx1vtK/AU82Ks8wu8=; b=lWUZHDx7hUOKBSCUeMV9XdM2iv3ozmpne9n6UdkHosK1KAF+euCUvf+9emrkzuHhy+ cwDnPRmaBxSio4/sfjz3ajOWekBnBZhDLblFQUb+54UHe2olPQHhGgX5N9c1sLLkm6cv ExrLyw73XubNr7dc9rbMTuk4uFjrufwik6EsNlGpEiX6crL3Xss1k3E7pnlqsuHnXDlZ 5N70hz9kEaXUJ/xRyTRljynSak9cB3gJP8Nbnb6tr+aow2zxEXYKiKU2TxDXJBdn2AlD H/W5l2cQr0+3dsMSwVPu4jirTsbs/Y6yeMbz47whZGcRj1uCdchQALZ5ZeISTQjtiIsY 9sTA==
X-Gm-Message-State: AOAM533VYYlPsVIedXih+os8Ydn6ZP/qZaA6hHbbi6qSY1tWTPC0/Noh 3CmbMnMeto034FUKPYekWsVxTGiLx3ESgGiNQ4+F8BiDmVI=
X-Google-Smtp-Source: ABdhPJzhEz3zKwXNZyYI6+lmij2gTOkFJ4Z2wjNjKo++zt+qxlTqI9ATAneKzsgyr+I8JyPxILL5mtF9g3noXyljQBY=
X-Received: by 2002:a25:bcc:: with SMTP id 195mr4149141ybl.273.1609911983445; Tue, 05 Jan 2021 21:46:23 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <519a0e4d-7102-fac8-1517-04c590a80080@network-heretics.com> <CAJU8_nUU0Km_YtgpWbLF-JVQVUXFYvxBNBYbzaLOXBqQyvvUaA@mail.gmail.com>
In-Reply-To: <CAJU8_nUU0Km_YtgpWbLF-JVQVUXFYvxBNBYbzaLOXBqQyvvUaA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 06 Jan 2021 00:46:12 -0500
Message-ID: <CAMm+LwjNVjqCqqdFry8xeeq637mzNTzCfboLZ4Vf59YkxYsmpw@mail.gmail.com>
Subject: Re: Old directions in social media.
To: Kyle Rose <krose@krose.org>
Cc: Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e49c2c05b834d76f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vufhoea_eMkRkMYQAegs0XQkfoA>
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: Wed, 06 Jan 2021 05:46:26 -0000

On Tue, Jan 5, 2021 at 12:09 PM Kyle Rose <krose@krose.org> wrote:

> I do not understand why tools need to be limited by the least common
> denominator for the IETF as a whole, or limited to 1982 technology. Why is
> it such a burden to ask people to learn a new tool once every 3 decades or
> so? Clearly, git (along with related tooling, such as kramdown) is of great
> value to many because they've spread across the IETF at (for this group) an
> incredibly rapid pace.
>
> IMO, a better response to the challenges posed by useful new tooling is to
> make it more accessible, not to prohibit it.
>
> Kyle
>

Since the Open Meeting requires a Lisp Machine to run (!) I was not
suggesting that we adopt that. What I said is that I am starting to build a
tool for my own purposes, namely the ability to hold end-to-end encrypted
collaborations in environments that require a higher level of security
including classified and SCI environments. I am not aware of github being
used for those purposes.

My problem with using git/github as a process driven collaboration tool is
that github is designed to perform an entirely different task. So the
effect is like someone telling you to use a screwdriver as a hammer and
ignoring the complaints from people pointing out its a bad match. That
doesn't mean it isn't the best tool available at the moment but it is not a
good tool for that purpose because thats not what it is for.