I don't think I talked about private events. I was just talking about following someone's public twitter-like posts.
Finding posts by ID wasn't the case I was thinking of, but in that case if you don't have a relay hint, I go to the seen-on relay of the event referencing the ID, and then I look at the p-tagged people and search their write relays in case one of them wrote it.
ok, so if i give it my relay set but only set writing to the ones i want to publish to it will search elsewhere for events if they don't appear on my relay set
i still would like to be able to disable this behaviour for testing my relays because getting nothing is confirmation of the relay failing to return something or failing to have stored it in the first place which is an important thing to be able to test, when the relay has ACLs and other kinds of filters running, sometimes you WANT it to not find it to confirm that it didn't store it or is not allowing the authed client to access it
Great. Then use a client like damus that only reads things from your relay set. It would be a huge rearchicture for gossip to do that, it's not just "disabling" a feature, it's rewriting huge amounts of code, because it never before sought events from your specified relays.
