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:
And 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.
please 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.
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?).
Nobody 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.
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
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