I have to agree with Mike. Human language is surprisingly tolerant of
overloading and inference from context. Neurotypical people have no
problem with it and perceive a software engineer's aversion to it as
being pedantic and strange. Note that "bits" was a term for a unit of
money long before the
Excellent move Jeff.
Best would now be to establish XBT as the ISO code for bits.
Regards,
Tamas Blummer
http://bitsofproof.com
On 02.05.2014, at 21:17, Jeff Garzik wrote:
>
>
> Related:
> http://blog.bitpay.com/2014/05/02/bitpay-bitcoin-and-where-to-put-that-decimal-point.html
>
> --
>
Think your example is not quite valid ...
People say or write $88M or $45k I.e. use SI prefix as a suffix, else it would
be more, not less, clear on what amount is being referred to.
For me, "bits" are easy to say and one million as a factor is simple to
understand.
M-bits, kilobits, millibits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
>Huh? Your examples demonstrate the *opposite* of your point. 'k' and
>'M' *are*
>the SI prefixes. People *do* use 63k USD, $63k, and $3M.
Excellent point.
Also, I frequently hear statements referring to mili-bitcoins, mBTC, pronounced
as "mili-
Luke,
My point is that you never apply the prefixes to the currency unit itself.
We don't spend kilodollars or megadollars.
Ben
On Fri, May 2, 2014 at 7:38 PM, Luke Dashjr wrote:
> On Saturday, May 03, 2014 12:54:37 AM Ben Davenport wrote:
> > My only addition is that I think we should all st
On Saturday, May 03, 2014 12:54:37 AM Ben Davenport wrote:
> My only addition is that I think we should all stop trying to attach SI
> prefixes to the currency unit. Name me another world currency that uses SI
> prefixes. No one quotes amounts as 63 k$ or 3 M$. The accepted standard at
> least in t
I live in Argentina. Here, 1BTC is around half of a monthly average
wage (net), so, as you
can imagine, the value of 1 BTC is *very* inconvenient for everyday
transactions.
Also it presents an important entry barrier for new adopters: It would be
easier to accept buying thousands of "bits" than
[resend - apologies if duplicate]
Microbitcoin is a good-sized unit, workable for everyday transaction
values, with room-to-grow, and a nice relationship to satoshis as 'cents'.
But "bits" has problems as a unit name.
"Bits" will be especially problematic whenever people try to graduate
from i
It will also be important to chose the currency symbol for "bits" at the
same time. Lowercase stroke "b" I think is the obvious choice.
Unicode U+0180
Aaron
On Friday, May 2, 2014, Alan Reiner wrote:
> I've been a strong supporter of the 1e-6 unit switch since the beginning
> and ready to do w
I've been a strong supporter of the 1e-6 unit switch since the beginning
and ready to do whatever I can with Armory to help ease that
transition. I'm happy to prioritize a release that updates the Armory
interface to make "bits" the default unit, when the time is right. I
think it makes sense to
I fully support this (it's what I suggested over a year ago), but what it
comes down to is BitPay, Coinbase, Blockchain and Bitstamp getting
together, agreeing what they're going to use, and doing a little joint
customer education campaign around it. If there's community momentum around
"bits", gre
> *Extended validation certs*
>
> When a business is accepting payment, showing the name of the business is
> usually better than showing just the domain name, for a few reasons:
>
>1. Unless your domain name *is* your business name like blockchain.info,
>it looks better and gives more in
At the moment BIP70 specifically requires that a request be rejected
if validation fails, so that should be fixed that sooner rather than
later:
"The recipient must verify the certificate chain according to
[RFC5280] and reject the PaymentRequest if any validation failure
occurs."
Aaron
There's
Related:
http://blog.bitpay.com/2014/05/02/bitpay-bitcoin-and-where-to-put-that-decimal-point.html
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--
"Accelerate
On Fri, May 2, 2014 at 7:46 PM, Kristov Atlas
wrote:
> Nice work! I can confirm that this dev binary runs smoothly in the latest
Thanks for testing!
> version of Tails, v1.0. Screenshot proof here [1]. When this is incorporated
> into the next release of Bitcoin Core, will this make the usual Li
On 04/30/2014 03:02 AM, Wladimir wrote:
> On Sat, Apr 26, 2014 at 7:29 PM, Kristov Atlas
> wrote:
>> Hey Wladimir,
>>
>> Thanks for building this binary. The initial problem with Qt was
>> resolved, and I was able to load the GUI that chooses my datadir. After
>> choosing the default datadir, how
A bunch of different people either have implemented or are implementing
BIP70 at the moment. Here's a bunch of things I've been telling people in
response to questions. At some point I'll submit a pull req with this stuff
in but for now it's just an email.
*Error handling during signature checking
On 14 November 2013 12:45, Melvin Carvalho wrote:
> Rationale
> ===
>
> Given the recent rise in value there seems to be anecdotal evidence that 1
> bitcoin being so high is putting off a lot of normal buyers, because they
> feel that putting down $400+ and only getting "1 coin", or having to
The Bonneau's Kickbacks problem is interesting because it is a
destabilizing incentive.
Just by luck yesterday I was working on the same problem. I found a way
to prevent Kickbacks and provide a conflict resolution strategy that
benefits all member of the network.
I will repost my blog post here, b
The original post is here: http://bitslog.wordpress.com/2014/05/02/decor/
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unp
20 matches
Mail list logo
