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; 
MIME-Version: 1.0
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
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
Precedence: list

--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">&lt;<a href=3D"mailto:da2ce7@gmail.com" target=3D"_blank">da2=
ce7@gmail.com</a>&gt;</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>&gt; I&#39;m confused about the problem we&#39;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&#39;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&#39;s a<b=
r>
lot of momentum behind those projects. Namecoin by contrast, could die<br>
tomorrow. And it isn&#39;t a big deal that they&#39;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--