Nostr Web Client

I actually don’t know what kind 4 is?

direct messages... chat...

the "deprecated" kind that has both sender and receiver pubkeys in it, as opposed to the receiver only 1059/1060 "giftwrap"

that pesky thing that can only be moderately protecting of user privacy IF CLIENTS IMPLEMENT NIP-42 authentication!!!!!

which nobody seems to want to do, and i've got a colleague from the company i work for adding this feature to #nostrudel if nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr won't do it (if you don't get it added it will be offered as a PR on a fork in a couple weeks time)

Reply to this note

Please Login to reply.

Discussion

rustyspark 1y ago

I’ve got like 6 clients I am trying out. I wonder which one used the deprecated protocol?

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

as far as i know they all still support it and the reason is that you can't decode your own outbound messages if they are the "new" 1059/1060 kind unless the client stores that key

there was a lot of talk about it but very little that used normal language so anyone, even technical, could understand what they were talking about

and none of it fixed anything and most of them ran off and did other things instead

it's a blind spot that has really serious privacy issues because they aren't dealing with the problem of authentication, it is not nearly as problematic with NIP-42 auth and NIP-65 in/outbox - because those two protocols enable containing the privacy issue between the users and the relays instead of it leaking out over everyone