Live data from Hacker News

Bitcoin URL scheme whitelisted in HTML5

html5.org

21–30 of 60 posts

Re: Bitcoin URL scheme whitelisted in HTML5

#21

What does this mean exactly?

It is referring to the registerProtocolHandler function. The function allows you to register handlers for custom schemes, so that you can do clever things with links like awesome.

The "web+something" namespace is what we should be using for our custom scheme handlers, but there are a bunch of other web-related schemes that will be fine to use too... "bitcoin" is one of the OK ones.

It's not a big deal as far as I can see... basically any scheme that is popular enough or documented enough and isn't supposed to launch some external application could probably get white-listed if you asked nicely.

Re: Bitcoin URL scheme whitelisted in HTML5

#22

"Added to HTML5" is misleading. More specifically, the bitcoin scheme was added as a valid scheme that websites may register themselves as handlers for via navigator.registerProtocolHandler, a list that already includes mms: xmpp: webcal: tel: and other misc schemes. It doesn't specify any kind of support for the scheme for the browser. See http://www.whatwg.org/specs/web-apps/current-work/#whitelist...

[deleted]

Re: Bitcoin URL scheme whitelisted in HTML5

#23

"Added to HTML5" is misleading. More specifically, the bitcoin scheme was added as a valid scheme that websites may register themselves as handlers for via navigator.registerProtocolHandler, a list that already includes mms: xmpp: webcal: tel: and other misc schemes. It doesn't specify any kind of support for the scheme for the browser. See http://www.whatwg.org/specs/web-apps/current-work/#whitelist...

[deleted]

Re: Bitcoin URL scheme whitelisted in HTML5

#24

"Added to HTML5" is misleading. More specifically, the bitcoin scheme was added as a valid scheme that websites may register themselves as handlers for via navigator.registerProtocolHandler, a list that already includes mms: xmpp: webcal: tel: and other misc schemes. It doesn't specify any kind of support for the scheme for the browser. See http://www.whatwg.org/specs/web-apps/current-work/#whitelist...

Yes, I didn’t know how to be more precise while being concise. I replaced the word “added” with “whitelisted”, thanks.

Re: Bitcoin URL scheme whitelisted in HTML5

#25

Earlier quoted context omitted.

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.

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

Re: Bitcoin URL scheme whitelisted in HTML5

#26
post #20

OK, if I understand correctly this is the WHATWG HTML5, not the W3C HTML5. Are there any browsers actually using WHATWG's spec?

Yes, all of them! :-) WhatWG HTML is the living standard, and the HTML5 (W3C) spec. is like a snapshot. http://wiki.whatwg.org/wiki/FAQ#What_is_HTML5.3F

No, it's not that simple.

http://wiki.whatwg.org/wiki/FAQ#WHATWG_and_the_W3C_HTML_WG

Re: Bitcoin URL scheme whitelisted in HTML5

#27

Earlier quoted context omitted.

You have given reasons that support the idea that this is arbitrary, but why is it horrible?

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.

Most scheme designate a protocol not a action.

Do you suggest that we should have the same scheme for HTTP and HTTPS because in the end both return you a resource ?

Same for ssh: and telnet:, same for xmpp:, msnim:, facetime:, irc:, skype:, etc ?

Re: Bitcoin URL scheme whitelisted in HTML5

#28
post #24

"Added to HTML5" is misleading. More specifically, the bitcoin scheme was added as a valid scheme that websites may register themselves as handlers for via navigator.registerProtocolHandler, a list that already includes mms: xmpp: webcal: tel: and other misc schemes. It doesn't specify any kind of support for the scheme for the browser. See http://www.whatwg.org/specs/web-apps/current-work/#whitelist...

Yes, I didn’t know how to be more precise while being concise. I replaced the word “added” with “whitelisted”, thanks.

It should also be made clear that being whitelisted is different from being implemented.

Re: Bitcoin URL scheme whitelisted in HTML5

#29
post #20

Earlier quoted context omitted.

Yes, all of them! :-) WhatWG HTML is the living standard, and the HTML5 (W3C) spec. is like a snapshot. http://wiki.whatwg.org/wiki/FAQ#What_is_HTML5.3F

No, it's not that simple. http://wiki.whatwg.org/wiki/FAQ#WHATWG_and_the_W3C_HTML_WG

Yeah, nothing is simple, but it’s still true most of the time. Feel free to explain better :-)

Re: Bitcoin URL scheme whitelisted in HTML5

#30

Earlier quoted context omitted.

You have given reasons that support the idea that this is arbitrary, but why is it horrible?

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.

Why stop at currencies ?

Are we now going to have evernote, dropbox, flickr etc ?

Post reply on HN