Post

It wouldn't solve my use-case for it, as my src-dst on the laptop are impromptu directories. Most often, I aggressively¹ archive multi-file named collections out of forScore, creating and recv a folder each on the Linux side + sanity check for corrupted exports (forScore fault, about every 15-20).

¹ Due to arbitrary backup limits of iOS — I can't provide my own storage backend. It could, however, replace one of my uses for Nextcloud (bug king of any app I've used, for 10 years): 1) Accessing remote files. Certain directories read-only, others read-write (may overlap with bind mounts).

2) Uploading forScore backup archives of the current library (1.4G-2.1G). I've gotten used to distrust transfers via the Files app. WebDAV, Google Drive, and Nextcloud all (when handling multiple files (5+) of 5-10M or large (150M+)):

- Get stuck uploading the files; - Upload the files a few months later; - Remote contents are outdated, can't refresh; - Download failed, can't restart, force restart, resume, nothing; - Slow transfers; - No clear indication whether a file is completely uploaded or downloaded.