there is an inherent conflict between outbox ("gossip") model and broadcast (blastr)

outbox is for private communication - ie DMs, application specific data, and closed groups

everything that is intended to be public should be broadcast so we don't get this problem of being unable to find notes

thus, if your client or middleware is looking for kind 0, 1, and other intentionally public things, there should be no limit to where you search for them 

- except for the case of intending to use a specific set of relays due to privacy, nor should there really be any limit to where you broadcast them

at minimum, clients should consider this in their configuration system, there is good reasons to limit this for such as metered connections and sticking to paid relays, who also should be seeking to pull in all available public events

paid relays should also broadcast any public type of messages on behalf of their users so that those that are not paying customers still see the public messages 

 https://github.com/nostr-protocol/nips/issues/1162

i've made an issue about this... i think if these distinctions were added to wherever they are relevant in the specification it would make it a lot easier for everyone to know how to design both clients and relays in order to maximize decentralization as well as defending privacy and bandwidth/battery use for mobile devices