Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread D.H.
Then forget the hardcoding of https the hardcoding of bitcoin-alias and ?handle= and the original email-looking gen...@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

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread D.H.
Sure, send it to david.bitcoin.se. That's not a valid URI. I'm not sure I get your point. If someone tells you hey, check out the web page at xkcd.com, is that your response or do you just open up your web browser and type xkcd.com? D.H.

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Jorge Timón
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

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Rick Wesson
I was looking at the wiki entry for this and noticed that your description of DNSSEC is incorrect. It is an internet standard and is widely deployed in the root (.), many TLDs, ccTLDs and second leverl domains. Also understand when the IETF or ICANN adopts new (we worked on DNSSEC no less than 10

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Luke-Jr
On Wednesday, December 14, 2011 6:02:25 PM Rick Wesson wrote: I also am largely in favor of using secured zones to publish TXT records to digital currencies. I've been thinking mainly about TXT using the following format for bitcoin. _btc.lhs.rhs Don't confuse BTC (Bitcoin unit) with BC

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Rick Wesson
understand that not *everyone* wants or will adhere to that best practice and in my NSHO it isn't. -rick 2011/12/14 Luke-Jr l...@dashjr.org: On Wednesday, December 14, 2011 6:02:25 PM Rick Wesson wrote: I also am largely in favor of using secured zones to publish TXT records to digital

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Zell Faze
Could we combine this proposal and the HTTPS proposal? The DNSSEC TXT record could give instructions on how to query an HTTPS server to get the address. Then we get the dynamism of HTTPS without having a rigid URL scheme for querying the server along with the advantages of DNSSEC. --- On

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Zell Faze
It is a lot easier to set up an HTTP server to dynamically respond with addresses than a DNS record.  It is considered a good practice to use a different address for every payment. It stopped being just a website a long time ago. For many of us, most of us, Wikipedia

Re: [Bitcoin-development] Fwd: [BIP 15] Aliases

2011-12-14 Thread Walter Stanish
Just so we're clear, what is the need for HTTP at all? A query for a string and an answer can all be handled via DNS. It is a lot easier to set up an HTTP server to dynamically respond with addresses than a DNS record. Interesting that you bring up the effort factor. The notion that every