From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RbdsA-0002yD-5s for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 19:55:14 +0000 X-ACL-Warn: Received: from mail-ey0-f175.google.com ([209.85.215.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rbds8-0001kr-QY for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 19:55:14 +0000 Received: by eaal1 with SMTP id l1so4690550eaa.34 for ; Fri, 16 Dec 2011 11:55:06 -0800 (PST) Received: by 10.204.145.74 with SMTP id c10mr3302416bkv.62.1324065306405; Fri, 16 Dec 2011 11:55:06 -0800 (PST) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.204.168.15 with HTTP; Fri, 16 Dec 2011 11:54:35 -0800 (PST) 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 Date: Fri, 16 Dec 2011 20:54:35 +0100 X-Google-Sender-Auth: N6AD_rTWx1IqEBmDPFk2EP9SdXs Message-ID: To: Khalahan Content-Type: multipart/alternative; boundary=001517493b7c3f6a6c04b43afa99 X-Spam-Score: 1.6 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message 0.6 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rbds8-0001kr-QY Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] [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: Fri, 16 Dec 2011 19:55:14 -0000 --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 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 'big' po= ol supporting merged mining), but I think there's really long way to pr= ovide 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 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's no magic transformation,= no forced "?handle=3D" parameters or whatever. And I don't c= are if somebody provide URL https://some.strange.do= main/name-of-my-dog?myhandle=3D5678iop&anything_else=3DTrue

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= ...

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.

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 b= itcoin addresses for normal users. Using some superior technology, which is= hard to implement or even understand won'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.

slush

On Fri, Dec 16,= 2011 at 6:23 PM, Khalahan <khal@dot-bit.org> wrote:
=20 =20 =20
Namecoin is a peer-to-peer generic name/value datastore system.
Don't forget it's not limited to .bit usage ! So, directly mapp= ing things to .bit url would not be the optimal way of using namecoin.
<= br>
--001517493b7c3f6a6c04b43afa99--