Replying to Avatar Vitor Pamplona

I love nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s and all his work to lead Nostr into the huge ecosystem we have today.

However, he is wrong about NIP-94.

NIP-94 was discussed for 2 months, agreed and merged. Amethyst is just implementing the consensus. I am not the one going sideways to implement my own way of doing things.

This is so misleading. Just because the nip was merged doesn’t mean it was meant to replace inline images

nostr:note1y7gvpksvt579am3gwegfpcpe445whqxn64gu8cv8ygpuku20m7sqpzjesv

Reply to this note

Please Login to reply.

Discussion

This is the same way we quote everything else. Polls, Long form content, other Kind 1s... It's still in spec.

Kind 1s don't require inline images.

Let’s all reread the ‘Client Behavior’ session & the 'Suggested Use Cases'..

So, say, what don’t we understand in all this ??

https://github.com/nostr-protocol/nips/blob/master/94.md

There could have been talk about web-SRI inside the NIP94 spec

https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity

Let's not reinvent the wheel when it could already be offloaded to the browser.