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 ) 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 ; 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: References: <4E68D968.1080604@gmail.com> <20110908162014.GA7513@ulyssis.org> Date: Thu, 8 Sep 2011 18:51:02 +0200 X-Google-Sender-Auth: O2Jnqmd3D6h5CQSAo31W_l7GY1Y Message-ID: From: Mike Hearn To: John Smith 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 Subject: Re: [Bitcoin-development] Alert System X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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.

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.

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.
--bcaec547cc2db20e7704ac70dd7c--