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 ) 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 ; 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: From: Wladimir To: Alan Reiner 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 <etotheipi@gmail.com&g= t; wrote:
=20 =20 =20
(1) What is the status &= amp; plans for supporting "bitcoin:" URIs in the Satoshi client?=C2=A0 My understanding is that it currently creates URIs, but does not 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'd recommend that we consider it a priorit= y -- 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 is= sue with boost::ipc that crashed bitcoin at startup on windows, so it's= temporarily disabled on Windows.
=C2=A0
(2) I need to understand better what the intentions w= ere behind "label=3D" and "message=3D".=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 "me= ssage=3D" field would be displayed to the user when a "bitcoin:" link i= s 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--