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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1VplbU-0004KY-L8
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 21:09:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.173 as permitted sender)
client-ip=209.85.192.173; envelope-from=gmaxwell@gmail.com;
helo=mail-pd0-f173.google.com;
Received: from mail-pd0-f173.google.com ([209.85.192.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VplbT-0003uP-SY
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 21:09:28 +0000
Received: by mail-pd0-f173.google.com with SMTP id p10so3964659pdj.18
for <bitcoin-development@lists.sourceforge.net>;
Sun, 08 Dec 2013 13:09:22 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.66.170.138 with SMTP id am10mr17098784pac.51.1386536961960;
Sun, 08 Dec 2013 13:09:21 -0800 (PST)
Received: by 10.70.81.170 with HTTP; Sun, 8 Dec 2013 13:09:21 -0800 (PST)
In-Reply-To: <CANAnSg3GeLPyXXK5Osg1hcC7MQ=Na3BWrGCe95ab7UcbeG2Jgw@mail.gmail.com>
References: <52A3C8A5.7010606@gmail.com>
<1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net>
<52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org>
<CANAnSg2OrmQAcZ+cZdtQeADicH3U29QOgYPfP1AQhOMP6+P1wg@mail.gmail.com>
<CAAS2fgR0khyJxmz9c2Oc87hOFgiNuiPJuaeugGajdo_EcKEW9w@mail.gmail.com>
<CANEZrP3+AowZZS1=hAkx0KODiT-vbcRKyZaHOE2CWaJk3y5-Dw@mail.gmail.com>
<CAAS2fgT2x3iLnRiLabPT28eO6rbGuBBgi2s-Yhtgwo+3XWq7+Q@mail.gmail.com>
<CANAnSg3GeLPyXXK5Osg1hcC7MQ=Na3BWrGCe95ab7UcbeG2Jgw@mail.gmail.com>
Date: Sun, 8 Dec 2013 13:09:21 -0800
Message-ID: <CAAS2fgS7=FbX6Si+vfHYL9jtwBm0ipSjsBy3PwJ5zQuYxEkPqg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Drak <drak@zikula.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.173 listed in list.dnswl.org]
-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
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: zikula.org]
-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: 1VplbT-0003uP-SY
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
your thoughts?
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: Sun, 08 Dec 2013 21:09:28 -0000
On Sun, Dec 8, 2013 at 12:51 PM, Drak <drak@zikula.org> wrote:
> What do you suggest though? We will need to trust someone (even in a group
> each person can act autonomously).
> The only thing I can suggest would be to hand the keys to the bitcoin
> project lead.
>
> Otherwise, who has admin rights to the code projects
> (github/sourceforge/this mailing list)? Those people have proven they can be
> trusted so far.
My concern isn't a matter of trustworthyness, it's a matter of too
many eggs in one basket (especially a basket with potentially poor
jurisdictional locality). The current control of the domain has
proven reasonably trustworthy, and if there is a concern for funding
our own server stuff that can be easily handled (e.g. if need be, I'd
pay for it myself, without being in control of it).
Also, in terms of effective lobbying/advocacy I worry that the
foundation would be unable to do an effective job if its saddled with
the belief that its in control of Bitcoin ("Why don't you just make
every transaction {...}": the answer is because its a decentralized
system and no one can unilaterally change it in ways its users would
hate, but it becomes complicated. It's crisper when its clear that
diverse and independant parties are in control of the popular
infrastructure).
|