{"action":"closed","issue":{"url":"https://api.github.com/repos/owncloud/client/issues/5118","repository_url":"https://api.github.com/repos/owncloud/client","labels_url":"https://api.github.com/repos/owncloud/client/issues/5118/labels{/name}","comments_url":"https://api.github.com/repos/owncloud/client/issues/5118/comments","events_url":"https://api.github.com/repos/owncloud/client/issues/5118/events","html_url":"https://github.com/owncloud/client/issues/5118","id":170665544,"number":5118,"title":"UX suggestion: Split the concepts of file synchronization and file deletion","user":{"login":"stefanmohl","id":12941516,"avatar_url":"https://avatars.githubusercontent.com/u/12941516?v=3","gravatar_id":"","url":"https://api.github.com/users/stefanmohl","html_url":"https://github.com/stefanmohl","followers_url":"https://api.github.com/users/stefanmohl/followers","following_url":"https://api.github.com/users/stefanmohl/following{/other_user}","gists_url":"https://api.github.com/users/stefanmohl/gists{/gist_id}","starred_url":"https://api.github.com/users/stefanmohl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefanmohl/subscriptions","organizations_url":"https://api.github.com/users/stefanmohl/orgs","repos_url":"https://api.github.com/users/stefanmohl/repos","events_url":"https://api.github.com/users/stefanmohl/events{/privacy}","received_events_url":"https://api.github.com/users/stefanmohl/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-08-11T14:52:56Z","updated_at":"2016-08-11T14:56:55Z","closed_at":"2016-08-11T14:56:54Z","body":"For new users, it is quite difficult to sort out the file deletion and synchronization relations, at times resulting in the contents of the local original folder getting deleted with resulting data loss. A suggestion is to simply make deletion and synchronization separate concepts.\r\n\r\n1. A file that is synchronized will stay in sync, i.e. files get deleted on server and all clients if they are deleted at either end. Note: This requires the user to perform an actual deletion operation on either the server or a client for the file to get deleted.\r\n2. When synchronization for a file is turned off, that is all that happens. The file status between server and client is no longer kept in sync, and nothing is changed on either end. In particular nothing gets deleted as a result of turning off synchronization.\r\n\r\nFor turning on synchronization:\r\n\r\n1. When synchronization is turned on, files that are missing at either end are copied to the other end, but nothing is deleted.\r\n2. When synchronization is turned on, files that differ by checksum are marked as different and do not get synchronized. If the file is deleted at either end, synchronization for the file gets turned on again and the remaining version of the file gets copied to both sides.\r\n 2. For files that differ at both ends and therefore do not get synchronized, it would be nice if some easily accessible diff command were added to the UI, as well as a force push to server or pull from server option were added. This would overwrite one version of the file and enable synchronization.\r\n3. When synchronization is turned on, the creation date is updated to the oldest creation date (the file has to have been at least that old). The modification date gets updated to the newest of the modification time (it was modified at least that late).\r\n\r\nThe effect is that nothing gets deleted unless the user manually performs a delete at either end; something that seems quite important if you are using OwnCloud as a backup solution."}}
{"actor":{"display_login":"danimo"}}