Nostr Web Client

Experimenting with NIP-17 clients more. I noticed in #Coop sending a picture uploads to nostrmedia.com NIP-96 server. The DM embeds a link to the media. However, if I copy this link & open in a browser, the media displays without issue. How should I understand the level of encryption on this media? Doesn't seem like E2EE unless the link itself contains the key, and it is decrypted on the fly in the browser session. Any thoughts nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpz3mhxue69uhhyetvv9ujuun909sjuum49ue5fn5u?

reya 4mo ago 💬 1

Hi nostr:npub17lmqmq680446scdgvv58snglr3h2phe00thqfe0twa3l8q5mzmusj6c60g,

Thank you for trying out Coop. In the current version, sending a picture works the same as putting a URL in a message and sending it. NIP-17 has instructions for sending encrypted file event messages (https://github.com/nostr-protocol/nips/blob/master/17.md#file-message-kind), but Coop doesn't support it yet. I already have it planned, but I want to wait until Coop is a bit more stable.

Reply to this note

Please Login to reply.

Discussion

Chris 4mo ago

Makes sense. In the interim, might be good to leave a little note in the UI so folks don't send media thinking encryption is on par with the likes of Signal.