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 ) 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 ; 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: References: Date: Mon, 16 Jul 2012 09:52:34 +0100 X-Google-Sender-Auth: Tv_f8nHKz8THh6d27z-sGZWt8m0 Message-ID: From: Gary Rowe 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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.

On 16 July 2012 09:16, Andreas Schi= ldbach <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 g= one
> 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<= 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.

The problem with this "accept everything even if broken" ap= proach 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/50122= 263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf300fad870ad3c004c4ee8d1c--