path: root/3d/ff59459204e6a5d95a79d1b1a6e76d55f3cb25

Return-Path: <miron@hyper.to>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id D5872C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 17 Sep 2022 07:53:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 948CC40121
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 17 Sep 2022 07:53:05 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 948CC40121
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id FZZ7barEjClB
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 17 Sep 2022 07:53:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 72E4D400C8
Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com
 [209.85.210.50])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 72E4D400C8
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 17 Sep 2022 07:53:03 +0000 (UTC)
Received: by mail-ot1-f50.google.com with SMTP id
 t8-20020a9d5908000000b0063b41908168so16368052oth.8
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 17 Sep 2022 00:53:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date;
 bh=iXsfNnec0k29NLn74MmGe8fmx1l5ROTjZB/KuQVvBT8=;
 b=hrjUVVruU3+pf0QafzJwLQHPEi6v5RHnkWx1eaXyoFPaIlyX2g+Szu4uUiqIMZjyqj
 FwBH6xbq48MFuou5VE8CGKS1UBCIbcE8oBMLJoYreT3XiJT6Ic7WV9eCOUpiatsRqKBe
 bmoW2nE7JgiaWYGsojxY7XPLfofd9rb/o+tJN/bjeV+b30zyOMeVA5onFbPZrtW23/F1
 O00RCOM/TUJoEtqZwq30IIHnXK3YAcX9X79A2KzKCdAcbrnxx11xZeP24Ow4K+jaEDnk
 +afKC2SLjPqE4kLUwhKJPa6Ye6dmM5uH65/YcW/vnZENsEFPXjBVIBQWrWkTSL2rNGhm
 AlqA==
X-Gm-Message-State: ACrzQf31Qr6FUZv73UgfSAFu7Lwez0R9StJ3Aw54X2glgKXqODlhsaj4
 3KV3MxhjJkxJ/x8U5pm+mx2bI6+xGpLfesG4FzvGzg==
X-Google-Smtp-Source: AMsMyM6Ah9QFpFOXlRSqleAvupaj6IFZgCq/KCz1UbB1VDNxV02XymntNY8BtN4YPf+9fwIUDU85ZhIHzWcOBDCni4Y=
X-Received: by 2002:a9d:63cc:0:b0:655:f233:a151 with SMTP id
 e12-20020a9d63cc000000b00655f233a151mr3891145otl.357.1663401182912; Sat, 17
 Sep 2022 00:53:02 -0700 (PDT)
MIME-Version: 1.0
References: <BQjnkZZajHKYBOUFAin8toHgNHhG346VUR4GQx6bSi2ftOuNTK1c1d4LWN4Zmr0tUg2w3xgtIZJSphBORYgWw4PPXq5pGFoZJk2Lx6AokuQ=@protonmail.com>
 <CALZpt+HaeyA8U_6G6RMZCzK944qs4i1ZtcQ=gvAYHm-NSFe4xw@mail.gmail.com>
In-Reply-To: <CALZpt+HaeyA8U_6G6RMZCzK944qs4i1ZtcQ=gvAYHm-NSFe4xw@mail.gmail.com>
From: Devrandom <c1.bitcoin@niftybox.net>
Date: Sat, 17 Sep 2022 09:52:49 +0200
Message-ID: <CAB0O3SVh6xgaUjG_8UyR_3FyG8mcvh7K6ydBkJBTmZXe+rU6Ew@mail.gmail.com>
To: Antoine Riard <antoine.riard@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000a07b6505e8dac465"
X-Mailman-Approved-At: Sat, 17 Sep 2022 08:14:50 +0000
Cc: Buck O Perley <buck.perley@protonmail.com>
Subject: Re: [bitcoin-dev] On a new community process to specify covenants
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2022 07:53:06 -0000

--000000000000a07b6505e8dac465
Content-Type: text/plain; charset="UTF-8"

On Fri, Sep 16, 2022 at 9:18 PM Antoine Riard via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi Buck,
>
[...]

>
> I would vote against Slack. IRC is probably the best but maybe too high a
> barrier to entry? Publishing logs at least would counter concerns of it
> being exclusive. Maybe discord as an alternative.
>
> I would say I really like IRC too. The strong text-based format, the lack
> of avatar emoji, the low-bar to participate pseudonymously, the leveling
> field for non-native speakers contrary to audio and the easiness to grab
> the mics, all features valuable for such a process I think.
>
> If IRC is still considered a technical high-bar for a standard
> communication organ by many community stakeholders, discord is an
> alternative.
>

I would rule out Discord, since it requires phone numbers.  It doesn't
require them for every user, but it's based on some risk measurement.  The
phone flow is probably more likely to be triggered by VPN / Tor.

--000000000000a07b6505e8dac465
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Sep 16, 2022 at 9:18 PM Antoi=
ne Riard via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Buck,<b=
r></div></blockquote><div>[...] <br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><br>I would vote against Slack. IRC is pr=
obably the best but maybe too high a barrier to entry? Publishing logs at l=
east would counter concerns of it being exclusive. Maybe discord as an alte=
rnative.<br><br>I would say I really like IRC too. The strong text-based fo=
rmat, the lack of avatar emoji, the low-bar to participate pseudonymously, =
the leveling field for non-native speakers contrary to audio and the easine=
ss to grab the mics, all features valuable for such a process I think.<br><=
br>If IRC is still considered a technical high-bar for a standard communica=
tion organ by many community stakeholders, discord is an alternative.<br></=
div></blockquote><div><br></div><div>I would rule out Discord, since it req=
uires phone numbers.=C2=A0 It doesn&#39;t require them for every user, but =
it&#39;s based on some risk measurement.=C2=A0 The phone flow is probably m=
ore likely to be triggered by VPN / Tor.</div><div><br></div></div></div>

--000000000000a07b6505e8dac465--