Feature Requests

At the moment when user enables E2E encryption for S3 back-ends (or S3Drive storage) UI updates between devices are encrypted using the user's defined encryption key. Rclone crypt back-end on the other hand, doesn't expose the encrypted data to S3Drive (only decrypted data is shown) and as such S3Drive operates on decrypted data. This could be improved by extracting the encryption passphrase from the user's config, deriving the encryption key and encrypting/decrypting the UI updates on both ends.

Provide a sync option which would allow to achieve similar concept as Wasabi Cloud NAS: https://wasabi.com/cloud-nas/ Such sync option would keep track of "file accessed" metadata and based on settings (e.g. 90 days) would move file from local location to cloud/S3. Whenever file is accessed it would be stored in local FS cache. If file gets added it would end up in local FS cache and get synced automatically to remote. On top of that we would provide FUSE mount, which would use the existing selected local FS as a cache. User would have to use FUSE mount in order to gain access to all files / unlimited storage. They would have to be instructed to actually not use the local FS, as it would only aim as a local cache. It would be possible to run S3Drive on a server, create FUSE mount and then share it via SMB/Webdav in which case the end users would be able to share storage. Alternatively each user could work with their local FUSE mount, but any changes could be synced online via AMQ or other queue/notify mechanism). Some resources: https://forum.rclone.org/t/solved-is-it-possible-to-access-my-rclone-mount-as-a-samba-share/18335/27 https://www.reddit.com/r/linuxquestions/comments/rkmhv0/is_it_possible_to_share_fuse_mounts_over_samba/ https://learn.microsoft.com/en-us/windows-hardware/drivers/ifs/about-file-system-filter-drivers https://wasabi.com/cloud-nas/ Based on user's feedback: https://discord.com/channels/1069654792902815845/1069654792902815848/1148261916846850108

We should encourage users to enable encryption by default. We should detect if bucket which is being set up previously used encryption and prompt user to set it up.

Implement background support, Implement request retry in case of a network, back-end failure, Implement process resume (if it was interrupted, then start from the last point), Prevent app screen lock during rebuild, Use Versioning API to get the recent file changes and apply that as a diff on search/order index Related: https://discord.com/channels/1069654792902815845/1231647377212051486

We could allow user to send the e-mail out from the app.

Despite lots of improvements in the past couple releases, background uploads on iOS still doesn't work as expected. This is to resolve any remaining issues preventing from background backup to run. UPDATE: Since release 1.6.4 there is a further improvement. Background backup should happen once device is connected to the charger and usually overnight. This is a limitation of iOS background framework: https://developer.apple.com/documentation/backgroundtasks and there isn't much we can do about. We will be exploring next improvements and tricks that we can implement in order to improve this further.

Add support for additional app protection to protect user's data and credentials.