indeed it is
Discussion
Ahh hmm y'all making me think was such a nostr.build manual head throughout this time
Suggestions for the copy? I don't know what's misleading about it.
I think it’s misleading to say nostrimg can change the content of your image, when the url to the image contains a hash of the content you uploaded
Hash urls don't mean that the file you are being provided matches the hash. Most of the time it's just a way to get a unique URL. And since we generally don't know how the hash is computed clients don't implement the verification. Also, it will be hard to clients to implement every single hashing procedure out there.
Anyway... the fact that you are pinging a hashed URL doesn't mean the server is replying with something that matches it.
from a purely technical standpoint I agree with your points, but from a community standpoint - I don’t. I appreciate the zero trust and verification, but I also think it’s important to “play well” in this new ecosystem. I guess the language in these warnings rubs me the wrong way. I’m not much of a copywriter though so I don’t have any suggestion for you. most I can do is share my feedback.
just a warning added, something like...
(new nip implementation - images may not display on other clients)