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 1Rav7d-0004EP-R0 for bitcoin-development@lists.sourceforge.net; Wed, 14 Dec 2011 20:08:13 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Rav7c-00056a-Sn for bitcoin-development@lists.sourceforge.net; Wed, 14 Dec 2011 20:08:13 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id E1C65560535; Wed, 14 Dec 2011 20:08:04 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Wed, 14 Dec 2011 15:07:59 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.6.5; x86_64; ; ) References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> <201112131622.08158.andyparkins@gmail.com> In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112141508.01136.luke@dashjr.org> X-Spam-Score: -2.2 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.3 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rav7c-00056a-Sn Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases 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: Wed, 14 Dec 2011 20:08:13 -0000 On Wednesday, December 14, 2011 2:22:12 PM D.H. wrote: > > Then forget the hardcoding of "https" the hardcoding of "bitcoin-alias" > > and> "?handle=" and the original email-looking "genjix@foo.org". Just > > use the URL.> Then the author of the service can use whatever they want. > > I like this a lot. It's very simple to understand and would be very > easy to implement and set up. > > "Sure, send it to david.bitcoin.se". That's not a valid URI.