public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Accepting broken QRcodes
Date: Mon, 16 Jul 2012 10:16:58 +0200	[thread overview]
Message-ID: <ju0ilq$7q7$2@dough.gmane.org> (raw)
In-Reply-To: <CANEZrP1=VLpRL5cWTS1gQnYmg0eChBmwWd_-i0S5Zqm3r6Jg5g@mail.gmail.com>

> 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.




  reply	other threads:[~2012-07-16  8:17 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 [this message]
2012-07-16  8:52   ` Gary Rowe
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='ju0ilq$7q7$2@dough.gmane.org' \
    --to=andreas@schildbach.de \
    --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