Gary Rowe [ARCHIVE] on Nostr: 📅 Original date posted:2012-07-16 📝 Original message:Is it worth having a few ...
📅 Original date posted:2012-07-16
📝 Original message: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 at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20120716/8f48a16b/attachment.html>;
📝 Original message: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 at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20120716/8f48a16b/attachment.html>;