{"action":"created","issue":{"url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/453","repository_url":"https://api.github.com/repos/pimutils/vdirsyncer","labels_url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/453/labels{/name}","comments_url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/453/comments","events_url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/453/events","html_url":"https://github.com/pimutils/vdirsyncer/issues/453","id":156167980,"number":453,"title":"Write-only storages","user":{"login":"Hawk777","id":365236,"avatar_url":"https://avatars.githubusercontent.com/u/365236?v=3","gravatar_id":"","url":"https://api.github.com/users/Hawk777","html_url":"https://github.com/Hawk777","followers_url":"https://api.github.com/users/Hawk777/followers","following_url":"https://api.github.com/users/Hawk777/following{/other_user}","gists_url":"https://api.github.com/users/Hawk777/gists{/gist_id}","starred_url":"https://api.github.com/users/Hawk777/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Hawk777/subscriptions","organizations_url":"https://api.github.com/users/Hawk777/orgs","repos_url":"https://api.github.com/users/Hawk777/repos","events_url":"https://api.github.com/users/Hawk777/events{/privacy}","received_events_url":"https://api.github.com/users/Hawk777/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-05-22T19:25:03Z","updated_at":"2016-05-23T17:32:29Z","closed_at":null,"body":"Just like we have read-only storages, I would like to propose the idea of write-only storages. The idea here is that vdirsyncer would keep the data in a write-only storage up-to-date when synced, but would never pull changes from that storage (and would, in fact, destroy any changes made to that storage locally).\r\n\r\nThe use case would be a storage which is used to display information, but should never be modified by any tool. By making that storage write-only, one ensures that no accidental modifications to the storage will ever make their way back to the canonical copy of the data and, furthermore, that such accidental modifications will be erased and restored back to the canonical data on the next sync."},"comment":{"url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/comments/221039580","html_url":"https://github.com/pimutils/vdirsyncer/issues/453#issuecomment-221039580","issue_url":"https://api.github.com/repos/pimutils/vdirsyncer/issues/453","id":221039580,"user":{"login":"Hawk777","id":365236,"avatar_url":"https://avatars.githubusercontent.com/u/365236?v=3","gravatar_id":"","url":"https://api.github.com/users/Hawk777","html_url":"https://github.com/Hawk777","followers_url":"https://api.github.com/users/Hawk777/followers","following_url":"https://api.github.com/users/Hawk777/following{/other_user}","gists_url":"https://api.github.com/users/Hawk777/gists{/gist_id}","starred_url":"https://api.github.com/users/Hawk777/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Hawk777/subscriptions","organizations_url":"https://api.github.com/users/Hawk777/orgs","repos_url":"https://api.github.com/users/Hawk777/repos","events_url":"https://api.github.com/users/Hawk777/events{/privacy}","received_events_url":"https://api.github.com/users/Hawk777/received_events","type":"User","site_admin":false},"created_at":"2016-05-23T17:32:29Z","updated_at":"2016-05-23T17:32:29Z","body":"Well, up to you which if any you implement, of course. I personally like the direction parameter in a pair out of those options (although should probably have values from_a/from_b, or to_a/to_b, not just a/b)."}}
{"actor":{"display_login":"Hawk777"}}