I'd like a server authoritative way to make sure my reducers aren't called a bazillion times. So this could mean a rate limiter or debounce, but either was as a macro would be nice.

• A rate limiter that does some nice things like burst management or X requests per second X per minute
• A debounce behavior like how web apps handle stuff, just accept the last request if they all burst in 10 within 100ms accept the last one. So at most X requests per Nms, without dropping requests. Slightly different than rate limit which complete blocks when reaching the limit.
• Some combination of both?
• Some other thing i'm unaware of?

ATM the only solution I can think of that we can do now is to implement a table to track last request and who made it, then comparing and returning error. Or we just simply rely on the client to be a good citizen and not hack to kill the server with requests.

Requested by @onx2 via the SpacetimeDB site.