But yeah, if it's not a nightmare then this would be a really useful bit of functionality in terms of mitigating a lot of the auth pains. When a file moves between user corpora it may also appear deleted even. If the item is deleted for all users, it will get marked deleted in all user change logs. However, the file is still available to other users who still have permission to access the file. I'm not sure if it's going to be so easy though as I am guess Google might have some funky way of reading/writing locally that isn't trivially compatible with gs4/gd. If a user loses access permission to a file, the change log entry will say deleted. I am in the process of researching a better solution to this in the gargle docs, but the easiest would be to tell them to install GDFS and then let gs4 read/write to that. I'm having a problem because the resulting electron app won't trigger a web browser opening - presumably an electron thing, but could be that I've done something daft - and I am trying to avoid them the hassle of installing R themselves and getting their own token. I want to be able to give this to colleagues and let them use it to read/write from their own G Drive. For example, I want to make a layman's shiny app using the fantastic electricShine to combine R/shiny etc with electron. In theory then, if googledrive (or googlesheets4) can read/write to this local drive, and then leave that to deal with syncing to G Drive, it removes a lot of the auth hassle for users/app creators. A bit late to the party but I was wondering if it's worth re-opening this issue (or moving it to a googlesheets4 issue)? To confirm Google Drive File Stream is essentially Google's answer to Dropbox, basically it installs a local drive (usually 'G:', at least in Windows) on your computer and then you can use this like Dropbox, with both 'normal' files and Google docs/sheets etc syncing with your G Drive account.

Google drive file stream changelog