Element should never try to rageshake more than 200MB of logs.

[ara4n]

Steps to reproduce

1. have a nasty problem
2. try to rageshake
3. discover you get a 413 Request Entity Too Large error if you try to upload more than 200MB of logs.

Element should discard/truncate older logs so it never tries to upload more than ~180MB or so, given cloudflare limits uploads to 200MB on the business plan, which rageshakes.element.io is on.

The workaround is to temporarily disable CDN for rageshakes.element.io, but this exposes the internal IP of the service, opening it up to potential abuse.

Outcome

What did you expect?

Rageshake should work.

Your phone model

No response

Operating system version

No response

Application version

No response

Homeserver

No response

Will you send logs?

Yes

[ara4n]

...except in the problem rageshake in question (linked), once it correctly uploaded logs, there's only 10MB of logs (76MB unzipped). However, the request took minutes to upload, implying it was at least 200MB large.

So there's a separate bug where we're trying to send loads of data, but only 10MB of it gets stored by rageshake.

Split out into https://github.com/vector-im/element-ios/issues/6596 and https://github.com/vector-im/element-ios/issues/6595