From: Steve <shadders.del@gmail.com>
To: David Perry <enmaku@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Alert System
Date: Fri, 09 Sep 2011 01:04:08 +1000 [thread overview]
Message-ID: <4E68D968.1080604@gmail.com> (raw)
In-Reply-To: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2739 bytes --]
I think there's a significant risk to not having it at this stage.
There's many reasons why an urgent update may been to rapidly propagated
in this stage of the network's lifecycle. Perhaps if there's a
perceived threat of abuse the protocol could be altered slightly so it
can't carry content. Only a notification of the fact that there is an
alert. Then it would be up to individual clients whether they react to
it or not. The main clients would probably check a central trusted
server for actual alert content. This would give a lot more flexibility
in how to deal with the alert. Alert content servers could for example
implement a json api to provide alert content with meta data like target
client version, priority etc.
I think it should be removed in the future but not for a good while yet.
On 09/09/11 00:42, David Perry wrote:
> There has been some discussion on the new Bitcoin StackExchange
> <http://bitcoin.stackexchange.com> site lately about the alert
> protocol. A few have suggested that it might carry the potential for
> abuse (spam/DoS) and others have argued that it's merely deprecated.
> In any case, enough have voiced concerns that I've forked
> bitcoin/bitcoin, removed the snippet of code from main.cpp that makes
> the questionable call and submitted a pull request
> <https://github.com/bitcoin/bitcoin/pull/506>. On that pull request it
> was noted by Gavin Andresen that it merited discussion here and some
> kind of consensus should be reached before acting on that pull
> request. It was also mentioned that he thought the feature was still
> more useful than dangerous and that he would argue against.
>
> So I pose the question to you fine fellows: Is the alert system
> valuable, an unnecessary risk or merely a snippet of deprecated code?
> Should it be removed?
>
> Sources:
> http://bitcoin.stackexchange.com/questions/583/what-is-the-alert-system-in-the-bitcoin-protocol-how-does-it-work/590
> http://bitcoin.stackexchange.com/questions/636/is-the-alert-system-still-in-the-main-clients-code-will-it-be-removed/711
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops? How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 4144 bytes --]
next prev parent reply other threads:[~2011-09-08 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 14:42 [Bitcoin-development] Alert System David Perry
2011-09-08 15:04 ` Steve [this message]
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
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=4E68D968.1080604@gmail.com \
--to=shadders.del@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=enmaku@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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