From mboxrd@z Thu Jan 1 00:00:00 1970 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 1RaPlG-0004NZ-NP for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 10:39:02 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.47 as permitted sender) client-ip=209.85.214.47; envelope-from=mh.in.england@gmail.com; helo=mail-bw0-f47.google.com; Received: from mail-bw0-f47.google.com ([209.85.214.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RaPlF-00059w-Ti for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 10:39:02 +0000 Received: by bkbzt4 with SMTP id zt4so9239448bkb.34 for ; Tue, 13 Dec 2011 02:38:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.92.68 with SMTP id ck4mr11798880wib.27.1323772735446; Tue, 13 Dec 2011 02:38:55 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.216.8.7 with HTTP; Tue, 13 Dec 2011 02:38:55 -0800 (PST) In-Reply-To: <201112121602.12806.luke@dashjr.org> References: <201112061610.41083.luke@dashjr.org> <201112101316.31666.luke@dashjr.org> <20111212205559.GA16665@ulyssis.org> <201112121602.12806.luke@dashjr.org> Date: Tue, 13 Dec 2011 11:38:55 +0100 X-Google-Sender-Auth: 6DBdCPzOrokHyXibbeuIu4Dm9u0 Message-ID: From: Mike Hearn To: Luke-Jr Content-Type: multipart/alternative; boundary=f46d043c806ca8de9804b3f6dbf5 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1RaPlF-00059w-Ti Cc: Pieter Wuille , bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Version bytes "2.0" 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: Tue, 13 Dec 2011 10:39:02 -0000 --f46d043c806ca8de9804b3f6dbf5 Content-Type: text/plain; charset=UTF-8 Why does anyone care what an address looks like? If the user is seeing an address, that's a usability fail right there. It's common today because AFAIK nobody finished off the URL handling support in the main client for browser integration. It'd be a much better use of time to finish off that integration and make it easy for people to create links containing a bitcoin: URL (like with copy/paste of text/html content). --f46d043c806ca8de9804b3f6dbf5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Why does anyone care what an address looks like?

If the user is seei= ng an address, that's a usability fail right there. It's common tod= ay because AFAIK nobody finished off the =C2=A0URL handling support in the = main client for browser integration. It'd be a much better use of time = to finish off that integration and make it easy for people to create links = containing a bitcoin: URL (like with copy/paste of text/html content). --f46d043c806ca8de9804b3f6dbf5--