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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <theymos@mm.st>) id 1Vpo8F-0002Hx-Ol
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 23:51:27 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of mm.st
designates 66.111.4.28 as permitted sender)
client-ip=66.111.4.28; envelope-from=theymos@mm.st;
helo=out4-smtp.messagingengine.com;
Received: from out4-smtp.messagingengine.com ([66.111.4.28])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Vpo8E-0004g5-AB
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 23:51:27 +0000
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AF21D20719
for <bitcoin-development@lists.sourceforge.net>;
Sun, 8 Dec 2013 18:51:20 -0500 (EST)
Received: from web6 ([10.202.2.216])
by compute3.internal (MEProxy); Sun, 08 Dec 2013 18:51:20 -0500
Received: by web6.nyi.mail.srv.osa (Postfix, from userid 99)
id 92339291618; Sun, 8 Dec 2013 18:51:20 -0500 (EST)
Message-Id: <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com>
X-Sasl-Enc: twU0rFZT0a3VkNUugMnYQF3ACRpflhq7efEiOzvTIBkI 1386546680
From: theymos <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_1386546680289320";
charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-c99dcdd8
Date: Sun, 08 Dec 2013 17:51:20 -0600
In-Reply-To: <CANAnSg0vwbSyYtzOpbFzaHmS2wQ2aQCibk9tg+G4VA_ESp_7ow@mail.gmail.com>
References: <52A3C8A5.7010606@gmail.com>
<CAAS2fgT2x3iLnRiLabPT28eO6rbGuBBgi2s-Yhtgwo+3XWq7+Q@mail.gmail.com>
<CANAnSg3GeLPyXXK5Osg1hcC7MQ=Na3BWrGCe95ab7UcbeG2Jgw@mail.gmail.com>
<201312082101.25609.luke@dashjr.org>
<CANAnSg0vwbSyYtzOpbFzaHmS2wQ2aQCibk9tg+G4VA_ESp_7ow@mail.gmail.com>
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
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: bitcoin.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
(theymos[at]mm.st)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Vpo8E-0004g5-AB
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 23:51:28 -0000
This is a multi-part message in MIME format.
--_----------=_1386546680289320
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:
It's not just about trust, there is the robustness factor: what if he
becomes sick, unavailable, hit by a bus? Others need the ability to
pickup and run with it. The control over the domain (including ability
to renew registration, alter nameservers) needs to be with more than
one person. That's why I suggest using the same people who have control
over the software project at sf,github
The bitcoin.org domain is controlled by me, Sirius, and an anonymous
person. Control will not be lost if Sirius becomes unavailable.
SSL is probably a good idea, and it's probably also a good idea to
separate bitcoin.org from Github. I don't know that I trust Github. I'm
sure that you can find a sponsor for a dedicated server. Let us know if
DNS changes to bitcoin.org are required.
--_----------=_1386546680289320
Content-Transfer-Encoding: 7bit
Content-Type: text/html
<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div><div><div>It's not just about trust, there is the robustness factor: what if he becomes sick, unavailable, hit by a bus? Others need the ability to pickup and run with it. The control over the domain (including ability to renew registration, alter nameservers) needs to be with more than one person. That's why I suggest using the same people who have control over the software project at sf,github<br></div>
</div>
</div>
</div>
</blockquote><div dir="ltr"><div><div><div> </div>
<div>The bitcoin.org domain is controlled by me, Sirius, and an anonymous person. Control will not be lost if Sirius becomes unavailable.<br></div>
<div> </div>
<div>SSL is probably a good idea, and it's probably also a good idea to separate bitcoin.org from Github. I don't know that I trust Github. I'm sure that you can find a sponsor for a dedicated server. Let us know if DNS changes to bitcoin.org are required.<br></div>
</div>
</div>
</div>
</body>
</html>
--_----------=_1386546680289320--
|
