pull down to refresh
Cool! Would love to hear more about how you think they'll work together.
FWIW, I actually don't think the current NIP5 identification system is bad. Probably better if anchored in Bitcoin, but doesn't seem like a hair on fire problem. At least not yet.
reply
It's actually quite easy
The web was created by adding hyperlinks (http://) in documents
The URI is the abstraction of the http: hyperlink
So, if you have another system to http (allowed and encouraged) you put those hyperlinks in your documents. In this case, JSON.
So add nostr: links in your json, or "nostr": <key> for example allows interop
And vice versa. This is all by design
reply
deleted by author
deleted by author
deleted by author
I laid part of the ground work for the creation of DIDs and it's at least 300 pages of reading, but more likely 3,000 pages to understand what you need to know
They dont even realize that all their canonical data types are buried in an obscure XML document from 2000. There's undoubtedly some good bits in there, but a lot of technical debt. Which is always swept under the carpet. It will come back to bite
I am however of the conclusion that it's worth trying, and might be useful, down the road. Actually for something completely different which is diverse checkpointing, but that's another story.
Nostr in contrast is 3 pages and you are off to the races
BTW is not 5 years of bike shedding, it's more like 20