requesting it, on the other hand, i think the out-bound should for "public messages" should be indiscriminate but - think about it, if the broadcast of public messages was already broadcast then you wouldn't need to look for them, either... your local relay would know how to find them, the one you pay
i've been working on a project that involves building a relay with a massive public "blockchain" based database, and now we are looking to actually do this with Arweave AO, which if you are not aware of it - someone started working on an arweave based relay about 6 months back, but abandoned it, i guess they got a grant, but arweave implements a content addressable, immutable append only storage system also
personally i'm much preferring the idea of Blossom, which simplifies and takes the "consensus" part out because why need consensus anyway, it's a broadcast, the data is public, nobody who published it cares, they want it to be public
this just isn't the case for DMs, and i've written extensively about the problem of privacy and metadata leaking, while we still can't have a monetised onion routing system where we can privately set up rendezvous points for our private messages without the problem of spam or traffic analysis, i'd rather trust a nostr relay operator who i constantly read and follow please