IETF Logo Mail Archive

Re: Old directions in social media.

Kyle Rose <krose@krose.org> Fri, 08 January 2021 16:07 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 BAC3F3A10B1 for <ietf@ietfa.amsl.com>; Fri, 8 Jan 2021 08:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=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 2lJmyyvCEQC2 for <ietf@ietfa.amsl.com>; Fri, 8 Jan 2021 08:07:26 -0800 (PST)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 DFA153A10A4 for <ietf@ietf.org>; Fri, 8 Jan 2021 08:07:25 -0800 (PST)
Received: by mail-yb1-xb36.google.com with SMTP id w127so9804861ybw.8 for <ietf@ietf.org>; Fri, 08 Jan 2021 08:07:25 -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=2EoG+Zv6CFgQpV0CUWt4AL52fZE916Frx2AeB6XBA5M=; b=OE8CosXVg83YGcOOx3eRzPaSNBswPzC55RoE3kT7XZQTPwNlwUk/g8zT8yGwJufd+b wSTO+0539FTl5nfGfklQY0xD/to7HnrBrMM6dZsIzp+5NjFSxbw8JvK8qJjnQBesSi6t vlcVHWgGOvDoEFlPdoztT00NP/gSf5qHvt93k=
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=2EoG+Zv6CFgQpV0CUWt4AL52fZE916Frx2AeB6XBA5M=; b=YToDZKdMY9s7ZWzV9siWTPT5UXbLLJ3MSrlLPS7cYEyqdUudLvWqraFIUFK/4FOegR 1RUhUOLn/P9IasikqaxeshaMmrVvk43cdY+RjmJOc0SFdkqJweDNmYoet0HRuMwzTWhU LGO1zgmG+nId6lhWQP8336V0bLiAYEXwmtIFGT69syu7cZs7LRQ4WySgNydvM1VKlyaS rElH21THrvK333UvSeBnqjvxbt6FTVajgfBlJMaGWRtxf1x+FBh+UdwihL7GmaYoqzEW GDKskGFfFwyFiFCTo5KgScpAWp2qsKZO3zqmEFGCRkqAwQFf8bVP/2XGVfsncgnSSkTp uECw==
X-Gm-Message-State: AOAM532NsELB5rL89JK4wL1hfGnkU/Zv0b+kTM/VYKo06R7eStrVPDSU muaTaEKQwCY6+iCCjH5luDBAQo7q5aNButaK9oxsXw==
X-Google-Smtp-Source: ABdhPJzcIThpAXpdavPsztP2Rdinh/1T8dYRZdhWTNg//asJaphX23SFE/tGe2EyLpnNfVsHzNiYHRntV8JUtU5oekA=
X-Received: by 2002:a25:d0cf:: with SMTP id h198mr6437122ybg.384.1610122044890; Fri, 08 Jan 2021 08:07:24 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <519a0e4d-7102-fac8-1517-04c590a80080@network-heretics.com> <MN2PR11MB43668BD4EE84EDCCA9C8062AB5D00@MN2PR11MB4366.namprd11.prod.outlook.com> <8d37d121-3f47-43b4-93ae-036068121b08@network-heretics.com> <91FCD1A5-050D-476D-8EEA-38CB43DE20F1@akamai.com> <CAMm+Lwgvats19N7P1um437_LXjNG2gLK9OZCQdWmWBD52Gbuwg@mail.gmail.com> <24914.1610060002@localhost> <CAC8QAccjdtoEDn0Ckac9FNwrUhQMq6N=opef7FkbaOFW0c2hNQ@mail.gmail.com>
In-Reply-To: <CAC8QAccjdtoEDn0Ckac9FNwrUhQMq6N=opef7FkbaOFW0c2hNQ@mail.gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Fri, 08 Jan 2021 11:07:12 -0500
Message-ID: <CAJU8_nX37oACG3GsyoHSSTaxqu_ZHFn-5uBBW2tkymJT4vNODQ@mail.gmail.com>
Subject: Re: Old directions in social media.
To: sarikaya@ieee.org
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Phillip Hallam-Baker <phill@hallambaker.com>, "ietf@ietf.org" <ietf@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000087f96e05b865c0f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rfpPLaKRetc25syGflZu2_UbHlo>
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: Fri, 08 Jan 2021 16:07:28 -0000

Tl;dr: Old man yells at cloud. Other old men yell back.

The thread starts here:

https://mailarchive.ietf.org/arch/msg/ietf/K0o3LACAN_xysoD8zlaqQgQN5rE/


On Fri, Jan 8, 2021 at 10:56 AM Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> Folks, I see heated discussions on this thread, but I missed its
> beginnings.
> I would appreciate if someone shortly describes what is being discussed
> and what has been learned so far?
>
> Behcet
>
> On Thu, Jan 7, 2021 at 4:53 PM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>>
>> Phillip Hallam-Baker <phill@hallambaker.com> wrote:
>>     PHB> My experience of the OpenPGP BIS WG was that the attempt to use
>> github were
>>     PHB> one of the things that led to its failure.
>>
>> Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>>     RS> That WG used GitLab, not GitHub.
>>
>> PHB,
>> I don't know what happened, or whether it was GitLab or GitHub.
>> I do know that it was at least five years ago, right?
>> I would appreciate some summary of what went wrong?
>> Was it really the tool?  Was it people using the tool wrong?
>> Were they fighting the tool?
>> Were they disagreeing (maybe even implicitely) on how to use the tool?
>>
>> I'm asking this to understand what a better tool would actually do.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting
>> )
>>            Sandelman Software Works Inc, Ottawa and Worldwide
>>
>>
>>
>>
>>

v2.23.0 | Report a Bug | By Email