nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Talking about nostr user relays management: is there a best practice in choosing/using inbox/outbox relays and app relays (the ones only used on the specific client)? Are there some articles or documentation about it?
I get one should use few inbox/outbox relays (normal and/or WoT ones), but what about all the other relay types? Search, app specific ones, etc...?
I see most of the clients have this "app relays" that are used "for everything in the app", but why would I use them if we have decided the outbox model is pretty much the one to follow? Aren't they "useless"? I mean I get the need for general search/read relays to search for content (for example global feed and to bootstrap the client after a fresh login), but why the write ones?
Please help a fellow nostrich.
Just think about what has to happen and make sure that it can happen:
Outbox -- Make sure you can write to it (subscriptions/AUTH are ok). Make sure everybody can read from it (without needing a subscription or AUTH).
Inbox -- Make sure everybody can write to it without a subscription or AUTH, at least in so much as when they tag you. And make sure you can read from it (subscriptiuon/AUTH are ok).
No replies yet.
