From: Wladimir <laanwj@gmail•com>
To: Gary Rowe <g.rowe@froot•co.uk>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Accepting broken QRcodes
Date: Mon, 16 Jul 2012 11:02:46 +0200 [thread overview]
Message-ID: <CA+s+GJBPQWYy1oftKkndZ8FF1hTaL-Zoc3bO_c3=s_LNkW635g@mail.gmail.com> (raw)
In-Reply-To: <CAKm8k+2UTofgBOCZ_VtHPJdPs4w3oEv4bSDzFbW4M2tw9ZtjRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2574 bytes --]
But is he the only one using the broken URLs? It was my impression that
they were widespread already.
Wladimir
On Mon, Jul 16, 2012 at 10:52 AM, Gary Rowe <g.rowe@froot•co.uk> wrote:
> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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: 3840 bytes --]
next prev parent reply other threads:[~2012-07-16 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 12:39 Mike Hearn
2012-07-16 8:16 ` Andreas Schildbach
2012-07-16 8:52 ` Gary Rowe
2012-07-16 9:02 ` Wladimir [this message]
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='CA+s+GJBPQWYy1oftKkndZ8FF1hTaL-Zoc3bO_c3=s_LNkW635g@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=g.rowe@froot$(echo .)co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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