Earlier quoted context omitted.
What you are describing sounds like two distinct files with the same content. The change only affects the same file that has been "hard linked" into two separate folders. Copies of files are unaffected.
Was this hard-linking only possible when performing an action via the web/app interfaces? Because the wording makes it extremely confusing. Even I thought this was going to affect copies of the same file in multiple places. I don't notice any points in their support doc which tells me otherwise.
Google Drive: Shortcuts replacing files and folders stored in multiple locations
71–74 of 74 posts
Re: Google Drive: Shortcuts replacing files and folders stored in multiple locations
#72Until today, I didn't know you could create hard links (ie "multi-parent" files/folders) in Google Drive. How did one achieve this? I would like to know, because I'm wondering if I have unintentionally done so. I gather this is completely different from "Make a copy" in the web UI. So how did you do it?
Re: Google Drive: Shortcuts replacing files and folders stored in multiple locations
#73Earlier quoted context omitted.
I switched from Dropbox to Nextcloud, and within a couple of months from Nextcloud to Google Drive. Really didn't like the software and it was so slow since I wasn't self-hosting it, but renting it from Hetzner. Currently thinking of switching from Google Drive to Syncthing, since the new Google Drive clients suck and Google is going to be making my service worse with the new G Suite changes.
The new Google Drive client is horrible with lots of files. It is doing something very wrong in its sqlite database and completely killing performance of the drive where AppData lives, even if the Google drive folder is on a different disk.
Re: Google Drive: Shortcuts replacing files and folders stored in multiple locations
#74Earlier quoted context omitted.
This is a concern of presentation, not the backing implementation: How to present (approximately) hardlinked files to users, with the possible complications of varying support for hard and soft links or other mechanisms across the various client implementations of Google Drive. There's advantages and disadvantages to using either.
I see. I don't use Drive via the web/app interfaces much but essentially, hard links are a thing already and users must've inadvertently created them anyway when doing actions via web/app. Any idea if these hard links can be created with Drive clients on Mac/Win?