If I ask for results from 2 pubkeys both nostr-rs-relay and strfry return 40 events from just one of the pubkeys.
Discussion
If both pubkeys were writing events interspersed in time than I'd consider that an implementation bug.
ah I see what you did there. thank you!!! that is one of the biggest unexpected behaviours!
they just return 40 events in total! not from each!
When making a query with no "limit" set, then this is somewhat fixed for nostr-rs-relay: 
But only because it apparently returns everything it has.
Nostream too.
I really don't know how you've been writing clients with these bugs in place. Aren't any of these clients using "limit" with more than one "author"? #[0] this might explain Coracle's problems with the feed showing just super old stuff + live posts that I've complained a lot a while ago.
I agree that would be a bug. The query should sort by time, and show the most recent 40 events taking into account both pubkeys and the age of their respective events. I will try and duplicate it myself.
I can't duplicate on nostr-rs-relay/sqlite. This query shows results for both pubkeys:
```
["REQ", "lim", {"authors": ["35d26e4690cbe1a898af61cc3515661eb5fa763b57bd0b42e45099c8b32fd50f", "887645fef0ce0c3c1218d2f5d8e6132a19304cdc57cd20281d082f38cfea0072"], "limit": 10}]
```
Sorry for wasting your time. My test was using spurious data so I got the wrong impression. Then I went to test strfry and got the same bug there, I went crazy.
No problem at all, you have made a good argument with all the confusion in this thread that we need a good relay conformance test suite!
I would expect most recent 40 results from both keys
Are you sure that one of those pubkeys doesn't have 40 events more recent than the other?
Sorry, this was fake news.