Add an option to use "bits" as a unit of account. The average user will have a difficult time understanding "μBTC", let alone pronounce it properly.
http://en.wikipedia.org/wiki/Bit_(money) The word bit is a colloquial expression referring to specific coins in various coinages throughout the world.
NACK, if you can't handle SI, use a sane unit system like Tonal... (also, the patch is inconsistent)
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/508ffac983f8fe9b48c57a53fa87786ed22ce12a for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
This certainly requires discussion on the mailing list first. If there's community consensus about this, sure, but let's try to keep uniform terminology across clients.
a wider-community consensus seems to be formed on reddit. As this is about end-user visible text, I do value that non-technical contribution of opinion. Hope it may cause some core-devs to look at this more in-depth too :)
See http://www.reddit.com/r/Bitcoin/comments/23flcn/bits_instead_of_%CE%BCbtc/
Please start a thread on the mailing list about this if you want different client developers to weigh in. Introducing something like this in just one client without communication with others is a bad idea.
Discussion thread started: https://sourceforge.net/p/bitcoin/mailman/message/32247013/
I apologize if submitting a code change was improper.
NACK.
SI units are international and well-rooted in other areas. Bits are not, they denote storage capacity.
I'm fine with using 'bits' colloquially but this is up to the community to decide not developers. Colloquial names are never formally used.
This also introduce a duplicate unit which is pointless... at most it would be an alias for micro-BTC.
SI units are international and well-rooted in other areas. Bits are not, they denote storage capacity.
I wish you would be a bit more open for discussion instead of concluding this. The logic is actually not as simple as you make it out to be. First of all; the idea that SI units are well rooted is not reflected by the real world. Try to order a 500gram piece of meat in a shop in the USA. Brits are also not that well versed in the metric system. Let alone the SI extension to that. Its not the job of bitcoin to educate about SI, instead we have to make due with what people understand.
I'm fine with using 'bits' colloquially but this is up to the community to decide not developers. Colloquial names are never formally used.
I understand that you, as a software developer, make the connection of "bits" to bytes/storage etc. This is unfortunate, but luckaly the vast majority of intended users won't be wired that way. :) Hope you can see the distinction and joke about it, as this is for sure not meant to insult in any way. The point is that "bits" is a play on "bitcoin". Only computer techies will make a connection with bytes, the rest of the people (see the reddit thead) will most likely see the intended connection which is that "bits" the small version of "Bitcoin".
This also introduce a duplicate unit which is pointless... at most it would be an alias for micro-BTC. I agree, I would personally remove uBtc.
I'm hoping this request doesn't have to be closed so fast, after all a HUGE amount of end users have been stating that the uBtc version is just too hard to use (again, see reddit links). Please don't ignore them by stating they are stupid and should learn SI.
@zander In shops, people use colloquial terms. That's how language works. People use whatever words they find funny and in common use. If you want to pay '10000 bits' in a shop that's fine.
On the other hand in a formal setting, colloquial units are never used. A bank web site won't give you '1000 bucks' or other slang terms.
I understand that you, as a software developer, make the connection of "bits" to bytes/storage etc. This is unfortunate, but luckaly the vast majority of intended users won't be wired that way.
I don't disagree with anything here. I just don't think this discussion belongs with the software.