Nostr Web Client

Clients and relays do not use any form of data encryption (defined in the nips) to speak with each-other, only TLS, TOR, and so on. This encryption is strictly for client data.

Are you suggesting storing plaintext client data, in a private relay, so that it could avoid that UX hassle?

I would love for clients to have that fine grained control over relays. Personally I'm mad and I'd like for every note signed, the option to select which relay it gets sent too.

Niel Liesmons 1y ago

> the option to select which relay it gets sent too

Yup, I've been breaking my non-dev mind over where to propose this crucial feature in the NIPs.

Needs:

1️⃣ Npub can specify what relays an event is targeted at

2️⃣ Npub can edit this relay-set later on

Reply to this note

Please Login to reply.

Discussion

Niel Liesmons 1y ago

An h-tag with the target relay, such as Chachi and the NIP-29 complexity lovers use, can only do the trick if the tags are editable after the fact.

fiatjaf 1y ago

NIP-70 does this in the best possible way.

Niel Liesmons 1y ago

With this, how does the author say "this event is targeted at these relays"?

This NIP asks relays to reject events with a ["-"]. It doesn't help in specifying the target audience for the event. That's what I need. In a way that's editable. For any event type.