If there is no field, it means the relay is used for both purposes. Was that how you configured gossip? I just pulled your relay list and you are right, none of them are single-purpose.
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr is so distracting lol, this morning I'm distracted by my nip65 relay list.. I just re-configured gossip to diagnose this, it appears my relay list as published from gossip does not have the extra field in the array for "read/write" .. I was wondering, do you plan on expanding nip65 to include other types and also, why didn't gossip add any fields there?
Discussion
ohh, gotcha. Yeah I need to think some more on this.. the rabbit hole always runs so deep with relay settings. I think what has to happen, is in the future, if you want to DM someone, you're gonna need to pay a small amount to their inbox relay. And then I can specify one (or two) inboxes. If you specify this, I'm wondering if it will say "inbox" in that field? Or because you also read from it, if it'll just be blank? 🤔
Inside the relay list event, it will be blank. Clients should not show blank to end users. Blank doesn't mean anything to an end user.
It is very hard for end users right now to pick inboxes. I don't pay relays in order to tag one of their users, so they simply don't get the note (well they do because of blastr). We need to push on technology that makes it easier for end users to pick appropriate relays, without picking them for them.