Why Nostr? What is Njump?
2024-06-09 05:31:37

tf on Nostr: hodlbod is there a way to configure relays in Coracle to work with both NIP-65 ...

is there a way to configure relays in Coracle to work with both NIP-65 inbox/outbox *and* paid relays?

So for nostr.wine which is free-to-read & pay-to-write I have



*But* I also want to read from nostr.wine

If I enable read others will try to write to it as my inbox (I think)

Similarly for filter.nostr.wine which is pay-to-read and pay-to-write, I don't want others to treat it as my inbox/outbox

Nostrudel & Amethyst work around this with app-specific relay settings

Tbf because NIP-65 ventures into this territory...

"When broadcasting an event, Clients SHOULD:

Broadcast the event to the WRITE relays of the author"

I think perhaps it needs more flexibility to cover client configuration with paid relays

So relays defined in kind 10002 could have separate read and write values for the author vs all others
Author Public Key
npub1dq0vnsph9wpmp9pcsc6qj2l5h7xsjyxyxt5tsl986u3v4lncknnsf8yffq