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
|
Return-Path: <jb55@jb55.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id E3B61C0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 9 Nov 2023 04:10:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id BFD3F60ECB
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 9 Nov 2023 04:10:01 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org BFD3F60ECB
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 3.208
X-Spam-Level: ***
X-Spam-Status: No, score=3.208 tagged_above=-999 required=5
tests=[BAYES_05=-0.5, RCVD_IN_SBL_CSS=3.335, RCVD_IN_XBL=0.375,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id b2eK1UX3PhMg
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 9 Nov 2023 04:10:01 +0000 (UTC)
X-Greylist: delayed 399 seconds by postgrey-1.37 at util1.osuosl.org;
Thu, 09 Nov 2023 04:10:00 UTC
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org CC4CC60E5D
Received: from jb55.com (jb55.com [IPv6:2600:3c01::f03c:91ff:fe08:5bfb])
by smtp3.osuosl.org (Postfix) with ESMTPS id CC4CC60E5D;
Thu, 9 Nov 2023 04:10:00 +0000 (UTC)
Received: from jb55.com (58x156x3x227.ap58.ftth.ucom.ne.jp [58.156.3.227])
by jb55.com (OpenSMTPD) with ESMTPSA id 2593bee2
(TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO);
Thu, 9 Nov 2023 04:03:19 +0000 (UTC)
Date: Thu, 9 Nov 2023 13:03:12 +0900
From: William Casarin <jb55@jb55.com>
To: Andrew Chow <lists@achow101.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ntl3yxklpw7z7etqhpvwvh2crjtjk3ys6azes4hompryv5xtux@mlcfro55cls5>
References: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
<CAKwYL5ERT0zH=kcpPwqWe2Q2Gtn+Lj5nQF14yzAZ2nhn8AdD6A@mail.gmail.com>
<2099470b-cca4-4fbe-99c3-ee2d2ed20157@achow101.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <2099470b-cca4-4fbe-99c3-ee2d2ed20157@achow101.com>
X-Mailman-Approved-At: Thu, 09 Nov 2023 12:42:08 +0000
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
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: Thu, 09 Nov 2023 04:10:02 -0000
On Tue, Nov 07, 2023 at 06:14:23PM +0000, Andrew Chow via bitcoin-dev wrote:
>Hi Dan,
>
>I don't think nostr would be a suitable replacement for the mailing
>list, although this opinion is biased by the fact that I do not use
>nostr and find it to be uninteresting.
email-like functionality over nostr isn't really explored yet, but it is
something I'm interesting in. So I agree nostr isn't a suitable email
replacement *yet*.
From my limited understanding of how nostr works, it's not clear to me
>how a distributed system that uses message broadcast would work in the
>same way as a mailing list.
My idea was to have a mailing list relay, the only thing missing is To:
and Cc: tags on notes so that the relay can reject notes not destined
for the mailing list
>How would people "subscribe"? How would archives be searched or
>otherwise be available to people who are not on nostr?
You would subscribe by connecting to the relay and pulling down the
notes. your client could cache notes and only pull new ones.
>How do you distinguish and filter between legitimate dev posts
>intended for discussion and random crap and shitposting as shows up on
>social media?
You would need to have metadata on the note that specifies that the note
is destined for that specific mailing list relay (To, Cc, etc). Then the
client sending the message can send it to that specific relay during
note composition. Again, this is different than then current model that
exists with social networking clients designed for blasting your note to
as many people as possible.
>I also don't think that long form text on nostr (or any similar
>platform) can sufficiently replace email. None of these things seem to
>contain a way to have a separate subject line as email does. Subjects
>are immensely important for me as it provides a quick and easy way to
>filter out things I don't care about reading. I don't want to have read
>something in before I can decide that I don't care about reading it.
Subject lines already exist in nostr and are a part of some email-like
clients like https://github.com/unclebob/more-speech . it's just a tag
like every other piece of metadata.
>In general, I strongly prefer email, or a platform that has email as a
>first class user interface, over platforms such as nostr, matrix, or web
>forums. Email is universal - everyone has one and everyone knows how it
>works. It dramatically lowers the barrier of entry. Having to make an
>account somewhere or download some specific client in order to
>participate will simply result in only the most dedicated participating.
>Development in open source must be an open process and the barriers to
>entry should be low.
I definitely prefer email at the moment as well, but it is also a pain
in the ass to run email infra. As someone who runs both email servers
and nostr relays I can say nostr is much more pleasant.
So yeah, it's a bit too early for a nostr replacement, but it's
definitely possible, and you get proper cryptographic identities and
schnorr signed notes which is a bonus. For dealing with spam you could
have a sat entrance fee via lightning. I will start looking into this!
Cheers,
Will
|
