From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Thu, 8 Sep 2011 13:15:09 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
	<CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
	<CANEZrP2sbLc-ATpf7Uu1S6UQfhd2LPPoHRJmvjZuzH2CUS-TqQ@mail.gmail.com>
In-Reply-To: <CANEZrP2sbLc-ATpf7Uu1S6UQfhd2LPPoHRJmvjZuzH2CUS-TqQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201109081315.12643.luke@dashjr.org>
Cc: David Perry <enmaku@gmail.com>
Subject: Re: [Bitcoin-development] Alert System
Precedence: list

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.