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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <da2ce7@gmail.com>) id 1RaO95-0005Wz-MW
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 08:55:31 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=da2ce7@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1RaO94-0007sR-M6
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 08:55:31 +0000
Received: by wgbds1 with SMTP id ds1so12281240wgb.10
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Dec 2011 00:55:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.20.134 with SMTP id n6mr25246215wie.49.1323766524085; Tue,
13 Dec 2011 00:55:24 -0800 (PST)
Received: by 10.216.18.212 with HTTP; Tue, 13 Dec 2011 00:55:23 -0800 (PST)
In-Reply-To: <9109000381434268897@unknownmsgid>
References: <9109000381434268897@unknownmsgid>
Date: Tue, 13 Dec 2011 08:55:23 +0000
Message-ID: <CAACjpwJnZPEnLtxbGeaOvdxjTekEkWEkTcXG30-Jfsqt2hacZg@mail.gmail.com>
From: Cameron Garnham <da2ce7@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=bcaec53d584b6f063904b3f569a0
X-Spam-Score: 0.8 (/)
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
(da2ce7[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (da2ce7[at]gmail.com)
1.3 URI_HEX URI: URI hostname has long hexadecimal sequence
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: 1RaO94-0007sR-M6
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 08:55:31 -0000
--bcaec53d584b6f063904b3f569a0
Content-Type: text/plain; charset=UTF-8
Namecoin makes sense; as we can use the same private keys to spend the
namecoin as spending the bitcoins.
Namecoin happens to be the only secure guaranteed global unique human
rememberable string system that exists.
I suggest that sending bitcoins to a namecoin name is the way to go...
It makes even more sense since namecoin started merged mining.
On 13 December 2011 08:03, Cameron Garnham <da2ce7@gmail.com> wrote:
>
> Sent from my Windows Phone
> De: Amir Taaki
> Enviado: 13/12/2011 0:43
> Para: bitcoin-development@lists.sourceforge.net
> Asunto: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
> > 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
>
>
>
> ------------------------------------------------------------------------------
> Systems Optimization Self Assessment
> Improve efficiency and utilization of IT resources. Drive out cost and
> improve service delivery. Take 5 minutes to use this Systems Optimization
> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Cameron Garnham:
email: da2ce7@gmail.com
website: http://da2ce7.blogspot.com
telephone: +61405227831
--bcaec53d584b6f063904b3f569a0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p>Namecoin makes sense; as we can use the same private keys to spend the<b=
r>namecoin as spending the bitcoins.</p><p>Namecoin happens to be the only =
secure guaranteed global unique human<br>rememberable string system that ex=
ists.</p>
<p>I suggest that sending bitcoins to a namecoin name is the way to go...<b=
r>It makes even more sense since namecoin started merged mining.<br><br></p=
><div class=3D"gmail_quote">On 13 December 2011 08:03, Cameron Garnham <spa=
n dir=3D"ltr"><<a href=3D"mailto:da2ce7@gmail.com" target=3D"_blank">da2=
ce7@gmail.com</a>></span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
<br>
Sent from my Windows Phone<br>
De: Amir Taaki<br>
Enviado: 13/12/2011 0:43<br>
Para: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net" target=
=3D"_blank">bitcoin-development@lists.sourceforge.net</a><br>
Asunto: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases<br>
<div>> I'm confused about the problem we're trying to solve.<br>
<br>
</div><div>I was in brmlab and wanted to pay 1 BTC for a Club Mate. They ha=
d on<br>
the wall a picture of their QR code and a bitcoin address. I don't own<=
br>
a mobile phone so the QR code is<br>
useless. Then I remembered FirstBits, went to my terminal and typed<br>
1brmlab. I got their bitcoin address from the website and copied that,<br>
then opened my terminal and pasted that in to send 1 BTC.<br>
<br>
</div><div>And<br>
these proposals for Namecoin, would make bitcoin implementations<br>
dependent on unproven technology. HTTPS/DNSSEC have been around a long<br>
time and are responsible for many mission critical systems. There's a<b=
r>
lot of momentum behind those projects. Namecoin by contrast, could die<br>
tomorrow. And it isn't a big deal that they're centralised. This is=
a<br>
convenience for end users and does not affect the core system much.<br>
<br>
tl;dr: usability<br>
<br>
<br>
</div><div><div>-----------------------------------------------------------=
-------------------<br>
Systems Optimization Self Assessment<br>
Improve efficiency and utilization of IT resources. Drive out cost and<br>
improve service delivery. Take 5 minutes to use this Systems Optimization<b=
r>
Self Assessment. <a href=3D"http://www.accelacomm.com/jaw/sdnl/114/51450054=
/" target=3D"_blank">http://www.accelacomm.com/jaw/sdnl/114/51450054/</a><b=
r>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Cameron Gar=
nham:<br>email: <a href=3D"mailto:da2ce7@gmail.com" target=3D"_blank">da2ce=
7@gmail.com</a><br>website: <a href=3D"http://da2ce7.blogspot.com" target=
=3D"_blank">http://da2ce7.blogspot.com</a><br>
telephone: <a href=3D"tel:%2B61405227831" target=3D"_blank" value=3D"+61405=
227831">+61405227831</a><br>
--bcaec53d584b6f063904b3f569a0--
|
