Grateful, for any constructive feedback, including suggestions on a different method for performing something similar.

Reply to this note

Please Login to reply.

Discussion

Then maybe you need to see if the versions match so you need to write the version somewhere

Versions have an eventID. We can compare that and fallback on the `a` tag, otherwise, and display an info.

Versioning could be handled by the metadata event nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 suggested 🤔

What is being versioned here? The entire tree structure?

Individual events in the tree, I think.

Can't relays choose to version them (or not)? Histories is outside of the scope of this NEP.

Yeah I agree it's outside scope. But if we wanted to add versioning, I think metadata would be the way to do it.

Okay. We can add that as a MAY suggestion.

i think leave versioning out of the spec for now, to build a versioning scheme for it is a whole other can of wriggly worms

Yeah, totally blows up the spec.