i think it would have been extremely helpful to discuss beforehand as prehaps updating the spec and existing apps may be beneficial. this NIP was discussed and changed several times before it was merged. maybe we overlooked an additional use case and it could be updated once again if this is deemed better.
Login to reply
Replies (2)
nostr:note1lmeucqh2t9y2xusmsmz7rs3mj5h6jwdz5ulxxcy0qaynya9g8mjqsve4jl
this is a breaking change for the sake of a breaking change. to the protocol, tags, content, they are the same.
this can be implemented in a nonbreaking and forward/backward compatible way by just adding a “transcription” tag