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
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1Sqh2q-0000tl-7v
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Jul 2012 08:52:44 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.175 as permitted sender)
client-ip=209.85.160.175; envelope-from=g.rowe.froot@gmail.com;
helo=mail-gh0-f175.google.com;
Received: from mail-gh0-f175.google.com ([209.85.160.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Sqh2l-0001z4-Q6
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Jul 2012 08:52:44 +0000
Received: by ghbz2 with SMTP id z2so4901463ghb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 16 Jul 2012 01:52:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.78.195 with SMTP id g43mr8660480yhe.62.1342428754400; Mon,
16 Jul 2012 01:52:34 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.236.48.201 with HTTP; Mon, 16 Jul 2012 01:52:34 -0700 (PDT)
In-Reply-To: <ju0ilq$7q7$2@dough.gmane.org>
References: <CANEZrP1=VLpRL5cWTS1gQnYmg0eChBmwWd_-i0S5Zqm3r6Jg5g@mail.gmail.com>
<ju0ilq$7q7$2@dough.gmane.org>
Date: Mon, 16 Jul 2012 09:52:34 +0100
X-Google-Sender-Auth: Tv_f8nHKz8THh6d27z-sGZWt8m0
Message-ID: <CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=20cf300fad870ad3c004c4ee8d1c
X-Spam-Score: -0.5 (/)
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
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
X-Headers-End: 1Sqh2l-0001z4-Q6
Subject: Re: [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: Mon, 16 Jul 2012 08:52:44 -0000
--20cf300fad870ad3c004c4ee8d1c
Content-Type: text/plain; charset=UTF-8
Is it worth having a few more people email Ben to ask him politely to fall
into line with the BIP? No point encouraging broken windows by not speaking
out.
On 16 July 2012 09:16, Andreas Schildbach <andreas@schildbach.de> wrote:
> > 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.
>
> The problem with this "accept everything even if broken" approach is
> that people will probably never fix the broken stuff. So we likely end
> up with a fragmented de-facto standard.
>
> That does not mean I am totally against accepting broken URLs, but there
> should be at least a promise that they will be fixed at the source.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--20cf300fad870ad3c004c4ee8d1c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Is it worth having a few more people email Ben to ask him politely to fall =
into line with the BIP? No point encouraging broken windows by not speaking=
out.<br><br><div class=3D"gmail_quote">On 16 July 2012 09:16, Andreas Schi=
ldbach <span dir=3D"ltr"><<a href=3D"mailto:andreas@schildbach.de" targe=
t=3D"_blank">andreas@schildbach.de</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">> I =
asked Ben to fix this (social networks don't parse QRcodes after<br>
> all), but after explaining that social networks don't parse URLs<b=
r>
> without :// in them, he stopped responding to my emails. So I've g=
one<br>
> ahead and added support for reading these types of URLs to bitcoinj,<b=
r>
> in the interests of "just works" interoperability.<br>
><br>
> This mail is just a heads up in case anyone else wants to do the same<=
br>
> thing. Hopefully at some point, Ben will stop generating such QRcodes<=
br>
> and we can remove these hacks and get back to BIP compliance.<br>
<br>
</div>The problem with this "accept everything even if broken" ap=
proach is<br>
that people will probably never fix the broken stuff. So we likely end<br>
up with a fragmented de-facto standard.<br>
<br>
That does not mean I am totally against accepting broken URLs, but there<br=
>
should be at least a promise that they will be fixed at the source.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today's security and<br>
threat landscape has changed and how IT managers can respond. Discussions<b=
r>
will include endpoint security, mobile security and the latest in malware<b=
r>
threats. <a href=3D"http://www.accelacomm.com/jaw/sfrnl04242012/114/5012226=
3/" target=3D"_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122=
263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br>
--20cf300fad870ad3c004c4ee8d1c--
|
