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.
Discussion
nostr:note1lmeucqh2t9y2xusmsmz7rs3mj5h6jwdz5ulxxcy0qaynya9g8mjqsve4jl
okay. are you using the same event kind? perhaps it makes sense for all apps to make these changes and choose to not show the content if they want to only show the link audio.
we've need to loop in all of the other app devs that we'd be talking about breaking changes as this would completely break old events and they would no longer show audio. maybe some regex kung-fu could be used to band-aid fix them on the client side.
maybe you could submit a PR to NIP-A0 and we can begin this discussion?
Not using the same kind, but the note structure is the same except for that change. It is what it is. You can still sign in with your key and connect to any relay, which is already better than Primal.
so you made a similar app to existing apps and features, but decided to NOT use the same event kind?
that's like making a photo feed app and not using kind:20 images in it because you wanted to add a new feature.
im trying really hard to understand and to work with you so we can keep app interoperability and compatability here for the betterment of nostr.
Putting a massive amount of text in a tag feels awfully awkward. We decided to make a new NIP for Airchat. If apps don’t want to support it, they don’t have to. Simple as that.
nostr has such an amazing chance to do something that no other social system has ever done, allowing developers to work together and build independantly. for that vision to come true, developers need to actually want to work together.
we have the opportunity to make this meme continue to be a reality or make it a laughable joke of the past. https://xkcd.com/927/
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