This is why I made NIP 32 labels, in order to classifybthings without tons of new kinds using user-provided labels. It hasn't worked out in practice so far, but I still think it's a better primitive because you can content-address individual endorsements.
In the context of decentralized technology there is a lot of gaps to bridge, as they are all context-specific
What we lack on Nostr is effective consensus mechanisms. When we can achieve decentralized consensus, we can achieve everything else.
The foundation of a Web of Trust is lists. Lists are the building block. On Nostr, this is NIP-51, which is why we now have sets of lists, kind 30000.
Even a few hours ago Pablo and Fiatjaf were considering wiki relay list management with yet another NIP-51 kind, and Pablo noted how NIP-51 could become bloated, assuming I interpreted their conversation correctly. I believe this trend will continue until NIP-51 lists become the foundation of the protocol. Sets of lists was an important step.
The rest isn't easy, but it will be rewarding.
nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3
Discussion
IMO you can remove tags from events and replace them with labels
i am betting that long term this will be a trajectory of change of the protocol, eliminate complexity and increase layering
I don’t understand how to use NIP 32 because I don’t know how namespaces are supposed to work. I need an example.
Is there supposed to be an endpoint at ontology.coracle.social?