Topic: [POLL 3/3] Bitcoin: URI refactor? Units (poll reset Apr 21 to clarify options) (Read 4809 times)
May 09, 2011, 11:27:40 AM
This poll is useless, there is no option for "decimal satoshis only for all API work".
April 20, 2011, 09:20:14 PM
URIs are not meant to be read by humans, so people being "familiar" with all possibilities is irrelevant.
Why do you even care what is supported, then?Quote
2. You assume a glim future where people still use not only decimal, but BTC. This is not even rationally possible: people will either use mBTC, TBC, or Bitcoin will fail outright.
Everyone will at least understand decimal for the next 100 years. Everyone will understand what an original BTC represents for as long as Bitcoin exists.Quote
You imply supporting hexadecimal is difficult.
It's a waste of time. April 20, 2011, 09:15:16 PM
URIs are not meant to be read by humans, so people being "familiar" with all possibilities is irrelevant.
Why do you even care what is supported, then?
Quote
2. You assume a glim future where people still use not only decimal, but BTC. This is not even rationally possible: people will either use mBTC, TBC, or Bitcoin will fail outright.
Everyone will at least understand decimal for the next 100 years. Everyone will understand what an original BTC represents for as long as Bitcoin exists.
Quote
You imply supporting hexadecimal is difficult.
It's a waste of time.
April 20, 2011, 09:10:42 PM
You're using emotionally-charged words in the poll. Few people will vote for "forcing" anyone to do anything. Maybe the options should be changed to:
1. URIs are not meant to be read by humans, so people being "familiar" with all possibilities is irrelevant.- Accept only normal decimal BTC amounts that everyone is guaranteed to be familiar with now and forever
- Force developers of Bitcoin URI software to support hexadecimal values on the slim chance that one of the few people who deal in hexadecimal wants to edit a Bitcoin URI manually
- Accept hexadecimal and yet another rarely-used number base, forcing developers to do even more work.
2. You assume a glim future where people still use not only decimal, but BTC. This is not even rationally possible: people will either use mBTC, TBC, or Bitcoin will fail outright.
3. You imply supporting hexadecimal is difficult.
4. Dozenal has a rather large userbase too.
April 20, 2011, 09:07:41 PM
You're using emotionally-charged words in the poll. Few people will vote for "forcing" anyone to do anything. Maybe the options should be changed to:
- Accept only normal decimal BTC amounts that everyone is guaranteed to be familiar with now and forever
- Force developers of Bitcoin URI software to support hexadecimal values on the slim chance that one of the few people who deal in hexadecimal wants to edit a Bitcoin URI manually
- Accept hexadecimal and yet another rarely-used number base, forcing developers to do even more work.
April 20, 2011, 09:03:44 PM
This poll is biased and therefore meaningless.
+1 ...
April 20, 2011, 09:03:01 PM
Objectively, the decimal-only option isn't rational, so the meaning of this poll remains: to show how bigoted the people on this forum are.
April 20, 2011, 09:01:00 PM
This poll is biased and therefore meaningless.
April 20, 2011, 08:41:12 PM
This poll is biased and therefore meaningless. 
Is not April 20, 2011, 08:38:43 PM
This poll is biased and therefore meaningless.
April 20, 2011, 08:32:14 PM
Should Bitcoin: URIs be allowed to contain only decimal bitcoins (BTC), or tolerate the human's choice of BTC or TBC (converted first to hexadecimal)?
Please note that even if hexadecimal is supported, nobody is required to use it. It remains the user's choice which number system they use. Even if you open a URI encoded in hexadecimal, you will see the Decimal/BTC equivalent in your client (unless you configure it for TBC). In other words, a vote for decimal-only is a vote to force humans who want to use tonal to switch to decimal.
If you want to request/bill for 10.25 BTC, you (or your shopping cart) would write:
If you want to request/bill for 1.5 mBTC (milli-BTC), you (or your shopping cart) would write:
If you want to request/bill for 10.2 TBC (TonalBitcoin), you (or your shopping cart) would write:
If you want to request/bill for 1 ᵐTBC (mill-TonalBitcoin), you (or your shopping cart) would write:
Please note that even if hexadecimal is supported, nobody is required to use it. It remains the user's choice which number system they use. Even if you open a URI encoded in hexadecimal, you will see the Decimal/BTC equivalent in your client (unless you configure it for TBC). In other words, a vote for decimal-only is a vote to force humans who want to use tonal to switch to decimal.
If you want to request/bill for 10.25 BTC, you (or your shopping cart) would write:
- Decimal only: bitcoin:youraddress?amount=10.25
- Decimal or hexadecimal: bitcoin:youraddress?amount=10.25
- Decimal or duodeci or hexadeci: bitcoin:youraddress?amount=10.25
If you want to request/bill for 1.5 mBTC (milli-BTC), you (or your shopping cart) would write:
- Decimal only: bitcoin:youraddress?amount=0.0015
- Decimal or hexadecimal: bitcoin:youraddress?amount=0.0015
- Decimal or duodeci or hexadeci: bitcoin:youraddress?amount=0.0015
If you want to request/bill for 10.2 TBC (TonalBitcoin), you (or your shopping cart) would write:
- Decimal only: bitcoin:youraddress?amount=0.01056768
- Decimal or hexadecimal: bitcoin:youraddress?amount=x10.2
- Decimal or duodeci or hexadeci: bitcoin:youraddress?amount=x10.2
If you want to request/bill for 1 ᵐTBC (mill-TonalBitcoin), you (or your shopping cart) would write:
- Decimal only: bitcoin:youraddress?amount=2.68435456
- Decimal or hexadecimal: bitcoin:youraddress?amount=x1000
- Decimal or duodeci or hexadeci: bitcoin:youraddress?amount=x1000
Jump to: