[deleted]
Bitcoin URL scheme whitelisted in HTML5
51–60 of 60 posts
Re: Bitcoin URL scheme whitelisted in HTML5
#52Earlier 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.
Are we going to have to whitelist every currency that will exist in the future?
Why not?
Re: Bitcoin URL scheme whitelisted in HTML5
#53Earlier quoted context omitted.
Care to elaborate?
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?
If those currencies gain traction comparable to Bitcoin, why not? The standard is being changed every day anyway.
Re: Bitcoin URL scheme whitelisted in HTML5
#54Aren't they picking favorites then? I mean what about alternatives like litecoin?
Yes. Favorites like http and not gopher. Litecoin will get whitelisted if it ever becomes important or useful.
If gopher is actually left out I won't be "upgrading" my pages to HTML5. Some of us still use these technologies even if they may not be the latest and greatest.
Re: Bitcoin URL scheme whitelisted in HTML5
#55Everyone who maintains the HTML5 spec. is named Mike.
I remember speculation that "Satoshi" was someone also named Mike. Coincidence?
Re: Bitcoin URL scheme whitelisted in HTML5
#56Earlier quoted context omitted.
Care to elaborate?
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?
I believe they can use "web+litecoin" in the meanwhile. When they'll get enough traction, they may get their designated "top-level" scheme.
Same as with MIME types: application/vnd.org.example.foobar for anyone, application/foobar when you're famous.
Re: Bitcoin URL scheme whitelisted in HTML5
#57Earlier quoted context omitted.
Yes. Favorites like http and not gopher. Litecoin will get whitelisted if it ever becomes important or useful.
If gopher is actually left out I won't be "upgrading" my pages to HTML5. Some of us still use these technologies even if they may not be the latest and greatest.
> Some of us
For very small values of 'some'.
Can you give a couple of (practical!) examples where gopher has not been replaced by http?
Chrome, explorer, opera and safari do not support gopher, and from 4.0 firefox did not support it either (though there is a plug-in).
Re: Bitcoin URL scheme whitelisted in HTML5
#58Earlier quoted context omitted.
Yes. Favorites like http and not gopher. Litecoin will get whitelisted if it ever becomes important or useful.
If gopher is actually left out I won't be "upgrading" my pages to HTML5. Some of us still use these technologies even if they may not be the latest and greatest.
Me too. Also, If the phone company makes it to where I can't use my 2400 baud modem anymore I am canceling my account.
Re: Bitcoin URL scheme whitelisted in HTML5
#59People are way overreacting to this.
HTML already lets arbitrary applications register themselves as protocol handlers at the OS level, so for instance spotify:// links get handled by the correct binary.
All this does is let a website register itself as the handler of a particular protocol. This has obvious uses for instance letting mailto: be handled by Google Mail if the user wants it to be.
I'm not sure why HTML5 has to have a whitelist of protocols that allow websites to register as handlers - it seems like an overhead.
Re: Bitcoin URL scheme whitelisted in HTML5
#60Earlier quoted context omitted.
If gopher is actually left out I won't be "upgrading" my pages to HTML5. Some of us still use these technologies even if they may not be the latest and greatest.
> Some of us For very small values of 'some'. Can you give a couple of (practical!) examples where gopher has not been replaced by http? Chrome, explorer, opera and safari do not support gopher, and from 4.0 firefox did not support it either (though there is a plug-in).
I was speaking for myself rather than making a principled stand; my site still links back to some documents on my old university's system, via gopher. Perhaps there is an http equivalent that new students would use, but if there is then I don't have access to it.