More or less, I'm still working out the details as I go along, and the model itself isn't very well defined. Below is a diagram by
npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk that tries to simplify, but I don't follow it to the letter.
Gossip relay model diagram by #[1]
#[0]
This is a leak! ;)
All credits for the idea/diagram to #[0]
Yes it is not the finished version, work in progress.
Let's call this model the NIP-65 read-write relay model. Because the term "gossip relay model" has been used to mean dynamically fetching stuff from where it is likely to be. This particular redefinition of the meanings/purposes of 'read' and 'write' relays arose during the drafting of NIP-65 and is a refinement to what gossip was doing previously.
Other than using kind-10002 to store the relays list, does Nostros implement the relay model defined in NIP-65??
#[2]
