summaryrefslogtreecommitdiff
path: root/33/097ea8f99a2bcd317b23f79c10b58062d64333
blob: 646c031863842030dec2bccaeb274cee5c372171 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <zgenjix@yahoo.com>) id 1RaGS1-0002Yn-Jq
	for bitcoin-development@lists.sourceforge.net;
	Tue, 13 Dec 2011 00:42:33 +0000
X-ACL-Warn: 
Received: from nm19-vm2.bullet.mail.ne1.yahoo.com ([98.138.91.95])
	by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76)
	id 1RaGRz-0004YO-Dq for bitcoin-development@lists.sourceforge.net;
	Tue, 13 Dec 2011 00:42:33 +0000
Received: from [98.138.90.55] by nm19.bullet.mail.ne1.yahoo.com with NNFMP;
	13 Dec 2011 00:42:26 -0000
Received: from [98.138.89.171] by tm8.bullet.mail.ne1.yahoo.com with NNFMP;
	13 Dec 2011 00:42:26 -0000
Received: from [127.0.0.1] by omp1027.mail.ne1.yahoo.com with NNFMP;
	13 Dec 2011 00:42:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 249148.15190.bm@omp1027.mail.ne1.yahoo.com
Received: (qmail 83429 invoked by uid 60001); 13 Dec 2011 00:42:26 -0000
X-YMail-OSG: eq3rHfcVM1l2GfhA8wz1BRGGmJfrbMam.cS8SXNVjNvkr_b
	7fYIdylFP3HUlqqqdSebB4pwvWDN2NA48CKb0Oy5BK0HbkjvABoLss5CsTeF
	iH67nxfxDUbV3D3Ejmp_XUFVi1g6sJvZcbobgNHU86p7BhKvJUrO5o_MvpAw
	f716pwi0sKa34OuaTeduI9.EGGQV7VzRsE7yKmU2r_cAnqoA717XcgXkHLvn
	qIX10UZ9ZAcZsCNUdvzqNcDLpZuIJB6V8G9Qngx9UrO.7si1T7qbzdwsZ3.q
	lwOm0kZ.QrxgFHF.SatqxCB5OGN8Urpt05u3qdZAaSwwx0zNDW2qNoo1wEc1
	Fc0_4Brcm.T3VRMHyVPShi1.K0UuWm6fiU6K5wxjsoBOza7x5eFHxp52H7ez g
Received: from [92.20.180.200] by web121001.mail.ne1.yahoo.com via HTTP;
	Mon, 12 Dec 2011 16:42:26 PST
X-Mailer: YahooMailWebService/0.8.115.331698
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
	<CAGQP0AGvq603oshSGiP79A+gqDqW_hHG+qZjaZccCmo+gd3W2A@mail.gmail.com>
	<201112121841.39864.luke@dashjr.org>
	<CAGQP0AGBKKEqhaJZj-Rw400AjrVHE9_EMve=RWdqoaOaDsTgtw@mail.gmail.com>
	<CAGQP0AGY32QP=rXyGftb5NbHA7fhcCne7W=pt5+onXp1Jbm98Q@mail.gmail.com>
Message-ID: <1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com>
Date: Mon, 12 Dec 2011 16:42:26 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CAGQP0AGY32QP=rXyGftb5NbHA7fhcCne7W=pt5+onXp1Jbm98Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -2.4 (--)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [98.138.91.95 listed in list.dnswl.org]
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(zgenjix[at]yahoo.com)
	-2.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	-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: 1RaGRz-0004YO-Dq
Subject: Re: [Bitcoin-development] Fwd:  [BIP 15] Aliases
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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 00:42:33 -0000

> I'm confused about the problem we're trying to solve.

I was in brmlab and wanted to pay 1 BTC for a Club Mate. They had on the wall a picture of their QR code and a bitcoin address. I don't own a mobile phone so the QR code is 
useless. Then I remembered FirstBits, went to my terminal and typed 
1brmlab. I got their bitcoin address from the website and copied that, 
then opened my terminal and pasted that in to send 1 BTC.

And 
these proposals for Namecoin, would make bitcoin implementations 
dependent on unproven technology. HTTPS/DNSSEC have been around a long 
time and are responsible for many mission critical systems. There's a 
lot of momentum behind those projects. Namecoin by contrast, could die 
tomorrow. And it isn't a big deal that they're centralised. This is a 
convenience for end users and does not affect the core system much.

tl;dr: usability