Correction - “The limit property of a filter is only valid for the initial query and can be ignored afterward. When limit: n is present it is assumed that the events returned in the initial query will be the latest n events. It is safe to return less events than limit specifies, but it is expected that relays do not return (much) more events than requested so clients don't get unnecessarily overwhelmed by data.”

I’ve passed this on to Doug @ Strfry.

Fow now filter.nostr.wine is solving this by chunking these requests for our users.

#[0]