MIME-Version: 1.0
Sender: marek@palatinus.cz
In-Reply-To: <4EEB7E98.8030006@dot-bit.org>
References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
	<1323979147.27319.140661012141129@webmail.messagingengine.com>
	<4EEB7E98.8030006@dot-bit.org>
From: slush <slush@centrum.cz>
Date: Fri, 16 Dec 2011 20:54:35 +0100
Message-ID: <CAJna-HjXp4XEHnbmX0HKsMDmnxoWQQMmqujN+D9nLV0Zz_omcg@mail.gmail.com>
To: Khalahan <khal@dot-bit.org>
Content-Type: multipart/alternative; boundary=001517493b7c3f6a6c04b43afa99
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
Precedence: list

--001517493b7c3f6a6c04b43afa99
Content-Type: text/plain; charset=ISO-8859-1

Khalahan, honestly, using namecoin for aliases is (for me) clean example of
over-engineering. I mean - it will definitely work if implemented properly.
I played with a namecoin a bit (as my pool was the first 'big' pool
supporting merged mining), but I think there's really long way to provide
such alias system in namecoin and *cleanly integrate it with bitcoin*.
Don't forget that people who want to do lookup need to maintain also
namecoin blockchain with their bitcoin client. It goes against my instinct
of keeping stuff easy.

For example, yesterday I implemented HTTPS lookup for addresses into my
fork of Electrum client. I did it in 15 minutes, it works as expected, it
does the job and the implementation is really transparent, becuase
implementation is 20 lines of code. There's no magic transformation, no
forced "?handle=" parameters or whatever. And I don't care if somebody
provide URL
https://some.strange.domain/name-of-my-dog?myhandle=5678iop&anything_else=True

And everybody can do the same in their clients, in their merchant
solutions, websites or whatever. Everybody can do HTTPS lookup. But try to
explain DNS, Namecoin, IIBAN, email aliases to other programmers...

Those IIBAN - well, why not. At least I see the potential in PR. So far I
understand it as some teoretic concept which is not supported by anything
else right now. Give it few years until it matures and then add IIBAN alias
to Bitcoin client too.

Maybe I'm repeating myself already, but the way to go is to make aliases as
easy as possible, so everybody can implement it in their own solution and
thus practially remove the need of using standard bitcoin addresses for
normal users. Using some superior technology, which is hard to implement or
even understand won't solve the situation, because it will ends up with
some reference implementation in standard client only and nobody else will
use it.

slush

On Fri, Dec 16, 2011 at 6:23 PM, Khalahan <khal@dot-bit.org> wrote:

> **
> Namecoin is a peer-to-peer generic name/value datastore system.
> Don't forget it's not limited to .bit usage ! So, directly mapping things
> to .bit url would not be the optimal way of using namecoin.
>
>

--001517493b7c3f6a6c04b43afa99
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Khalahan, honestly, using namecoin for aliases is (for me) clean example of=
 over-engineering. I mean - it will definitely work if implemented properly=
. I played with a namecoin a bit (as my pool was the first &#39;big&#39; po=
ol supporting merged mining), but I think there&#39;s really long way to pr=
ovide such alias system in namecoin and *cleanly integrate it with bitcoin*=
. Don&#39;t forget that people who want to do lookup need to maintain also =
namecoin blockchain with their bitcoin client. It goes against my instinct =
of keeping stuff easy.<div>

<br></div><div>For example, yesterday I implemented HTTPS lookup for addres=
ses into my fork of Electrum client. I did it in 15 minutes, it works as ex=
pected, it does the job and the implementation is really transparent, becua=
se implementation is 20 lines of code. There&#39;s no magic transformation,=
 no forced &quot;?handle=3D&quot; parameters or whatever. And I don&#39;t c=
are if somebody provide URL <a href=3D"https://some.strange.domain/name-of-=
my-dog?myhandle=3D5678iop&amp;anything_else=3DTrue">https://some.strange.do=
main/name-of-my-dog?myhandle=3D5678iop&amp;anything_else=3DTrue</a></div>

<div><br></div><div>And everybody can do the same in their clients, in thei=
r merchant solutions, websites or whatever. Everybody can do HTTPS lookup. =
But try to explain DNS, Namecoin, IIBAN, email aliases to other programmers=
...<br>

<div><br></div><div>Those IIBAN - well, why not. At least I see the potenti=
al in PR. So far I understand it as some teoretic concept which is not supp=
orted by anything else right now. Give it few years until it matures and th=
en add IIBAN alias to Bitcoin client too.</div>

<div><br></div><div>Maybe I&#39;m repeating myself already, but the way to =
go is to make aliases as easy as possible, so everybody can implement it in=
 their own solution and thus practially remove the need of using standard b=
itcoin addresses for normal users. Using some superior technology, which is=
 hard to implement or even understand won&#39;t solve the situation, becaus=
e it will ends up with some reference implementation in standard client onl=
y and nobody else will use it.</div>

<div><br></div><div>slush<br><br><div class=3D"gmail_quote">On Fri, Dec 16,=
 2011 at 6:23 PM, Khalahan <span dir=3D"ltr">&lt;<a href=3D"mailto:khal@dot=
-bit.org">khal@dot-bit.org</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">

<u></u>

 =20
   =20
 =20
  <div bgcolor=3D"#ffffff" text=3D"#000000"><div><div class=3D"h5">
    Namecoin is a peer-to-peer generic name/value datastore system.<br>
    Don&#39;t forget it&#39;s not limited to .bit usage ! So, directly mapp=
ing
    things to .bit url would not be the optimal way of using namecoin.<br><=
br></div></div></div></blockquote></div></div></div>

--001517493b7c3f6a6c04b43afa99--