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
|
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 <witchspace81@gmail.com>) id 1R1iTZ-0005UL-RX
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 17:33:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com;
helo=mail-yx0-f175.google.com;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1R1iTZ-0001Rh-5e
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 17:33:21 +0000
Received: by yxj17 with SMTP id 17so1062194yxj.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 08 Sep 2011 10:33:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.148.6 with SMTP id a6mr1189312ybo.178.1315503195711; Thu,
08 Sep 2011 10:33:15 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Thu, 8 Sep 2011 10:33:15 -0700 (PDT)
In-Reply-To: <201109081315.12643.luke@dashjr.org>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
<CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
<CANEZrP2sbLc-ATpf7Uu1S6UQfhd2LPPoHRJmvjZuzH2CUS-TqQ@mail.gmail.com>
<201109081315.12643.luke@dashjr.org>
Date: Thu, 8 Sep 2011 17:33:15 +0000
Message-ID: <CAJNQ0ss2fkmps32uPAD3ALLmo1JKaF3cc1Ai_m7VuB5858jNJg@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=00151750ed5cae675604ac7174d8
X-Spam-Score: -0.5 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R1iTZ-0001Rh-5e
Cc: bitcoin-development@lists.sourceforge.net, David Perry <enmaku@gmail.com>
Subject: Re: [Bitcoin-development] Alert System
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: Thu, 08 Sep 2011 17:33:21 -0000
--00151750ed5cae675604ac7174d8
Content-Type: text/plain; charset=ISO-8859-1
Be careful though, if you relay everything, it suddenly *does* have DDoS
potential...
JS
On Thu, Sep 8, 2011 at 5:15 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Thursday, September 08, 2011 12:51:02 PM Mike Hearn wrote:
> > Bitcoin is one of the few pieces of software I use that has no concept of
> > automatic updates or even notifications at all. Yet the network badly
> > relies on people upgrading for stability, scalability and to enable new
> > features.
> >
> > If the alert system goes away, it'd just end up being replaced by polling
> > something over HTTP, which is less decentralized than before. Having zero
> > way to communicate upgrades to end-users is a non-starter for anything
> > serious about mass market penetration.
>
> In fact, I think the alert system should relay (note, NOT display) messages
> *regardless of the key used*, so it isn't yet another "our client gets
> special
> status" thing, and can be used for other clients as well.
>
--00151750ed5cae675604ac7174d8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br>Be careful though, if you relay everything, it suddenly *does* have DDo=
S potential...<br><br>JS<br><br><br><div class=3D"gmail_quote">On Thu, Sep =
8, 2011 at 5:15 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"mailto:luke@da=
shjr.org">luke@dashjr.org</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On Thursday, September 08=
, 2011 12:51:02 PM Mike Hearn wrote:<br>
> Bitcoin is one of the few pieces of software I use that has no concept=
of<br>
> automatic updates or even notifications at all. Yet the network badly<=
br>
> relies on people upgrading for stability, scalability and to enable ne=
w<br>
> features.<br>
><br>
> If the alert system goes away, it'd just end up being replaced by =
polling<br>
> something over HTTP, which is less decentralized than before. Having z=
ero<br>
> way to communicate upgrades to end-users is a non-starter for anything=
<br>
> serious about mass market penetration.<br>
<br>
</div>In fact, I think the alert system should relay (note, NOT display) me=
ssages<br>
*regardless of the key used*, so it isn't yet another "our client =
gets special<br>
status" thing, and can be used for other clients as well.<br>
</blockquote></div><br>
--00151750ed5cae675604ac7174d8--
|
