From: John Smith <witchspace81@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net,
David Perry <enmaku@gmail•com>
Subject: Re: [Bitcoin-development] Alert System
Date: Thu, 8 Sep 2011 17:33:15 +0000 [thread overview]
Message-ID: <CAJNQ0ss2fkmps32uPAD3ALLmo1JKaF3cc1Ai_m7VuB5858jNJg@mail.gmail.com> (raw)
In-Reply-To: <201109081315.12643.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
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.
>
[-- Attachment #2: Type: text/html, Size: 1315 bytes --]
next prev parent reply other threads:[~2011-09-08 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 14:42 David Perry
2011-09-08 15:04 ` Steve
2011-09-08 16:09 ` David Perry
2011-09-08 16:16 ` Matt Corallo
2011-09-08 16:20 ` Pieter Wuille
2011-09-08 16:37 ` John Smith
2011-09-08 16:51 ` Mike Hearn
2011-09-08 16:56 ` Alex Waters
2011-09-08 17:15 ` Luke-Jr
2011-09-08 17:33 ` John Smith [this message]
2011-09-08 17:59 ` Luke-Jr
2011-09-08 19:25 ` Will
[not found] ` <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com>
2011-09-09 9:15 ` Christian Decker
2011-09-08 15:20 ` Matt Corallo
2011-09-08 15:25 ` Steve Coughlan
2011-09-08 19:43 ` theymos
2011-09-08 19:45 ` Luke-Jr
2011-09-08 20:17 ` theymos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJNQ0ss2fkmps32uPAD3ALLmo1JKaF3cc1Ai_m7VuB5858jNJg@mail.gmail.com \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=enmaku@gmail$(echo .)com \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox