public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gary Rowe <g.rowe@froot.co.uk>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Accepting broken QRcodes
Date: Mon, 16 Jul 2012 09:52:34 +0100	[thread overview]
Message-ID: <CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com> (raw)
In-Reply-To: <ju0ilq$7q7$2@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2467 bytes --]

  reply	other threads:[~2012-07-16  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 12:39 [Bitcoin-development] Accepting broken QRcodes Mike Hearn
2012-07-16  8:16 ` Andreas Schildbach
2012-07-16  8:52   ` Gary Rowe [this message]
2012-07-16  9:02     ` Wladimir
2012-07-16  9:32       ` Gary Rowe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com \
    --to=g.rowe@froot.co.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox