Replying to Avatar Vitor Pamplona

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.
Avatar
Leo Wandersleb 2y ago

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?

Reply to this note

Please Login to reply.

Discussion

No replies yet.