You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for taking care of the syncing issue. I appreciate that.
With the frequency that files sync from my PC, I personally think that the ability to schedule syncing would be of benefit.
Presently I pause the app when I can, but the app will often immediately unpause itself and begin syncing again. So pausing it isn't super useful.
If I could schedule it to sync every hour for X duration, or at specific times of the day for X duration, that would be great and it would stop hammering your API.
The text was updated successfully, but these errors were encountered:
I don't know if it's intended behavior, so I haven't reported it as a bug. It happens quite consistently.
This happens whenever there are several small files seeing frequent changes and being listed in the app to upload (under 1 mb) and / or a single file is seeing rapid changes. The app will pause very briefly when I click the pause button, and then immediately unpause itself for the list of small files that quickly follow.
I use Cryptomator for my Documents folder. As you probably know, it seems to split a single file into smaller, encrypted chunks. If more than one file is changing then that can easily lead to half a dozen or so files being listed in the upload que.
It's my general practice for all cloud services. For now I let mega run at boot and then try to remember to close the app.
First, thank you for taking care of the syncing issue. I appreciate that.
With the frequency that files sync from my PC, I personally think that the ability to schedule syncing would be of benefit.
Presently I pause the app when I can, but the app will often immediately unpause itself and begin syncing again. So pausing it isn't super useful.
If I could schedule it to sync every hour for X duration, or at specific times of the day for X duration, that would be great and it would stop hammering your API.
The text was updated successfully, but these errors were encountered: