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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <nanotube@gmail.com>) id 1RzJ3T-0006de-VV
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 02:32:44 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=nanotube@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RzJ3T-0001x0-4g
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Feb 2012 02:32:43 +0000
Received: by vbbff1 with SMTP id ff1so5024813vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 19 Feb 2012 18:32:37 -0800 (PST)
Received-SPF: pass (google.com: domain of nanotube@gmail.com designates
10.52.173.230 as permitted sender) client-ip=10.52.173.230;
Authentication-Results: mr.google.com;
spf=pass (google.com: domain of nanotube@gmail.com
designates 10.52.173.230 as permitted sender)
smtp.mail=nanotube@gmail.com;
dkim=pass header.i=nanotube@gmail.com
Received: from mr.google.com ([10.52.173.230])
by 10.52.173.230 with SMTP id bn6mr8753588vdc.19.1329705157797
(num_hops = 1); Sun, 19 Feb 2012 18:32:37 -0800 (PST)
Received: by 10.52.173.230 with SMTP id bn6mr7080612vdc.19.1329705157749;
Sun, 19 Feb 2012 18:32:37 -0800 (PST)
Received: from [192.168.2.102] (c-68-80-166-130.hsd1.nj.comcast.net.
[68.80.166.130]) by mx.google.com with ESMTPS id
bj13sm12562717vdc.15.2012.02.19.18.32.36
(version=SSLv3 cipher=OTHER); Sun, 19 Feb 2012 18:32:36 -0800 (PST)
Message-ID: <4F41B0C2.5000209@gmail.com>
Date: Sun, 19 Feb 2012 21:32:34 -0500
From: Daniel F <nanotube@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <15A9E3BE-3288-4CDC-8243-05669298CDB0@ceptacle.com>
<CAD2Ti2_QDX-tFZFsweLU=5AptzxhAs-d2euJ+kWHnL3Kh6rzvA@mail.gmail.com>
<4F417E76.30001@gmail.com>
<CAD2Ti2-KxefhJHJXozfS7wCnMmmsbscA9ne05aTqdwW-ZcJmUg@mail.gmail.com>
In-Reply-To: <CAD2Ti2-KxefhJHJXozfS7wCnMmmsbscA9ne05aTqdwW-ZcJmUg@mail.gmail.com>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(nanotube[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1RzJ3T-0001x0-4g
Subject: Re: [Bitcoin-development] off-topic: bitcoin-forum...
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 02:32:44 -0000
on 02/19/2012 07:13 PM grarpamp said the following:
>> Some time ago i started a googlegroup mailing list, bitcoin-discussion.
>> It's been pretty low-volume... but it's something. :)
>> http://groups.google.com/group/bitcoin-discussion
>
> Unfortunately it appears to be just as dead as the one
> on sourceforge.
That's exactly what i said above, in a more euphemistic fashion :D
> Well there's a couple things I see...
>
> 1) Yes, IMO, a real mailing list for users needs to exist.
> Among the prior reasons... lists tend to house a more
> technical crowd than forums which are magnets for
> initiates.
indeed.
> 2) There was originally one client. Now there are many,
> all adherant to the same bitcoin spec. So while:
> bitcoin-development@lists.sourceforge.net
> represents the dev community for the original client,
> it may not, or won't be, for any other client.
> And as:
> bitcoin-list@lists.sourceforge.net
> was for, and is administratively tied to, the original client...
> it may not be the place, or a welcome one, to hold talk of all
> the adherant clients.
i'm sure that with the list being unused, we could change the charter
and do whatever with it, and the people who matter probably won't object.
> 3) The sourceforge list browsing interface is ridiculously
> lame and overweight, and it doesn't appear to be setting
> a '^Reply-to: ' header which is bad. Googlegroups would
> be an ok site I suppose. And a pure MailMan interface would
> be even better and more customarily accepted.
Indeed, good points on all counts.
> So for the user list, I'd suggest:
> 1) Search a bit to make sure there's not already a busy list
> out there somewhere. Check the list aggregator sites
> like markmail, gmane, etc too.
> 2) Charter it as bitcoin protocol, client agnostic.
> 3) Find an impartial administrative and robust home for the list
> with browsable, searchable and hopefully downloadable archives.
> 4) Make the announcement to other known client lists/forums.
> 5) Close any relevant old lists.
> 6) Promote via similar announcement from time to time.
good points. re 1), i'm pretty sure that -dev is the most active
bitcoin-related public mailing list. things may have changed in the past
half-year, but it seems unlikely.
> http://groups.google.com/group/bitcoin-discussion/about
> Description: A place for discussion related to bitcoin.
>
> Is this sufficient charter to go with? Is the creator/maintainer
> known impartial? What happens to ongoing list operations when
> said people vanish? It is presumed googlegroups itself is robust.
charter can be changed if needed. creator/maintainer, that being me, is
generally known to be a pretty decent guy :). i'm not attached to this
particular list though, but whatever happens, i'd hope that there will
be more people willing to share administrative duties. not sure if
googlegroups is the best interface, if we can find some good free host
with mailman, downloadable archives, the works, that may be preferable.
i started that group on gg simply because it was free and easily
available and easy to set up.
|
