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"
Cc: Buck O Perley <buck.perley@protonmail.com>
Subject: Re: [bitcoin-dev] On a new community process to specify covenants
Precedence: list

--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--