Are we going to have to whitelist every currency that will exist in the future? At least have a pay: schema so you do pay:bitcoin.com/... or something.
paypal:// ... googlecheckout:// ... etc://
Both paypal and googlecheckout are implemented in one way. It is not a protocol. Only the service's website can handle the request for payment in those currencies. Bitcoin is decentralized. The user can install/associate any service/application to send bitcoins, much like emails using mailto:
Why stop at currencies ? Are we now going to have evernote, dropbox, flickr etc ?
No. Evernote, dropbox and flickr are all services implemented by a single organization each. You could just to use HTTP to link to a flickr profile. Bitcoin is decentralized. It is like a protocol. Each user can have his wallet stored in a different service, or even in his computer. The spec allows a wallet service or an application to add itself as a handler for bitcoin: links. Similar to mailto:, the user can choos…
Its like a protocol but if it was a protocol it could be used by different currencies. Just because it is distributed does not mean it cannot have a URI to identify some metadata about the currency being used.
Maybe because there are many other currencies besides bitcoin, what about ripple, litecoin, etc? Would they alter the standart every time to add one of them?
No. Evernote, dropbox and flickr are all services implemented by a single organization each. You could just to use HTTP to link to a flickr profile. Bitcoin is decentralized. It is like a protocol. Each user can have his wallet stored in a different service, or even in his computer. The spec allows a wallet service or an application to add itself as a handler for bitcoin: links. Similar to mailto:, the user can choos…
Its like a protocol but if it was a protocol it could be used by different currencies. Just because it is distributed does not mean it cannot have a URI to identify some metadata about the currency being used.
> Its like a protocol but if it was a protocol it could be used by
different currencies.
No. Evernote, dropbox and flickr are all services implemented by a single organization each. You could just to use HTTP to link to a flickr profile. Bitcoin is decentralized. It is like a protocol. Each user can have his wallet stored in a different service, or even in his computer. The spec allows a wallet service or an application to add itself as a handler for bitcoin: links. Similar to mailto:, the user can choos…
Its like a protocol but if it was a protocol it could be used by different currencies. Just because it is distributed does not mean it cannot have a URI to identify some metadata about the currency being used.
My point is.. you can have any application or service to handle bitcoin address clicks. You can choose to open your wallet service on any website, or an application which manages your bitcoins stored in your hard disk. It isn't a HTTP link, and there isn't some central web service to transfer bitcoins.
Exactly. Needs another layer of abstraction to handle competing crypto currencies. BTC was the first, but won't be the last.
Something analogous to the way magnet URIs are used as an extensible scheme for peer-to-peer filesharing links? http://en.wikipedia.org/wiki/Magnet_URI_scheme
Right; perhaps it would be better to introduce a generic URI scheme for paying:
Something analogous to the way magnet URIs are used as an extensible scheme for peer-to-peer filesharing links? http://en.wikipedia.org/wiki/Magnet_URI_scheme
Right; perhaps it would be better to introduce a generic URI scheme for paying: pay:?currency=btc&address=1BlaH&amount=1.0
Then you need some standardisation on what 'currency' is anyway, and if you use ISO 4217 you shut out Bitcoin.