Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R1xCE-0000hF-Ku for bitcoin-development@lists.sourceforge.net; Fri, 09 Sep 2011 09:16:26 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=decker.christian@gmail.com; helo=mail-wy0-f175.google.com; Received: from mail-wy0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R1xCC-0005KI-9A for bitcoin-development@lists.sourceforge.net; Fri, 09 Sep 2011 09:16:26 +0000 Received: by wyf19 with SMTP id 19so1800930wyf.34 for ; Fri, 09 Sep 2011 02:16:18 -0700 (PDT) Received: by 10.227.121.68 with SMTP id g4mr56585wbr.95.1315559778079; Fri, 09 Sep 2011 02:16:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.55.133 with HTTP; Fri, 9 Sep 2011 02:15:38 -0700 (PDT) In-Reply-To: <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com> References: <201109081315.12643.luke@dashjr.org> <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com> From: Christian Decker Date: Fri, 9 Sep 2011 11:15:38 +0200 Message-ID: To: Bitcoin Development Content-Type: multipart/alternative; boundary=00248c0ef25e40d4bd04ac7ea1b6 X-Spam-Score: -0.6 (/) 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 (decker.christian[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 X-Headers-End: 1R1xCC-0005KI-9A 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: Fri, 09 Sep 2011 09:16:26 -0000 --00248c0ef25e40d4bd04ac7ea1b6 Content-Type: text/plain; charset=ISO-8859-1 Resending to mailing list as I replied directly... On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker < decker.christian@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 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 > >potential... > > > >no more than other messages such as transactions. > Only verified and valid trandactions are forwarded which is desired as it > costs the sender a fee if he attempts to spam, messages have no such > penalty. > > > >>Maybe require a proof-of-work then? > > > >kind of defeats the purpose of the alert if it takes a long time to > >issue > >one. > > > >I think leave the alert in, but relay alert messages even if they don't > >use > >the correct key. This means that if we later decide to add new keys to > >the > >alert root trust then older clients will still relay these. > > > >my .02btc > > > >Will > I'm for keeping it in there as well, maybe even extend it with a mechanism > to sign other certificates giving alternative client developers the ability > to issue their own alerts. Think ssl certificates... > > Regards, > Chris > > >------------------------------------------------------------------------------ > >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 > > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > --00248c0ef25e40d4bd04ac7ea1b6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Resending to mailing list as I replied directly.= ..
On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker &= lt;decker.christian@gmail.com= > wrote:


Will <will@phase.net> wrote:
>> In fact, I think the alert system should relay (note, NOT display)=
>messages
>> *regardless of the key used*, so it isn't yet another "ou= r client
>gets
>> special
>> status" thing, and can be used for other clients as well.
>>
>>
>> Be careful though, if you relay everything, it suddenly *does* hav= e
>DDoS
>potential...
>
>no more than other messages such as transactions.
Only verified and valid trandactions are forwarded which is desired a= s it costs the sender a fee if he attempts to spam, messages have no such p= enalty.
>
>>Maybe require a proof-of-work then?
>
>kind of defeats the purpose of the alert if it takes a long time to
>issue
>one.
>
>I think leave the alert in, but relay alert messages even if they don&#= 39;t
>use
>the correct key. =A0This means that if we later decide to add new keys = to
>the
>alert root trust then older clients will still relay these.
>
>my .02btc
>
>Will
I'm for keeping it in there as well, maybe even extend it with a = mechanism to sign other certificates giving alternative client developers t= he ability to issue their own alerts. Think ssl certificates...

Regards,
Chris
>-------------------------------------= -----------------------------------------
>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? =A0 How do next-generation virtual
>desktops
>provide companies an easier-to-deploy, easier-to-manage and more
>affordable
>virtual desktop
>model.http://www.acc= elacomm.com/jaw/sfnl/114/51426474/_________________________________________= ______
>Bitcoin-development mailing list
>Bitcoin-de= velopment@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoi= n-development

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

--00248c0ef25e40d4bd04ac7ea1b6--