Ok. I’ll meet you half way.
Carrots over sticks.
Using a standardized way to reference NIPs (via NIP 73) assures that “your reaction” and “your comment” (ect…) will be available for a wider audience of “nip reviewers” (and robots) … cause the reference ITSELF is tagged with “nip”. It’s the easiest way!
As it stands, NIP 73 style “external references” are only available when publishing reactions as kind 17 events.
Go ahead. Put an e tag on it. I’ll even add this as a “suggestion” in the proposed spec for referencing NIPs.
Everybody wins. 🔥
Login to reply
Replies (1)
I want to take a step back and consider a bigger question. It’s related and I don’t know the answer.
Currently, a wiki entry or nip nip can be edited by the event author. So how can we enable the community to edit an existing NIP?
One way would be something like git versioning, where your WoT decides what gets merged, but idk if that can work and even if it can, we’re far from ready to implement it.
So here’s another idea. Take NIP-73 as an example. Take the existing version and express it using the nip nip. But we don’t copy the whole thing verbatim. Instead, we replace the table of Supported ID Types with a Decentralized List, one for each type. Each list item adds a row to the table and maybe also includes a corresponding explanation and example.
So when it comes time for you to propose support for NIPs, you simply add another item to the list of supported types.
The complexity would be we’d need a script to ingest the curated list and spit out a markdown file. We’d have to figure out how to make that work.
And we will need to implement vanilla list curation first.