Wait. Is it not common knowledge that Android and iOS log every application you open down to the exact millisecond you open and close them?
Is it not common knowledge how telemetry works for the operating systems? They generally batch up a bunch of logs like this, encrypt them, compress them, and then send them to the mothership (hopefully when you're on WiFi).
Logging and telemetry are completely separate use cases. For example to do some kind of battery use accounting you need some record of when exactly which app was active.
And no, it's not widely known or documented - there is no good description of what telemetry exists or contains on iOS that I know of.
Yeah, because encrypted data should be incompressible, as it should be indistinguishable from random data, which is also incompressible.
Reality is a little different of course, and compression can cause problems for encryption because compressed data tends to be highly predictable (especially things like compression headers and compression dictionaries). This allows for potential “known/chosen plaintext” attacks on the encryption.
Some classic examples of this type of attack are breaking Enigma (known plaintext, no compression) by assuming the content of some messages[0] and the more recent CRIME[1] attacks against TLS using compression to help produce a chosen plaintext.
The simple solution in these scenarios is to avoid using compression completely.
Is it not common knowledge how telemetry works for the operating systems? They generally batch up a bunch of logs like this, encrypt them, compress them, and then send them to the mothership (hopefully when you're on WiFi).