Closed taoeffect closed 4 months ago
Although their response might be taken as a bit abrasive, I ask that you please forgive them and look past it
It's really hard not to start a rant. This whole response has a bit of a "piss me in the face and tell me it's raining" feel to it. Guess where the user's media files are that he wants to synchronise? Exactly, they're outside our app's storage.
They could have synced the data to their app storage by default and provided a storage provider for browsing it in the file manager.
It's a valid approach for a limited use case. The problem is that most of the necessary changes would have to be made in the app itself, such as a UI that guides the user to select the correct location, and the implementation of the storage provider.
I'm also worried about the restrictions if the app is being uninstalled. Are the files simply gone?
Just for the record, you can already sync into the Syncthing app's own storage if you input the path manually using the Web GUI, however the first problem is that the path is inaccessible to other apps (hence the talk about providing a dedicated file browser), and the second problem is that when it comes to Android specifically, most users simply want to sync their photos and videos, and those are located on the shared storage, which makes the suggested approach not very feasible anyway.
(Note: I realize that this project is in maintenance mode. As this is not a feature request, I've decided to post this issue here, as well as in SyncThing-Fork, in case someone is able to take this on for Android/GrapheneOS users.)
Description of the issue
Hi, SyncThing is perfect for syncing large amounts of small files that don't change, e.g. photo albums and music libraries.
However, on Android, it's a well known issue that the performance is almost prohibitively bad for this use-case.
Example threads:
I reached out to the GrapheneOS developers to see if they knew why this might be happening.
Here is what they had to say (reposted with their permission), I hope it is helpful to addressing this issue. Although their response might be taken as a bit abrasive, I ask that you please forgive them and look past it, in case what they have to say is useful for addressing this problem that users (like me and others) are facing:
Version Information
SyncThing-Fork 1.27.2.1 on GrapheneOS (I'm guessing the same issue exists for this repo as well though.)