Feature Requests

This isn't possible with pure S3, but for our managed storage we could theoretically allow "block level" updates using different protocol. Challenges: regenerate whole file MD5 after every block change? if content is encrypted using V2 cipher, shall we also regenerate the unencrypted hash? can we skip MD5 altogether? What ETag we would then return from S3 endpoint? What if e.g. 200GB image gets updated frequently? Hash regeneration would kill performance dramatically. Interesting projects: https://github.com/archiecobbs/s3backer

In a similar way to current Media Backup, allow background execution of jobs configured in the Sync tab.

Once user creates a share and then modifies the file contents, it makes the new file version not downloadable/previewable. Issue applies to externally used S3 and isn't present in storage plans that S3Drive provides. Why? Every file version has its unique encryption key. Once user uploads new version (e.g. modification to existing file), new encryption key is used. This doesn't match the encryption key that was "extracted" for the share itself, hence data can't be decrypted until share is created again. Solution? There are some workarounds that we plan to implement. E.g. we could track "shared" resources from the S3Drive and regenerate the share data to include JSON keys. Related: https://discord.com/channels/1069654792902815845/1348564160480280586