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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1RsEgM-0005vm-8D
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:27:38 +0000
X-ACL-Warn:
Received: from nm39.bullet.mail.ne1.yahoo.com ([98.138.229.32])
by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RsEgG-0006ti-NA for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:27:38 +0000
Received: from [98.138.90.53] by nm39.bullet.mail.ne1.yahoo.com with NNFMP;
31 Jan 2012 14:27:27 -0000
Received: from [98.138.89.232] by tm6.bullet.mail.ne1.yahoo.com with NNFMP;
31 Jan 2012 14:27:27 -0000
Received: from [127.0.0.1] by omp1047.mail.ne1.yahoo.com with NNFMP;
31 Jan 2012 14:27:27 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 79192.86087.bm@omp1047.mail.ne1.yahoo.com
Received: (qmail 71901 invoked by uid 60001); 31 Jan 2012 14:27:27 -0000
X-YMail-OSG: .9XkXqYVM1lVvPQNv7vVityl203hvFY9T6REXWgRZ3rg_ug
8OvoBH4eq_sfHoLSnJFojl52LTJ8BM6nxG107BM5RDW8VdVJjSNZ3ArE_3si
Kb9tLC1mYSWK3LVRbryPSD6pnbm74UExwAb8bj6xEiYrO2n_Vbo0kNa3xAPm
eSyMGtUzloUu4rwtZ8M603ZD7TTRMCurLPGUO6eseBICX9b7G1xPHMgMdkCY
fHuGJGyhMwY7IjB4Qt4Y6TMOudnDECHe0wAmPS6kFzavBvIndAHdX.7ezyv7
W4Whd3vKDwpe2SrKBJm2dCwHuM5o2G8XUXX_n2vdGkvaA5iyjlwhC507oPXH
h0eWtC613_0_Ik32syDLHgS3FOareqU7Rxx4Pd9qDaVPl5GYm28xx0LphVg- -
Received: from [92.20.121.197] by web121002.mail.ne1.yahoo.com via HTTP;
Tue, 31 Jan 2012 06:27:26 PST
X-Mailer: YahooMailWebService/0.8.116.331537
Message-ID: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
Date: Tue, 31 Jan 2012 06:27:26 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.229.32 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RsEgG-0006ti-NA
Subject: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 14:27:38 -0000
BIP 20 really has no support among implementations such as Bitcoin-Qt, Elec=
trum, MultiBit or Bitcoin-JS. As the most active and visible user facing GU=
I projects (all with some form of URI Scheme), their opinion carries the mo=
st weight. To a lesser degree Bitcoin-Qt has the large majority of users to=
o (although that's a line of reasoning I'd discourage).=0A=0ANormally we sh=
ould probably Reject BIP 21 and re-submit a new standard (for history's sak=
e), but as a) BIP 21 is largely a copy paste of BIP 20 sans some sections b=
) it is still a draft, probably the best thing here is if you all agree on =
something to run it by BlueMatt and then we'll make it the new BIP 21.=0A=
=0AI can see a consensus forming on most parts. Just the send private key i=
s contentious, and there's the topic of adding a time to expire field for m=
erchants (this is a very good idea IMO).=0A=0AAlso BIP 20 is problematic be=
cause it is incompatible with about every standard on the web. All the HTML=
, URI and everything uses decimal numbers alone. I see no reason for breaki=
ng with tradition. Note that everytime I have to write Color or Vectorize (=
as a British speaker) in my code, I die a little inside. But it's conventio=
n and American English =3D International English. Also it would be cool if =
all code used a *real* international language (like Esperanto) but the worl=
d ain't perfect! We live in a decimal-counting English-speaking Windows-usi=
ng God-worshipping world!=0A=0A(no offense to=A0decimal-counting English-sp=
eaking Windows-using God-worshipping world- I do half those things too :)
|
