NIP-31!!!
Imagine if the template your app creates even generates a gorgeous card for the NIP-31 opengraph and your not-9802-supporting-client just renders that.
Context was the missing piece to make this work and NIP-31, specially with the template idea, provides all the context, and with NIP-89, you can even find how to consume the unsupported content (i.e. if it's a podcast open fountain, etc)
I think this is more or less what I had in mind
It would enable a far more interesting internet with more niche use cases
nostr:naddr1qvzqqqr4gupzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqy88wumn8ghj7mn0wvhxcmmv9uqpqvecd96nvar5de4nv7nhxdmkgeqfea8mz
Thread collapsed
Thread collapsed
Sure, but why can't you do NIP-31 with Comments themselves? If the answer is NIP-31, you can just NIP-31 everything, including Comments.
hmmm, because they wouldn't be rendered? because they are a different kind? we're talking in circles but I think now on the github issue we've arrived to a conclusion
Thread collapsed
Thread collapsed