Subtly Modulate Uploads

Resource Abuse that relies on storage (like Chia Mining, or Obfuscated Encrypted Storage (OES)) often relies on precise retrieval (i.e. the user expects to get the bytes they put in exactly when they download the file). If a platform is able to break that assumption, they're able to guard against these types of abuses by modulating the inputs slightly, so that legitimate users do not notice, but users just using the storage for its byte value will be stymied.

This is categorized as "Omission" because the platform is omitting the feature of 1:1, byte-for-byte upload:download.

Examples:

1. When storing images, rather than storing the bytes as handed to you by the user, copy and paste the pixel values into a new image. This will strip out any unwanted metadata in a way that is non-opinionated.
2. When serving documents, add and remove some invisible unicode characters to prevent their use for Chia or OES.
3. When accepting media,  do a light compression on the data before persistence (which both saves you storage costs, and prevents replays).