"In an annoying coincidence, Joplin released its new Joplin Cloud-storage subscription service a couple of months before the native file system syncing broke."
Coincidences, coincidences... I wonder what those who got stuck on the word "manipulation" I used when opening the topic would say about this coincidence...
Like other users on Android, I wish the initial sync would be faster than it does currently, but nobody does not demand the author to fix the issue by implying that he may well fix it, even using a word which can have both positive and negative connotations simultaneously (what is the point of taking such a risk in the first place?).
If you think there is indeed manipulation to nudge users to use Joplin Cloud so that the author can make money easily, why not stop speculation and point out the issue so that we, including you who can become a developer like anyone else, can fix the issue together? Please stop assuming that someone out there may well fix an issue for you, because as you have correctly said:
After all, Joplin Cloud is also an open-source project.
If you cannot point out an exact issue or propose a fix for it, your opinion is both unproductive and nothing but based on hearsay, and you should stop already for the sake of everyone's sanity because your questions have been apparently answered.
If our options as users are limited, then we should see developers taking a more active approach to addressing this issue right?
No, this is not right, because you can both be user and developer when it comes to free and open source software. You are expected to be active here. Grow up.
When a clear problem is being pointed out, ignoring it and focusing on the one pointing out the problem is an ad hominem and a fallacy of logic. No one is forcing you to go to this thread and read what is written. Therefore, isn't it quite meaningful that you are both uncomfortable with the subject and at the same time you are posting on this subject for the first time in the forum?
Then read the responses to the responses given. No one can offer a clear solution to the problem and no one can develop a clear approach. If you pay attention to which messages I quoted, you can see this very clearly. So it would be a good start for your message diversity (!) to stop defending someone and develop your own approach!
Also - Android's file system access is slow, as @tomasz86 has pointed out. Even if the existing code can be optimized, I am not convinced there can be huge performance gain.
Since we’re going to talk about doubts, I also don’t believe that the file synchronization issue ‘coincidentally’ emerged shortly before the release of Joplin Cloud. If the reported problem still exists in the code and hasn’t been fixed, it’s probably not due to the incompetence of the developer who made the conspiracy theory accusation. Unlike he, I wouldn’t want to unfairly criticize him.
By the way, if you’d like, you can retract your message and say that you didn’t mean it. The link I provided should be sufficient on its own.
It emerged when Google made changes to the file access API, and has nothing to do with Joplin.
For a while there was no option to use file system sync on newer Androids until someone came along and implemented the support for this new file access API.
I've only got 3,700 notes and a bit over 14,000 items to sync (resources etc.). I got a new android 13 tablet a couple of months ago, which is pretty powerful. 8 GB ram, 256 storage and a fairly powerful processor. I have excellent Internet. I use Joplin Cloud. Still, it took over 4 hours to sync my new tablet. I was surprised because that was just one thing I needed to do with my new tablet, and I'd been expecting it to be much quicker. I think if I had 30,000 notes, I'd either delete some (I continually try to keep my database clean), or create multiple databases. 30,000 notes would be horrible.
From cloud to brand new just getting setup tablet. However, it is conceivable, that because it was LATE and I was tired and the syncing continued until about 2AM, than I'm not remembering when I started. I think it was about 4 hours, but honestly, I could have started at 11PM not 10PM. But still, it surprised me.
It's surprising that you're experiencing slow synchronization despite being a Joplin Cloud user. Because in many places, Joplin Cloud, WebDAV, and even S3 are touted as exceptional solutions for slow synchronization issues. Have you been using Joplin Cloud from the beginning? Or did you switch later on?
By the way, if we're talking about reducing the number of notes in a "note-taking app" instead of increasing them, there's a problem.
I think it's deliberate that a note-taking app that has been in operation since 2018 cannot find a solution for days-long synchronization in 2024. I also believe that the problems in other synchronization solutions are deliberately overlooked or even worsened to sell Joplin Cloud to people. I'm not presenting this as a claim. It's my own opinion based on the developments, and it can change.
Apart from a one-sentence accusation message that @laurent could respond to with a clear and detailed answer satisfying everyone and ending the discussions. His lack of contribution to the topic also justifies these suspicions.
Then, you might be interested in the message in "the solution" (at the lower section of the first post in the thread) which picked by the thread starter of a Joplin thread which just updated an hour ago.
Thanks. I've read that too. But what our developer doesn't seem to understand or is ignoring is the problem caused by the first synchronization taking days.