Oddbean

Somewhat disagree. Say someone chooses inboxes that require access control. This is on purpose, to fend off garbage and bots. The UI needs to notify the user attempting to send/connect to an access controlled inbox, that there are steps needed to send there.. visiting the relay landing page to see what the deal is, would be one option (the relay is paid, the relay only allows follows, the relay needs captcha, stuff like this)

Oh sure, that's fine. I thought you were talking about how people select which relay will be their inbox. Because relay rules can be complex, and this is a growing field, I think the most a nostr client should do is 1) Indicate that the post failed, 2) Give the user a link to the relay support page, including information about the post that failed. Then the user and the relay can "sort it out" using any complex method they want. And 3) Give the user a method to retry the post after they have sorted it out. My point being that gossip cannot keep up with and implement in-UI schemes for relay payment, captchas, and every other fresh new idea someone comes up with. NIP-11 doesn't have a general "support" URL, it only has a "payments_url". So maybe we should change that.

Yes, I think we are on the same page. Nip11 does have a link to policy.. perhaps this can be used. For all my relays I make sure the root domain landing page has all necessary info for users to figure it out. And I set all Nip11 fields that are available in the nip. I agree, for clients, there just needs to be ability to click a link for the handoff to 'more info'.