Automatic rate limiting

[ddevault]

mumble-voip/mumble#3510

This patch added rate limiting to mumble upstream, which simply drops messages if they're sent too quickly. I ran into this while working on a bot and it took me a bit to figure out that this was the reason my messages were being dropped. It would be nice if gumble had built-in throttling.

Do you have any thoughts on the implementation? None of gumble's the sending methods currently have a return value.

[ddevault]

Maybe you could just accumulate messages to be sent into a queue, then flush them with a rate limit in the main loop of gumbleutil?

I see the rate limiting is also configurable (see mumble-voip/mumble#3517), so I'm not sure how this could be done reliably on the client-side. I would like to see the server expose its rate limiting options to the client (similar to how the maximum audio bitrate is exposed), before a client-side rate limit is added inside of gumble.