Nostr devs: is the Tags array the right place to add app-specific metadata related to an event?

If so, is there a tag type for this? In the nips I see type “e”, “p”, “r”, and “g”. Is it reasonable to just use a new one?

If not, where should we encode application-specific metadata? Is it preferred to use a custom kind and e.g. json encode data in the content field?

Reply to this note

Please Login to reply.

Discussion

you can change nips however you want, just dont expect anyone to follow and you might need a custom relay

Intending to keep these on an application-specific relay, but it’s always possible the events get xposted to public relays; in that case I’d like to ensure the events aren’t problematic

its nice but problematic events have and do occur, the relays and clients handle it and why you will likely need a modified relay

changing things is good and how nips are created and nostr advances

Single letter tags are meant to be indexable. If you don’t need that just use any tag longer than that.

Even better, make it interoperable so other apps can use the same data.

Tags only allow strings btw.

What do you need application specific metadata for? Usually a new kind is a better idea. You might also consider kind 30078 for storing application-specific data https://github.com/nostr-protocol/nips/blob/master/78.md