nostr:npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6 this should be of interest
Just deployed a massive change to Snort which i've been working on for about 5 weeks now.
It's called "gossip model", this makes Snort more resistant to censorship by connecting to the relays that your follows use.
This means that Snort will also distribute load across multiple relays instead of always querying your own relay list.
This is better for relays and better for nostr as a whole because it allows small communities to co-exist without the need for shared relay sets or without you needing to add those community specific relays to your relay list!
I also have created an NPM package which will allow anybody to build Nostr apps with Snort's internal nostr code, including the "gossip" model, check it out here https://www.npmjs.com/package/@snort/system
Please be aware that there are NO DOCS, keep an eye out and I should be able to create some example code in the coming weeks!
Discussion
If gossip is the way, clients are heading, we probably should also use that for our relay.
Mobile clients still have a hard time keeping dozens of websockets open all the time so I think there will be demand for relays that get the events you care about for you. But "follows of follows" is probably too simple an approach.