Coracle will write replies to the inbox relays of those you have tagged in the reply. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is using relay.damus.io, nos.lol, and hbr.coracle.social as inbox relays. nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz is using creatr.nostr.wine, among others.

Reply to this note

Please Login to reply.

Discussion

Yes, this is what is redundant with filter.nostr.wine, as it also does that. It is its own mailbox implementation.

Interesting. I knew about its blastr relays, but did not know it also uses NIP-65 for replies to post to the inbox relays of those mentioned.

Is this something we should be expecting relays to handle for us, rather than clients?

I think our collective paranoia is negatively affecting UX.

As long as these all-in-one relays do not censor it's a superior solution with less waste.

Censorship incentives are low, they can be swapped immediately for a different provider and affect their brand reputation.

Yeah, we have a set of powerful community relays, and clients mostly just mess them up.

And every client is different...

Our collective paranoia is all we really have

who sent you?

Some paranoia is helpful, it is also possible to go too far!