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

Bushrod "Feedback" to deletion error handling #144

Open
crspybits opened this issue Nov 21, 2018 · 0 comments
Open

Bushrod "Feedback" to deletion error handling #144

crspybits opened this issue Nov 21, 2018 · 0 comments

Comments

@crspybits
Copy link
Owner

crspybits commented Nov 21, 2018

C: SharedImages can now cope with users removing or renaming files in their own cloud storage!

R: Do other users get to keep their copy?

C: Sure... until such a point as they remove their app and try to re-install, re-download. In that case, they won't be able to re-download files that owning users removed. Or try to re-install/re-download on a new device.

R: Might want a way to save your own copy of missing files to your own storage to prevent that issue.
I’d rather it gave me the option to make my own persistent copy.

R: It might be tough to know something has gone missing until you go checking for it, so you’d need a periodic sync check to persist from your local cache. Definitely complicated.

R: But then every user would make their own persistent copy. And then where would the conversations live?

C: I think someone would have to take new ownership.

C: Just to make sure the context is apparent, this isn't really a "take it down" situation. That would be deletion from the UI. This is a -- some user goes into their Google Drive directly and removes or renames files. A, hopefully, rare situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant