Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Raxg3-0004GN-GK for bitcoin-development@lists.sourceforge.net; Wed, 14 Dec 2011 22:51:55 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; envelope-from=timon.elviejo@gmail.com; helo=mail-ww0-f41.google.com; Received: from mail-ww0-f41.google.com ([74.125.82.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Raxg2-0004lc-PO for bitcoin-development@lists.sourceforge.net; Wed, 14 Dec 2011 22:51:55 +0000 Received: by wgbdt12 with SMTP id dt12so2137782wgb.4 for ; Wed, 14 Dec 2011 14:51:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.0.100 with SMTP id 4mr865265wid.48.1323903108719; Wed, 14 Dec 2011 14:51:48 -0800 (PST) Received: by 10.223.81.79 with HTTP; Wed, 14 Dec 2011 14:51:48 -0800 (PST) In-Reply-To: <1323894080.30850.7.camel@mei> References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> <201112131622.08158.andyparkins@gmail.com> <201112141508.01136.luke@dashjr.org> <1323894080.30850.7.camel@mei> Date: Wed, 14 Dec 2011 23:51:48 +0100 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.2 (-) 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 -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.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Raxg2-0004lc-PO 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 22:51:55 -0000 What if we specify "bitcoin" to make it easier for software (maybe the browser, a plugin for the browser, the bitcoin client analyzing the clipboard...) to easily detect that you expect a bitcoin address when going to url? If puted in the bitcoin client, the "bitcoin://" is optional (? and can also be replaced by http ?) since from the context you already expect an address or an url that will give you the address. In the browser: bitcoin://address bitcoin://rest_of_url In the bitcoin client: address rest_of_url bitcoin://address bitcoin://rest_of_url http://rest_of_url ?? Maybe in the bitcoin client you can put any site and the client downloads the web to look for occurrences of "bitcoin://" (? or just valid addresses ?) in it. It caches and shows them to you to decide what to do with each one. I have used other programs (jdownloader) that read the clipboard looking for patterns in links and is very convenient. Maybe then parameters for the client can be added to this. bitcoin://address?amount=10.53 bitcoin://rest_of_url?amount=10.53&green_address=r bitcoin://rest_of_url?amount=10.53&green_address=r&green_address_list=address1,address2,address3 Whatever the community have planned for bitcoin URIs.