Thanks for your work on this - sounds great! I'm unfortunately too busy at the moment to give it a try - but I think this is a good step forward!
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/
domob wrote:Thanks for your work on this - sounds great! I'm unfortunately too busy at the moment to give it a try - but I think this is a good step forward!
It would be nice if someone could give it a try as I would like to claim the bounty.
nx.bit - some namecoin stats nf.bit - shortcut to this forum
Specifically what spec is this implementing to parse the id/ values? (I realize you gave example names, including mine, but this isn't really a substitute for a spec.)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy DyName: Dynamic DNS update client for .bit domains.
biolizard89 wrote:Specifically what spec is this implementing to parse the id/ values? (I realize you gave example names, including mine, but this isn't really a substitute for a spec.)
biolizard89 wrote:Specifically what spec is this implementing to parse the id/ values? (I realize you gave example names, including mine, but this isn't really a substitute for a spec.)
Well, frankly that spec is horrifyingly complex and has features for which I can think of no legitimate applications, so I certainly hope you didn't implement that entire spec. What I was asking was specifically which features from that spec you implemented. I.e. what fields does it check, etc.
It's also worth reminding everyone that that spec is pending revision.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy DyName: Dynamic DNS update client for .bit domains.
biolizard89 wrote:Specifically what spec is this implementing to parse the id/ values? (I realize you gave example names, including mine, but this isn't really a substitute for a spec.)
Well, frankly that spec is horrifyingly complex and has features for which I can think of no legitimate applications, so I certainly hope you didn't implement that entire spec. What I was asking was specifically which features from that spec you implemented. I.e. what fields does it check, etc.
It's also worth reminding everyone that that spec is pending revision.
No no, this is really simple. It just takes the 'gpg/fpr' field or if that is missing the 'fpr' field directly. Updated OP to include this.
At the bottom of the file there are some tests included that you can run with an instance active already.
nx.bit - some namecoin stats nf.bit - shortcut to this forum