Here’s how our new NIP-65 broadcast service for 🍷 filter.nostr.wine works: 1. A background service constantly monitors kind 10002 events across (most) known relays and updates the results in redis. 2. When one of our paid users sends an event to filter, their first 4 “write” relays are pulled from redis and sent to our broadcaster. 3. If users are tagged in the event, the first 4 “read” relays from the first 5 tagged pubkeys are pulled from redis and sent to our broadcaster. 4. The broadcaster service batches requests and then connects to the necessary relays and sends the events. 5. In addition, events are also broadcasted to our list of public relays visible on

Replies (1)

No - should have been more clear! This only applies to broadcast=true. One note that’s a bit confusing: if you connect with /npub path you need to include ?broadcast=true whereas if you are connected at root, true is the default. Either way, you can always specify broadcast=false to opt out.