public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: David Perry <enmaku@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Alert System
Date: Thu, 8 Sep 2011 09:09:12 -0700	[thread overview]
Message-ID: <CAK5y1FhyCCwL+w4Uo6Xht9BFkZiAmNCeywACnx=eQa6f2iFP2Q@mail.gmail.com> (raw)
In-Reply-To: <4E68D968.1080604@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

@Steve re "Who knows, it might be the only way we'll ever hear from Satoshi
again."

That brings up a good point... Does anyone aside from Satoshi actually have
the ability to send such an alert? Should we at the very least change the
alert system to give such privileges to current devs and ensure that that if
the missing Mr. Satoshi has had his key compromised we don't see an
authoritative-looking alert come up from a malicious source?

[-- Attachment #2: Type: text/html, Size: 673 bytes --]

  reply	other threads:[~2011-09-08 16:09 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 [this message]
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
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='CAK5y1FhyCCwL+w4Uo6Xht9BFkZiAmNCeywACnx=eQa6f2iFP2Q@mail.gmail.com' \
    --to=enmaku@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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