The call to revisions?include=changes (to show the history window) can get ridiculously large when there are a large number of files in the changes retrieved. For example, when retrieving the most recent changes for a project where I published 20,000 unique randomly-generated text files, the call resulted in a response body >4 megabytes.

REPRO STEPS:
1. Start Fiddler / Charles Proxy
2. Create a project and enable collab
3. Publish 20,000 files
4. Using Fiddler / Charles, look at the size of the response for revisions?include=changes when refreshing the Collab History window

RESULTS:
revisions?include=changes call is >4MB and uncompressed

EXPECTED:
Large calls that are mostly text are GZIPped

IMPACT:
Major slow-down for users retrieving collab history at average connection speeds