Nvm, makes sense. And I know Vitor was trying to get it working together with Nostr.Build, they will 🚀
Discussion
#[2]​ I think you should update the copy regarding nostrimg, it’s misleading at best.
nostr:note12avuy724ajyx3jn8ayz29gecxc7qagcd2tchdjj00ms69c5cgy7ql4palt
indeed it is
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)
Thanks 🤙🏻💜
we'll see. he's an amazing dev, but he dropped the ball on user experience comes before innovation with this one...and just left users to their devices. like, any option but the first still bricks images on anything but amethyst (apk) and snort.
and according to his recent statements, we have to chase around the other clients and ask when they will implement it.
I believe this fractures our community. and i hate it because i love amethyst (still thing it's the most mature and secure client for android) and i happen to be quite fond of nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.
again, i feel he's a brilliant dev and i agree with his security forward approach. imo we just need a little notice and user experience first mentality before releasing the kracken.
i feel his cooperation in making a distinction between the beta and full apk releases was a huge win from our last convo đź’ś
Asking around when clients will implement it doesn't fraction the community. It a very common question we get all the time for every NIP.
I believe labeling beta releases will help. Those of us who use github scanning apps like #obtainium filer out beta releases. When open source first people install the apk and it's not labeled beta, it should work as expected.
After re-reading everything...I honestly feel this was the breaking point when so many kept posting, not knowing they were using a beta release and pics got bricked with no warning.
As far as the wording update, I feel just a disclaimer like (new feature -vmay cause images to not be displayed on other clients)
i still love your work
make sense nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z?
Its a tiny blip in the nostr timeline. There is so much ahead.