NIP32 is not prescriptive about the content-field's content. On the other hand, label's were deliberately not made replaceable.
If in my application, the reasoning for a label was rather a long-form reason than what the examples in the nip showcase, should I link a NIP23 long-form article with a nostr:naddr, use markdown in a long-form style article or something else?
#askNostr
I would do an a-tag and an e-tag at the same time.
The a-tag allows clients to assign the label to the latest version of an event while the e-tag allows them to also show the past history if they have the exact event this was assigned to, or tell the user that the event has changed since the label was applied.
I'm not sure we are talking about the same thing. My use-case is wallet reviews. The subject of the label thus would be no a or e tag. I'm talking about the review itself being a long-form post. As nip32 is not explicit about the content supporting markdown, should I create long-form posts where markdown would be expected and link those from the content of my nip32 events or should I just go with long form in my nip32 event?
