Unfortunately for users, there are a lot of complex policies that different relays adopt which make them unsuitable for inbox/outbox usage.

If a relay requires payment to write, and you use it as your outbox without paying, then your messages will not be accepted by that relay.

If a relay requires payment to read, and you use it as your outbox (paying or not), then most users can't read your posts because they didn't sign up for that same relay.

If a relay requires AUTH to defeat spam, and you use it as your INBOX, then people who care about privacy will not reply to your messages.

I could go on, the list of gotchas is far longer than just this.

Gossip client, admittedly written for technical people not normies, has a "test relay" button to check if a relay is suitable as an outbox or inbox.

Reply to this note

Please Login to reply.

Discussion

I think it is complex even for devs. Like I don't know how to check if a relay is good or not for outbox, I had to look at the notices of each relay to figure out what they do :(

It's a Cambrian explosion of complexity. Very innovative space and cool ideas are being tested.

I don't know how to check fully either. I just react to what I do know and hope it is good enough for now.

We need some sort of better feature detection, or maybe we need to better utilize what we already have. NIP-11 has "payment_required" which is defined as payment for ANY action, so such relays are completely unsuitable for inbox/outbox/dm. "restricted_writes" means it won't be a good inbox. But then there are more. How can you deal with the posting policy? You have to just post and hope.

Your PR #1924 and nostr:npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2 PR #1969 should be combined. Neither of them help explain however if the relay would be a good inbox or outbox.

This is an age-old catch-22. Give users the power, or basically make primal.

Balance will be the solution, but I don't know what that is in this case.

I'm facing the same problem.