Thanks. Currently it's depending on the user publishing their relay list (kind 10002) on the bootstrapping relays (damus/primal/nos.lol), and then NDK should connect to the relays published there.
Any suggestion how this could be improved in order to find the correct relays?
DM inbox relays are listed in kind 10050, not 10002.
I know, but I assume you have your "full" list of relays (kind 10002) you want to connect include the DM inbox relays, and use the "shorter list" of DM inbox relays (kind 10050)to let people who want to send you a (NIP-17) DM know where to leave the gift-wrapped messages.
No. Kind 10002 is only public outbox/write relays and public inbox (that is for things like replies and reactions to public posts).
I would not want someone sending a DM to my wot.brightbolt.net, for instance, or relay.brightbolt.net/inbox. Rather, I only want DMs to be sent to inbox.nostr.wine and relay.brightbolt.net/chat, hence why they are a separate list.
10002, as far as I know, has no means of differentiating between which relays are public inboxes and which are a DM inboxes.
Yes, thats what I meant.
How I see it:
10002 is your generic "I want to connect to all these relays" list for the clients you use.
10050 is your "please deliver here and nowhere else" list for giftwrapped DMs.
But I do expect that you always want to connect to your Inbox relays, so they are in the kind 10002 list as well...
No. I don't always want to connect to my DM inbox relays. I ONLY want to connect to them for DMs. That is why they aren't in my 10002. I don't want people sending replies to my kind 1 notes to my DM inbox relays. That's not what they are for.
