4 ms·
I also like the idea of Keybase.io, though I wish it was based on something a little more decentralized. The unfortunately-named WebFist looks cool: http://www
by epaulson 13y ago
I also like the idea of Keybase.io, though I wish it was based on something a little more decentralized. The unfortunately-named WebFist looks cool:
http://www.onebigfluke.com/2013/06/bootstrapping-webfinger-with-webfist.html http://www.onebigfluke.com/2013/06/bootstrapping-webfinger-w...
- jnbiche 13y agoHave you checked out OneName? It runs on the Namecoin blockchain, so it's quite decentralized. I've not actually tried it yet, but it looks pretty damn cool. https://onename.io/ https://onename.io/
- riffraff 13y agoplease correct me if I'm wrong, but I think this is not really decentralized. It's a single authority that owns a namespace in namecoin and is giving out sub-names. It's decentralized in the same way a twitter account is.
- jnbiche 13y agoNo, you're wrong. It's entirely decentralized. Have a look at the spec: https://github.com/onenameio/onename https://github.com/onenameio/onename Anyone running a full Namecoin node (ie, anyone running Namecoin client) can register an identification. OneName is providing a convenient web portal to this key-value store on Namecoin, so their business model is somewhat analogous to Blockchain.info's (or perhaps they have another business model in mind, who knows?).
- vertex-four 13y agoNobody can own namespaces. They're "just" acting as a middleman for buying names in Namecoin in a namespace they've defined themselves, but anyone could bypass them and buy their own names in that namespace. The annoying thing is, we already have a namespace for identities, it's standardised and documented on the wiki. They came in and defined their own namespace for no good reason.
- rakoo 13y agoThen 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?
- larrysalibra 13y agoAnd unlike keybase's "it's complicated so it must be good" proofs, onename's proofs are easy -> add a pointer from your onename namespace to your social media property and a pointer back to onename to prove you own it. No need to generate signatures that break when anything changes. https://onename.io/larry https://onename.io/larry https://keybase.io/larry https://keybase.io/larry