Is there a relay query that echos its configs so you can choose relays based on settings?
Discussion
We’re moving to a more decentralized model where users don’t choose relays since that doesn’t scale
How does the outbox model even choose the relays then?
Is there redundancy in case a relay goes down?
Will clients even be in sync? I imagine global is worse off not showing everything
the way i would prefer it is use nip05 relays to get their relays, if they have no nip05 try your best based on popular bootstrap relays. Once you have their relays you know where a particular user reads from and writes to. So when sending them a note or replying to them you select their read relays. When reading their notes you pull from the relays they are writing too. Pretty straightforward.
Gotcha. I bounce around and use all sorts of clients right now to feel out how various features are being implemented. I’m not client committed.
What if I just want to push to my own relay but want to use a good client I found?
Would client selected relays start segmenting the landscape of users?
Client influenced segmentations of communities isn’t ideal if I want unlimited reach and exposure to varied content. Is that the eventual result if my client chooses relays for me without my input?
Or any I missing something?
The point is that you should be able to set any relay you want and clients should be smart enough to pull from the right relays. Outbox reduces segmentation. It would be transparent.
Users are segmented on clients that strictly follow a users relay list (like damus ios atm)
Thanks for the clarification. 🤙
When I first showed up I thought I’d be able to run my own relay and broadcast to that for my content to be found there, archived there, and just self hosted. But most clients won’t even respect my ws://[address].onion relay address.