Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1RaQKZ-0001ym-L8 for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 11:15:31 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.47 as permitted sender) client-ip=209.85.210.47; envelope-from=laanwj@gmail.com; helo=mail-pz0-f47.google.com; Received: from mail-pz0-f47.google.com ([209.85.210.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RaQKU-0002Ke-4Z for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 11:15:31 +0000 Received: by dake40 with SMTP id e40so8115196dak.34 for <bitcoin-development@lists.sourceforge.net>; Tue, 13 Dec 2011 03:15:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.75.130 with SMTP id c2mr43300468pbw.92.1323774920181; Tue, 13 Dec 2011 03:15:20 -0800 (PST) Received: by 10.142.161.12 with HTTP; Tue, 13 Dec 2011 03:15:20 -0800 (PST) In-Reply-To: <CANEZrP3EpkCaK2nXXazX-D-a0yO_3SkWXg74V2zh+nCM=Ko20w@mail.gmail.com> References: <201112061610.41083.luke@dashjr.org> <201112101316.31666.luke@dashjr.org> <20111212205559.GA16665@ulyssis.org> <201112121602.12806.luke@dashjr.org> <CANEZrP2GvBg19LMyDG_DJe18cvUg3xG7H9S7m+8EemkARz7_Tg@mail.gmail.com> <CA+s+GJDxJesFGhE8K2DiR_nxfDebEKtDRGWxeVRC7eaZbO9fSw@mail.gmail.com> <CANEZrP3EpkCaK2nXXazX-D-a0yO_3SkWXg74V2zh+nCM=Ko20w@mail.gmail.com> Date: Tue, 13 Dec 2011 12:15:20 +0100 Message-ID: <CA+s+GJCdKAOtpwitGWOXW9yq5qBD6Up8KdkJwvwQNM3No-pHOg@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Mike Hearn <mike@plan99.net> Content-Type: multipart/alternative; boundary=f46d041b4732e1495704b3f75d98 X-Spam-Score: -0.6 (/) 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 (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RaQKU-0002Ke-4Z Cc: Pieter Wuille <pieter.wuille@cs.kuleuven.be>, bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Version bytes "2.0" 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: Tue, 13 Dec 2011 11:15:31 -0000 --f46d041b4732e1495704b3f75d98 Content-Type: text/plain; charset=UTF-8 > > > That's cool. I hope Matts change gets merged soon. Then the issue becomes > how do people find out about this capability? Expecting people to learn how > to hand-craft Bitcoin links won't work. But all modern operating systems > support copy/paste and drag/drop of rich content. Qt probably makes it easy > to expose an UI like this: > > *Pay me* [Copy to clipboard] > > Clicking the link in the UI would pop up an alert saying something like > > "You can drag this link to an email, chat window or editing program." > Good idea! This could be integrated with the QR-code generation ( https://github.com/bitcoin/bitcoin/pull/629) which adds "create a payment link" functionality (but currently only "exports" this link as a QR code). Wladimir --f46d041b4732e1495704b3f75d98 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi= n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"gma= il_quote"><div class=3D"im"><div><br></div></div><div>That's cool. I ho= pe Matts change gets merged soon. Then the issue becomes how do people find= out about this capability? Expecting people to learn how to hand-craft Bit= coin links won't work. But all modern operating systems support copy/pa= ste and drag/drop of rich content. Qt probably makes it easy to expose an U= I like this:</div> <div><br></div><div>=C2=A0 =C2=A0<u><font color=3D"#3333ff">Pay me</font></= u> =C2=A0 =C2=A0[Copy to clipboard]</div><div><br></div><div>Clicking the l= ink in the UI would pop up an alert saying something like</div><div> <br></div><div>=C2=A0 =C2=A0"You can drag this link to an email, chat = window or editing program."</div></div></blockquote><div><br></div><di= v>Good idea! This could be integrated with the QR-code generation (<a href= =3D"https://github.com/bitcoin/bitcoin/pull/629">https://github.com/bitcoin= /bitcoin/pull/629</a>) which adds "create a payment link" functio= nality (but currently only "exports" this link as a QR code).</di= v> <div><br></div><div>Wladimir</div><div><br></div></div> --f46d041b4732e1495704b3f75d98--