If there is a good use case and it is really needed, it can be offered for sure. The problem I have is that I am wasting a ton of time on implementing something just to start over to implement some other hype. This is just wasting time and effort, instead of trying to innovate and find a better approach. Content hashes do exist, and if that is needed, it can be done 🐶🐾🫡 

 100% agree, that's why I'm saying offering this as nip96 option (even if paid, restricted etc) could serve those use cases, and I'm guilty as anyone in digging hyped stuff without looking through existing NIPs first. And you sure didn't waste time implementing nip96, it seems to be quite good, even if a bit too verbose for my taste. 

 There is a PR now to simplify it. Please submit a PR that will request immutability of the media. Also allow for the host to reject the upload based on presence of private metadata and viruses/exploits. Once you have it in, I will make sure to comment and implement once it’s merged 🐶🐾🫡 

 Deal, thank you! 

 https://github.com/nostr-protocol/nips/pull/1236
Is the PR I talked about 🐶🐾🫂🫡