I already have 583,144 ids. So I'm not sure this is the right direction to go in.
Added support for "not" filter to Iris. It adds filter { not: { ids: alreadyHave }} to all queries in order to avoid downloading events that you already have locally. It's only sent to relays that support nip 113 (which I haven't written yet).
Also implemented it in nostr-rs-relay, although haven't tested with a real database yet: https://github.com/mmalmi/nostr-rs-relay/commit/55eb916123006f1ca9ca7b4bb107e69deac3579d
If you're connected to 10 relays and query them sequentially, adding alreadyHave to each request you might save up to 90% in bandwidth by not getting the same events 10 times.
However, I started thinking if it would make more sense to just implement negentropy in the browser and nostr-rs-relay. It's more efficient sync, but more difficult to implement.
I think { not: { ids: alreadyHave }} might be the main use case for the not filter. One consideration is that the "not" part might be so large that you need to discard it on the relay after eose.
Any other use cases for not filter? Maybe excluding muted authors from a global query, but not sure if worth it.
Discussion
No replies yet.