You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: