summaryrefslogtreecommitdiff
path: root/0e/324bb8ebd2e250ee2b1fe291dce5d434539fa7
blob: 0674a2861018702b191c266021c90549d1279164 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
Return-Path: <kanzure@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 61EA5C0029;
 Sat,  3 Jun 2023 00:07:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 31F3684619;
 Sat,  3 Jun 2023 00:07:10 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 31F3684619
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20221208 header.b=jKiiJIk1
X-Virus-Scanned: amavisd-new at osuosl.org
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, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 7nVmEm8x7n5O; Sat,  3 Jun 2023 00:07:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org C494B845C0
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com
 [IPv6:2a00:1450:4864:20::136])
 by smtp1.osuosl.org (Postfix) with ESMTPS id C494B845C0;
 Sat,  3 Jun 2023 00:07:08 +0000 (UTC)
Received: by mail-lf1-x136.google.com with SMTP id
 2adb3069b0e04-4f50470d77cso3627437e87.0; 
 Fri, 02 Jun 2023 17:07:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1685750826; x=1688342826;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=29Ur7du4BcTuxynfoeT8pFf/nGvCpNKLJJFm/Z+bDuU=;
 b=jKiiJIk1OZ2HYH27r+CNsq4CduJrBy7voAvNP/oNd3AamFOtnztyVGl1GWJGa1U5gt
 nGuMD0r7dUq8Mj0WW6xIuDTCfgqRDlmG56V7oLpRqh5M0f9EaK07n9BAnTznPb/84xEY
 cBAA9ZewcZdiFHWyWSHEcCdgZtNijpz81ZhVdoF7E5AXLQJIxmIisokZ8RuYVwnJp28C
 H6Ujc+9i43n5YQMzO346HrACMpMpItMx5rKrYM/Q1hxId524fjtIYWjuS7pr2zPQv7WJ
 FbnDvY6yX/FfULQaXYwfH3wuzOOW+k5vDVDfDgkTbhsCAU7NKeUB/9M7Jc7NtshIDJ5u
 3/yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1685750826; x=1688342826;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=29Ur7du4BcTuxynfoeT8pFf/nGvCpNKLJJFm/Z+bDuU=;
 b=IIgSwZZdJUN6m4CjequTE0rEA6+RHqnRfSRfffW+LUQCOgk+TEjaR/a8W2qkrudXQl
 PP0pxhnESP2SbM3mjZWk0JSPAA0/t6mPekmegaWqVR1ZEDf0OmBH2xQY825EwNqo4AGG
 Yt1pfAdRpflXDZePzF6dwZZ+uYiHdS897srmH426R9FPmUCa/xcbXGstg9MwdBC5zCMT
 YYW1fOoF8i00zFPxLp2lNhQJ3mWzu+ROusjhUXwwAPAGODtvx8Dzff1GvOkYlkXhc/5E
 SpExZUD8wtZqCp+04xGeYYjwOQpBb9j2axNbHj7zvHrf7PqdgN38o+aidXy89rBBwo7U
 uRnw==
X-Gm-Message-State: AC+VfDw/kwUxtBvwFhT45cJavEgn4J0NYOx4D1xdw0kvcD5hSRZJjY4e
 QNprTqvAzH7l67rDqymhTaexzW++agD2ulTsmb4=
X-Google-Smtp-Source: ACHHUZ6zWW8Gha2YqgoP4PuCGD4ZGEoerGGmBuO5Y5x4wBIAILkWX8SlBU2WD7xQVlw2IbE/o4Uwck5eRwFAyeIS2WM=
X-Received: by 2002:ac2:4856:0:b0:4f4:ce42:e8fb with SMTP id
 22-20020ac24856000000b004f4ce42e8fbmr2550037lfy.4.1685750826011; Fri, 02 Jun
 2023 17:07:06 -0700 (PDT)
MIME-Version: 1.0
References: <eXXv90Zp7BkXLnld8dDksxrZ7tA0rHngfZ2NLwQ3hrt5tBWGmodmDaT7_JzbcyMukDSVSNtbNoV0wxrkFZt29bXW5WyAT6iyL4lFcvlRDI4=@protonmail.com>
In-Reply-To: <eXXv90Zp7BkXLnld8dDksxrZ7tA0rHngfZ2NLwQ3hrt5tBWGmodmDaT7_JzbcyMukDSVSNtbNoV0wxrkFZt29bXW5WyAT6iyL4lFcvlRDI4=@protonmail.com>
From: Bryan Bishop <kanzure@gmail.com>
Date: Fri, 2 Jun 2023 19:06:53 -0500
Message-ID: <CABaSBawHd4C0POxCs5NUA7pAjyz_MR2JmSoCTsC26Kf9H_zEDw@mail.gmail.com>
To: Dr Maxim Orlovsky <orlovsky@protonmail.com>
Content-Type: multipart/alternative; boundary="0000000000002a130b05fd2e7373"
Cc: bitcoin-dev@lists.linuxfoundation.org,
 lightning-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [Lightning-dev] Bitcoin mail list needs an
	explicit moderation policy
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, 03 Jun 2023 00:07:10 -0000

--0000000000002a130b05fd2e7373
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Maxim,

This is exceedingly boring. This is not a good use of your time. There are
thousands of developers subscribed to this mailing list, and we should not
waste their time, including this discussion.

On Fri, Jun 2, 2023 at 6:44=E2=80=AFPM Dr Maxim Orlovsky via Lightning-dev =
<
lightning-dev@lists.linuxfoundation.org> wrote:

> What happened next was very unexpected. I am giving the core of the
> conversation over Twitter after in Annex A - with the purpose to showcase
> the problem I=E2=80=99d like to address in this e-mail. From the discussi=
on, it is
> clear that bitcoin-dev mail list lacks clear explicit moderation (or
> peer-review) policies, which must be applied on a non-selective basis.
> Also, Bryan Bishop, as the current moderator, had abused his powers in
> achieving his agenda based on personal likes or dislikes. The conversatio=
n
> went nowhere, and the post got published only after a requirement from
> Peter Todd [9].
>

What exactly is the abuse being alleged here though? Why would it be
surprising that your tweets didn't get the behavior you wanted out of me?
In general mailing list moderators should not be sending items through
based on twitter mobbing, that's a policy you can consider if you want to
think about policies.

Annex A:
>
>    - @kanzure just like to check that our submission to bitcoin-dev
>    hasn=E2=80=99t got to spam <
>    https://twitter.com/lnp_bp/status/1664649328349069320?s=3D61&t=3D9A8uv=
ggqKVKV3sT4HPlQyg
>    >
>    - A few mods are reviewing it <
>    https://twitter.com/kanzure/status/1664680893548572677?s=3D61&t=3D9A8u=
vggqKVKV3sT4HPlQyg
>    >
>    - Oh, so a peer review is required to get to bitcoin-dev mail list?
>    Never read about that requirement anywhere <
>    https://twitter.com/lnp_bp/status/1664695061462777858?s=3D61&t=3D9A8uv=
ggqKVKV3sT4HPlQyg>.
>    Seems like bitcoin-dev mail list requirements are now specific to the
>    author :) <
>    https://twitter.com/dr_orlovsky/status/1664695668475142144?s=3D61&t=3D=
9A8uvggqKVKV3sT4HPlQyg
>    >
>    - Not the greatest email to pull this over. I'll double check but
>    pretty sure the antagonization is boring me. <
>    https://twitter.com/kanzure/status/1664705038315409420?s=3D61&t=3D9A8u=
vggqKVKV3sT4HPlQyg
>    >
>    - Not sure I understand what you are saying. Can you please clarify? <
>    https://twitter.com/dr_orlovsky/status/1664705280393859103?s=3D61&t=3D=
9A8uvggqKVKV3sT4HPlQyg
>    >
>    - You are boring me and these antics don't make me want to go click
>    approve on your email. <
>    https://twitter.com/kanzure/status/1664705509147004946?s=3D61&t=3D9A8u=
vggqKVKV3sT4HPlQyg
>    >
>
>
Excluding your (and my) other tweets and any other collaborators' tweets
from your report is kind of weird. I think you should include the other
tweets that you were sending me because it provides context. Zooming out,
the entirety of your complaint seems to be about moderation queue latency
and delay. Why would you, or anyone, allege that that moderator latency is
indicative of me specifically not liking you? Wouldn't it be more likely
that the other moderators and I are looking at your email and talking with
each other asynchronously about whether to suggest edits/reject/submit?

I suspect you may be attributing malice to me because I recently asked you
to stop tagging me on quantum woo and you might have taken that negatively
- please keep in mind that not everyone believes in quantum consciousness
or is interested in hearing about it, and it's okay for people like me to
not want to engage on each of your different interests. There is some
overlap in our interests outside of crypto, but that isn't one of them. I
noticed some odd tweets from you to me after that, so that's why that
incident came to my mind as a possible explanation for this.

Thank you.

- Bryan
https://twitter.com/kanzure

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Maxim,<br><br>This is exceedingly bori=
ng. This is not a good use of your time. There are thousands of developers =
subscribed to this mailing list, and we should not waste their time, includ=
ing this discussion.</div><div dir=3D"ltr"><br>On Fri, Jun 2, 2023 at 6:44=
=E2=80=AFPM Dr Maxim Orlovsky via Lightning-dev &lt;<a href=3D"mailto:light=
ning-dev@lists.linuxfoundation.org">lightning-dev@lists.linuxfoundation.org=
</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div> <div dir=3D"auto">What happened next was v=
ery unexpected. I am giving the core of the conversation over Twitter after=
 in Annex A - with the purpose to showcase the problem I=E2=80=99d like to =
address in this e-mail. From the discussion, it is clear that bitcoin-dev m=
ail list lacks clear explicit moderation (or peer-review) policies, which m=
ust be applied on a non-selective basis. Also, Bryan Bishop, as the current=
 moderator, had abused his powers in achieving his agenda based on personal=
 likes or dislikes. The conversation went nowhere, and the post got publish=
ed only after a requirement from Peter Todd [9].<br></div></div></blockquot=
e><div><br>What exactly is the abuse being alleged here though? Why would i=
t be surprising that your tweets didn&#39;t get the behavior you wanted out=
 of me? In general mailing list moderators should not be sending items thro=
ugh based on twitter mobbing, that&#39;s a policy you can consider if you w=
ant to think about policies.</div><div><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div><div dir=3D"auto"><p style=3D"margin:0px;line-=
height:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-t=
ransform:none;white-space:normal;word-spacing:0px;text-decoration:none"><sp=
an>Annex A:</span></p><ul style=3D"list-style-type:&quot;\002014\0000a0\000=
0a0&quot;;letter-spacing:normal;text-align:start;text-indent:0px;text-trans=
form:none;white-space:normal;word-spacing:0px;text-decoration:none"><li sty=
le=3D"margin:0px;line-height:normal"><span></span><span>@kanzure just like =
to check that our submission to bitcoin-dev hasn=E2=80=99t got to spam &lt;=
<a href=3D"https://twitter.com/lnp_bp/status/1664649328349069320?s=3D61&amp=
;t=3D9A8uvggqKVKV3sT4HPlQyg" target=3D"_blank">https://twitter.com/lnp_bp/s=
tatus/1664649328349069320?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&gt;</sp=
an></li><li style=3D"margin:0px;line-height:normal"><span></span><span>A fe=
w mods are reviewing it &lt;<a href=3D"https://twitter.com/kanzure/status/1=
664680893548572677?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg" target=3D"_blank"=
>https://twitter.com/kanzure/status/1664680893548572677?s=3D61&amp;t=3D9A8u=
vggqKVKV3sT4HPlQyg</a>&gt;</span></li><li style=3D"margin:0px;line-height:n=
ormal"><span></span><span>Oh, so a peer review is required to get to bitcoi=
n-dev mail list? Never read about that requirement anywhere &lt;<a href=3D"=
https://twitter.com/lnp_bp/status/1664695061462777858?s=3D61&amp;t=3D9A8uvg=
gqKVKV3sT4HPlQyg" target=3D"_blank">https://twitter.com/lnp_bp/status/16646=
95061462777858?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&gt;. Seems like bi=
tcoin-dev mail list requirements are now specific to the author :) &lt;<a h=
ref=3D"https://twitter.com/dr_orlovsky/status/1664695668475142144?s=3D61&am=
p;t=3D9A8uvggqKVKV3sT4HPlQyg" target=3D"_blank">https://twitter.com/dr_orlo=
vsky/status/1664695668475142144?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&g=
t;</span></li><li style=3D"margin:0px;line-height:normal"><span></span><spa=
n>Not the greatest email to pull this over. I&#39;ll double check but prett=
y sure the antagonization is boring me. &lt;<a href=3D"https://twitter.com/=
kanzure/status/1664705038315409420?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg" t=
arget=3D"_blank">https://twitter.com/kanzure/status/1664705038315409420?s=
=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&gt;</span></li><li style=3D"margin=
:0px;line-height:normal"><span></span><span>Not sure I understand what you =
are saying. Can you please clarify? &lt;<a href=3D"https://twitter.com/dr_o=
rlovsky/status/1664705280393859103?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg" t=
arget=3D"_blank">https://twitter.com/dr_orlovsky/status/1664705280393859103=
?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&gt;</span></li><li style=3D"marg=
in:0px;line-height:normal"><span></span><span>You are boring me and these a=
ntics don&#39;t make me want to go click approve on your email. &lt;<a href=
=3D"https://twitter.com/kanzure/status/1664705509147004946?s=3D61&amp;t=3D9=
A8uvggqKVKV3sT4HPlQyg" target=3D"_blank">https://twitter.com/kanzure/status=
/1664705509147004946?s=3D61&amp;t=3D9A8uvggqKVKV3sT4HPlQyg</a>&gt;</span></=
li></ul></div></div></blockquote><div><br>Excluding your (and my) other twe=
ets and any other collaborators&#39; tweets from your report is kind of wei=
rd. I think you should include the other tweets that you were sending me be=
cause it provides context. Zooming out, the entirety of your complaint seem=
s to be about moderation queue latency and delay.=C2=A0Why would you, or an=
yone, allege that that moderator latency is indicative of me specifically n=
ot liking you? Wouldn&#39;t it be more likely that the other moderators and=
 I are looking at your email and talking with each other asynchronously abo=
ut whether to suggest edits/reject/submit?</div><div><br></div><div>I suspe=
ct you may be attributing malice to me because I recently=C2=A0asked you to=
 stop tagging me on quantum woo and you might have taken that negatively - =
please keep in mind that not everyone believes in quantum consciousness or =
is interested in hearing about it, and it&#39;s okay for people like me to =
not want to engage on each of your different interests. There is some overl=
ap in our interests outside of crypto, but that isn&#39;t one of them. I no=
ticed some odd tweets from you to me after that, so that&#39;s why that inc=
ident came to my mind as a possible explanation for this.</div><div><br></d=
iv><div>Thank you.<br><br></div></div><div dir=3D"ltr" class=3D"gmail_signa=
ture"><div dir=3D"ltr">- Bryan<br><a href=3D"https://twitter.com/kanzure" t=
arget=3D"_blank">https://twitter.com/kanzure</a></div></div></div>

--0000000000002a130b05fd2e7373--