I'm so glad this died, we don't need even more broken implementations of this crap. If someone comes up with a good implementation (and one of the factors will be that PHP won't be among the words used) then I'm all for it. The gambling section is breaking records with crap implementations already, 100x that doesn't help anyone.
Anyway, the coolest thing in this thread is TF talking about how inputs.io is secure and how it is not a scam. Let me save some of that:
You could add api for sites like blockchain or inputs.io
Ew Inputs. That site is so insecure. The owners could steal your BTC any time they want, and you can't export your private keys.
Just don't use a web wallet for anything more than pocket change. For big stuff, use an encrypted desktop client or even an offline cold storage wallet on a Raspberry Pi.
Just like blockchain.info who could have been recording all your passwords that you feed to the API.
Not allowing people to export their private keys
is a good thing because private keys should not be exported or reused for security reasons.
You could have been recording our passwords for all we know. Your site could be a scam for all we know. Maybe you're just waiting until enough people store enough bitcoins to take the money and run? What's stopping you?
No, because your browser hashes your password in the browser, and we don't ask you to send your password for the API (you use your API key which is not your password).