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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1SqO7E-0008TB-8r
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Jul 2012 12:40:00 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.181 as permitted sender)
client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f181.google.com;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SqO7B-0001x4-CV
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Jul 2012 12:40:00 +0000
Received: by wibhm2 with SMTP id hm2so1531357wib.10
for <bitcoin-development@lists.sourceforge.net>;
Sun, 15 Jul 2012 05:39:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.14.8 with SMTP id l8mr10838566wic.6.1342355990976; Sun, 15
Jul 2012 05:39:50 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.19.13 with HTTP; Sun, 15 Jul 2012 05:39:50 -0700 (PDT)
Date: Sun, 15 Jul 2012 14:39:50 +0200
X-Google-Sender-Auth: TmQNtlKTdfW2ezWqK4kO0aRmyZ4
Message-ID: <CANEZrP1=VLpRL5cWTS1gQnYmg0eChBmwWd_-i0S5Zqm3r6Jg5g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -0.9 (/)
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.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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.6 URIBL_SBL Contains an URL listed in the SBL blocklist
[URIs: blockchain.info]
X-Headers-End: 1SqO7B-0001x4-CV
Subject: [Bitcoin-development] Accepting broken QRcodes
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: Sun, 15 Jul 2012 12:40:00 -0000
Hi bitcoin-development,
blockchain.info generates non-BIP-compliant URIs in its QRcodes, as
does its iPhone app. They are of the form bitcoin://address not
bitcoin:address.
I asked Ben to fix this (social networks don't parse QRcodes after
all), but after explaining that social networks don't parse URLs
without :// in them, he stopped responding to my emails. So I've gone
ahead and added support for reading these types of URLs to bitcoinj,
in the interests of "just works" interoperability.
This mail is just a heads up in case anyone else wants to do the same
thing. Hopefully at some point, Ben will stop generating such QRcodes
and we can remove these hacks and get back to BIP compliance.
|
