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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VgJIB-0006gY-AN for bitcoin-development@lists.sourceforge.net; Tue, 12 Nov 2013 19:06:27 +0000 X-ACL-Warn: Received: from mail-gg0-f171.google.com ([209.85.161.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VgJI9-0001pT-BJ for bitcoin-development@lists.sourceforge.net; Tue, 12 Nov 2013 19:06:27 +0000 Received: by mail-gg0-f171.google.com with SMTP id 21so609941ggh.16 for ; Tue, 12 Nov 2013 11:06:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=2BkuXvH8JdWH3TpfQaHXmdEnOnCmeSldjWS+dkmXwOg=; b=XoobE8u/OKtN3ogx7uhA0bH/2WJ0CM3xNzr4QtJoOAIyJrwHWwK926ji3Y8BizcIYu lahQsCkACGlowHNBhg/8l0AfCn8LNDvdDKGmW2Ner63AiN4WkgOUlEdBZnolahVeO+Mu MGOwDB6ew9AivaLJthvu/jbxBAVv4NvhLfj2RtwZaPnnPYtvV8tQuzhpeiIi/F8n5k8W ld2xrbzc4RzwQG1Md/2fgJXD6yP4kYuz0JPFuz/W/jP4W+cRYI2cZLSOgYwQ+cxEOw8g Au5ty1DdRblGywVSgTMrDoNKlYUUyeDMUoG7SjpORPYiIS/v8z29VZD7D0171IT6LTLC V91g== X-Gm-Message-State: ALoCoQmosaOUArpPWw41Wry6qVejO9txWs+8UooC6ZT9IF6WXSLVc+mMaGqS9Yz2OSs7Zp1LJY2E X-Received: by 10.236.42.10 with SMTP id i10mr1324060yhb.130.1384281290425; Tue, 12 Nov 2013 10:34:50 -0800 (PST) Received: from [127.0.0.1] (bolobolo1.torservers.net. [96.47.226.20]) by mx.google.com with ESMTPSA id x9sm40482482yhd.13.2013.11.12.10.34.43 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Nov 2013 10:34:49 -0800 (PST) Sender: Wendell Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Wendell In-Reply-To: Date: Wed, 13 Nov 2013 02:34:37 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0887034B-AA65-468B-A8DB-4DF1E6C27DA2@gmail.com> To: Mike Hearn X-Mailer: Apple Mail (2.1283) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: grabhive.com] X-Headers-End: 1VgJI9-0001pT-BJ Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Extending the Payment Protocol with vCards 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: Tue, 12 Nov 2013 19:06:27 -0000 Hi Mike, It seems to me there is some confusion about this. Taylor's talking = about a standard way to pass around data; the end user would never be = exposed to something like a "vCard". That vCard's existence itself would = in fact be very temporary. -wendell grabhive.com | twitter.com/hivewallet | gpg: 6C0C9411 On Nov 10, 2013, at 7:08 PM, Mike Hearn wrote: > It's great to see people thinking about payment protocol extensions. = I'm not totally convinced vCard support is the best idea relative to = social network integration - I can't recall the last time I saw someone = use a vCard. However, that should not hold you back from experimenting = or prototyping. All an extension requires is some tag numbers and we're = not in danger of running out of numbers any time soon. >=20