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 ) 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 ; 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: From: Cameron Garnham 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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

Namecoin makes sense; as we can use the same private keys to spend thenamecoin as spending the bitcoins.

Namecoin happens to be the only = secure guaranteed global unique human
rememberable string system that ex= ists.

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 <da2= ce7@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 ha= d on
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
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-de= velopment



--
Cameron Gar= nham:
email: da2ce= 7@gmail.com
website: http://da2ce7.blogspot.com
telephone: +61405227831
--bcaec53d584b6f063904b3f569a0--