it would be better and easier to do this instead
bitcoin://public key
bitcoin://send/amount/public key
bitcoin://about
then the browser would pass that off to the default program. then you only need to mess with bitcoin instead of html.
Topic: Machine-detectable way to give a bitcoin address in an HTML page - page 2. (Read 2378 times)
One of the tough things we need to improve for everyday use of bitcoin is how to remember, share and input bitcoin addresses. You can't give your bitcoin address as easily as you give your email address.
To address this issue, a couple of wonderful bitcoin address shortening services, such as FirstBits and payb.tc, started to appear. They're actually so useful that bitcoin handling tools (e.g. the original client, a mobile phone app, etc.) would highly benefit from integrating them wherever a bitcoin address is expected. The interface would go, e.g.: "Pay to: payb.tc/da".
Obviously, it wouldn't be safe to be hard-bound to one specific shortening service, so we need to be able to parse any random HTML page and extract the bitcoin address it contains. Where interactive use is possible, such programs would optionally handle the case where there are several addresses, and let the user choose one from a list.
I long ago suggested a -based way to do it, and I still think it would work well, as well as be easy to implement:
(Well, PIF isn't there anymore, but I just copied and paste my former example.)
As someone said later in the same thread, it's very similar to how OpenID does it.
It would be great if address-shortening services, and generally other services that return bitcoin addresses would use this approach (or a similar one). What do you think?
To address this issue, a couple of wonderful bitcoin address shortening services, such as FirstBits and payb.tc, started to appear. They're actually so useful that bitcoin handling tools (e.g. the original client, a mobile phone app, etc.) would highly benefit from integrating them wherever a bitcoin address is expected. The interface would go, e.g.: "Pay to: payb.tc/da".
Obviously, it wouldn't be safe to be hard-bound to one specific shortening service, so we need to be able to parse any random HTML page and extract the bitcoin address it contains. Where interactive use is possible, such programs would optionally handle the case where there are several addresses, and let the user choose one from a list.
I long ago suggested a -based way to do it, and I still think it would work well, as well as be easy to implement:
Code:
As someone said later in the same thread, it's very similar to how OpenID does it.
It would be great if address-shortening services, and generally other services that return bitcoin addresses would use this approach (or a similar one). What do you think?
Jump to: