Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.47 as permitted sender)
	client-ip=209.85.160.47; envelope-from=laanwj@gmail.com;
	helo=mail-pb0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com>
References: <CANEZrP1=VLpRL5cWTS1gQnYmg0eChBmwWd_-i0S5Zqm3r6Jg5g@mail.gmail.com>
	<ju0ilq$7q7$2@dough.gmane.org>
	<CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com>
Date: Mon, 16 Jul 2012 11:02:46 +0200
Message-ID: <CA+s+GJBPQWYy1oftKkndZ8FF1hTaL-Zoc3bO_c3=s_LNkW635g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Gary Rowe <g.rowe@froot.co.uk>
Content-Type: multipart/alternative; boundary=047d7b15a81389e7e704c4eeb1b0
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Accepting broken QRcodes
Precedence: list

--047d7b15a81389e7e704c4eeb1b0
Content-Type: text/plain; charset=UTF-8

But is he the only one using the broken URLs? It was my impression that
they were widespread already.

Wladimir

On Mon, Jul 16, 2012 at 10:52 AM, Gary Rowe <g.rowe@froot.co.uk> wrote:

> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

--047d7b15a81389e7e704c4eeb1b0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

But is he the only one using the broken URLs? It was my impression that the=
y were widespread already.<div><br></div><div>Wladimir<br><br><div class=3D=
"gmail_quote">On Mon, Jul 16, 2012 at 10:52 AM, Gary Rowe <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:g.rowe@froot.co.uk" target=3D"_blank">g.rowe@froot.c=
o.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Is it worth having a few more people email B=
en to ask him politely to fall into line with the BIP? No point encouraging=
 broken windows by not speaking out.<div class=3D"HOEnZb">
<div class=3D"h5"><br><br><div class=3D"gmail_quote">On 16 July 2012 09:16,=
 Andreas Schildbach <span dir=3D"ltr">&lt;<a href=3D"mailto:andreas@schildb=
ach.de" target=3D"_blank">andreas@schildbach.de</a>&gt;</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>&gt; I asked Ben to =
fix this (social networks don&#39;t parse QRcodes after<br>
&gt; all), but after explaining that social networks don&#39;t parse URLs<b=
r>
&gt; without :// in them, he stopped responding to my emails. So I&#39;ve g=
one<br>
&gt; ahead and added support for reading these types of URLs to bitcoinj,<b=
r>
&gt; in the interests of &quot;just works&quot; interoperability.<br>
&gt;<br>
&gt; This mail is just a heads up in case anyone else wants to do the same<=
br>
&gt; thing. Hopefully at some point, Ben will stop generating such QRcodes<=
br>
&gt; and we can remove these hacks and get back to BIP compliance.<br>
<br>
</div>The problem with this &quot;accept everything even if broken&quot; 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><div><br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today&#39;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" target=3D"_bla=
nk">Bitcoin-development@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>
</div></div><br>-----------------------------------------------------------=
-------------------<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today&#39;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>
<br></blockquote></div><br></div>

--047d7b15a81389e7e704c4eeb1b0--