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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <nanotube@gmail.com>) id 1RaITP-0002oc-QH
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 02:52:07 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.47 as permitted sender)
client-ip=209.85.214.47; envelope-from=nanotube@gmail.com;
helo=mail-bw0-f47.google.com;
Received: from mail-bw0-f47.google.com ([209.85.214.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RaITP-0000Xj-19
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 02:52:07 +0000
Received: by bkbzt4 with SMTP id zt4so8790430bkb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 12 Dec 2011 18:52:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.205.131.16 with SMTP id ho16mr8951187bkc.105.1323744720688;
Mon, 12 Dec 2011 18:52:00 -0800 (PST)
Received: by 10.205.83.66 with HTTP; Mon, 12 Dec 2011 18:52:00 -0800 (PST)
In-Reply-To: <1323743826.16120.YahooMailNeo@web121003.mail.ne1.yahoo.com>
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>
<1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com>
<CAHY2ayB_36VyKF1HfCf3oGNJB7FGGidXidsbLP=HXMzdbnyWDg@mail.gmail.com>
<1323743826.16120.YahooMailNeo@web121003.mail.ne1.yahoo.com>
Date: Mon, 12 Dec 2011 21:52:00 -0500
Message-ID: <CAHY2ayBUZjh3UNwgc8AcgLXJF+EQjPsWR2XpvTJRqfJAm=jkyw@mail.gmail.com>
From: Daniel F <nanotube@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(nanotube[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1RaITP-0000Xj-19
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: [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: Tue, 13 Dec 2011 02:52:07 -0000
On Mon, Dec 12, 2011 at 9:37 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> lol, way to miss the point nanotube.
>
> FirstBits *is* useless, but not for the reasons you specified. But simply=
because the resources it needs rises exponentially as the number of partic=
ipants in the network grows linearly.
>
> The point is that if FirstBits were built into the implementation, that w=
ould allow me to simply send to 1brmlab. The proposal here is not for a web=
site where people can lookup bitcoin addresses, but a shared naming scheme =
between bitcoin implementations. Here's the story again:
well, it's easy to miss the point when the example you use doesn't
make the point you think you're making. :D
but ok, yes, it would be nice to send directly to something like
1brmlab from the client. i suppose figuring out how to make sure that
1brmlab actually does send to whom you think it sends, is left to the
details of implementation, but that's a separate question.
|
