1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
Return-Path: <natanael.l@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E1916BDA
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Dec 2017 22:01:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0F1EC3F9
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Dec 2017 22:01:11 +0000 (UTC)
Received: by mail-wm0-f47.google.com with SMTP id r78so14121309wme.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Dec 2017 14:01:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=s5Dc1/fuYc9IbfU9SCj0vFzpYPIsTaMS28NDNbOg4j0=;
b=iPHpQn6Dt2KnwCfLEnX6LkcaCdN427a6JF+5JpTUZwb1cN8AKvjLwXAMXiMjTsKrp9
AWPbd8acqwTdBTGDSS6obN415XZhPECIN7lBQEQCqOJeRKkGqYI8ZIMM9jHkVr4AeP/C
UouGe8n2psaKhQaStT5IwwTyu2ENG3GgM5ssvoSpvz7olC4tZeJ8lW3kYs1Rodmnbwnj
DEYFylmhdqYln+ClxD7wA2pw5RQHfJX8fEWrLNeDOERsP9OYjW9PtvhRT9Ts0gRptNAN
d0ukkATBoI2VWQ6Q1qxG1s3MNbBcRDjaO3m1RtpotWy0SYqTTrVsES4touSs4+IjEQH7
DUtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=s5Dc1/fuYc9IbfU9SCj0vFzpYPIsTaMS28NDNbOg4j0=;
b=pTEn798bC+jpKIYuzwvsJAPwh7EgnHJXq6vKGMCNnyfIV+x8qLT9rAK6danSgEnfRa
xayPw1MQlEiW5zmUQWoJjEVy0lCGDbjqpUJkbxaHXMmW2jkZoRn2oVAMoEZqLHtxHo+U
ZLwEJa/G93/+cwQ/QAqBXMQMS17lyB0upgab8bkq91d6NIgISCxSyYY2Rqw3jiawb+5w
6Mw2BMiJ+4PkW2RHtfmZ2HR5+TeWfigJC7eJtwcnobt+qlqJialiECXrT1ZncivNkJ+6
5QZUs8k+ePvb76sONq44TDfcb3osk2t11XA1InGZFz80EpzzvXMw4pMWDf8I/PsUlZ3N
eueg==
X-Gm-Message-State: AKGB3mIuq14rQkXD673bmgjsIuPxLQvAyqjsGRAEWryybiEs4rKgkicZ
xChQfNcRXWJQlarhMCrhuT+Fy/DrlrEUSsjPcwY=
X-Google-Smtp-Source: ACJfBouXDZ4I5TTolHj+FqFeDZhDTome5Rx9xfhyJId2CvzE3t21HbnZg5GVOwL82NKk5s4rYuYG96SWUa4SWSZsLi4=
X-Received: by 10.80.244.194 with SMTP id v2mr14416832edm.68.1513288870549;
Thu, 14 Dec 2017 14:01:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.176.3 with HTTP; Thu, 14 Dec 2017 14:01:09 -0800 (PST)
Received: by 10.80.176.3 with HTTP; Thu, 14 Dec 2017 14:01:09 -0800 (PST)
In-Reply-To: <CAAUq485pTYs++FY9GkAt64gvba_Mngzpui7TWXdQM-x9GyAQdg@mail.gmail.com>
References: <CAJR7vkqcBo+o9BL8sK1TBqqNUNSMWdut_aL_YMXse8rDC2ju9A@mail.gmail.com>
<20171213213607.ijlvqwpdaokucgi6@fedora-23-dvm>
<CAAUq485pTYs++FY9GkAt64gvba_Mngzpui7TWXdQM-x9GyAQdg@mail.gmail.com>
From: Natanael <natanael.l@gmail.com>
Date: Thu, 14 Dec 2017 23:01:09 +0100
Message-ID: <CAAt2M19ZrbvrKc+mz1LEKrM2AuGH01gN+i9w8zSvdmazommMxg@mail.gmail.com>
To: Marcel Jamin <marcel@jamin.net>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="94eb2c091cba925d9105605405b7"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 22:01:13 -0000
--94eb2c091cba925d9105605405b7
Content-Type: text/plain; charset="UTF-8"
Reposting /u/BashCo's post on reddit here, for visibility:
---8<---------------------------------------------------------------
> Before anyone says 'bits' are too confusing because it's a computer
science term, here's a list of homonyms [https://en.wikipedia.org/
wiki/List_of_true_homonyms] that you use every day. Homonyms are fine
because our brains are able to interpret language based on context, so it's
a non-argument.
This ignores the fact that there exists multiple meanings of bits *within
the same context*, and that beginners likely can't tell them apart.
Feel free to try it yourself - talk about Bitcoin "bits" of a particular
value with somebody who doesn't understand Bitcoin. Then explain that the
cryptography uses 256 bit keys. I would be surprised if you could find
somebody who would not be confused by that.
Let's say a website says a song is 24 bits. Was that 24 bit audio
resolution or 24 bit price? Somebody writes about 256 bit keys, are that
their size or value?
You guys here can probably tell the difference. Can everybody...? Bits will
cause confusion, because plenty of people will not be able to tell these
apart. They will not know WHEN to apply one definition or the other.
https://www.reddit.com/r/bitcoin/comments/24m3nb/_/ch8gua7
--94eb2c091cba925d9105605405b7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div><div class=3D"gmail_extra"><div class=3D"gmail_quote=
"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"quoted-text"><br>
</div>Reposting /u/BashCo's post on reddit here, for visibility:<br>
<br>
---8<-------------------------<wbr>------------------------------<wbr>--=
------<br>
<br>
> Before anyone says 'bits' are too confusing because it's a=
computer science term, here's a list of homonyms [<a href=3D"https://e=
n.wikipedia.org/wiki/List_of_true_homonyms" rel=3D"noreferrer" target=3D"_b=
lank">https://en.wikipedia.org/<wbr>wiki/List_of_true_homonyms</a>] that yo=
u use every day. Homonyms are fine because our brains are able to interpret=
language based on context, so it's a non-argument.=C2=A0</blockquote><=
/div></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">This ignores=
the fact that there exists multiple meanings of bits *within the same cont=
ext*, and that beginners likely can't tell them apart.=C2=A0</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Feel free to try it yourself - tal=
k about Bitcoin "bits" of a particular value with somebody who=C2=
=A0 doesn't understand Bitcoin. Then explain that the cryptography uses=
256 bit keys. I would be surprised if you could find somebody who would no=
t be confused by that.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Let's say a website says a song is 24 bits. Was that 24 bit audio =
resolution or 24 bit price? Somebody writes about 256 bit keys, are that th=
eir size or value?=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>You guys here can probably tell the difference. Can everybody...? Bits wil=
l cause confusion, because plenty of people will not be able to tell these =
apart. They will not know WHEN to apply one definition or the other.=C2=A0<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://www.r=
eddit.com/r/bitcoin/comments/24m3nb/_/ch8gua7">https://www.reddit.com/r/bit=
coin/comments/24m3nb/_/ch8gua7</a></div><div dir=3D"auto"><br></div><div di=
r=3D"auto"><br></div><div dir=3D"auto"></div></div>
--94eb2c091cba925d9105605405b7--
|
