How about a working, documented plugin API? Or sync clients that work? Instead of taping more random crap onto a base product that only barely works?
Perhaps the grandparent commentor is using an older version of the android client or server?
In my case, I managed to track it down and, by knowing what causes the sync issue, I can avoid it, or ignore it. Could be that grandparent has this issue too bu her/his server is set to much lower limits even?
Just keep in mind it uploads the original files, not, like eg whatsapp, downsized, compressed one that is 1/10th the size...
I’m on a local network over WiFi. The “server” is a RPi3+ with an extrernal USB 3 drive. Granted, I don’t expect it to be blazing-fast, but not 3-5 pictures-per-hour slow either.
Something is fundamentally broken on the iOS app especially since both the Windows and OSX clients are much faster (same network).
We do very frequent releases so perhaps it'll just be fixed at some point ;-)
Good luck and sorry for the problem!
I often find myself in your shoes in my daily work - answering frustrated users’ emails - but it’s funny how when the tables are turned, I am reminded how something as simple as “we fix stuff frequently, and sorry for the problem” makes a huge difference in product perception.
Also, it’s a free product, you don’t owe me an apology at all, but thanks!
Maybe Seafile somehow found a good solution that doesn't cause breakage in other places. Any specific reason you want to switch to them?
OP just told you the problem
From a server admin perspective, they support docker natively and there support of WebDAV and FUSE give you a lot of flexibility in how you can leverage the software.
edit > Typos
Can not fail and resume, basically there can be months of pictures lost since it resumes, crashes dies, does not resume next time. The android app that is.
Disclaimer: I fixed some of these bugs, so seeing the source-code was repulsive enough, but there just isnt anything else better as far as I know.
It is more of a toolbox for building NextCloud or anything else. But all the components have been tested on all platforms and work (and are secure). It has a working, fully documented plugin API.
I wholeheartedly agree that they should focus on more important features.
I use nextcloud in my home with a mix of clients, all working on the same files. Changes propagate up and down to/from all clients. Maybe you mean something different?
-
I am of two minds here:
1. Minimal specification worked for HTTP.
2. Most problems with HTTP come from it being minimally specified.
ActivityPub is exploding the way HTTP did. At worst, it's as imperfect as HTTP. At best, it's a way to get people used to federation for whatever comes next and improves on it.
My experience has not been that it "barely works", it works quite well for me.
I agree with him, they put a lot of energy on non crucial features when a lot of their core features could be improved.