That's great to hear! Gonna test it as soon as you release version 2.1;)
In another discussion, which I can no longer find, I reported an issue with how a provider handles multiple requesters. When a provider doesn't have enough capacity to fully satisfy all the requests, it should serve the requesters in rotation: send everything it currently has to one requester, then, when the next batch arrives, send it to another requester, and so on.
At the moment, it seems to always prioritize the closest requester and keep trying to fulfill that request before serving the others.
Are you planning to fix this one as well?