Resending to mailing list as I replied directly...
On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker <
decker.christ...@gmail.com> wrote:
>
>
> Will wrote:
>
> >> In fact, I think the alert system should relay (note, NOT display)
> >messages
> >> *regardless of the key used*, so it isn't yet anot
> 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.
>
>
> Be careful though, if you relay everything, it suddenly *does* have DDoS
On Thursday, September 08, 2011 3:45 PM, "Luke-Jr" wrote:
> I don't seem to recall this ever happening, despite Deepbit having over 50%
> multiple times now.
An alert would have been issued if they had abused that position.
---
On Thursday, September 08, 2011 3:43:12 PM theymos wrote:
> The alert system will be very important if there are ever any critical
> problems in the network. For example, it is currently Bitcoin's only
> defense against an attacker with >50% of the computational power, where
> alerts would be used
The alert system will be very important if there are ever any critical
problems in the network. For example, it is currently Bitcoin's only
defense against an attacker with >50% of the computational power, where
alerts would be used to tell people to stop accepting transactions.
Displaying a messa
On Thursday, September 08, 2011 1:33:15 PM John Smith wrote:
> Be careful though, if you relay everything, it suddenly *does* have DDoS
> potential...
Maybe require a proof-of-work then?
--
Doing More with Less: The Next
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 up
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.
>
https://github.com/bitcoin/bitcoin/pull/506 has been closed pending
additional commits or a change in consensus.
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented m
Alert system should be upgraded to pop up a dialog box every 30 minutes
whilst you're using the software.
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, scalab
There is a lot of complaining about this alert system, but I really don't
see the problem.
As others have already said, it's just a message. Even if someone managed to
compromise the private key, the most they could do is spam graffiti messages
or try phishing. There are much worse things that cou
On Thu, Sep 08, 2011 at 09:09:12AM -0700, David Perry wrote:
> @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 chan
On Thu, 2011-09-08 at 09:09 -0700, David Perry wrote:
> @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?
Gavin does
> Should we at the very l
@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
Who knows, it might be the only way we'll ever hear from Satoshi again.
On Sep 9, 2011 1:21 AM, "Matt Corallo" wrote:
> On Thu, 2011-09-08 at 07:42 -0700, David Perry wrote:
>> There has been some discussion on the new Bitcoin StackExchange site
>> lately about the alert protocol. A few have sugge
On Thu, 2011-09-08 at 07:42 -0700, David Perry wrote:
> There has been some discussion on the new Bitcoin StackExchange 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
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
17 matches
Mail list logo
