Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1RsIya-0000Tq-14 for bitcoin-development@lists.sourceforge.net; Tue, 31 Jan 2012 19:02:44 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.47 as permitted sender) client-ip=209.85.210.47; envelope-from=laanwj@gmail.com; helo=mail-pz0-f47.google.com; Received: from mail-pz0-f47.google.com ([209.85.210.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RsIyU-0007n7-OV for bitcoin-development@lists.sourceforge.net; Tue, 31 Jan 2012 19:02:43 +0000 Received: by dakj40 with SMTP id j40so250757dak.34 for <bitcoin-development@lists.sourceforge.net>; Tue, 31 Jan 2012 11:02:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.234.7 with SMTP id ua7mr41818866pbc.89.1328036552891; Tue, 31 Jan 2012 11:02:32 -0800 (PST) Received: by 10.143.8.11 with HTTP; Tue, 31 Jan 2012 11:02:32 -0800 (PST) In-Reply-To: <1328034145.2832.11.camel@BMThinkPad.lan.bluematt.me> References: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com> <1328025899.2832.5.camel@BMThinkPad.lan.bluematt.me> <1328034145.2832.11.camel@BMThinkPad.lan.bluematt.me> Date: Tue, 31 Jan 2012 20:02:32 +0100 Message-ID: <CA+s+GJAyNR7+=Dht4uLVjJ5DLLwhyG2aTDuFonu0ABXXCUVBKA@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Matt Corallo <bitcoin-list@bluematt.me> Content-Type: multipart/alternative; boundary=047d7b33d6d6fbde1e04b7d79a98 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 (laanwj[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: 1RsIyU-0007n7-OV Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Tue, 31 Jan 2012 19:02:44 -0000 --047d7b33d6d6fbde1e04b7d79a98 Content-Type: text/plain; charset=UTF-8 On Tue, Jan 31, 2012 at 7:22 PM, Matt Corallo <bitcoin-list@bluematt.me>wrote: > > All that said, I dont think its an ideal solution, depending on the > names of variables to provide information is ugly. If anyone has a > better idea on how to do backward compatibility, please suggest it. > I like the mustimplement: idea, though I'd recommend a shorter (abbreviated) prefix, to keep URL sizes small for QR codes and such, Wladimir --047d7b33d6d6fbde1e04b7d79a98 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <br><div class=3D"gmail_quote">On Tue, Jan 31, 2012 at 7:22 PM, Matt Corall= o <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-list@bluematt.me">bitcoin= -list@bluematt.me</a>></span> wrote:<br><blockquote class=3D"gmail_quote= " style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> All that said, I dont think its an ideal solution, depending on the<br> names of variables to provide information is ugly. =C2=A0If anyone has a<br= > better idea on how to do backward compatibility, please suggest it.<br></bl= ockquote><div><br>I like the mustimplement: idea, though I'd recommend = a shorter (abbreviated) prefix, to keep URL sizes small for QR codes and su= ch,<br> <br> Wladimir<br><br></div></div> --047d7b33d6d6fbde1e04b7d79a98--