But is he the only one using the broken URLs? It was my impression that they were widespread already.<div><br></div><div>Wladimir<br><br><div class="gmail_quote">On Mon, Jul 16, 2012 at 10:52 AM, Gary Rowe <span dir="ltr"><<a href="mailto:g.rowe@froot.co.uk" target="_blank">g.rowe@froot.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<div class="HOEnZb">
<div class="h5"><br><br><div class="gmail_quote">On 16 July 2012 09:16, Andreas Schildbach <span dir="ltr"><<a href="mailto:andreas@schildbach.de" target="_blank">andreas@schildbach.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>> 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<br>
> without :// in them, he stopped responding to my emails. So I've gone<br>
> ahead and added support for reading these types of URLs to bitcoinj,<br>
> 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" approach 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's security and<br>
threat landscape has changed and how IT managers can respond. Discussions<br>
will include endpoint security, mobile security and the latest in malware<br>
threats. <a href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/" target="_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net" target="_blank">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</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's security and<br>
threat landscape has changed and how IT managers can respond. Discussions<br>
will include endpoint security, mobile security and the latest in malware<br>
threats. <a href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/" target="_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br></div>