Trying to figure out Files App sync

[p4tr1ck]

I just got a fairphone6 with /e/os on it from Murena.

I can’t figure the Files app sync logic. Is it one way only?

Or is it just file deletion that does not sync?

This is confusing and I have not found anything in the eDrive online doc.

I can’t imagine how a non-tech user could figure it out.

Is there an official description on what we can expect as users?

PS: I have taken the time to install the nextcloud mobile app on my iphone and everything regarding file sync is working as intuitively expected.

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services

[tcecyk]

@p4tr1ck

Is it one way only?

Or is it just file deletion that does not sync?

here’s an excerpt of what I once wrote (click uncollapse to see the quote):

Delete sync workspace device

what you describe is correct and that behaviour isn’t configurable. I explained what I know from reading the code here (a bit annoyed - sorry for that): I agree this is missing in the docs. A workaround to get propagating deletes is using two folders where each end has precedence to overwrite / delete per rule. RoundSync could be used to set something up like this, Syncthing has behaviour switches. Then there’s the free/commercial FolderSync.

I acknowledge missing docs, but it’s something I can’t change without pull requests in the doc repo.

You can ofc use the Nextcloud app client, it can do full (deleting) bi-directional sync optionally, but also has other pros and cons in terms of file permissions device side.

[p4tr1ck]

Thanks for clarifying. I will try and switch to the Nextcloud client.

I wonder if it’s been done like this by design or whether it would be relevant to open a bug or a feature request.

This is counterintuitive for most people to have additive only file management behaviour. Amongst other things, I believe this is the kind of thing that still corners /e/os into a niche user base.

I love my journey into data sovereignty though

[tcecyk]

@p4tr1ck

I wonder if it’s been done like this by design

remote-side deletions got neutered within this MR (some code commentary here). As there is (or was) no file versioning / trash-bin remote side, failure cases resulted in data loss.

eDrive is a bit of a crude tool, but if you know the gotchas it also has upsides, primarily its permissions as system app. But users who run into the downsides (static folders config, sync behaviour) are understandably upset.