Replying to Avatar Laeserin

At any rate, isn't a label a particular type of tag structure? With a defined namespace?

And a highlight is an event that refers to another event or a URI. It uses a tag, but that's not the point of the NIP. The point is the specified selection.

The problem is less consolidation than a lack of process architecture. There could be a tag, with labels and highlights beneath it. A level down.
Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

yes, nip-32 is literally a kind of tag structure beyond the tags

you wouldn't need the event tags field if you just used labels instead

instead of publishing an event with tags you would publish the event and then the label for the tags tied to the event

it's simpler, and the whole history of protocols shows that this is the right approach and eventually complicated shit like events with tags gets overwritten by a simplified event without tags and a separate label

Reply to this note

Please Login to reply.

Discussion

Avatar
Laeserin 1y ago

Well, that would be a breaking change to NIP-01 and NIP-10, tho, among many others. Almost a Nostr v2.0.

But I don't understand the topic enough, to know if that would be an improvement, or not. Would have the benefit of never having to change the core event structure. Just have different label configs.