From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <mh.in.england@gmail.com>) id 1W7u2D-0003ns-OX for bitcoin-development@lists.sourceforge.net; Mon, 27 Jan 2014 21:48:01 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.171 as permitted sender) client-ip=209.85.214.171; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f171.google.com; Received: from mail-ob0-f171.google.com ([209.85.214.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W7u2C-0001Gy-US for bitcoin-development@lists.sourceforge.net; Mon, 27 Jan 2014 21:48:01 +0000 Received: by mail-ob0-f171.google.com with SMTP id wp4so7145953obc.16 for <bitcoin-development@lists.sourceforge.net>; Mon, 27 Jan 2014 13:47:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.131.170 with SMTP id on10mr9753970obb.2.1390859275506; Mon, 27 Jan 2014 13:47:55 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.99.112 with HTTP; Mon, 27 Jan 2014 13:47:55 -0800 (PST) In-Reply-To: <lc6h0g$i3c$1@ger.gmane.org> References: <lc5hmg$1jh$1@ger.gmane.org> <CANEZrP3POX5SACS18_rrQxx=mzmthrM418zmd8Z7-5CBNFSW4Q@mail.gmail.com> <lc67sl$h3$1@ger.gmane.org> <lc6h0g$i3c$1@ger.gmane.org> Date: Mon, 27 Jan 2014 22:47:55 +0100 X-Google-Sender-Auth: TKOePkPlu79-ZonIkM-FKmJWKaA Message-ID: <CANEZrP2yck_H8u+F4AQzqaE9yaTxYyfNa5VSXdyOmuZSv07hqw@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Andreas Schildbach <andreas@schildbach.de> Content-Type: multipart/alternative; boundary=001a11c1e6760ce6bc04f0faa9a4 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 (mh.in.england[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: 1W7u2C-0001Gy-US Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Experiment with linking payment requests via href X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 27 Jan 2014 21:48:01 -0000 --001a11c1e6760ce6bc04f0faa9a4 Content-Type: text/plain; charset=UTF-8 > > All insist on handling the link with their download manager, which would > involve an additional click. That's the expected behaviour, right? That's why I said "download and open". The Bitcoin URI with r= is better because it lets you remove that second click, but in some contexts the file approach is the right way to go - like for an email attachment or payment request sent via WhatsApp. --001a11c1e6760ce6bc04f0faa9a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex">All insist on handling the link with their downl= oad manager,=C2=A0which would involve an additional click.</blockquote> <div><br></div><div>That's the expected behaviour, right? That's wh= y I said "download and open". The Bitcoin URI with r=3D is better= because it lets you remove that second click, but in some contexts the fil= e approach is the right way to go - like for an email attachment or payment= request sent via WhatsApp.</div> </div></div></div> --001a11c1e6760ce6bc04f0faa9a4--