Yeah, I just scan for a predefined ports and pull in any that are in a kind 10432.
I had to build that because I test local relays and write installers, and I need lots of ports. Also wanted to solve for someone running GRW on a server, with different local relays for different customers. Might end up with 10 instances of the same local relay, after all.
Can use the 10432 to map a local relay to one or remote relays, and create a secure data tunnel.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7
I was thinking this for something like MedSchlr or our gitcitadel enterprise relay. Otherwise you might accidentally transfer stuff from a protected AUTH relay to other relays, over a local sync. Have to explicitly set them up as local/remote mirrors.
And that would help daily-driver clients to manage your connections to those relays, as the map is stored in an event that you can keep on something like wss://profiles.nostr1.com or wss://purplepag.es.
A community admin could provide a default 10432 template, that users integrate during the onboarding wizard.
