@tessus, I was just about to suggest removing this from iOS and giving the option to set cloud syncing app instead. Do you know if there are plans to set what cloud syncing app is used so that if one uses the filesystem sync on a desktop, they can still sync with an unsupported client on their mobile phone?
I don’t understand this question. Unless you mean that one can set e.g. Syncthing as a target. But in that case I don’t get it either, because you have to set a target dir, which you can’t on iOS. So I highly doubt that this will be implemented. Also, specifying external sync clients is too fragile. This is not maintainable.
I’m sorry for not asking an understandable question. I don’t know exactly how syncing works from a technical standpoint, so bear with me.
My question is: since the desktop version can use a directory for syncing to an unsupported target (tested with pCloud), how hard would it be to let the mobile phone user use their default syncing service that they have setup on their phone without having to set the directory on their device?
Thanks for getting back to me. I was looking at the sync code on my bus ride home from work and it looks fairly simple to add new services as long as they have an API that will work with its code. How are id’s determined for each of the sync services? Everything else looks pretty straight forward.
This is rather very specific and before a new sync target is added, it should be discussed with Laurent first. Let’s say someone adds a new sync target, Laurent will then have to maintain it from the point forward. So this is quite a change…
Yep, good plan. Fixing issues always helps. And it is a good way to learn the code, because during implementation you can try different things. Find the most elegant solution and create a PR... If it were that easy.