summaryrefslogtreecommitdiff
path: root/68/273be1e2a78892b20b435e6cb9f16d076cfa74
blob: 58e9a0021eb0a7388cc386ae2b24955c9a2dfee8 (plain)
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
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 <bitcoin-list@bluematt.me>) id 1RqxmC-00018r-CS
	for bitcoin-development@lists.sourceforge.net;
	Sat, 28 Jan 2012 02:12:24 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me
	designates 173.246.101.161 as permitted sender)
	client-ip=173.246.101.161;
	envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; 
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1RqxmB-00036C-9L for bitcoin-development@lists.sourceforge.net;
	Sat, 28 Jan 2012 02:12:24 +0000
Received: from [21.93.184.243] (66-87-104-243.pools.spcsdns.net
	[66.87.104.243])
	by mail.bluematt.me (Postfix) with ESMTPSA id CD1DF3F8
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 28 Jan 2012 03:03:51 +0100 (CET)
References: <1327704664.31621.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<201201271800.31819.luke@dashjr.org>
	<05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com>
	<201201272045.10787.luke@dashjr.org>
User-Agent: K-9 Mail for Android
In-Reply-To: <201201272045.10787.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
From: bitcoin-list@bluematt.me
Date: Fri, 27 Jan 2012 21:12:11 -0500
To: bitcoin-development@lists.sourceforge.net
Message-ID: <759be3f8-ca4c-4e36-aac1-b3894dda450d@email.android.com>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.4 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.4 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records
	-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RqxmB-00036C-9L
Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
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: Sat, 28 Jan 2012 02:12:24 -0000



Luke-Jr <luke@dashjr.org> wrote:

>On Friday, January 27, 2012 7:36:31 PM bitcoin-list@bluematt.me wrote:
>> It was implemented in the waylaying client with the merge of
>Bitcoin-Qt for
>> drag and drop, and just recently for system URI handling in
>>
>https://github.com/bitcoin/bitcoin/commit/70f55355e29c8e45b607e782c5d766=
09
>> d23cc858.
>
>It's been implemented in many clients for nearly all 2011.
>Bitcoin-Qt is just behind the pace. Not relevant.
>
>> However the version on the wiki armed as BIP 20 has a ton of
>extraneous crap
>> in it's number encoding which is not implemented in Bitcoin-Qt since
>it was
>> explicitly voted against at the time the spec was being discussed.
>
>You mean 3 months *after* the spec had a consensus and multiple=20
>implementations.
I'm really not gonna reopen this debate.  You made a poll that was worded=
 in the most biased way I could think of and still lost.  The multiple im=
plementations were written but you and I know of no sites that actually h=
ad links to your version.