/e/ Drive - sync stopped, files deleted from workspace, what will happen when sync resumes?

I was quite surprised that, when I started syncing files onto my phone with Syncthing, Murena /e/ Drive (eDrive) started syncing them up into the Murena Workspace (murena.io). I don’t want anything to be uploaded to some cloud storage without being asked.

Thus, I disabled file sync in /e/ Drive (cf. eDrive | /e/OS documentation) and then deleted the files it already uploaded from murena.io.

Now I wonder: What will happen if sync ever resumes, i.e. if Murena account sync is turned on again in the phone settings, possibly by accident? (Worst case scenario would be if all files deleted from murena.io would now also be deleted from the phone.)

e / os / eDrive · GitLab does not appear to have information on this scenario, and there is no way to submit questions there. I hope this here is the correct way to submit questions about /e/ apps used by Murena.

Hello,

Yes this is an annoying behavior that has been ongoing for a very long time without Murena solving it so far. Here is what I can tell you to reassure you:

  • I also had to deactivate file sync but it never automatically reverted to ON even after updates or upgrades.
  • The reason for me to deactivate it was that depsite Murena’s claim that the sync is bi-directional, if you delete a file/picture on the phone or the server while the sync is ON, it will not delete it on the other side. This is by design according to the doc, see quote and link below. This behaviour makes the feature unusable in practice. I guess /e/ OS developpers and leaders do not use the file sync feature :laughing: I hope that in the future the limited two-way sync on deletions will stop and instead files will be moved to the cloud Garbage bin like emails or other cloud services…

synchronization is two-way: new and changed files are uploaded from the device, and changes made in the cloud come back to the device. eDrive never deletes your files — removing a file on one side does not remove it on the other.

About the proper place to questions, I think that you are in the correct place.

You can use Gitlab to create an issue-work-item to raise attention on a problem but not to ask questions (maybe in comments but that may be frown upon if we pollute with personal complaints their development environment and repo).
Here are the issue-work-items on our two issues :

  1. When a Murena account is logging in for the first in a phone, /e/OS should not swith ON automatic file sync before checking the availability of the online storage first (depends on the plan and how much data the phone has). The user must be offered the choice (opt-in) whether to activate the feature in a notification so that he does not miss that feature.
    I have created an issue in gitlab, will send the link later.
  2. The current purposeful limitation on two-way sync for file deletion should be removed and converted to a file transfer to the bin instead.
    In that regard there is already an issue created. Let’s to to push it forward with our comments, but not sure whether that will be seen :grin: eDrive doesn't sync properly - no file deletions sync (#1) · Issues · e / os / elib · GitLab

The user must be offered the choice (opt-in) whether to activate the feature in a notification so that he does not miss that feature.
I have created an issue in gitlab.

Thanks! Where did you create the issue? I cannot see it in Work items · e / os / elib · GitLab and e / os / eDrive · GitLab does not appear to have “work items” (issues) enabled at all.

The above are "Searches`

In order to Report an issue | /e/OS documentation please notice that one is asked to use an email ID derived from an account at murena.io.

wooo, there seems to be a problem, I do not see any issue anymore, including the two I created :slight_smile:

Maybe it is a protection from gitlab to limit access after a given number of interraction per day.
Let’s wait for tomorrow