Which nostr clients follow the gossip model of looking at a profile event to see what relays an npub uses, and then pulls from that instead of pulling from a random / user set group of relays?
Discussion
https://github.com/unclebob/more-speech from nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft.
more-speech pulls from an editable set of relays at the moment. It gives you a lot of filtering power over those relays. For example, you can read just your trusted npubs from the relay, or the npubs trusted by your trusted npubs, or even all npubs.
more-speech also adds relays found in events to the list of possible relays, but does not activate them.
At some point I will be adding more dynamic relay processing to more-speech; but that's for the future.
From: mutatrum<-DerekRoss at 08/14 15:27
> https://github.com/unclebob/more-speech from nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft.
CC: #[4]
CC: #[5]
Coracle does, still refining it of course
This one use gossip: https://camelus.app/
Is Nos going to do that at some point?
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 how does Snort implement it?
Any time you query by author it uses the authors write relays to query thr data for that pubkey, currently picking 2 relays per pubkey to query data. No cap on number of relay connections
AFAIK gossip, coracle, nozzle, camelus.app, snort. Vitor says he intends to do it in Amethyst.
Android: Nozzle
Desktop: Gossip
Web: Coracle
Highlighter, Agora