Feature Requests

Ciphers are similar, but not the same. We/Rclone uses: XSalsa20-Poly1305, Kopia uses: CHACHA20-POLY1305-HMAC-SHA256. It also uses different storage layout. https://kopia.io/docs/advanced/architecture/#content-addressable-block-storage-cabs and https://kopia.io/docs/advanced/architecture/#content-addressable-object-storage-caos that we would have to parse/decrypt and understand in order to produce file list viewable to the user.

Files > 100M are uploaded using multipart upload using 5MB chunks. If upload gets interrupted, next time when file gets uploaded we verify MD5 (only if E2E encryption is disabled) of each chunk so it doesn't gets reuploaded. The issues is that MD5 verification is relatively slow. If 10GB file was interrupted at 50%, then it means we need to verify 5GB of data which isn't instant. The idea is to store the file local modification date and trust that file contents hasn't changed if modification date hasn't changed. Using this pattern we could resume upload immediately. We could also resume upload of encrypted files given that we continue uploading chunks using the same nonce prefix (this is safe, because we're not reusing nonce. Yet to be uploaded chunks receive their own nonce counter). Finally implement exponential back-off retry for failed transfers (e.g. 400 bad request, 5xx errors and timeouts).

Originally from @Ludwig https://discord.com/channels/1069654792902815845/1268292873367851049/1268552678049452114 "When I tried to upload a folder around 5 GB (some 80 files in it) usage of Ram goes extrem at one point. When upload was around 1.5 GB, the usage of Ram was about 8 GB. Around 4 GB upload the usage of Ram hit 16 GB and the web page is crashed. It happened in both browser."

At the moment S3Drive will upload media to <SuffixDirectoryPath>/<AlbumName> path, where SuffixDirectoryPath is configurable and by default set to Automatic Uploads/<PhoneBrandName> . Some users don't have need for multiple album upload and would like to keep the simplicity of folder structure. We probably shouldn't allow disabling the structure that was implemented: https://s3drive.canny.io/feature-requests/p/preserve-folder-structure-for-a-different-albums-media-backup as we would risk file collisions, if multiple files are uploaded to a single folder. What we could do is to confirm the upload path with the user the very first moment when album gets selected. At this stage user could configure upload path for their preferred album to custom location.

Ur rclone type for connection of Google/ OneDriVery troublesome, I configured on the phone all day and still encountered all kinds of incomprehensible problems and finally failed, There may be no problem on the computer but you need to keep the Internet connected to start the service, which is extremely difficult, I hope you can apply for the relevant Drive api permission with Google and Microsoft, directly log into the authentication of my Google / Microsoft account can be directly synchronized to use sync management. I really hate Rclone right now. It's a lot of trouble and it's always having problems and failure. I find it hard to accept. 😟 , really really please!