we currently set an upload rate limit of 32 crashes over a 24 hour window.  this is both to help not overload the crash server and to not overload the client's bandwidth (which might not be that great).

but not all crash reports are equal.  chrome and such can be on the larger side (many KB), while others can be quite small (less than 1 KB).  we should improve the upload rate limit check to factor in sizes too.

if we consider Chrome as the highest consumer, we could use that as an upper limit.  e.g. if each report is 100KiB, then we set the ceiling to 3.2MiB, so we could upload a lot more smaller reports when they're <1KiB each.

our uploader also adds a random delay between 30sec and 10min between each upload.  we wouldn't want to be uploading small reports every 30sec even if they were only 1KiB.  so we prob should adjust the upload delay once we hit the 32/24hr limit to be always be like 10min.  that would help spread things out w/out overloading the server.