Rework of Identity wiki page

Post Reply
domob
Posts: 1129
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Rework of Identity wiki page

Post by domob »

I've reworked the id/ wiki page (https://github.com/namecoin/wiki/wiki/Identity) a bit to bring it up to date with the current version of id/ I have in mind. What do you guys think about it? I still have to write up the GPG fingerprint specs, which are basically those defined in the "Personal Namespace" page (but I think they should be part of the Identity page). Two things that came to my mind while working through it:
  • Why are not at least dashes also allowed for characters? I think we should allow them (as for domains). And what about internationalised names like the IDN domains? I think this makes sense to allow for names in foreign languages, ideally with the same IDN syntax (so that implementations can use the same code, for instance in libnmcrpc).
  • Can anyone who knows more about MediaWiki than I do check why there are display problems whenever a square bracket is part of an example code block? It is surely something stupid, but I have no idea how to fix it.
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

Ben
Posts: 65
Joined: Fri Dec 20, 2013 2:22 pm
os: linux

Re: Rework of Identity wiki page

Post by Ben »

I fixed the square brackets.

I agree that dashes should be allowed. Why restrict id/ at all? Why not allow everything, including unicode?
N9kVqK8zrgtHvD6kD4yk3UgM2dkP2NykDr

domob
Posts: 1129
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Re: Rework of Identity wiki page

Post by domob »

Ben wrote:I fixed the square brackets.

I agree that dashes should be allowed. Why restrict id/ at all? Why not allow everything, including unicode?
Thanks for the fix! I expected that using the "code environment" with indentation would already switch off markdown interpretation. I also tried '\[' to escape the square brackets, but it didn't work. :) Thanks!

I think we should use IDN encoding for Unicode names instead of "plain" Unicode strings (they would have to be encoded anyway, maybe in UTF-8, but then I think it is best for compatbility to use only ASCII chars for encoding--and IDN is something which is already used for domains anyway).
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

Post Reply