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 ) 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 ; 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: <201109081315.12643.luke@dashjr.org> Date: Thu, 8 Sep 2011 17:33:15 +0000 Message-ID: From: John Smith To: Luke-Jr 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 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 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 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
Be careful though, if you relay everything, it suddenly *does* have DDo= S 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<= br> > relies on people upgrading for stability, scalability and to enable ne= w
> 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 z= ero
> 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) me= ssages
*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--