Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1SPosY-0000uy-JK
	for bitcoin-development@lists.sourceforge.net;
	Thu, 03 May 2012 05:47:02 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.47 as permitted sender)
	client-ip=209.85.213.47; envelope-from=laanwj@gmail.com;
	helo=mail-yw0-f47.google.com; 
Received: from mail-yw0-f47.google.com ([209.85.213.47])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1SPosX-0005F4-TF
	for bitcoin-development@lists.sourceforge.net;
	Thu, 03 May 2012 05:47:02 +0000
Received: by yhjj56 with SMTP id j56so1764653yhj.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 02 May 2012 22:46:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.161.102 with SMTP id v66mr1000567yhk.56.1336024016536;
	Wed, 02 May 2012 22:46:56 -0700 (PDT)
Received: by 10.236.176.38 with HTTP; Wed, 2 May 2012 22:46:56 -0700 (PDT)
In-Reply-To: <4FA2095D.9060307@gmail.com>
References: <4FA2095D.9060307@gmail.com>
Date: Thu, 3 May 2012 07:46:56 +0200
Message-ID: <CA+s+GJA2qZxq=V_=Ma0LESOjae49aZHdrpMeJzQS3GtwP5T6=w@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303f6528eac3e804bf1b54b6
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
X-Headers-End: 1SPosX-0005F4-TF
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] URI Handling in Bitcoin-Qt
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: Thu, 03 May 2012 05:47:02 -0000

--20cf303f6528eac3e804bf1b54b6
Content-Type: text/plain; charset=UTF-8

On Thu, May 3, 2012 at 6:28 AM, Alan Reiner <etotheipi@gmail.com> wrote:

> **
> *(1) *What is the status & plans for supporting "bitcoin:" URIs in the
> Satoshi client?  My understanding is that it currently creates URIs, but
> does *not* register itself with the OS to handle such links.  Is this
> accurate?  This seems like a very high-value feature, and I'd recommend
> that we consider it a priority -- I can't think of any other upgrade that
> can improve usability so dramatically on the desktop.
>

It is already implemented for Linux (Gnome) and Windows, but there is an
issue with boost::ipc that crashed bitcoin at startup on windows, so it's
temporarily disabled on Windows.


> *(2) *I need to understand better what the intentions were behind
> "label=" and "message=".  The way I understand it is that Bitcoin-Qt uses
> and stores only address-labels, and no other transactional info is stored
> in the wallet.  As such, the "message=" field would be displayed to the
> user when a "bitcoin:" link is clicked, but that message wouldn't be saved
> anywhere.
>

Label is a label for the destination address, message is a freeform message
describing the transaction.

I don't think the message is currently stored in the Satoshi client. That
feature is somewhere on our way-too-long issue and todo list.

But I understand that you want to add transaction meta-data fields such as
contact information, bought items, item prices?

Wladimir

--20cf303f6528eac3e804bf1b54b6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, May 3, 2012 at 6:28 AM, Alan Reiner <span dir=3D"ltr">&lt;<a href=
=3D"mailto:etotheipi@gmail.com" target=3D"_blank">etotheipi@gmail.com</a>&g=
t;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<u></u>

 =20

   =20
 =20
  <div bgcolor=3D"#ffffff" text=3D"#000000"><b>(1) </b>What is the status &=
amp; plans for supporting &quot;bitcoin:&quot;
    URIs in the Satoshi client?=C2=A0 My understanding is that it currently
    creates URIs, but does <b>not</b> register itself with the OS to
    handle such links.=C2=A0 Is this accurate?=C2=A0 This seems like a very
    high-value feature, and I&#39;d recommend that we consider it a priorit=
y
    -- I can&#39;t think of any other upgrade that can improve usability so
    dramatically on the desktop.<br></div></blockquote><div><br></div><div>=
It is already implemented for Linux (Gnome) and Windows, but there is an is=
sue with boost::ipc that crashed bitcoin at startup on windows, so it&#39;s=
 temporarily disabled on Windows.</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#ffffff" te=
xt=3D"#000000"><b>(2) </b>I need to understand better what the intentions w=
ere
    behind &quot;label=3D&quot; and &quot;message=3D&quot;.=C2=A0 The way I=
 understand it is that
    Bitcoin-Qt uses and stores only address-labels, and no other
    transactional info is stored in the wallet.=C2=A0 As such, the &quot;me=
ssage=3D&quot;
    field would be displayed to the user when a &quot;bitcoin:&quot; link i=
s
    clicked, but that message wouldn&#39;t be saved anywhere.<br></div></bl=
ockquote><div><br></div><div>Label is a label for the destination address, =
message is a freeform message describing the transaction.</div><div><br>
</div><div>I don&#39;t think the message is currently stored in the Satoshi=
 client. That feature is somewhere on our way-too-long issue and todo list.=
</div><div><br></div><div>But I understand that you want to add transaction=
 meta-data fields such as contact information, bought items, item prices?</=
div>
<div><br></div><div>Wladimir</div><div><br></div></div>

--20cf303f6528eac3e804bf1b54b6--