Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vh752-0003Lp-HH for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:16:12 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Vh74z-0005BJ-7n for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:16:11 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:be5f:f4ff:febf:4f76]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 23BFC1080833; Fri, 15 Nov 2013 00:16:11 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Fri, 15 Nov 2013 00:15:58 +0000 User-Agent: KMail/1.13.7 (Linux/3.12.0; KDE/4.10.5; x86_64; ; ) References: <201311142301.39550.luke@dashjr.org> <5285589E.10707@monetize.io> In-Reply-To: <5285589E.10707@monetize.io> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201311150015.59537.luke@dashjr.org> X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_FILL_THIS_FORM_SHORT Fill in a short form with personal information X-Headers-End: 1Vh74z-0005BJ-7n Subject: Re: [Bitcoin-development] moving the default display to mbtc 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, 15 Nov 2013 00:16:14 -0000 On Thursday, November 14, 2013 11:11:26 PM Mark Friedenbach wrote: > On 11/14/13 3:01 PM, Luke-Jr wrote: > > I think we all know the problems with the term "address". People > > naturally compare it to postal addresses, email addresses, etc, > > which operate fundamentally different. I suggest that we switch to > > using "invoice id" to refer to what is now known as addresses, as > > that seems to get the more natural understanding to people. On the > > other hand, with the advent of the payment protocol, perhaps > > address/invoice id use will die out soon? > > > > Thoughts? > > "key id" (thanks sipa). To be clear, I wasn't suggesting renaming scriptPubKey, which sipa was talking about with "key id"; just the destination-for-transaction presented to end-users.