> 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
