Namecoin Forum

I think some of the types you've listed are unnecessary. That's fine - the spec shouldn't care at all about how many types can be used, becase applications and users should be able to add their own on the fly. The only purpose of registering them at all is for improved coordination between applicat...

Onename are also doing some verifications of websites & social media profiles. We need a way to store these verifications (and others), along with the identity of the verifier. I think that might be best done in a new namespace. I had some thoughts about a more-general solution for that before. Thi...

It looks like you've missed out an url for a public key. The current id spec allows a gpg fingerprint & an url to link to your public key. Why would you need a url to a public key if the fingerprint is specified? The essential information that needs to be stored in this record is the association be...

One thing the onename guys have that is missing in id & justusranvier's proposal is social network profiles. I don't understand why you would say that is missing from this proposal: https://github.com/opennamesystem/openspecs/commit/82ede24eb896faec83e4ecdc913a7438859dfcdb#diff-fcf6a5ef3b924df8ae29...

I've written a reply to the ONS specification on GitHub but it's equally relevant to this project. Even if NamecoinID uses a different namespace than Onename, it would be highly beneficial if both namespaces could use the same specification. https://github.com/opennamesystem/openspecs/commit/82ede24...

I'd like so see some improvements from the u/ namespace merged into the id/ namespace as well.

Linked lists to extend the maximum amount of data that can be stored is a good idea.

Adding a site field that collects (URL,username) tuples would be a better way to store the same data as onename.io.

https://wiki.namecoin.info/index.php?title=Identity Taking a look at the at the specification for the id/ namespace, I can see some things that could be improved. name should be capable of being specified as an array, just like email birthdate should be in ISO-8601 format weblog should be capable of...