Why is this important? An example:

Npubs you somehow interact with *might* use your inbox relays to reply to you, to make sure you get the message on a relay you can read from and not posting replies in the void.

NostrDVM framework for example now integrates the outbox model. Clients like Amethyst check for a DVMs inbox relays and sends a NIP90 request, e.g. to generate a feed, directly to these relays.

The DVM receives the request, does some magic and checks for the user's inbox relays to deliver the reply to relays the user then again can read from and the client shows the result.

If your inbox relays use paid services for which the DVM is not registered for, the relay will reject the response event and you won't get a reply.

You want others to be able to write to your inbox relays, and you can't assume others have a subscription on any relay you might pay for.

Same goes for private inbox relays with DMs.

I hope this helps understanding what kind of relays you should put in inbox relays.

nostr:nevent1qqs2vq42xfkxlk23xkle6hvptu3wv3ker42as2eav3f746wtgjgd3hcppamhxue69uhkummnw3ezumt0d5pzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqvzqqqqqqy42cpej

Reply to this note

Please Login to reply.

Discussion

I simply whitelisted the npubs (like your DVM) that I want to communicate with on my private relay.

Projects should simply make sure to publish their npubs and include them prominently in any documentation.

I just added the DVM to my whitelist.

I just whitelisted your DVM. 🤷‍♀️ Give the particular npubs you want to communicate with write access.

That's fine for your own relay. I mean mostly people who enter paid ones they don't have control over.

Ah, you mean they're doing it by accident?

Yes. I think people don't know yet what inbox relays are about. So they pay for premium relays, enter them in their inbox relays field and if a service wants to send to their inbox it can't, except it's paying for all possible premium relays out there 😀

😂