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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1R1hoj-0005Dx-38
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 16:51:09 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.53 as permitted sender)
client-ip=209.85.212.53; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f53.google.com;
Received: from mail-vw0-f53.google.com ([209.85.212.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R1hoi-0002hC-Ag
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 16:51:09 +0000
Received: by vws13 with SMTP id 13so117991vws.12
for <bitcoin-development@lists.sourceforge.net>;
Thu, 08 Sep 2011 09:51:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.112.163 with SMTP id ir3mr1034887vdb.124.1315500662590;
Thu, 08 Sep 2011 09:51:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.157.228 with HTTP; Thu, 8 Sep 2011 09:51:02 -0700 (PDT)
In-Reply-To: <CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
<4E68D968.1080604@gmail.com>
<CAK5y1FhyCCwL+w4Uo6Xht9BFkZiAmNCeywACnx=eQa6f2iFP2Q@mail.gmail.com>
<20110908162014.GA7513@ulyssis.org>
<CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
Date: Thu, 8 Sep 2011 18:51:02 +0200
X-Google-Sender-Auth: O2Jnqmd3D6h5CQSAo31W_l7GY1Y
Message-ID: <CANEZrP2sbLc-ATpf7Uu1S6UQfhd2LPPoHRJmvjZuzH2CUS-TqQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: John Smith <witchspace81@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec547cc2db20e7704ac70dd7c
X-Spam-Score: -0.7 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R1hoi-0002hC-Ag
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 16:51:09 -0000
--bcaec547cc2db20e7704ac70dd7c
Content-Type: text/plain; charset=UTF-8
Alert system should be upgraded to pop up a dialog box every 30 minutes
whilst you're using the software.
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.
--bcaec547cc2db20e7704ac70dd7c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Alert system should be upgraded to pop up a dialog box every 30 minutes whi=
lst you're using the software.<div><br></div><div>Bitcoin is one of the=
few pieces of software I use that has no concept of automatic updates or e=
ven notifications at all. Yet the network badly relies on people upgrading =
for stability, scalability and to enable new features.<br>
</div><div><br></div><div>If the alert system goes away, it'd just end =
up being replaced by polling something over HTTP, which is less decentraliz=
ed than before. Having zero way to communicate upgrades to end-users is a n=
on-starter for anything serious about mass market penetration.</div>
--bcaec547cc2db20e7704ac70dd7c--
|
