To Bitcoin developers,
Who do you think you are to decide what's good or bad for us?
Why are you treating bitcoiners like a "nanny-government"?
Why do you stall for months patches and features to the reference client that are useful to all of us?
Oh please...Who do you think you are to decide what's good or bad for us?
Why are you treating bitcoiners like a "nanny-government"?
Why do you stall for months patches and features to the reference client that are useful to all of us?
"Oh please", but you didn't address either one...
"coin control / less change / refactor coin selection" - https://github.com/bitcoin/bitcoin/pull/1017
For a popular feature, nobody was willing to take the effort required to address problems with it, until very recently (too late for 0.
. Hopefully it will make it into 0.9.Nice to hear that, didn't know.
"let user select wallet file with -wallet=foo.dat" - https://github.com/bitcoin/bitcoin/pull/1889
Too short-sighted. sipa and CodeShark have been working on true multi-wallet support for a while, and that will hopefully be ready for 0.9.Nice to hear that too, didn't know.
"Addition of Import Private Key Menu" - https://github.com/bitcoin/bitcoin/pull/2050
Too dangerous for easy access - do you really want to enable people coins from newbies? Power users can already import private keys using the debug console.What? Please listen to yourself. The answer is yes, people can and will take care for themselves.
"Add user interface to set dust limit and filtered addresses" - https://github.com/bitcoin/bitcoin/pull/2383
I agree this would be nice (in some form), but the filtering is inevitably a political move to try to force others to stop reusing addresses. While I think that may be necessary, it's arguable whether it belongs in the reference client.Oh no, not again. The feature is there waiting for an approval that never comes. WTF?
I refuse to fork or join or split or whatever. The code is there waiting for what? Main developers mercy?