summaryrefslogtreecommitdiff
path: root/74/955f5f92f624c29af5e62ae24ba332a791929a
blob: bcbc34f32466ed6cbded67be4928f0e41c474699 (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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <zellfaze@yahoo.com>) id 1RaF6h-0008EW-KT
	for bitcoin-development@lists.sourceforge.net;
	Mon, 12 Dec 2011 23:16:27 +0000
X-ACL-Warn: 
Received: from nm31-vm0.bullet.mail.ne1.yahoo.com ([98.138.229.40])
	by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
	id 1RaF6g-0000Dm-Qa for bitcoin-development@lists.sourceforge.net;
	Mon, 12 Dec 2011 23:16:27 +0000
Received: from [98.138.90.57] by nm31.bullet.mail.ne1.yahoo.com with NNFMP;
	12 Dec 2011 23:16:21 -0000
Received: from [98.138.88.235] by tm10.bullet.mail.ne1.yahoo.com with NNFMP;
	12 Dec 2011 23:16:21 -0000
Received: from [127.0.0.1] by omp1035.mail.ne1.yahoo.com with NNFMP;
	12 Dec 2011 23:16:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 649122.75442.bm@omp1035.mail.ne1.yahoo.com
Received: (qmail 46030 invoked by uid 60001); 12 Dec 2011 23:16:21 -0000
X-YMail-OSG: l4nGnYIVM1mq12xVQUepgmnzmgW2uLpSE0Qe36Ez2.2SWAX
	0aeIrT9sXgJueOVUh.1SyUMiPxl60SQcgbxGf4Cnev1iiLrTnGar2cCZ5gT.
	Ml32gtxe9NXLzyjDx0t.U6jEIN32iHRt5f7WgFLY9N7tUPBiEFtdqLoLhDvI
	ggSWC.RNgu3dh9xSMvqFV0UjACAv5vnxbp0LY27jPeEWjvGgVZXIOg2hUTEv
	Ayd6tMV59GFcStLcnIfBOzEvcnauvynIniCjtgpnK8T4z4UFUBWRywD73fMI
	UZfpV4kEpN7a8SVv0NtwYw7UOsuSUvTw8gnZvxjqdTLN9nHw1n4Idc2jXxSP
	R6MBcXCL6p97zdzncbhPpDkIFC2a6ilh9pa11OOyvCsqXZ9K1ncB4_THlt4S
	IWbG1enWISFG5roolSNsJqR3eKSXoIeBmn8pfL0lzLzAy8jF3U87BSIAhau7 39nQ-
Received: from [108.8.7.210] by web120920.mail.ne1.yahoo.com via HTTP;
	Mon, 12 Dec 2011 15:16:21 PST
X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698
Message-ID: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
Date: Mon, 12 Dec 2011 15:16:21 -0800 (PST)
From: Zell Faze <zellfaze@yahoo.com>
To: bitcoin-development@lists.sourceforge.net
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(zellfaze[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
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [98.138.229.40 listed in list.dnswl.org]
X-Headers-End: 1RaF6g-0000Dm-Qa
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
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: Mon, 12 Dec 2011 23:16:27 -0000

I agree with Luke-Jr.  We need to try to find a decentralized solution if we are going to implement BIP 15.  Bitcoin needs to remain decentralized in every aspect of the protocol or we lose its greatest strength.

I feel like the HTTPS idea would be a great idea for a client feature, but not really something that should be added to the protocol.

--- On Mon, 12/12/11, Luke-Jr <luke@dashjr.org> wrote:

> From: Luke-Jr <luke@dashjr.org>
> Subject: Re: [Bitcoin-development] [BIP 15] Aliases
> To: bitcoin-development@lists.sourceforge.net, "Amir Taaki" <zgenjix@yahoo.com>
> Date: Monday, December 12, 2011, 5:32 PM
> FirstBits looks nice at glance, but
> is bound to create a gold-rush to grab 
> every nice-looking FirstBits address.
> 
> HTTPS is only as secure as the (centralized) CAs, thus not
> really any better 
> than TXT records.
> 
> I don't think an address of some form is avoidable.