Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RbsDp-000615-Ub for bitcoin-development@lists.sourceforge.net; Sat, 17 Dec 2011 11:14:33 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=timon.elviejo@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RbsDo-0000pR-J8 for bitcoin-development@lists.sourceforge.net; Sat, 17 Dec 2011 11:14:33 +0000 Received: by wgbds1 with SMTP id ds1so6949678wgb.10 for ; Sat, 17 Dec 2011 03:14:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.19.137 with SMTP id f9mr7663475wie.62.1324120465218; Sat, 17 Dec 2011 03:14:25 -0800 (PST) Received: by 10.223.81.79 with HTTP; Sat, 17 Dec 2011 03:14:24 -0800 (PST) In-Reply-To: <201112170132.26201.luke@dashjr.org> References: <201112170132.26201.luke@dashjr.org> Date: Sat, 17 Dec 2011 12:14:24 +0100 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= Cc: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 (timon.elviejo[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header -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 -0.3 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RbsDo-0000pR-J8 Subject: Re: [Bitcoin-development] Pubkey addresses 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: Sat, 17 Dec 2011 11:14:34 -0000 Don't know much about QR codes, but I thought they have a length limitation= . Why jav wants to use not just addresses but firstbits then? "Allow a field "green_address_list" (short "gal") to specify acceptable addresses in Firstbit format directly in the QR code and only use the "green_address_details" mechanism when that starts to get too long to fit comfortably into the QR code" https://bitcointalk.org/index.php?topic=3D32818.msg422789#msg422789 2011/12/17, Luke-Jr : > IMO, we should standardize and support public key addresses. While not id= eal > for humans, because of their length, it's a better fit for large QR Codes > IMO. > > -------------------------------------------------------------------------= ----- > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what i= t > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --=20 Jorge Tim=F3n