Should profile pictures be NIP 95?
In NIP95, images come from relays and can be verified to not have changed since the author posted.
Discussion
Most relays are banning N95, so not sure if that would be a useful user experience.
We just need one relay that supports nip95.
Anyone connected to the relay could get the photo, indipendent of NIP95 support from the client side?
No, clients must support as well... Same case with gifs, SVGs and video links. Many clients don't show anything if you add such urls.
Cryptographically verify ALL THE THINGS!
How about both options and each one chooses the one they prefer?
Remember to only send the NIP-95 to those who support it.
Nice. We can easily add an extra field in the user metadata and include the nostr:event with the nip95 content. Clients that support it wouldn't need to load the http content..
It could be confusing though to change your profile in a client that doesn't support nip95 and have the url link point to a different image than the nostr:event field.
NIP-95 will not be supported much. for profile picture may not be a good option. Because there will be customers who will not identify the photo.
Needs more explanation for non-developers community
What about using NIP-94 to check that the profile picture is not changing while still using a HTTP URL to get the file?
Kind-0 attribute could be added to publish the profile picture this way, innit?
There are two ways: you can do another field in the User Metadata for NIP-94 that will store the nostr:nevent OR add a URL suffix like "#nip94=nevent"
Either way, you need client support to change your image correctly, and client support to display the nevent field and the verify the image.
Pixel and HTTP ping tracking would still happen, though.
Yes, tracking will still happen if no proxy is used, but the picture will be change-protected in nostr clients supporting NIP-94.
I think it's a step in the right direction.
And less controversial that NIP-95 right now.
I'm not sure I see the point. PFPs can be changed on a whim already just by changing the link in your profile.
Has the sentiment towards nip-95 among relay operators changed? I thought the majority of them was against hosting images...
NIP 95 will make the json msg become large.
All json will be decode and encode in transfer. The msg more large the speed more slow.
But if the image transfer throw like file, it doesn't need to decode and encode, and it has cdn support, compress support, maybe it will be offer thumnbal function.
These make me believe that #NIP-95 isn't a good idea.🐼
You can move images around to different relays to avoid censorship of image servers as well as have a backup when image servers go bankrupt.