3 ms·
Then again, why not use namecoin ? They (we ?) have a spec with what format your records should look like: https://wiki.namecoin.info/index.php?title=Identity
by rakoo 13y ago
Then again, why not use namecoin ? They (we ?) have a spec with what format your records should look like:
https://wiki.namecoin.info/index.php?title=Identity https://wiki.namecoin.info/index.php?title=Identity
Basically, there's a whole id/ namespace where you register your personal information, and there's a d/ namespace where you register domain names (akin to DNS). Onename is the same except they use i/ (they haven't even tried to discuss it and basically did it all from scratch to start clean)
The major problem is that you basically need a namecoin client to interact with the data... unless you use dnschain [0], which act as a HTTP-to-Namecoin and DNS-to-Namecoin bridge. Try this:
$ dig @dns.dnschain.net otokar.bit
$ curl http://dns.dnschain.net/d/otokar http://dns.dnschain.net/d/otokar
both are my personal domain, delivered to you through plain old protocols. The last one even works in your browser !
Come and join us, this is actually the future. Oh and by the way I'm id/rakoo.
[0] https://github.com/okTurtles/dnschain https://github.com/okTurtles/dnschain
- voltagex_ 13y ago>You have asked Firefox to connect securely to wiki.namecoin.info, but we can't confirm that your connection is secure.
- itistoday2 13y agoLooks like they didn't pay protection money to a CA. Huh.
- SideshowBobb 13y agoDoesn't putting the namecoin blockchain on a remote server and then using the traditional DNS system to interact with the remote Namecoin DNS system completely defeat the purpose of Namecoin DNS?