This is the sort of relay centrifuge that makes client development a heck of a lot easier, as you can just hook relays up and get the service from there.
Login to reply
Replies (1)
i just got done adding that feature to #orly today. in fact all i did was change it from only fetching a few event types to just grabbing all events every time the spider runs, of all the whitelisted users on the relay.
the spider triggers hourly or any time anyone on the list publishes a new follow list, as it needs to recompute the whitelist from it.
my current task is making a push sync between relays, so you can have two or more relays that instantly receive any new events on other relays in the group.
it could be done by a pull but since implementing it on orly means just doing a nip-98 auth and a HTTP request i am just doing it by push. the other benefit is that events received by this route (or EVENT envelopes) also broadcast to subscribers with matching filters.
the reason i'm making the push sync is because i mean to set up a wireguard mesh (already done) with a round-robin DNS and this way i will have 3 relays that are all replicas and any events going to one will go to all, and if one goes down, the other two will stay up. although this does mean the one that is out of sync will not have events during that period, gotta think about that one as well. simple enough to just add the relays to each other's spider relay list, then it's done automatically.