Has anyone figured out a UX for relay management that includes this sort of stuff. Like “who hangs out here” info for relay management

nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240

nostr:note14y8sjaerlqxqu9yhyxq2r8x3pnukuwdncszaa6cly947d6yza4yq2xh0pd

Reply to this note

Please Login to reply.

Discussion

If your client is doing outbox properly, you shouldn't lose contact with anyone (as long as they relays they choose are functioning properly as outboxes/inboxes). I started building a relay management client for things like this a while ago though, but I just don't have time to finish it.

Managing relays is like configuring SMTP servers, I want to hide or automate it as much as possible, eventually. In Nostur you could use Relay Connection stats to kind of find out who is using which relays, I wrote how I use that here: nostr:nevent1qqspmnx62g439w7mnr7aqr6s56y6e9l08th0u60e2elglx2h49sn0rgzyzd7p0swvnfc52dfemy6tj80tkrnc2l62d32fd2cmf0ldx7rewupuqcyqqqqqqgpzamhxue69uhkvctzd9skutnwdaehgu339e3k7mgpp4mhxue69uhkummn9ekx7mqtj3lw2

additionally when you use Relay Autopilot you shouldn't have to worry about any of this but it won't really work unless most other clients also use it (outbox) properly.

in the outbox model, every user still configures which relays they personally want to post to right? How do they choose exactly? Are they choosing their “home base” relay?

I keep wondering if it may make more sense to intentionally choose relays on a post by post basis. Different logic behind that UX, but it’s definitely easier to conceptualize. Less of a black box

It’s nip-29 group focused but we’ve been working a lot on relay management https://github.com/verse-pbc/groups_relay

Should I be on the TestFlight or main App Store version?