Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting for file-conflict #12178

Open
Spielmops opened this issue Nov 16, 2023 · 3 comments
Open

Setting for file-conflict #12178

Spielmops opened this issue Nov 16, 2023 · 3 comments
Labels
enhancement hotspot: sync conflicts Sync conflict management matters

Comments

@Spielmops
Copy link

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I upload several files to my server, because they changed. And then there ist the bulk of notifications with "file-conflict, which file do you want to stay" ...

Describe the solution you'd like

A clear and concise description of what you want to happen.

I wish there would be a setting, where I could set a default action for that.

Spielmops

@joshtrichards joshtrichards added the hotspot: sync conflicts Sync conflict management matters label Nov 16, 2023
@mattbell87
Copy link

+1 from me.

I have had a bunch of these notifications sitting on my phone for well over a month. It happened after switching my server to AIO. There are so many of them I just give up 😆.

It would be great to see an "Apply to all" checkbox.

I may end up clearing out the photos/videos on my phone just so there's nothing to sync. Could be a workaround... not ideal though.

@MaciejIwan
Copy link

MaciejIwan commented Nov 18, 2023

I face with same issue, bulk conflict accept is also good solution here (currently "skip" is avaible only for single file)
Idea for developers: App could compare hashcodes for conflicted files (espesiaclly photos (size is not huge) and skip if name && hashes are the same

@tovine
Copy link

tovine commented Nov 19, 2023

I agree 100% with @MaciejIwan on this - if the file is identical then it should be automatically skipped.
This can for example be checked by first seeing if the size is the same, and then if the file size matches you could compare the checksum (so you don't have to spend time on that if the size is different).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement hotspot: sync conflicts Sync conflict management matters
Projects
None yet
Development

No branches or pull requests

5 participants