m^2, but yes
the first part prevents exponentially scaling broadcast storm-like behavior, while the 2nd part means you do not have a persistent trackable identifier being broadcast to the networks you use
Discussion
this protocol was made originally for IRC-based /dev/random cross-seeding, while also allowing on demand requests if required
it still works to this day
yeah was thinking about how to deal with that without over complicating it. Not a big deal for small networks but would be important for conferences.
I think in those situations you would want the client to discover a relay and use that.
I wouldn’t want my phone to announce to be a master node if theres like 1000 nostr nodes on the network
the master here would only coordinate the schedule of discovery messages, which does not change if you have 1 or 1000 clients